There are three ways to archive the offline redo log files using BRARCHIVE in the case of a Parallel Server configuration of the database:
Normally the R/3 System is installed so that the mixed scenario is used for archiving for a Parallel Server configuration. SAP recommends this scenario for archiving the offline redo log files in production systems.
The distributed and especially the central scenario should only be used with some restrictions and then only for test systems.
Offline redo log files of different instances can be stored in a local archiving directory of an instance. This can occur if the online redo log files of instance X were not saved in the archiving directory for a long time (either the instance is closed or it is open but not active. Therefore a redo log file change is not forced and thus ORACLE archivation is not activated). One of the "active" instances notices this status and ensures that the current online redo log file of instance X is saved in its own archiving directory.
Parameter parallel_instances must therefore be set in the init
No comments:
Post a Comment