Moving Oracle Database between AWS instance.

-
When moving an Oracle database between two Amazon ec2 instances, we can easily accomplish it without backup/restore or Rman duplication as below.

Setup - Oracle 11.2.0.1 Running on Amazone ec2 Linux 6.4

Requirment - Moving above oracle database from one Amazone ec2 instance (A) to another (B).

Restrications - Need to Shutdown the database on source instance. (A)

Step 1.

In source ec2 instance,

Take control file create statement to trace using below command,

 alter database backup controlfile to trace;

Create pfile from spfile.

 create pfile from spfile

Step 2.

In source ec2 instance,

Shutdown the oralce database. (In order put all data files on consistent state)

Identify the volumes (EBS) which are storing the data files and take snapshot of each of the volume.
(If you are dealing with large volumes, take a full AMI (Machine Image) prior to taking volume snapshots. Then after db shutdown take the volume snapshot. This will reduce the snapshot time)

Step 3.

In Amazone ec2 management,

Create new volumes from the snapshots, Mount this new volumes to instance which db need to be moved.
(Need to have same version of oracle installed on this second server)

If possible use the same mount point paths as it will reduce the changes in db creation. (eg - paths to data files)

Step 4.

In destination instance,

Go through the controlfile dumped to trace, (show parameter user_dump_dest;) and do required changes.
e.g,
*Change datafile paths to reflect the correct location in new instance.
*If redo log location is unchanged and the redo files were mounted from snap shots from source  instance, remove those files from os level. (rm -rf)
*Remove "recover database" statements and "open database" statements..
*Changes 'NORESETLOGS' to 'RESETLOGS'.

Step 5.

 Run the above edited control file create statement so the new db will be created.

Step 6.

 Startup the database.




Comments

  1. UnknownJune 16, 2017 at 12:50 AM

    I really appreciate information shared above. It’s of great help to us. If someone wants to learn (ILT) instructor lead live training on AWS (Amazon Web Services) MaxMunus Offer World Class AWS Certification level classroom training in Bangalore, we have industry expert trainers. We provide Training Material and Software Support. MaxMunus has successfully conducted 1, 00,000 + trainings in India, USA, UK, Australia, Switzerland, Qatar, Saudi Arabia, Bangladesh, Bahrain and UAE etc.
    Enroll for the live & interactive classroom training
    Arvind
    MaxMunus
    E-mail: arvind.sharma@maxmunus.com
    Skype id: arvind.sharma901
    Ph :( 0) 9019891304 / 080 - 41103383

    ReplyDelete

Post a Comment

Popular posts from this blog

ORA-16433: The database or pluggable database must be opened in read/write

-
Image
ORA-16433 is an error returned when a database cannot be opened. This can be a result of multiple conditions including, The inconsistency of the database Physical corruption Loss of dependent files or access issues etc.. More often than not the solution is to recover from available backups, but there can be situations where backups are not available, specially on UAT or Test setups. Although not the ideal scenario, in this type of situation you might want to open the databases even with inconsistency.  In Comes --> _ALLOW_RESETLOGS_CORRUPTION First, if you are in a position to use _ALLOW_RESETLOGS_CORRUPTION=TRUE, that means it has to be a critical moment, and when you come across more ora- errors while you are trying to reopen the databsae, that can be annoying. Note - _ALLOW_RESETLOGS_CORRUPTION=TRUE must only be used after Oracle support confirmation as a last resort. Also make sure to take cold backup before proceeding. Basic steps to be followed to resolve ORA 16433 after
Read more

Oracle Multitenant - Create new service for PDB using DBMS_SERVICE

-
Image
When an Oracle PDB is created it starts up a default service with the PDB name. For direct connections to    PDB this service can be used. But there are situations where new service name is required in PDB level, common example is after a PDB restoration/clone, in order to enable application connections without changes in connection string. Setting service_names parameter in PDB level is not possible hence it is not an option in multitenant setup. How to create a new PDB service on Oracle 12C Check the current services, here only the default service is running, SQL> show pdbs; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 3 NFACTORPDB READ WRITE NO SQL> select service_id, name, pdb from dba_Services; SERVICE_ID NAME PDB ---------- ---------------------------------------- ---------- 7 nfactorpdb NFACTORPDB SQL> Create
Read more

Wait for unread message on broadcast channel - Blocking Sessions

-
Image
What is Wait for unread message on broadcast channel wait event? Wait for unread message on broadcast channel is a wait event where source destination communication is involved and the database is waiting for a reply from remote party. Mostly this wait is seen related to data pump export (expdp) or import (impdp) operations. Although categorized in idle wait class "Wait for unread message on broadcast channel" can become the blocking session for some other sessions. Common causes for stuck sessions waiting on this wait event includes, Broken databases links, where remote database is not responding. Abnormally killed remote processes causing the sessions to wait. When a session is waiting on "Wait for unread message on broadcast channel" it can become a blocking session for dependent sessions. Most probably these sessions will be waiting on "library cache pin" or related concurrency wait events. The blocking_session column of (g)v$session view
Read more