In standby transmission mode, the archiving destination is either a local or remote standby database. If you are operating your standby database in managed recovery mode , you can keep your standby database synchronized with your source database by automatically applying transmitted archive logs. To transmit files successfully to a standby database, either ARC n or a server process must do the following:.
Transmit the archived logs in conjunction with a remote file server RFS process that resides on the remote server. You transmit archived logs through a network to a remote location by using Oracle Net Services. Indicate a remote archival by specifying a Oracle Net service name as an attribute of the destination. Oracle Database then translates the service name, through the tnsnames. The RFS process, which is required when archiving to a remote destination, is responsible for the following tasks:.
Archived redo logs are integral to maintaining a standby database, which is an exact replica of a database. You can operate your database in standby archiving mode, which automatically updates a standby database with archived redo logs from the original database. Oracle Data Guard Concepts and Administration. Oracle Database Net Services Administrator's Guide for information about connecting to a remote database using a service name.
Sometimes archive destinations can fail, causing problems when you operate in automatic archiving mode. Oracle Database provides procedures to help you minimize the problems associated with destination failure.
These procedures are discussed in the sections that follow:. The default value is 1. Valid values for n are 1 to 2 if you are using duplexing, or 1 to 10 if you are multiplexing. The following rules apply:. The default value for n is seconds. In this situation, consider the following options:. Change the destination by deferring the destination, specifying the destination as optional, or changing the service.
ARC n reopens a destination only when starting an archive operation from the beginning of the log file, never during a current operation. ARC n always retries the log copy from the beginning. If it is, ARC n retries the log copy. Background processes always write to a trace file when appropriate. In the case of the archivelog process, you can control the output that is generated to the trace file. The following values can be specified:. You can combine tracing levels by specifying a value equal to the sum of the individual levels that you would like to trace.
You can set different values for the primary and any standby database. At this level, the archivelog process generates appropriate alert and trace entries for error conditions.
For example:. You can display information about the archived redo logs using the following sources:. Several dynamic performance views contain useful information about archived redo logs, as summarized in the following table. This display tells you all the necessary information regarding the archived redo log settings for the current instance:. What Is the Archived Redo Log? The archiving of filled groups has these advantages: A database backup, together with online and archived redo log files, guarantees that you can recover all committed transactions in the event of an operating system or disk failure.
Controlling Archiving This section describes how to set the archiving mode of the database and how to control the archiving process. Back up the database. Start a new instance and mount, but do not open, the database. Performing Manual Archiving To operate your database in manual archiving mode, follow the procedure shown in "Changing the Database Archiving Mode".
Specifying the Archive Destination Before you can archive redo logs, you must determine the destination to which you will archive and familiarize yourself with the various destination states. The following topics are contained in this section: Specifying Archive Destinations Understanding Archive Destination Status Specifying Archive Destinations You can choose whether to archive redo logs to a single destination or multiplex them.
The default for this parameter is operating system dependent. Specifying the Mode of Log Transmission The two modes of transmitting archived logs to their destination are normal archiving transmission and standby transmission mode.
Normal Transmission Mode In normal transmission mode, the archiving destination is another disk drive of the database server. Standby Transmission Mode In standby transmission mode, the archiving destination is either a local or remote standby database.
Caution: You can maintain a standby database on a local disk, but Oracle strongly encourages you to maximize disaster protection by maintaining your standby database at a remote site. Managing Archive Destination Failure Sometimes archive destinations can fail, causing problems when you operate in automatic archiving mode.
No destination is a standby database. In this situation, consider the following options: Archive manually to the failed destination. Book List. Master Index. Contact Us. Displays historical archived log information from the control file. Describes the current instance, all archive destinations, and the current value, mode, and status of these destinations. Displays information about the state of the various archive processes for an instance.
The resulting command is shown here:. Because I can supply an array of strings to the path parameter, I can search for both. I look inside both types of files for a pattern match of ed. The revised command is shown here:. Because the pattern parameter also accepts an array of strings, I can also search the. In addition to directly using the path parameter in the Select-String cmdlet, it may be easier to use the Get-Childitem cmdlet for more granular control over the files to be parsed.
I include only. I do the same thing with the recurse switch in that I just use the letter r. I pipe the results to the Select-String cmdlet and look for the pattern fail pattern is the default parameter and therefore is omitted in the command. The long version of the command is shown here:. Interestingly enough, the above output displays information from an install. I decide that I would like to see the successes as well as the failures. I modify the command by adding the word success to the pattern.
As I look over the output from the previous command, I see a pattern appearing: on all the servers, the installation failed. On the client computers, the installation was a success.
But I am missing my Windows XP computers in the output. I decide to add the word pending to my array of search terms. Here is the revised command:. Well, SH, thank you for your question.
I hope I have encouraged you to spend a bit more time exploring the Select-String cmdlet. I invite you to follow me on Twitter and to join the Scripting Guys on Facebook.
0コメント