Software A monitoring standby database, as its name suggests, is a copy of a base of operations, held ready for use in place of the latter for availability in case of disasters and production database failure when the main base of operations has fallen and is not available. Usually, only the production data is cloned, is considered the secondary database or destination. The mechanics of implementing an emergency basis were officially available from Oracle 7. However, each new version of Oracle, the database has been waiting for a more robust and automatic. Regardless of the version, each implementation of databases expected to follow certain well-defined steps. I have referred to the standby database and development, always within Oracle, such as the deployment of regular sleep and conventional, instead of a personalized approach described below. Based on the version, the current method to perform some steps may vary. However, the overall objective remains the same. Refer to your version of Oracle-specific documents for details on setting up databases before, how they work, how to improve the availability, and what the relevant questions should be aware of before deciding to implement databases so out. Also, I’ve developed on the basis of some new features available in Oracle Standby and DataGuard. Standby feature of Oracle was introduced in Oracle 7.3, so the previous version of Oracle does not provide database in standby mode. Oracle expects function is absolutely based on the changes and redo log file. Database standby function requires integrity checks inherent in the issue of the journal file and record changes in the control file. The transactions take place in the primary database to the standby database to apply through the archive log. Archive logs are a copy of the redo logs. The transactions are written to redo log online after the process of .mit, the redo logs are full, switch and stored (copied) Arch in background process. Thus, both primary and standby databases must be in ARCHIVELOG mode. Archived logs are copied to the .work via a remote server in standby (either manually or automatically). In standby mode, the database is a constant state of recovery mode. All archived logs applied to copy the standby database, so that it can reach the contents of the primary database. In standby mode, the database is always behind the primary database for a few seconds. Even if all archived logs generated to date have been implemented, which continues to lag behind, because transactions are being written at the primary online redo logs and can be applied after they are archived and copied. There are some new measures introduced to prevent this situation from Oracle 9i. About the Author: 相关的主题文章: