DB2 - Problem description
| Problem IC97163 | Status: Closed |
SQL1499W WHEN UPGRADING DATABASE | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
After upgrading database to v10.1, "db2 UPGRADE DATABASE" is
returning SQL1499W "Database upgrade was successful; however,
additional user action may be required. See the administration
notification log for more details."
In the db2diag.log you will see messages like so:
2013-10-06-01.57.32.491410-300 E9220A533 LEVEL:
Warning
PID : 45678762 TID : 1 PROC : db2bp
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPID : *LOCAL.db2inst1.131006065730
HOSTNAME: wdc-aixbetadb-11
EDUID : 1
FUNCTION: DB2 UDB, base sys utilities, sqlePostUpgDpfTask,
probe:977
MESSAGE : ADM7535W The UPGRADE DATABASE command failed to
refresh the table
space attributes in the catalog table. However the
database was
upgraded successfully.
2013-10-06-01.57.32.492605-300 I9754A1017 LEVEL:
Warning
PID : 45678762 TID : 1 PROC : db2bp
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPID : *LOCAL.db2inst1.131006065730
HOSTNAME: wdc-aixbetadb-11
EDUID : 1
FUNCTION: DB2 UDB, base sys utilities, sqlePostUpgDpfTask,
probe:985
MESSAGE : ZRC=0xFFFFFF98=-104
SQL0104N An unexpected token "" was found following
"". Expected
tokens may include: "".
DATA #1 : String, 35 bytes
admin_refresh_tbsp_attribs() failed
DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCAM sqlcabc: 136 sqlcode: -104 sqlerrml: 44
sqlerrmc: ALTER TABLESPACE BEGIN-OF-STATEMENT <values>
sqlerrp : SQLNP01F
sqlerrd : (1) 0xFFFFFFFF (2) 0x00000000 (3)
0x00000001
(4) 0x4553988B (5) 0xFFFFFD3F (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 42601
SYSIBMINTERNAL.ADMIN_REFRESH_TBSP_ATTRIBS is fetching tablespace
names from SYSIBM.SYSTABLESPACES and using them to dynamically
construct ALTER TABLESPACE statements without enclosing the
tablespace identifiers in delimiters. This results in the
SQL1499W message with tablespace names that contain hyphens. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v10.1 fix pack 4. * **************************************************************** | |
| Local Fix: | |
N/A | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
| Solution | |
First fixed in DB2 v10.1 fix pack 4. | |
| Workaround | |
N/A | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.10.2013 26.06.2014 26.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 |
|