linux_db2_hadr常见异常处理

1.  No start database manager command was issued. SQLSTATE=57019

a)   db2trc on -f db2trace.out
b)   db2start
c)   db2trc off



2  ANR0151W Database manager fails to start. SQL1032N

Technote (troubleshooting)

Problem(Abstract)

Due to problems with internal disks, a Tivoli Storage Manager fails to properly start and is aborted. Subsequently, once the disks problems are resolved, the instance fails to start with the below errors.

Symptom

When starting the server in the foreground using the "dsmserv" command, the following messages are reported:


ANR0151W Database manager fails to start. For more information about the failure, issue the db2start command.
ANR0172I rdbdb.c(1722): Error encountered performing action InstanceStop. ANR0162W Supplemental database diagnostic information: -1032:SQLSTATE 57019: The statement was not successful, because of a problem with a resource.
:-1032 (SQL1032N No start database manager command was issued. SQLSTATE=57019 


Cause

Improper shutdown of instance produced orphaned IPC resources

Diagnosing the problem

In the db2diag.log of the instance, the following error is logged :


<timestamp> I779399E357 LEVEL: Severe 
PID : 18375 TID : 140737134171936PROC : db2star2
INSTANCE: tsmserv NODE : 000 
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:580 
MESSAGE : ECF=0x900003DE=-1879047202=ECF_TRCAPI_MUTEX_LOCK_ERROR 
Trace facility mutex unexpected lock error 


Resolving the problem

Complete the following steps to resolve the error:

1. Log on with the Tivoli Storage Manager server instance user ID on Linux.

2. Run the following command to stop the DB2 instance :

db2stop

If the command fails or does not complete, run the following command :

db2_kill


3. Run the following ipcs command to verify whether there are outstanding IPC resources that are associated with the instance :

ipcs -a


4. Run the ipclean command to clean up IPC resources that are associated with the instance :

-bash-3.1$ ipclean
ipclean: Removing DB2 engine and client's IPC resources for tsmserv.


5. Run the following ipcs command to verify whether there are outstanding IPC resources that were not removed by the ipclean command. For example :

ipcs -a


6. If there are outstanding IPC resources associated to the instance, use the following commands to remove them :

To remove a shared memory segment resource, run the following command :
ipcrm -m <shmid>

To remove a semaphore resource, run the following command :
ipcrm -s <semid>

To remove a message queue resource, run the following command :
ipcrm -q <msgid>

7. Once all outstanding IPC resources have been removed, restart the Tivoli Storage Manager server instance.