D17316 gc20 appa
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
556
On Slideshare
556
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
8
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Oracle Database 10 g : Data Guard Administration A - Appendix A Practices and Solutions
  • Practice 1: Oracle Data Guard Overview 1. Which one of the following statements is true? a. A standby database is a set of log files that will be applied in the event of a system failure. b. A primary database is the production database. c. A logical standby is an extension to the physical standby database. d. The redo logs contain native SQL that can be applied to the standby database. Solution: b 2. Which one of the following is not an Oracle Data Guard service? a. Role management b. Redo transport c. Redo log d. Log apply Solution: c 3. Which one of the following operations would you perform when the primary database is completely lost? a. Switchover b. Apply backups to standby c. Apply redo logs d. Failover Solution: d 4. The Oracle Data Guard broker is a distributed management framework that automates and centralizes the creation, maintenance, and monitoring of Data Guard configurations. a. True b. False Solution: a 5. Enterprise Manager provides monitoring, automation, and management of the Data Guard broker components. a. True b. False Solution: a
  • Practice 1: Oracle Data Guard Overview (continued) 6. Which protection mode will cause the primary database to be shut down if contact with all standby databases is lost? a. Maximum protection b. Maximum availability c. Maximum performance Solution: a 7. Which protection mode has the lowest impact on the performance of the primary database but has the possibility of data loss? a. Maximum protection b. Maximum availability c. Maximum performance Solution: c 8. Real Application Clusters and Oracle Data Guard should not be used together because they basically do the same thing. a. True b. False Solution: b
  • Practice 2-1: Architecture Overview 1. Which one of the following statements is true? a. The ARC n process creates a copy of the online redo logs for use by the LGWR process . b. The LGWR process collects transaction redo and updates the data files. c. The FAL process provides a client/server mechanism for resolving gaps that are detected in the range of archive redo logs. d. The MRP process applies archived redo log information to the logical standby database. Solution: c 2. Which one of the following is not an operational requirement for the Data Guard environment? a. The primary and standby databases must use the same database release. b. Each primary and standby database must have its own control file. c. The primary database must operate in ARCHIVELOG mode. d. The standby must be on the same node as the primary . Solution: d 3. What are the modes of a physical standby database? _______________________________________________________ _______________________________________________________ Solution: Managed recovery and open read-only 4. What technology is used to transform the redo log into SQL? _______________________________________________________ _______________________________________________________ Solution: LogMiner 5. Should you create standby redo logs on the primary database? ______________________________________________________ Solution: Yes 6. How many standby redo log groups should you have? _______________________________________________________ ______________________________________________________ Solution: At a minimum, the number of standby redo log groups should be equal to the number of online redo log file groups on the primary database; one more (per primary database instance) than this is recommended.
  • Practice 2-2: Installing the Oracle Management Agent Oracle Enterprise Manager Grid Control is installed and operational on a server for your practices. You must install the Oracle Management Agent on your PC so that you can use Grid Control to monitor, configure, and administer the databases on your PC. 1. Open a terminal window and log on as the oracle user with a password of oracle . 2. Oracle Enterprise Manager Grid Control software is staged in the agent_installmedia directory. Change directories to agent_installmedia/Disk1/linux/agent . [oracle@EDRSR10P1 oracle]$ cd agent_installmedia/Disk1/linux/agent 3. Set your $ORACLE_HOME environment variable by executing the export command. [oracle@EDRSR10P1 oracle]$ export ORACLE_HOME=$AGENT_HOME [oracle@EDRSR10P1 oracle]$ echo $ORACLE_HOME /u01/app/oracle/product/10.2.0/agent10g 4. Invoke the Oracle Universal Installer by issuing the following command: ./runInstaller 5. On the Specify Installation Type page, select Additional Management Agent. Click Next. 6. On the Specify Installation Location page, specify /u01/app/oracle/product/10.2.0 in the Parent Directory field. Click Next. 7. On the Product Specific Prerequisite Checks page, select the check box next to Status to manually verify the warning. The status changes to User Verified. Click Next. 8. On the Specify Oracle Management Service Location page, enter the following information about the host machine that Oracle Enterprise Manager Grid Control is installed on: Management Service Host Name: <OMS_host> (Example: ex0026.oracle.com ) Management Service Port: 4889 Click Next. 9. On the Specify Agent Registration Password page, specify oracle1 in the Password field. Click Next.
  • Practice 2-2: Installing the Oracle Management Agent (continued) 10. On the Oracle Configuration Manager Agreement page, select Decline License Agreement. Click Next. 11. Click OK on the warning page. 12. Click Install on the Summary page. The Install page appears showing the progress of the installation. 13. The “Execute Configuration scripts” dialog box appears. Follow the instructions to execute the root.sh script. Open a new terminal window, log in as the root user, change to the specified directory, and execute the root.sh script. [oracle@EDRSR10P1 oracle]$ su - Password: [root@EDRSR10P1 root]# cd /u01/app/oracle/product/10.2.0/agent10g [root@EDRSR10P1 root]# ./root.sh Accept the default values for all prompts during the execution of the root.sh script. After the root.sh script completes, return to the “Execute Configuration scripts” dialog box and click OK. 14. The Configuration Assistants page appears. Once the configuration is complete, the “End of Installation” page appears. Verify that the installation was successful and click Exit to exit the Oracle Universal Installer. Click Yes in the Exit dialog box. 15. Configure monitoring credentials for your database. Open your browser and enter the following URL: http://<oms_host>:7777/em 16. Log in as the user sysman with password oracle1 , and change the Monitor Password for your database to oracle . a. Log in as the user sysman with password of oracle1 and click Login. b. Review the licensing information and click “I agree.” c. Select Targets and click Databases. d. Select your database ( <HOSTNAME>_ORCL ) from the list of databases and click Configure. e. Enter the Monitor Password of oracle and click Test Connection. f. Verify that the connection is successful and click Next. Click Submit. g. Click OK on the Database Instance Configuration Result page.
  • Practice 2-3: Configuring Your Primary Database As you proceed through the remaining practices, use this page to record information about your databases. Primary Database Database Name: ___________________________________________________ Instance Name: ____________________________________________________ Database Unique Name: _____________________________________________ Target Name: _____________________________________________________ Host: ____________________________________________________________ Oracle Home: _____________________________________________________ Standby Database Database Name: ___________________________________________________ Instance Name: ____________________________________________________ Database Unique Name: _____________________________________________ Target Name: _____________________________________________________ Host: ____________________________________________________________ Oracle Home: _____________________________________________________ Type of standby: ___________________________________________________ Standby Database Database Name: ___________________________________________________ Instance Name: ____________________________________________________ Database Unique Name: _____________________________________________ Target Name: _____________________________________________________ Host: ____________________________________________________________ Oracle Home: _____________________________________________________ Type of standby: ___________________________________________________
  • Practice 2-3: Configuring Your Primary Database (continued) IMPORTANT NOTE: PLEASE USE PAGE A-7 TO RECORD INFORMATION ABOUT THE SYSTEMS YOU WILL USE AND DATABASE NAMES. 1. Invoke Enterprise Manager Grid Control and view your database home page. a. Enter the URL supplied by your instructor: http:// hostname :7777/em b. Supply the following to log in to Grid Control: User name: SYSMAN Password: _________ c. Click Login. d. Click Targets to access the Hosts page. e. Click Databases to access the Databases page. f. Select your database by clicking the database link name. Important: Because you are logging in as the SYSMAN user, you will be able to see and modify all databases in your classroom. Be careful as you select only your database in the list. 2. Configure preferred credentials for your database. a. Access your database home page. b. Click Preferences in the top-right corner. c. Click Preferred Credentials on the left side. d. Click the Set Credentials icon for the Database Instance target type. e. Locate your database in the Target Credentials region and enter the usernames and passwords as follows: Normal username: SYSTEM Normal password: oracle SYSDBA username: SYS SYSDBA password: oracle Host username: oracle Host password: oracle f. Click Test to verify your entries. You receive the message “Credentials successfully verified for <database instance name>.” If you do not receive this message, correct your errors and click Test again. g. Click Apply to confirm your entries. You receive the message “Credential changes successfully applied.” h. Click Targets. Click Databases to return to the Databases page. Note: Practice 2-3 continues on the next page.
  • Practice 2-3: Configuring Your Primary Database (continued) 3. Configure ARCHIVELOG mode for your database. Use the flash recovery area for the archive log destination. Do not set up any other destinations at this time. In addition, configure Flashback Database for your database. You must be logged in as SYSDBA to complete this task. a. Select your database on the Databases page. On your database home page, click Maintenance to access the Maintenance page. b. Click Recovery Settings to access the Configure Recovery Settings page. c. Because you are logged in as SYSTEM , the Database Login page is displayed. If the Database Login page does not display, click Logout in the upper-right corner of the page. Select “Log out of database” and “Display database login page after logout.” d. Enter the username SYS , password ORACLE , and select SYSDBA from the “Connect As” drop-down menu. Click Login. e. Select “ARCHIVELOG Mode” in the Media Recovery section. f. Accept the default of USE_DB_RECOVERY_FILE_DEST in destination 10 to indicate that the flash recovery area should be used. g. Select “Enable Flashback Database - flashback logging can be used for fast database point-in-time recovery*.” h. Enter 12 hours in the Flashback Retention Time field. i. Click Apply. j. Click Yes on the confirmation page to restart the database instance. k. Confirm the host and database credentials or enter them if required. Click OK. l. Click Yes to restart the database instance after shutdown. m. An Update Message is displayed confirming your change. n. Click the Database Instance link to return to the Maintenance page.
  • Practice 4: Creating a Physical Standby Database by Using Enterprise Manager 1. Invoke Enterprise Manager 10 g Grid Control and access your database home page. a. Enter the URL supplied by your instructor: http:// hostname :7777/em b. Supply the following to log in to Grid Control: User name: SYSMAN Password: _________ c. Click Login. d. Click Targets to access the Hosts page. e. Click Databases to access the Databases page. f. Click the link for your database to access the database home page. Practice 4 continues on the next page.
  • Practice 4: Creating a Physical Standby Database by Using Enterprise Manager (continued) 2. Create a physical standby database with the following specifications by using Grid Control: Primary database unique name: <HOSTNAME>_ORCL Standby database unique and target name: <HOSTNAME>_SITE1 Location: Create your physical standby database on the next highest student PC in your classroom. For example, if your host name is EDRSR8P1, create your physical standby database named EDRSR8P1_SITE1 on EDRSR8P2. Note: Your instructor may modify this configuration. Use the naming conventions provided above to avoid confusion when selecting your databases in Grid Control. Record information on page A-7. a. Access your database home page and select Maintenance to access the Maintenance page. b. Click Setup and Manage in the Data Guard section. c. Provide the SYSDBA login information on the Database Login page if requested. c. Click Add Standby Database to invoke the Add Standby Database Wizard. d. Select “Create a new physical standby database” and click Continue. e. Select “Perform a live backup of the primary database” and click Next. f. Accept the default location for the backup and the default option to delete the working directory after the standby creation. If the password field is empty, provide the password for the Oracle server owner user and select Save as Preferred Credential. Click Next. g. Accept the default instance name of dg2 . Enter the credentials for the standby host machine if they differ from the default supplied. Select the host in the Standby Database Location section as described above. Click Next. h. Accept the default, to transfer files, in the Standby Host Backup File Access section. Select “Convert to Oracle OFA” in the Standby Database File Locations section. Accept the default location for the network configuration file location. Click Next. i. If you receive the following warning message: “The following files already exist and will be overwritten: /u01/app/oracle/product/10.2.0/db_1/demo/schema/sales_history/sale1v3.dat; Click ‘Yes’ to continue, or click ‘No’ then ‘Customize’ to make changes.”, click Yes to continue. j. Specify Database Unique Name and Target Name as <HOSTNAME>_SITE1 . Accept the default location for the archived redo logs. Click Next. k. Review your configuration information and click Finish. l. After you are returned to the Data Guard page, select “Real Time: 1 Minute Refresh” from the View Data drop-down menu to monitor the creation of your standby database. Click “Creation in progress” to view detailed information about the creation of your physical standby database. The creation is complete when the status changes to Normal.
  • Practice 4: Creating a Physical Standby Database by Using Enterprise Manager (continued) 3. After the physical standby creation is complete, use Verify to validate the configuration and add standby redo logs. a. Access your Data Guard configuration by selecting your primary database. Select Setup and Manage in the Data Guard section of the Maintenance page. b. Click Verify Configuration in the Additional Administration section. c. Review the information in the “Detailed Results” section. d. Select “Create standby redo logs for the following database(s)” to create standby redo logs for your primary and standby databases. Click OK. 4. Enable Flashback Database for your physical standby database, setting the retention time to 12 hours as follows: a. Navigate to the Maintenance page for your physical standby database. b. Select Recovery Settings in the Backup/Recovery Settings section of the Maintenance page. c. Supply SYSDBA login information. Click Login. d. Select “Enable Flashback Database-flashback logging can be used for fast database point-in-time recovery.” e. Enter 12 hours in the Flashback Retention Time field. f. Click Apply. g. Click Yes to restart the database instance. h. Enter the Host Credentials and Database Credentials if they are not supplied. Click OK. i. Click Yes to restart the database instance. j. Return to the database home page after the database instance has been restarted.
  • Practice 6: Configuring Data Protection Modes and Redo Transport Services 1. Using Enterprise Manager, change the data protection mode for your standby database to maximum protection. a. On the Databases target page, click the link for your primary database. b. Click Maintenance. c. Click Setup and Manage in the Data Guard section. d. In the Overview section, click the link in the Protection Mode field to access the Change Protection Mode: Select Mode page. e. Select Maximum Protection and click Continue. f. Accept the default selection of your physical standby database and click Continue. g. If requested, supply the host login credentials and click Continue. h. Click Yes on the Confirmation: Change Protection Mode page. i. The Processing: Change Protection Mode page is displayed. j. You are returned to the Data Guard Overview page. Verify that your protection mode has been changed to maximum protection. 2. Using Enterprise Manager, configure a delay for the application of redo to the standby database to allow you to stop the application of any corrupt data. Set the delay for 2 hours (120 minutes). a. Select your standby database and click Edit on the Data Guard page. b. Click Standby Role Properties on the Edit Standby Database Properties page. c. Enter the delay value of 120 in the Apply Delay field. d. Click Apply. You receive the “All changes successfully applied.” message. 3. In preparation for later practices, use Enterprise Manager to change the data protection mode back to maximum performance. a. Navigate to the Data Guard page. b. Click the link in the Protection Mode field to access the Change Protection Mode: Select Mode page. c. Select Maximum Performance and click Continue. d. Click Yes on the Confirmation: Change Protection Mode page. e. You are returned to the Data Guard Overview page and the “Confirmation The protection mode has been successfully changed.” message is displayed. 4. You decide that you no longer want the delayed application of redo. Use Enterprise Manager to disable the delay in the application of redo. a. Select your standby database and click Edit on the Data Guard page. b. Click Standby Role Properties on the Edit Standby Database Properties page. c. Enter the delay value of 0 in the Apply Delay field. d. Click Apply. You receive the “Success All changes successfully applied.” message.
  • Practice 7: Creating a Logical Standby Database by Using Enterprise Manager 1. Use Enterprise Manager Grid Control to create a logical standby database with the following specifications: Standby database unique and target name: <HOSTNAME>_SITE2 Location: Create your logical standby database on the next highest student PC in your classroom. For example, if your host name is EDRSR8P1, create your logical standby database named EDRSR8P1_SITE2 on EDRSR8P2. Note: Your instructor may modify this configuration. Use the naming conventions provided above to avoid confusion when selecting your databases in Grid Control. Record information on page A-7. a. Select your primary database on the Databases target page. b. Select Maintenance to access the Maintenance page. c. Click Setup and Manage in the Data Guard section. d. Click Add Standby Database in the Standby Databases section to invoke the Add Standby Database Wizard. e. Select “Create a new logical standby database” and click Continue. f. Select “Perform a live backup of the primary database” and click Next. g. Accept the default location for the backup and the default option to delete the directory after the standby creation. Enter primary host credentials if needed. Click Next. h. On the Database Location page, accept the default instance name of dg3 . Enter the credentials for the host machine if they differ from the default supplied. Select the host in the Standby Database Location section as described above. Click Next. i. Accept the default, to transfer files, in the Standby Host Backup File Access section. Select “Convert to Oracle OFA” in the Standby Database File Locations section. Accept the default location for the network configuration file location. Click Next. j. If you receive the warning message “Warning: The following files already exist and will be overwritten: /u01/app/oracle/product/10.2.0/db_1/demo/schema/sales_history/sale1v3.dat; Click ‘Yes’ to continue, or click ‘No’ then ‘Customize’ to make changes.”, click Yes. k. Accept the default Database Name. Specify Database Unique Name and Target Name as <HOSTNAME>_SITE2 . Accept the default location for the archived redo logs. Click Next. l. Review your configuration information and click Finish. You may see an “ORA-16821- logical standby database dictionary not yet loaded” warning message. Wait until you see the “normal” status. m. Select “Real Time: 1 Minute Refresh” in the View Data drop-down menu to monitor the creation. 2. After the logical standby database creation is complete, use Verify to validate the configuration. a. Select Setup and Manage in the Data Guard section of the Maintenance page. Access your Data Guard configuration by selecting your primary database. b. Click Verify Configuration in the Additional Administration section. c. View progress on the Processing: Verify page. d. Review results in the Detailed Results window. Click OK to return to the Data Guard page.
  • Practice 7: Creating a Logical Standby Database by Using Enterprise Manager (continued) 3. Enable Flashback Database for your logical standby database, setting the retention time to 12 hours as follows: a. Navigate to the Maintenance page for your logical standby database. b. Click Recovery Settings in the Backup/Recovery Settings section of the Maintenance page. c. Specify the following to configure the Flash Recovery Area: Flash Recovery Area: /u01/app/oracle/product/10.2.0/db_1/oradata/dg3/arc Flash Recovery Size: 3106 MB d. Select “Enable Flashback Database-flashback logging can be used for fast database point-in-time recovery.” e. Enter 12 hours in the “Flashback Retention Time” field. f. Click Apply. g. Click Yes to restart the database instance. h. Enter the Host Credentials and Database Credentials if they are not supplied. Click OK. i. Click Yes to restart the database instance. j. Return to the database home page after the database instance has been restarted.
  • Practice 9: Performing Switchover and Failover 1. Create a table in your primary database defined as follows: Schema: HR Name: MY_TABLE Column Name: COL1 Data type: NUMBER Tablespace: EXAMPLE a. Select your primary database on the Databases target page. b. Select Tables in the Schema section of the Administration page. c. Supply login information (SYS/ORACLE, Connect as SYSDBA) and click Login. c. Click Create. d. Select Standard, Heap Organized and then click Continue. e. Enter the table name, schema, tablespace name, and column information. Click OK. You receive a confirmation message: “Update Message Table HR.MY_TABLE has been created successfully.” 2. Perform a log switch on your primary database. a. Return to your primary database home page by clicking the database instance link. b. Click Redo Log Groups in the Storage section of the Administration page. c. Select “Switch logfile” in the Actions list. d. Click Go. You receive the “Update Message Log group successfully switched.” message. 3. Access the Data Guard page for your configuration. a. Return to the Administration page for your primary database by clicking on the database instance link. b. Access the Maintenance page. Select Setup and Manage in the Data Guard section. 4. Select your physical standby database and perform a switchover. a. Select your physical standby database and click Switchover. b. Supply host login credentials and click Login. c. Click Yes to confirm the switchover operation. d. View the progress on the Processing: Switchover page. e. You are returned to the Data Guard page and receive the “Information Switchover completed successfully” message. 5. Verify that the HR.MY_TABLE table you created in step 1 exists on your new primary database. a. Access the database home page for your new primary database. b. Select Tables in the Schema section of the Administration page. c. Log in to your database as SYS with a password of ORACLE as SYSDBA . d. Enter HR in the Schema field and MY_TABLE in the Object Name field. e. Click Go. f. The table is displayed in the table list. Note: Practice 9 continues on the next page.
  • Practice 9: Performing Switchover and Failover (continued) Perform a complete failover to your physical standby database by using Enterprise Manager. a. Navigate to the Data Guard page. b. Select your physical standby database and click Failover. c. On the confirmation page, click Yes to proceed with the failover. d. Supply host login credentials. Click Continue. e. Select Complete for the type of failover and click Yes. f. The Processing: Failover page is displayed. When the failover is completed, you are returned to the Data Guard page and receive the “Information Failover completed successfully” message. 7. Attempt to reinstate the former primary database ( HOSTNAME_SITE1 ). a. Click the “Database must be reinstated” link for your <HOSTNAME>_SITE1 database. b. On the Edit Standby Database Properties: <HOSTNAME>_SITE1 page, click Reinstate. c. Provide the SYSDBA login credentials ( SYS/ORACLE ). Click Yes to restart the instance. The “Information Database <HOSTNAME>_SITE1 has been successfully started.” message is displayed and you are returned to the Data Guard page. d. Again, click the “Database must be reinstated” link. e. Click Reinstate. f. Supply SYSDBA login credentials again if requested and click Yes. g. The Processing: Reinstating Database page is displayed. Once complete, you are returned to the Data Guard page and receive the “Information Database <HOSTNAME>_SITE1 has been successfully reinstated.” message.
  • Practice 10: Enabling Fast-Start Failover 1. Use Enterprise Manager to enable fast-start failover to your physical standby database. a. Access the Data Guard page. b. In the Overview section, click the Disable link next to “Fast-Start Failover.” c. In the Target Database Selection section, select your physical standby database ( <HOSTNAME>_SITE1 ). d. In the Properties section, click “Set Observer.” The Fast-Start Failover: Set Observer page appears. e. Click the flashlight icon next to the Observer Host field to select the host machine for the observer. For the purposes of this practice, select the same host that your physical standby database is on. f. Click OK to accept the selected Observer Host and Observer Oracle Home. Because you are using the same host for the observer, you will receive a warning message: “You have chosen to start the observer on the same host where the primary or standby database is located. Oracle recommends the observer be on a separate host.” g. The Fast-Start Failover: Configure page displays again with the specified Observer Location. Set the Fast-Start Failover Threshold to 90 seconds. Click Continue. h. On the Observer Host Credentials page, supply the operating system user name of oracle and password of oracle for the observer host. Click Continue. i. On the Confirmation: Enable Fast-Start Failover page, click Yes. j. The Processing: Enable Fast-Start Failover page displays. After processing completes (which may take some time), the Data Guard overview page displays with the “Information The fast-start failover mode has been successfully changed and the primary database has been restarted.” message. Note that the Fast-Start Failover field indicates that fast-start failover is enabled. 2. In preparation for later steps, access the Data Guard configuration through your physical standby database. a. Click the Databases subtab. b. Click your physical standby database. c. Click Maintenance. Click Setup and Manage in the Data Guard section. 3. Shut down your primary database to simulate a failure. a. Open a terminal window to the host your primary database is on and log in as the oracle user. b. Invoke SQL*Plus and connect as the SYS user with SYSDBA privileges as follows: sqlplus / as sysdba Note: If you receive an error regarding ORACLE_HOME , set it to: /u01/app/oracle/product/10.2.0/db_1 c. Shut down the database with the ABORT option: SQL> shutdown abort
  • Practice 10: Enabling Fast-Start Failover (continued) 4. Return to the Data Guard page for your configuration to monitor the fast-start failover. a. Set the View Data field to Real Time: 1 Minute Refresh. b. Note that the Data Guard status has turned to “Error.” and “ORA-16625: cannot reach the database” is displayed. c. Continue monitoring the Data Guard page until your former physical standby database is shown as the primary database. 5. Restart your primary database. a. Return to your terminal window. b. Restart your database instance: SQL> connect / as sysdba Connected to an idle instance. SQL> startup 6. Return to Enterprise Manager to monitor your configuration as the new physical standby database is added back into the configuration. 7. In preparation for later practices, perform a switchover to your physical standby database (<HOSTNAME>_ORCL.oracle.com ) a. Select your physical standby database ( <HOSTNAME>_ORCL.oracle.com ). Click Switchover. b. On the Confirmation: Switchover to <HOSTNAME>_ORCL.oracle.com , click Yes. The Processing: Switchover page is displayed. c. After the switchover is complete, you are returned to the Data Guard page. Confirm that your <HOSTNAME>_ORCL.oracle.com database is listed as your primary database.
  • Practice 13: Workshop Preparation To prepare for the workshop, you need to drop your Data Guard configuration and your standby databases. Follow the steps below to accomplish these tasks. 1. Access the Data Guard page and disable fast-start failover. a. Select the link next to Fast-Start Failover in the Overview section. b. Select “Disable” and “Stop observer” on the Fast-Start Failover: Change Mode page. Click Continue. c. Click Yes on the confirmation page. 2. Change the protection mode from Maximum Availability to Maximum Performance. a. Click “Maximum Availability” next to Protection Mode in the Overview section. b. Select “Maximum Performance” and click Continue. c. Click Yes on the confirmation page. 3. Drop your Data Guard configuration by selecting Remove Data Guard Configuration in the Additional Administration section. Click Yes on the Confirmation: Remove Data Guard Configuration page to confirm. The “Confirmation The Data Guard configuration has been removed.” message is displayed. 4. Remove your <HOSTNAME>_SITE1 and <HOSTNAME>_SITE2 databases from Grid Control. a. Navigate to the Databases page. b. Select your <HOSTNAME>_SITE1 database and click Remove. c. Click Yes to confirm. d. Repeat for your <HOSTNAME>_SITE2 database. 5. Open a terminal window and telnet to the machine your standby databases are on. Log in as the oracle user with password of oracle . Invoke DBCA on the server machine your standby databases are on and delete your standby databases. Invoke DBCA by entering dbca at the command prompt. a. Open a terminal window and log in as the oracle user. b. Enter the command: xhost + c. Telnet to the machine your standby databases are on: telnet <hostname> d. Invoke DBCA by entering dbca at the command prompt. a. Click Next on the DBCA Welcome page. b. On the Step 1 of 2: Operations page, select “Delete a Database” and click Next. c. On the Step 2 of 2: Database page, select “dg2” and click Finish. d. Click Yes to confirm the deletion. e. Click Yes to perform another operation. f. Repeat the deletion steps for “dg3.” g. After you complete the deletion of dg3, click No to exit DBCA.
  • Practice 13: Workshop As you proceed through the workshop, use this page to record information about your databases. Primary Database Database Name: ___________________________________________________ Instance Name: ____________________________________________________ Database Unique Name: _____________________________________________ Target Name: _____________________________________________________ Host: ____________________________________________________________ Oracle Home: _____________________________________________________ Standby Database Database Name: ___________________________________________________ Instance Name: ____________________________________________________ Database Unique Name: _____________________________________________ Target Name: _____________________________________________________ Host: ____________________________________________________________ Oracle Home: _____________________________________________________ Type of standby: ___________________________________________________ Standby Database Database Name: ___________________________________________________ Instance Name: ____________________________________________________ Database Unique Name: _____________________________________________ Target Name: _____________________________________________________ Host: ____________________________________________________________ Oracle Home: _____________________________________________________ Type of standby: ___________________________________________________
  • Practice 13: Workshop Scenarios 1. You need to create a Data Guard configuration to ensure high availability, data protection, and disaster recovery for your enterprise data. You want to be able to open your standby database in read-only mode so that queries can be executed. Create your standby database to meet these requirements with the following specifications: Standby database unique and target name: <YOUR_HOSTNAME>_SITE1 Location: Create your standby database on the next highest student PC in your classroom. For example, if your host name is EDRSR8P1, create your physical standby database named EDRSR8P1_SITE1 on EDRSR8P2. Note: Your instructor may modify this configuration. Use the naming conventions provided above to avoid confusion when selecting your databases in Grid Control. Record information on page A-18. a. Select your primary database on the Databases page. b. Click Setup and Manage in the Data Guard section of the Maintenance page. c. On the Data Guard page, click Add Standby Database. d. Select “Create a new physical standby database” and click Continue. e. Select “Perform a live backup of the primary database” and click Next. f. Accept the default location for the Backup Files Directory Location. Enter the Primary Host Credentials if not already populated. Click Next. g. Accept the default instance name. Select the host for the Standby Database Location (as instructed above) and click Next. h. Select “Transfer files from the primary host backup files directory to a standby host directory” and “Convert to OFA.” Click Next. i. Click Yes for the “The following files already exist and will be overwritten: /u01/app/oracle/product/10.2.0/db_1/demo/schema/sales_history/sale1v3.dat; Click ‘Yes’ to continue, or click ‘No’ then ‘Customize’ to make changes.” warning message. j. Change the Database Unique Name and Target Name to <YOUR_HOSTNAME>_SITE1 as described above. Accept the default for the Standby Archive location. Click Next. k. Review the information and click Finish. l. When the Data Guard page reappears, select Real Time: 1 Minute Refresh from the View Data drop-down menu. You can also click the link in the Status column to review additional information. 2. You want to ensure that you have created your standby database successfully and that the redo transport and apply services are working. Use Enterprise Manager to confirm that your Data Guard configuration is functioning properly. a. Click Verify Configuration in the Additional Administration section of the Data Guard page. b. Click OK to create standby redo logs.
  • Practice 13: Workshop Scenarios (continued) 3. You understand that Data Guard can automatically detect archive gaps and resolve those gaps by copying the missing sequence of log files to the standby destination. As an example, if connectivity is lost between the primary and one or more standby databases (for example, due to network problems), redo data being generated on the primary database cannot be sent to those standby databases. Once a connection is reestablished, the missing archived redo log files (referred to as a gap) are automatically detected by Data Guard, which then automatically transmits the missing archived redo log files to the standby databases. Verify that this feature is working properly in your configuration by simulating a loss of connectivity. Disable redo transport services to your standby database, switch the log on your primary database, and reenable redo transport services to your standby database. a. Disable redo transport services as follows: On the Data Guard page, select the standby database and click Edit. Click the Standby Role Properties tab. Expand Show Advanced Properties. Select OFF in the Log Shipping drop-down menu. Click Apply. Select the Databases targets tab. b. Force three to five log switches on the primary database as follows: Click the link for your primary database on the Databases targets tab. Click Redo Log Groups on the Administration page for the primary database. Select Switch Logfile in the Actions drop-down menu and click Go. Repeat three to five times. Return to the Data Guard page and observe the difference in the current log number for the primary database and the last received log for the standby database. c. Enable redo transport services to the physical standby database as follows: On the Data Guard page, select the standby database and click Edit. Select the Standby Role Properties page. Expand Show Advanced Properties. Select ON in the Log Shipping drop-down menu. Click Apply. d. Verify that all redo has been applied as follows: Return to the Data Guard page and observe that the standby database has received the redo log files from the primary database.
  • Practice 13: Workshop Scenarios (continued) 4. Maximum performance is the default protection mode and provides the highest level of data protection that is possible without affecting the performance of the primary database. This is accomplished by allowing a transaction to commit as soon as the redo data needed to recover that transaction is written to the local online redo log. You have determined that you need to change the data protection mode to ensure the redo data needed to recover each transaction is written to both the local online redo log and to the standby redo log on at least one standby database before the transaction commits. You also want to configure the protection mode so that the primary database does not shut down if a fault prevents it from writing its redo stream to a remote standby redo log. Change the protection mode so that your configuration meets these requirements. Change the protection mode to maximum availability as follows: a. On the Data Guard page, click the link in the Protection Mode field. b. Select Maximum Availability and click Continue. c. Click Continue on the Change Protection Mode: Standby Databases and Standby Redo Log Files page. d. Click Yes on the Confirmation: Change Protection Mode page. e. After the protection mode is changed you are returned to the Data Guard page and receive a confirmation message.
  • Practice 13: Workshop Scenarios (continued) 5. You want to ensure that you will not need to re-create the primary database after you have performed a failover operation. Configure the feature that will enable you to flash back the failed primary database to a point in time before the failover and convert it into a standby database for the new primary database. Enable Flashback Database for your primary database, setting the retention time to 12 hours as follows: a. Navigate to the Maintenance page for your primary database. b. Select Recovery Settings in the Backup/Recovery Settings section of the Maintenance page. c. Verify that the “Enable Flashback Database-flashback logging can be used for fast database point-in-time recovery.” feature is selected. If it is not, select it at this time. d. Enter 12 hours in the “Flashback Retention Time” field. e. Click Apply. You receive an Update Message if the feature was previously enabled. Skip to step i. Otherwise, complete steps f – i. f. Click Yes to restart the database instance. g. Enter the Host Credentials and Database Credentials if they are not supplied. Click OK. h. Click Yes to restart the database instance. i. Return to the database home page after the database instance has been restarted. 6. You have been asked to add a data file to the EXAMPLE tablespace in your primary database. Add the data file with the following specifications: Data file name: /u01/app/oracle/oradata/orcl/example02.dbf Data file size: 2 MB Verify that the new data file has been added to your standby database. a. Add the new data file as follows: Select the primary database. Select Tablespaces in the Storage section of the Administration page. Select the EXAMPLE tablespace. Select Add Datafile in the Actions drop-down menu and click Go. Enter example02.dbf in the File Name field and 2 MB in the File Size field. Click OK. An update message is displayed.
  • Practice 13: Workshop Scenarios (continued) b. Force a log switch as follows: Return to your primary database home page. Select Redo Log Groups on the Administration page for the primary database. Select Switch Logfile in the Actions drop-down menu and click Go. c. Verify that the new data file was added to the standby database as follows: Open a terminal window and telnet to the machine your standby database is on. Log in as the oracle user with a password oracle . Set the ORACLE_SID environment variable to dg2 . You must start a SQL*Plus session to verify that the new data file was added to the standby database. Because the database is in MOUNT mode, Enterprise Manager does not display the tablespaces and datafiles. Issue the following query to verify that the file was added and then exit from SQL*Plus: SELECT name FROM v$datafile; Sample output is as follows: [oracle@EDRSR4P1 oracle]$ export ORACLE_SID=dg2 [oracle@EDRSR4P1 oracle]$ sqlplus / as sysdba SQL*Plus: Release 10.2.0.2.0 - Production on Wed Aug 23 12:49:10 2006 Copyright (c) 1982, 2005, Oracle. All Rights Reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production With the Partitioning, Oracle Label Security, OLAP and Data Mining options SQL> SELECT db_unique_name FROM v$database; DB_UNIQUE_NAME ------------------------------ EDRSR10P1_SITE1 SQL> SELECT name FROM v$datafile; NAME ---------------------------------------------------------- /u01/app/oracle/product/10.1.0/db_1/oradata/dg2/system01.dbf /u01/app/oracle/product/10.1.0/db_1/oradata/dg2/undotbs01.dbf /u01/app/oracle/product/10.1.0/db_1/oradata/dg2/sysaux01.dbf /u01/app/oracle/product/10.1.0/db_1/oradata/dg2/users01.dbf /u01/app/oracle/product/10.1.0/db_1/oradata/dg2/example01.dbf /u01/app/oracle/product/10.1.0/db_1/oradata/dg2/example02.dbf 6 rows selected. SQL> exit
  • Practice 13: Workshop Scenarios (continued) 7. The application users need to run some additional reports and do not want to impact the production system. Perform the steps required to make the standby database available for this reporting task. Verify that you can query tables in the standby database and then restart log apply services so that the standby database will be resynchronized with the primary database. a. On the Data Guard page, select the standby database and click Edit. b. Select “Read Only” in the Log Apply Services section. Click Apply. You receive the “All changes successfully applied.” message. c. Return to the Data Guard page and verify the status of “Normal, Read Only” for your standby database. d. Open a terminal window and telnet to the machine your standby database is on. Log in as the oracle user with the password oracle . Set the ORACLE_SID environment variable to dg2 . Invoke SQL*Plus. Connect as the HR user and query the HR.EMPLOYEES table as follows: SQL> SELECT count(*) FROM employees; Sample output is as follows: [oracle@EDRSR4P1 oracle]$ export ORACLE_SID=dg2 [oracle@EDRSR4P1 oracle]$ sqlplus hr/hr SQL*Plus: Release 10.2.0.2.0 - Production on Wed Aug 23 13:34:40 2006 Copyright (c) 1982, 2005, Oracle. All Rights Reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production With the Partitioning, Oracle Label Security, OLAP and Data Mining options SQL> SELECT count(*) FROM employees; COUNT(*) ---------- 107 SQL> exit Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - With the Partitioning, Oracle Label Security, OLAP and Data Mining options e. On the Data Guard page, select the standby database and click Edit. f. Select Online in the Log Apply Services section. Click Apply. The “All changes successfully applied.” message is displayed. g. Return to the Data Guard page and verify the status of Normal for your standby database.
  • Practice 13: Workshop Scenarios (continued) h. Open a terminal window and telnet to the machine your standby database is on. Log in as the oracle user with password of oracle . Invoke SQL*Plus. Connect as the HR user and attempt to query the HR.EMPLOYEES table as follows: SQL> SELECT count(*) FROM employees; Sample output is as follows: [oracle@EDRSR4P1 oracle]$ sqlplus hr/hr SQL*Plus: Release 10.2.0.2.0 - Production on Wed Aug 23 13:40:42 2006 Copyright (c) 1982, 2005, Oracle. All Rights Reserved. ERROR: ORA-00604: error occurred at recursive SQL level 1 ORA-01219: database not open: queries allowed on fixed tables/views only 8. You have determined that the users will need to run reports on a regular basis and do not want to impact the production database. In addition, you would like to add a standby database to your configuration for additional data protection. Configure a second standby database that will be available for users to perform queries, summations, and reporting activities against at all times with the following specifications: Standby database unique and target name: <HOSTNAME>_SITE2 Location: Create your standby database on the next highest student PC in your classroom. For example, if your host name is EDRSR8P1, create your standby database on EDRSR8P2. Note: Your instructor may modify this configuration. Use the naming conventions provided above to avoid confusion when selecting your databases in Grid Control. Record information on page A-18. a. On the Data Guard page, click Add Standby Database. b. Select “Create a new logical standby database” and click Continue. c. Select “Perform a live backup of the primary database” and click Next. d. Accept the default location for the Backup Files Directory Location. Enter the Primary Host Credentials if the fields are not already populated. Click Next. e. Accept the default instance name. Select the host for the Standby Database Location and click Next. f. Select “Transfer files from the primary host backup files directory to a standby host directory” and “Convert to OFA.” Click Next. g. Click Yes for the “The following files already exist and will be overwritten: /u01/app/oracle/product/10.2.0/db_1/demo/schema/sales_history/sale1v3.dat; Click ‘Yes’ to continue, or click ‘No’ then ‘Customize’ to make changes.” warning message. h. Accept the Database Name. Change the Database Unique Name and Target Name to <HOSTNAME>_SITE2 as described above. Click Next.
  • Practice 13: Workshop Scenarios (continued) i. Review the information and click Finish. j. When the Data Guard page reappears, select “Real Time: 1 Minute Refresh” from the View Data drop-down menu. You can also click the link in the Status column to review additional information. 9. Verify that the automatic gap detection and resolution feature is working properly in your configuration by simulating a loss of connectivity to your new standby database. Disable redo transport services to your standby database, switch the log on your primary database, and reenable redo transport services to your standby database. a. Disable redo transport services to the logical standby database as follows: On the Data Guard page, select the logical standby database and click Edit. Select the Standby Role Properties page. Expand Show Advanced Properties. Select OFF in the Log Shipping drop-down menu. Click Apply. Return to the Databases target page. b. Force three to five log switches on your primary database as follows: Select your primary database on the Database target page by clicking the link. Select Redo Log Groups on the Administration page for the primary database. Select Switch Logfile in the Actions drop-down menu and click Go. Repeat three to five times. Return to the Data Guard page and observe the difference in the current log number for the primary database and the last received log for the logical standby database. c. Enable redo transport services to the logical standby database as follows: On the Data Guard page, select your logical standby database and click Edit. Select the Standby Role Properties page. Expand Show Advanced Properties. Select ON in the Log Shipping drop-down menu. Click Apply. d. Verify that all redo has been applied to the logical standby database as follows: Return to the Data Guard page and observe that the logical standby database has received the redo log files from the primary database.
  • Practice 13: Workshop Scenarios (continued) 10. Because the users want to use some tables in the new standby database to report against for historical purposes, you need to configure SQL Apply so that certain DML statements are not executed against those tables on the logical standby database. You decide to test this feature first by creating a new table on the primary database as follows: CREATE TABLE hr.emp_name AS SELECT first_name, last_name FROM hr.employees WHERE 1=2; Define a filter that prevents SQL Apply from issuing DML statements against the HR.EMP_NAME table on the logical standby database. Insert a few rows into the HR.EMP_NAME table on the primary database and commit your changes. Force a log switch on the primary database and then verify that the new rows are not applied to your logical standby database. a. Open a terminal window. b. Change to the labs directory. c. Invoke SQL*Plus and connect as hr/hr . Execute the lab_13_10_c.sql script in your labs directory to create the HR.EMP_NAME table as described. Maintain the SQL*Plus session for later steps. Note: If you receive an error regarding ORACLE_HOME , set it to: /u01/app/oracle/product/10.2.0/db_1 d. Configure SQL Apply on the logical standby database so that no DML statements are executed against the HR.EMP_NAME as follows: Navigate to the Data Guard page. Select the logical standby database and click Edit. Click Standby Role Properties. Expand Show Advanced Properties. Click Add in the Skip Table Entries section. Enter the following information in the specified fields: SQL Statement: DML Schema: HR Object Name: EMP_NAME Select “Always skip this statement type.” Click OK. Verify the information in the Skip Table Entries section and click Apply. A success message is displayed.
  • Practice 13: Workshop Scenarios (continued) e. In your SQL*Plus session, execute the lab_13_10_e.sql script in the labs directory to insert two rows in the HR.EMP_NAME table as follows: INSERT INTO hr.emp_name VALUES ('Don','Miller'); INSERT INTO hr.emp_name VALUES ('Sally','Hebert'); COMMIT; Exit from your SQL*Plus session. f. On your primary database, force a log switch as follows: Access the Administration page for your primary database. Click Redo Log Groups. Select Switch logfile in the Actions drop-down menu and click Go. g. Access your logical standby database and query the HR.EMP_NAME table to determine if any rows have been inserted into the table as follows: Open a terminal window and telnet to the machine your standby database is on. Log in as the oracle user with password of oracle . Invoke SQL*Plus for your logical standby database. Connect as hr/hr . Issue the following command: SELECT count(*) FROM emp_name; There should be no rows in the emp_name table. Exit from SQL*Plus. Sample output is as follows: [oracle@EDRSR4P1 oracle]$ export ORACLE_SID=dg3 [oracle@EDRSR4P1 oracle]$ sqlplus hr/hr SQL*Plus: Release 10.2.0.2.0 - Production on Thu Aug 24 07:00:58 2006 Copyright (c) 1982, 2005, Oracle. All Rights Reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production With the Partitioning, Oracle Label Security, OLAP and Data Mining options SQL> SELECT count(*) FROM emp_name; COUNT(*) ---------- 0 SQL> exit
  • Practice 13: Workshop Scenarios (continued) 11. You have been asked to create a view for the users to query on the logical standby database. Create the view as follows: CREATE VIEW hr.emp_90_vw AS SELECT * FROM hr.employees WHERE department_id=90; a. Invoke SQL*Plus and connect to your logical standby database as the SYS user. Set the Data Guard guard to STANDBY so that you can create a view by issuing the following statement: ALTER DATABASE GUARD STANDBY; Sample output is as follows: [oracle@EDRSR4P1 oracle]$ export ORACLE_SID=dg3 [oracle@EDRSR4P1 oracle]$ sqlplus / as sysdba SQL*Plus: Release 10.2.0.2.0 - Production on Thu Aug 24 07:04:17 2006 Copyright (c) 1982, 2005, Oracle. All Rights Reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production With the Partitioning, Oracle Label Security, OLAP and Data Mining options SQL> ALTER DATABASE GUARD STANDBY; Database altered. SQL> exit b. Connect to your logical standby database as HR , with HR as the password. Create a view on the HR.EMPLOYEES table as follows: CREATE VIEW emp_90_vw AS SELECT * FROM employees WHERE department_id=90; You can use the lab_13_11_b.sql script to create the view. Sample output follows: [oracle@EDRSR8P1 ~]$ cd labs [oracle@EDRSR8P1 labs]$ sqlplus hr/hr SQL*Plus: Release 10.2.0.2.0 - Production on Thu Aug 24 07:09:21 2006 Copyright (c) 1982, 2005, Oracle. All Rights Reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0-Production With the Partitioning, Oracle Label Security, OLAP and Data Mining SQL> @lab_13_11_b.sql View created.
  • Practice 13: Workshop Scenarios (continued) c. Connect to your logical standby database as SYS and set the Data Guard guard back to ALL as follows. Exit from SQL*Plus. ALTER DATABASE GUARD ALL; Sample output is as follows: SQL> connect / as sysdba Connected. SQL> ALTER DATABASE GUARD ALL; Database altered. SQL> exit 12. You have experienced a failure on your primary database server. Fail over to your physical standby database. a. On the Data Guard page, select your physical standby database and click Failover. On the Confirmation: Redirect page, click Yes to continue with the failover. Supply the database login information. Click Continue. Supply operating system credentials. Click Continue. On the Confirmation: Failover page, select Complete and click Yes. The Processing: Failover page is displayed. The Data Guard page is displayed after processing completes. b. Force one or two log switches as follows: Click on the link for your new primary database. Select the Administration page and click Redo Log Groups. Select “Switch logfile” from the Actions drop-down menu and click Go. Repeat. Return to the Data Guard page.
  • Practice 13: Workshop Scenarios (continued) 13. You have been able to restore the server on which your primary database was originally located. Add your original primary database back into your Data Guard configuration as a physical standby database. a. You can use Enterprise Manager to enable the physical standby database as follows: Access the Data Guard page. Your new physical standby database shows a status of “Database must be reinstated.” Click the “Database must be reinstated” link. On the Edit Standby Database Properties page, click Reinstate. Click Yes to confirm reinstating. The new physical standby database is reset and is now part of your configuration. Click Verify to verify your Data Guard configuration. Review the results of the verify and click OK to return to the Data Guard configuration. 14. Return to your original Data Guard configuration with your HOSTNAME_ORCL.oracle.com database as your primary database. a. Perform a switchover operation by selecting your current physical standby database and clicking Switchover. Click Yes to confirm the switchover operation.

Transcript

  • 1. APractice Solutions
  • 2. Practice 1-1: OverviewA-2 Copyright © 2006, Oracle. All rights reserved.
  • 3. Practice 1: OverviewA-3 Copyright © 2006, Oracle. All rights reserved.
  • 4. Practice 2-1: Architecture OverviewA-4 Copyright © 2006, Oracle. All rights reserved.
  • 5. Practice 2-2: Installing the Oracle Management AgentA-5 Copyright © 2006, Oracle. All rights reserved.
  • 6. Practice 2-2: Installing the Oracle Management AgentA-6 Copyright © 2006, Oracle. All rights reserved.
  • 7. Practice 2-3: Configuring Your Primary DatabaseA-7 Copyright © 2006, Oracle. All rights reserved.
  • 8. Practice 2-3: Configuring Your Primary DatabaseA-8 Copyright © 2006, Oracle. All rights reserved.
  • 9. Practice 2-3: Configuring Your Primary DatabaseA-9 Copyright © 2006, Oracle. All rights reserved.
  • 10. Practice 4: Creating a Physical Standby Database Using EMA - 10 Copyright © 2006, Oracle. All rights reserved.
  • 11. Practice 4: Creating a Physical Standby Database Using EMA - 11 Copyright © 2006, Oracle. All rights reserved.
  • 12. Practice 4: Creating a Physical Standby Database Using EMA - 12 Copyright © 2006, Oracle. All rights reserved.
  • 13. Practice 6: Data Protection Modes and Redo Transport ServicesA - 13 Copyright © 2006, Oracle. All rights reserved.
  • 14. Practice 7: Creating a Logical Standby Database Using EMA - 14 Copyright © 2006, Oracle. All rights reserved.
  • 15. Practice 7: Creating a Logical Standby Database Using EMA - 15 Copyright © 2006, Oracle. All rights reserved.
  • 16. Practice 9: Switchover and FailoverA - 16 Copyright © 2006, Oracle. All rights reserved.
  • 17. Practice 9: Switchover and FailoverA - 17 Copyright © 2006, Oracle. All rights reserved.
  • 18. Practice 10: Fast-Start FailoverA - 18 Copyright © 2006, Oracle. All rights reserved.
  • 19. Practice 10: Fast-Start FailoverA - 19 Copyright © 2006, Oracle. All rights reserved.
  • 20. Practice 13: Workshop PreparationA - 20 Copyright © 2006, Oracle. All rights reserved.
  • 21. Practice 13: Workshop Recording PageA - 21 Copyright © 2006, Oracle. All rights reserved.
  • 22. Practice 13: Workshop ScenariosA - 22 Copyright © 2006, Oracle. All rights reserved.
  • 23. Practice 13: Workshop ScenariosA - 23 Copyright © 2006, Oracle. All rights reserved.
  • 24. Practice 13: Workshop ScenariosA - 24 Copyright © 2006, Oracle. All rights reserved.
  • 25. Practice 13: Workshop ScenariosA - 25 Copyright © 2006, Oracle. All rights reserved.
  • 26. Practice 13: Workshop ScenariosA - 26 Copyright © 2006, Oracle. All rights reserved.
  • 27. Practice 13: Workshop ScenariosA - 27 Copyright © 2006, Oracle. All rights reserved.
  • 28. Practice 13: Workshop ScenariosA - 28 Copyright © 2006, Oracle. All rights reserved.
  • 29. Practice 13: Workshop ScenariosA - 29 Copyright © 2006, Oracle. All rights reserved.
  • 30. Practice 13: Workshop ScenariosA - 30 Copyright © 2006, Oracle. All rights reserved.
  • 31. Practice 13: Workshop ScenariosA - 31 Copyright © 2006, Oracle. All rights reserved.
  • 32. Practice 13: Workshop ScenariosA - 32 Copyright © 2006, Oracle. All rights reserved.
  • 33. Practice 13: Workshop ScenariosA - 33 Copyright © 2006, Oracle. All rights reserved.
  • 34. Practice 13: Workshop ScenariosA - 34 Copyright © 2006, Oracle. All rights reserved.