If you get an SQLCODE -497 while trying to run a QMF PROC, read this:
SQLCODE -497 means "THE MAXIMUM LIMIT OF INTERNAL IDENTIFIERS HAS BEEN
EXCEEDED FOR DATABASE database"
You need to run the MODIFY utility with RECOVERY option to fix this issue.
The MODIFY online utility with the RECOVERY option deletes records from the SYSIBM.SYSCOPY catalog table, related log records from the SYSIBM.SYSLGRNX directory table, and entries from the DBD. You can remove records that were written before a specific date or you can remove records of a specific age. You can delete records for an entire table space, partition, or data set.
Sample SYSIN for MODIFY:
MODIFY RECOVERY TABLESPACE database.tablespace DELETE AGE(365)
Showing posts with label QMF. Show all posts
Showing posts with label QMF. Show all posts
Friday, January 9, 2009
Monday, November 3, 2008
DB2 SQLCODE=-950
We use BCV split (Business Continuance Volume) technology to clone our Peoplesoft DB2 production subsystem to DB2 test subsystem. After we cloned one of our subsystems, we noticed that our programmers were not able to access QMF. They started getting the error message:
"DSQ16950 The location name is not known to the local DB2 subsystem.".
This was the error message from QMF. The actual error message issued by DB2 was "SQLCODE -950" which means "THE LOCATION NAME SPECIFIED IN THE CONNECT STATEMENT IS INVALID OR NOT LISTED IN THE COMMUNICATIONS DATABASE".
When you get this message check SYSIBM.LOCATIONS to see if a row is there for the DB2 subsystem it is complaining about. If there is one and the values are correct, check the application PLAN. In our case we checked QMF PLAN.
Check if you have the right value for CURRENTSERVER in your BIND PLAN. If you don't have the correct value, rebind the plan with correct value for this parameter. If you are on a local server (on a local LPAR), just remove this parameter. Removing this parameter and rebinding the plan fixed our issue with QMF.
"DSQ16950 The location name is not known to the local DB2 subsystem.".
This was the error message from QMF. The actual error message issued by DB2 was "SQLCODE -950" which means "THE LOCATION NAME SPECIFIED IN THE CONNECT STATEMENT IS INVALID OR NOT LISTED IN THE COMMUNICATIONS DATABASE".
When you get this message check SYSIBM.LOCATIONS to see if a row is there for the DB2 subsystem it is complaining about. If there is one and the values are correct, check the application PLAN. In our case we checked QMF PLAN.
Check if you have the right value for CURRENTSERVER in your BIND PLAN. If you don't have the correct value, rebind the plan with correct value for this parameter. If you are on a local server (on a local LPAR), just remove this parameter. Removing this parameter and rebinding the plan fixed our issue with QMF.
Wednesday, October 22, 2008
QMF Tips
If you want to delete/drop a saved data table in QMF, read on.
After doing a "LI TABLES" to list all the saved data tables, if you want to drop one of the tables, use command "ERASE" (DROP, DELETE etc are not for this purpose).
Subscribe to:
Posts (Atom)