|
Problem IC68248
|
Status: Closed |
UPGRADING A NON-ROOT COPY FROM DB2 V95 TO V97 FIX PACK 2 FAILS |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When you attempt to upgrade a non-root copy of DB2 V95 to V97
Fix Pack 2 using the "db2_install -m" command the DB2 installer
is failing with the following error:
./db2_install -m -p ese
DBI1160I Non-root install is being performed.
DB2 installation is being initialized.
Total number of tasks to be performed: 10
Total estimated time for all tasks to be performed: 614
Task #1 start
Description: Preparing the system
Estimated time 120 second(s)
DBI1205E One or more local databases cannot be upgraded to the
version
from which you are running this command. Check the log
file
/tmp/db2t02.tmp for the list of errors.
Explanation:
The following list provides the reasons why a database cannot be
upgraded and the corrective action to take:
* Database is in Backup pending state. Perform backup of the
database.
* Database is in Roll-forward pending state. Perform a
roll-forward
database to end of logs and stop.
* Database is in Restore pending state. Perform restore of the
database.
* Database is inconsistent. Restart database to return it to a
consistent state.
* Database has one or more table space not in normal state.
Perform a
roll-forward database.
* Database contains database objects that have a schema name of
SYSCAT,
SYSFUN, SYSIBM, SYSPUBLIC, or SYSSTAT. Drop the object and
re-create
the object with a correct schema name (qualifier). If the
object is a
table you should first export its data, drop the table,
re-create the
table with a correct schema name, and then import or load the
data to
the new table.
* Database contains database objects that have a dependency on
the
SYSFUN.DIFFERENCES function. Possible violated objects and
the
associated action to correct the violation are:
* constraint - alter table to drop the constraint
* function - drop the function
* trigger - drop the trigger
* view - drop the view
* Database contains user-defined data types that are reserved
in the
new version. Rename the data types.
* Database contains orphan rows in system catalog tables.
Contact IBM
technical service representative.
* Cataloged database does not exist. Create cataloged database.
* SYSCATSPACE does not have at least 50 free pages if
SYSCATSPACE is a
DMS table space and AUTORESIZE is not enabled. Increase
available
space for SYSCATSPACE table space.
* Database does not allow successful connection as an HADR
primary
database. Stop HADR on primary database.
* A database has HADR standby role. Stop HADR on the standby
database
and drop the standby database. Upgrade the HADR primary
database.
Reinitialize the standby database from the copy of upgraded
primary
database via restore or db2inidb.
User response:
Determine the reason why the database cannot be upgraded and
take the
corresponding action specified in the explanation. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* When you attempt to upgrade a non-root copy of DB2 V95 to *
* V97 Fix Pack 2 using the "db2_install -m" command the DB2 *
* installer is failing with the following error: *
* *
* *
* *
* ./db2_install -m -p ese *
* *
* *
* *
* DBI1160I Non-root install is being performed. *
* *
* *
* *
* *
* *
* DB2 installation is being initialized. *
* *
* *
* *
* Total number of tasks to be performed: 10 *
* *
* Total estimated time for all tasks to be performed: 614 *
* *
* *
* *
* Task #1 start *
* *
* Description: Preparing the system *
* *
* Estimated time 120 second(s) *
* *
* DBI1205E One or more local databases cannot be upgraded to *
* the *
* version *
* *
* from which you are running this command. Check the log *
* *
* file *
* *
* /tmp/db2t02.tmp for the list of errors. *
* *
* *
* *
* Explanation: *
* *
* *
* *
* The following list provides the reasons why a database *
* cannot be *
* upgraded and the corrective action to take: *
* *
* *
* *
* * Database is in Backup pending state. Perform backup of *
* the *
* database. *
* *
* * Database is in Roll-forward pending state. Perform a *
* *
* roll-forward *
* *
* database to end of logs and stop. *
* *
* * Database is in Restore pending state. Perform restore of *
* the *
* database. *
* *
* * Database is inconsistent. Restart database to return it *
* to a *
* consistent state. *
* *
* * Database has one or more table space not in normal state. *
* *
* Perform a *
* *
* roll-forward database. *
* *
* * Database contains database objects that have a schema *
* name of *
* SYSCAT, *
* *
* SYSFUN, SYSIBM, SYSPUBLIC, or SYSSTAT. Drop the object and *
* *
* re-create *
* *
* the object with a correct schema name (qualifier). If the *
* *
* object is a *
* *
* table you should first export its data, drop the table, *
* *
* re-create the *
* *
* table with a correct schema name, and then import or load *
* the *
* data to *
* *
* the new table. *
* *
* * Database contains database objects that have a dependency *
* on *
* the *
* *
* SYSFUN.DIFFERENCES function. Possible violated objects and *
* *
* the *
* *
* associated action to correct the violation are: *
* *
* * constraint - alter table to drop the constraint *
* *
* * function - drop the function *
* *
* * trigger - drop the trigger *
* *
* * view - drop the view *
* *
* *
* *
* * Database contains user-defined data types that are *
* reserved *
* in the *
* *
* new version. Rename the data types. *
* *
* * Database contains orphan rows in system catalog tables. *
* *
* Contact IBM *
* *
* technical service representative. *
* *
* * Cataloged database does not exist. Create cataloged *
* database. *
* * SYSCATSPACE does not have at least 50 free pages if *
* *
* SYSCATSPACE is a *
* *
* DMS table space and AUTORESIZE is not enabled. Increase *
* *
* available *
* *
* space for SYSCATSPACE table space. *
* *
* * Database does not allow successful connection as an HADR *
* *
* primary *
* *
* database. Stop HADR on primary database. *
* *
* * A database has HADR standby role. Stop HADR on the *
* standby *
* database *
* *
* and drop the standby database. Upgrade the HADR primary *
* *
* database. *
* *
* Reinitialize the standby database from the copy of *
* upgraded *
* primary *
* *
* database via restore or db2inidb. *
* *
* *
* *
* *
* *
* User response: *
* *
* *
* *
* Determine the reason why the database cannot be upgraded and *
* *
* take the *
* *
* corresponding action specified in the explanation. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.7 Fix Pack 2 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC68253
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.04.2010
13.05.2010
13.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
