How Do I Interpret the Error Information?

The ladb.log file contains useful information that might help you resolve errors. The ladb.log file includes:

A brief error message from the Oracle server.
The last SQL statement executed.
The API being processed.
The row being used.
The index keys being used.

Here are some tips to aid in understanding the information in log file.

When users come to you with an error that they saw on their screen, they might frequently tell you that they are getting an "Oracle 59" error. This is not really the case. The number 59 is an internal error number used to identify that the error originated from the Oracle database. For example, the user who encountered the reorganization problem as shown above would have seen the following message on the screen:
```
 lawsonEnv-> dbreorg keyserpl
Processing KEYSERPL
CKPOINT Reorganizing:
DB Error: Oracle database error (59)
Additional Information Is 959, 5401.
```
The Additional Information section contains the actual error number returned by the Oracle database.

The most recent error written to the ladb.log file is not always the real cause of the problem. The same goes for errors returned to the screen. Seemingly nonsensical error messages are often caused by other, underlying problems that result in other conditions also being exhibited. For example, while running an application, a user sees the following message on the screen:

DB Error: Oracle database error (59)
Additional Information Is 1008, 6719.

At first glance, this error appears to be a problem with the oradb11 / oradb12 database driver. However, when examining the ladb.log file, we find that the real problem is something else entirely.

UID   PID  PPID  C    STIME TTY       TIME COMMAND
  chrisj  6760  6730  0 10:03:37 ttypf     0:00 dbtest1 -df TESTPROD

LastFunction = FIND_PREV on file THEFILE Path=1 oradb10_pid = 6761
Parse Error Offset (may not apply) = 0
Error Text = ORA-01000: maximum open cursors exceeded

Mon Mar 17 10:03:55 2000: Trouble (1000) opening PREV cursor.
  UID   PID  PPID  C    STIME TTY       TIME COMMAND
  stevej  6760  6730  0 10:03:37 ttypf     0:00 dbtest1 -df TESTPROD
LastFunction = FIND_NXT on file THEFILE Path=1 oradb10_pid = 6761
Parse Error Offset (may not apply) = 0
Error Text = ORA-01008: not all variables bound

The binding problem was really just a symptom of the fact that the maximum number of open cursors had been exceeded.