|
Problem IC64413
|
Status: Closed |
SQL0083C MEMORY ALLOCATION ERROR DURING A SELECT/DROP COMMAND ISSUED AGAINST A VIEW |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
After migration of database to DB2 Version 9.7, some views may
become inoperable.
Any SELECT or DROP command on the view shows a memory
allocation error (SQL0083C)
A similar thing can happen when a view or a dependent
object (underlying table, variable, user defined function,
etc.) is altered.
The stack trace observed is as follows:
[0] 0x00002ABA260CC31F pdLog + 0x2A9
[1] 0x00002ABA286B441A sqlogmblkEx + 0x8A0
[2] 0x00002ABA2648D47F
_ZN9sqlnq_ftb16populate_from_pdEP8sqlrg_pdP11sqlrrstringP3lociP1
5SQLD_TABLE_DATA
+ 0x2EF7
[3] 0x00002ABA264B68C7
_Z15sqlnq_cat_look2P20sqlnq_multipart_namePP9sqlnq_ftbP3loc21sql
nq_hierarchy_usage
+ 0x68D
[4] 0x00002ABA264B58AD
_Z14sqlnq_cat_lookP20sqlnq_multipart_namePP9sqlnq_ftbP3loc21sqln
q_hierarchy_usage
+ 0x1E9
[5] 0x00002ABA264EF8F8
_Z27sqlnq_handle_qtb_extref_rec20sqlnq_multipart_namePP9sqlnq_qt
biP3loc21sqlnq_hierarchy_usage
+ 0xC4
[6] 0x00002ABA2651D976
_Z26sqlnq_check_referenced_qtbPP9sqlnq_qtbP9sqlnq_qunP3loc21sqln
q_hierarchy_usage
+ 0x138A
[7] 0x00002ABA2651C2BE
_Z27sqlnq_handle_from_table_refP20sqlnq_multipart_namePhiPP9sqln
q_qunP9sqlnq_qtbP3locP9sqlnq_opr21sqlnq_hierarchy_usagePP8stkno
+ 0xF0
[8] 0x00002ABA26532767
_Z9sqlnq_semPP8stknode_i10actiontypePhP3loc + 0x114E3
[9] 0x00002ABA286AE0CF _Z12sqlnp_smactnP8sqlnp_cbi + 0x915 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* After migration of a database to DB2 Version 9.7, some *
* viewsmay become inoperable.Any SELECT or DROP command on the *
* view shows a memoryallocation error (SQL0083C).A similar *
* thing can happen when a view or a dependentobject *
* (underlying table, variable, user defined function,etc.) is *
* altered.The stack trace observed is as follows:[0] *
* 0x00002ABA260CC31F pdLog + 0x2A9[1] 0x00002ABA286B441A *
* sqlogmblkEx + 0x8A0[2] *
* 0x00002ABA2648D47F_ZN9sqlnq_ftb16populate_from_pdEP8sqlrg_pdP1
* 0x2EF7[3] *
* 0x00002ABA264B68C7_Z15sqlnq_cat_look2P20sqlnq_multipart_namePP
* 0x68D[4] *
* 0x00002ABA264B58AD_Z14sqlnq_cat_lookP20sqlnq_multipart_namePP9
* 0x1E9[5] *
* 0x00002ABA264EF8F8_Z27sqlnq_handle_qtb_extref_rec20sqlnq_multi
* 0xC4[6] *
* 0x00002ABA2651D976_Z26sqlnq_check_referenced_qtbPP9sqlnq_qtbP9
* 0x138A[7] *
* 0x00002ABA2651C2BE_Z27sqlnq_handle_from_table_refP20sqlnq_mult
* 0xF0[8] *
* 0x00002ABA26532767_Z9sqlnq_semPP8stknode_i10actiontypePhP3loc
* + 0x114E3[9] 0x00002ABA286AE0CF _Z12sqlnp_smactnP8sqlnp_cbi *
* + 0x915 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.07.200 *
**************************************************************** |
| Local Fix: |
Recreate the view with a different name |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 2 |
| Workaround |
Recreate the problem view using different name |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.11.2009
10.06.2010
10.06.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.7.200,
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
