RMAN DUPLICATE DATABASE WITHOUT CONNECTING TO TARGET DATABASE

Have come across a requirement to clone a database using RMAN from from PROD to TEST in the same server

The only way you can clone a database from PROD to TEST (Different SID) in the same server is using RMAN duplicate command.

Usually RMAN duplicate command uses auxilary database and connect to target(PROD) database while creating the TEST.

We have a new feature in 11GR2, Which allows to clone using RMAN duplicate command without connecting to source PROD database.

It will only access the backup piecies and clones database.

This method works in cloning the database in the same server or different server

Source : PROD
Target : TEST

Steps:

1) Copy the Oracle home from source PROD to target TEST and create the parameter file for TEST database

2) Copy the backupsets to TEST server (If the clone is in the same server, This step is not required)

3)If you are cloning the database in the same server as PROD,Modify the below two parameters in the TEST (target instance),

This step is very importent step to mention the different directory structure for TEST datafiles if you are restoring on the same server as PROD.

db_file_name_convert=('/oradata/PROD' '/oradata/TEST')
log_file_name_convert=('/oradata/PROD' '/oradata/TEST')

4) Start the TEST Instance (This is called as auxilarary database)
$ sqlplus "/ as sysdba"
SQL> startup nomount;

5) Run the RMAN duplicate command from
rman auxiliary /
RMAN> DUPLICATE DATABASE TO NEWDB BACKUP LOCATION '/RMAN_Backup_Location/';

Fusion Applications Installation FAQ - I

=> Why Oracle Fusion Applications?

Designed from the ground up using the latest technology advances and incorporating the best practices gathered from Oracle's thousands of customers, Oracle Fusion Applications are 100 percent open-standards-based business applications that set a new standard for the way we innovate, work, and adopt technology. Built on a set of unique design principles, only Oracle Fusion Applications set a new standard for business.

Oracle Fusion Applications are a complete, standards-based platform.
Oracle Fusion Applications also provide a flexible approach to adoption and deployment.
Oracle Fusion Applications application and process leadership give you the “best-of-the-best” combination.

=> What ar ethe different version of the Fusion Applications Available now?

The base (First) Version of Fusion Applications is
Oracle Fusion Applications 11g (11.1.1.5.1)  -
Oracle Fusion Applications 11g (11.1.2.0.0)  - RUP1
Oracle Fusion Applications 11g (11.1.3.0.0)  - RUP2
Oracle Fusion Applications 11g (11.1.4.0.0)  - RUP3 (Latest)
=> You can directly install any version or upgrade to that version, i.e IN order to install RUP3, We dont require the base version to be installed first.
 Directly RUP3 can downloaded and installed.

=> How big is it?
The software size is approx 50GB

=> What are the different components of Fusion Applications ?

Fusion Applications is combination of two families

1)IDM Family
2)Fusion Applications Family

1) Identity Management (IDM) for Fusion Applications involves installation of the following:

• Oracle Database 11g R2
• JDK (JRockit 64-bit)
• Oracle WebLogic Server
• Oracle Fusion Middleware Web Tier (Oracle HTTP Server)
• Oracle Fusion Middleware SOA Suite
• Oracle Identity Management (OID and OVD)
• Oracle Identity and Access Management (OIM and OAM)
• Oracle Access Manager WebGate

2) Fusion Applications installation of the following:

• Oracle Database 11g R2
• JDK (JRockit 64-bit)
• Oracle WebLogic Server
• Oracle Fusion Middleware Web Tier (Oracle HTTP Server)
• All the modules of Fusion Applications deployed as Weblogic Domains
  - The numbers of managed/applications servers depends on the number of modules chosen to install, This number can go as high as 60+

...watch this space for more updates on Fusion Applications

Fusion Applications (FA) Installation

Have completed Fusion Applications Installations, 

Watch this space for more information on Fusion Applicatins Installation and Administration........

Below are the logn screens of Fusion Applications

Oracle EM 12C Grid Installation

Have recently Installed Oracle EM 12C Grid on Linux x86_64.

EM 12C Grid contains weblogic and JDK , It is installed automatically along with the EM (If you have not already installed weblogic separetely)

Installing Database 11G (11GR1 or 11GR2) is a pre-requisite for installing EM 12c.

Modify the recomended parameters (these will shown while installing) for better performence of EM.

Below are the high level steps:

1) Install Oracle database 11G ( Have installed 11GR2)
2) Remove the EM schema components (SYSMAN) from the database, Using the below command.

$<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop -SYS_PWD <sys pasword> -SYSMAN_PWD <sysman password>
 3) Install EM 12c by running runinstaller.

Login to EM 12c :

https://exmaple.oracle:7801/em
Login using User ID sysman and password chosen during the install

https://exmaple.oracle.com:7102/console
Login using User ID sysman and password chosen during the install

How To start EM Grid Control follow the steps below:

1. Start the listener
2. Start the database
3. Start OMS11g using the command <EM OMS Oracle Home>/bin/emctl.sh start oms -all
5. Go to the WLS Console and start the EM Domain (if not already started)

Find the below step by step screen shots of EM Installation ....

Upgrade Oracle 11.1.0.7 database to 11.2.0.3 with EBS R12

Upgrade Oracle 11.1.0.7 database to 11.2.0.3 with EBS R12

The below provides high level steps for the upgrade of the EBS database from 11.1.0.7 to 11.2.0.3
The main document to be followed for this upgrade is "Interoperability Notes EBS R12 with Database 11gR2 [ID 1058763.1] "

STEPS:
=====
1)Install 11.2.0.3 software in a different oracle home
If the existing database oracle home is /u01/TEST/db/tech_st/11.1.0, You can create directory /u01/TEST/db/tech_st/11.2.0 and install it on this location.

2)Drop SYS.ENABLED$INDEXES (conditional)
If the SYS.ENABLED$INDEXES table exists, use SQL*Plus to connect to the database as SYSDBA and running the following command to drop it:
SQL> drop table sys.enabled$indexes;

3) Run the Pre-Upgrade Information Tool by executing the utlu112i.sql script:
SQL> SPOOL upgrade.log
SQL> @utlu112i.sql

4)Shutdown Apps & DB services

4)Set the environment variables to the new home 11.2.0.3 i.e /u01/TEST/db/tech_st/11.2.0
 a.The ORACLE_BASE environment variable must be set accordingly.
 b.The ORACLE_HOME environment variable points to the new 11.2.0 Oracle home.
 c.The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new perl executable is located (usually $ORACLE_HOME/perl/bin).
 d.The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib.
 e.The PERL5LIB environment variable points to the directories where the new perl libraries are located (usually $ORACLE_HOME/perl/lib/[perl version] and $ORACLE_HOME/perl/lib/site_perl/[perl version])

5)Create nls/data/9idata directory
On the database server node, as the owner of the Oracle RDBMS file system and database instance, run the $ORACLE_HOME/nls/data/old/cr9idata.pl script to create the $ORACLE_HOME/nls/data/9idata directory.
After creating the directory, make sure that the ORA_NLS10 environment variable is set to the full path of the 9idata directory whenever you enable the 11g Oracle home.

6)Apply additional 11.2.0.3 RDBMS patches 
Apply the following patches on the NEW ORACLE_HOME:
For all UNIX/Linux platforms:
4247037
9858539
12942119
12960302
13004894

7) Copy initSID.ora from old oracle_home to new oracle_home 11.2.0.3
 set at the initSID.ora
 compatible = '11.2.0'

8)Upgrade the database instance
sqlplus "/ as sysdba"
SQL> STARTUP UPGRADE
Run the catupgrd.sql script, this script is doing the UPGRADE
SQL> spool upgrade.log
SQL>@$ORACLE_HOME/rdbms/upgrade/catupgrd.sql
SQL>spool off
SQL> STARTUP
Run utlu112s.sql to display the results of the upgrade as follows:
SQL> @utlu112s.sql

9)Copy $AD_TOP/patch/115/sql/adctxprv.sql from the administration server node to the database server node.
 Use SQL*Plus to connect to the database as APPS and run the script using the following command:
 $ sqlplus apps/[APPS password] @adctxprv.sql [SYSTEM password] CTXSYS

10) Set CTXSYS parameter
 Use SQL*Plus to connect to the database as SYSDBA and run the following command:
 $ sqlplus "/ as sysdba"
 SQL> exec ctxsys.ctx_adm.set_parameter('file_access_role', 'public');

11) Copy the listner & tnsnames.ora from old oracle home to new oracle home and modify the oracle home & all the refrences of old entries to new oracl home

12)Copy the old appsutil from 11.1.0.7 ORACLE_HOME to the new ORACLE_HOME. and change in all the files inside appsutil all the references from 11.1.0 to 11.2.0

13)Copy the $ORACLE_11.1.0_HOME/SID_host.env to $ORACLE_11.2_HOME/SID_host.env, make the necessary changes to point the new 11.2.0 home and source the environment.

14)Copy $APPL_TOP/admin/adstats.sql from the apps tier to the database home and execute it in database restrict mode.

15)Run adadmin - recreate grants and synonyms and compile apps schema

16)Upgrade completed - Start the Applications: