Bypass RMAN-08137 Error on Primary Database

 Hi  Friends                                                                                                                                                                                                              I am going to explain how to bypass RMAN-08137 error when we use dataguard. When we try to delete archive log files in primary database, we can see following error. It means we can not archivelog because some archivelogs has not been moved to standby database yet. Maybe you can ask that why we need to  remove this archivelog without moved to standby database.  In certain circumstance when there is no space for archivelog in primary database, database will be hang.In this situtation  we need to make room for new archive log and we try to remove archivelog file  by using rman but we have seen following error. I will explain that how can we bypass this error. Actually there is a simple way to do this.We can remove archivelog manually but this method may lead us to make wrong things so  I will explain to remove archivelog by using rman.

RMAN> list archivelog all;

List of Archived Log Copies for database with db_unique_name YAYAPRM
=====================================================================

Key     Thrd Seq     S Low Time
——- —- ——- – ———
2086    1    132     A 14-OCT-15
Name: /oracle/fast_recovery_area/YAYAPRM/archivelog/2015_10_14/o1_mf_1_132_c1wfl5dv_.arc

2087    1    133     A 14-OCT-15
Name: /oracle/fast_recovery_area/YAYAPRM/archivelog/2015_10_14/o1_mf_1_133_c1wfl9ds_.arc

2088    1    134     A 14-OCT-15
Name: /oracle/fast_recovery_area/YAYAPRM/archivelog/2015_10_14/o1_mf_1_134_c1wflbhp_.arc

2089    1    135     A 14-OCT-15
Name: /oracle/fast_recovery_area/YAYAPRM/archivelog/2015_10_14/o1_mf_1_135_c1wfldfp_.arc

2090    1    136     A 14-OCT-15
Name: /oracle/fast_recovery_area/YAYAPRM/archivelog/2015_10_14/o1_mf_1_136_c1wflfj5_.arc

RMAN> delete archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=17 device type=DISK
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/oracle/fast_recovery_area/YAYAPRM/archivelog/2015_10_14/o1_mf_1_132_c1wfl5dv_.arc thread=1 sequence=132
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/oracle/fast_recovery_area/YAYAPRM/archivelog/2015_10_14/o1_mf_1_133_c1wfl9ds_.arc thread=1 sequence=133
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/oracle/fast_recovery_area/YAYAPRM/archivelog/2015_10_14/o1_mf_1_134_c1wflbhp_.arc thread=1 sequence=134
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/oracle/fast_recovery_area/YAYAPRM/archivelog/2015_10_14/o1_mf_1_135_c1wfldfp_.arc thread=1 sequence=135
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/oracle/fast_recovery_area/YAYAPRM/archivelog/2015_10_14/o1_mf_1_136_c1wflfj5_.arc thread=1 sequence=136

Query Result Cache in Oracle

Hi

I will try to explain query result cache in the oracle. Sometimes query response time is very important to us and of course for application. Sometimes we execute same query many times and each time we read data from disk or buffer cache. If which we want to data is in the buffer, response time can be acceptable.it  may not a problem. Because data fetching from buffer cache is faster than from disk but maybe data is not in the buffer cache all the time. At this point we should go disk to fetch data again. At this situation performance degradation can be  appears. A new feature came with 11g to help this kind of performance problem. This is query result cache. This is a subset area of  SGA. We keep result of which we want to query and when we execute this query, result has fetched from result cache. Before doing an example we will look that which parameter is exist in database and how it can be managed with database parameter. If database use AMM, result cache has controlled by the database.We can specify result_cache_max_size parameter. We add upper limit for result cache with this parameter. So AMM can increase the result_cache size maximum to this value. This parameter is dynamic so we can change this parameter while database is running. If this parameter is zero during database start. It means that result cache has disabled. And result_cache_mode parameter.This parameter have two option.FORCE means that all queries will cached. MANUAL means that we specify cached queries with hint. result_cache_max_result  means that  percentage of result_cache_max_size that any single result can use. We can check result cache status with following command.

SQL> SELECT dbms_result_cache.status() FROM dual;
DBMS_RESULT_CACHE.STATUS()
—————————-
ENABLED

Oracle 12c Dataguard Switchover Verify

Hi Friends

I want to mention  a new feature about data guard that came with oracle 12c.This feature is switchover verify. As  you know switchover is planned role transition. So you make switchover when you want to test that whether standby database is working correctly.Before 12c you make switchover and you see error during switchover if there is an error in dataguard configuration. But now we can check that whether data guard configuration is proper before switchover. We can check some configuration with this verify. Some of this checked configurations are like following.

1) Whether redo apply is running on the standby
2) Whether log destination is correct
3) Version of the switchover target is 12.1 or later

Clone Pluggable Database without Data

Hi

Sometimes we need to database that  include only object structure without data.The new feature came too with 12.1.0.2.0 version. We can create pluggable database with only objects definition with “no data” clause. This clause can be used while create plugable database and  only structure will clone without data.Let’s do a simple example.Remember that already we have container database from previous post. Our pluggable database are as the following and we are going to clone CLONEPDB pluggable database without data.

Clone 12c Non Container Database To Container Database as Pluggable Database over the Network

Hi

In the my previous  post I mentioned that clone pluggable database to another Container database over the network. In this post I will mention that  clone non container  database to 12c container database as the pluggable database over the network. We will use same environment.

Container Database: TRGCDB

SQL> select name,open_mode from v$pdbs;
NAME                           OPEN_MODE
—————————— ———-
PDB$SEED                       READ ONLY
PDB1                           READ WRITE
CLONEPDB                       READ WRITE

Non Container Database :NONCDB

SQL> select name from v$database;
NAME
———
NONCDB

Clone Pluggable Database To Another Container Database over the Network

Hi

I would like to mention a new feature that came with 12.1.0.2.0 version. This feature allow us to clone pdb to another container database  or noncdb database to  container database  as pluggable database over the network. In this post we clone pluggable database to another  container database  over the  network. Our used environments are the following.

Target Container Database is TRGCDB and including pluggable database.

SQL> select name,open_mode from v$pdbs;
NAME                           OPEN_MODE
—————————— ———-
PDB$SEED                       READ ONLY
PDB1                           READ WRITE

Source Container Database is SRCCDB and including pluggable database.

SQL> select name,open_mode from v$pdbs;
NAME                           OPEN_MODE
—————————— ———-
PDB$SEED                       READ ONLY
CLONEPDB                       READ WRITE

We clone clonepdb pluggable database in the source container database over network. Before doing this  we should meet some prerequisite in order to do this.

Oracle Recovery Catalog

Hi

I want to explain rman catalog database.When we take backup, there are some information about this backup (backup time,backupset information which database backup etc) This rman information  can be kept in two different place. This information can be kept in the controlfile but only one database metadata of rman  can be kept with this way. Also there is a limitation in this method. Metadata of rman can be keep for specified time period. We specify a time with CONTROL_FILE_RECORD_KEEP_TIME parameter. This parameter means that minimum day before deleting  metadata about rman. Other way we can use catalog database to keep metadata of rman. One or more database rman info can be keep with this way in the one central inventory. So if we have one more than databases we can use catalog database to keep metadata of rman backup. Also we can keep metadata of backup forever. We specfiy this when we take backup. But control file does not support this. Let’s configure catalog database.

As I mentioned before catalog database is different database and we create catalog user and tablespace to kept metadata of rman.

1)First we create a tablespace.

SQL> create tablespace rmancatalog datafile ‘/oracle/oradata/catdb/catalog.dbf’ size 100M;
Tablespace created

FAL Request Error ORA-01009 on Data Guard

Hi

I want to mention an error that I took 2 weeks ago on my data guard enviroinment. My database version is like following

SQL> select * from v$version;

BANNER
——————————————————————————–
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 – 64bit Production
PL/SQL Release 11.1.0.6.0 – Production
CORE    11.1.0.6.0      Production
TNS for Linux: Version 11.1.0.6.0 – Production
NLSRTL Version 11.1.0.6.0 – Production

And when there are log  gap between primary and standby database after start log applying process. I seen that log gap can not be resolve.When  ı check alert log ı see that following log information.

2014-10-30 10:08:12.094000 +02:00
FAL[client, MRP0]: Error 1009 fetching archived redo log from PR_DATAG
Errors in file /oracle/diag/rdbms/datags/datags/trace/datags_mrp0_32071.trc:
ORA-01009: missing mandatory parameter
2014-10-30 10:15:25.737000 +02:00

Disable Active Data Guard on the 11g

Hi

I want to mention a subject about active dataguard  that I liked  when I hear. When you use Active data guard you have  to pay extra license cost. But sometimes you don’t need to active dataguard but you can inadvertently open active data guard. For example you have shutdown standby database and open “startup” command directly without mount. This command open database as “read only” and you start log applying so that you use active data guard option without be aware. Actually you don’t use active data guard  but it is active.Let’s do what I say.First stop our standby database after that start .

SQL> startup
ORACLE instance started.
Total System Global Area 1653518336 bytes
Fixed Size                  2213896 bytes
Variable Size             956303352 bytes
Database Buffers          687865856 bytes
Redo Buffers                7135232 bytes
Database mounted.
Database opened.

SQL> select open_mode from v$database;
OPEN_MODE
——————–
READ ONLY

Dataguard Broker Configuration

Hi

I will explain dataguard broker configuration in this my post.Database version is 11.2.First off all we set dg_broker_start parameter all databases that which we intend  add to broker configuration.We have one primary database and one physical standby database.Also in order to configure data guard broker we must use spfile both database.

primary database unique name=datagp

standby database unique name=datags

SQL> alter system set dg_broker_start=TRUE scope=both;
System altered.

We add following entry to primary database listener.ora file and we execute “lsnrctl reload” command.

SID_LIST_LISTENER=
(SID_LIST=
(SID_DESC=
(GLOBAL_DBNAME=datagp_DGMGRL)
(SID_NAME=datagp)
(ORACLE_HOME=/oracle/ora11g)
)
)