×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 16-Dec-2011 09:18 , Dan Kimmel wrote:
55019 The table is in an invalid state for the operation
Anyone know what this really means? I have a SQL insert trigger on
a table that deletes and inserts records into another table. The
triggered table inserts worked, the inserts into the other table
threw this error. Started throwing the error about 6:00 last night
and continued until about 9:44 this morning when it started working
again.
The associated SQLcode to that SQLState has a corresponding SQL####
message. The joblog for the code that was running when the error was
received may provide more specific details, including the message and
replacement text, plus any preceding message(s) that may have
contributed to the condition effecting the SQLcode as the logged error
message. Also knowing the time-frame, the journal for the "other table"
can be reviewed by DSPJRN for what happened to that TABLE, both when the
error started and later stopped occurring, and in what job the work
against the table transpired of which the other joblog(s) may be
reviewed as well.
Otherwise various SQLcodes which might arise from that SQL state are
listed; just repeat "find" requests in the text of [in the respective
release docs]:
_Listing of SQL messages_
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzala/rzalaml.htm
"
These tables list SQL messages. Use these tables to find message text,
cause text, recovery text, and corresponding SQLCODEs and SQLSTATEs.
You can use the following tables with both positive and negative
SQLCODEs. Take the absolute value of the SQLCODE, then append it to the
letters SQL (for SQLCODEs less than 10 000) or the letters SQ (for
SQLCODEs greater than or equal to 10 000) to determine the message
identifier. Each SQLCODE corresponds to one or more SQLSTATEs.
"
Regards, Chuck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.