Instructions often need some extra explanation so that they make sense, so they are followed with:
This heading explains the working of tasks or instructions that you have just completed.
You will also find some other learning aids in the book, including:
These are short multiple-choice questions intended to help you test your own understanding.
These are practical challenges that give you ideas for experimenting with what you have learned.
You will also find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: The LOG_ARCHIVE_DEST_n
parameters must be configured properly on every instance of primary and standby databases to show remote archiving destinations.
A block of code is set as follows:
LOG_ARCHIVE_CONFIG = { [ SEND | NOSEND ] [ RECEIVE | NORECEIVE ] [ DG_CONFIG=(remote_db_unique_name1, ... remote_db_unique_name9) | NODG_CONFIG ]
When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:
2 DBMS_SCHEDULER.CREATE_JOB (
3 JOB_NAME => 'REFRESH_EMPDEPT_MV_PRIMARY',
4 JOB_TYPE => 'PLSQL_BLOCK',
Any command-line input or output is written as follows:
RFS LogMiner: Registered logfile [/u01/app/oracle/archive_std/1_106_791552282.arc] to LogMiner session id [1] ... LOGMINER: Begin mining logfile for session 1 thread 1 sequence 106, /u01/app/oracle/archive_std/1_106_791552282.arc LOGMINER: End mining logfile for session 1 thread 1 sequence 106, /u01/app/oracle/archive_std/1_106_791552282.arc
New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: Expand the Data Guard Performance category and click on the Estimated Failover Time section.