Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC96821 Status: Closed

QUERIES USING ORDER BY CLAUSE MAY FAIL WITH SQL1585N ON THE HADR STANDBY
SERVER(READS ON STANDBY ENABLED)

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Following error will be reported on the standby server even 
though we have the system temporary tablespace available: 
SQL1585N  A system temporary table space with sufficient page 
size does not exist.  SQLSTATE=54048 
 
A trace will have the following information: 
 
22605    data DB2 UDB SW- common services sqlnn_erds fnc 
(3.3.49.21.0.0) 
    pid 7077896 tid 32321 cpid 17104918 node 0 sec 0 nsec 
54378130 probe 0 
    bytes 72 
    CompID= 53, FcnId= 602, sqlCode= -1585, loc= 1000, 
numTokens= 0
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4.                      * 
****************************************************************
Local Fix:
Deactivate and activate the standby database
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 Fix Pack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.10.2013
02.06.2014
02.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList