Friday, December 18, 2015

Fix RMAN-03002

If you face ORA-19804 error just increase db_recovery_file_dest_size value

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 12/18/2015 15:10:43

RMAN-03009: failure of backup command on ORA_DISK_1 channel at 12/18/2015 15:10:40
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 214748364800 limit

SQL> set linesize 120  
 SQL> col name for a40  
 \SQL> col type for a40  
 SQL> show parameter db_re  
 NAME                       TYPE         VALUE  
 -------------------------  ---------    ----------------------------  
 db_recovery_file_dest      string       /u01/app/oracle/flash_recovery_area  
 db_recovery_file_dest_size big integer  200G  
 db_recycle_cache_size      big integer  0  


 SQL> alter system set db_recovery_file_dest_size=600G scope=both;  
 System altered.  
That`s all.

Friday, November 27, 2015

Fix ORA-16072

Today after restore and recovery prod database on test environment I faced with strange error:

ORA-16072: a minimum of one standby database destination is required.

My database environment :

 OS: OEL 6.5  
 DB: 11.2.0.4  

After recovery database stays on MOUNT mode and could not open it.

RMAN-00571: ===========================================================  
 RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============  
 RMAN-00571: ===========================================================  
 RMAN-03002: failure of recover command at 11/27/2015 12:55:01  
 RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 9573 and starting SCN of 556583605 

RMAN> alter database open resetlogs;  
 RMAN-00571: ===========================================================  
 RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============  
 RMAN-00571: ===========================================================  
 RMAN-03002: failure of alter db command at 11/27/2015 12:56:08  
 ORA-03113: end-of-file on communication channel  
 Process ID: 12064  
 Session ID: 958 Serial number: 11  
 RMAN-00571: ===========================================================  
 RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============  
 RMAN-00571: ===========================================================  
 ORA-03114: not connected to ORACLE  
 RMAN-00571: ===========================================================  
 RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============  
 RMAN-00571: ===========================================================  
 RMAN-03002: failure of alter db command at 11/27/2015 12:56:08  
 ORA-03113: end-of-file on communication channel  
 Process ID: 12064  
 Session ID: 958 Serial number: 11  
 [oracle@TESTDB dbs]$  


Checking alertlog:
LGWR: STARTING ARCH PROCESSES  
 Fri Nov 27 14:44:35 2015  
 ARC0 started with pid=22, OS id=23775   
 ARC0: Archival started  
 LGWR: STARTING ARCH PROCESSES COMPLETE  
 ARC0: STARTING ARCH PROCESSES  
 LGWR: Primary database is in MAXIMUM AVAILABILITY mode  
 LGWR: Destination LOG_ARCHIVE_DEST_1 is not serviced by LGWR  
 LGWR: Minimum of 1 LGWR standby database required  
 Errors in file /u01/oracle/diag/rdbms/prod/XXXX/trace/XXXX_lgwr_23742.trc:  
 ORA-16072: a minimum of one standby database destination is required 


I turned off archivelog mode on my test database and tried to open. It opened successfully. But I need my test database have to be on archivelog mode.

To handle it I checked and corrected some parameters:

SQL> select open_mode, log_mode from v$database;  
 OPEN_MODE   LOG_MODE  
 -------------------- ------------  
 READ WRITE   NOARCHIVELOG  



SQL> set linesize 100  
 SQL> show parameter fal_  
 NAME     TYPE     VALUE  
 ------------------------------------ -------------------------------- ------------------------------  
 fal_client    string     XXXX  
 fal_server    string     XXXX_SB  
 SQL> alter system set fal_client='' scope=spfile;  
 System altered.  
 SQL> alter system set fal_server='' scope=spfile;  
 System altered.  
 SQL> alter system set log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST';  
 System altered  
 SQL> select open_mode, DATABASE_ROLE, guard_status, SWITCHOVER_STATUS from v$database;  
 OPEN_MODE   DATABASE_ROLE  GUARD_S SWITCHOVER_STATUS  
 -------------------- ---------------- ------- --------------------  
 MOUNTED    PRIMARY    NONE  NOT ALLOWED  
 Database altered.  


Restart database

 SQL> shut immediate  
 ORA-01109: database not open  
 Database dismounted.  
 ORACLE instance shut down.  
 SQL> startup mount  
 ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance  
 ORACLE instance started.  
 Total System Global Area 8584982528 bytes  
 Fixed Size   2260128 bytes  
 Variable Size  6341788512 bytes  
 Database Buffers 2214592512 bytes  
 Redo Buffers   26341376 bytes  
 Database mounted.  
 SQL> alter database open;  
 Database altered.  

Perfect

SQL> select name, open_mode from v$database;  
 NAME OPEN_MODE  
 ---------  ------------------------  
 XXXX  READ WRITE  
 SQL>  



But in alertlog still error

 Errors in file /u01/oracle/diag/rdbms/prod/XXXX/trace/XXXX_arct_24125.trc:  
 ORA-00313: open failed for members of log group 7 of thread 0  
 ORA-00312: online log 7 thread 0: '/u01/oracle/fast_recovery_area/XXXX/onlinelog/o1_mf_7_c4vcl2pw_.log' 


There standby redo logs. Let`s drop it

 SQL> select group#, bytes from v$standby_log;  
   GROUP# BYTES  
 ---------- ----------  
  4 314572800  
  5 314572800  
  6 314572800  
  7 314572800  
 SQL> set linesize 150  
 SQL> col member for a80  
 SQL> select group#, member from v$logfile;  
   GROUP# MEMBER  
 ---------- --------------------------------------------------------------------------------  
  1 /u01/oracle/oradata/XXX/redo01.log  
  2 /u01/oracle/oradata/XXX/redo02.log  
  3 /u01/oracle/oradata/XXX/redo03.log  
  4 /u01/oracle/fast_recovery_area/XXX/onlinelog/o1_mf_4_c5jf59f8_.log  
  5 /u01/oracle/fast_recovery_area/XXX/onlinelog/o1_mf_5_c5jf5df9_.log  
  6 /u01/oracle/fast_recovery_area/XXX/onlinelog/o1_mf_6_c5jf5hfv_.log  
  7 /u01/oracle/fast_recovery_area/XXX/onlinelog/o1_mf_7_c5jf5lw1_.log  
 7 rows selected.  


[oracle@TESTDB onlinelog]$ pwd
/u01/oracle/fast_recovery_area/XXXX/onlinelog

[oracle@TESTDB onlinelog]$ ls -lrt  
 total 1228820  
 -rw-r-----. 1 oracle oinstall 314573312 Nov 27 14:47 o1_mf_4_c5jf59f8_.log  
 -rw-r-----. 1 oracle oinstall 314573312 Nov 27 14:47 o1_mf_5_c5jf5df9_.log  
 -rw-r-----. 1 oracle oinstall 314573312 Nov 27 14:47 o1_mf_6_c5jf5hfv_.log  
 -rw-r-----. 1 oracle oinstall 314573312 Nov 27 14:47 o1_mf_7_c5jf5lw1_.log



 SQL> select status, group#, bytes from v$standby_log;  
 STATUS    GROUP#  BYTES  
 ---------- ---------- ----------  
 UNASSIGNED   4 314572800  
 UNASSIGNED   5 314572800  
 UNASSIGNED   6 314572800  
 UNASSIGNED   7 314572800  
 SQL> alter database drop standby logfile group 4;  
 Database altered.  
 SQL> alter database drop standby logfile group 5;  
 Database altered.  
 SQL> alter database drop standby logfile group 6;  
 Database altered.  
 SQL> alter database drop standby logfile group 7;  
 Database altered.  

After restart db check alertlog

SQL> shut immediate  
 Database closed.  
 Database dismounted.  
 ORACLE instance shut down.  
 SQL> startup  
 ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance  
 ORACLE instance started.  
 Total System Global Area 8584982528 bytes  
 Fixed Size   2260128 bytes  
 Variable Size  6341788512 bytes  
 Database Buffers 2214592512 bytes  
 Redo Buffers   26341376 bytes  
 Database mounted.  
 Database opened.  
 SQL>   

Alertlog is clear
Fri Nov 27 15:15:42 2015  
 ALTER DATABASE OPEN  
 LGWR: STARTING ARCH PROCESSES  
 Fri Nov 27 15:15:42 2015  

Sunday, November 22, 2015

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  

Monday, November 16, 2015

Fix INS-32025

Sometimes we face "[INS-32025] The chosen installation conflicts with software already installed in the given Oracle home" error when we reinstall Oracle home.



To fix this error, go to oraInventory folder.


cd /u01/oraInventory/ContentsXML --this is my folder
edit inventory.xml any editor
remove below line:

<HOME NAME="OraDb11g_home1" LOC="/u01/oracle/product/11.2.0/dbhome_1" TYPE="O" IDX="1"/>

execute runInstaller again

Thursday, November 5, 2015

List of most used tables

I requested to gather most used tables list in production database.
After investigation I found some advice and of course metalink note.

Here is OTN link:  https://forums.oracle.com/forums/thread.jspa?threadID=511661


Use below query.

SQL> SELECT ROWNUM AS RANK, Seg_Lio.*  
  FROM ( SELECT St.Owner,  
          St.Obj#,  
          St.Object_Type,  
          St.Object_Name,  
          St.VALUE,  
          'LIO' AS Unit  
       FROM V$segment_Statistics St  
       WHERE St.Statistic_Name = 'logical reads'  
     ORDER BY St.VALUE DESC) Seg_Lio  
 WHERE owner not in ('SYS', 'SYSTEM') and object_type='TABLE' and ROWNUM <= 20  
 UNION ALL  
 SELECT ROWNUM AS RANK, Seq_Pio_r.*  
  FROM ( SELECT St.Owner,  
          St.Obj#,  
          St.Object_Type,  
          St.Object_Name,  
          St.VALUE,  
          'PIO Reads' AS Unit  
       FROM V$segment_Statistics St  
       WHERE St.Statistic_Name = 'physical reads'  
     ORDER BY St.VALUE DESC) Seq_Pio_r  
 WHERE owner not in ('SYS', 'SYSTEM') and object_type='TABLE' and ROWNUM <= 20  
 UNION ALL  
 SELECT ROWNUM AS RANK, Seq_Pio_w.*  
  FROM ( SELECT St.Owner,  
          St.Obj#,  
          St.Object_Type,  
          St.Object_Name,  
          St.VALUE,  
          'PIO Writes' AS Unit  
       FROM V$segment_Statistics St  
       WHERE St.Statistic_Name = 'physical writes'  
     ORDER BY St.VALUE DESC) Seq_Pio_w  
 WHERE owner not in ('SYS', 'SYSTEM') and object_type='TABLE' and ROWNUM <= 20  
 UNION ALL  
 SELECT ROWNUM AS RANK, Seq_Pio_w.*  
  FROM ( SELECT St.Owner,  
          St.Obj#,  
          St.Object_Type,  
          St.Object_Name,  
          St.VALUE,  
          'PIO READS Direct' AS Unit  
       FROM V$segment_Statistics St  
       WHERE St.Statistic_Name = 'physical reads direct'  
     ORDER BY St.VALUE DESC) Seq_Pio_w  
 WHERE owner not in ('SYS', 'SYSTEM') and object_type='TABLE' and ROWNUM <= 20  
 UNION ALL  
 SELECT ROWNUM AS RANK, Seq_Pio_w.*  
  FROM ( SELECT St.Owner,  
          St.Obj#,  
          St.Object_Type,  
          St.Object_Name,  
          St.VALUE,  
          'DB Block changes' AS Unit  
       FROM V$segment_Statistics St  
       WHERE St.Statistic_Name = 'db block changes'  
     ORDER BY St.VALUE DESC) Seq_Pio_w  
 WHERE owner not in ('SYS', 'SYSTEM') and object_type='TABLE' and ROWNUM <= 20  
For detail please refer to metalink note: 252597.1

Also you may select below views to get some necessary information.

--tables which modificated
 SQL> select * from dba_tab_modifications where table_owner='????' 

Starting Oracle 11g if your statistics_level`s value TYPICAL Oracle automatically will gather and monitor your tables.

--List of monitored tables
SQL> select * from dba_tables where owner='?????' and monitoring='YES' 


 SQL> select owner, monitoring, count(1)   
 from dba_tables   
 group by owner, monitoring   
 order by 1, count(1) 




Thursday, October 29, 2015

Fix ORA-08104

While rebuilding index my toad session was hanged and I decided to kill session but it also hanged

SQL> alter index xxx.xxxxx rebuild online parallel 8;

To fix it I connected db with new sesssion and got object_id of mentioned index

 SQL> select object_id obj#, i.status from dba_indexes i, dba_objects o  
 where o.object_name=i.index_name and  
 i.index_name='LOYAL_RES_IDX1';


--Note flags
SQL> select flags from ind$ where obj#=356001; 


Using DBMS_REPAIR package clean index

SQL> declare  
 isclean boolean;  
 begin  
 isclean :=false;  
 while isclean=false loop  
 isclean := DBMS_REPAIR.ONLINE_INDEX_CLEAN  
 (dbms_repair.all_index_id,dbms_repair.lock_wait);  
 dbms_lock.sleep(10);  
 end loop;  
 end;  
 /  


--Note flags
 SQL> select flags from ind$ where obj#=356001; 


As you see it was decreased and normal

Thursday, October 15, 2015

Brief practice about shrink extents

Today after analyzing segments I found out some tables have 0 rows but segment size more than 2 GB. For practice purpose I simulated some actions on test environment. To do that I created a simple user, grant him essential grants, created table, load some data etc.

 create user ulfet identified by ulfet;  
 grant connect, resource to ulfet; 

--create table with 1 mln rows
 create table ulfet.btt nologging as  
 SELECT   
        LEVEL id,      
        dbms_random.string ('U', 10) text1,   
        reverse(dbms_random.string ('U', 10)) text2  
 FROM   dual  
 CONNECT BY   LEVEL   <= 1000000;  

--Check segment, block size
 SQL> select  
           bytes,   
           bytes/1024/1024 SIZEMB,   
           extents,   
           s.blocks,  
           t.num_rows,   
           t.last_analyzed,   
           t.blocks  
 from dba_segments s, dba_tables t  
 where s.segment_name = t.table_name   
 and segment_name='BTT'; 

 BYTES,SIZEMB,EXTENTS,BLOCKS,NUM_ROWS,LAST_ANALYZED,BLOCKS_1  
 37748736,36,51,4608,,,  





--compute statistics
 analyze table ulfet.btt compute statistics; 

--Check again segment, block size
SQL> select  
           bytes,   
           bytes/1024/1024 SIZEMB,   
           extents,   
           s.blocks,  
           t.num_rows,   
           t.last_analyzed,   
           t.blocks  
 from dba_segments s, dba_tables t  
 where s.segment_name = t.table_name and segment_name='BTT';  

 BYTES,SIZEMB,EXTENTS,BLOCKS,NUM_ROWS,LAST_ANALYZED,BLOCKS_1  
 37748736,36,51,4608,1000000,14.10.2015 10:03:04,4504 

--inserted 15 000 000 rows
 insert into ulfet.btt  
 select * from ulfet.btt;  

 insert into ulfet.btt  
 select * from ulfet.btt;  

 insert into ulfet.btt  
 select * from ulfet.btt;  

 insert into ulfet.btt  
 select * from ulfet.btt;  

 select count(1) from ulfet.btt;  
 --16000000  
commit;

Now check segment size
 SQL> select  
           bytes,   
           bytes/1024/1024 SIZEMB,   
           extents,   
           s.blocks,  
           t.num_rows,   
           t.last_analyzed,   
           t.blocks  
 from dba_segments s, dba_tables t  
 where s.segment_name = t.table_name and segment_name='BTT';  

 BYTES,SIZEMB,EXTENTS,BLOCKS,NUM_ROWS,LAST_ANALYZED,BLOCKS_1  
 587202560,560,141,71680,1000000,14.10.2015 10:03:04,4504 

--gather table`s stat again for fresh statistics
 EXEC DBMS_STATS.gather_table_stats('ULFET', 'BTT');

--Check segment and block size
 SQL> select  
           bytes,   
           bytes/1024/1024 SIZEMB,   
           extents,   
           s.blocks,  
           t.num_rows,   
           t.last_analyzed,   
           t.blocks  
 from dba_segments s, dba_tables t  
 where s.segment_name = t.table_name and segment_name='BTT';  

 BYTES,SIZEMB,EXTENTS,BLOCKS,NUM_ROWS,LAST_ANALYZED,BLOCKS_1  
 587202560,560,141,71680,16000000,14.10.2015 10:10:15,71377

Now delete rows
 delete from ulfet.btt;  
 commit; 

--Again take statistics
 EXEC DBMS_STATS.gather_table_stats('ULFET', 'BTT');

--Check again
 SQL> select  
           bytes,   
           bytes/1024/1024 SIZEMB,   
           extents,   
           s.blocks,  
           t.num_rows,   
           t.last_analyzed,   
           t.blocks  
 from dba_segments s, dba_tables t  
 where s.segment_name = t.table_name and segment_name='BTT';  

 BYTES,SIZEMB,EXTENTS,BLOCKS,NUM_ROWS,LAST_ANALYZED,BLOCKS_1  
 587202560,560,141,71680,0,14.10.2015 10:17:30,71377 

As you see extent not changed

Ulfet user has quota on two tablespaces
SQL> select   
     tablespace_name,   
     bytes,   
     bytes/1024/1024 SIZEMB,   
     blocks   
 from dba_ts_quotas   
 where username='ULFET';

 TABLESPACE_NAME,BYTES,SIZEMB,BLOCKS  
 DATA01,0,0,0  
 DATA001,624951296,596,76288  

--Move segment to another tablespace for shrink purpose
SQL> alter table ulfet.btt move tablespace DATA01;

Now check again
 SQL> select   
     tablespace_name,   
     bytes,   
     bytes/1024/1024 SIZEMB,   
     blocks   
 from dba_ts_quotas   
 where username='ULFET'; 

 TABLESPACE_NAME,BYTES,SIZEMB,BLOCKS  
 DATA01,65536,0,0625,8  
 DATA001,37748736,36,4608  

--Check segment size and extents
SQL> select  
           bytes,   
           bytes/1024/1024 SIZEMB,   
           extents,   
           s.blocks,  
           t.num_rows,   
           t.last_analyzed,   
           t.blocks  
 from dba_segments s, dba_tables t  
 where s.segment_name = t.table_name and segment_name='BTT'; 

 BYTES,SIZEMB,EXTENTS,BLOCKS,NUM_ROWS,LAST_ANALYZED,BLOCKS_1  
 65536,0,0625,1,8,0,14.10.2015 10:17:30,71377 

Sunday, September 20, 2015

Activate Standby Database on Oracle 11g

On Oracle 11g to activate standby database we should do:

--stop apply process  
 SQL> alter database recover managed standby database cancel;  
 --finish recovery managed  
 SQL> alter database recover managed standby database finish;  
 Database altered.  
 --activate database  
 SQL> alter database activate physical standby database;  
 Database altered.  
 --open database  
 SQL> alter database open;  
 Database altered.  
 SQL> select name, open_mode from v$database;  
 NAME   OPEN_MODE  
 --------- --------------------  
 PROD1   READ WRITE  
 SQL>  

Tuesday, July 7, 2015

Remove Data Guard Configuration Oracle 11g

Today I will show you how to remove DG configuration

DGMGRL> show configuration;  
 Configuration  
  Name:        DGMANAGER  
  Enabled:       YES  
  Protection Mode:   MaxAvailability  
  Databases:  
   PROD - Primary database  
   STAND - Physical standby database  
 Fast-Start Failover: DISABLED  
 Current status for "DGMANAGER":  
 SUCCESS  

 DGMGRL> remove configuration;  
 Error: ORA-16627: operation disallowed since no standby databases would remain to support protection mode  
 Failed.  

I tried to remove database from configuration

DGMGRL> remove database "STAND";  
 Error: ORA-16627: operation disallowed since no standby databases would remain to support protection mode  
 Failed.  

But result was same. Unsuccess.

I changed protection mode to MaxPerformance and then retied again

DGMGRL> edit configuration set protection mode as MaxPerformance;  
 Succeeded.  

DGMGRL> show configuration;  
 Configuration  
  Name:        DGMANAGER  
  Enabled:       YES  
  Protection Mode:   MaxPerformance  
  Databases:  
   PROD - Primary database  
   STAND - Physical standby database  
 Fast-Start Failover: DISABLED  
 Current status for "DGMANAGER":  
 SUCCESS  

DGMGRL> remove database "STAND"  
 Removed database "STAND" from the configuration  
 DGMGRL> remove configuration;  
 Removed configuration  
 DGMGRL> show configuration  
 Error: ORA-16532: Data Guard broker configuration does not exist  
 Configuration details cannot be determined by DGMGRL  
 DGMGRL>  

Dataguard configuration successfully removed. Now we have to disable some parameters.

SQL> set linesize 200  
 SQL> show parameter dg_broker  
 NAME                 TYPE               VALUE  
 ------------------------------------ --------------------------------- ------------------------------  
 dg_broker_config_file1        string              /u01/app/oracle/product/11.1.0  
                                     /db_1/dbs/dr1PROD.dat  
 dg_broker_config_file2        string              /u01/app/oracle/product/11.1.0  
                                     /db_1/dbs/dr2PROD.dat  
 dg_broker_start           boolean              TRUE  
 SQL>  


Change dg_broker_start`s value to FALSE on both side

alter system set dg_broker_start=FALSE;

At the end
remove dr*.dat files on both side

 -bash-3.00$ pwd  
 /u01/app/oracle/product/11.1.0/db_1/dbs  
 -bash-3.00$ ls -lrt dr*.dat  
 -rw-r-----  1 oracle  oinstall    1024 Jul 07 12:25 dr2PROD.dat  
 -rw-r-----  1 oracle  oinstall    1024 Jul 07 12:25 dr1PROD.dat  
 -bash-3.00$ rm dr*.dat  


 -bash-4.2$ pwd  
 /u01/app/oracle/product/11.0.1/db_1/dbs  
 -bash-4.2$ ls -lrt dr*.dat  
 -rw-r-----  1 oracle  oinstall    1024 Jul 07 12:24 dr2STAND.dat  
 -rw-r-----  1 oracle  oinstall    1024 Jul 07 12:24 dr1STAND.dat  
 -bash-4.2$ rm dr*.dat 

Sunday, February 8, 2015

WARNING: Subscription for node down event still pending

Today early morning I saw strange error on listener log.

...
Mon Feb 09 07:53:24 2015
WARNING: Subscription for node down event still pending
09-FEB-2015 07:53:24 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=????)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=185599744)) * status * 0
...

After searching on metalink I found : MOS document with ID 372959.1

In a nutshell to fix it we should add SUBSCRIBE_FOR_NODE_DOWN_EVENT_YOURLISTENER_NAME=OFF on listener.ora file

In my case:

 SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER=OFF 

Then restart/reload listener.
 lsnrctl reload;