Restore RMAN backup
=================

If you are new to RMAN, you should first understand how to backup oracle database using RMAN.

RMAN> SET DBID 12345; 


RMAN> STARTUP NOMOUNT;  or  RMAN> STARTUP FORCE MOUNT;

RMAN> RESTORE CONTROLFILE FROM "/backup/rman/ctl_c-12345-20141003-03";


RMAN> RESTORE CONTROLFILE;


RMAN> RESTORE DATABASE; 


RMAN> RECOVER DATABASE; 

RMAN> ALTER DATABASE OPEN RESETLOGS;

Problem

Oracle Database recovery using RMAN fails with RMAN-06054: media recovery requesting unknown archived log 

https://www.veritas.com/support/en_US/article.100022346

Error Message

archived log file name=/opt/app/oracle/flash_recovery_area/ETAUTOIT/archivelog/2014_04_18/o1_mf_1_20725_9o0qrvh2_.arc thread=1 sequence=20725
channel default: deleting archived log(s)
archived log file name=/opt/app/oracle/flash_recovery_area/ETAUTOIT/archivelog/2014_04_18/o1_mf_1_20725_9o0qrvh2_.arc RECID=20582 STAMP=845172555
unable to find archived log
archived log thread=1 sequence=20726
released channel: c0
released channel: c1
released channel: c2
released channel: c3
released channel: c4
released channel: c5
released channel: c6
released channel: c7
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/18/2014 02:10:32
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 20726 and starting SCN of 3101263306

Cause

Oracle does not stop recovery at the last available archive log in the database backupsets as per the restored control file.

Solution

Oracle does not stop recovery at the last available archive log in the database backupsets as per the restored control file. It keeps on requesting for "next available archive log sequence number (20726)". In fact, there is no log sequence 20726 recorded in the restored control file. Hence the database is already consistent after applying log sequence 20725 whose existence was already recorded in the target database control file and that is why the recovery is successful. Now try to open the database with below command and It should complete successfully.

sqlplus '/ as sysdba'
sql>alter database open resetlogs;

Once you execute above command, You should get the "Database altered" message which indicates that the database opened successfully.

Enable and Disable Archive Log Mode 10g/11g

Enable Archive Log Mode
============================

http://www.oracledistilled.com/oracle-database/backup-and-recovery/enabledisable-archive-log-mode-10g11g/

https://logic.edchen.org/how-to-set-use_db_recovery_file_dest/

[oracle@ora1 ~]$ sqlplus / as sysdba


SQL> archive log list
Database log mode              No Archive Mode
Automatic archival             Disabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     25
Current log sequence           27

-----------------------------------------------------------------------------------------------

SQL> show parameter recovery_file_dest

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest                string      /u01/app/oracle/flash_recovery
                                                 _area
db_recovery_file_dest_size           big integer 3852M
SQL>

--------------------------------------------------------------------------------------------------

SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 80G SCOPE=BOTH;

SQL>  alter system set db_recovery_file_dest='/u04/fast_recovery_area/' scope=both;

SQL>  alter system set log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST' scope=both;

SQL> archive log list;
Database log mode              No Archive Mode
Automatic archival             Disabled
Archive destination            DB_RECOVERY_FILE_DEST
Oldest online log sequence     25
Current log sequence           27


---------------------------------------------------------------------------------------------------

SQL> shutdown immediate
.

SQL> startup mount

----------------------------------------------------------------------------------------------

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            DB_RECOVERY_FILE_DEST
Oldest online log sequence     25
Next log sequence to archive   27
Current log sequence           27


-----------------------------------------------------------------------------------------------

SQL> alter system switch logfile;

System altered.

SQL> host
[oracle@ora1 ~]$ ls /u02/app/oracle/oradata/orcl/arch
1_27_711369564.dbf
[oracle@ora1 ~]$ exit
exit

SQL>

--------------END-----------------------


Disable Archive Log Mode
=========================

[oracle@ora1 ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Thu Apr 8 12:54:05 2010

Copyright (c) 1982, 2009, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /u02/app/oracle/oradata/orcl/arch
Oldest online log sequence     26
Next log sequence to archive   28
Current log sequence           28
SQL>

----------------------------------------------------------------------------------------------

SQL> shutdown immediate

SQL> startup mount

--------------------------------------------------------------------------------------------

SQL> alter database noarchivelog;

Database altered.

SQL> alter database open;

Database altered.

SQL> archive log list;
Database log mode              No Archive Mode
Automatic archival             Disabled
Archive destination            DB_RECOVERY_FILE_DEST
Oldest online log sequence     26
Current log sequence           28
SQL>

Configure RMAN
=================

prerequisite : Enable Archive Logs.  Click here to see

1. CREATE TABLESAPCE FOR CATELOG

CREATE TABLESPACE TB_RMAN
DATAFILE '/rman/app/orarman/oradata/rman/rman01.dbf'
SIZE 100M AUTOEXTEND ON;



2. CREATE USER RMAN...

CREATE USER RMANPRODDB IDENTIFIED BY rmanproddb DEFAULT TABLESPACE TB_RMAN
TEMPORARY TABLESPACE TEMP
QUOTA UNLIMITED ON TB_RMAN;


SQL> grant RECOVERY_CATALOG_OWNER to rman;

Grant succeeded.


SQL> grant connect, resource to rman;

Grant succeeded.



3. CREATE THE CATALOG

[root@ebizstb Desktop]# su - oraebiz
[oraebiz@ebizstb ~]$ tnsping rman

TNS Ping Utility for Linux: Version 11.2.0.4.0 - Production on 10-MAR-2017 15:48:35

Copyright (c) 1997, 2013, Oracle.  All rights reserved.

Used parameter files:
/ebiz/ebizdb/tech_st/11.2.0/network/admin/PRODDB_ebiz/sqlnet_ifile.ora


Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = stb.expolanka.com)(PORT = 1525))) (CONNECT_DATA = (SERVICE_NAME = rman.expolanka.com)))
OK (40 msec)

[oraebiz@ebizstb ~]$ rman catalog rmanproddb/rmanproddb@rman

Recovery Manager: Release 11.2.0.4.0 - Production on Fri Mar 10 15:51:33 2017

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to recovery catalog database

RMAN> create catalog;     

recovery catalog created

RMAN> exit


Recovery Manager complete.
[oraebiz@ebizstb ~]$ rman target sys/erporacle321@proddb catalog rmanproddb/rmanproddb@rman

Recovery Manager: Release 11.2.0.4.0 - Production on Fri Mar 10 15:53:23 2017

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: PRODDB (DBID=26011804)
connected to recovery catalog database

RMAN> register database;

database registered in recovery catalog
starting full resync of recovery catalog
full resync complete

5) Configuration of RMAN Parameters.

RMAN configuration parameters for database with db_unique_name VISDB are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/data/FRA_visdb/VISDB/rman_backup/full_%u_%s_%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/vis/visdb/tech_st/11.2.0/dbs/snapcf_VISDB.f'; # default

6) RMAN backup script

[root@vis Desktop]# cat /PRODBACKUP/rman/runrman.sh

dt=`date +%d%m%y`

logfile="Rman"$dt".log"

echo "Start RMAN Backup of Vis8070 Instance on `date` " 2>&1  >> /PRODBACKUP/rman/log/$logfile

su - oravis -c "rman target sys/erporacle321 catalog rmanvis/r@rman << EOF

RESYNC CATALOG;

#RECOVER COPY OF DATABASE WITH TAG 'OSS';

#BACKUP DEVICE TYPE DISK INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'OSS' DATABASE;

#BACKUP DEVICE TYPE DISK ARCHIVELOG ALL;

#BACKUP AS BACKUPSET DATABASE PLUS ARCHIVELOG;

#DELETE NOPROMPT OBSOLETE DEVICE TYPE DISK;

BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 0 DATABASE;

#BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 0 WITH TAG 'FULL_BACKUP' DATABASE;

DELETE NOPROMPT EXPIRED BACKUP;

DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;

DELETE NOPROMPT OBSOLETE REDUNDANCY 1;

#DELETE NOPROMPT OBSOLETE;

#DELETE NOPROMPT ARCHIVELOG ALL;

EXIT;

EOF" 2>&1 >> /PRODBACKUP/rman/log/$logfile

echo "Complete RMAN Backup of Vis8070 on `date` " 2>&1  >> /PRODBACKUP/rman/log/$logfile

#sh /PRODBACKUP/rman/dump/dump.sh  2>&1 >> /PRODBACKUP/rman/log/$logfile

echo "End Backing up recovery catalog on `date` " 2>&1  >> /PRODBACKUP/rman/log/$logfile

cat /PRODBACKUP/rman/log/$logfile  2>&1 | mail -s "Vis8070 - Daily Online Backup" pramuditha@expolanka.com

Commands to check the Linux Version, Release name & Kernel version.

uname -a (Print all Information)

uname -r (Print the kernel name)

cat /proc/version

cat /etc/issue

cat /etc/redhat-release

lsb_release –a

tail /etc/redhat-release

Maintaining RMAN Backups

Whatever backups you take using RMAN, it store all the backup information in the database Control File and also in the Recovery Catalog if you are using RMAN with Catalog.

To maintain the information in up-to-date state we might need the following commands

To register manual backups

Suppose we have taken a backup of a particular datafile outside of RMAN through O/s commands. Whatever backup you take outside of RMAN, RMAN will not know about it and it will not consider this backup exist until we register the backup in RMAN catalog.

For example suppose we have taken a backup of users01.dbf datafile on /u02/oracle/d2/users01.dbf' directory and now we want to register this backup in RMAN repository

To register give the following command

RMAN> catalog datafilecopy '/u02/oracle/d2/users01.dbf';

 

Once you issue the above command then RMAN will enter the information about this backup in the catalog and will recover from it in future recovery operation if needed.

Crosscheck Command in RMAN

Crosscheck is a very useful command in RMAN which automatically checks all the backups whose information is store in the RMAN repository and whether they are available on the disk or not.

If a corresponding backup is not available on the disk then Crosscheck command marks the backup as Expired otherwise it marks it as Available

To check status of all backupsets we can give the following command

RMAN> crosscheck backup;

To check status of all image copies we can give the following command

RMAN> crosscheck copy;

To know the status of Expired and Available backupsets give the following command

RMAN> list expired backup;

To know the status unavailable image copy copy give the following command

RMAN> list expired copy;

To delete the expired backup sets we can give the following command

RMAN> delete expired backup

To delete the expired image copies we can give the following command

RMAN> delete expired copy;

R12.2.x ADOP : [ERROR] ETCC not run in the database node DBHOSTNAME

R12.2.x ADOP : [ERROR] ETCC not run in the database node DBHOSTNAME

[applvis@vis apps]$ adop phase=prepare

Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:

Validating credentials.

Validating system setup.

    Node registry is valid.

    [ERROR]     ETCC not run in the database node vis

                The EBS Technology Codelevel Checker needs to be run on the database node.

                It is available as Patch 17537119.

    

    Encountered the above errors when performing database validations.

    Resolve the above errors and restart adop.

[STATEMENT] Please run adopscanlog utility, using the command

"adopscanlog -latest=yes"

to get the list of the log files along with snippet of the error message corresponding to each log file.

adop exiting with status = 1 (Fail)

[root@vis Desktop]# su - oravis

[oravis@vis ~]$ cd $ORACLE_HOME

[oravis@vis 11.2.0]$ mkdir -p etcc

[oravis@vis 11.2.0]$ mv p17537119_R12_GENERIC.zip etcc/

[oravis@vis 11.2.0]$ unzip etcc/p17537119_R12_GENERIC.zip 

[oravis@vis 11.2.0]$  sh etcc/checkDBpatch.sh

Now type

[applvis@vis apps]$ adop phase=prepare

adnodemgrctl.sh: check the logfile /u01/vis/visapps/apps/fs2/inst/apps/VISDB_vis/logs/appl/admin/log/adnodemgrctl.txt for more information ...


The prepare phase completed successfully.


adop exiting with status = 0 (Success)

Oracle EBS 12.2 Cloning Document

Oracle EBS 12.2 Cloning Document

Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1)