Db_file_name_convert parameter causes ora-15124:asm FILE NAME ' ... ' Containsan invalid alias name

RAC Main Library +DG in a stand-alone environment, once the primary repository has an archive interval before it can be deleted for various reasons, such as the archive being cleaned up, the backup set policy has exceeded the required archive. Do not worry, you can follow the following approximate steps to recover:

o Make an SCN-based incremental backup on the main library

o Transfer the backup to the standby library

o Standby Recovery Incremental backup

o Main Library Create a standby controlfile and transfer it to the standby library

o Control file of the previous step generated control file replacement repository

These days, a very strange problem, the main library created standby Controlfile always error ORA-15124. This problem also bothered myself for many days.

Have tried:

o Check all physical files of the database Asmcmd ls-l to view

o Check the database data dictionary V$database.name/dba_data_files.file_name

o ls-l viewing files in asmcmd debug mode

o Check ASM v$asm_file, V$asm_alias, etc.

O to ORA-15124 do 10046 and Errorstack

o Check DG Backup, etc.

In the creation of standby Controlfile still error, errors are as follows:

Sql> Show parameter conver;

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
Db_file_name_convert String/data, +data/orcl/datafile
Log_file_name_convert String/data, +data/orcl/onlinelog

(in the actual process, these two parameters are so configured that there is no problem ...)

sql> ALTER DATABASE create standby Controlfile as '/tmp/a.ctl ' reuse;
ALTER DATABASE create standby Controlfile as '/tmp/a.ctl ' reuse
*
ERROR at line 1:
Ora-15124:asm file name ' +data/odsptdb+datafile/system.259.862837403 ' Containsan Invalid alias name

The above bold part of the string is where the expression is very questionable!

Finally, the configuration of the Db_file_name_convert parameter is checked and the following tests are done:

Sql> alter session set db_file_name_convert= '/data ', '+abc';
------------------------------------------------------------------------/\\\\\\\\\
Session altered.

sql> ALTER DATABASE create standby Controlfile as '/tmp/a.ctl ' reuse;
ALTER DATABASE create standby Controlfile as '/tmp/a.ctl ' reuse
*
ERROR at line 1:
Ora-15124:asm file name ' +data/odsptdb+abcfile/system.259.862837403 ' Containsan Invalid alias name
----------------------------------------------------------/\\\\\\\\\\

Sql> alter session set db_file_name_convert= '/data ', 'abc+abc';
-------------------------------------------------------------------------////\\\\
Session altered.

sql> ALTER DATABASE create standby Controlfile as '/tmp/a.ctl ' reuse;
ALTER DATABASE create standby Controlfile as '/tmp/a.ctl ' reuse
*
ERROR at line 1:
Ora-15124:asm file name ' +data/odsptdbabc+abcfile/system.259.862837403 ' contains an invalid alias name
-------------------------------------------------------------////\\\\

Sql> alter session set db_file_name_convert= '/data ', 'ABC';

Session altered.

sql> ALTER DATABASE create standby Controlfile as '/tmp/a.ctl ' reuse;

Database altered.

As can be seen from the above experiments, Db_file_name_convert does affect the creation of standby controlfile. And the string cannot contain "+" (that is, plus)

In the past rac+asm, the impression inside the Db_file_name_convert and Log_file_name_convert parameters can have "+" (that is, plus), this time encountered a very strange problem. Plan to find a time window, the above two parameters to change the second half to "+data", completely let ASM to manage.

Deliberately recorded here.

-------------------------------------------------------------------------------------------------

This article is from my technical blog http://blog.csdn.net/robo23

Reprint please mark source text link, otherwise investigate legal liability!

Db_file_name_convert parameter causes ora-15124:asm FILE NAME ' ... ' Containsan invalid alias name