I updated my code so that my DB2 table is cleared of all existing records through the use of this statement:

Call con.Action ( LCACTION_TRUNCATE )

However, when my code attempted to insert one new record into the table, I got this nasty LSX error:

LSX Error occurred in UPDATE_TABLE
LSX Error: Status 12325
LSX Error: Err = 12325
LSX Error Line 126
LSX Error: Status Text = Error: [IBM][CLI Driver][DB2] SQL0904N Unsuccessful execution caused by an unavailable resource. Reason code: "00D70014", type of resource: "00000200", and resource name: "S001 .TABLE1 ". SQLSTATE=57011, Connector 'odbc2', Method -Insert- (-904)

Relatively befuddled, I began searching the internet for what the above could possibly mean. A google search on Unsuccessful execution caused by an unavailable resource and found this message reference:

SQL0904N

Unsuccessful execution caused by an unavailable resource. Reason code: "<reason-code>", type of resource: "<resource-type>", and resource name: "<resource-name>".

Explanation: The SQL statement could not be executed because resource "<resource-name>" of type "<resource-type>" was not available at the time for the reason indicated by "<reason-code>". Refer to the Problem Determination documentation of DB2 for MVS for an explanation of resource type codes.

Taking the DB2 InfoCenter's advice, I looked for more info about the "00D70014" Reason Code. Another Google search on Problem Determination documentation of DB2 for MVS helped me find my way to the DB2 for z/OS and OS/390 - DB2 Version 7 Library Page, where I used the "Search Version 7 BookManager Shelf" to search on "00D70014". This yielded the following:

00D70014

Explanation: An attempt to extend a data set failed, because a problem was detected in media manager services.

This reason code is issued by the following CSECT: DSNPXTN0

System Action: Abort the request.

User Response: Notify the operator, system programmer, or database administrator.

Operator Response: Notify the system programmer or database administrator.

System Programmer Response: Notify the database administrator if appropriate. Otherwise, check the packs available to the data set. They may merely be full or the data set may have reached its maximum allowable extents. For additional information, see the description of message DSNP001I.

Problem Determination: Obtain console sheet showing associated DSNP001I, DSNO007I, or DSNP011I messages and any related messages preceding them. This documentation will assist you in determining the cause of the problem. For additional information, see the description of these messages.

As it turned out, the database I was updating was out of extents, and needed to be moved to a new pack. Wow. I'll never make fun of cryptic DB2 error messages again!

No comments.