During the DB2 migration today, from V8.1 to V9.7, due to version differences and the database is a development test database, we plan to forceapplication and make an offline backup
During the DB2 migration today, from V8.1 to V9.7, due to version differences and the library is a development test library, we plan to force the application and make an offline backup
Sql00002c
An unexpected system error occurred.
Description
A system error occurred. Possible causes of this error are:
The command cannot be processed.
User response
To update an instance for configuration or function access, run DB2IUPDT. .
If an error occurs when you try to connect to the database, obtain the trace information (as instructed below) and contact the IBM support organization.
If this problem falls beyond the above suggestions, ensure that the system time and date are correctly set and that the system has sufficient memory and swap/paging space available.
Resubmit the current command.
If the problem persists, stop and restart the Database Manager.
If an error persists, reinstall the Database Manager.
If the trail is active, call "independent tracing facility" at the operating system command prompt ". Please contact your technical service representative and provide the following information:
Required information:
Federated system users: if necessary, locate the problem in the data source that causes the request to fail (refer to the fault diagnosis guide to learn the process to be followed by the data source that identifies the failure ). If the problem occurs to the data source, follow the problem determination process of the data source.
Sqlcode:-1042
Sqlstate: 58004
Run the DB2IUPDT command in the DB2 installation directory/instance;
Run the./db2iupdt db2inst1 command as the root user (db2inst1 indicates the Instance name)
Run./db2iupdt-e as the root user to confirm that the instance is updated.
Then you can start the database at db2start;