|
Problem IC85565
|
Status: Closed |
SQL0901N IS RETURNED WHEN MOVING A DATABASE THAT IS CREATED ON OR UPGRADED DIRECTLY TO V10.1 FP1 DOWN TO V10.1 GA |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
If you create or upgrade directly a database to DB2 Version 10.1
Fix Pack 1 without landing on DB2 Version 10.1 GA, you will
receive SQL0901N when moving the database to DB2 Version 10.1
GA.
For example,
connect to sample
SQL0901N The SQL statement failed because of a non-severe
system error.
Subsequent SQL statements can be processed. (Reason "Scan
interface error".)
SQLSTATE=58004
2012-07-25-15.01.34.328999-240 I111805044E1779 LEVEL:
Severe
PID : 20724 TID : 46913063741760 KTID :
20778
PROC : db2sysc
INSTANCE: user NODE : 000 DB : SAMPLE
APPHDL : 0-7 APPID: *LOCAL.user.120725190132
AUTHID : USER
EDUID : 16 EDUNAME: db2agent (V98)
FUNCTION: DB2 UDB, catalog services, sqlrlCatalogScan::insert,
probe:20
DATA #1 : String, 20 bytes
Scan interface error
DATA #2 : String, 22 bytes
Fields not fully setup
DATA #3 : String, 11 bytes
SYSVERSIONS
DATA #4 : String, 11 bytes
INDTABLES01
DATA #5 : Catalog Scan, PD_TYPE_SQLRL_CATALOG_SCAN, 520 bytes
# Key Fields requested: 0
# Key Fields set up: 0
# Fetch Fields requested: 4
# Fetch Fields set up: 3
# LOB Fields: 0
# XML Fields: 0
Scan type: Insert
Lock intent: SQLD_SLI_IS_NS (7)
Lock isolation: SQLZ_CSTAB
Scan flags 1: 0x0000000000000008 SQLD_SCAN1_INDEX_FIXLATCH_OPT
Scan flags 2: 0x00000000
CALLSTCK:
[0] 0x00002AAAACE021AA pdLog + 0x1D6
[1] 0x00002AAAB076C549 _ZN16sqlrlCatalogScan13checkForErrorEv
+ 0x11B
[2] 0x00002AAAB0774003 _ZN16sqlrlCatalogScan6insertEv + 0x42F
[3] 0x00002AAAB086DA2C
_Z20sqlrlGetVersionTimesP8sqlrr_cbbPP17sqlr_versionTimes + 0xCFC
[4] 0x00002AAAAFE2A218 _Z15sqlrr_appl_initP8sqeAgentP5sqlca +
0x2314 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users running DB2 Version 10.1 on Linux, Unix or Windows *
* platform and moving a database that is created on or *
* upgraded directly to v10.1fp1 to v10.1 GA *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update the DB2 Version 10.1 Fix Pack 1. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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 is first fixed in DB2 Version 10.1 Fix Pack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.07.2012
31.10.2012
31.10.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
