Skip to main content

Fix ORA-16053

Today I will show you how to handle ORA-16053 error

--Check maximum sequence number of archive log
SQL> select max(sequence#) from v$archived_log;  
 MAX(SEQUENCE#)  
 --------------  
       36  


--Now check parameter
SQL> col destination for a70  
 SQL> select dest_id, status, destination, error from v$archive_dest;  
   DEST_ID STATUS  DESTINATION                              ERROR  
 ---------- --------- ---------------------------------------------------------------------- -----------------------------------------------------------------  
      1 BAD PARAM                                    ORA-16053: DB_UNIQUE_NAME is not in the Data Guard Configuration  
      2 VALID   PROD  
      3 INACTIVE  
      4 INACTIVE  
      5 INACTIVE  
      6 INACTIVE  
      7 INACTIVE  
      8 INACTIVE  
      9 INACTIVE  
     10 INACTIVE  
     11 VALID   /u01/app/oracle/product/11.0.1/db_1/dbs/arch  
 11 rows selected.  

Here is error which means db_unique_name not setted on parameter.


--Also below query provide us bad param if not properly configured.
SQL> select status, dest_id, error from v$archive_dest_status;  
 STATUS    DEST_ID ERROR  
 --------- ---------- -----------------------------------------------------------------  
 BAD PARAM     1 ORA-16053: DB_UNIQUE_NAME is not in the Data Guard Configuration  
 VALID       2  
 INACTIVE      3  
 INACTIVE      4  
 INACTIVE      5  
 INACTIVE      6  
 INACTIVE      7  
 INACTIVE      8  
 INACTIVE      9  
 INACTIVE     10  
 VALID       11  
 11 rows selected.  

SQL> show parameter log_archive_config  
 NAME                 TYPE    VALUE  
 ------------------------------------ ----------- ------------------------------  
 log_archive_config          string   DG_CONFIG=(PROD,STAND)  
 --set log_archive_config  
 SQL> alter system set log_archive_config='DG_CONFIG=(STAND,PROD)';  
 System altered. 


SQL> show parameter log_archive_dest_1  
 NAME                 TYPE    VALUE  
 ------------------------------------ ----------- ------------------------------  
 log_archive_dest_1          string   LOCATION=USE_DB_RECOVERY_FILE_  
                          DEST VALID_FOR=(ALL_LOGFILES,A  
                          LL_ROLES) DB_UNIQUE_NAME=PROD  
 log_archive_dest_10         string  
 SQL> show parameter log_archive_dest_2  
 NAME                 TYPE    VALUE  
 ------------------------------------ ----------- ------------------------------  
 log_archive_dest_2          string   SERVICE=PROD VALID_FOR=(ONLINE  
                          _LOGFILE,PRIMARY_ROLE) async d  
                          b_unique_name=PROD  
 SQL> alter system set log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES_ DB_UNIQUE_NAME=STAND' scope=both;  
 System altered.  



SQL> select status, dest_id, error from v$archive_dest_status where dest_id=2;  
 STATUS         DEST_ID ERROR  
 -------------------- ---------- -----------------------------------------------------------------  
 VALID    

 SQL> select dest_id, status, destination, error from v$archive_dest;  
   DEST_ID STATUS        DESTINATION                              ERROR  
 ---------- -------------------- ---------------------------------------------------------------------- -----------------------------------------------------------------  
      1 VALID        USE_DB_RECOVERY_FILE_DEST  
      2 VALID        PROD  
      3 INACTIVE  
      4 INACTIVE  
      5 INACTIVE  
      6 INACTIVE  
      7 INACTIVE  
      8 INACTIVE  
      9 INACTIVE  
     10 INACTIVE  
     11 VALID        USE_DB_RECOVERY_FILE_DEST  
 11 rows selected.  


--Now check again and you will see logs start to receive and applying.

 SQL> select max(sequence#) from v$archived_log;  
 MAX(SEQUENCE#)  
 --------------  
       45  

Comments

Popular posts from this blog

Rman encryption and other techniques

Today I will demonstrate Recovery Manager features, especially encryption and some other techniques. First of all let me note about RMAN backup encryption. Staring from Oracle 10g RMAN now creates encrypted backups that cannot be restored by unauthorized people. There are 3 modes of backup encryption: * Transparent encryption * Password encryption * Dual-mode encryption using either transparent or password encryption All RMAN backups are not encrypted but you can encrypt any RMAN backup in the form of a backup set. In this tutorial I will show you how to configure Password encryption. Let`s finish talking and start to demonstrate. check parameters with "SHOW ALL" command, by default encryption is OFF RMAN> show all; RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTR...

ORA-03206: maximum file size of (5242880) blocks in AUTOEXTEND clause is out of range

Today when I want to change max size of datafile I got strange error. ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/MYDB/users01.dbf' AUTOEXTEND ON NEXT 1280K MAXSIZE 32GB ORA-03206: maximum file size of (5242880) blocks in AUTOEXTEND clause is out of range Here is reason: The maximum file size for an autoextendable file has exceeded the maximum number of blocks allowed. After research internet I found that instead of using 32GB we can use 32767M. (same values but in MB). Or you may use 31GB too. ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/MYDB/users01.dbf' AUTOEXTEND ON NEXT 1280K MAXSIZE 32767M;

Fix ORA-01139: RESETLOGS option only valid after an incomplete database recovery

While shutting down my TEST database process was hanged. Then I had to use shutdown abort. But when I wanted to start database it did not open. SQL> select name from v$database; NAME --------- TEST SQL> shut abort; ORACLE instance shut down. SQL> startup mount ORACLE instance started. Total System Global Area 6597406720 bytes Fixed Size 2265664 bytes Variable Size 3204451776 bytes Database Buffers 3372220416 bytes Redo Buffers 18468864 bytes Database mounted. SQL> alter database open; alter database open * ERROR at line 1: ORA-03113: end-of-file on communication channel Process ID: 6552 Session ID: 191 Serial number: 3  What`s wrong?  SQL> alter database open resetlogs; ERROR:    ORA-03114: not connected to ORACLE    SQL> exit Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Pr...