8.1.1 Starting Up a Physical Standby Database To start a physical standby database, use SQL*Plus to connect to the database with administrator privileges, and then use either the SQL*Plus STARTUP or STARTUP MOUNT statement. When used on a physical standby database: • The STARTUP statement starts the database, mounts the database as a physical standby database, and opens the database for read-only access. • The STARTUP MOUNT statement starts and mounts the database as a physical standby database, but does not open the database. Once mounted, the database can receive archived redo data from the primary database. F1 Racing Games.

Jan 29, 2014 Recovering data file from a fuzzy. File ORA-01194: file needs more recovery to be consistent This site moved to dbacatalog. Counter Strike Android Game. blogspot. Moving an Oracle.

You then have the option of either starting Redo Apply or real-time apply, or opening the database for read-only access. 8.1.2 Shutting Down a Physical Standby Database To shut down a physical standby database and stop Redo Apply, use the SQL*Plus SHUTDOWN statement. Control is not returned to the session that initiates a database shutdown until shutdown is complete. If the primary database is up and running, defer the destination on the primary database and perform a log switch before shutting down the standby database. To stop Redo Apply before shutting down the database, use the following steps: • Issue the following query to find out if the standby database is performing Redo Apply or real-time apply.

If the MRP0 or MRP process exists, then the standby database is applying redo. SQL>SELECT PROCESS, STATUS FROM V$MANAGED_STANDBY; • If Redo Apply is running, cancel it as shown in the following example: SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; • Shut down the standby database. SQL>SHUTDOWN IMMEDIATE. 8.2 Opening a Standby Database for Read-Only or Read/Write Access When a standby database is open for read-only access, users can query the standby database but cannot update it. Thus, you can reduce the load on the primary database by using the standby database for reporting purposes.

You can periodically open the standby database for read-only access and perform ad hoc queries to verify Redo Apply is updating the standby database correctly. (Note that for distributed queries, you must first issue the ALTER DATABASE SET TRANSACTION READ ONLY statement before you can issue a query on the read-only database.) shows a standby database open for read-only access. 8.2.1 Assessing Whether or Not to Open a Standby Database As you decide whether or not to open a physical standby database for read-only or read/write access, consider the following: • Opening the physical standby database read-only may lengthen the time it takes to recover from a failure or outage, because the database must be restarted after a failover. As long as the physical standby database has not been opened read-only since the last time it was started, a restart is unnecessary after failover, thus increasing system availability.

• While a standby database is open for read-only or read/write access, it does not apply redo data received from the primary database, thus it is not kept transactionally consistent with the primary database. When a physical standby database is open, redo data from the primary database is received by the standby database, but the log files are not applied. At some point, you need to resume Redo Apply on the standby database, and apply the archived redo log files to resynchronize the standby database with the primary database. Because of the additional time required to apply any accumulated archived redo log files, having a standby database open for read-only access can increase the time required to complete failovers or switchovers. You can use a physical standby database for reporting purposes or as a clone database while also maintaining the ability to complete a failover or switchover quickly if you configure more than one standby database on the standby system. Gta San Andreas Pc Brasil Rar Tpb more.

For example, based on your business requirements, you might: • Configure two physical standby databases with one standby database always performing Redo Apply to be as current as possible with the primary database and the other standby database open in read-only mode during business hours for reporting purposes. • Configure a physical standby database to maintain a copy of the primary database for disaster recovery purposes and also configure a logical standby database to off-load reporting tasks that require access to the latest data from the primary database. When configuring more than one standby database on the same system, consider using the DEPENDENCY attribute of the LOG_ARCHIVE_DEST_ n initialization parameter to define one archival destination to receive redo data on behalf of all of the destinations, rather than transmitting redo data to each individual destination. See for more information. 8.2.2 Opening a Physical Standby Database for Read-Only Access You can alternate between having a physical standby database open for read-only access and performing Redo Apply using the following procedures. To open a standby database for read-only access when it is currently shut down: Start, mount, and open the database for read-only access using the following statement: SQL>STARTUP; To open a standby database for read-only access when it is currently performing Redo Apply: • Cancel Redo Apply: SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; • Open the database for read-only access: SQL>ALTER DATABASE OPEN; You do not need to shut down the instance to open it for read-only access.