|
Problem IC69792
|
Status: Closed |
Resolving routine may return SQL0901N "Invalid collation ID" if corruption exists in routine packed descriptor |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
This symptom can be seen if the database is created with
username of which length is greater than 8 characters such as
ADMINISTRATOR. When trying to resolve a routine, we need to
check for the routine's collation id. If there exists corruption
in the routine definer inside the routine packed description of
SYSCAT.COLLATIONNAME, then SQL0901N may be returned and the
below entry output to the db2diag.log.
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
probe:300
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 20
sqlerrmc: Invalid collation ID
sqlerrp : SQLNQB62
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0xFFFFFF9C (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
To see if such corruption exists in your database, use the
db2cat utility under the sqllib/bin directory.
> db2cat -d <dbname> -s SYSCAT -n COLLATIONNAME -p routine -o
rtn.fmt
> find /i "definer" rtn.fmt
---------- RTN.FMT
Definer length : 13
Definer : SYSIBM RATOR
Definer type : S
If you see the definer length greater than 8 and see text
following "SYSIBM ", then you have corruption in the routine
packed descriptor. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* Using system defined modules result in SQL0551N like *
* "SYSIBMRATOR" does not have the required authorization *
* orprivilege. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.5 FP7 *
****************************************************************
Close |
| Local Fix: |
None, contact IBM DB2 Services to get the corruption patched. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 Version 9.5 Fix Pack 7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.07.2010
25.04.2012
25.04.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP7
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.7
|
 |
| 9.5.0.7
|
|
