Rename logfile in ASM

Is there any way we can rename a logfile that is in ASM without dropping it and re-creating it?
alter database rename file '+DATA1/vmracdev/onlinelog/redog16l1_fprcprod.log' to '+DATA1/vmracdev/onlinelog/redog16l1_vmracdev.log';
alter database rename file '+DATA1/vmracdev/onlinelog/redog16l1_fprcprod.log' to '+DATA1/vmracdev/onlinelog/redog16l1_vmracdev.log'
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01512: error renaming log file DATA1/vmracdev/onlinelog/redog16l1_fprcprod.log - new file DATA1/vmracdev/onlinelog/redog16l1_vmracdev.log not found
ORA-17503: ksfdopn:2 Failed to open file +DATA1/vmracdev/onlinelog/redog16l1_vmracdev.log
ORA-15173: entry 'redog16l1_vmracdev.log' does not exist in directory 'onlinelog'

there is actually no 'cp' command in asmcmd. Which command did you mean?
Another question for you. I currently have 8 log groups (g9 to g16). Can I get rid of the following entries?
ASMCMD> ls -al +DATA1/vmracdev/onlinelog
Type Redund Striped Time Sys Name
ONLINELOG UNPROT FINE APR 08 14:00:00 Y +DATA1/VMRACDEV/redo01.log => group_1.259.651167685
ONLINELOG UNPROT FINE APR 08 15:00:00 Y +DATA1/VMRACDEV/ONLINELOG/redog10l1_vmracdev.log => group_10.356.651509911
ONLINELOG UNPROT FINE APR 08 15:00:00 Y +DATA1/VMRACDEV/ONLINELOG/redog11l1_vmracdev.log => group_11.357.651509917
ONLINELOG UNPROT FINE APR 08 15:00:00 Y +DATA1/VMRACDEV/ONLINELOG/redog12l1_vmracdev.log => group_12.358.651509925
ONLINELOG UNPROT FINE APR 08 15:00:00 Y +DATA1/VMRACDEV/ONLINELOG/redog13l1_fprcprod.log => group_13.350.651433179
ONLINELOG UNPROT FINE APR 08 15:00:00 Y +DATA1/VMRACDEV/ONLINELOG/redog14l1_fprcprod.log => group_14.351.651433185
ONLINELOG UNPROT FINE APR 08 15:00:00 Y +DATA1/VMRACDEV/ONLINELOG/redog15l1_fprcprod.log => group_15.352.651433189
ONLINELOG UNPROT FINE APR 08 15:00:00 Y +DATA1/VMRACDEV/ONLINELOG/redog16l1_fprcprod.log => group_16.353.651433193
ONLINELOG UNPROT FINE APR 08 14:00:00 Y +DATA1/VMRACDEV/redo02.log => group_2.260.651167687
ONLINELOG UNPROT FINE APR 08 14:00:00 Y +DATA1/VMRACDEV/redo03.log => group_3.274.651169505
ONLINELOG UNPROT FINE APR 08 14:00:00 Y +DATA1/VMRACDEV/redo04.log => group_4.275.651169513
ONLINELOG UNPROT FINE APR 08 14:00:00 Y +DATA1/VMRACDEV/redo05.log => group_5.261.651167689
ONLINELOG UNPROT FINE APR 08 14:00:00 Y +DATA1/VMRACDEV/redo06.log => group_6.262.651167691
ONLINELOG UNPROT FINE APR 08 14:00:00 Y +DATA1/VMRACDEV/redo07.log => group_7.263.651167691
ONLINELOG UNPROT FINE APR 08 14:00:00 Y +DATA1/VMRACDEV/redo08.log => group_8.264.651167693
ONLINELOG UNPROT FINE APR 08 15:00:00 Y +DATA1/VMRACDEV/ONLINELOG/redog9l1_vmracdev.log => group_9.355.651509903
N redog10l1_vmracdev.log => +DATA1/VMRACDEV/ONLINELOG/group_10.356.651509911
N redog11l1_vmracdev.log => +DATA1/VMRACDEV/ONLINELOG/group_11.357.651509917
N redog12l1_vmracdev.log => +DATA1/VMRACDEV/ONLINELOG/group_12.358.651509925
N redog13l1_fprcprod.log => +DATA1/VMRACDEV/ONLINELOG/group_13.350.651433179
N redog14l1_fprcprod.log => +DATA1/VMRACDEV/ONLINELOG/group_14.351.651433185
N redog15l1_fprcprod.log => +DATA1/VMRACDEV/ONLINELOG/group_15.352.651433189
N redog16l1_fprcprod.log => +DATA1/VMRACDEV/ONLINELOG/group_16.353.651433193
N redog9l1_vmracdev.log => +DATA1/VMRACDEV/ONLINELOG/group_9.355.651509903
Message was edited by:
JrOraDBA

Similar Messages

Create logfile using ASM

Hello All,
I am getting following errors in RAC standby Node 1 database.
ORA-00313: open failed for members of log group 23 of thread 1
RFS[2]: No standby redo logfiles of size 102400 blocks available
RFS[2]: Opened log for thread 1 sequence 146 dbid 1483762860 branch 732196712
Wed Oct 13 15:35:21 2010
Errors in file /u01/app/oracle/diag/rdbms/mdm1/MDM11/trace/MDM11_arc1_8609.trc:
ORA-00313: open failed for members of log group 21 of thread 1
Wed Oct 13 15:35:21 2010
Errors in file /u01/app/oracle/diag/rdbms/mdm1/MDM11/trace/MDM11_arc0_8607.trc:
ORA-00313: open failed for members of log group 21 of thread 1
Errors in file /u01/app/oracle/diag/rdbms/mdm1/MDM11/trace/MDM11_arc0_8607.trc:
ORA-00313: open failed for members of log group 21 of thread 1
Errors in file /u01/app/oracle/diag/rdbms/mdm1/MDM11/trace/MDM11_arc0_8607.trc:
ORA-00313: open failed for members of log group 21 of thread 1
ARC0: Archiving not possible: error count exceeded
Trace file says
DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
ORA-00312: online log 21 thread 1: '+MDMDG1/mdm1/onlinelog/group_21.314.732284813'
ORA-00312: online log 21 thread 1: '+MDMDG2/mdm1/onlinelog/group_21.390.732284813'
*** 2010-10-13 15:04:24.216 4529 kcrr.c
ORA-16014: log 21 sequence# 131 not archived, no available destinations
ORA-00312: online log 21 thread 1: '+MDMDG1/mdm1/onlinelog/group_21.314.732284813'
ORA-00312: online log 21 thread 1: '+MDMDG2/mdm1/onlinelog/group_21.390.732284813'
and when I try to open the database
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-10458: standby database requires recovery
ORA-01157: cannot identify/lock data file 16 - see DBWR trace file
ORA-01111: name for data file 16 is unknown - rename to correct file
ORA-01110: data file 16:
'/u01/app/oracle/product/11.2.0/dbhome_1/dbs/UNNAMED00016'
I am not sure what is the problem and what to fix.
Thanks.

[oracle@rs1pre91dvdbaa01 ~]$ cat /u01/app/oracle/diag/rdbms/mdm1/MDM11/trace/MDM11_arc1_8609.trc
Trace file /u01/app/oracle/diag/rdbms/mdm1/MDM11/trace/MDM11_arc1_8609.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1
System name: Linux
Node name: rs1pre91dvdbaa01.pre.ccosvc.com
Release: 2.6.18-194.11.3.el5
Version: #1 SMP Mon Aug 23 15:51:38 EDT 2010
Machine: x86_64
Instance name: MDM11
Redo thread mounted by this instance: 1
Oracle process number: 35
Unix process pid: 8609, image: [email protected] (ARC1)
*** 2010-10-13 15:10:20.313
*** SESSION ID:(406.2) 2010-10-13 15:10:20.313
*** CLIENT ID:() 2010-10-13 15:10:20.313
*** SERVICE NAME:() 2010-10-13 15:10:20.313
*** MODULE NAME:() 2010-10-13 15:10:20.313
*** ACTION NAME:() 2010-10-13 15:10:20.313
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 21 of thread 1
*** 2010-10-13 15:15:20.506
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 21 of thread 1
DDE: Problem Key 'ORA 313' was flood controlled (0x1) (no incident)
*** 2010-10-13 15:20:20.756
ORA-00313: open failed for members of log group 21 of thread 1
ORA-00313: open failed for members of log group 21 of thread 1
*** 2010-10-13 15:25:21.228
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 21 of thread 1
*** 2010-10-13 15:30:21.550
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 21 of thread 1
DDE: Problem Key 'ORA 313' was flood controlled (0x5) (no incident)
*** 2010-10-13 15:35:21.835
ORA-00313: open failed for members of log group 21 of thread 1
ORA-00313: open failed for members of log group 21 of thread 1
*** 2010-10-13 15:40:22.121
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 21 of thread 1
*** 2010-10-13 15:45:22.422
DDE rules only execution for: ORA 313
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----
ORA-00313: open failed for members of log group 21 of thread 1
DDE: Problem Key 'ORA 313' was flood controlled (0x5) (no incident)
*** 2010-10-13 15:50:22.674
ORA-00313: open failed for members of log group 21 of thread 1
ORA-00313: open failed for members of log group 21 of thread 1

Script redo migration to asm win2003 10.2.0

I am trying this script for online log migartion to ASM(found on the internet)
my databse name is orcl, asm instance is +ASM using 10.2.0 on win 2003
also i already done the previous steps correctly when i am firing this sql script its show me error:
can somebody tell me where i am wrong.
SQL> @C:\a.sql;
39 /
declare
ERROR at line 1:
ORA-00349: failure obtaining block size for '+TESTDB_DATA1'
ORA-06512: at line 26
here is the script:
set serveroutput on
declare
cursor rlc is
select group# grp, thread# thr, bytes/1024 bytes_k, 'NO' srl
from v$log
union
select group# grp, thread# thr, bytes/1024 bytes_k, 'YES' srl
from v$standby_log
order by 1;
stmt varchar2(2048);
swtstmt varchar2(1024) := 'alter system switch logfile';
ckpstmt varchar2(1024) := 'alter system checkpoint global';
begin
for rlcRec in rlc loop
if (rlcRec.srl = 'YES') then
stmt := 'alter database add standby logfile thread ' ||
rlcRec.thr || ' ''+TEST'' size ' ||
rlcRec.bytes_k || 'K';
execute immediate stmt;
stmt := 'alter database drop standby logfile group ' || rlcRec.grp;
execute immediate stmt;
else
stmt := 'alter database add logfile thread ' ||
rlcRec.thr || ' ''+TEST'' size ' ||
rlcRec.bytes_k || 'K';
execute immediate stmt;
begin
stmt := 'alter database drop logfile group ' || rlcRec.grp;
dbms_output.put_line(stmt);
execute immediate stmt;
exception
when others then
execute immediate swtstmt;
execute immediate ckpstmt;
execute immediate stmt;
end; end if;
end loop;
end;

I can't debug your script, but I can tell you that it is much easier to "migrate" your logfiles to ASM.
You point your DB_CREATE_FILE_DEST parameter to the database area diskgroup (if not already set)
You point your DB_RECOVERY_FILE_DEST parameter to the recovery area (if not already set)
You look at the old logfiles and remember their number
Then you say
alter database add logfile;
as many times as you want to have new loggroups to be on ASM
Then you drop all the old loggroups.
That is done interactively (in about 5 minutes), though.
But you could script that with a .sql script also quiet easily, instead of "breaking your fingers" with PL/SQL, couldn't you? :-)
Kind regards
Uwe
http://uhesse.wordpress.com

Oracle RAC 10g: ASM can't start in one node.

Hi all,
I succesfully installed RAC in Enterprise Linux. Node1 starts correctly (ASM and DB) but Node2 doesn´t. This is the error in Node2 when I try to startup de ASM instance:
SQL> startup
ASM instance started
Total System Global Area 92274688 bytes
Fixed Size 1217884 bytes
Variable Size 65890980 bytes
ASM Cache 25165824 bytes
ORA-15032: not all alterations performed
ORA-15130: diskgroup "DG1" is being dismounted
ORA-15066: offlining disk "VOL1" may result in a data loss
Any ideas?
Thanks!

Hi, you will must check the configuration of your shared storage, maybe the problem is there, you can verify the some log information in the clusterware layer, and you can find more information in the bdump directory of ASM Instance.
Please paste here the alert logfile of ASM Instance.
Luck.
Have a good day.

Error during restore/recovery and 'open resetlogs'

Hello forum. I'm attempting to restore a database to a new host and have run into an error during the opening of the database (with resetlogs). The renaming of the datafiles, restore, switching of datafiles, and recovery are all done by an rman script, the contents of which are below:
# Restore production database to DR site using file system
# instead of ASM
run {
set newname for datafile 1 to '/opt/oracle/product/10gR2/oradata/DB01/system.dbf';
set newname for datafile 2 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf';
set newname for datafile 3 to '/opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf';
set newname for datafile 4 to '/opt/oracle/product/10gR2/oradata/DB01/users.dbf';
set newname for datafile 5 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf';
set newname for datafile 6 to '/opt/oracle/product/10gR2/oradata/DB01/file1.dbf';
set newname for datafile 7 to '/opt/oracle/product/10gR2/oradata/DB01/file2.dbf';
restore database;
switch datafile all;
recover database;
I get the following output:
RMAN> @/home/oracle/scripts/rman_dr.rman
RMAN> # Restore production database to DR site using file system
2> # instead of ASM
3> #
4> run {
5> set newname for datafile 1 to '/opt/oracle/product/10gR2/oradata/DB01/system.dbf';
6> set newname for datafile 2 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf';
7> set newname for datafile 3 to '/opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf';
8> set newname for datafile 4 to '/opt/oracle/product/10gR2/oradata/DB01/users.dbf';
9> set newname for datafile 5 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf';
10> set newname for datafile 6 to '/opt/oracle/product/10gR2/oradata/DB01/file1.dbf';
11> set newname for datafile 7 to '/opt/oracle/product/10gR2/oradata/DB01/file2.dbf';
12>
13> restore database;
14> switch datafile all;
15> recover database;
16> }
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 03-JAN-08
Starting implicit crosscheck backup at 03-JAN-08
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 651 objects
Finished implicit crosscheck backup at 03-JAN-08
Starting implicit crosscheck copy at 03-JAN-08
using channel ORA_DISK_1
Crosschecked 1 objects
Finished implicit crosscheck copy at 03-JAN-08
searching for all files in the recovery area
cataloging files...
no files cataloged
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /opt/oracle/product/10gR2/oradata/DB01/system.dbf
restoring datafile 00002 to /opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf
restoring datafile 00003 to /opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf
restoring datafile 00004 to /opt/oracle/product/10gR2/oradata/DB01/users.dbf
restoring datafile 00005 to /opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf
restoring datafile 00006 to /opt/oracle/product/10gR2/oradata/DB01/file1.dbf
restoring datafile 00007 to /opt/oracle/product/10gR2/oradata/DB01/file2.dbfchannel ORA_DISK_1: reading from backup piece /ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642899284.1.1.bus
channel ORA_DISK_1: restored backup piece 1
piece handle=/ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642899284.1.1.bus tag=20080101_LV0_DB
channel ORA_DISK_1: restore complete, elapsed time: 01:22:28
Finished restore at 03-JAN-08
datafile 1 switched to datafile copy
input datafile copy recid=14 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/system.dbf
datafile 2 switched to datafile copy
input datafile copy recid=15 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf
datafile 3 switched to datafile copy
input datafile copy recid=16 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf
datafile 4 switched to datafile copy
input datafile copy recid=17 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/users.dbf
datafile 5 switched to datafile copy
input datafile copy recid=18 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf
datafile 6 switched to datafile copy
input datafile copy recid=19 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/file1.dbf
datafile 7 switched to datafile copy
input datafile copy recid=20 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/file2.dbf
Starting recover at 03-JAN-08
using channel ORA_DISK_1
starting media recovery
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=2 sequence=1005
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=1365
channel ORA_DISK_1: reading from backup piece /ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642900444.1.1.bus
channel ORA_DISK_1: restored backup piece 1
piece handle=/ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642900444.1.1.bus tag=20080101_LV0_DB
channel ORA_DISK_1: restore complete, elapsed time: 00:00:05
archive log filename=/opt/oracle/product/10gR2/db/flash_recovery_area/DB01/archivelog/2008_01_03/o1_mf_1_1365_3qtshnfv_.arc thread=1 sequence=1365
archive log filename=/opt/oracle/product/10gR2/db/flash_recovery_area/DB01/archivelog/2008_01_03/o1_mf_2_1005_3qtshncz_.arc thread=2 sequence=1005
channel default: deleting archive log(s)
archive log filename=/opt/oracle/product/10gR2/db/flash_recovery_area/DB01/archivelog/2008_01_03/o1_mf_1_1365_3qtshnfv_.arc recid=2418 stamp=643049236
unable to find archive log
archive log thread=1 sequence=1366
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/03/2008 16:47:22
RMAN-06054: media recovery requesting unknown log: thread 1 seq 1366 lowscn 181804603
RMAN> **end-of-file**
I searched for a decription of the 06054 error, and found that if the archive logs weren't available, then to run "alter database open resetlogs;", which I did. Here's the output:
RMAN> alter database open resetlogs;
database opened
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
ORACLE error from target database:
ORA-06553: PLS-801: internal error [56319]
I've done all of this twice now, with the same result. I've googled PLS-801 and found more than a few instances of people getting this code, but not during a database open after a restore. Can anyone shed some light on what might have gone wrong? In the interest of brevity, I left out the rest of the restore process prior to running the database restore, but other than setting "compatible" and "db_recovery_file_dest_size", it was all by the book.
Thanks in advance.

Thanks for the reply Pierre.
I am not using RMAN Duplicate. Yes, the source of the backup is an RAC. The destination is a single server, with the DB on the filesystem. Here's an overview of of the commands I ran and the procedure.
Copied tar'd backup controlfile and datafiles to destination machine. Untar'd. Install 10.2.0.1.0 on destination machine, patch to 10.2.0.2.0.
OS> sqlplus /nologin
SQL> alter system set compatible = '10.2.0.2.0' scope=spfile;
SQL> alter system set db_recovery_dest_file_size = '8g'; scope spfile;
SQL> shutdown immediate;
SQL> startup; (to verify changes took...)
SQL> shutdown immediate;
OS> Copy control file from untar'd dir and place in $ORACLE_HOME/dbs/, truncate name to c-DBID-date-00.
OS> rman target /
RMAN> startup nomount;
RMAN> set dbid <dbid from control file>;
RMAN> restore controlfile from autobackup; (finds control file with no problem...)
RMAN> alter database mount;
RMAN> @/home/oracle/rman_dr.rman (script cited in first post, to rename datafiles from ASM to filesystem, restore, switch files, and recover...)
RMAN> alter database open resetlogs; (as cited before...)
If I'm not using Duplicate and not specifying dates, the UNTIL/SET UNTIL commands aren't necessary, correct?

Post activity for drop & recreating log group

Hi,
We need to drop redolog group from old file system & going to recreate in different file system.
ex,
when group 3 is in "INACTIVE"
alter database drop logfile group 3;
alter database add logfile group 3 ('/u01/oracle/ica01/log3.ora,'/u01/oracle/ica02/log3.ora’ ) size 2G;
Is there any post activity to update in control files or any other things ?
Thx,
Gowin.

Osama_mustafa wrote:
you need to rename logfile on OS Level "Physically" or you move them to another location.
http://docs.oracle.com/cd/B28359_01/server.111/b28310/onlineredo004.htm
That's if you are moving an existing file. The OP was asking about dropping an existing file and creating a new one. While the purpose may be the same (to relocate a file), the technique is vastly different and so the answer to his question is vastly different.
To the OP: as you described your actions of dropping a redo log group and "recreating" it, the answer is no, there is no follow up work to be done. You did two logically un-connected actions:
First, you dropped a redo log group. Fine. That is easily done online with no impact to the users and requires no follow-up actions.
Second, you created a redo log group. Fine. That is easily done online with no impact to the users and requires no follow-up actions.
The fact that the new redo log group has the same group name as the former - now non-existent - group is merely coincidental.

ORA-17503: ksfdopn:2 Failed to open file +M0347_DG1/m0347/spfilem0347.ora ORA-15001

ASM database version:11.2.0.3
Getting below error in both alert logfile of ASM in two node cluster.
============
Errors in file /u02/diag/asm/+asm/+ASM1/trace/+ASM1_ora_86521.trc:
ORA-17503: ksfdopn:2 Failed to open file +M0347_DG1/m0347/spfilem0347.ora
ORA-15001: diskgroup "M0347_DG1" does not exist or is not mounted
Same thing is written in trace file as well.
There is only one database P0347 is running and diskgroup M0347_DG1 was for other database M0347 which is discontinued so diskgroup M0347_DG1 was dropped.
But why it is looking for spfilem0347.ora, please let me know how to rectify it.

ORA-17503: ksfdopn:2 Failed to open file +M0347_DG1/m0347/spfilem0347.ora
The database P0347 has nothing to do with the issue . right?
Probally you don't removed database M0347 from OCR and CRS was trying to start database.
Using $ORACLE_HOME of Database
$ srvctl config database -d M0347
If it's registered in OCR you should remove it.
This command will remove database.
$ srvctl remove database -d M0347
Check if Diskgroup is registred.
Using $ORACLE_HOME of GI
$ srvctl config diskgroup -g M0347
If registered in OCR you can remove it.
$ srvctl remove diskgroup -g M0347

Rename asm instance in RAC

Hello,
ClusterWare 11.2.0.3 + RAC db same version .
I need to rename one of the ASM instances
How can this be done ?
the situation is as follows , I needed to take one of the server out of the cluster and then bring him back in .
when I have added him , he got a new ASM instance name (was ASM1 now it got ASM3 , 2 node rac) ,
thanks
S.

Sahar wrote:
ClusterWare 11.2.0.3 + RAC db same version .
I need to rename one of the ASM instancesNo you don't. Supply reasons and justification for wanting to changes the SID of an ASM instance,
the situation is as follows , I needed to take one of the server out of the cluster and then bring him back in .
when I have added him , he got a new ASM instance name (was ASM1 now it got ASM3 , 2 node rac) ,So? What is wrong with an instance called +ASM3 in a 2 node RAC? How does that now reduce and impair cluster functionality?

Is it possible to rename an ASM folder?

i want to rename an ASM folder containing my database:
+DBDNL2_G2_DATA_AREA/EVJA/DATAFILE
to
+DBDNL2_G2_DATA_AREA/DITOC/DATAFILE
I do not want any file movement or file copying, just rename the folder and afterwards I rename the datafiles of the database. is this possible?
Regards,
Tim

You can't. This folder is the name of Your database and it's a part Oracle Managed Files hieararchy.
You can make directory DITOC and then make aliases to Your db files.

Can The ASM Disk Header and Disk Group Be Renamed?

I have a requirement to mount multiple SAN clones (EMC Symclone) of a production ASM instance on the same development server. RMAN is too slow to be an option, unless I find a white paper explaining any way to make RMAN perform a clone faster than the SAN.
The default response is normally, "Do your clone to dedicated hardware." However, that answer is not an option for obvious financial reasons, especially since I am working with a RAC environment with ~10 development and test environments.
The only way to do this (that I can think of) is to rename the disk header and probably the disk group prior to making it available to the ASM instance.
I have heard that Oracle has come up with an undocumented solution for one or more businesses. I believe it has something to do with the kfed library located in $ORACLE_HOME/rdbms/lib.
Has anyone out there managed to do this? If so, can you share your solution or point me in the right direction?
I know I am not the only one out there looking for a solution to this issue...
Thanks in advance.

This is absolutely possible. Can be done via kfed. I never found the answer searching the net and had to figure it out. Here it is in hopes that it helps someone else. DISCLAIMER.... If you screw up your disks don't blame me. If you have any questions about this you can email me: [email protected]
The procedure is basically this:
- compile kfed
- dump the disk header with kfed
- Modify the dump file
- write the dump back to the disk header.
** Changing ANYTHING other than the diskgroup name will render your disks useless.
Here is a script to do the work for you:
for file in `ls /dev/vx/rdsk/as1_pccdw/asmdata*`
do
echo "Processing DATA disk $file ..."
search=ASCDW_DATA
replace=AS1CDW_DATA
newlength=`echo $replace | wc -m`
let newlength=$newlength-1
shortname=`echo $file | cut -f 6 -d /`
kfed op=read dev=$file | sed -e '24,24s/ '$search' / '$replace' /' -e '24,24s/length=.*/length='$newlength'/' > /tmp/$shortname.kfed
kfed op=write dev=$file text=/tmp/$shortname.kfed CHKSUM=YES
done
for file in `ls /dev/vx/rdsk/as1_pccdw/asmredo*`
do
echo "Processing REDO disk $file ..."
search=ASCDW_REDO
replace=AS1CDW_REDO
newlength=`echo $replace | wc -m`
let newlength=$newlength-1
shortname=`echo $file | cut -f 6 -d /`
kfed op=read dev=$file | sed -e '24,24s/ '$search' / '$replace' /' -e '24,24s/length=.*/length='$newlength'/' > /tmp/$shortname.kfed
kfed op=write dev=$file text=/tmp/$shortname.kfed CHKSUM=YES
done
Edited by: user4630111 on Nov 10, 2008 6:03 PM

How to rename ASM diskgroups after having cloned the original disks to the same server. ASMlib is used

Linux RHE 6
Oracle Grid single instance (Oracle Restart) 11.2.0.4 installed
Oracle RDBMS 11.2.0.4 installed
One 11.2.0.4 database single instance running
Our ASM have DATA, REDO, FRA diskgroup mounted
We need to do a storage snapshot for creating on THE SAME server a copy of the current ASM diskgroups DATA, REDO, FRA. Then we would rename the cloned diskgroups using renamedg command.
We have done this operation several times when ASMlib is not used. The command used when ASMlib is not used is for example:
renamedg dgname=FRA newdgname=FRA2 verbose=true phase=both asm_diskstring='/dev/oracle/fra*'
With ASMlib in use I am not sure about the steps to follow
First I am not sure about what to provide to the asm_diskstring parameter of the renamedg command. I need to provide an asm_diskstring which identifies the path pointing to the disks belonging to the cloned diskgroup (I do not want to rename the original diskgroup). Though in an ASM instance using ASMlib the parameter asm_diskstring is is ‘ORCL:*’.
Second, I suppose after the diskgroup rename ASMlib would return an error because it would find duplicated disks.
Could you please advise ?
Thanks in advance
Massi

Hi,
As you have OS level clone ,you have same ASMlib label.
ASMlib always mount unique ASMLib label only.
+you need to identify those newly cloned device.
+ Then rename those ASMLib label using force-renamedisk after taking 1Mb disk backup using dd read on one node .
+ Then run scandisks on other nodes .
+ Then validate newly labelled device is mounted or not on all nodes .
$ ls -ltr /dev/oracleasm/disks/*
+ Then run renamedg command with asm_diskstring of /dev/oracleasm/disks/*
Regards,
Aritra

Is there a way to rename an ASM DiskGroup from the Disks in 11g ?

Hello,
I've been looking for that and I didn't find anything except that it may not have been possible with 10g.
I'd like to rename a diskgroup to reuse it in the same ASM instance from a netapp snapclone. Of course I would prefer to do it without any ASM instance accessing it but afterall, if there is a way... (even not supported; it's to enable a set of testing database all together) !
Thank you for your help.
Gregory

Hi Gregory,
since all information about ASM Disk, Diskgroup, etc. are stored directly on the disks there is no way to rename the diskgroup at the moment (hopefully in the future, like a way to change diskgroup redundance).
Only option you have is to create a new diskgroup and copy the datafiles over with either RMAN or DBMS_FILE_TRANSFER. Then rename the file to point to new location. (alter datafile).
But since you want to duplicate it into a different ASM Diskgroup, that will not help you. The option left is to change the Disk Header information directly. Unfortunately I do not have any information about the disk header itself...
Hopefully someone can give you a hint what all to change there if you would DD this to a file change it and store it back...
Regards
Sebastian

Is it possible to rename an ASM alias?

I want to rename my db from dw1 to dw so I also want to rename the ASM alias for the files.
mvalias or rename alias isn't an option. Any ideas?
asmcmd>help
commands:
cd
du
find
help
ls
lsct
lsdg
mkalias
mkdir
pwd
rm
rmalias

PROBLEM!
From the docs: RENAME DIRECTORY Use this clause to change the name of a directory for hierarchically named aliases. This clause is not valid for renaming directories created as part of a system alias. Such directories are labeled with the value Y in the SYSTEM_CREATED column of the V$ASM_ALIAS dynamic performance view.
SQL> select alias_directory,system_created from v$asm_alias where name = 'DW1';
ALI SYS
Y Y
So, if I change my database name, how do I change the ASM alias?

Register logfile manually in asm.

Hi,
My primary databse is on file system having 10.2.0.5 db version.
My standby db is on ASM(11.2.0.2)
Operating system is Windows 2003.
somehow My standby database is not able to capture archivelogs from primary database.
so i want to manually transfer missing archivelogs on standby datbase server and want to manually register the missing archivelogs.
But as my primary db is in file system and standby db is in asm. how i can copy my missing archivelogs in asm diskgroups.
So please let me know wht are the steps to register logfile manually in asm.

919131 wrote:
Hi,
My primary databse is on file system having 10.2.0.5 db version.
My standby db is on ASM(11.2.0.2)
Operating system is Windows 2003.
somehow My standby database is not able to capture archivelogs from primary database.
so i want to manually transfer missing archivelogs on standby datbase server and want to manually register the missing archivelogs.
But as my primary db is in file system and standby db is in asm. how i can copy my missing archivelogs in asm diskgroups.
So please let me know wht are the steps to register logfile manually in asm.Use this link to move Archive files from ASM to normal file system --> http://repettas.wordpress.com/2008/11/01/restore-archive-logs-to-new-location-using-rman/
>
919131
     Newbie
Handle:      919131
Status Level:      Newbie
Registered:      Mar 6, 2012
Total Posts:      13
Total Questions:      7 (7 unresolved)
>
OTN is not helpful to you to resolve your questions, all questions are unanswered, when all questions are unanswered why you are posting here?
Close all old threads and keep the forum clean.
Edited by: CKPT on Jul 3, 2012 6:48 PM

Steps to register logfile manually in asm.

Hi,
My primary databse is on file system having 10.2.0.5 db version.
My standby db is on ASM(11.2.0.2)
Operating system is Windows 2003.
somehow My standby database is not able to capture archivelogs from primary database.
so i want to manually transfer missing archivelogs on standby datbase server and want to manually register the missing archivelogs.
But as my primary db is in file system and standby db is in asm. how i can copy my missing archivelogs in asm diskgroups.
So please let me know wht are the steps to register logfile manually in asm.

Duplicate post: Register logfile manually in asm.
And:
What were you thinking that this should work in the first place ??
Why take a totally other version for the standby database and also select ASM instead of a filesystem to make it even more complex??
Start reading the documentation, like http://docs.oracle.com/cd/B19306_01/server.102/b14239/create_ps.htm
Cheers
FJFranken

Rename logfile in ASM

Similar Messages

Maybe you are looking for