• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

Database not running error

 5 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Saurabh
Veteran Member Send Private Message
Posts: 94
Veteran Member
5/6/2009 2:38 PM

Hi All

We are on Lawson S3, LSF 9.0.0.4, SQL2005

We recently had a failure of our database server and had to rebuilt a new sql server (using the same name, same domain but different IP address).

We restored the following databases DEV, GEN,LOGAN and MSCM90

However now when we try and start lawson we are getting the following error in ladb.log

*****ladb.log************* start

Wed May 06 16:23:32 2009: ladb (main): can't create shared memory
    Invalid argument (22)
Wed May 06 16:23:32 2009: ladb (ShutDown): initiated (-2)
Wed May 06 16:23:32 2009: ladb (ShutDown): startup
ladb: Database server startup failed.

*****ladb.log************* end

Any tips from anyone would be great on what steps needs to be done if we have to restore the database

regards

Saurabh

 

Saurabh
Veteran Member Send Private Message
Posts: 94
Veteran Member
5/6/2009 2:42 PM

Just to add to the above we have done a restart of both apps and sql server a few times

Roger French
Veteran Member Send Private Message
Posts: 549
Veteran Member
5/6/2009 4:42 PM
Have you checked out KB article 1090723 ?
John Costa
Veteran Member Send Private Message
Posts: 154
Veteran Member
5/6/2009 7:29 PM

Since you rebuilt your entire SQL-Server box, I would make sure the database account(s) specified in your CAPS files for DEV, LOGAN, GEN, and MSCM90 have been created at the SQL-Server level.  The database restores you've done restore the user accounts at the database level but SQL-Server may consider those uses as "orphan" accounts because they don't tie to SQL-Server accounts.

Connect to SQL-Server via Management Studio, then open the Security folder followed by the Logins folder.  Make sure your user accounts and their passwords have been created here and those accounts have been "mapped" to the correct databases, schemas (such as "dbo"), and database roles (such as "db_owner").  You may have to drop the database accounts first before creating them at the server level.  I know there are SQL scripts that will do everything I described but I am so use to using the Management Studio interface.

Hope this helps.

_________________ John - Wichita, KS
Jimmy Chiu
Veteran Member Send Private Message
Posts: 641
Veteran Member
5/6/2009 7:48 PM

use this script to relink the orphan user account in SQL2005

use databasename;
exec sp_change_users_login 'Auto_Fix', 'userID'
 

Saurabh
Veteran Member Send Private Message
Posts: 94
Veteran Member
5/6/2009 9:55 PM
The logins and sids were realigned. Had checked and ensure that schema of db's matched the MICROSOFT file.

The issue seemed to have been the following
a. Lawson uses static port for SQL (we have three environment DEV, UAT and PREPROD)
in the new environment we had the port set to a different number

b. we had 3 hung java.exe processes whic had to be manually killed (so the article was close but does not specify which processes to look for). the java.exe processes did not seem to have a reference to any of the environments and did not get killed off even after doing a restart

I have now got the Productline databases up but am still getting the error
"Database is currently unavailable. " from the MSCM portal

Many thanks for the continused help
Saurabh