Database Analyzer Extract Job finished with RC=16 and a SQLCODE -438 error message
Article ID: 262814
Updated On:
Products
Issue/Introduction
A Database Analyzer Extract Job finished with RC=16 and the following SQLCODE -438 error message.
SQL ERROR OCCURRED!!! SQLCODE -438, SQLSTATE=00000 Details follow:
1) SQL statement text issued that received error
2) object IDs information (if available)
3) error assistance text (for common errors only)
4) standard DB2 SQL diagnostic text
5) a recovery status for this SQL statement
SQLERR: RALRTOS (Internal info: DROP_CTV_DGTT , EXTRPTIN )
SQL: Length=36 x24
SQL: DROP TABLE SESSION.RAOS_CTV_2000
Current object values could not be determined (PREPARE, OPEN or FETCH error)
DSNT408I SQLCODE = -438, ERROR: APPLICATION RAISED ERROR WITH
DIAGNOSTIC TEXT: PTABDBS: PTMBDB not connected.
DSNT412I SQLCABC = 131 SQLCA BYTE COUNT
DSNT418I SQLSTATE = 00000 SQLSTATE RETURN CODE
Severe SQL error occurred and recovery not possible (PREPARE or OPEN cursor)
Environment
Release : 20.0
Resolution
Table RAOS_CTV_2000 was in tablespace PTDB.PTTSROS7 and the Database Analyzer Extract Job was not able to connect to the tablespace.
After the a reorg of the tablespace PTDB.PTTSROS7 the Database Analyzer Extract Job finished correctly.
On a busy Db2 subsystem the tables PTI.RAOS_CTVAP_2000 and PTI.RAOS_CTV_2000 may grow significantly. To avoid this kind of problems PTF LU04989 changed the COLLECT_CTV valid value range from 13-32767 months to 1-32767 months. The default value is still at 13 months but you can reduce the COLLECT_CTV parameter to a lower value if you find the tables PTI.RAOS_CTVAP_2000 and PTI.RAOS_CTV_2000 are very large.
Feedback
