|
Problem IC96285
|
Status: Closed |
DB2ADVIS MAY FAIL WITH SQL0304N WHEN PROCESSING LARGE INPUT FILES |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Depending on the size and content of the input file, db2advis
may fail with error SQL0304N. Symptoms could look like the
following in the output file: i
+1 execution started at timestamp
2013-06-26-11.38.36.254710
+2 found [4945] SQL statements from the input file
+3 Recommending indexes...
+4
+5 0 solutions were evaluated by the advisor
+6
+7 exiting with error code [-304]
and in db2diag.log:
2013-06-26-17.07.01.758200+060 I165624A714 LEVEL: Error
PID : 54657106 TID : 1 PROC :
db2advis
INSTANCE: db2inst1 NODE : 000
APPID : *N0.db2inst1.130906150326
EDUID : 1
DATA #1 : String, 51 bytes
*** Error at line 1372, in file db2advindex.SQC
DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -304 sqlerrml: 0
sqlerrmc:
sqlerrp : SQLADRBO
sqlerrd : (1) 0x882A000C (2) 0x0000000C (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 22003 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all using db2advis *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to version 10.1 Fixpack 3 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in version 10.1 Fixpack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.09.2013
27.09.2013
27.09.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
