R12 clone with RMAN auxiliary db.

Hi all,
We require daily clone for our setup due to testing and other reason. Can we replace only database via RMAN Clone?
R12 clone with RMAN Auxiliary DB. Find below steps, if I am wrong correct me.
1.     run autoconfig on apps tier.
2.     perl <AD_TOP>/bin/admkappsutil.pl and Synchronize appsutil on db tier.
3.     Run autoconfig on dbtier or adconfig.sh <contextfile>) (which is correct? i am using autoconfig not with contextfile)
4.     adpreclone.pl dbTier
5.     adpreclone.pl appsTier
6.     copy source to target including db and apps tiers.
7.     perl adcfgclone.pl dbTechStack .
8.     create duplicate db (auxiliary db) from rman backup.
9.     sqlplus "/ as sysdba" @adupdlib.sql so
10.     perl adcfgclone.pl dbconfig <CONTEXT_NAME.xml> (This gives error, I am skipping this step. I have tried with perl adcfgclone.pl database but then also its give error. )
11.     exec FND_CONC_CLONE.SETUP_CLEAN;
12.     perl adcfgclone.pl dbTier (if we run perl adcfgclone.pl dbTechStack ,Is this step require?)
13.     perl adcfgclone.pl appsTier
please correct my steps.
thanks in advance,
sandeep

Hi,
3.     Run autoconfig on dbtier or adconfig.sh <contextfile>) (which is correct? i am using autoconfig not with contextfile)Run $ORACLE_HOME/appsutil/bin/adconfig.sh contextfile=$CONTEXT_FILE appspass=apps -- See (Note: 603104.1 - Troubleshooting RapidClone issues with Oracle Applications R12) for details.
10.     perl adcfgclone.pl dbconfig <CONTEXT_NAME.xml> (This gives error, I am skipping this step. I have tried with perl adcfgclone.pl database but then also its give error. )What is the error?
12.     perl adcfgclone.pl dbTier (if we run perl adcfgclone.pl dbTechStack ,Is this step require?)After running "perl adcfgclone.pl dbTechStack", you need to run "perl adcfgclone.pl dbconfig <Database target context file> -- See (Note: 406982.1 - Cloning Oracle Applications Release 12 with Rapid Clone) and (Note: 799735.1 - Rapid Clone Documentation Resources, Release 11i and 12) for details.
Regards,
Hussein

Similar Messages

Auxiliary channel allocation in TSPITR with RMAN-managed instance

Hi,
I'm trying do perform TSPITR with RMAN-managed auxiliary instance. All backups are stored on tape. I need to send MML environment values while allocating auxiliary channel to connect to correct NetWorker server and send other NetWorker parameters.
Unfortunately I have issues with sending these params - I can't send them from recover RUN block, as auxiliary instance does not exists at the time when I'm starting to execute script. (example from test env using disk channels)
RMAN> RUN
2> {
3> ALLOCATE CHANNEL c1 DEVICE TYPE disk;
4> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE disk;
5> SET NEWNAME FOR DATAFILE 1 TO '/u01/backup/tspitr/10gdb2/system01.f';
6> SET NEWNAME FOR DATAFILE 2 TO '/u01/backup/tspitr/10gdb2/undo01.f';
7> SET NEWNAME FOR DATAFILE 7 TO '/u01/backup/tspitr/10gdb2/hr_bak01.f';
8> SET AUXILIARY INSTANCE PARAMETER FILE TO '/home/oracle/params_auxinit.ora';
9> RECOVER TABLESPACE hr_test UNTIL TIME "SYSDATE - 1/4"
10> AUXILIARY DESTINATION '/u01/backup/tspitr/10gdb2';
11> RELEASE CHANNEL c1;
12> RELEASE CHANNEL aux1;
13> }
allocated channel: c1
channel c1: sid=141 devtype=DISK
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at 04/07/2010 17:21:53
RMAN-06174: not connected to auxiliary databaseI know I can do it using configure, but is there any way to set this on session level?
10.2.0.4, RHEL
Thanks,
Lukasz

What can be done here, is to CONFIGURE AUXILIARY CHANNEL to set appropriate params for auxiliary instance (without allocating channels manually).
I just wanted to know, if I can do it just for this one session (without permanent modification). What I can do, is:
CONFIGURE AUXILIARY CHANNEL DEVICE TYPE sbt_tape PARMS 'mml settings';
CONFIGURE CHANNEL DEVICE TYPE sbt_tape PARMS 'mml settings';
CONFIGURE DEFAULT DEVICE TYPE TO sbt_tape;
RUN
(new names, auxiliary parameter file)
RECOVER TABLESPACE ...
CONFIGURE AUXILIARY CHANNEL DEVICE TYPE sbt_tape CLEAR;
CONFIGURE CHANNEL DEVICE TYPE sbt_tape CLEAR;
CONFIGURE DEFAULT DEVICE TYPE CLEAR;I just wanted more 'elegant' solution.
Update:
Due to bug no. 4768353 there is no possibility to use automatic channel allocation in auxiliary instance. Problem resolved by using own customized auxiliary instance started before recovery process. Channels have been allocated manually using ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt... on already running aux.
Thanks,
Lukasz
Edited by: Łukasz Mastalerz on Apr 19, 2010 6:47 PM

Tablespace Point in Time Recovery fails with RMAN-06026:

I have cataloged with RMAN the datafiles from Snapshot backup. Still it fails with the following error.
RMAN> RECOVER TABLESPACE TSPC UNTIL TIME "to_date('03-apr-2013 02:18:00','dd-mon-yyyy hh24:mi:ss')" AUXILIARY DESTINATION '/tmp/auxpran';
Starting recover at 03-APR-13
using channel ORA_DISK_1
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time
List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS1
Creating automatic instance, with SID='Ebgt'
initialization parameters used for automatic instance:
db_name=ORCL
db_unique_name=Ebgt_tspitr_ORCL
compatible=11.2.0.0.0
db_block_size=8192
db_files=200
sga_target=280M
processes=50
db_create_file_dest=/tmp/auxpran
log_archive_dest_1='location=/tmp/auxpran'
#No auxiliary parameter file used
starting up automatic instance ORCL
Oracle instance started
Total System Global Area 292933632 bytes
Fixed Size 1336092 bytes
Variable Size 100666596 bytes
Database Buffers 184549376 bytes
Redo Buffers 6381568 bytes
Automatic instance created
Running TRANSPORT_SET_CHECK on recovery set tablespaces
TRANSPORT_SET_CHECK completed successfully
contents of Memory Script:
# set requested point in time
set until time "to_date('03-apr-2013 02:18:00','dd-mon-yyyy hh24:mi:ss')";
# restore the controlfile
restore clone controlfile;
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log
sql 'alter system archive log current';
# avoid unnecessary autobackups for structural changes during TSPITR
sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
executing Memory Script
executing command: SET until clause
Starting restore at 03-APR-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=19 device type=DISK
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: copied control file copy
input file name=/tmp/auxpran/controlbc.ctl
output file name=/tmp/auxpran/ORCL/controlfile/o1_mf_8opkv8v4_.ctl
Finished restore at 03-APR-13
sql statement: alter database mount clone database
sql statement: alter system archive log current
sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
contents of Memory Script:
# set requested point in time
set until time "to_date('03-apr-2013 02:18:00','dd-mon-yyyy hh24:mi:ss')";
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile 1 to new;
set newname for clone datafile 3 to new;
set newname for clone datafile 2 to new;
set newname for clone tempfile 1 to new;
set newname for datafile 5 to
"+DG_DATA/orcl/datafile/tspc.268.811733685";
# switch all tempfiles
switch clone tempfile all;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile 1, 3, 2, 5;
switch clone datafile all;
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
renamed tempfile 1 to /tmp/auxpran/ORCL/datafile/o1_mf_temp_%u_.tmp in control file
Starting restore at 03-APR-13
using channel ORA_AUX_DISK_1
One or more auxiliary set datafiles could not be removed
Removing automatic instance
shutting down automatic instance
database dismounted
Oracle instance shut down
Automatic instance removed
auxiliary instance file /tmp/auxpran/ORCL/controlfile/o1_mf_8opkv8v4_.ctl deleted
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/03/2013 02:32:55
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
Could anyone please reply ASAP?
Regards,
Pranam

I had created a snapshot of the database(datafiles and archivelogs) and cataloged them.
CATALOG START WITH "+TBL_DG_DATA/ORCL/DATAFILE/" NOPROMPT;
catalog start with "+DG_ARCH/ORCL/ARCHIVELOG/" NOPROMPT;
The time i gave was after the snapshot was created.
When it failed the first time I created another controlfile using
sql "alter database backup controlfile to ''/tmp/auxpran/controlbc.ctl''";
And ran the recover command after the time after i generated this controlfile. Changed nothing else. TSPITR completed successfully. But it had failed first time. Cannot figure how it ran the second time but failed the first time.
Removing automatic instance
Automatic instance removed
auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_temp_8opndd87_.tmp deleted
auxiliary instance file /tmp/auxpran/ORCL/onlinelog/o1_mf_3_8opnd1o6_.log deleted
auxiliary instance file /tmp/auxpran/ORCL/onlinelog/o1_mf_2_8opncy32_.log deleted
auxiliary instance file /tmp/auxpran/ORCL/onlinelog/o1_mf_1_8opncv7d_.log deleted
auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_sysaux_8opn516p_.dbf deleted
auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_undotbs1_8opn4j14_.dbf deleted
auxiliary instance file /tmp/auxpran/ORCL/datafile/o1_mf_system_8opmyvly_.dbf deleted
auxiliary instance file /tmp/auxpran/ORCL/controlfile/o1_mf_8opmy14q_.ctl deleted
Finished recover at 03-APR-13

Cloning with rman

Hi all,
cloning the database using rman.
i configure everything and finally executed
RMAN> duplicate target database to 'clone';
It have executed. but because of some problem with naming convention of directories it is cancelled.
I resoleved that and connected to target database
RMAN>connect target sys/oracle@sales;
and connected to auxiliary
RMAN> connect target sys/oracle@clone;
but it is connecting to sales instance only.
so when i executed
RMAN>duplicate target database to 'clone'
it is saying database name mismathes, auxiliary instance has sales, command specifies clone.
How can i resolve it. thank you!

RMAN> connect target sys/oracle@clone;the clone tns service is for auxiliary, then why you mentioned target again?
It should as below
rman target sys/oracle@sales auxiliary sys/oracle@clone;(or)
from auxiliary server
$ rman target sys/oracle@sales auxiliary /
RMAN> duplicate target database to 'clone';Always run duplicate from auxiliary/clone server, to avoid much pressure on target/primary.
Edited by: CKPT on Dec 12, 2011 1:51 PM

Problem creating physical Standby database with RMAN

Hi All
I am trying to learn oracle dataguard and as part of the process learning creating standby database.
Platform : Sun-Fire-V250 Sparc, Solaris 10
Database Version - Oracle 11R2
I am creating standby database on same server, so directory structure is different.
Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
On Primary Database:
*.FAL_CLIENT='orcl11020' #Primary database unique name
*.FAL_SERVER='stdby_11' #Standby database unique name
db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
standby_file_management=auto
*.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
*.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
*.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_MAX_PROCESSES=30
Copied same pfile for standby database and modified following-
*.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
*.db_name='orcl1102'
*.db_unique_name='stdby_11'
*.FAL_CLIENT='stdby_11'
*.FAL_SERVER='orcl11020'
db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
standby_file_management=auto
*.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
*.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=orcl11020'
3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
3. Created password file with same credential as primary database.
4.Up-to-date RMAN backup of primary database available.
5.Create standby controlfile with rman
While primary database s open (I tried with primary database in mount mode as well)-
$>rman catalog rman/paswd@rman target /
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
6. Open a new terminal and startup standby database in nomount mode using parameter file created -
$>ORACLE_SID=stdby_11
$>export ORACLE_SID
$>sqlplus / as sysdba
SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
SQL>quit
$> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
Error 1017 received logging on to the standby
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
So on both primary and standby I confirmed
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
Password files are called - orapworcl11020 and orapwstdby_11
Can someone guide me where thisngs are going wrong here please.

Not sure if I understood it clearly.
SELECT * FROM V$ARCHIVE_GAP;
returns no rows so there is no gap.
But could you please explain me the result of the previous query. To catch up again, on standby when I check
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
SEQUENCE# APPLIED
75 NO
74 NO
76 NO
77 NO
I understand that though archive files have been copied across but they are not applied yet.
On primary when I give your query -
SELECT name as STANDBY,SEQUENCE#,applied, completion_time
2 FROM v$archived_log
3 where dest_id=2
4 and sequence# BETWEEN 74 and 80;
I get -
STANDBY SEQUENCE# APPLIED COMPLETIO
stdby_11 74 YES 28-JUN-11
stdby_11 75 YES 28-JUN-11
stdby_11 76 YES 29-JUN-11
stdby_11 77 YES 29-JUN-11
stdby_11 78 YES 29-JUN-11
stdby_11 79 YES 29-JUN-11
stdby_11 80 YES 29-JUN-11
stdby_11 75 NO 07-JUL-11
stdby_11 74 NO 07-JUL-11
stdby_11 76 NO 07-JUL-11
stdby_11 77 NO 07-JUL-11
stdby_11 78 NO 07-JUL-11
I have intentionally given
sequence# BETWEEN 74 and 80
because I know in the current incarnaion of the database, max sequence is 78.
So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
Then my final question is, when will these archives be applied to standby database?
I am sorry to ask too many questions but I am just trying to understand how it all works.
Thanks for your help again

Oracle 3113 creating a standby with rman

Hello,
environment is 11gR2 on Linux.
Tested on CentOS 5.5 as OS and local LAN as interconnect and the duplicate command terminates successfully in some minutes.
Same script but using oel 5.5 and a wan (3Mbit/s) and I keep getting 3113 errors after about 2h or 3h.
I suspect some timeout on wan (that is over vpn) but I would also like to trace something at my side.
I run a shell script with nohup and send it to background and this is the log, from which you can see the rman script:
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Sep 7 14:50:11 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN>
connected to target database: TESDB1 (DBID=11492743)
RMAN>
connected to auxiliary database: DUMMY (not mounted)
RMAN>
RMAN> run{
2> allocate channel prmy1 type disk;
3> allocate auxiliary channel stby1 type disk;
4> duplicate target database for standby from active database
5> spfile
6> parameter_value_convert 'TESDB1','TESDB1DR'
7> set db_file_name_convert='/TESDB1/','/TESDB1DR/'
8> set log_file_name_convert='/TESDB1/','/TESDB1DR/'
9> set 'db_unique_name'='TESDB1DR'
10> set control_files='/app/oradata/TESDB1DR/control01.ctl','/app/oradata/flash_recovery_area/TESDB1DR/control02.ctl'
11> set db_recovery_file_dest='/app/oradata/flash_recovery_area'
12> set DB_RECOVERY_FILE_DEST_SIZE='4977M'
13> nofilenamecheck;
14> }
using target database control file instead of recovery catalog
allocated channel: prmy1
channel prmy1: SID=12 device type=DISK
allocated channel: stby1
channel stby1: SID=135 device type=DISK
Starting Duplicate Db at 07-SEP-10
executing Memory Script
executing command: SET NEWNAME
renamed tempfile 1 to /app/oradata/TESDB1DR/temp01.dbf in control file
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting backup at 07-SEP-10
channel prmy1: starting datafile copy
input datafile file number=00003 name=/app/oradata/TESDB1/undotbs01.dbf
.. after about three hours (and 3.2Gb transferred) it continues with:
RMAN-03009: failure of backup command on prmy1 channel at 09/07/2010 17:53:49
RMAN-06136: ORACLE error from auxiliary database: ORA-03113: end-of-file on communication channel
Process ID: 3187
Session ID: 192 Serial number: 3
continuing other job steps, job failed will not be re-run
.. after 15 minutes:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/07/2010 18:09:35
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on clone_default channel at 09/07/2010 18:09:34
RMAN-10038: database session for channel clone_default terminated unexpectedly
RMAN> **end-of-file**
RMAN>
Recovery Manager complete.
the undo tbs is 3.2 Gb so I'm not sure if the 3113 happens at the end of copy... but the tablespace doesn't succeed
and the other jobs don't start even if it says "continuing other job steps"..
rman started at 14:50 and in listener at dr site I have:
Tue Sep 07 14:50:55 2010
07-SEP-2010 14:50:55 * service_update * TESDB1DR * 0
07-SEP-2010 14:50:55 * (CONNECT_DATA=(SERVICE_NAME=TESDB1DR)(CID=(PROGRAM=oracle)(HOST=lb-orajde.boiron.ntm)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.49.1.93)(PORT=35240)) * establish * TESDB1DR * 0
Tue Sep 07 15:00:58 2010
07-SEP-2010 15:00:58 * service_update * TESDB1DR * 0
Tue Sep 07 16:35:04 2010
07-SEP-2010 16:35:04 * service_update * TESDB1DR * 0
Tue Sep 07 17:02:04 2010
07-SEP-2010 17:02:04 * service_update * TESDB1DR * 0
07-SEP-2010 17:02:10 * service_update * TESDB1DR * 0
Tue Sep 07 17:53:17 2010
07-SEP-2010 17:53:17 * service_update * TESDB1DR * 0
Tue Sep 07 18:09:00 2010
07-SEP-2010 18:09:00 * (CONNECT_DATA=(SERVICE_NAME=TESDB1DR)(CID=(PROGRAM=rman)(HOST=lb-orajde.boiron.ntm)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.49.1.93)(PORT=32610)) * establish * TESDB1DR * 0
In alert.log at dr site I have at 17:02 (about 50 minutes before error):
Tue Sep 07 15:05:01 2010
db_recovery_file_dest_size of 4977 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Tue Sep 07 17:02:03 2010
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 07-SEP-2010 17:02:03
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 110
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.49.1.93)(PORT=35226))
some times (always at 17:02) and nothing more
In alert.log at primary site:
Tue Sep 07 14:50:36 2010
Clearing standby activation ID 11529351 (0xafec87)
The primary database controlfile was created using the
'MAXLOGFILES 16' clause.
There is space for up to 13 standby redo logfiles
Use the following SQL commands on the standby database to create
standby redo logfiles that match the primary database:
ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800;
Tue Sep 07 16:00:40 2010
Thread 1 advanced to log sequence 759 (LGWR switch)
Current log# 3 seq# 759 mem# 0: /app/oradata/TESDB1/redo03.log
Tue Sep 07 16:00:41 2010
Archived Log entry 528 added for thread 1 sequence 758 ID 0xafec87 dest 1:
In sqlnet.log of primary site:
Tue Sep 07 17:53:49 2010
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 07-SEP-2010 17:53:49
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 110
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.12.41)(PORT=1521))
and the same at 18:09
No other errors.
Any hints?
BTW: what is the minimum size of undo tbs? Can I have compression enabled also during duplication if transport service is configured with COMPRESSION=ENABLED, or does it count only when copying redo files?
Thanks in advance,
Gianluca

Thanks for your reply.
I will try your suggestion as it could come useful some time.
So with this alternate method at the end I would have standby aligned as of backup time, correct?
And after running something like this on standby:
SQL> alter database recover managed standby database disconnect from session;
It will begin to receive, archive and apply redo logs, correct?
Some answers regarding the original question. It was confirmed that there was a 2hours cut-off time at firewall level.
The first datafile that the rman session began to copy was 3.2Gb in size, taking more than 2 hours completing.
Monitoring with netstat on source and target I saw this at source during the duplicate process:
tcp 0 0 10.49.1.93:46626 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46627 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46629 192.168.12.41:1521 ESTABLISHED
tcp 0 369240 10.49.1.93:50371 192.168.12.41:1521 ESTABLISHED
and the session bound to port 50371 was the only one pushing data (send queue not empty).
The other 3 ones I presume are for control of rman session. I get 3 sessions even if I open only one channel on primary side.
After the first datafile completes copy, a new session (with port 14871) is established substituting the other one.
The three initial ones instead remain for all the duplicate process.
tcp 0 487872 10.49.1.93:14871 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46626 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46627 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46629 192.168.12.41:1521 ESTABLISHED
So after the copy of the first file, the session come back to one or more of the initial 3 ones, and they probably make a push-ack, got a 3113 as the firewall has silently cut them after 2 hours.... and the datafile, even if completed, is not marked as completed. A new run would copy again it...
Now the time has been put to 8hours, with 24hours being the maximum value set (no disable possible as far as the network guy said...).
And the duplicate completed correctly.
Would I have to fear any problems with this cut-off due to "normal" dataguard operations or not, in your opinion?
Thanks
Gianluca

Ebs r12 cloning using rman online backup

dear all,
how are you guys? i have ebs r12 on multi node and i want to clone db tier and apps tier using rman online backup,can anybody provide me the detail steps of cloning ebs(db tier and appstier ) using rman online backup and directory structure on source and target database is also different.your help highly appreciated thanks in advance.
regards.

Hi,
You cannot use RMAN to clone the Apps tier of the EBS and you may use RMAN only on the DB tier. For a complete backup, as mentioned by Hemant K Chitale, you will have to use the rapid clone utility.
To perform a rapid clone using RMAN there are plenty of step by step instructions in google which may guide in addition to support.oracle.com, Let me google that for you
Thanks &
Best Regards,

R12 Apps with 4 node RAC and 4 apps nodes - Post Install check list

Hi All,
We have a new Oracle Apps R12 instalaltion with 4 node RAC and 4 Apps nodes with load balancing and external web tier being done by an outside firm. We are assigned the responsibility of checking that everything has been configured properly both on the RAC side and Apps side. I haven't worked on RAC earlier. Please let me know what all need to be checked before approving the install done by the outside firm.
Thank you!

Please check below metalink notes
RAC Assurance Support Team: RAC and Oracle Clusterware Starter Kit and Best Practices (Generic) [ID 810394.1]
Using Oracle 10g Release 2 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12 [ID 388577.1]
Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 12 [ID 823587.1]
Oracle E-Business Suite and Oracle Real Application Clusters Documentation Roadmap [ID 745759.1]
745759.1 Oracle E-Business Suite and Oracle Real Application Clusters Documentation Roadmap
384248.1 Sharing The Application Tier file system in Oracle E-Business Suite Release 12
387859.1 Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12
406982.1 Cloning Oracle Applications Release 12 with Rapid Clone
240575.1 RAC on Linux Best Practices
265633.1 Automatic Storage Management Technical Best Practices
Loadbalancer
note 380489.1 Using Load-Balancers with Oracle E-Business Suite Release 12
note 727171.1 Implementing Load Balancing On Oracle E-Business Suite - Documentation For Specific Load Balancer Hardware
note 601694.1 How To Check Session Persistence On BigIP F5 And Cisco Ace Load Balancer Appliances
note 603325.1 Using Cisco ACE Series Application Control Engine with Oracle E-Business Suite Release 12
Installation R12
note 761564.1 Oracle Applications Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86
note 402310.1 Oracle Applications Installation and Upgrade notes Release 12 (12.0) for Linux (32-bit)
note 559518.1 Cloning Oracle E-Business Suite Release 12 RAC-Enabled Systems with Rapid Clone
note 735276.1 Interoperability notes E-Business Suite R12 with Oracle Database 11gR1
Shared Applications Confiugurations:
note 380483.1 Oracle E-Business Suite Release 12 Additional Configuration and Deployment Options
note 384248.1 Sharing The Application Tier File System in Oracle E-Business Suite Release 12
Edited by: Amigo on Dec 20, 2010 9:58 AM

R12 clone have PRODUCTION ENTRIES

Hi All
We are running r12 EBS on solaris 5.10. Recently I cloned r12 instance with latest production image.
After clonning I noticed some PRODUCTION ENTRIES in Concurrent managers and in
System Administration--> Oracle Applications Manager --> Hosts. It was showing me of PRODUCTION Application and database server's host along with clone instance hosts.
Is there anyways I can remove this entries or I do have to re-clone.
Regards
Musaddaq

Hi,
These entries wouldn't do any harm, but as best practise you can run "EXEC FND_CONC_CLONE.SETUP_CLEAN;" and run autoconfig (db first and then apps).
The command would clear the node information from fnd_nodes table and running autoconfig would populate the correct entries in the table.
--Jayant

Restore backups on new server with RMAN (nocatalog).

Hi,
On my production database (Oracle8i/Solaris8) I use RMAN(nocatalog) to backup database:
connect target
run {
allocate channel d1 type disk;
backup full tag = 'Full Backup'
format '/oracle_backups/db_%t_%s_p%p'
(database);
sql 'alter system switch logfile';
backup
full
etc.}
I need to test backup by restoring it on test server (Oracle8i/Linux7.3). How I can point RMAN on test server to backup files location?
Thanks.

If you use a recovery catalog and want to duplicate database in a fresh server.
1. connect with the target database.
2. connect with the recovery catalog.
3. connect with the auxiliary database.
4. Run the duplicate command.
Before running the duplicate command copy the backup piece to your fresh server from the target server. Both mount point should be same.
Regards
Asif Kabir
-- mark your helpful post as correct/helpful.

Got error while recover controlfile with rman

Dear all,
My controlfile and some datafiles were crash and i tried to recover their with rman as the following step:
1. startup nomount;
2. restore controlfile from autobackup;
3. alter database mount;
4. restore database;
5.SELECT archivelog_change#-1 FROM v$database;
ARCHIVELOG_CHANGE#-1
1301671
6.run {
set until scn 1301671;
recover database;
executing command: SET until clause
Starting recover at 01 พ.ย. 2006
using channel ORA_DISK_1
starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/01/2006 15:38:01
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database reco
ver if needed
start until change 1301671 using backup controlfile
ORA-00283: recovery session canceled due to errors
ORA-01190: controlfile or data file 1 is from before the last RESETLOGS
ORA-01110: data file 1: 'C:\ORACLE\ORADATA\DB01\SYSTEM01.DBF'
What happend? Please give me some advise.
Thaks for advance !
Chara

After every resetlogs you have to take fresh backup.
It seems you have opened your database in resetlogs and your backup is prior to this resetlogs.So the controlfile is showing inconsistance with the other datafiles.

Migrating with RMAN from 10g to 11g

Hi gurus,
I am following the following procedure to migrate database from 10g to 11g using rman
Source side:
RMAN>connect target
RMAN>backup database;
RMAN>backup archivelog all;
RMAN>backup current controlfile;
SQL> create pfile from spfile;
Copied datafile, archivelog backup files and pfile and password files to target side. i.e. on 11g server side
Target side:
Set proper parameters for 11g
SQL>startup nomount;
RMAN>connect target
RMAN>set dbid=<source database id>
RMAN>catalog start with '<rman backup file location';
RMAN>restore controlfile;
RMAN>run
set newname for datafile 1 to '<target datafiles location with file name';
restore database;
switch datafile all;
finished
upto now it's success full when i am trying to recover
RMAN>recover database;
it is saying
rman 00571
rman 00569
rman 00571
rman 03002
ora - 19698
can you please suggest the solution for this.
thanks a lot.

I'm not sure what you're doing is supported.
You are taking a 10g database and restore and recover it using 11g software.
I think you are allowed to do that with 10g software only.

Logical Standby recover with RMAN

Hi All,
I have a test environment with Primary DB Server, Physical Standby and Logical Standby.
The Logical Standby DB (cur_log_stdb) is backed up every evening by RMAN and I have a question:
If I recover my Logical Standby DB from backup and switch replication to new Logical Standby DB (new_log_stdb) it will work or not?
My steps e.g.:
1. Make a new server for my new_log_stdb and repair structure of catalogs;
2. Repair listener.ora and tnsnames.ora files from cur_log_stdb to new_log_stdb;
3. Restore DB with RMAN from backup to new_log_stdb;
4. On cur_log_stdb execute "alter database stop logical standby apply";
5. Change a DNS name from cur_log_stdb to new_log_stdb;
6. On new_log_stdb execute "alter database start logical standby apply immediate";
I'm not sure that archivelogs will apply to the new_log_stdb for period since rman backup was created.
But if this plan won't work how can I restore Logical Standby DB from RMAN backup and resume replication from Primary?
Configuration:
Oracle Linux 6.4
Oracle Database 11.2.0.3
Primary and Physical with Data Guard

Hello;
The only way to know for sure is to test it. You are asking somebody you don't know to confirm a recovery test for you. You have to perform the test yourself to be certain.
If your plan does not work you can always rebuild the Standby.
Best Regards
mseberg

How to start with RMAN as I am beginner?

Dear all,
How to start with RMAN as I am beginner? Any simple document or guide line for me.
Thanks,
Amy

How to start with RMAN as I am beginner? Any simple
document or guide line for me.go to yours oracle home directory /orahome/bin there is RMAN exe tool run it it will show you prompt RMAN
Recovery Manager: Release 10.1.0.2.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
RMAN> connect target sys/sys
connected to target database: ORCL (DBID=1171886541)
RMAN> backup database
2> ;
Starting backup at 21-JAN-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\SYSAUX01.DBF
input datafile fno=00005 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\EXAMPLE01.DBF
input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 21-JAN-08
channel ORA_DISK_1: finished piece 1 at 21-JAN-08
piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2008_01_21\O1_MF_NNNDF_TAG20080121T135924_3S8QQF74_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 21-JAN-08
channel ORA_DISK_1: finished piece 1 at 21-JAN-08
piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2008_01_21\O1_MF_NCSNF_TAG20080121T135924_3S8QSSN4_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 21-JAN-08
http://www.orafaq.com/faq/rmanKhurram

Recovery with RMAN in case of complete lost of all files

Hi,
I am using RMAN in nocatalog mode to backup my databases to tape using the RMAN-Module for Legato.
I4ve read that in case of loosing all my controlfiles i cannot easily restore the controlfiles.
Lets assume the following scenario:
I am performing a daily full backup with RMAN in nocatalog mode. Approx. 2 hours after the completed backup my machine crashes and all files (i.e. OS-Files, Database, Controlfiles) are lost.
Now I have to reinstall the OS, reinstall Oracle and restore the backup.
Due to backups made with RMAN in nocatalog mode i have the restore the controlfies prior to restore the database. Metalink says restoring the controlfile from RMAN in nocatalog mode is not that easy.
Is there any way to restore the controlfile from RMAN in nocatalog mode in case of complete crash ??
Thanks.
Ronny.

RESTORE CONTROLFILE FROM 'filename...' doesn't appear to be supported in 8i.
What are the options for 8i?.
I have the backup sets with me from my previous installation before crash which also contains Control files.
However I am unclear as to how to proceed wit RMAN recovery with those files. There seems to be no way to point RMAN to those backupsets since RMAN apparently reads its information from catalog or the control file in case of nocatalog.
I think if there is a way to atleast restore the control file from the backup set, RMAN can proceed since it will find all the other backup details there.
Any help is greatly appreciated.
thanks
RP

R12 clone with RMAN auxiliary db.

Similar Messages

Maybe you are looking for