SQL1034C The database is damaged - DB2

-
DB2 v9.1
AIX 5.3

This post demonstrate step by step approach to restart a database which returns SQL1034C in DB2.

Error →

bash-4.2$ db2 connect to TESTDB
SQL1034C The database is damaged. All applications processing the database
have been stopped. SQLSTATE=58031

1. DB2 stop with force application all.

bash-4.2$ db2 force application all
DB20000I The FORCE APPLICATION command completed successfully.
DB21024I This command is asynchronous and may not be effective immediately.

bash-4.2$ db2 list active databases
SQL1611W No data was returned by Database System Monitor.

bash-4.2$ db2stop
02/24/2015 01:38:16 0 0 SQL1025N The database manager was not stopped because databases are still active.
SQL1025N The database manager was not stopped because databases are still active.

2. DB2 quiesce instance force connections

bash-4.2$ db2 quiesce instance TINST1 immediate force connections
SQL0913N Unsuccessful execution caused by deadlock or timeout. Reason code
"80". SQLSTATE=57033

While the command was running errors were reported in diag log and in .nfy log there were below errors,

ADM7519W DB2 could not allocate an agent. The SQLCODE is "-3807".

3. DB2stop force

bash-4.2$ db2stop force
02/24/2015 02:12:22 0 0 SQL1042C An unexpected system error occurred.
SQL1025N The database manager was not stopped because databases are still active.

4. DB2 kill followed by admin mode start and database restart.

bash-4.2$ db2_kill

followed by ipcs and ipcrm to remove any remaing db2 ipcs processes.

bash-4.2$ db2start admin mode
02/24/2015 02:14:42 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
bash-4.2$
bash-4.2$ db2 restart database TESTDB
DB20000I The RESTART DATABASE command completed successfully.
bash-4.2$
bash-4.2$
bash-4.2$ db2 connect to TESTDB
Database Connection Information
Database server = DB2/AIX64 9.1.9
SQL authorization ID = TINST1
Local database alias = TESTDB
bash-4.2$

After above steps db instance was stopped/ started normally (using db2stop and db2start) and the db was available for applications.

Comments

Post a Comment

Popular posts from this blog

ORA-16433: The database or pluggable database must be opened in read/write

-
Image
ORA-16433 is an error returned when a database cannot be opened. This can be a result of multiple conditions including, The inconsistency of the database Physical corruption Loss of dependent files or access issues etc.. More often than not the solution is to recover from available backups, but there can be situations where backups are not available, specially on UAT or Test setups. Although not the ideal scenario, in this type of situation you might want to open the databases even with inconsistency.  In Comes --> _ALLOW_RESETLOGS_CORRUPTION First, if you are in a position to use _ALLOW_RESETLOGS_CORRUPTION=TRUE, that means it has to be a critical moment, and when you come across more ora- errors while you are trying to reopen the databsae, that can be annoying. Note - _ALLOW_RESETLOGS_CORRUPTION=TRUE must only be used after Oracle support confirmation as a last resort. Also make sure to take cold backup before proceeding. Basic steps to be followed to resolve ORA 16433 after
Read more

Oracle Multitenant - Create new service for PDB using DBMS_SERVICE

-
Image
When an Oracle PDB is created it starts up a default service with the PDB name. For direct connections to    PDB this service can be used. But there are situations where new service name is required in PDB level, common example is after a PDB restoration/clone, in order to enable application connections without changes in connection string. Setting service_names parameter in PDB level is not possible hence it is not an option in multitenant setup. How to create a new PDB service on Oracle 12C Check the current services, here only the default service is running, SQL> show pdbs; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 3 NFACTORPDB READ WRITE NO SQL> select service_id, name, pdb from dba_Services; SERVICE_ID NAME PDB ---------- ---------------------------------------- ---------- 7 nfactorpdb NFACTORPDB SQL> Create
Read more

Wait for unread message on broadcast channel - Blocking Sessions

-
Image
What is Wait for unread message on broadcast channel wait event? Wait for unread message on broadcast channel is a wait event where source destination communication is involved and the database is waiting for a reply from remote party. Mostly this wait is seen related to data pump export (expdp) or import (impdp) operations. Although categorized in idle wait class "Wait for unread message on broadcast channel" can become the blocking session for some other sessions. Common causes for stuck sessions waiting on this wait event includes, Broken databases links, where remote database is not responding. Abnormally killed remote processes causing the sessions to wait. When a session is waiting on "Wait for unread message on broadcast channel" it can become a blocking session for dependent sessions. Most probably these sessions will be waiting on "library cache pin" or related concurrency wait events. The blocking_session column of (g)v$session view
Read more