View Full Version: Error Is Database Error (94).

LawsonTalk > Coding, Program Errors and Bugs > Error Is Database Error (94).


Title: Error Is Database Error (94).


trezaei - October 26, 2006 12:27 AM (GMT)
We have a custom table called XACTUALHRS. When running a custom program, the job goes into recovery with this error

File ITTEST/XACTUALHRS.
FindDBRec error is Database error (94).
Elapsed Time . . . . . .: 00:00:00

Any ideas what this might be ?

Thanks

T

Ragu - October 26, 2006 12:59 AM (GMT)
Did you look at thr database log ? $LAWDIR/system/ladb.log ?
That will usually give you more details.
Is date one of the keys to an index ? Quite possibly, when populating the key, the date is formatted incorrectly

trezaei - October 26, 2006 01:08 AM (GMT)
Heh heh, yes it was the date. I actually figured it out and was coming back here to post the reply and ... Thank Ragu. good catch.

T

Milo - October 26, 2006 06:59 PM (GMT)
Where can a listing of the errors that Ladb returns be found? That will help us all... :nix:

trezaei - October 26, 2006 11:05 PM (GMT)
Well here are the Micro Focus COBOL Status Key Values. There is probably another list out there somewhere.

CODE

Status Key Description
9 001 Insufficient buffer space
9 002 File not open when access attempted
9 003 Serial mode error
9 004 Illegal file name
9 005 Illegal device specification  
9 006 Attempt to write to a file opened for input
9 007 Disk space exhausted
9 008 Attempt to input from a file opened for output
9 009 No room in directory or directory does not exist
9 010 File name not supplied
9 012 Attempt to open a file which is already open
9 013 File not found
9 014 Too many files opened simultaneously
9 015 Too many indexed files open
9 016 Too many devices open
9 017 Record error: probably zero length
9 018 Read part record error: EOF before EOR or file open in wrong mode
9 019 Rewrite error: open mode or access mode wrong
9 020 Device or resource busy
9 021 File is a directory
9 022 Illegal or impossible access mode for OPEN
9 023 Illegal or impossible access mode for CLOSE
9 024 Disk I/O error
9 025 Operating system data error
9 026 Block I/O error
9 027 Device not available
9 028 No space on device
9 029 Attempt to delete open file
9 030 File system is read only
9 031 Not owner of file
9 032 Too many indexed files, or no such process
9 033 Physical I/O error
9 034 Incorrect mode or file descriptor
9 035 Attempt to access a file with incorrect permission
9 036 File already exists
9 037 File access denied
9 038 Disk not compatible
9 039 File not compatible
9 040 Language initialization not set up correctly
9 041 Corrupt index file
9 042 Attempt to write on broken pipe
9 043 File information missing for indexed file
9 045 Attempt to open an NLS file using an incompatible program
9 047 Indexed structure overflow
9 065 File locked  
9 066 Attempt to add duplicate record key to indexed file
9 067 Indexed file not open
9 068 Record locked
9 069 Illegal argument to ISAM module
9 070 Too many indexed files open
9 071 Bad indexed file format
9 072 End of indexed file
9 073 No record found in indexed file
9 074 No current record in indexed file
9 075 Indexed data file name too long
9 077 Internal ISAM module failure
9 078 Illegal key description in indexed file
9 081 Key already exists in indexed file
9 100 Invalid file operation
9 101 Illegal operation on an indexed file
9 102 Sequential file with non-integral number of records
9 104 Null file name used in a file operation
9 105 Memory allocation error
9 129 Attempt to access record zero of relative file
9 135 File must not exist
9 138 File closed with lock - cannot be opened
9 139 Record length or key data inconsistency
9 141 File already open - cannot be opened
9 142 File not open - cannot be closed
9 143 REWRITE/DELETE in sequential mode not preceded by successful READ
9 146 No current record defined for sequential read
9 147 Wrong open mode or access mode for READ/START
9 148 Wrong open mode or access mode for WRITE
9 149 Wrong open mode or access mode for REWRITE/DELETE
9 150 Program abandoned at user request
9 151 Random read on sequential file
9 152 REWRITE on file not opened I-O
9 158 Attempt to REWRITE to a line-sequential file
9 159 Malformed line-sequential file
9 161 File header not found (also described as illegal intermediate code
<<Check MF's latest description>>

9 173 Called program not found
9 180 End-of-file marker error
9 182 Console input or console output open in wrong direction
9 183 Attempt to open line-sequential file for I-O
9 188 File name too large
9 193 Error in variable length count
9 194 File size too large
9 195 DELETE/REWRITE not preceded by a successful READ
9 196 Record number too large in relative or indexed file
9 210 File is closed with lock
9 213 Too many locks
9 218 Malformed MULTIPLE REEL/UNIT file
9 219 Operating system shared file limit exceeded
9 220 Attempt to execute more than one SORT or MERGE at once (F)
You've coded your program for this, prohibited under ANSI COBOL rules.
Recode so it doesn't do more than one SORT or MERGE at any one time.

aarganesh - October 27, 2006 04:08 AM (GMT)
When a batch job goes to "Needs Recovery" mode, how to troubleshoot?
The first thing that I would do will be to examine the log file. I mostly use LID and then test it via portal. So I see the log file. A copy of the log file is located under $LAWDIR/system/joblog & if a ls -ltr is used, its usually the last file lapm.XXXX file. Again, ladb.log is also a good place to look for additional information, so take a look at both these files.

Check these files & I'm sure one can find out the rest of the problem. We came across an issue recently, where the system was unable to detect newly added columns in the EMPLOYEE table, due to which this issue occured.

We tried to recover the job once or twice & it failed. We then checked the logs & were able to solve the issue ourselves. Once the problem was resolved, we tried recovering back and it didn't. So we removed the job & submit it once again and it was all good to go this time.

Cheers
Ganesh .R



Hosted for free by InvisionFree