SQL Codes › SQL Return Codes -1 through -999 › -326 - MAXIMUM NUMBER (number) OF DIAGNOSTICS AREAS EXCEEDED

-326 - MAXIMUM NUMBER (number) OF DIAGNOSTICS AREAS EXCEEDED

Explanation

In the message text, the number variable gives how many diagnostics areas are allowed in a unit of work.

This error was generated because:

• A series of SQL statements have failed, or because
• SIGNAL statements were executed, or because
• Both of the previous occurred.

A single procedure statement and any related condition-handlers were executed, but an error-handler for the most recent error failed and there was not enough room to store additional error information. Error-handling was therefore aborted.

The SQLSTATE that equates to this SQL return code is 0Z001.

User Response

Examine the series of errors that caused this error by either performing GET DIAGNOSTICS statements within your procedures or by the short-cut method of looking at the DIAGNOSTICS AREA dumps directly in the PXXSQL file in the MUF. An example DIAGNOSTICS AREA dump follows:

DIAGNOSTICS AREA 1/3 (23039A78) STATEMENT INFO (23039AB4:142/440 BYTES RELEVANT):
      offset:0
        <-     Y    CALL                                    > <-                                                  >
        <-04004E0400CCDD000000000000000000000000000000000000> <-00000000000000000000000000000000000000000000000000>
        <-00020800043133000000000000000000000000000000000000> <-00000000000000000000000000000000000000000000000000>
      offset:100
        <-                                          >
        <-000000000000000000000000000000000000000400>
        <-000000000000000000000000000000000000000007>
DIAGNOSTICS AREA 1, CONDITION INFO #1 of 2 (23039C6C:152/3072 BYTES RELEVANT):
      offset:0
        <-                  57S04 IN ERRHANDLER1:INDEX FULL > <-- DBID=16                                         >
        <-000000040004020402FFEFF4CD4CDDCCDCDCDF7CDCCE4CEDD4> <-64CCCC7FF44000000000000000000000000000000000000000>
        <-0100000006000B000B57204095059981543591A95457064330> <-004294E1600000000000000000000000000000000000000000>
      offset:100
        <-                                               0K0> <-00>
        <-00000000000000000000000000000000000000000000004FDF> <-FF>
        <-00000000000000000000000000000000000000000000000020> <-00>
DIAGNOSTICS AREA 1, CONDITION INFO #2 of 2 (2303A86C:152/3072 BYTES RELEVANT):
      offset:0
        <-                  MAXIMUM NUMBER (3) OF DIAGNOSTIC> <-S AREAS EXCEEDED                                  >
        <-000000040004030403DCECDED4DEDCCD44F54DC4CCCCDDEECC> <-E4CDCCE4CECCCCCC4000000000000000000000000000000000>
        <-010000000700010001417944405442590D3D06604917562393> <-20195120573554540000000000000000000000000000000000>
      offset:100
        <-                                               0Z0> <-01>
        <-00000000000000000000000000000000000000000000004FEF> <-FF>
        <-00000000000000000000000000000000000000000000000090> <-01>

The word CALL, located 10 bytes into the STATEMENT INFO dump, indicates that these errors occurred during execution of a CALL PROCEDURE statement. CONDITION INFO #1 contains the error message (VARCHAR(128) at offset 16 that was generated prior to, and precipitated, the -326 (message for -326 is in CONDITION INFO #2), followed by the SQLSTATE. This is sufficient, in this case, to tell us that an INDEX FULL occurred during execution of an error handler named ERRHANDLER1 in the called procedure.

In cases where more information is required, examine DIAGNOSTICS AREA 2 and DIAGNOSTICS AREA 3 to see the sequence of errors that led to the current situation. In cases where only the first diagnostics area is dumped but prior (instigating) error conditions are suspected, you can search backwards through the PXXSQL file to find the previous DIAGNOSTICS AREA dumps. The prior dumps could also be marked DIAGNOSTICS AREA 1 because only one area might have been in use at the time of the original error.