|
Problem IC89505
|
Status: Closed |
AUTOREORG USES INDEX REBUILD OPTION AGAINST PURESCALE SERVER RESULTING IN SQL1419 |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When auto reorg is enabled and the auto reorg policy has :
indexReorgMode="Online"
then when formula F5 and F6 of reorgchk output is exceed an
online index rebuild will be scheduled.
This is not supported in a Purescale environment and will hence
raise error SQL1419 in the db2diag.log
e.g.
FUNCTION: DB2 UDB, Automatic Table Maintenance,
db2AutoReorgExec,
probe:190
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1419 sqlerrml: 1
sqlerrmc: 7
sqlerrp : db2Reorg
sqlerrd : (1) 0x801A006D (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0xFFFFFEED (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 56038
The auto reorg option should detect that it is running against a
Purescale environment and not submit the online rebuild option. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade the database server to V10.1 Fix Pack 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 |
This problem was first fixed in DB2 V10.1 Fix Pack 3 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC96603
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.01.2013
21.10.2013
21.10.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
|
|
