Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

Most changes to the primary databases are propagated using normal propagation; however some changes are not propagated to the standby database. This is not a constraint from Dbvisit Standby, but from Oracle. The list below indicates whether a command is normally propagated or requires extra administrative efforts to be fully propagated.

Error rendering macro 'viewxls' : Failed to find attachment with Name Appendix_A.xlsx

 

Note 1:
Recovery process at standby will fail during application of archive if datafiles do not already exist. Datafiles should be pre-created at the standby to prevent automatic recovery from failing. However, if the recovery process fails, then the problem can be fixed by creating the datafile(s) and restarting recovery. 

Note 2:
If incomplete or media recovery is performed, which requires the standby to be rebuilt. However, if you can perform complete recovery without resetting the logs, then the standby is not invalidated. 

Note 3:
The standby controlfile is not updated. If the redo log configuration at the standby is different than at the primary, then no action is needed. Else, rename as for datafiles. Datafiles at standby must be renamed at the operating system level and then at the database level; that is, repeat the commands issued at the primary. 


Note 4:
If archive stream interrupted. In which case, must rebuild standby. However, if this is a temporary halt in archiving, then it has no effect. 


Note 5:
If the archive stream is interrupted, in which case, rebuild standby. However, if you are performing complete recovery without resetting the online redo logs, then the standby is not invalidated. For example, if all primary controlfiles are lost but all other files are available, then the controlfile can be created with NORESETLOGS. Furthermore, if you create a control file to increase maximum values, such as MAXDATAFILES (and do not reset the redo logs), then you should refresh the standby controlfile if the change must be propagated. 

Note 6:
If the affected objects are needed after activation, then, at the standby, either:

  • rebuild the standby
  • backup up the affected datafiles at the primary and
    restore at the standby

If the affected objects are not needed, then ensure that the tables exist in a tablespace that can be off-lined dropped at the standby.

  • No labels