OCA: Oracle Database 11g Administrator Certified Associate Study Guide- P22

Chia sẻ: Thanh Cong | Ngày: | Loại File: PDF | Số trang:50

0
47
lượt xem
15

OCA: Oracle Database 11g Administrator Certified Associate Study Guide- P22

Mô tả tài liệu

OCA: Oracle Database 11g Administrator Certified Associate Study Guide- P22: There is high demand for professionals in the information technology (IT) industry, and Oracle certifications are the hottest credential in the database world. You have made the right decision to pursue certification, because being Oracle Database 11g certified will give you a distinct advantage in this highly competitive market.

Chủ đề:

Bình luận(0)

Lưu

Nội dung Text: OCA: Oracle Database 11g Administrator Certified Associate Study Guide- P22

4. 984 Chapter 17 N Moving Data and Using EM Tools If you choose custom packaging, the screen will look like Figure 17.16. Here Oracle will show you all the incidents to report and the files that are being packaged. You can exclude the files you do not want to send. Also, you have the option to add more incidents to the same package. F i g U r E 17.1 6 Customize Package screen In the Packaging Tasks section, you have the option to add more problems or exclude problems. You can also edit the files you sent to Oracle. Once you have added all the neces- sary files, click the Finish Contents Preparation link. You will see a confirmation screen with all the files you choose to include in the packaging and an option to generate the upload file. After the file is generated, the Send to Oracle button will be enabled, and you can use it to send the information to Oracle. Configuring Incident Packaging You can customize the package-retention and -configuration rules by using the Incident Packaging Configuration link in the Related Links section of the Support Workbench screen. Figure 17.17 shows the default retention and packaging settings.
5. Using EM Support Workbench 985 F i g U r E 17.17 Incident packaging configuration Click the Edit button to change the defaults. You can change the following values: Incident Metadata Retention Period Information such as the incident ID, time, and prob- lem are known as the metadata. The default is to keep this information for 365 days. Incident Files Retention Period Specify how long you want to keep the files (data) related to an incident; the default is 30 days. Cutoff Age for Incident Inclusion Include the incidents that are not older than the value specified here in days. Leading Incidents Count and Trailing Incidents Count If a problem has several incidents, the packaging by default includes only three incidents from the time it started occurring and three incidents from the latest occurrence. Correlation Time Proximity Specify the interval in minutes that should be treated as “happened at the same time” for related incidents. The default is 90 minutes. Time Window for Package Content This is the time in minutes to include incidents in the package; the default is 24 minutes. Tracking and Closing the Incident You can track the progress of the incident by adding comments to the activity log. The activ- ity log is available on the Problem Details screen as well as on the packaging screens. The Activity Log tab shows the system-generated operations that have occurred on the problem
7. Using EM to Manage Patches 987 number, 1 is the maintenance release number, 0 is the application-server release number, 6 is the component-specific release number, and 0 is the platform-specific release number. When a patch release is applied, the component-specific release number will change. Patch releases go through rigorous regression testing. Patch releases are cumulative, which means the latest patch release will include most interim patches and critical patch updates, as well as lower patch releases. Interim patches Interim patches are one-off patches to fix a specific issue on a platform. The Oracle release numbers do not change when applying interim patches. Interim patches do not go through regression testing. Critical patch updates Critical patch updates (CPUs) include security patches and other patches that depend on the security patches. CPUs are cumulative, which means previ- ous CPUs are included. CPUs go through regression testing, and they do not advance the release numbers. Patch releases are installed using the Oracle Universal Installer (OUI). You can install interim patches and CPUs using the OPatch utility. You can use opatch lsinventory to review all the patches applied to an Oracle Home installation: ORACLE_HOME/OPatch/opatch lsinventory Invoking OPatch 11.1.0.6.0 Oracle Interim Patch Installer version 11.1.0.6.0 Copyright (c) 2007, Oracle Corporation. All rights reserved. Oracle Home : /u01/app/oracle/product/11.1.0/db_1 Central Inventory : /u01/app/oraInventory from : /etc/oraInst.loc OPatch version : 11.1.0.6.0 OUI version : 11.1.0.6.0 OUI location : /u01/app/oracle/product/11.1.0/db_1/oui Log file location : /u01/app/oracle/product/11.1.0/db_1/  cfgtoollogs/opatch/opatch2008-11-16_23-08-22PM.log Lsinventory Output file location : /u01/app/oracle/product/11.1.0/db_1/cfgtoollogs/opatch/  lsinv/lsinventory2008-11-16_23-08-22PM.txt -------------------------------------------------------------------------------- Installed Top-level Products (1): Oracle Database 11g 11.1.0.6.0 There are 1 products installed in this Oracle Home.
8. 988 Chapter 17 N Moving Data and Using EM Tools Interim patches (1) : Patch 6529615 : applied on Sun Nov 16 23:08:05 CST 2008 Created on 7 Nov 2008, 04:01:26 hrs US/Pacific Bugs fixed: 6529615 -------------------------------------------------------------------------------- OPatch succeeded. $To apply a patch using OPatch, first read the README.txt file accompanying each patch for instructions. Most of the patches are installed by using the opatch apply statement, from the patch staging directory. Enterprise Manager can be used to review, download, and apply patches. The patch-management links are in the Database Software Patching section on the Software and Support tab of Database Control, as shown in Figure 17.19. F i g U r E 17.1 9 Database Software Patching links on EM I will discuss each link in the following sections. Using the Patch Advisor The Patch Advisor shows the critical patch updates and the recommended patches for the release of the database on your server. Before you can use the Patch Advisor, you must set up Metalink login credentials and perform Metalink integration with EM. You can do this in two steps: 1. Enter the Metalink username and password. Click the Setup link on the top-right corner of EM Database Control. Click Patching Setup on the left menu, as shown in Figure 17.20. 2. Run the Refresh from Metalink job. Under the Related Links section on the Database Control home page, click the Jobs link to invoke the Job Activity screen. Under the Create drop-down list, choose Refresh from Metalink, and click Go, as shown in Figure 17.21. Click the Patch Advisor link on the screen shown in Figure 17.19. The Patch Advi- sor screen shows critical security patches that need to be applied to ORACLE_HOME and 9. Using EM to Manage Patches 989 recommended patches, as shown in Figure 17.22. Oracle can show the recommended patches based on the features used in the database. Select All from the drop-down box to show all the recommended patches. F i g U r E 17. 2 0 Software patching setup in EM F i g U r E 17. 2 1 Refresh from Metalink job setup in EM 10. 990 Chapter 17 N Moving Data and Using EM Tools F i g U r E 17. 2 2 Patch Advisor screen on EM You can also invoke the patching setup screen by clicking the Patching Setup link in the Related Links section. Viewing the Patch Cache The patch cache is the location on the server where all your patches are downloaded and kept. One advantage of having the patch cache is that you can apply the patch to multiple Oracle Homes from one download. Figure 17.23 shows the Patch Cache screen. F i g U r E 17. 2 3 Patch Cache screen in EM You can click the View ReadMe button to read the patch application details, and you can click the Patch button to apply the patch. 11. Using EM to Manage Patches 991 Finding the Patch Prerequisites Click the Patch Prerequisite Check link to get the screen to evaluate the standard prerequisite checks on Oracle Home and Server with deployment-specific checks. Figure 17.24 shows the Patch prerequisite checker screen. F i g U r E 17. 2 4 Patch Prerequisite Checker screen in EM Staging a Patch You can download patches from Metalink and stage them for later application. Figure 17.25 shows the staging patch screen. You can select the patch to download by specifying the patch number or by specifying the product and release-number criteria. When the patches are displayed, choose the patch you want to stage. Click Next to prepare for staging or applying the patch. On the next screen, specify the targets or destination of the patch. You can choose the Oracle Instance name or the Oracle home location. On the Set Credentials screen, specify the host operating-system username and password. On the Stage or Apply screen, you can choose to download the patch or to apply the patch after downloading. On the Schedule screen, specify whether you want the patch to be downloaded immediately or at a later time. Figure 17.26 shows the Summary screen. Review the patch sizes, where the patches will be applied, and so on, and click the Finish button to download the patch. 12. 992 Chapter 17 N Moving Data and Using EM Tools F i g U r E 17. 2 5 Staging patch screen in EM F i g U r E 17. 2 6 Patch: Summary screen in EM Staged patches are stored under the$ORACLE_HOME/EMStagedPatches directory in this example.