Shulou(Shulou.com)05/31 Report--

This article mainly explains "what parameters are not applicable to the new data file after DATAGURAD synchronization", interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Next let the editor to take you to learn "the new data file after DATAGURAD synchronization is not applicable to what parameters" bar!

After the DATAGURAD is built and synchronized, the data file is added to the main library. If the slave database wants to modify the file path, the parameter db_file_name_convert is no longer applicable to the new data file.

Because this is the actual path where the slave database is automatically created through standby_file_management='AUTO', if you want to change the path of this new file, you can only set standby_file_management='MANUAL' and then alter database rename.

Reserve database parameters

Db_file_name_convert='/iso/db/oradata/DW','/u01/app/oracle/oradata/DW'

Standby_file_management='AUTO'

When setting up DATAGUARD

The files of the main library are all in / iso/db/oradata/DW, so the files of the backup library are naturally transferred to / u01/app/oracle/oradata/DW.

After building the DATAGURAD, it has been synchronized.

The main library creates a data file, such as / iso/db/oradata/DW/eps.dbf

Naturally, the library also put this file into / u01/app/oracle/oradata/DW/eps.dbf.

Now the repository modifies the path of the data file for some reasons, such as changing ORACLE_BASE or ORACLE_HOME, and copying the data file to another path.

For example, change / u01/app/oracle/oradata/DW to / u01/app/oradw/oradata/DW

Prepare the library to modify db_file_name_convert='/iso/db/oradata/DW','/u01/app/oradw/oradata/DW'

Query select * from v$dbfile after preparing the library startup mount and find that the new file path is / u01/app/oracle/oradata/DW/eps.dbf

Did not become the / u01/app/oradw/oradata/DW/eps.dbf we imagined, although the main library is / iso/db/oradata/DW/eps.dbf

And then alter database recover managed standby database disconnect from session

Error

ORA-01157: cannot identify/lock data file 70-see DBWR trace file

ORA-01110: data file 201:'/ u01 * app *

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

The restore operation is as follows

Alter database rename file'/ u01 alter database rename file'/ u01qqappActionoradataUnderDWUniqqep.dbf'oradata'/ u01GrexamplicaloradataDwUnipletoradataDwUnipletoradataDW

ORA-01275: Operation RENAME is not allowed if standby file management is automatic.

You can only close the database and modify standby_file_management='MANUAL'.

Startup mount re-execution

Alter database rename file'/ u01 alter database rename file'/ u01qqappActionoradataUnderDWUniqqep.dbf'oradata'/ u01GrexamplicaloradataDwUnipletoradataDwUnipletoradataDW

Modify standby_file_management='AUTO' before closing the database

Startup mount

Alter database recover managed standby database disconnect from session

Everything's all right.

At this point, I believe that everyone on the "DATAGURAD synchronization after the new data file is not applicable to what parameters" have a deeper understanding, might as well to the actual operation of it! Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.