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

-

ORA-16433 is an error returned when a database cannot be opened. This can be a result of multiple conditions including,

  1. The inconsistency of the database
  2. Physical corruption
  3. 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. 

ora 16433 The database or pluggable database must be opened in read/write

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 the loss of Online redo logs using _ALLOW_RESETLOGS_CORRUPTION are listed below (if using PDBs refer Note below), 

1. Create pfile from spfile, If RAC stop all nodes except one.

2. Add or change parameters as below,

Set UNDO_MANAGEMENT=MANUAL and remove UNDO_TABLESPACE and UNDO_RETENTION.

Set CLUSTER_DATABASE=FALSE, JOB_QUEUE_PROCESSES=0.

Include  _ALLOW_RESETLOGS_CORRUPTION=TRUE

3. Recreate the controlfile with resetlogs option.

4. If any of the datafiles are in offline status, try to alter the datafile online as below,

 select file#, name, status from v$datafile where status not in ('SYSTEM', 'ONLINE');  
 alter database datafile <file#> online;

If the status changes to RECOVER perform an incomplete recovery as below, (This is to update the status, not actual recovery)

 recover database using backup controlfile until cancel; -- type cancel in prompt

5. Open database with reset logs,

 alter database open resetlogs;

Additional point to consider is that, a database opened with _ALLOW_RESETLOGS_CORRUPTION=TRUE Is not supported by Oracle, hence make sure to take logical backup (i.e export/import) and recreate the database.

ORA-16433 with PDB setup

In case you are running Oracle 12c and above with PDBs enabled make sure to include below event parameter to pfile along with others mentioned in step 2 above. event="21307096 trace name context forever, level 1"

Comments

Post a Comment

Popular posts from this blog

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> ...
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