Duplication of controlfile in ASM

Hi all

I just created a database of stand-alone 10g with just a controlfile. I just a DG, but I want to multiplex using the RMAN copy.

Can someone tell me what are the steps to reproduce the controlfile in ASM?

The controlfile will reside in + DG / < DID > controlfile and the other will be in + DG / < a > / datafile directories in the same DG.

RMAN copy of

ALTER system set control_files ='+ DG / < a > < DID > /controlfile/ct1.f','+DG/ / datafile/ct2.f ' scope = spfile

Thank you

I was able to copy the controlfiles usign rman.

I reproduced it and inserted the new controlfile in spfile.

Tags: Database

Similar Questions

Controlfile on ASM performance issue
See the Controlfile Enqueue performance tips, review are to go the separator control file diskgroup(need outage)? or add a disc (different LUN, (I prefer this approach) in the same disk group, seems to slow down disc boxes for that matter...)

2nd question: snapshot controlfile can be placed on the storage of the ASM?
The following can help:
-Separate control to an another diskgroup file can make things even worse in case that the total number of discs is not in the new disk group.
-Those who control claim file questions are usually nothing to do with storage throughput you have, but the number of operations that require different levels of exclusion on the control files.
-Given that several copies of controlfiles are updated at the same time a possible, sometimes, it's the secondary copy of controlfile is slower than the other. Please check that this is not the question (different storage levels can cause such problems)

Kind regards
Hüsnü Sensoy

Check lock Enqueue controlfile to ASM RAC
I do the research, there is demand to go controlfile separate starts, & create new controlfile with new values, because this alert, there are assumptions that controlfile can be the cause of the performance problem. any body has that question or a suggestion or metalink note # for additional researchwork would be useful.

INST_ID SELECT USERNAME SERVICE_NAME SID BLKSID EVENT PROGRAM
3 rman@prod1 (TNS V1 - V3) SYS SYS$ 2000 USERS control file single write

Current values:
MAXLOGFILES 384
MAXLOGMEMBERS 3
MAXDATAFILES 2048
MAXINSTANCES 32
MAXLOGHISTORY 10904

Proposed values:
MAXLOGFILES 64
MAXLOGMEMBERS 3
MAXDATAFILES 2048
MAXINSTANCES 8
MAXLOGHISTORY 4000

Published by: DBA2008 on July 10, 2009 10:49
Hello

Control causes the performance problem! ... I don't think so...

Have done u face any problem of performance due to control file?

Thank you
Baskar.l

controlfile multiplexing
Please guide me...

control file multiplexing...
Salvation;

Please see:
http://download.Oracle.com/docs/CD/B12037_01/server.101/b10739/control.htm#i1006192
http://kamranagayev.com/2009/03/23/step-by-step-multiplexing-control-file-of-Oracle-database-by-adding-new-hard-drive-to-Linux/

See also:
Re: Multiplexing Controlfiles in ASM

Respect of
HELIOS

Automatically deleted from the storage of the DSO after data files using the command cp ASMCMD... why?

I installed Oracle database on Linux 6.6, Virtualbox 11.2.0.1.0.
I used ASM for database storage.
When I want to perform a backup in offline mode. I stop the database data files and copy to the filesystem as follows (for example).
ASMCMD [+] > cp +DATA/ora11g/datafile/system.270.883592533/u01/app/oracle
The files copied with success and also any other data files, logs and controlfiles files. Then, I also rename all the files in editing mode.
After that, I used the backup files to start the oracle of backup (storage non - ASM with new pfile edited)
Open successfully from a backup database.
But when I want to use old spfile to open the database for the storage of the DSO again, a few errors have occurred as no data files in ASM storage.
I check the contents of the ASM storage with ASMCMD commands. And realize that there only spfile and controlfile located ASM storage and other files: data files and online redo logfiles automatically deleted.
Why the data files and log files deleted ASM storage? Is this normal? I have no delete all files of the DSO.
It is actually deleted from the use of the cp command?

Exactly what we say. Data in ASM files are OMF (Oracle managed files). The RENAME translates the DSO by deleting the original file.

Hemant K Collette

ORA-19504: cannot create the file '+ DATA '.

Hello everyone.
This is the scenario:
We have a test server that is used to restore daily backups of the Production database. Restore us the database with the same SID as the production one.
For specific reasons, we need create a second database (with a different SID) on this server with an older backup from the production one. To realize that I'm trying to use a part of the "DUPLICATE without connection to the target" tutorials on the web.
I tried the simple guide that I found which is:
(1) copy the backup files cold /somedirectory
(2) start OLD database with nomount
(3) connect RMAN with OLDER as an auxiliary
(4) run the following: DUPLICATE DATABASE FOR OLD BACKUP LOCATION ' / somedirectory' NOFILENAMECHECK.
Here's the result (I deleted some lines because of the size of it):
----------------------
RMAN > ProdDB to OlderDB DUPLICATE DATABASE
2 > LOCATION of BACKUP "/ home/oracle/OlderBackupFiles.
3 > NOFILENAMECHECK.
4 >
From October 1, 14 Db double
content of Script memory:
{
clone of SQL 'alter system set control_files =
"+DATA/OlderDB/controlfile/current.829.859839217" comment =
' Set by RMAN "scope = spfile;
clone of SQL 'alter system set = db_name
"ProdDB" comment =
' Modified by RMAN duplicate "scope = spfile;
clone of SQL 'alter system set db_unique_name =
"OlderDB" comment =
' Modified by RMAN duplicate "scope = spfile;
clone to stop immediately;
Start clone force nomount
Restore controlfile primary clone of ' / home/oracle/OlderDB/controlfile_ProdDB_20141001_4159.bkp';
change the clone database mount;
}
execution of Script memory
SQL statement: alter system set control_files = comment "+DATA/OlderDB/controlfile/current.829.859839217" = "defined by RMAN" scope = spfile
SQL statement: change the system db_name set = comment "ProdDB" = "modified by RMAN duplicate" scope = spfile
SQL statement: alter system set db_unique_name = comment "OlderDB" = "modified by RMAN duplicate" scope = spfile
(...)
From restoration to 1 October 14
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID = 191 type device = DISK
channel ORA_AUX_DISK_1: restore the control file
channel ORA_AUX_DISK_1: restoration complete, duration: 00:00:03
output file name=+DATA/OlderDB/controlfile/current.829.859839217
Restoration finished in October 1, 14
mounted database
output channel: ORA_AUX_DISK_1
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID = 191 type device = DISK
content of Script memory:
{
until the SNA 274262921.
the value of newname for datafile clone 1 again;
the value of newname for datafile clone 2 again.
the value of newname for datafile clone 3 again.
the value of newname for datafile clone 4 new ones;
the value of newname for datafile clone 5 again.
the value of newname for datafile clone 6 again.
the value of newname for datafile clone 7 again.
restoration
database clone;
}
(...)
From restoration to 1 October 14
using the ORA_AUX_DISK_1 channel
channel ORA_AUX_DISK_1: from the restore backup set data file
channel ORA_AUX_DISK_1: specifying datafile (s) to restore from backup set
channel ORA_AUX_DISK_1: restore datafile 00001 to + DATA
channel ORA_AUX_DISK_1: restore datafile 00002 to + DATA
channel ORA_AUX_DISK_1: restore datafile 00003 to + DATA
channel ORA_AUX_DISK_1: restore datafile 00004 in + DATA
channel ORA_AUX_DISK_1: restore datafile 00005 to + DATA
channel ORA_AUX_DISK_1: restore datafile 00006 to + DATA
channel ORA_AUX_DISK_1: restore datafile 00007 to + DATA
channel ORA_AUX_DISK_1: reading from the backup /home/oracle/OlderDB/database_ProdDB_20141001_4157.bkp piece
channel ORA_AUX_DISK_1: ORA-19870: error when restoring the backup /home/oracle/OlderDB/database_ProdDB_20141001_4157.bkp piece
ORA-19504: cannot create the file '+ DATA '.
ORA-17502: ksfdcre:4 cannot create the file + DATA
ORA-15041: diskgroup space 'DATA' exhausted
switch to the previous backup
Oracle instance started
(...)
content of Script memory:
{
clone of SQL 'alter system set = db_name
"OlderDB" comment =
' Restore the original value by RMAN "scope = spfile;
clone of SQL 'alter system reset db_unique_name scope = spfile;
clone to stop immediately;
}
execution of Script memory
Errors in the script of the memory
RMAN-03015: an error has occurred in the script stored memory Script
RMAN-06136: the auxiliary database ORACLE error: ORA-01507: database not mounted
ORA-06512: at "SYS." "X$ DBMS_RCVMAN ', line 13466
ORA-06512: at line 1
RMAN-05556: not all data files have backups can be recovered on SNA 274262921
RMAN-03015: an error has occurred in the script stored memory Script
RMAN-06026: some targets not found - abandonment of restoration
RMAN-06023: no backup or copy of the file 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the command duplicate Db at 15:39:11 01/10/2014
RMAN-05501: abandonment of duplicate target database
Complete recovery manager.
------------------------------------------------------------------
The first mistake of the stack was ORA-19504 while trying to restore the backup of the database.
First thing I took a glance was ASM occupation but it enough available space.
The second was a permission problem, but it doesn't seem to be the case because RMAN can correctly write the controlfile to ASM.
One have some advice on what I should look for?
Thanks in advance sorry for my English.
Select this option.

Hello.

Thanks, but is not the case. As I have said, that the DATA diskgroup has space enough he uses only a single disk in a RAID.

But I solved my problem... To the auxiliary database, I added the following to the spfile:

DB_FILE_NAME_CONVERT = '+ DATA/ProdDB', '+ DATA/OlderDB ".

LOG_FILE_NAME_CONVERT = '+ DATA/ProdDB', '+ DATA/OlderDB ".

I don't know why, but with these two clauses, it worked well. Perhaps RMAN was trying to restore it to the wrong place?

Conversion of ASM controlfile
How to copy a controlfile to an instance of the DSO to a filesystem?

Concerning
Johnnie f
Hello Johnnie,
ASM version do you use?
If it's 11g, you can use the cp command in asmcmd to copy the file on a file system.
If it is 10g, you must use rman.

Liron Amitzi
Consultant senior s/n
[www.dbsnaps.com]

ASM files using RMAN backupset backup system migration

my script to backup daily as below
backup in the format of compressed backupset "$BACKUP_DIR/db_%U" database
backup current controlfile "$BACKUP_DIR/Cont_%U" format
backup as backupset archivelog Tablet format all '$BACKUP_DIR/arch_%U ';
It is possible to migrate the database ASM uses above backup backupset RMAN?
because I restore the database is restored, the problem is when he try to recover it, unable to understand the archivelog and redlog files.

Hello

in fact, after I moved the pieces to another server and called with RMAN (including the archivelog files)

1. When you have moved to another server, then at this stage - my hypothesis, you have restored the controlfile to fileystem and mounted

2. as you said moved to another server, the parts are on file system or (ASM location - still the second server can see)? If your answer is no, when you catalog now, controfile must save it with the file system path but not ASM

Note - If you're still see ASM path then. the migration of the ASM to no - asm (the steps are not correct) logically you went wrong and implementation/execution thrown.

3. provide the plan and execution - what you did (while we can fix). To be honest, while on the move DB to non - asm, why you need first to recovery? Tell me about your backup procedure itself is gone bad.

To be honest, you try to database host of ASM no - asm as backup in function (but no real process of moving). Therefore, in spite of the use of rman backup in dual function duplication... you have implemented in the wrong approach.

This is the reason why I have provided the link and examples to understand.

Hope you understand now.

-Pavan Kumar N

Duplication active with different name of DB
Hello

I am trying to duplicate a primary database in another server db with different name. On the current database of target duplicate for the eve of the database nofilenamecheck of shooting, I am facing ORA-01103: name "ORADB" in the control of the database file is not "11GDB" error. I tried a few other commands of duplication in surfing the internet, but nothing has worked.

DB primary

name of the data base: ORADB

OS: OracleLinux 5

version: 11.2.0.1.0

Watch DB

name: 11GDB

OS: OracleLinux 5

version: 11.2.0.1.0

Both the db runs in ASM diskgroup with different name. The watch below the content of the Standby database pfile.

11GDB.__db_cache_size = 314572800
11GDB.__java_pool_size = 4194304
11GDB.__large_pool_size = 4194304
11GDB.__oracle_base='/U01/app/oracle'#ORACLE_BASE the value of the environment
11GDB.__pga_aggregate_target = 318767104
11GDB.__sga_target = 478150656
11GDB.__shared_io_pool_size = 0
11GDB.__shared_pool_size = 146800640
11GDB.__streams_pool_size = 0
*.audit_file_dest='/U01/app/Oracle/admin/11GDB/adump '
* .audit_trail = "db".
* full = '11.2.0.0.0'
*.control_files='+STDBY/11gdb/controlfile/current.260.788911153'
* .db_block_size = 8192
* .db_create_file_dest = "+ STDBY.
* .db_domain = "
* .db_file_name_convert = '+ DATA', '+ STDBY.
* .db_name = "11GDB".
* .db_unique_name = "11GDB".
*.diagnostic_dest='/U01/app/Oracle '
*. Dispatchers ='(Protocol=TCP) (SERVICE = 11GDBXDB)"
*. FAL_CLIENT = "11GDB."
*. FAL_SERVER = "ORADB".
* .log_archive_config = 'dg_config = (oradb, 11gdb)'
* .log_archive_dest_1 = "LOCATION = + STDBY valid_for = (all_logfiles, all_roles) db_unique_name = 11GDB'"
* .log_archive_dest_2 = "service = ORADB LGWR async valid_for = (online_logfiles, primary_role) db_unique_name = ORADB'"
* .log_archive_dest_STATE_1 = 'ENABLE '.
* .log_archive_dest_state_2 = 'ENABLE '.
* .log_file_name_convert = '+ DATA', '+ STDBY.
* .memory_target = 796917760
* .open_cursors = 300
* runoff = 150
* .remote_login_passwordfile = "EXCLUSIVE."
* .standby_file_management = "AUTO".
* .undo_tablespace = "UNDOTBS1.

Please, someone tell me where it won't.

Kind regards
007
The mentioned error the primary SID is ORADB

Whereas, in the pfile file displayed by you, there name

* .db_name = "11GDB".

db_unique_name may be different but db_name should be the same.

Please make the changes and go ahead and share the output.

Conversion no - ASM ASM!
Dear friends,

I try to convert file system RAC ASM normal fielsystem using the DB with RMAN duplication method. DC, I want to create a new database duplicate of asm source database to normal file system destination. I use the Oracle 11 g R2 on linux. That's why I use the sub process:

'http://oracleinstance.blogspot.com/2010/08/duplicatecloneconvert-asm-file-system.html '.

I have successfully all the steps as below:

(1) take rman backup on/u01/rmanback:

Run {}
Configure channel device type disk format ' / u01/rmanback/%U';
full backup of database format ' / u01/rmanback/%d_%U.bkp' more archivelog format ' / u01/rmanback/%d_%U.bckp';
ARCHIVELOG BACKUP ALL.
}

(2) configure the tns and earphone with success

(3) create pfile as below and place it in $ORACLE_HOME/dbs location:

dupdb.__db_cache_size = 310378496
dupdb.__java_pool_size = 4194304
dupdb.__large_pool_size = 4194304
dupdb.__shared_pool_size = 121634816
dupdb.__streams_pool_size = 0
*.audit_file_dest='/U01/app/Oracle/admin/dupdb/adump '
*.background_dump_dest='/U01/app/Oracle/admin/dupdb/bdump '
* full = '11.2.0.0.0'
*.core_dump_dest='/U01/app/Oracle/admin/dupdb/cdump '
* .db_block_size = 8192
* .db_domain = "
* .db_file_multiblock_read_count = 16
* .db_name = "dupdb.
*.db_recovery_file_dest='/U01/app/Oracle/flash_recovery_area '
* .db_recovery_file_dest_size = 2147483648
*. Dispatchers ='(Protocol=TCP) (SERVICE = dupdbXDB)"
* .job_queue_processes = 10
*.log_archive_format='%t_%s_%r.dbf'
* .open_cursors = 300
* .pga_aggregate_target = 147849216
* runoff = 150
* .remote_login_passwordfile = "EXCLUSIVE."
* .sga_target = 444596224
* .undo_management = "AUTO".
* .undo_tablespace = "UNDOTBS1.
*.user_dump_dest='/U01/app/Oracle/admin/dupdb/udump '

db_file_name_convert ='+ DATA/cars/datafile / ',' / u01/app/oracle/oradata/dupdb /'
log_file_name_convert ='+ DATA/cars/ONLINELOG / ',' / u01/app/oracle/oradata/dupdb /'

4)
create the required directories of bdump, cdump, adump and udump places and also directories for the database files.

5)
Copy the backup files from the source to the target computer to the same directory "rmanback/u01 / '.

6)

rman target $ [oracle@server dbs] = sys / [email protected]:1521 / auxiliary rac.localdomain.

Recovery Manager: release 11.2.0.1.0 - Production on Mon Mar 12 11:27:01, 2012

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

connected to target database: RAC (DBID = 2360197604)
connected to the auxiliary database: DUPDB (unassembled)

RMAN >

(7) the duplication script output:

-----------------------------------------------------------------------------------------------------------------------------------------------
SQL > startup nomount
ORA-32004: outdated or obsolete parameters specified for the instance of RDBMS
ORACLE instance started.

Total System Global Area 442601472 bytes
Bytes of size 2214176 fixed
138413792 variable size bytes
293601280 of database buffers bytes
Redo buffers 8372224 bytes
SQL > exit
Disconnected from the database to Oracle 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production
With partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@server dbs] $
[oracle@server dbs] $ rman auxiliary target=sys/sys123@rac.

Recovery Manager: release 11.2.0.1.0 - Production on Tue Mar 13 10:20:50 2012

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

connected to target database: RAC (DBID = 2360197604)
connected to the auxiliary database: DUPDB (unassembled)

RMAN > duplicate target database to dupdb nofilenamecheck.

From March 13, 12 Db double
using the control file of the target instead of recovery catalog database
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID = 134 type device = DISK

content of Script memory:
{
clone of SQL "create spfile from memory";
}
execution of Script memory

SQL statement: create spfile memory

content of Script memory:
{
clone to stop immediately;
startup nomount clone;
}
execution of Script memory

Instance Oracle to close

connected to the auxiliary database (not started)
Oracle instance started

Total System Global Area 442601472 bytes

Bytes of size 2214176 fixed
142608096 variable size bytes
289406976 of database buffers bytes
Redo buffers 8372224 bytes

content of Script memory:
{
clone of SQL 'alter system set control_files =
"/U01/app/oracle/flash_recovery_area/DUPDB/controlfile/o1_mf_7oxlx2w0_.ctl" comment =
' Set by RMAN "scope = spfile;
clone of SQL 'alter system set = db_name
Comment of "CAR" =.
' Modified by RMAN duplicate "scope = spfile;
clone of SQL 'alter system set db_unique_name =
"DUPDB" comment =
' Modified by RMAN duplicate "scope = spfile;
clone to stop immediately;
Start clone force nomount
Restore controlfile primary clone;
change the clone database mount;
}
execution of Script memory

SQL statement: alter system set control_files = comment "/u01/app/oracle/flash_recovery_area/DUPDB/controlfile/o1_mf_7oxlx2w0_.ctl" = "defined by RMAN" scope = spfile

SQL statement: alter the db_name set = comment system "AS" = "modified by RMAN duplicate" scope = spfile

SQL statement: alter system set db_unique_name = comment "DUPDB" = "modified by RMAN duplicate" scope = spfile

Instance Oracle to close

Oracle instance started

Total System Global Area 442601472 bytes

Bytes of size 2214176 fixed
142608096 variable size bytes
289406976 of database buffers bytes
Redo buffers 8372224 bytes

From restoration to March 13, 12
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID = 134 type device = DISK

channel ORA_AUX_DISK_1: from the restore backup set data file
channel ORA_AUX_DISK_1: restore the control file
channel ORA_AUX_DISK_1: reading from the backup /u01/rmanback/RAC_0vn5n1em_1_1.bkp piece
channel ORA_AUX_DISK_1: part handle=/u01/rmanback/RAC_0vn5n1em_1_1.bkp tag = TAG20120312T173346
channel ORA_AUX_DISK_1: restored the backup part 1
channel ORA_AUX_DISK_1: restoration complete, duration: 00:00:07
output file name=/u01/app/oracle/flash_recovery_area/DUPDB/controlfile/o1_mf_7oxlx2w0_.ctl
Finished restore at March 13, 12

mounted database
RMAN-05529: WARNING: DB_FILE_NAME_CONVERT gave rise to incorrect ASM names; names have been changed to the disk only group.

content of Script memory:
{
until the SNA 7413726.
the value of newname for datafile 1 to
"/ u01/app/oracle/oradata/dupdb/system.265.772215015";
the value of newname for datafile 2 to
"/ u01/app/oracle/oradata/dupdb/sysaux.266.772215039";
the value of newname for datafile 3 to
"/ u01/app/oracle/oradata/dupdb/undotbs1.267.772215049";
the value of newname for datafile 4 to
"/ u01/app/oracle/oradata/dupdb/users.268.772215051";
the value of newname for datafile 5 to
"/ u01/app/oracle/oradata/dupdb/undotbs2.276.772216083";
the value of newname for datafile 6 to
"/ u01/app/oracle/oradata/dupdb/test.286.772637303";
restoration
clone database
;
}
execution of Script memory

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

executing command: SET NEWNAME

From restoration to March 13, 12
using the ORA_AUX_DISK_1 channel

channel ORA_AUX_DISK_1: from the restore backup set data file
channel ORA_AUX_DISK_1: specifying datafile (s) to restore from backup set
channel ORA_AUX_DISK_1: restore datafile 00001 to /u01/app/oracle/oradata/dupdb/system.265.772215015
channel ORA_AUX_DISK_1: restore datafile 00002 to /u01/app/oracle/oradata/dupdb/sysaux.266.772215039
channel ORA_AUX_DISK_1: restore datafile 00003 to /u01/app/oracle/oradata/dupdb/undotbs1.267.772215049
channel ORA_AUX_DISK_1: restore datafile 00004 in /u01/app/oracle/oradata/dupdb/users.268.772215051
channel ORA_AUX_DISK_1: restore datafile 00005 to /u01/app/oracle/oradata/dupdb/undotbs2.276.772216083
channel ORA_AUX_DISK_1: restore datafile to /u01/app/oracle/oradata/dupdb/test.286.772637303 00006
channel ORA_AUX_DISK_1: reading from the backup /u01/rmanback/RAC_0un5n142_1_1.bkp piece
channel ORA_AUX_DISK_1: part handle=/u01/rmanback/RAC_0un5n142_1_1.bkp tag = TAG20120312T173346
channel ORA_AUX_DISK_1: restored the backup part 1
channel ORA_AUX_DISK_1: restoration complete, duration: 00:02:45
Finished restore at March 13, 12

content of Script memory:
{
switch from clone datafile;
}
execution of Script memory

DataFile 1 passed to the copy of the data file
entry of data copy file RECID = STAMP 8 = 777810427 file name=/u01/app/oracle/oradata/dupdb/system.265.772215015
DataFile 2 passed to the copy of the data file
entry of data copy file RECID = STAMP 9 = 777810427 file name=/u01/app/oracle/oradata/dupdb/sysaux.266.772215039
DataFile 3 to the copy of the data file
entry of data copy file RECID = STAMP 10 = 777810427 file name=/u01/app/oracle/oradata/dupdb/undotbs1.267.772215049
DataFile 4 switched to the copy of the data file
entry of data copy file RECID = STAMP 11 = 777810427 file name=/u01/app/oracle/oradata/dupdb/users.268.772215051
DataFile 5 passed to the copy of the data file
entry of data copy file RECID = STAMP 12 = 777810427 file name=/u01/app/oracle/oradata/dupdb/undotbs2.276.772216083
DataFile 6 switched to the copy of the data file
entry of data copy file RECID = STAMP 13 = 777810427 file name=/u01/app/oracle/oradata/dupdb/test.286.772637303

content of Script memory:
{
until the SNA 7413726.
recover
clone database
delete archivelog
;
}
execution of Script memory

executing command: SET until clause

From pick up to March 13, 12
using the ORA_AUX_DISK_1 channel

starting media recovery

RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of Db in dual at 13/03/2012 10:27:27
RMAN-03015: an error has occurred in the script stored memory Script
RMAN-06053: unable to perform the recovery of the media because of the missing journal
RMAN-06025: no backup log archived for thread 2 with sequence 177 and YVERT departure from 7391253 found to restore
RMAN-06025: no backup log archived for thread 2 with sequence 176 and YVERT departure from 7388346 found to restore
RMAN-06025: no backup log archived for thread 2 with sequence 175 and YVERT departure from 7385846 found to restore
RMAN-06025: no backup log archived for thread 2 with sequence 174 and YVERT departure from 7379952 found to restore
RMAN-06025: no backup log archived for 2 with sequence 173 threading and YVERT departure from 7374414 found to restore
RMAN-06025: no backup log archived for thread 2 with sequence 172 and YVERT departure from 7349294 found to restore
RMAN-06025: no backup log archived for thread 1 with sequence 134 and YVERT departure from 7385852 found to restore
RMAN-06025: no backup log archived for thread 1 with sequence 133 and YVERT departure from 7349318 found to restore

RMAN >
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Now, since I managed to copy and paste the backup with the files on the destination machine archivelogs, then why he seeks the archivelog finally. I try the method several times but every time the database cannot be opened due to the loss of some archivelogs.

My database is mounted and would someone please tell me, is it possible to open the database without missing some archivelogs in this stadium?

Edited by: shipon_97 March 13, 2012 11:52
Check your auxiliary instance alerts log and try to connect it manully

as
sqlplus / as sysdba
Select instance_name, status from v$ instance;

How to create a no - ASM ASM DR 2 nodes (OMF)

All,
I have a need to create a DR on a virtual machine to a single node to a DB of RAC 2 nodes that would be used only as a reporting env. Unfortunately, Google has not given results in this direction. When I read the docs of the oracle, it seems that this is not possible. Someone at - it created such a DR and has steps for him?
References that are in conflict:
Ref 1: If data source files use OMF, you cannot rename using DB_FILE_NAME_CONVERT . "Use of storage no-ASM" address details and options of data managed by OMF files

Ref 2:
- You use the LOG_FILE_NAME_CONVERT parameter to name the standby redo logs if the main and backup databases use different naming conventions for the log files.
- You cannot use the SET NEWNAME or CONFIGURE AUXNAME commands to rename the standby redo log files.
- You cannot use the LOGFILE section of the DUPLICATE command to specify the names of files to the standby redo log files.
Courses in typical errors include:
From backup 26 January 16
using channel ORA_DISK_1
channel ORA_DISK_1: from data file copy
copy of the control file ensures
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of Db in dual at 26/01/2016 05:15:04
RMAN-05501: abandonment of duplicate target database
RMAN-03015: an error has occurred in the script stored memory Script
RMAN-03009: failure of the backup command on 26/01/2016 05:15:04 channel ORA_DISK_1
ORA-17628: error Oracle 19505 returned by remote Oracle Server

Thanks in advance for your suggestions.
aBBy

As I understand it, your question is mainly with primary OMF and OMF - not on the physical database. If so, then the show a duplicate RMAN by defining "db_file_name_convert" isn't a valid option. Pending reason - this setting on the database, and then run the duplicate would lead to the creation of OMF files on the eve.

The best approach would be to use the "set newname for data file" (if the number of data file is less) or you can go with the 'set newname for the database' option too.

Happens to your other concern about how the day before would work if 'db_file_name_convert' is not defined. It's true, if a data file is added on the primary (I'm talking about the OMF files), the file would not be reflected or automatically created on the standby database (even if you set standby_file_management true) as 'db_file_name_convert' is not defined. In this case, manual intervention is necessary. An entry could be created for the newly added 'no FILE NAME"data file on the database pending and which will have to be renamed according to the system non - OMF file you want. Thus, overall, to solve OMF datafiles on the primary database no omf files of the database data pending, you need manual intervention.

You can see the messages of this kind in the alerts log:

WARNING: OMF is enabled on this database. Creating a physical

standby controlfile, when OMF is enabled on the primary

database, requires manual intervention by RMAN to solve the OMF

the data file paths.

HTH

-Jonathan Rolland

That means recommended recommended for an ASM diskgroup to maintain production database?

Dear Experts,
That means recommended recommended for an ASM diskgroup to maintain production database?
+ DATA
to keep the redo log groups redo1a, redo2a, redo3a with 3 members = redo1b, redo2b, redo3b, redo1c, redo2c, redo3c
to organize 3 controlfiles
organize storage of data files
to keep the index tablespaces
How many disk (as a point of reference)
+ FRA
Where to place archivelogs
Thanks in advance,
Kind regards
IVW

Salvation;

A good practice is:

+ DATA holds:
- Redo log files, Member 1.
- Control file.
- Data files.
+ FRA holds:
- Redo log files, Member of the 2.
- Control file
- Backup of files: archived redo logs, control automatic file backups, spills auto backups, copies, backup sets, flashback logs.
This is the distribution of files most used; but always distribution will depend on the size of your database and how do you set up your database. Remember that you need to know how your database works. As Aman said in another post, distribution of files depends on how many disk groups you can have, depending on the speed of the disc.

Kind regards.

Willy

: Error communication with ASM slave; 20344 termination process

Hello
My db version: 11 GR 2
When im waiting for my instance creation is shown like this... acutally my prod to + ASM .im created my standby instance is non - asm is there any problem with Controlfiles?

How you create the database pending?

What are the other messages are found in the log of alerts? There is no problem with the control on which file it is, but he must know how have the parameters there are resolved.

Hope that helps you to create a physical primary ASM wait (Doc ID 787793.1)

You could also hit a bug RMAN RESTORE from ASM to no - ASM fails with ORA-03113 ORA-01403 / shows Alert.log slave communication error with the ASM (Doc ID 1368809.1)

-Jonathan Rolland

12 c DB Upgrade and migration of the ASM

Hello Experts,
Need some advice here,
We currently have a database with 11.2.0.3 running standalone on FS & owned by the user of the OS "XYZ". Accordingly, we have already made as a result of tasks,
1. already installed Oracle 12 c rack single node. (OS - oracle user)
2 set up ASM & disks created according to the needs. (OS - oracle user)
3 installed 12 c (12.1.0.2) RDBMS binaries (OS - oracle user)
Now, we wanted to do next,
1 upgrade of database existing at 12 c
2 migrate filesystem to ASM
To do this, we already referred a few documents and use the DBUA inplace upgrade. However, my question is, since the database existing is the property of "xyz" OS user & now we want to change the property of the user 'oracle' OS, there will be no problem around upgrading? We need to take care of things when doing this?
Please notify.
Thank you
Abhijit-

What questions are: group owner and permissions on the database files, controlfiles and redo logs.

(I guess that all other folders - for example the archivelogs if on file systems - are created under the new 'oracle' user)

You can use chown to change the owner: group files (database, controlfile, redolog) until you start DBUA.

Hemant K Collette

Assignment of names manually in ASM files

Version of grid infrastructure: 11.2.0.4
RDBMS Version: 11.2.0.4
When you have an ASM filesystem, you can add a file of data using Method1 or methode2 below.
Name the files manually using the method 1 (non - OMF) is not recommended. But I don't remember why? Anyone know?

-Method1 (non - OMF)
ALTER TABLESPACE CSE_TBS add DATAFILE '+ UIM_DATA/eimprod/datafile/cse_tbs_03.dbf' size 10g autoextend on next 100 m MAXSIZE 32767 m;
-Methode2 (OMF leaving decide the file naming)
ALTER TABLESPACE CSE_TBS add DATAFILE '+ UIM_DATA' size 10g autoextend on next 100 m MAXSIZE 32767 m;

ASM starts is only designed to manage Oracle data files. Whether or not, you use OMF ASM knows Oracle databases and put in the right place including the optimum settings for the distribution and duplication, without worrying. When you specify the name of the data file, ASM will always create a data using OMF file, but it will create an additional ALIAS according to the name you specified. I'm not sure if not using OMF is really recommended, but it can really be any advantage and quite confusing.

Duplication of controlfile in ASM

Similar Questions

Maybe you are looking for