askMLabs

In this article we will see step by step instructions on how to configure dataguard broker configuration using DGMGRL utility. The dataguard broker makes it easy to maintain and administer several standby databases. Dataguard broker maintains its own configuration files and runs a background process DMON both on primary and standby database servers. Dataguard broker configuration can be created using either OEM grid control or using a command line utility DGMGRL. In the present article we are using DGMGRL to create dataguard broker configuration to maintain standby databases.

1. Stop Managed Recovery Process On Standby Database
2. Shutdown Standby Database
3. Connect To Primary Database As SYS
4. Create A New Physical Standby Controlfile From The Primary
5. Copy Created Controlfile to Standby Server
6. Mount Standby Database With Newly Created Controlfile
7. Rename Datafiles ( Optional If db_file_name_convert and log_file_name_convert are specified)
8. Create Standby Redo Logs ( Optional )
9. Re-Enable Flashback
10. Start Managed Recovery

On Standby Server :

STEP 1:

[oracle@dgaskmsby01 ~]$ clear
[oracle@dgaskmsby01 ~]$ sqlplus '/as sysdba'
SQL*Plus: Release 11.2.0.2.0 Production on Sun Nov 27 10:09:21 2011
Copyright (c) 1982, 2010, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> alter database recover managed standby database cancel;
Database altered.

STEP 2:

SQL> shut immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@dgaskmsby01 ~]$ clear

On Primary Server :

STEP 3 : 
[oracle@dgaskmpri01 ~]$ sqlplus '/as sysdba'

SQL*Plus: Release 11.2.0.2.0 Production on Sun Nov 27 10:10:14 2011
Copyright (c) 1982, 2010, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

STEP 4:

SQL> alter database create standby controlfile as '/tmp/askm/askm_control01.ctl';
Database altered.

On Standby Server :

STEP 5 :

[oracle@dgaskmsby01 ~]$ cd /tmp/askm
[oracle@dgaskmsby01 askm]$ scp root@192.168.1.34:/tmp/askm/askm_control01.ctl .
root@192.168.1.34's password:
askm_control01.ctl                                                                                                                    100%   10MB   3.3MB/s   00:03
[oracle@dgaskmsby01 askm]$ grep -i controlfile $ORACLE_HOME/dbs/initsbyorcl.ora
*.control_files='/home/oracle/app/oracle/oradata/sbyorcl/s_control01.ctl','/home/oracle/app/oracle/flash_recovery_area/sbyorcl/s_control02.ctl'#Restore Controlfile
[oracle@dgaskmsby01 askm]$ cp askm_control01.ctl /home/oracle/app/oracle/oradata/sbyorcl/s_control01.ctl
[oracle@dgaskmsby01 askm]$ cp askm_control01.ctl /home/oracle/app/oracle/flash_recovery_area/sbyorcl/s_control02.ctl
STEP 6 :
[oracle@dgaskmsby01 askm]$ sqlplus '/as sysdba'
SQL*Plus: Release 11.2.0.2.0 Production on Sun Nov 27 10:12:55 2011
Copyright (c) 1982, 2010, Oracle.  All rights reserved.
Connected to an idle instance.
SQL> startup mount
ORACLE instance started.
Total System Global Area  456146944 bytes
Fixed Size                  1344840 bytes
Variable Size             348129976 bytes
Database Buffers          100663296 bytes
Redo Buffers                6008832 bytes
Database mounted.
STEP 9 :

SQL> alter database flashback off;
Database altered.
SQL> alter database flashback on;
alter database flashback on
*
ERROR at line 1:
ORA-01153: an incompatible media recovery is active
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> alter database flashback on;
Database altered.
STEP 10 :SQL> alter database recover managed standby database using current logfile disconnect from session;
Database altered.

Reference :  459411.1

Hope It Helps

SRI

	Primary Site	Standby Site
Hostname	dgaskmpri01	dgaskmsby01
Database Name	orcl	orcl
Database Unique Name	orcl	sbyorcl
Net Service Name	orcl	sbyorcl

Primary Site Preparation :

SQL> select FORCE_LOGGING from v$database;
SQL> ALTER DATABASE FORCE LOGGING;

SQL> select name,user from v$database;
NAME USER
--------- ------------------------------
ORCL SYS
SQL> col group# for 9999
SQL> col member for a50
SQL> set linesize 120
SQL> select name,user from v$database;
NAME USER
--------- ------------------------------
ORCL SYS
SQL> select GROUP#,THREAD#,MEMBERS,BYTES FROM V$LOG;
GROUP# THREAD# MEMBERS BYTES
------ ---------- ---------- ----------
1 1 1 52428800
2 1 1 52428800
3 1 1 52428800
SQL> select group#,member from v$logfile;
GROUP# MEMBER
------ --------------------------------------------------
3 /home/oracle/app/oracle/oradata/orcl/redo03.log
2 /home/oracle/app/oracle/oradata/orcl/redo02.log
1 /home/oracle/app/oracle/oradata/orcl/redo01.log
SQL> SELECT GROUP#, BYTES FROM V$STANDBY_LOG;
no rows selected
SQL> ALTER DATABASE ADD STANDBY LOGFILE ('/home/oracle/app/oracle/oradata/orcl/s_redo01.log') SIZE 52428800;
Database altered.
SQL> ALTER DATABASE ADD STANDBY LOGFILE ('/home/oracle/app/oracle/oradata/orcl/s_redo02.log') SIZE 52428800;
Database altered.
SQL> SELECT GROUP#, BYTES FROM V$STANDBY_LOG;
GROUP# BYTES
------ ----------
4 52428800
5 52428800
SQL> ALTER DATABASE ADD STANDBY LOGFILE ('/home/oracle/app/oracle/oradata/orcl/s_redo03.log') SIZE 52428800;
Database altered.
SQL> ALTER DATABASE ADD STANDBY LOGFILE ('/home/oracle/app/oracle/oradata/orcl/s_redo04.log') SIZE 52428800;
Database altered.
SQL> SELECT GROUP#, BYTES FROM V$STANDBY_LOG;
GROUP# BYTES
------ ----------
4 52428800
5 52428800
6 52428800
7 52428800
SQL>

DB_NAME=orcl
DB_UNIQUE_NAME=orcl
LOG_ARCHIVE_CONFIG='DG_CONFIG=(orcl,sbyorcl)'LOG_ARCHIVE_DEST_1='LOCATION=/home/oracle/app/oracle/flash_recovery_area/orcl/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=orcl'LOG_ARCHIVE_DEST_2='SERVICE=sbyorcl ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=sbyorcl'LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
LOG_ARCHIVE_MAX_PROCESSES=30
FAL_SERVER=sbyorcl
DB_FILE_NAME_CONVERT='sbyorcl','orcl'LOG_FILE_NAME_CONVERT='/home/oracle/app/oracle/flash_recovery_area/sbyorcl/','/home/oracle/app/oracle/flash_recovery_area/orcl/'STANDBY_FILE_MANAGEMENT=AUTO

SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP MOUNT;
ORACLE instance started.
Total System Global Area 456146944 bytes
Fixed Size 1344840 bytes
Variable Size 381684408 bytes
Database Buffers 67108864 bytes
Redo Buffers 6008832 bytes
Database mounted.
SQL> ALTER DATABASE ARCHIVELOG;
Database altered.
SQL> ALTER DATABASE OPEN;
Database altered.
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /home/oracle/app/oracle/flash_recovery_area/orcl/
Oldest online log sequence 360
Next log sequence to archive 362
Current log sequence 362
SQL>

In this demo I am using cold backup of the primary database. There are various other options like RMAN duplicate from active database to create physical standby database without even having the primary database backup in 11g. But in this article I am showing setup without RMAN and using simple sql commands.

Create a temporary directory (/tmp/askm/) on primary server and copy all the controlfile,online redolog files and database files to this location after shutting down the database.

SQL> startup mount
ORACLE instance started.
Total System Global Area 456146944 bytes
Fixed Size 1344840 bytes
Variable Size 381684408 bytes
Database Buffers 67108864 bytes
Redo Buffers 6008832 bytes
Database mounted.
SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS '/tmp/askm/s_control01.ctl';
Database altered.
SQL> ALTER DATABASE OPEN;
Database altered.

SQL> CREATE PFILE='/tmp/askm/initsbyorcl.ora' FROM SPFILE;
File created.

[oracle@dgaskmpri01 admin]$ cat listener.ora
LISTENER_PRI =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1525))
)
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dgaskmpri01.localdomain)(PORT = 1525))
)
)
SID_LIST_LISTENER_PRI =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME = /home/oracle/app/oracle/product/11.2.0/dbhome_2)
(SID_NAME = orcl)
)
)
[oracle@dgaskmpri01 admin]$ cat tnsnames.ora
orcl =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dgaskmpri01.localdomain)(PORT = 1525))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SID=orcl)
)
)
sbyorcl =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dgaskmsby01.localdomain)(PORT = 1525))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SID=sbyorcl)
)
)
[oracle@dgaskmpri01 admin]$

Create a temporary directory(/tmp/askm) on standby server and copy coldbackup, init.ora, password file(orapwsbyorcl) and standby controlfile (s_control01.ctl) from primary server to standby server.

[oracle@dgaskmsby01]$ mkdir /home/oracle/app/oracle/oradata/sbyorcl/
[oracle@dgaskmsby01]$ mkdir /home/oracle/app/oracle/flash_recovery_area/sbyorcl/
[oracle@dgaskmsby01]$ cd $ORACLE_HOME/dbs
[oracle@dgaskmsby01 dbs]$ cd /home/oracle/app/oracle/oradata/sbyorcl/
[oracle@dgaskmsby01 sbyorcl]$ cp /tmp/askm/*.dbf .
[oracle@dgaskmsby01 sbyorcl]$ cp /tmp/askm/*.log .
[oracle@dgaskmsby01 sbyorcl]$ cp /tmp/askm/s_control01.ctl .
[oracle@dgaskmsby01 sbyorcl]$ cp /tmp/askm/s_control01.ctl /home/oracle/app/oracle/flash_recovery_area/sbyorcl/s_control02.ctl
[oracle@dgaskmsby01 sbyorcl]$ cp /tmp/askm/initsbyorcl.ora $ORACLE_HOME/dbs

DB_NAME=orcl
DB_UNIQUE_NAME=sbyorcl
LOG_ARCHIVE_CONFIG='DG_CONFIG=(orcl,sbyorcl)'CONTROL_FILES='/home/oracle/app/oracle/oradata/sbyorcl/s_control01.ctl', '/home/oracle/app/oracle/flash_recovery_area/sbyorcl/s_control02.ctl'DB_FILE_NAME_CONVERT='orcl','sbyorcl'LOG_FILE_NAME_CONVERT='/home/oracle/app/oracle/flash_recovery_area/orcl/','/home/oracle/app/oracle/flash_recovery_area/sbyorcl/'LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
LOG_ARCHIVE_DEST_1='LOCATION=/home/oracle/app/oracle/flash_recovery_area/sbyorcl/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=sbyorcl'LOG_ARCHIVE_DEST_2='SERVICE=orcl ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=orcl'LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
STANDBY_FILE_MANAGEMENT=AUTO
FAL_SERVER=orcl

[oracle@dgaskmsby01 admin]$ cat listener.ora
LISTENER_SBY =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1525))
)
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dgaskmsby01.localdomain)(PORT = 1525))
)
)
SID_LIST_LISTENER_SBY =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME = /home/oracle/app/oracle/product/11.2.0/dbhome_2)
(SID_NAME = sbyorcl)
)
)
[oracle@dgaskmsby01 admin]$ cat tnsnames.ora
orcl =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dgaskmpri01.localdomain)(PORT = 1525))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SID=orcl)
)
)
sbyorcl =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dgaskmsby01.localdomain)(PORT = 1525))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SID=sbyorcl)
)
)
[oracle@dgaskmsby01 admin]$

On Primary Server:

[oracle@dgaskmpri01]$ lsnrctl stop LISTENER_PRI
[oracle@dgaskmpri01]$ lsnrctl start LISTENER_PRI
[oracle@dgaskmpri01]$ tnsping orcl
[oracle@dgaskmpri01]$ tnsping sbyorcl
[oracle@dgaskmpri01]$ sqlplus sys/xxxxx@orcl
[oracle@dgaskmpri01]$ sqlplus sys/xxxxx@sbyorcl

On Standby Server:

[oracle@dgaskmsby01]$ lsnrctl stop LISTENER_SBY
[oracle@dgaskmsby01]$ lsnrctl start LISTENER_SBY
[oracle@dgaskmsby01]$ tnsping orcl
[oracle@dgaskmsby01]$ tnsping sbyorcl
[oracle@dgaskmsby01]$ sqlplus sys/xxxxx@orcl
[oracle@dgaskmsby01]$ sqlplus sys/xxxxx@sbyorcl

Creating Physical Standby Database :

SQL> startup mount
ORACLE instance started.
Total System Global Area  456146944 bytes
Fixed Size                  1344840 bytes
Variable Size             381684408 bytes
Database Buffers           67108864 bytes
Redo Buffers                6008832 bytes
Database mounted.
SQL>

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;

On Standby:

SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;

Do some redo log switches

SQL> ALTER SYSTEM SWITCH LOGFILE;

On Standby:
  Verify that the recent archived log file is shifted to standby side and applied with the following commands.

SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;

egrep -i "DB_NAME|DB_UNIQUE_NAME|LOG_ARCHIVE_CONFIG|CONTROL_FILES|LOG_ARCHIVE_DEST_1|LOG_ARCHIVE_DEST_2|LOG_ARCHIVE_DEST_STATE_1|LOG_ARCHIVE_DEST_STATE_2|REMOTE_LOGIN_PASSWORDFILE|LOG_ARCHIVE_FORMAT|LOG_ARCHIVE_MAX_PROCESSES|FAL_SERVER|DB_FILE_NAME_CONVERT|LOG_FILE_NAME_CONVERT|STANDBY_FILE_MANAGEMENT" <specify init.ora parameter file>

To Cancel the Standby Recovery Mode:

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

Useful commands To Troubleshoot:

select message from v$dataguard_status where dest_id = 2;
select archived_thread#, archived_seq#, applied_thread#, applied_seq# from v$archive_dest_status;
select registrar, creator, thread#, sequence#, first_change#, next_change# from v$archived_log;
select thread#, sequence#, first_change#, next_change# from v$log_history;

To Verify Recover Process On Standby:

select thread#, sequence# from v$log where status='CURRENT'; = > On Primary
select thread#, sequence#, status from v$managed_standby where process='MRP0'; = > On Standby

References :
http://download.oracle.com/docs/cd/E11882_01/server.112/e25608/create_ps.htm#i63561
MOS ID :  249703.1

The following steps are useful to delete the backups which are marked as NO-EXPIRE. No expire backup are the backups for which the retention policy will not apply and the backups remain till you manually and forcibly delete these backups.  The best example for No-expire backups are the backups kept for training purposes. After successfully creating any training environment, we will backup the database with NO-Expire option and these backups will be used to refresh the database every week.

The following commands show you how to delete these no-expire backups on tape from  RMAN CATALOG. This is useful in cases where if you made any changes to the databases and need to preseve these changes in the database forever, you will take new NO-EXPIRE backups and delete the old backups.

RMAN> list backup summary;
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
145913  B  0  A SBT_TAPE    25-APR-11       1       1       YES        NOEXPIRE
145914  B  0  A SBT_TAPE    25-APR-11       1       1       YES        NOEXPIRE
145915  B  0  A SBT_TAPE    25-APR-11       1       1       YES        NOEXPIRE
145916  B  0  A SBT_TAPE    25-APR-11       1       1       YES        NOEXPIRE
145917  B  0  A SBT_TAPE    25-APR-11       1       1       YES        NOEXPIRE
147274  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147275  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147276  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147277  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147278  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147498  B  F  A SBT_TAPE    29-APR-11       1       1       NO         NOEXPIRE

RMAN> DELETE BACKUPSET 145913,145914,145915,145916,145917;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=522 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 05/01/2011 01:20:25
RMAN-06160: no backup pieces found for backup set key: 145913

RMAN> ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE sbt;
released channel: ORA_DISK_1
allocated channel: ORA_MAINT_SBT_TAPE_1
channel ORA_MAINT_SBT_TAPE_1: sid=522 devtype=SBT_TAPE
channel ORA_MAINT_SBT_TAPE_1: Data Protection for Oracle: version 5.5.2.0
RMAN> ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE sbt;
allocated channel: ORA_MAINT_SBT_TAPE_2
channel ORA_MAINT_SBT_TAPE_2: sid=525 devtype=SBT_TAPE
channel ORA_MAINT_SBT_TAPE_2: Data Protection for Oracle: version 5.5.2.0
RMAN> DELETE BACKUPSET 145913,145914,145915,145916,145917;
List of Backup Pieces
BP Key  BS Key  Pc# Cp# Status      Device Type Piece Name
------- ------- --- --- ----------- ----------- ----------
145919  145913  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set9_piece1_copy1_20110425_09mal5t9_1_1
145920  145914  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set8_piece1_copy1_20110425_08mal5t9_1_1
145921  145915  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set11_piece1_copy1_20110425_0bmal6d9_1_1
145922  145916  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set7_piece1_copy1_20110425_07mal5t9_1_1
145923  145917  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set10_piece1_copy1_20110425_0amal6br_1_1
Do you really want to delete the above objects (enter YES or NO)? NO
RMAN> delete noprompt BACKUPSET 145913,145914,145915,145916,145917;
List of Backup Pieces
BP Key  BS Key  Pc# Cp# Status      Device Type Piece Name
------- ------- --- --- ----------- ----------- ----------
145919  145913  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set9_piece1_copy1_20110425_09mal5t9_1_1
145920  145914  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set8_piece1_copy1_20110425_08mal5t9_1_1
145921  145915  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set11_piece1_copy1_20110425_0bmal6d9_1_1
145922  145916  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set7_piece1_copy1_20110425_07mal5t9_1_1
145923  145917  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set10_piece1_copy1_20110425_0amal6br_1_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of delete command on ORA_MAINT_SBT_TAPE_1 channel at 05/01/2011 01:27:05
ORA-27191: sbtinfo2 returned error
Additional information: 2

RMAN> delete noprompt force BACKUPSET 145913,145914,145915,145916,145917;
List of Backup Pieces
BP Key  BS Key  Pc# Cp# Status      Device Type Piece Name
------- ------- --- --- ----------- ----------- ----------
145919  145913  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set9_piece1_copy1_20110425_09mal5t9_1_1
145920  145914  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set8_piece1_copy1_20110425_08mal5t9_1_1
145921  145915  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set11_piece1_copy1_20110425_0bmal6d9_1_1
145922  145916  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set7_piece1_copy1_20110425_07mal5t9_1_1
145923  145917  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set10_piece1_copy1_20110425_0amal6br_1_1
deleted backup piece
backup piece handle=backup_CRTRNG_3679252776_set9_piece1_copy1_20110425_09mal5t9_1_1 recid=7 stamp=749377449
deleted backup piece
backup piece handle=backup_CRTRNG_3679252776_set8_piece1_copy1_20110425_08mal5t9_1_1 recid=8 stamp=749377449
deleted backup piece
backup piece handle=backup_CRTRNG_3679252776_set11_piece1_copy1_20110425_0bmal6d9_1_1 recid=9 stamp=749377962
deleted backup piece
backup piece handle=backup_CRTRNG_3679252776_set7_piece1_copy1_20110425_07mal5t9_1_1 recid=10 stamp=749377449
deleted backup piece
backup piece handle=backup_CRTRNG_3679252776_set10_piece1_copy1_20110425_0amal6br_1_1 recid=11 stamp=749377916
Deleted 5 objects
RMAN> list backup summary;
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
147274  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147275  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147276  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147277  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147278  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147498  B  F  A SBT_TAPE    29-APR-11       1       1       NO         NOEXPIRE
RMAN>

Hope it helps

SRI

In this article, we will discuss how to install OEM grid control 10.2.0.1 on Linux 5.4(32 bit).

Download the required software from the location : Download Software
Download the installation Document from the location : Download Installation Document

If you are planning to install OEM grid control in a vmware linux machine, Please follow the article VMware Server - Linux installation  and complete the linux machine creation. You can omit this point if you are directly provided with linux machine with OS linux 5.4.

Prepare the linux machine ( Linux 5.4 ) for the OEM grid control 10201 installation. Please use the article  Prepare Linux virtual machine for OEM Grid Control Installation. Though this is to prepare the linux machine for 11gR2 database, it holds good for OEM 10201 installation also. You can also refer the document mentioned above to prepare the linux machine for OEM grid control installation.

There are some identified Common Installation Errors while installing OEM 10201 on Linux 5.4. Please follow the article OEM Gridcontrol 10201 Installation Errors On Linux 5.4 to correct all the issues.

Follow the video to complete the installation of OEM grid control 10.2.0.1 on Linux 5.4.

Video will be uploaded very soon. <video place holder>

Hope It Helps
SRI

In this article I will explain what is a node manager , how do we configure a node manager in weblogic server, how do we start node manager and how do we use node manager to administer managed servers already created.

Node Manager : A node manager is a separate utility which runs on machines which are hosting weblogic. We can use node manager to remotely startup weblogic servers.

Review my previous articles on weblogic server.

Domain creation and deletion in Weblogic Server

Configuring Managed Servers In Weblogic Server 10.3.4

Creating And Configuring Machines in Weblogic Server 10.3.4

Thanks

SRI

In this article, we will discuss how to create and configure machines in weblogic server 10.3.4. We can do this in three different ways

1. Domain Configuration Wizard
2. Administration Console
3. Command Line ( WLST )

A managed server is a computer  that hosts the Oracle Weblogic server instances. After creating the machines, we will assign managed servers to these machines.

Following video demo gives you the basics of creating and configuring machines.




Review the previous articles if you want to know how to create managed servers and configure them using administration server.

Domain creation and deletion in Weblogic Server

Configuring Managed Servers In Weblogic Server 10.3.4

Thanks

SRI