Dear Erman sir,
We have need your support, We are resyncing our standby database from SCN based method , the reason behind the resync is archive files gap are huge so using SCN based method are easy to synchronized standby database. All the production and standby database are in sync mode and there is no archive gap. Today morning I have seen the standby alert log files are throwing the below messages. 2024-05-05T11:22:34.754547+03:00 ***************************************** WARNING: The converted filename '+DATA/prodcdb/tempfile/temp.897.1109638083' is an ASM fully qualified filename. Changing the filename to '+DATA/MUST_RENAME_THIS_TEMPFILE_1.4294967295.4294967295'. Please rename it accordingly. ***************************************** ***************************************** WARNING: The converted filename '+DATA/prodcdb/e3678777e9b64012e0530a6910ac751b/tempfile/temp.901.1109639 183' is an ASM fully qualified filename. Changing the filename to '+DATA/MUST_RENAME_THIS_TEMPFILE_2.4294967295.4294967295'. Please rename it accordingly. ***************************************** ***************************************** WARNING: The converted filename '+DATA/prodcdb/e36a7c4446b84d0be0530a6910ac23da/tempfile/temp2.313.110969 4783' is an ASM fully qualified filename. Changing the filename to '+DATA/MUST_RENAME_THIS_TEMPFILE_3.4294967295.4294967295'. Please rename it accordingly. ***************************************** ***************************************** WARNING: The converted filename '+DATA/prodcdb/e36a7c4446b84d0be0530a6910ac23da/tempfile/temp2.312.110969 4797' is an ASM fully qualified filename. Changing the filename to '+DATA/MUST_RENAME_THIS_TEMPFILE_4.4294967295.4294967295'. Please rename it accordingly. I have query v$tempfile in standby database. Total 12 tempfiles are having same name issues. Need to fix it as per you recommendation. SQL> select name from v$tempfile; NAME -------------------------------------------------------------------------------- +DATA/MUST_RENAME_THIS_TEMPFILE_1.4294967295.4294967295 +DATA/MUST_RENAME_THIS_TEMPFILE_2.4294967295.4294967295 +DATA/MUST_RENAME_THIS_TEMPFILE_3.4294967295.4294967295 +DATA/MUST_RENAME_THIS_TEMPFILE_4.4294967295.4294967295 +DATA/MUST_RENAME_THIS_TEMPFILE_5.4294967295.4294967295 +DATA/MUST_RENAME_THIS_TEMPFILE_6.4294967295.4294967295 +DATA/MUST_RENAME_THIS_TEMPFILE_13.4294967295.4294967295 +DATA/MUST_RENAME_THIS_TEMPFILE_14.4294967295.4294967295 +DATA/MUST_RENAME_THIS_TEMPFILE_15.4294967295.4294967295 +DATA/MUST_RENAME_THIS_TEMPFILE_16.4294967295.4294967295 +DATA/MUST_RENAME_THIS_TEMPFILE_17.4294967295.4294967295 NAME -------------------------------------------------------------------------------- +DATA/MUST_RENAME_THIS_TEMPFILE_18.4294967295.4294967295 12 rows selected. Regards, Raiq |
Administrator
|
The warning signifies that the database expects OMF filenames (based on DB_FILE_NAME_CONVERT) but encounters ASM fully qualified names during recovery.
Do you use OMF? -I guess you do Do you have *_file_name_convert parameters set? |
Dear Sir,
Below are the convert parameters information in standby database. SQL> show parameter convert NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ db_file_name_convert string +DATA, +DATA log_file_name_convert string +RECO, +RECO pdb_file_name_convert string Please advice . Regards, Raiq |
Administrator
|
Please see the MOS note: "Usage and Limitation of db_file_name_convert and log_file_name_convert (Doc ID 1367014.1)" -- Read item 2), 3), 4) and 5) documented there and ensure you are aligned with these..
|
This post was updated on .
Dear Erman Sir,
I have read this note , issue are started once we have synchronized a standby database through scn based recovery method from production database. Kindly suggest me , should I do manually rename the temp files through alter database rename file command. For you information , I have attached report schema for standby database to your review.report_schema_standby.txt Kindly advice. Regards, Raiq. |
Administrator
|
You should get rid of this mess first..
Temporary tablespace has no role in restore recovery that is the main function of using Active Dataguard or Standby Database. So those files are not in use. But once you open that standby database read write or read only, you will need them.. Operations like RMAN Duplicate automatically adds the Tempfile to the Standby Database.. Probably your SCN based recovery is analogous to this. |
Administrator
|
This may be due to db_file_name_convert. Why are using this ? You already using it as DATA , DATA . The same.. You don't convert actually..
|
Administrator
|
Also note that, If OMF parameters are set on the standby, then new files on that standby are always created as OMF, regardless of how they were created on the primary. Therefore, if both the DB_FILE_NAME_CONVERT and DB_CREATE_FILE_DEST parameters are set on the standby, the DB_CREATE_FILE_DEST parameter takes precedence.
|
Administrator
|
Ref:
Dataguard DB/LOG FILE NAME CONVERT has been set but files are created in a different directory (Doc ID 1348512.1) On Standby Datafiles are Going Into Wrong Diskgroup ( Db_file_name_convert, Db_create_file_dest ) (Doc ID 1408666.1) |
Hi Erman sir,
Thanks for your details, just guide me for db_file_name_convert parameter in stanadby database , during restore database time, I have set both parameter db/log_file_name_convert as mentioned earlier . As my understanding both prod and standby database are ASM based and if prod database are restore in standby database, all data files are restore in DATA disk group , so I have set the parameter below db_file_name_convert string +DATA, +DATA log_file_name_convert string +RECO, +RECO Now due to this mess, If I plan to build the standby database from scratch and restore all production database to standby database , what parameter I have to set in db_file_name_convert and log_file_name_convert in standby database , so database restoration should be happen smoothly and all the datafiles will restore on +DATA and redo log file will restore on +RECO. Hope you understand my query. Regards, Raiq |
Administrator
|
I already stated that this may be due to db_file_name_convert. Why are using this ? You already using it as DATA , DATA . The same.. You don't convert actually..
|
Free forum by Nabble | Edit this page |