Note |
---|
Dbvisit Standby does not support special characters in database file name locations (datafiles, redo logs or controlfiles) - example " ` ' $ % * ^ The + is supported when using ASM. |
During standby database creation a standby control file is created for the primary database, shipped to the standby server and restored as the standby control file. The standby control file created on the primary server contains the names of the primary datafiles, tempfiles and redo logs. In case the primary and the standby databases have different structure (different file names and/or locations), or storage type is different for the primary and the standby (ASM and filesystem), database files must be renamed in the standby control file to match the storage type and the structure of the standby database. This is automatically done by Dbvisit Standby.
...
Prior to this fix OMF file names had the following format:
File Type | Format | Example |
---|---|---|
Datafile | ora_%t_%u.dbf | ora_tbs1_2ixfh90q.dbf |
Tempfile | ora_%t_%u.tmp | ora_temp1_6dygh80r.tmp |
Redo log file | ora_%g_%u.log | ora_1_wo94n2xi.log |
Control file | ora_%u.ctl | ora_cmr7t90p.ctl |
Where:
%t is the tablespace name (possibly truncated)
...
- an "ora_" prefix
- and a ".dbf", ".tmp", ".log" or ".ctl" extension
...
The new and current format for OMF file names on Windows and Unix-based systems are:
File Type | Format | Example |
---|---|---|
Datafile | o1_mf_%t_%u_.dbf | o1_mf_tbs1_2ixfh90q_.dbf |
Tempfile | o1_mf_%t_%u_.tmp | o1_mf_temp1_6dygh80r_.tmp |
Redo log file | o1_mf_%g_%u_.log | o1_mf_1_wo94n2xi_.log |
Control file | o1_mf_%u_.ctl | o1_mf_cmr7t90p_.ctl |
Where:
%t is the tablespace name (possibly truncated)
...
- a "o1_mf_" prefix
- and a ".dbf", ".tmp", ".log", or ".ctl" extension
- and an "_" character immediately preceding the extension
...
Align |
---|
Dbvisit Standby recognizes both naming formats ora_* and o1_mf_* as OMF file formats. OMF files should be created and managed by Oracle. Oracle does not recommend creating files with OMF names implicitly as Oracle is not able to recognize these files as an Oracle managed files and will not manage the files accordingly. |
...
+dgroup2/sample/controlfile/control01.dbf
...