Creating DR standby from RAC to single NODE

OS and Database versions Primary:
node1:- OEL 5.7
node2:- OEL 5.7
inst1:- prod1 Oracle 11.2.0.3
inst2:- prod2 Oracle 11.2.0.3
Standby:
OEL 5.7
Oracle 11.2.0.3
NOTE:- Creating Standby on Single node.
My scenario:
============
node1:- linuxdb1
node2:- linuxdb2
inst1:- prod1
inst2:- prod2
Point1:- We have 2 node RAC with ASM disk and database is okay. Now i want to make DR on single node with ASM disk created already.
Point2:- grid and oracle users are on RAC prod database & also same grid and oracle users on SINGLE node DR
Point3:- Took RMAN backup from prod database ( 2 node RAC ) and copied to DR as shown below:
RMAN>backup device type disk format '/u02/stby/%U' database plus archivelog;
RMAN>backup device type disk format '/u02/stby/%U' current controlfile for standby;
scp -rp /u02/stby/* [email protected]:/u02/stby/
Point4:- Now when i run below command on DR ( oracle@linuxdr2 )
[oracle@linuxdr2 stby]$ rman target sys/pwd@prod1 auxiliary /
Recovery Manager: Release 11.2.0.3.0 - Production on Sun Mar 10 13:18:20 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: PROD (DBID=220323208)
connected to auxiliary database: PROD (not mounted)
RMAN> duplicate target database for standby;
Starting Duplicate Db at 10-MAR-13
using target database control file instead of recovery catalog
configuration for DISK channel 2 is ignored
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=1142 device type=DISK
contents of Memory Script:
restore clone standby controlfile;
executing Memory Script
Starting restore at 10-MAR-13
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /u02/stby/33o464m6_1_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/10/2013 13:19:22
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred
Can you please help me to resolve the issue.
Thanks,
Vikhar

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/10/2013 13:19:22
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred Any errors in alert log file?
Have you tried once again ?
Why cant you go for RMAN duplicate from active database, If you have any concerns then enable trace of RMAN and share the information
rman target / log=/u01/test/rman_log.txt trace=/u01/test/rmantrace.log

Similar Messages

ORA-24544 When Creating a Standby From RAC One Node

I have a RAC One Node database running on node A and am attempting to create a Data Guard standby on node B using the following RMAN command -
duplicate target database for standby from active database
Error returned is -
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/10/2015 11:11:06
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-04014: startup failed: ORA-24544: Oracle RAC One Node instance is already running.
Can anyone advise ?
Thanks in advance

Hi,
ORA-24544: Oracle RAC One Node instance is already running.
Cause: An instance startup failed because an instance of the Oracle RAC One Node database was already running on one of the cluster nodes.
Action: In Oracle RAC One Node, avoid any attempt to start a second instance by any means while the instance is already running.
I have never used One Node RAC, but it looks like RMAN trying to start an offline instance of current One Node RAC on Node B.
HTH,
Pradeep

Best way to move from RAC to single node database.

Hi,
One of my customer is having RAC setup with EBS R12. Due to some other issues, customer is looking to switch back to Standalone database. What could be the best approach for this?
I am thinking to perform the following approach. Could any body comment on the same?
1) create a new oracle_home on the same server.
2) Modify the cluster_database to false.
3) start the database from new oracle_home.
4) Create a new listener with same port#(off course i will stop all RAC services including listener).
Version details are :- 11gR2 on Solaris.
EBS is :- R12.
Is this approach sounds good or any better method.
Thanks in-advance.
Regards
DBA.

Hello DBA,
You can follow these steps...
a) Stop database using srvctl
srvctl stop database -d mydb
b) Remove the database entry from crs
$ srvctl remove instance -d mydb -i mydb1
$ srvctl remove instance -d mydb -i mydb2
$ srvctl remove database -d mydb
c) Start the database on first instance
SQL> startup
SQL> alter system set cluster_database=false scope=spfile;
System altered.
SQL> alter system set cluster_database_instances=1 scope=spfile;
System altered.
SQL> alter database disable thread 2;
Database altered.
d) Delete the unwanted thread and redo logfiles
e) Drop the unwanted undo tablespace
f) Create pfile from spfile
g) Remove second instance references from the pfile and start the instance
h) create spfile from pfile.
Regards,
Alex Alvarenga
SP - Brasil

RAC to Single node cloing

Hi all,
We have our production running on 2 node RAC and its in ASM cluster and AppsTier on single node
Node 1 - AppsTier
Node 2 - RAC 1
Node 3 - RAC 2
Now I would like to do a cloning for the production from RAC to Single Instance
Is there any doc or steps to be followed for the RAC to single instance cloning ??..
Regards,
Mahesh

Hi Makesh;
This topic discussed here many times, Just check below links which u can find all notes and also see general search link
CLONE-RAc to nonrac
RAC -> NON RAC ebiz clone
Re: Clone Oracle Apps 11.5.10.2 RacDB to Non-RAC DB
General search:
http://forums.oracle.com/forums/search.jspa?threadID=&q=rac+to+nonrac+clone&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Regard
Helios

RMAN backup restore from RAC to single instance ASM

Hi,
We are using oracle 11gR2 on AIX 6.1,
We need to restore RMAN backup from RAC to single instance ASM,
Im new to RAC & ASM, What will be the changes
What will be steps involved into it.
Thanks

Hello,
Refer this MOS doc *HowTo Restore RMAN Disk backups of RAC Database to Single Instance On Another Node [ID 415579.1]*
On the Single Instance ASM, you need to specify the diskgroup name for the parameters "control_files, db_create_file_dest"
Handle:      user10745179
Email:      [email protected]
Status Level:      Newbie (5)
Registered:      Feb 24, 2009
Total Posts:      168
Total Questions:      74 (52 unresolved)
Name      Devesh
Location      Mumbai If you feel that your questions have been answered, then please consider closing the threads by providing appropriate points. Please keep the forum clean !!
Regards,
Shivananda

Standby setup in 11g R2 RAC to single node

Hi,
How can we setup 11gR2 Standby Setup : Primary Database 2 Node RAC to Standalone Standby Database

ashish wrote:
Hi,
Our requirement is to create single node standby of a 11g R2 RAC 2 node database.To implement there is not much changes in functionality of dataguard, Except some new features like
1) Active dataguard
-- Where you can run MRP even in open status, so that it can be only readable.
2) password file on standby should not be created, it should copy from primary and rename it.
3) from 11g you can perform duplicate from active database without backup.
& so on.
To build a stand alone standby from 2-node RAC, MAA pdf is better one
http://www.oracle.com/technetwork/database/features/availability/maa-wp-10g-racprimaryracphysicalsta-131940.pdf
http://www.oracle.com/technetwork/database/features/availability/twp-dataguard-11gr2-1-131981.pdf
*How to create physical standby database with 11g RMAN DUPLICATE FROM ACTIVE DATABASE [ID 747250.1]*

2 Node RAC with Single Node Standby Help

Hello Everyone -
I'm preparing to set up a 2 node RAC and use a single-node standby database.
I'm a bit confused on how to set up the Standby Redo Logs on the standby to use the LGWR functionality from the RAC instances.
Should I just create a set of standby redo logs (alter database add standby logfile...) like on a single-instance environment or do I need to create standby logfile threads (alter database add standby logfile thread. . . ) one for each cooresponding thread on the RAC?
It just seems odd that 2 RAC redo threads are able to write to one standby redo logfile at the same time (or maybe each RAC redo thread picks the first available standby redo log and writes to it??)
If anyone has some advice or insight, I'd appreciate it.
Andy

Hello Andy,
Did you get answer to your question about RAC with single standby?
Could you please share with me your experience if you have done so.
Thanks
Amit

Streams Setup from RAC to Single instance

Does anyone have a document to setup streams from RAC to Non RAC. I successfully setup streams on 2 single instances but I am having issues in replicating, Streams is setup on node1 or Rac and Apply process is also setup on single node. but data is not replicating.
Appreciate any suggestions.

From Metalink Note 418755.1:
Additional Configuration for RAC Environments for a Source Database Archive Logs
The archive log threads from all instances must be available to any instance
running a capture process. This is true for both local and downstream capture.
Queue Ownership
When Streams is configured in a RAC environment, each queue table has an
"owning" instance. All queues within an individual queue table are owned by
the same instance. The Streams components (capture/propagation/apply) all
use that same owning instance to perform their work. This means that
+ a capture process is run at the owning instance of the source queue.
+ a propagation job must run at the owning instance of the queue
+ a propagation job must connect to the owning instance of the target queue.
Ownership of the queue can be configured to remain on a specific instance,
as long as that instance is available, by setting the PRIMARY _INSTANCE
and/or SECONDARY_INSTANCE parameters of DBMS_AQADM.ALTER_QUEUE_TABLE.
If the primary_instance is set to a specific instance (ie, not 0), the queue
ownership will return to the specified instance whenever the instance is up.
Capture will automatically follow the ownership of the queue.If the ownership
changes while capture is running, capture will stop on the current instance
and restart at the new owner instance.
For queues created with Oracle Database 10g Release 2, a service will be
created with the service name= schema.queue and the network name
SYS$schema.queue.global_name for that queue. If the global_name of the
database does not match the db_name.db_domain name of the database, be sure
to include the global_name as a service name in the init.ora.
For propagations created with the Oracle Database 10g Release 2 code with
the queue_to_queue parameter to TRUE, the propagation job will deliver only
to the specific queue identified. Also, the source dblink for the target
database connect descriptor must specify the correct service (global name of
the target database ) to connect to the target database. For example, the
tnsnames.ora entry for the target database should include the CONNECT_DATA
clause in the connect descriptor for the target database. This claus should
specify (CONNECT_DATA=(SERVICE_NAME='global_name of target database')).
Do NOT include a specific INSTANCE in the CONNECT_DATA clause.
For example, consider the tnsnames.ora file for a database with the global name
db.mycompany.com. Assume that the alias name for the first instance is db1 and
that the alias for the second instance is db2. The tnsnames.ora file for this
database might include the following entries:
db.mycompany.com=
(description=
(load_balance=on)
(address=(protocol=tcp)(host=node1-vip)(port=1521))
(address=(protocol=tcp)(host=node2-vip)(port=1521))
(connect_data=
(service_name=db.mycompany.com)))
db1.mycompany.com=
(description=
(address=(protocol=tcp)(host=node1-vip)(port=1521))
(connect_data=
(service_name=db.mycompany.com)
(instance_name=db1)))
db2.mycompany.com=
(description=
(address=(protocol=tcp)(host=node2-vip)(port=1521))
(connect_data=
(service_name=db.mycompany.com)
(instance_name=db2)))
Use the italicized tnsnames.ora alias in the target database link USING clause.
DBA_SERVICES lists all services for the database. GV$ACTIVE_SERVICES identifies
all active services for the database In non_RAC configurations, the service
name will typically be the global_name. However, it is possible for users to
manually create alternative services and use them in the TNS connect_data
specification . For RAC configurations, the service will appear in these views
as SYS$schema.queue.global_name.
Propagation Restart
Use the procedures START_PROPAGATION and STOP_PROPAGATION from
DBMS_PROPAGATION_ADM to enable and disable the propagation schedule.
These procedures automatically handle queue_to_queue propagation.
Example:
exec DBMS_PROPAGATION_ADM.stop_propagation('name_of_propagation'); or
exec DBMS_PROPAGATION_ADM.stop_propagation('name_of_propagation',force=>true);
exec DBMS_PROPAGATION_ADM.start_propagation('name_of_propagation');
If you use the lower level DBMS_AQADM procedures to manage the propagation schedule,
be sure to explicitly specify the destination_queue name when queue_to_queue propagation has been configured.
Example:
DBMS_AQADM.UNSCHEDULE_PROPAGATION('source_queue_name','destination',destination_queue=>'specific_queue');
DBMS_AQADM.SCHEDULE_PROPAGATION('source_queue_name','destination',destination_queue=>'specific_queue');, DBMS_AQADM.ENABLE_PROPAGATION_SCHEDULE('source_queue_name','destination',destination_queue=>'specific_queue');,
DBMS_AQADM.DISABLE_PROPAGATION_SCHEDULE('source_queue_name','destination',destination_queue=>'specific_queue');, DBMS_AQADM.ALTER_PROPAGATION_SCHEDULE('source_queue_name','destination',destination_queue=>'specific_queue');
Changing the GLOBAL_NAME of the Source Database
See the OPERATION section on Global_name below. The following are some
additional considerations when running in a RAC environment.
If the GLOBAL_NAME of the database is changed, ensure that any propagations
are dropped and recreated with the queue_to_queue parameter set to TRUE.
In addition, if the GLOBAL_NAME does not match the db_name.db_domain of the
database, include the global_name for the queue (NETWORK_NAME in DBA_QUEUES)
in the list of services for the database in the database parameter
initialization file.
Section 4. Target Site Configuration
The following recommendations apply to target databases, ie, databases in which
Streams apply is configured.
1. Privileges
Grant Explicit Privileges to APPLY_USER for the user tables
Examples:
Privileges for table level DML: INSERT/UPDATE/DELETE,
Privileges for table level DDL: CREATE (ANY) TABLE , CREATE (ANY) INDEX,
CREATE (ANY) PROCEDURE
2. Instantiation
Set Instantiation SCNs manually if not using export/import. If manually
configuring the instantiation scn for each table within the schema, use the
RECURSIVE=>TRUE option on the DBMS_STREAMS_ADM.SET_SCHEMA_INSTANTIATION_SCN
procedure
For DDL Set Instantiation SCN at next higher level(ie,SCHEMA or GLOBAL level).
3. Conflict Resolution
If updates will be performed in multiple databases for the same shared
object, be sure to configure conflict resolution. See the Streams
Replication Administrator's Guide Chapter 3 Streams Conflict Resolution,
for more detail.
To simplify conflict resolution on tables with LOB columns, create an error
handler to handle errors for the table. When registering the handler using
the DBMS_APPLY_ADM.SET_DML_HANDLER procedure, be sure to specify the
ASSEMBLE_LOBS parameter as TRUE.
In Streams Concepts manual 10.2 chapter 22: Monitoring Apply
Displaying detailed information about Apply errors.
4. Apply Process Configuration
A. Rules
If the maintain_* procedures are not suitable for your environment,
please use the ADD_RULES procedures (ADDTABLE_RULES , ADD_SCHEMA_RULES ,
ADD_GLOBAL_RULES (for DML and DDL), ADD_SUBSET_RULES (DML only).
These procedures minimize the number of steps required to configure Streams
processes. Also, it is possible to create rules for non-existent objects,
so be sure to check the spelling of each object specified in a rule carefully.
APPLY can be configured with or without a ruleset. The ADD_GLOBAL_RULES can
be used to apply all changes in the queue for the database. If no ruleset is
specified for the apply process, all changes in the queue are processed by the apply process.
A single Streams apply can process rules for multiple tables or schemas
located in a single queue that are received from a single source database .
For best performance, rules should be simple. Rules that include LIKE clauses are
not simple and will impact the performance of Streams.
To eliminate changes for particular tables or objects, specify the
include_tagged_lcr clause along with the table or object name in the
negative rule set for the Streams process. Setting this clause will
eliminate all changes, tagged or not, for the table or object.
B. Parameters
Set the following parameters after a apply process is created:
+ DISABLE_ON_ERROR=N Default: Y
If Y, then the apply process is disabled on the first unresolved error,
even if the error is not fatal.
If N, then the apply process continues regardless of unresolved errors.
+ PARALLELISM=3* Number of CPU Default: 1
Apply parameters can be set using the SET_PARAMETER procedure from the
DBMS_APPLY_ADM package. For example, to set the DISABLE_ON_ERROR parameter
of the streams apply process named APPLY_EX, use the following syntax while
logged in as the Streams Administrator:
exec dbms_apply_adm.set_parameter('apply_ex','disable_on_error','n');
Change the apply parallelism parameter recommendation to a lower number.
In general, try 4 or 8 and increase or decrease as necessary for your workload.
In some cases, performance can be improved by setting the following hidden
parameter. This parameter should be set when the major workload is UPDATEs
and the updates are performed on just a few columns of a many-column table.
+ DYNAMICSTMTS=Y Default: N
If Y, then for UPDATE statements, the apply process will optimize the
generation of SQL statements based on required columns.
CHECKPOINTFREQUENCY=1000
Increase the frequency of logminer checkpoints especially in a
database with significant LOB or DDL activity.
exec dbms_capture_adm.set_parameter('capture_ex','_checkpoint_frequency','1000');
5. Additional Configuration for RAC Environments for a Apply Database
Queue Ownership
When Streams is configured in a RAC environment, each queue table has an
"owning" instance. All queues within an individual queue table are owned
by the same instance. The Streams components (capture/propagation/apply)
all use that same owning instance to perform their work. This means that
the database link specified in the propagation must connect to the owning
instance of the target queue. the apply process is run at the owning instance
of the target queue
Ownership of the queue can be configured to remain on a specific instance,
as long as that instance is available, by setting the PRIMARY _INSTANCE and
SECONDARY_INSTANCE parameters of DBMS_AQADM.ALTER_QUEUE_TABLE. If the
primary_instance is set to a specific instance (ie, not 0), the queue
ownership will return to the specified instance whenever the instance is up.
Apply will automatically follow the ownership of the queue. If the ownership
changes while apply is running, apply will stop on the current instance and
restart at the new owner instance.
Changing the GLOBAL_NAME of the Database
See the OPERATION section on Global_name below. The following are some
additional considerations when running in a RAC environment.
If the GLOBAL_NAME of the database is changed, ensure that the queue is
empty before changing the name and that the apply process is dropped and
recreated with the apply_captured parameter = TRUE. In addition, if the
GLOBAL_NAME does not match the db_name.db_domain of the database, include
the GLOBAL_NAME in the list of services for the database in the database
parameter initialization file.

Clone from multinode to single node

Hi,
db version=10.2.0.3 Oracle Application 12.1.2 o/s Linux 5
i want to clone from multi node to single node i am just concern about how to define the Hosts for Database and Application in a single machine
should i define db host on etho and Application host on eth1 network adapters
Pleas advice ....

HI,
Refer Note 230672.1 - Cloning Oracle Applications Release 11i with Rapid Clone
I hope u have applied necessary patches...(Latest Rapid Clone patch & autoconfig patches)
Follow these steps....
Clone PROD to DEV
1.     Prepare the Source System
a.     cd <RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>
perl adpreclone.pl dbTier
b.     cd <COMMON_TOP>/admin/scripts/<CONTEXT_NAME>
perl adpreclone.pl appsTier
2.     Shutdown the Source system.
Take the Backup
tar -czvf prodappl.tar.gz prodappl/
tar -czvf prodcomn.tar.gz prodcomn/
tar -czvf prodora.tar.gz prodora/
3.     Scp /ftp the all files & folders od source to target.
Scp *.tar.gz hostname@username:/path
4.     Shutdown Apllication & Database of Target.
5.     Take backup of target
mv devappl bdevappl
mv devcomn bdevcomn
mv devora bdevora
6.     Mv proadappl devappl
Mv prodcomn devcomn
Mv prodora devora
Mv proddata devdata
Mv proddb devdb
7.     Login as root
Remove the entries in oratab & oraInventory
8.     Run post clone scripts
a.Database Tier
cd $ORACLE_HOME/appsutil/clone/bin
perl adcfgclone.pl dbTier
[oracle@dbs4 bin]$ perl adcfgclone.pl dbTier
Enter the APPS password [APPS]:
First Creating a new context file for the cloned system.
The program is going to ask you for information about the new system:
Provide the values required for creation of the new Database Context file.
Do you want to use a virtual hostname for the target node (y/n) [n] ?:
Target instance is a Real Application Cluster (RAC) instance (y/n) [n]:
Target System database name [PROD]:DEV
Target system RDBMS ORACLE_HOME directory [oraDB/proddb/9.2.0]:/devDB/devdb/9.2.0
Target system utl_file accessible directories list [1]:
Number of DATA_TOP's on the target system [1]:
Target system DATA_TOP 1 [oraDB/proddata]:/devDB/devdata/
Do you want to preserve the Display set to dbs1:0.0 (y/n) [y] ?:
Do you want to preserve the port values from the source system on the target system (y/n) [y] ?:
Database port is 1521
Backing up /devDB/devdb/9.2.0/appsutil/DEV_dbs4.xml to /devDB/devdb/9.2.0/appsutil/DEV_dbs4.xml1.bak
Creating the new Database Context file from :
/devDB/devdb/9.2.0/appsutil/template/adxdbctx.tmp
The new database context file has been created :
/devDB/devdb/9.2.0/appsutil/DEV_dbs4.xml
Log file located at /devDB/devdb/9.2.0/appsutil/clone/bin/CloneContext_06210847.log
Running Rapid Clone with command:
perl /devDB/devdb/9.2.0/appsutil/clone/bin/adclone.pl java=/devDB/devdb/9.2.0/appsutil/clone/bin/../jre mode=apply stage=/devDB/devdb/9.2.0/appsutil/clone/bin/.. component=dbTier method=CUSTOM dbctxtg=/devDB/devdb/9.2.0/appsutil/DEV_dbs4.xml showProgress contextValidated=true
Beginning database tier Apply - Mon Jun 21 08:48:20 2010
Log file located at /devDB/devdb/9.2.0/appsutil/log/DEV_dbs4/ApplyDBTier_06210848.log
Completed Apply...
Mon Jun 21 08:50:06 2010
Beginning APPSDB_DEV registration to central inventory...
ORACLE_HOME NAME : APPSDB_DEV
ORACLE_HOME PATH : /devDB/devdb/9.2.0
Using Inventory location in /etc/oraInst.loc
Log file located at /etc/oraInventory/logs/OracleHomeCloner_06210850.log
ORACLE_HOME /devDB/devdb/9.2.0 was registered successfully.
Starting database listener for DEV:
Running:
/devDB/devdb/9.2.0/appsutil/scripts/DEV_dbs4/addlnctl.sh start DEV
You are running addlnctl.sh version 115.6
Logfile: /devDB/devdb/9.2.0/appsutil/log/DEV_dbs4/addlnctl.txt
Starting listener process DEV ...
Listener DEV has already been started.
addlnctl.sh: exiting with status 0
Apps tier
[applmgr@dbs4 ~]$ cd /devAPP/devcomn/clone/bin/
[applmgr@dbs4 bin]$ perl adcfgclone.pl appsTier
Enter the APPS password [APPS]:
First Creating a new context file for the cloned system.
The program is going to ask you for information about the new system:
Provide the values required for creation of the new APPL_TOP Context file.
Do you want to use a virtual hostname for the target node (y/n) [n] ?:
Target system database SID [PROD]:DEV
Target system database server node [dbs1]:dbs4
Target system database domain name [dbs.com]:
Does the target system have more than one application tier server node (y/n) [y] ?:n
Is the target system APPL_TOP divided into multiple mount points (y/n) [n] ?:
Target system APPL_TOP mount point [oraAPP/prodappl]:/devAPP/devappl
Target system COMMON_TOP directory [oraAPP/prodcomn]:/devAPP/devcomn
Target system 8.0.6 ORACLE_HOME directory [oraAPP/prodora/8.0.6]:/devAPP/devora/8.0.6
Target system iAS ORACLE_HOME directory [oraAPP/prodora/iAS]:/devAPP/devora/iAS
Do you want to preserve the Display set to dbs2:1.0 (y/n) [y] ?:
Do you want to preserve the port values from the source system on the target system (y/n) [y] ?:
Complete port information available at /devAPP/devappl/admin/out/DEV_dbs4/portpool.lst
UTL_FILE_DIR on database tier consists of the following directories.
1. /usr/tmp
2. 1
3. /devDB/devdb/9.2.0/appsutil/outbound/DEV_dbs4
4. /usr/tmp
Choose a value which will be set as APPLPTMP value on the target node [1]:
Backing up /devAPP/devappl/admin/DEV_dbs4.xml to /devAPP/devappl/admin/DEV_dbs4.xml1.bak
Creating the new APPL_TOP Context file from :
/devAPP/devappl/ad/11.5.0/admin/template/adxmlctx.tmp
The new APPL_TOP context file has been created :
/devAPP/devappl/admin/DEV_dbs4.xml
Log file located at /tmp/CloneContext_06210854.log
Running Rapid Clone with command:
perl /devAPP/devcomn/clone/bin/adclone.pl java=/devAPP/devcomn/clone/bin/../jre mode=apply stage=/devAPP/devcomn/clone/bin/.. component=appsTier method=CUSTOM appctxtg=/devAPP/devappl/admin/DEV_dbs4.xml showProgress contextValidated=true
Beginning application tier Apply - Mon Jun 21 08:55:51 2010
Log file located at /devAPP/devappl/admin/DEV_dbs4/log/ApplyAppsTier_06210855.log
Completed Apply...
Mon Jun 21 09:00:47 2010
Beginning APPSIAS_DEV registration to central inventory...
ORACLE_HOME NAME : APPSIAS_DEV
ORACLE_HOME PATH : /devAPP/devora/iAS
Using Inventory location in /etc/oraInst.loc
Log file located at /etc/oraInventory/logs/OracleHomeCloner_06210900.log
ORACLE_HOME /devAPP/devora/iAS was registered successfully.
Skipping the starting of services
INFO : Rapid Clone completed successfully
Thanks
Adiga

Clone 11i from multinode to single node to new server.

Hi,
As per the following details, I have to clone the 11i environment from multinode (3 nodes) to single node on OLE5.
ServerA: FORMS, WEB, ADMIN
ServerB: CP, FORMS, WEB, ADMIN
serverC: DB
Hardware Loadbalancer used with SSL encryption.
Clone requirements:
ServerX: CP, FORMS, WEB, ADMIN, DB (No hardware Load balancing & No SSL)
Please guide me with the important steps to clone from multi-node to single node in this situation.
Thanks,

959674 wrote:
Hi,
As per the following details, I have to clone the 11i environment from multinode (3 nodes) to single node on OLE5.
ServerA: FORMS, WEB, ADMIN
ServerB: CP, FORMS, WEB, ADMIN
serverC: DB
Hardware Loadbalancer used with SSL encryption.
Clone requirements:
ServerX: CP, FORMS, WEB, ADMIN, DB (No hardware Load balancing & No SSL)
Please guide me with the important steps to clone from multi-node to single node in this situation.
Thanks,Use Rapid Clone.
Rapid Clone Documentation Resources For Release 11i and 12 [ID 799735.1]
Cloning Oracle Applications Release 11i with Rapid Clone [ID 230672.1]
Cloning Oracle Applications Release 12 with Rapid Clone [ID 406982.1]
Thanks,
Hussein

Failover from RAC to Single Instance db

Hi
i know that i can have a single instance db , as the failover option in my dataguard system
do i need to change some parameters while i am failing over from Rac DB to Single Instance DB
something like cluster_db = false
Thanks

RonHeeb wrote:
thanks for the response. i have been regularly taking current sizes of each SGA from gv$sgastat to see what's being allocated. my thinking is that this is a minimum and that i should add to it for peak loads, ensuring that it's not set below any minimum that RACOne requires.
beyond that going to RACOne seems to be a direction for virtualized DB servers and for us 24 by 7 is not needed (although more than a few minutes outage would be an issue). in any case if needed we could go RAC on our most critical environments. I'm attracted to how patching/server maintenance can be achieved with RACOne.Okay, you either need high availability or you don't. if having a db go down "for more than a few minutes" is a problem then, don't you really need 24x7 ? And in that case, isn't the high availability offered by RAC is your only option? For me, having a mission critical database (and it looks like this qualifies) on anything "vitualized" is a disaster waiting to happen. I find it lunacy to have, say, 4 virtual failover servers (RACOne) on the same physical hardware. When that server crashes so does your entire failover scenario.
>
Edited by: user10489842 on Sep 13, 2012 2:04 PM

2 Node RAC to single node clonning

Hello,
We have 2 Node RAC database for R12 EBS on production now we want to refresh developement enviorenment which is single node so now can anybody tell me process to follow this or any documentaion for same.
Regards
Saransh Soni

Hi Saransh,
Please refer to similar threads in past :
convert RAC to single instance ebs R12
Re: Clone Oracle Apps 11.5.10.2 RacDB to Non-RAC DB
Regards
Rajesh

Resizing redo log files on a 3 node RAC with single node standby database

Hi
On a 3 node 11g RAC system,I have to resize the redo logs on primary database from 50M to 100M. I was planning to do the following steps:
SQL> select group#,thread#,members,status from v$log;
GROUP# THREAD# MEMBERS STATUS
1 1 3 INACTIVE <-- whenefver INACTIVE, logfile group can be dropped
2 1 3 CURRENT & resized, switch logfile can change logfile group
3 1 3 INACTIVE
4 2 3 INACTIVE
5 2 3 INACTIVE
6 2 3 CURRENT
7 3 3 INACTIVE
8 3 3 INACTIVE
9 3 3 CURRENT
9 rows selected.
SQL> alter database drop logfile group 1;
Database altered.
SQL> ALTER DATABASE ADD LOGFILE THREAD 1
GROUP 1 (
'/PROD/redo1/redo01a.log',
'/PROD/redo2/redo01b.log',
'/PROD/redo3/redo01c.log'
) SIZE 100M reuse; 2 3 4 5 6
Database altered.
However I am not sure what needs to be done for the standby. The standby_file_management is set to auto and it is single instance standby.
SQL> select group#,member from v$logfile where type='STANDBY';
GROUP#
MEMBER
10
/PROD/flashback/PROD/onlinelog/o1_mf_10_7b44gy67_.log
11
/PROD/flashback/PROD/onlinelog/o1_mf_11_7b44h7gy_.log
12
/PROD/flashback/PROD/onlinelog/o1_mf_12_7b44hjcr_.log
Please let me know.
Thanks
Sumathy

Hello;
For Redo and Standby redo this won't help :
standby_file_management is set to auto
On the Standby cancel recovery, then drop and recreate the redo and or Standby redo.
Then start recovery again.
Example ( I have a habit of removing the old file at the OS to avoid REUSE and conflicts )
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
SQL> ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT='MANUAL';
alter database add standby logfile group 4
('/u01/app/oracle/oradata/orcl/standby_redo04.log') size 100m;
ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT='AUTO'
Notes worth reviewing :
Online Redo Logs on Physical Standby [ID 740675.1]
Error At Standby Database Ora-16086: Standby Database Does Not Contain Available Standby Log Files [ID 1155773.1]
Example of How To Resize the Online Redo Logfiles [ID 1035935.6]
Best Regards
mseberg

Create new db from RAC cold backup

Hi Team
i need to copy cold database from one server to another server . and build an new rac database out of that cold backup .. i have done it for singel node instance . but do you know if i have to do something special for RAC instance .. or simply below mention steps are enough to build RAC database out of cold backup
oracle version is 10.2.0.1
1. install software and clusterware on new set of machine
2. copy cold backup on that set of machine
3.copy spfile and controlfile
4.open the database up with controlfile,spfile and dbf files
now i am not sure on one thing if i have to do something special for RAC DB or its like single instance.
please let me know if this is not clear or you need more info on that
Regards,
Devender

Hi,
Please check below which could be helpful for your issue
Migrate Non-RAC(Standalone) to RAC
Clonimg Standalone Database to RAC Database
Regard
Helios

Converting from RAC to Single Instance - Memory

hi,
we are moving forward with virtualizing our database environment and want to use 11g RACOne. We currently are using 3 node, 10g RAC. In coming up with specifications I am wondering what general rule there is for sizing the SGA. As an example if one of my databases has 3 500MB SGA's do I simply have a single instance with 1500MB SGA? I'm not sure what the approach would be.
Any info appreciated. Thanks in advance...ron

RonHeeb wrote:
thanks for the response. i have been regularly taking current sizes of each SGA from gv$sgastat to see what's being allocated. my thinking is that this is a minimum and that i should add to it for peak loads, ensuring that it's not set below any minimum that RACOne requires.
beyond that going to RACOne seems to be a direction for virtualized DB servers and for us 24 by 7 is not needed (although more than a few minutes outage would be an issue). in any case if needed we could go RAC on our most critical environments. I'm attracted to how patching/server maintenance can be achieved with RACOne.Okay, you either need high availability or you don't. if having a db go down "for more than a few minutes" is a problem then, don't you really need 24x7 ? And in that case, isn't the high availability offered by RAC is your only option? For me, having a mission critical database (and it looks like this qualifies) on anything "vitualized" is a disaster waiting to happen. I find it lunacy to have, say, 4 virtual failover servers (RACOne) on the same physical hardware. When that server crashes so does your entire failover scenario.
>
Edited by: user10489842 on Sep 13, 2012 2:04 PM

Creating DR standby from RAC to single NODE

Similar Messages

Maybe you are looking for