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]

Tags: Database

Similar Questions

Conversion of ASM boutien

Hello
has anyone tried to mount a drive to big endian asm (AIX for example) on little endian env (linux x 86)?
I have a disc which KFED is able to read but ASM is unable to mount because of the incompatibility boutien.
Thank you!
the KFED to read:
kfbh.endian: 0; 0 x 000: 0x00
kfbh. Hard: 130; 0 x 001: 0 x 82
kfbh.type: 1; 0 X 002: KFBTYP_DISKHEAD
kfbh.datfmt: 1; 0 x 003: 0x01
kfbh. Block.BLK: 0; 0 x 004: blk = 0
kfbh. Block.obj: 128; 0 x 008: file = 128
kfbh. Check: 1999209486; 0x00c: 0x7729840e
kfbh. FCN.base: 0; 0 x 010: 0x00000000
kfbh. FCN. Wrap: 0; 0 x 014: 0x00000000
kfbh.spare1: 0; 0 x 018: 0x00000000
kfbh.spare2: 0; 0x01c: 0x00000000
kfdhdb. Driver.provstr: ORCLDISK; 0 x 000: length = 8
kfdhdb. Driver.reserved [0]: 0; 0 x 008: 0x00000000
kfdhdb. Driver.reserved [1]: 0; 0x00c: 0x00000000
kfdhdb. Driver.reserved [2]: 0; 0 x 010: 0x00000000
kfdhdb. Driver.reserved [3]: 0; 0 x 014: 0x00000000
kfdhdb. Driver.reserved [4]: 0; 0 x 018: 0x00000000
kfdhdb. Driver.reserved [5]: 0; 0x01c: 0x00000000
kfdhdb.compat: 4106; 0 x 020: 0x0000100a
kfdhdb.dsknum: 0; 0 x 024: 0x0000
kfdhdb.grptyp: 1; : 0 X 026: KFDGTP_EXTERNAL
kfdhdb.hdrsts: 3; 0 X 027: KFDHDR_MEMBER
kfdhdb.dskname: AIXDG_0000; 0 x 028: length = 10
kfdhdb.grpname: AIXDG; 0 x 048: length = 5
kfdhdb.fgname: AIXDG_0000; 0 x 068: length = 10
kfdhdb.capname:; 0 x 088: length = 0
kfdhdb.crestmp.Hi: 3043620609; 0X0A8: HOUR = 0 X 1 DAYS = 0 X 18 MONTHS = 0XD YEAR = 0X5A7
kfdhdb.crestmp.Lo: 9184640; 0X0AC: USEC = 0 X 180 MS = 0 X 309 SECONDS = 0 X 8 MIN = 0X0
kfdhdb.mntstmp.Hi: 3043620609; 0X0B0: HOUR = 0 X 1 DAYS = 0 X 18 MONTHS = 0XD YEAR = 0X5A7
kfdhdb.mntstmp.Lo: 7910528; 0X0B4: USEC = 0X80 MSEC = 0X22D SECONDS = 0 X 7 MN = 0X0
kfdhdb.secsize: 2; 0x0b8: 0x0002
kfdhdb. BLKSIZE: 16; 0x0ba: 0 x 0010
kfdhdb.ausize: 4096; 0x0bc: 0 x 00001000
kfdhdb. MFACT: 2159804672; 0x0c0: 0x80bc0100
kfdhdb.dsksize: 7864320; 0x0C4: 0 x 00780000
kfdhdb.pmcnt: 33554432; 0x0c8: 0 x 02000000
kfdhdb.fstlocn: 16777216; 0x0cc: 0 x 01000000
kfdhdb.altlocn: 33554432; 0x0d0: 0 x 02000000
kfdhdb.f1b1locn: 33554432; 0x0d4: 0 x 02000000
kfdhdb.redomirrors [0]: 0; 0x0d8: 0x0000
kfdhdb.redomirrors [1]: 0; 0x0da: 0x0000
kfdhdb.redomirrors [2]: 0; 0x0dc: 0x0000
kfdhdb.redomirrors [3]: 0; 0x0de: 0x0000
kfdhdb.dbcompat: 4106; 0x0e0: 0x0000100a
kfdhdb.grpstmp.Hi: 3043620609; 0X0E4: HOUR = 0 X 1 DAYS = 0 X 18 MONTHS = 0XD YEAR = 0X5A7
kfdhdb.grpstmp.Lo: 2630528; 0X0E8: USEC = 380 MS = 208 SECONDS 0 X X 0 = 0 X 2 MIN = 0X0
kfdhdb.vfstart: 0; 0x0ec: 0x00000000
kfdhdb. VFEND: 0; 0x0f0: 0x00000000
kfdhdb. SPFile: 0; 0x0f4: 0x00000000
kfdhdb.spfflg: 0; 0x0f8: 0x00000000
kfdhdb.ub4spare [0]: 0; 0x0fc: 0x00000000
kfdhdb.ub4spare [1]: 0; 0 x 100: 0 x 00000000
kfdhdb.ub4spare [2]: 0; 0 x 104: 0 x 00000000
kfdhdb.ub4spare [3]: 0; 0 x 108: 0 x 00000000
kfdhdb.ub4spare [4]: 0; 0x10c: 0x00000000
kfdhdb.ub4spare [5]: 0; 0 x 110: 0 x 00000000
kfdhdb.ub4spare [6]: 0; 0 x 114: 0 x 00000000
kfdhdb.ub4spare [7]: 0; 0 x 118: 0 x 00000000
kfdhdb.ub4spare [8]: 0; 0x11c: 0x00000000
kfdhdb.ub4spare [9]: 0; 0 X 120: 0 x 00000000
kfdhdb.ub4spare [10]: 0; 0 x 124: 0 x 00000000
kfdhdb.ub4spare [11]: 0; 0 x 128: 0 x 00000000
kfdhdb.ub4spare [12]: 0; 0x12c: 0x00000000
kfdhdb.ub4spare [13]: 0; 0 x 130: 0 x 00000000
kfdhdb.ub4spare [14]: 0; 0 x 134: 0 x 00000000
kfdhdb.ub4spare [15]: 0; 0 x 138: 0 x 00000000
kfdhdb.ub4spare [16]: 0; 0x13c: 0x00000000
kfdhdb.ub4spare [17]: 0; 0 x 140: 0 x 00000000
kfdhdb.ub4spare [18]: 0; 0 x 144: 0 x 00000000
kfdhdb.ub4spare [19]: 0; 0 x 148: 0 x 00000000
kfdhdb.ub4spare [20]: 0; 0x14c: 0x00000000
kfdhdb.ub4spare [21]: 0; 0 x 150: 0 x 00000000
kfdhdb.ub4spare [22]: 0; 0 x 154: 0 x 00000000
kfdhdb.ub4spare [23]: 0; 0 x 158: 0 x 00000000
kfdhdb.ub4spare [24]: 0; 0x15c: 0x00000000
kfdhdb.ub4spare [25]: 0; 0 x 160: 0 x 00000000
kfdhdb.ub4spare [26]: 0; 0 X 164: 0 x 00000000
kfdhdb.ub4spare [27]: 0; 0 x 168: 0 x 00000000
kfdhdb.ub4spare [28]: 0; 0x16c: 0x00000000
kfdhdb.ub4spare [29]: 0; 0 x 170: 0 x 00000000
kfdhdb.ub4spare [30]: 0; 0 x 174: 0 x 00000000
kfdhdb.ub4spare [31]: 0; 0 x 178: 0 x 00000000
kfdhdb.ub4spare [32]: 0; 0x17c: 0x00000000
kfdhdb.ub4spare [33]: 0; 0 x 180: 0 x 00000000
kfdhdb.ub4spare [34]: 0; 0 x 184: 0 x 00000000
kfdhdb.ub4spare [35]: 0; 0 x 188: 0 x 00000000
kfdhdb.ub4spare [36]: 0; 0x18c: 0x00000000
kfdhdb.ub4spare [37]: 0; 0 x 190: 0 x 00000000
kfdhdb.ub4spare [38]: 0; 0 x 194: 0 x 00000000
kfdhdb.ub4spare [39]: 0; 0 x 198: 0 x 00000000
kfdhdb.ub4spare [40]: 0; 0x19c: 0x00000000
kfdhdb.ub4spare [41]: 0; 0x1a0: 0x00000000
kfdhdb.ub4spare [42]: 0; 0x1a4: 0x00000000
kfdhdb.ub4spare [43]: 0; 0x1a8: 0x00000000
kfdhdb.ub4spare [44]: 0; 0x1ac: 0x00000000
kfdhdb.ub4spare [45]: 0; 0x1b0: 0x00000000
kfdhdb.ub4spare [46]: 0; 0x1b4: 0x00000000
kfdhdb.ub4spare [47]: 0; 0x1b8: 0x00000000
kfdhdb.ub4spare [48]: 0; 0x1bc: 0x00000000
kfdhdb.ub4spare [49]: 0; 0x1c0: 0x00000000
kfdhdb.ub4spare [50]: 0; 0x1c4: 0x00000000
kfdhdb.ub4spare [51]: 0; 0x1c8: 0x00000000
kfdhdb.ub4spare [52]: 0; 0x1cc: 0x00000000
kfdhdb.ub4spare [53]: 0; 0x1d0: 0x00000000
kfdhdb.acdb.ABA.SEQ: 0; 0x1d4: 0x00000000
kfdhdb.acdb.ABA.BLK: 0; 0x1d8: 0x00000000
kfdhdb.ACDB.ENTs: 0; 0x1dc: 0x0000
kfdhdb.ACDB.ub2spare: 0; 0x1de: 0x0000

I already tried, will not work and is not supported by Oracle.

Each AU, measurement, etc... have own change ENDIAN, it corrupt manually and ASM block.

https://forums.Oracle.com/thread/2387671

Big-endian files differently to little-endian. In a little-endian file, these bytes are reversed compared with big endian files.

Some compilers have options to generate code that allows global conversion for all file i/o operations. This allows to reuse the code on a system with the "endianness" opposed without having to change the code itself. If the compiler does not support this conversion, the programmer must swap the bytes via ad-hoc code. (I think that ASM is not only)

If you have number 0xDEADBEEF in a big endian platform, in little endian platform system stored in the form 0xEFBEADDE), because you will need a compiler to convert the data, the "kfbh.endian" parameter is only a parameter change will damage you the datablock.

Post edited by: Levi-Pereira

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;

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.

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

Conversion of the ASM
Hi all

What are the steps to migrate from a non - file system asm in a file system of the asm to 10g / 11g.
I guess you want to migrate your data to a plain old ASM file system files. This is possible by creating first ASM on your server and then use rman to copy your data files to ASM diskgroup. Tim Hall put in place this small howto http://www.oracle-base.com/articles/10g/AutomaticStorageManagement10g.php#migrating_to_asm_using_rman

Bjoern

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

Move a file to the ASM system tablespace
Hi DBAs,

I want to convert a tablespace to ASM, I published the following steps

Put the tablespace in readonly mode and connected to the rman as "target rman /'"

RMAN > convert tablespace users format '+ DATA ';

The above command has successfully completed and created a database in asm diskgroup DATA asDATA/oratest/datafile/usrs.244.33333333. But once I request the tablespace datafile, it still points to the old/oradata/user.dbf.

It appears next to the command convert, I need to perform a few extra steps. Please help me what I have to do.

Thank you
-Shaw-
Hello

After the conversion, you must run the command

RMAN > change user tablespace to copy

then only it will update the controlfile

or else

do one thing

RMAN > backup as copy users tablespace format "+ dg /...» »
RMAN > change user tablespace to copy

hope it will work for you, mark it as answered so useful

Thank you

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

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

IM + ASM + DBMS DB cloning

Hello.
I have 1-node RAC deployed 11.2.0.3 on OL5.11 with test DB in ASM (3 x OCR_VOTE discs, discs of DATA 2 x, 2 x discs of FRA).
The goal is to create new cluster using the current cluster as a master and cross DB ASM cloning disks.
Regarding http://docs.oracle.com/cd/E11882_01/rac.112/e41959/clonecluster.htm#CWADD92122 and "HOW to CLONE a 11.2.0.3 HOME AND CLUSTERWARE GRID INFRASTRUCTURE (DOC ID 1413846.1) ' it is necessary to: »»
1. prepare the node
2. deploy the GI
3. Run clon.pl
4. Running config.sh
Steps 1 and 2 in my case have been replaced by:
1. creating a master node in what concerns the docs (remove the cluster configuration and other files vs deleting on direct copy).
2. cloning of disks and the virtual machine
3. change the names and IP addresses
I managed to "running config.sh. But config.sh I am running:
[FATAL] [INS-40401] Setup has detected an Oracle Clusterware House on the system configuration.
Any ideas? Comments?
Thanks in advance for your valuable time.

Problem solved.

Environment:
- VirtualBox.
- 5.11 Linux
- 1-node cluster with ASM (11.2.0.3)
- DBMS (11.2.0.3) installed
- 1 RAC created DB.
ASM disks:
- shareable x 3 ocrvote
- given shareable x 2
- shareable 2 x fra
1. create the pfile to DB file.

2. stop all CARS services, disable the crs.

3. delete the files regarding official documents.

4. clean the files of the OS: logs, tmp, etc..

5 detach GI home

6 detach the DB home

We now have the master node.

1 clone the virtual machine (or disks).

We now have the first node to the new cluster.

1. prepare the conversion table: IPs, names.

2. sign in IP addresses, names in DNS

3. start cloned host.

4. change IP, OS names.

5 remove and create ssh, establish the equivalence for the users of the grid and oracle ssh.

6 redefine the responsibilities of ASM disks.

7 run clone.pl as a user of GI.

8. as root, run the root.sh script.

9 unlock GI.

10 move or delete ocr.loc.

11 start config.sh.

12. check the configuration of the cluster.

13 control the ASM.

14. change the name to scan again.

15 resolving multicast (if necessary)

GI is ready.

To prepare the RAC DBMS.

1. run clone.pl.

2. run the root.sh script.

3 change the DB record.

4 Add the instance.

5 edit tnsnames.ora with the new name of scan.

6 change created pfile initially with the new name of scan.

7. start the DB file pfile.

8. change remote_listener. Create the spfile.

9 start DB.

10. If necessary, it is possible to change the names of groups of DB name, DBID, disks.

We again invite you cluster and new CARS DB.

Disaster recovery with different ASM starts

Hi@all,
in fact, I'm testing a scenario of recovery after a disaster. To an Oracle Linux 6 Server with installed grid below 12 c and Ora Database 11.2.0.4 (there is also a 12.1.0.2 instance of database) I'm doing a recovery after a disaster. But I'm unleashed by the restoration and recovery of the database. The problem here is that ASM diskgroup name has changed. As you read I also changed the physical server, but I think that should not be a problem.
To the old server, I have two ASM starts '+ DATA' and '+ FRA_1', to the new, they are called '+ DATA_SRVNAME' and '+ FRA_SRVNAME '. I already changed the startup in spfile parameter, but now after restoring the controlfile RMAN has directions to the old diksgroup:
```
RMAN> report schema;


using target database control file instead of recovery catalog
RMAN-06139: WARNING: control file is not current for REPORT SCHEMA
Report of database schema for database with db_unique_name SID


List of Permanent Datafiles
===========================
File Size(MB) Tablespace           RB segs Datafile Name
---- -------- -------------------- ------- ------------------------
1    0        SYSTEM               ***     +DATA/SID/datafile/system.438.816606399
```
So I tried three ways. First was rename data file name:
```
ALTER DATABASE RENAME FILE '+DATA/SID/datafile/system.438.816606399' TO '+DATA_SRVNAME/SID/datafile/system.438.816606399';
```
Then had to set the newname in RMAN:
```
set newname for datafile 16 to '+DATA_SRVNAME/SID/datafile/mms_basic_tab.455.816617697/';
```
And the second was to recreate the controlfile with
```
CREATE CONTROLFILE REUSE DATABASE "SID" RESETLOGS ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 254
    MAXINSTANCES 1
    MAXLOGHISTORY 1815
LOGFILE
  GROUP 1 ('+DATA__SRVNAME', '+FRA_SRVNAME')  SIZE 1024M,
DATAFILE
  '+DATASRVNAME/SID/datafile/system.438.816606399',
CHARACTER SET AL32UTF8;
```
But the three methods gave me the error that the file data to the new location is not available (for example):
```
ORA-15012: ASM file '+DATA_QUM169/cogn11/datafile/system.438.816606399' does not exist
```
So now my question: how am I able to say the controlfile or the database to use the another diskgroup in ASM?
I know, the simplest way would be to create a diskgroup + DATA and do the restore / recovery, but on the new server, I have no more storage to assign to a new diskgroup, and because there are running other forums I would'nt change ASM starts.
Do you have anny solution?
A big thank you and best regards,
Dave

Please try this

RMAN > run

{

the value of newname for datafile 1 to "+ DATA_SRVNAME";

restore data file 1;

switch datafile 1;

recover datafile 1;

}

Did you create + diskgroup DATA_SRVNAME?

and

Conversion of ASM controlfile

Similar Questions

Maybe you are looking for