Align |
---|
Normally, Oracle does not propagate the adding of datafiles on the primary database to the standby database. This must be done manually on the standby database. Dbvisit Standby will automatically add the datafile to the standby database. Dbvisit Standby version 6.0.26 and later, will attempt to generate a new name for a standby datafile, in case the primary name cannot be used due to different storage type (ASM and non ASM) or different database file structure between the primary and standby. There are some restrictions to automatically adding the datafiles to the standby database. |
Note | ||
---|---|---|
|
Every time Dbvisit Standby runs on the primary, it takes a snapshot of primary datafile ids and names and saves it in the repository.
...
Dbvisit Standby can by default only add a maximum of 10 data files per session. This is controlled by the MAX_DATAFILES_TO_ADD parameter that can be set in the Dbvisit Database Configuration File (DDC)
When Using ASM
If the Standby database is making use of ASM, using OMF (Oracle Managed Files) is recommended.
Note | ||
---|---|---|
| ||
If ASM is used on the standby database for database storage, datafiles on the standby database will be created as Oracle Managed Files (OMF). |
If a new datafile was added to the primary database the same process will be followed as mentioned above where the "datafiles_ORACLE_SID_DEST.txt" file is used, but if the standby database is making use of ASM and OMF is enabled - db_create_file_dest is set to a specific disk group - the standby database datafiles will be added as OMF files. (Aliases will not be used).