DB2 - Problembeschreibung
Problem IT10455 | Status: Geschlossen |
DB2LOOK WHEN USED WITH "-l" OPTION FAILS WITH ERROR SQL1635N or SQL1092N | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
DB2LOOK with -l option fails with the following error message SQL1635N The snapshot operation failed because the size of the snapshot is"2508486824" bytes, which exceeds the maximum allowable size of "2147483135" db2look invokes API db2GetSnapshotSize() to get estimated size of buffer to hold snapshot information. The size is limited to 2G and it is a current limitation. Hence if the estimated buffer size exceeds 2G, db2look will run into error SQL1635N. db2 trace will have the following function entry with rc = -1635 1048103 create_tablespace_ddl entry ... 1049426 | sqm___sqlmonsz entry ... 1050655 | | sqm___sqlm_send_est_buf_size_db2ra entry 1050715 | | | | | | sqlerInvokeKnownProcedure entry 1059081 | | | | | | sqlerInvokeKnownProcedure exit [rc = 0xFFFFF99D = -1635] ... 1059114 | | sqm___sqlm_send_est_buf_size_db2ra exit [rc = 0xFFFFFFFF = -1] 1059115 | sqm___sqlmonsz error [probe 600] create_tablespace_ddl is invoked by db2look which is making a call to db2GetSnapshotSize() (function sqlmonsz) to get estimated buffer size Another symptom of this APAR is, db2look when used with "-l" option may fail with SQL1092N even though the user has DBADM authority. This is due to the fact that db2look invokes API db2GetSnapshotSize internally and this needs one of the following authority.. * sysadm * sysctrl * sysmaint * sysmon | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * db2forluw * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to V10.5 FP7 * **************************************************************** | |
Local-Fix: | |
Lösung | |
v105 fp7 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 31.07.2015 21.01.2016 21.01.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.7 |