mostrightfuture
29th December 2004, 14:49
Hi friends,

I have copied the complete Baan environment from one Live server to another Test server, did following:

Installed SQL server database
Installed BaanERP
copied BSE folders (Applications, dict, tools)
copied all td* files from BSE/lib to new server

Now I try to start the Baan on the new Test server, I am getting the following error:

bdb_errno 510 on ttadv999
Error 510 (Database not on) on Select
Can not continue in ottstpstdlib (mess)

Let me tell you one more thing, the database location on the Live Server and Test server are different. On Live Server, SQL server is installed on "D" drive while on the Test Server, SQL server is installed on "H" drive.

How could I change the location of the Server?

Thanks in advance
Mahmood

Dikkie Dik
30th December 2004, 14:19
It depends a littel on your configuration, but I expect that you have to change the content of your %BSE%\lib\tabledef6.2 file to the right SQL server config.

Hope this helps,
Dick

tspratap
10th January 2009, 09:43
hello, i am getting same error , but i am not able to solve , have you any resources to solve it.

thanks

vinceco252
11th January 2009, 08:00
As Dick says, check your $BSE\lib\tabledef6.2 file. Also, you may want to check your $BSE\lib\defaults\db_resource and $BSE\lib\bse_vars files (neither of these files is required to exist, so you may not find them) to see if there's anything in there that may be affecting this. Also, make sure your database IS on... ;-)

Vince

RedBatz
16th January 2009, 20:25
Hi,
check if user baan and baandb have same passwords as Live environment.

cherokee
8th December 2018, 07:54
we copied the prod db to the dev environment and I got the error bdb_errno 510 on ttadv999

make sure your database IS on... ;-)

The DB is available, how it is/gets turn on? please advise

bhushanchanda
8th December 2018, 11:04
Check the database name defined in $BSE/lib/defaults/db_resource file. Also check if the database services are running.

cherokee
8th December 2018, 14:23
thank you for you help. By the way we are in BaaN 5

I will ask to check the DB services to be checked.

This is our db_resource, I do not see db name in this.

dbsinit:01
bdb_max_session_schedule:50
msql_level1:0
msql_lock_timeout:5
msql_max_free_cursors:0
msql_retained_cursors:0
msql_opt_rows:0
msql_cursor_type:2
msql_use_ffo:1
msql_force_order:1

Thank you for your help again.

ERPpals
10th December 2018, 20:58
Hi,

Check if the tabeldef is pointed to correct DB or not.

Thanks

cherokee
10th December 2018, 22:20
Hi ERPpals

Yes, it is pointing to the right db name, srvsqldev, there is a long list of tables, I put only the last rows. (please see attachment for the error we get)

.......
whwmd210:*:msql7(MSQL_SERVERHOST=srvsqldev):Y
whwmd215:*:msql7(MSQL_SERVERHOST=srvsqldev):Y
whwmd300:*:msql7(MSQL_SERVERHOST=srvsqldev):Y
*:*:msql7(MSQL_SERVERHOST=srvsqldev):N

Thanks for your help.

mark_h
11th December 2018, 16:30
When you copied did you copy company 000 also? I mean we use oracle but tabledef still has 000 in it pointing to a different name - are all of your still in msq17?

cherokee
11th December 2018, 18:31
In the procedure document I got(created by someone few years back), we have to regenerate the users after db copied, will that tell me that the backup includes company 000?

And yes same MSQL version.

Thank you, appreciated your help.

ERPpals
11th December 2018, 18:48
Hi,

What's your OS (Windows/Unix/Linux) could you please see the $BSE/log and see if its writing any errors there, if windows, check event viewer and share that info.

Thanks

cherokee
11th December 2018, 21:04
- we are in Windows

This is(in the code tags below here) in the log directory a file is created by the process that does the refresh process. All other files are dated before all this started.

Changed database context to 'baandb'.
Changed database context to 'master'.
Processed 9567056 pages for database 'baandb', file 'baandbdata' on file 1.
Processed 273 pages for database 'baandb', file 'baandblog' on file 1.
RESTORE DATABASE successfully processed 9567329 pages in 328.897 seconds (227.258 MB/sec).
Changed database context to 'baandb'.

(130 rows affected)
Msg 15150, Level 16, State 1, Server SRVSQLDEV, Procedure sp_revokedbaccess, Line 51
Cannot drop the user 'INFORMATION_SCHEMA'.
Msg 15150, Level 16, State 1, Server SRVSQLDEV, Procedure sp_revokedbaccess, Line 51
Cannot drop the user 'sys'.

Any specific data from the Event Viewer should I look in to? there is so much things in it.

Thanks again.

mark_h
11th December 2018, 23:58
I just know everytime we do a full clone (copy application directories) versus just refreshing the data I get a new set of challenges. From making sure tabledef6.1 is correct to making sure ora table spaces are correct. I do not know about windows but we also have some $BSE/etc startup files that we have to make sure are correct - like rc.set_vars. I am not even sure that comes into play with this issue. Since you cloned from prod to a test you might just try search all the $lib files (and sub directories) for anything that might be lingering with something pointing to production.

Not sure about your setup but our tabledef6.1 has stuff like this in it.

trwoc000:701:oracle8(ORACLE_SERVICE_NAME=oracleinstancename):Y
tssma000:701:oracle8(ORACLE_SERVICE_NAME=oracleinstancename):Y
ttaad200:000:oracle8(ORACLE_SERVICE_NAME=oracleinstancename):Y
tuxch001:701:oracle8(ORACLE_SERVICE_NAME=oracleinstancename):Y
*:000:oracle8(ORACLE_SERVICE_NAME=oracleinstancename):N

Some company 000 tables are specifically spelled out. I am not really sure why. But we also just had a case where we cloned for years and years (company 000 is shared with production and simulation company). But we could not get the sim company to work - for some reason we had a table in sim company pointing to production instance(it worked on these years) but now it does not. The table was also an empty parameter table for a module we do not use. Like I said each clone or copy is an adventure here lately.

cherokee
12th December 2018, 16:41
Thank you, we were able to started it. It was an issue with the user at the DB level, DB admin recreated the user in MySQL and matching the password with the prod server and we were able to login. I still not sure if all works but for now we have access to the system.

Thank you for all your help!