mohdzain
15th February 2007, 05:44
When i open more than 4 sessions regardless of whether is a finance,distribution or manufacturing it will prompt out this error
Error : SLQState QP999: Database not on (error 510) (vrc_search .....
Fatal Error : Error 510 (Database not on) on select
Fatal Error : cannot continue in tdpur0197m000 in DLL: ottdll -- i'm not sure what it goes here. But tdpur0197m000 is the last session that i open
Is it a database problem?? Appreciate your help. Thanks
Zain
mohdzain
30th March 2007, 10:51
I was finally able to solve the problem after few weeks of frustration by restarting server and the database. It seems that db2cli.ini which resides in the /$DBINSTHOME/sqllib/cfg need to add some line under [common]. Add the following line
[common]
MultiConnect=3
IgnoreWarnings=1
CloseOpen=1
UseLightOutputSQLDA=1
Save the file and login back to LN. Now i'm able to browse thru the session without that error.
jaya_ra
16th November 2012, 09:04
Hi,
Every alternative days we are getting the error "Error 510 , database not on, can not continue" We are unable to figure out the cause of it. So once we get the error, users cant use the system , and we need to restart ERPLN server. Can anyone help us on this.
Regards,
P. Jayanthi
bdittmar
16th November 2012, 09:55
Hi,
Every alternative days we are getting the error "Error 510 , database not on, can not continue" We are unable to figure out the cause of it. So once we get the error, users cant use the system , and we need to restart ERPLN server. Can anyone help us on this.
Regards,
P. Jayanthi
Hello,
why MSSQL in DB2 thread ?
Avoid double post, please.
http://www.baanboard.com/baanboard/showthread.php?t=61173
http://www.baanboard.com/baanboard/showthread.php?t=31367
Check all database setup and configurations.
Is the DB stopped (e.g. for Backup) and not restarted ?
Is application and DB on same maschine?
a.s.o.
Regards
jaya_ra
17th November 2012, 14:22
Hi,
The DB was not stopped. The backup is realtime backup. Application and DB reside on the same machine. The same setup we are using for about 10 years, but suddenly this error started to appear.
Thks & Rgds,
P. Jayanthi