Using the Database Server Log File

Use this procedure to access and use the information in the Lawson Database Service log file.

  1. Using a text editor, open the %LALOGDIR%\lads.log to view the contents. The file will contain entries similar to the following example: 
    Wed Jul 18 15:45:24 CDT 2007 : Response(com.lawson.lajavarts.db.dbserver.
   ConnectionState@1507fb2)=LOCK_RELEASE;SUCCESS=TRUE,RESOURCE=com.lawson.
   db.dataarea.mysamplehr,ID=0113dae9-a818-0000-0000-00044592f0c8
Wed Jul 18 15:45:24 CDT 2007 : Wrote 109 bytes
Wed Jul 18 15:45:24 CDT 2007 : SelectionKey is writeable
Wed Jul 18 15:45:24 CDT 2007 : Write is complete, registering for read
Wed Jul 18 17:00:47 CDT 2007 : SelectionKey is readable
Wed Jul 18 17:00:49 CDT 2007 : Connection lost (caught IOException during read 
   from socket)
Wed Jul 18 17:00:49 CDT 2007 : Releasing all locks(com.lawson.lajavarts.
   db.dbserver.ConnectionState@1507fb2)
Wed Jul 18 17:00:49 CDT 2007 :   Releasing 0113dae9-a818-0000-0000-00024592f0c8
Wed Jul 18 17:00:49 CDT 2007 :   Releasing 0113dae9-a818-0000-0000-00054592f0c8
Wed Jul 18 17:00:49 CDT 2007 :   Releasing 0113dae9-a818-0000-0000-00014592f0c8
Wed Jul 18 17:00:49 CDT 2007 :   Releasing 0113dae9-a818-0000-0000-00004592f0c8
Thu Jul 19 09:04:16 CDT 2007 : Notifying laservice of started status
Thu Jul 19 09:04:16 CDT 2007 : LADS Server has been started successfully
  2. Locate the date and time of the error you are trying to troubleshoot to determine if there is any helpful information in this file.

    Most of the entries will indicate successful start or stop procedures. Some, as shown in the above example, may indicate the type of database error that occurred.

  3. Use this information to understand any problems with lads.
    Note: 

    This file will not record information about application processing; it only records information about the Lawson Database Service itself.