ultegra
21st April 2009, 18:48
Hi,

Is anybody had experience on this error?

When LN installation users/LN admin user login to my LN backup server via Worktop, I have these error:

process 1 - error : bdb_errorno 510 on ttadv999
process 1 - error : bdb_errorno 13873 on ttadv999
process 1 - error : [MS_E_READING] Cannot read session or object (ttstpoledaem).

Normal users login will only get error 510 on ttadv.

When I restore sequention dump from my production server, the log file will display Can't lock table (error 510) for tables.

this server is running on MS Windows 2003 x64 SP2, MS SQL 2005 x64 SP2 and LN 6.1 FP3.


Anyone can help here? Many thanks!!

toolswizard
22nd April 2009, 17:12
This error indicates that the database is not started / up. However it can be misleading. If the database is up, then check the OS level permissions for the directories and files of your database and make sure that the users can access them. Make sure your groups have been created at the OS level also.

maximus
23rd April 2009, 21:48
We have also seen this error in the past when $BSE/lib/msql/msql_users did not have an entry for the user OR the username or password in the file were incorrect.

ranjankool
31st October 2013, 21:25
Hi,
I am also getting same problem, looked at above point, but could n't resolve the issue. Could you please help what could be the issue.

Regards
Ranjan kumar

bhushanchanda
1st November 2013, 05:34
Hi,

Try to create the user again ! Or, just do a convert to runtime for all users and log out and log in again.
Normally it happens when you move your data from one box to other..

toolswizard
1st November 2013, 22:43
Was it working and now it is not?

I ran across another issue with the oracle SID during an upgrade. We could no longer use the ORACLE_SID parameter, and had to change it to ORACLE_SERVICE_NAME. This was during a porting set upgrade on LN, to support the upgrade of Oracle.

If you can connect through easy sql or other tool to the database, it is usually a permissions or parameter issue.