Extract job ends with return code 08 with -802 SQL errors
Article ID: 129144
Updated On:
Products
Database Analyzer for DB2 for z/OS
Fast Unload for DB2 for z/OS
Fast Check for DB2 for z/OS
Fast Index for DB2 for z/OS
Rapid Reorg for DB2 for z/OS
Issue/Introduction
A CA Database Analyzer extract is failing with a return code 8, with -802 SQL errors reported in Action Processing. What is causing these errors and how can they be resolved?
Environment
Release:
Component: PDA
Component: PDA
Resolution
The -802 SQL errors could indicate invalid RTS statistics or orphaned RTS rows. In this situation we point users to HIGHLVL.CDBASAMP(RTOSESQL). This member contains instructions on how to understand and solve -802 SQL errors. Specifically refer to section 'E. If you are getting a SQLCODE -802'.
Follow the recommended steps that apply to this scenario, 'divide by zero error, SQL state (22012).
You can use the SQL provided in CDBASAMP(RTSCLNUP) to clean up the TOTALROWS -1 values. In RTSCLNUP refer to '5) Clean up negative TOTALROWS and TOTALENTRIES IBM APAR PK53341'.
This SQL can be used to clean up the -1 entries in SYSTABLESPACESTATS which is the cause of the -802 errors for this database.
Follow the recommended steps that apply to this scenario, 'divide by zero error, SQL state (22012).
You can use the SQL provided in CDBASAMP(RTSCLNUP) to clean up the TOTALROWS -1 values. In RTSCLNUP refer to '5) Clean up negative TOTALROWS and TOTALENTRIES IBM APAR PK53341'.
This SQL can be used to clean up the -1 entries in SYSTABLESPACESTATS which is the cause of the -802 errors for this database.
Feedback
Yes
No
Powered by
