View Full Version : DB XREF Files Corrupt after V5R1 stored procedure fails
12-11-2001, 10:47 AM
Hello Brian, We had a similar problem during our V4R5 to V5R1 Upgrade. Running the RCLSTG SELECT(*DBXREF) corrected our problem. We are planning to do a RCLSTG prior to any future upgrades if we have the time to hopefully be proactive. What does IBM Support have to say about this? Thanks, Keith
12-11-2001, 10:53 AM
We are getting invalid data in cross reference files since V5R1 upgrade giving the following.. We ran the RCLSTG on the XREF files but still have the problem. One of the things that this is affecting is a Stored Procedure job prior to V5R1 we did not have to hard code LIB names and now the only way this will work is if we hard code the LIB. This procedure works fine on other V5R1 systems ???? the following error messages back to the caller ... [IBM][Client Access Express ODBC Driver (32-bit)][DB2/400 SQL]SQL0204 - SDC_SHPINQI in *N type *N not found. SQLState = S0002 NativeError = -204 [IBM][Client Access Express ODBC Driver (32-bit)]ExtendedDynamic support disabled. SQLState = 01000 Additional Message Information Message ID . . . . . . : CPF32A2 Severity . . . . . . . : 60 Message type . . . . . : Information Date sent . . . . . . : 12/10/01 Time sent . . . . . . : 03:58:12 Message . . . . : Unexpected data found in system cross reference files. Cause . . . . . : The system cross reference files are not up to date. The unexpected data was encountered when updating the system cross reference files running operation type 3 on file testSDL1 in library TEST. The error code is 2. When the system cross reference files are not up to date, the system may not allow data dictionary definitions to be changed or deleted, the system may not allow data dictionaries to be deleted, SQL catalogs may not be up to date, and the system may not allow constraints to be added or removed from files. Recovery . . . : Request a reclaim storage (RCLSTG command specifying SELECT(*ALL) or SELECT(*DBXREF)) to update the system cross reference files Technical description . . . . . . . . : The operation types and their More.. Any one have this problem after V5R1 ??? Thanks Brian
12-11-2001, 10:53 AM
Hi Keith Thanks for the responce... The call is now with IBM Rochester I was hoping someone else had already been through this. Also we cannot to a SAVSYS since the upgrade As far as stored procedures go we had other problems since the upgrade but they were corrected with the lastest V4R5 C/A service pack 66513 I just have this one outstanding stored procedure problem.. Thanks Brian
Powered by vBulletin® Version 4.1.5 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.