These parameter settings determine the filenames of the archived redo logs at the standby site. FigureB-1 shows a database in manual recovery mode. A non-Data Guard environment is one in which you manually: Even if you implement a Data Guard environment, you might occasionally choose to perform manual recovery on the standby database. For example, you might choose to manually resolve an existing archive gap by using manual recovery mode. To keep the standby database current, you must manually apply archived redo logs from the primary database to the standby database. For example, assume that your database has the following datafiles, which you want to rename as shown in the following table: You can set DB_FILE_NAME_CONVERT as follows to convert the filenames for the first two datafiles: Nevertheless, this parameter will not capture the renaming of /data/df3.dbf. For example, you can set the following in the primary initialization parameter file to make standby1 a mandatory archiving destination: One consequence of this configuration is that unless the network problem is fixed, the primary database eventually stalls because it cannot switch into an unarchived online redo log. For example, execute one of the following statements: As the Oracle database server generates archived redo logs, you must continually copy and apply them to the standby database to keep it current. If step 6 renamed all files, skip this step. Connect to the primary database and create the standby control file. Please message us on YouTube or Instagram if you have any concerns.We believe these videos are fair use because:They are transformative in a positive sense, I take clips from various sources to help create an atmospheric feeling that will help people in hard situations in their life.I also do not wish to use the heart of any piece of work that would perhaps decrease the market value of the original content, if anything I hope to promote the content so that people can reach out and subsequently increase the market value.Lastly these videos are to educate people in an entertaining fashion. To determine if there is an archive gap, query the V$ARCHIVED_LOG and V$LOG views.

Specify the FROM 'location' option only if the archived log group is not in the location specified by the LOG_ARCHIVE_DEST_n parameter (where n is an integer from 1 to 10) or the LOG_ARCHIVE_DEST_n parameter in the standby initialization parameter file. Either make a new backup of the primary database datafiles or access an old backup. Now that all required logs are in the STANDBY_ARCHIVE_DEST directory, you can proceed to SectionB.3.4 to apply the archive gap logs to the standby database. Otherwise, the primary database eventually stalls because it cannot archive its online redo logs. For example, you might see: The following error messages are acceptable after recovery cancellation and do not indicate a problem: Oracle Corporation recommends automatically applying the logs in the archive gap using the RECOVER MANAGED STANDBY DATABASE clause of the ALTER DATABASE statement. It includes the following topics: TableB-1 summarizes the basic tasks for setting up a standby database in preparation for manual recovery. Preparing a Standby Database for Manual Recovery: Basic Tasks, Placing the Standby Database in Manual Recovery Mode, Manually Transmitting the Logs in the Archive Gap to the Standby Site, Manually Applying the Logs in the Archive Gap to the Standby Database, Shutdown of the Standby Database When the Primary Database Is Open, Network Failure Preventing the Archiving of Logs to the Standby Site. Manual recovery mode is required in a non-Data Guard environment. Because the standby database requires the sequential application of redo logs, media recovery stops at the first missing log encountered. This section contains the following topics: Typically, archive gaps are resolved automatically without the need for manual intervention. The archived log filenames on the standby site are generated by the STANDBY_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT parameters in the standby initialization parameter file. If you maintain a Data Guard environment, and the network goes down, the primary database might continue to archive to disk but be unable to archive to the standby site. If the standby database is on the same site as the primary database, or the standby database is on a remote site with a different directory structure than the primary database, the filenames for the logs on the standby site cannot be the same as the filenames of the logs archived by the primary database. If you do not want to use Oracle Net to connect to the standby database, skip steps 4 and 5. After you have started and mounted the standby database, you can place it in manual recovery mode. If the archiving destination is mandatory, then the primary database will not archive any logs until it is able to archive to the standby site. Fair use is a use permitted by copyright statute that might otherwise be infringing. Before transmitting the archived logs to the standby site, determine the correct filenames for the logs at the standby site. Archived log sequences 4 and 5 are now part of an archive gap, and these logs must be applied to the standby database. For example, you must shut down the standby database when you change a control file parameter, such as MAXDATAFILE, in the primary database. If an archive gap exists, the output of the query specifies the thread number and log sequence number of all logs in the archive gap. An archive gap can occur whenever the primary database archives a log, but the log is not archived to the standby site. For example, assume the following standby initialization parameter settings: Because the parameter values are different, copy the archived logs to the LOG_ARCHIVE_DEST location: When you initiate manual recovery, the Oracle database server looks at the LOG_ARCHIVE_DEST value to determine the location of the logs. My understanding is that it is in correlation to Fair Right Use, however, given that it is open to interpretation, if any owners of the content clips would like me to remove the video, I have no problem with that and will do so as fast as possible. Perform similar copy commands to copy archive gap logs for threads 2 and 3. If there is no archive gap for a given thread, the query returns no rows. This section contains the following topics: Archived redo logs arrive at the standby site in one of the following ways: The standby database assumes that the archived log group is in the location specified by either of the following parameters in the standby initialization parameter file: If the archived logs are not in the location specified in the initialization parameter file, you can specify an alternative location using the FROM option of the RECOVER statement. To prevent this problem, you can specify that the standby destination have mandatory status. Consequently, the Oracle database server can create an archive gap. The AUTOMATIC option automatically generates the name of the next archived redo log needed to continue the recovery operation. You must rename this datafile manually in the standby database control file by issuing a SQL statement as follows: When you manually rename all of the datafiles that are not captured by the DB_FILE_NAME_CONVERT parameter, the standby database control file can correctly interpret the log stream during the recovery process. While connected to the standby database, manually change the names of the primary datafiles and redo logs in the standby control file for all files not automatically renamed using DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT in step 6. Sometimes all of the primary datafiles and redo logs cannot be renamed in the standby control file by conversion parameters. For example, assume the scenario illustrated in FigureB-2. Text description of the illustration sbr81098.gif. You need to copy logs from threads 1, 2, and 3. To avoid creating archive gaps, follow these rules: If you violate either of these two rules, then the standby database is down while the primary database is open and archiving. You might choose manual recovery mode for any of the following reasons: This appendix explains how to work in manual recovery mode. See Section6.4 for more information about how log apply services automatically recover from gaps in the redo logs. If a thread appears in the view, then it contains an archive gap. Section6.4 and LOCATION and SERVICE in Chapter12. After recovering the available logs, the Oracle database server prompts for the name of a log that does not exist. I do not own the clips and music we use in most cases. Although Oracle Corporation recommends that you use the managed recovery mode for your physical standby databases, you can also use manual recovery mode. Start the standby instance and mount the standby database. Non-profit, educational or personal use tips the balance in favor of fair use.-This video has no negative impact on the original works (It would actually be positive for them)-This video is also for teaching purposes.-It is not trans-formative in nature.-This video is for Training purpose ONLY.I make these videos with the intention of educating others in a motivational/inspirational form.

For example, the following query shows that there is a difference in the RECD and SENT sequence numbers for the destination specified by DEST_ID=2, indicating that there is a gap: Use the following query to determine the names of the archived redo logs on the local system that must be copied to the standby system that has the gap: After you have obtained the log sequence numbers of the logs in the archive gap, you can obtain their filenames by querying the V$ARCHIVED_LOG view on the primary site. If you want to create an Oracle Net connection to the standby database, configure the listener on the standby site so that it can receive requests for connections to the standby instance. The reason is that the recovery process does not know about the logs archived to the standby site by the primary database. In this situation, archived logs accumulate as usual on the primary site, but the standby instance is unaware of them. This procedure assumes that you plan to connect to the standby database through Oracle Net. Query the V$ARCHIVED_LOG and V$LOG views on the standby database. Optionally, set DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT to automatically rename primary files in the standby control file. Create the standby initialization parameter file on the standby site and set the initialization parameters for the standby database. After you have copied the logs in the archive gap to the standby site, you can apply them using the RECOVER AUTOMATIC statement. Prepare and copy the backup datafiles and standby control file from the primary site to the standby site. ::::Disclaimer::::FAIR-USE COPYRIGHT DISCLAIMER* Copyright Disclaimer Under Section 107 of the Copyright Act 1976, allowance is made for \"fair use\" for purposes such as criticism, commenting, news reporting, teaching, scholarship, and research. Archive gaps can occur in the following situations: One example of an archive gap occurs when you create the standby database from an old backup. This problem is exacerbated if you maintain only two online redo logs in your primary database. If the standby site is specified as MANDATORY in one of the LOG_ARCHIVE_DEST_n parameters of the primary initialization parameter file, dynamically change it to OPTIONAL before shutting down the standby database. Another typical example of an archive gap occurs when you generate the standby database from a hot backup of an open database. An archive gap is a range of archived redo logs created whenever you are unable to apply the next archived redo log generated by the primary database to the standby database. Section6.5.3 and V$ARCHIVED_LOG in Chapter14. An educational talk to an audience, Especially new professionals in the information technology universe. Text description of the illustration sbr81090.gif. If you want to create an Oracle Net connection to the standby database, create a service name. For example, if the standby database is made from a backup that contains changes through log 100, and the primary database currently contains changes through log 150, then the standby database requires that you apply logs 101 to 150. You might be required to shut down the standby database to resolve maintenance issues.