Configure Recovery Catalog - Rman

Pre-requisite

> we can use same instance for catalog db. my recommendation is separate instance is better.
> create separate schema and grant 'recovery_catalog_owner' privilege
> configure password file and listener file

1. configure recovery catalog.

$> export oracle_sid=rmandb
$> rman catalog rmanc/rmanc
...
...

rman> create catalog tablespace tbsnam;
...
rman> exit;

2. Register target db with catalog db

$> rman catalog rmanc/rmanc target sys@db1
target database password:
connected to target.....
.....

rman> register database;
database register in recovery catalog...
....
...
rman> exit

3. check and confirm the db register with catalog db

login rman schema

$ sqlplus rmanc/rmanc
$ select * from db;

you can see the target db id and incarnation information..

now target db was configured with catalog db.. next we have to configure rman for target db...

bye..

ORA-00704 bootstrap process failure

while i create fresh database using 10.2.0. i faced bootstrap failure. i was scared. most of them asked me to contact oracle. but again i tried with upgrade option and run catalog.sql and catproc.sql script, the problem was solved, now the db is working fine. But still i am not able to find the root cause why it was happen. If any one know please share the details..

ORA-00704: bootstrap process failure
ORA-39700: database must be opened with upgrade option

platform : Redhat 4

error in invoking target 'all_no_orcl ihsodbc' of makefile

I'm installing Oracle 10.2.0 on RHEL 4 ES. The Linux runs on VMWare 1.0.5. The Virtual Machine has 800 Mb of RAM, and 12Gb of hard drive space (/dev/sda).When I was running the Oracle Universal Installer, I got the following error message:

error in invoking target 'all_no_orcl ihsodbc' of makefile '/rman/oracle/product/10.2.0/rdbms/lib/ins_rdbms.mk

I was wounder what happen actually. i investigate the error log.. two library files are missing, so OUI not able to link files..

'/rman/oracle/product/10.2.0/rdbms/lib/ins_rdbms.mk'.See '/u01/app/oracle/oraInventory/logs/installActions2009-11-14_06-41-37PM.log'

solution

Install the following rpm

compat-libstdc++-296-2.96-132.7.2.i386.rpm
compat-libstdc++-33-3.2.3-47.3.i386.rpm

note: check all mandatory rpm before install..

Oracle 10g upgradation Outline

Platform: Sun Solaris 5.8
Architecture: Sun Sparc 64bit
Oracle Version: 10.1.0.2.0 64bit
Upgradation path: 10.1.0.2.0 --> 10.2.0.1.0 --> 10.2.0.4.0
How to get RDBMS: Download from OTN / Metalink

Upgradation Steps:

1. Shutdown oracle db [shutdown immediate]

2. Take complete backup [cold backup]

3. Stop all services

Listener, OEM console, Cronjobs

4. Backup oracle home and inventory files

a. $ tar -cvf 10102.tar $OH/10102

b. $ tar –cvf Inventory.tar $OH/oraInventory

c. Save it in backup location

5. Install new Oracle home 10.2.0.1 in separate folder

6. Startup database with previous home [10.1.0.2.0]

a. Export ORACLE_HOME=/u01/app/oracle/product/10.1.0

b. Startup normal;

7. Check the compatibility

a. sql> @/u01/app/oracle/product/10.2.0/rdbms/admin/utlu102i.sql

b. Examine spool file and correct if any errors.

8. Startup db with new home 10.2.0.1.0 in upgrade mode.

a. $ export ORACCLE_HOME=/u01/app/oracle/product/10.2.0

b. Sql> Startup upgrade; (copy spfile from pervious to new home)

9. Upgrade the database

a. Sql> @/u01/app/oracle/product/10.2.0/rdbms/admin/catupgrade.sql

b. Verify the spool file and correct the errors if any. c. Bounce the database.

10. Examine and compile invalid object

a. Sql> @/u01/app/oracle/product/10.2.0/rdbms/admin/utlrp.sql

b. Examine spool file and re-compaile if any invalid objects.

11. Database has upgraded to 10.2.0.1.0 and now want to apply the patchset 10.2.0.4.0 on top of 10.2.0.1.0.

12. Omit step 5 and 6. Repeat remaining steps. Before install 10.2.0.4 patchset backup the following files " utlu102i.sql and catupgrade.sql "

Enable Archive Log in 10g

Oracle version : 10.1.0.2.0 (64b)

Platform : Sun Sparc 5.8 (64b)

Server : Solaris Fire v20

Storage : SAN

before enabling archivelog mode take complete backup after database shutdown (cold backup).

1. backup spfile : create pfile='/path/pfile.ora' from spfile;

2. enable archive destination

sql> alter system set log_archive_dest_1='Locatin=\path' scope=spfile;

sql> shutdown immediate;

3. perform complete backup

5. connect exclusive mode

$sqlplus "/as sysdba"

sql> startup mount;

sql> alter database archivelog;

sql> alter database open;

sql> archive log list;

Database log mode Archive Mode

Automatic archival Enabled
Archive destination \path\archive
Oldest online log sequence 5
Next log sequence to archive 7

Current log sequence 7

6. after enable archive, better to another complete backup

sql> create spfile from pfile='/path/pfile.ora'

sql> shutdown immediate;

$ cold backup

sql> startup

Note :

log_archive_format must be in this format '%t_%s_%r

%t - thread number

%s - sequence number

%r - resetlog id

Error :

SQL> startup pfile=D:\oracle\admin\ORCL\pfile\initORCL.ora

ORA-32006: LOG_ARCHIVE_START initialization parameter has been deprecated

SQL> startup pfile=D:\oracle\admin\ORCL\pfile\initORCL.ora
ORA-32006: LOG_ARCHIVE_START initialization parameter has been deprecated
ORA-19905: log_archive_format must contain %s, %t and %r

Metalink Doc:

Doc ID: 274302.1

Doc ID: 371139.1

Doc ID: 69739.1

Doc ID: 420371.1

Good Luck!