Sql00002c error occurs when DB2 data is restarted.

During the DB2 migration today, from V8.1 to V9.7, we plan to force application and make an offline backup because of version differences and the library is a development Test Library, when you use db2 force applications all in the source database and there is always a new connection, you decide to restart the database and disable database connection by setting db2set DB2COMM = tcpip to null. Use the following command to stop a database: db2 force application all; \ db2 force application all; \ db2 force application all; \ db2 force application all; \ db2 force application all; \ db2 force application all; \ db2stop: When the database is re-opened, the following error message is returned: 12/03/2013 11:05:54 0 SQL1042N An unexpected system error occurred. SQL1032N No start database manager command was issued. SQLSTAT = 57019
It can be seen that SQL1042N is an important information, and there is a lot of information in db2diag. log (the company's database is on the Intranet and cannot be developed );
According to the error code, google's SQL1042N is as follows: sql1_2c

An unexpected system error occurred.

Description

A system error occurred. Possible causes of this error are:

• The database manager is not correctly installed or the environment is not correctly set.
• On UNIX-based systems, you may need to run db2iupdt to update the DB2 instance, this gives you access to new system configurations or features associated with installing or removing certain product options, modifying packages, or modifying levels.
• You may receive this message because the correct DB2 management server password is not used.

  The command cannot be processed.

  User response
  • To update an instance for configuration or function access, run DB2IUPDT <InstName>.
  • 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:

    • Problem description
    • SQLCODE or message number
    • If possible, SQLCA content should also be provided
    • If possible, trace files should also be provided.

      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 by the root user (db2inst1 is the instance name) and run the command by the root user./db2iupdt-e to confirm that the instance has been updated.
      Then you can start the database at db2start;
      
      
      
      
      

      Bytes --------------------------------------------------------------------------------------------

      Copyright. For reprinted copies, please indicate the author and original article links. Otherwise, you will be held legally responsible!

      QQ: 584307876

      Author: Seven

      Link: http://blog.csdn.net/sunjiapeng/article/details/17100419

      Email: seven_ginna@foxmail.com