I want to know about single patches as well as critical patch updates CPU. Is there a data dictionary view to list patches? Answer: Oracle provides many ways to list patches:. The OS opatch command: This opatch command list all patches that have been applied. The data dictionary: You can query sys. Below we run the opatch command with the lsinventory option to list patches:.
Optionally, you can use the -display flag with opatch to see details on applied patches:. Oracle released a good number of versions since and the latest version is 19C which is available for on-premise as well as in the cloud. Many of the users are still using 11g, 12c, and 18C. Internally, Oracle maintains versions as five numeric segments XX. X divided by periods. Just run a query against these views to find out the database version.
Knowing the version information is useful when you open a support request or when a patch needs to be applied. The installation procedure for the new Oracle Database 11 g Release 2 This is referred to as an out-of-place upgrade and is different from patch set releases for earlier releases of Oracle Database, where the patch set was always installed in place. Oracle strongly recommends that you follow the steps in this procedure to ensure minimal downtime for the upgrade process and integrity of the new binaries and software libraries.
If you are upgrading an Oracle RAC database, then you must perform the following steps in the order shown:. Perform operating system prerequisite checks on each of the nodes that you intend to upgrade, to ensure that they meet the system prerequisites for Oracle Grid Infrastructure Oracle Clusterware and Oracle ASM. If necessary, perform patch upgrades of the earlier release of Oracle Clusterware or Oracle Cluster Ready Services software to the most recent patch version.
Ensure that you are logged in as the user that you want to own the Oracle Grid Infrastructure installation, and run the Oracle Grid Infrastructure installation. Provide information as prompted by the installer. When prompted, open a separate terminal session, log in as root , and run root.
After upgrading Oracle Clusterware, follow the instructions in your Oracle operating system-specific documentation to prepare for installation of Oracle Database software and start the Oracle Universal Installer.
You can then run DBUA independently after the installation is complete. When installation of Oracle Database software has completed successfully, click Exit to close Oracle Universal Installer. The software for Oracle Database 11 g Release 2 It is not necessary to check for patch set updates before proceeding with the upgrade process for this release. However, Oracle recommends that you periodically check for patches and patch set updates as a part of database administration.
After you have installed the software for Oracle Database 11 g Release 2 This is done by running the Pre-Upgrade Information Tool from the environment of the database you are to upgrade. This is a required step if you are upgrading manually; otherwise, the catupgrd. The Pre-Upgrade Information Tool displays warnings about possible upgrade issues with the database. The output in Example shows the report that is generated from running the Pre-Upgrade Information Tool after installing the software for Oracle Database 11 g Release 2 In addition to the warnings that the tool displays, you must address any errors described in the output of the Pre-Upgrade Information Tool before performing the upgrade.
For invalid objects or invalid components, Oracle recommends running the the utlrp. The following topics contain sample output of the Pre-Upgrade Information Tool and provide descriptions of each section of the output. The Database section displays global database information about the current database, such as the database name, release number version , compatibility level, blocksize, OS platform, and time zone file. The Tablespaces section displays a list of tablespaces in the current database.
For each tablespace, the tablespace name and minimum required size is displayed. In addition, a message displays next to each tablespace confirming that the tablespace is adequate for the upgrade.
If the minimum required size is not met, then you must make adjustments, which the tool recommends. In a manual upgrade using SQL scripts and utilities, space must be added to tablespaces that do not have enough free space in the current database. These tablespace adjustments must be made before the database is upgraded. Some of these tasks are performed automatically by DBUA.
The Rollback Segments section shows the status for rollback segments in the SYSTEM tablespace and displays a warning about any adjustments that need to be made before performing the upgrade.
This section only appears if there are rollback segments. The Flashback section shows whether flashback is ON or OFF, and displays warnings about pool size and cache size that must be increased. The Update Parameters section displays a list of initialization parameters in the parameter file init. The adjustments must be made to the parameter file after it is copied to the new Oracle Database 11 g release.
If you are using Oracle ASM disk groups, then you must ensure that the database compatibility attribute for the disk groups matches the compatibility parameter that is set in init. The Renamed Parameters section displays a list of initialization parameters in the parameter file of the current database that are renamed in the new Oracle Database 11 g release.
New default values are also given. Obsolete initialization parameters must be removed from the parameter file before the database is upgraded. The Components section displays a list of database components in the database to be upgraded or installed when the current database is upgraded to the new Oracle Database 11 g release.
Miscellaneous Warnings Section Contents. The Miscellaneous Warnings section provides warnings about specific situations that require attention before or after the upgrade. For example, if the database is using a time zone file that is a version older than what is required for the upgrade, then a warning displays with the required action. The Recommendations section provides Oracle recommendations, including the recommended SQL statements and commands, that should be performed before upgrading to the new Oracle Database 11 g release.
Before upgrading to the new Oracle Database 11 g release, Oracle recommends analysis of the information and warnings displayed by the Pre-Upgrade Information Tool. The following topics describe warnings and the appropriate actions to take. After upgrading to the new Oracle Database 11 g release from Oracle9 i Release 2 9.
If you have applications that use one of these packages, then you must install Oracle XML DB if it is not currently installed. After upgrading to the new Oracle Database 11 g release, you may need to assess the dependencies of network utility packages and provide access by adding the appropriate access control lists ACLs.
To check the status of access and add ACLs for network utility packages. Prepare post-upgrade scripts now to make the scripts available for use in the test environment. This ensures the new access controls are part of your upgrade testing.
To configure network access control lists ACLs in the database so that these packages can work as they did in prior releases, see the example script provided in "Configuring Fine-Grained Access to External Network Services After Upgrading Oracle Database". After the upgrade, you must grant the specific required privileges. Access is based on the usage in the original database.
This information is important only if you need to downgrade to your original database release after performing the upgrade. During the upgrade to the new Oracle Database 11 g release from Oracle9 i Release 2 9. To downgrade to the original release, all of the database links with encrypted passwords must be dropped before the downgrade.
Consequently, the database links are nonexistent in the downgraded database. This dump file can then be used to replace the database links after the downgrade. Ensure that you know the password for any newly-created database links that is, database links that you may have created while running the new release.
Knowing the database link password is necessary because you will need to reset the database link password after downgrading to an earlier release. The time zone files that are supplied with Oracle Database 11 g Release 2 The time zone behavior for Oracle Database 11 g Release 2 You must make sure to obtain the latest time zone files before you upgrade the database.
If the time zone file version of the database being upgraded is not the most recent version of the time zone file available for the new Table describes the warnings and summarizes how to resolve a mismatch in time zone file versions. Earlier than the most current version included in the new database release and the Pre-Upgrade Information Tool displays "Database is using a time zone file older than version n.
Later than the version included in the new database release and the Pre-Upgrade Information Tool displays "Database is using a time zone file greater than version n. Otherwise the upgrade will fail. You must patch the Oracle home with the appropriate patch for the time zone file version in use.
Apply the patch for each database to be upgraded. Otherwise, the upgrade script terminates without upgrading the database. Oracle Database Globalization Support Guide for detailed descriptions of time zone upgrade. When upgrading to the new Oracle Database 11 g release, optimizer statistics are collected for dictionary tables that lack statistics.
This statistics collection process can be time consuming for databases with a large number of dictionary tables, but statistics gathering only occurs for those tables that lack statistics or are significantly changed during the upgrade.
To decrease the amount of downtime incurred when collecting statistics. Collect statistics before performing the actual database upgrade. For example, you can enter the following SQL statement:. Table lists the system components and schemas that are checked for statistics collection during the upgrade.
If you plan to downgrade Oracle Enterprise Manager Database Control after upgrading to the new Oracle Database 11 g release, then you must save your database control files and data before upgrading your database.
Oracle provides the emdwgrd utility to use before upgrading your database to keep a copy of your database control files and data. The emdwgrd utility consists of emdwgrd and emdwgrd. Before running the utility, you must install the software for the new Oracle Database 11 g release, and then invoke the script from the new Oracle home.
Install the software for the new Oracle Database 11 g release. This step is not required for an in-place patch set upgrade. If the database is an Oracle RAC database, remote copy is required across the cluster nodes. Define an environment variable to indicate which remote copy is configured. If the release 10 g Oracle home is on a shared device, add -shared to the previous command line.
You must wait until all materialized views have completed refreshing before upgrading. You can query the system to determine if there are any materialized view refreshes still in progress. To determine if there are any materialized view refreshes still in progress. Before upgrading the database, you must ensure that there are no files requiring media recovery.
You can query the system to get a list of files and then recover them as appropriate. Files must not be in backup mode when performing the upgrade; therefore, you must wait until backups are completed. You can query the system to see a list of any files in backup mode and then take appropriate action by either waiting for the backup to complete, or by aborting any backups that are not needed. You must resolve outstanding distributed transactions before performing the upgrade.
You can do this by first querying to see any pending transactions, and then committing the transactions. You must wait until all pending distributed transactions have been committed. If the query in the previous step returns a row, then synchronize the standby database with the primary database.
Make sure all the logs are transported to the standby server after a final log switch in the primary. The database recycle bin must be empty before you begin the upgrade process. You use the PURGE statement to remove items and their associated objects from the recycle bin and release their storage space. The database recycle bin must be empty during the upgrade process to avoid possible ORA errors and to minimize the upgrade time. If you are upgrading from Oracle9 i and a listener was not configured in the Oracle9 i repository, then you must run Oracle Net Configuration Assistant to configure the listening protocol address and service information for the new Oracle Database 11 g database, including a listener.
A new version of the listener is required for an Oracle Database 11 g database. Previous versions of the listener are not supported for use with an Oracle Database 11 g database.
However, it is possible to use the new version of the listener with previous versions of Oracle Database. This is a two-step option. You must first run Oracle Net Configuration Assistant from the old Oracle home to remove the old listener. Then you must run Oracle Net Configuration Assistant again from the Oracle home of the new Oracle Database 11 g release to create a new listener. You must remove the old listener before creating a new one.
If you attempt to create a new listener from the new Oracle home first, and use the same name and port as the old listener, then Oracle Net Configuration Assistant returns an error. DBUA provides a graphical user interface GUI to guide you through the upgrade of a database, or you can invoke it in silent mode, which does not present a user interface.
Important: If you terminate the upgrade, but do not restore the database, then you cannot restart DBUA. Instead, you must continue with a manual command line upgrade as described in "Manually Upgrading Oracle Database".
The procedure to upgrade patch releases is no different from the normal upgrade procedure. If you are upgrading an existing Oracle Enterprise Manager Database Control or if you are configuring a new Oracle Enterprise Manager Database Control for the new Oracle Database 11 g release, then the listener must be running before upgrading Oracle Enterprise Manager.
If DBUA detects that an Oracle Enterprise Manager upgrade or configuration is requested, and DBUA does not see a listener running, then it prompts you and starts the default listener in either of these cases. If the database instance is not running, then DBUA tries to start the instance with the default initialization parameter file. If that fails, then DBUA prompts you to provide the name of the correct initialization parameter file or to start the instance.
If the instance is up and running, then DBUA connects to it. You cannot go back to the original server unless you restore your database. If you need to re-run the upgrade, then you must run DBUA from the restored backup of the database you are upgrading. The presence of this file indicates to DBUA that this is a re-run operation.
If you installed Oracle Database 11 g Release 2 However, if you did not specify that you are upgrading an existing database, then you can start DBUA independently after installation is complete. While the upgrade is in process, DBUA shows the upgrade progress for each component.
To enhance security, DBUA automatically locks new user accounts in the upgraded database. DBUA then proceeds to create new configuration files parameter and listener files in the new Oracle home. Listener running if Oracle Enterprise Manager Database Control upgrade or configuration is requested. During the upgrade, DBUA automatically modifies or creates new required tablespaces and invokes the appropriate upgrade scripts, as follows:.
If the datafiles are auto extensible and have enough disk space to grow, then DBUA continues with the upgrade. If the datafiles are not autoextensible, then DBUA prompts you and makes the files auto extensible. If there is not enough disk space to grow, then DBUA prompts you to create space by adding more datafiles. Complete the following steps to upgrade a database using the DBUA graphical user interface.
These steps are performed from within the new Oracle home where the latest database software has been installed as described in "Installing the New Oracle Database Software for the Upgrade". If you terminate the upgrade, but do not restore the database, then you cannot restart DBUA. If you need help at any screen or want to consult more documentation about DBUA, then click Help to open the online help. Select the database you want to upgrade to Oracle Database 11 g Release 2 You can select only one database at a time.
If you do not see the database that you want, then make sure an entry with the database name exists in the oratab file in the etc directory. DBUA analyzes the database, performing pre-upgrade checks and displaying warnings as necessary. Examples of DBUA database checks include:. Redo log files whose size is less than 4 MB. When you upgrade a database to Oracle Database 11 g Release 2 The time it takes to recompile the module can result in poor performance when you begin to use your newly upgraded database.
To eliminate these performance issues, select Recompile invalid objects at the end of upgrade. This ensures that you do not experience any performance issues later, as you begin using your newly upgraded database.
If you have multiple CPUs, then you can reduce the time it takes to perform this task by taking advantage of parallel processing on your available CPUs.
You can adjust this default value by selecting a new value from the Degree of Parallelism menu. Oracle strongly recommends that you back up your database before starting the upgrade. If errors occur during the upgrade, then you might be required to restore the database from the backup. If you use DBUA to back up your database, then it makes a copy of all your database files in the directory you specify in the Backup Directory field.
DBUA performs this cold backup automatically after it shuts down the database and before it begins performing the upgrade procedure. The cold backup does not compress your database files, and the backup directory must be a valid file system path. You cannot specify a raw device for the cold backup files. In addition, DBUA creates a batch file in the specified directory. You can use this batch file to restore the database files:.
If you choose not to use DBUA for your backup, then Oracle assumes you have backed up your database using your own backup procedures. Your database files are moved to Oracle ASM storage, which must currently exist on your system. The Recovery and Diagnostic Locations screen displays, where you can designate a flash recovery area for your database. Flash recovery area is an Oracle managed disk location used for storing backup and recovery related files.
Oracle strongly recommends configuring a flash recovery area, because it significantly enhances speed, reliability, and manageability of the database recovery process. The location of the flash recovery area is also used by Enterprise Manager if you enable local management and daily backups on the Management Options screen. If you selected the Move Database Files during Upgrade option in step 5 , or if an Oracle Express Edition database is being upgraded to Oracle Enterprise Edition, then you must configure a flash recovery area.
If a flash recovery area is currently configured, then the current settings are retained but the screen displays to allow you to override these values. Enter the full path to a different location in the Flash Recovery Area field. If no other database is currently being monitored with Enterprise Manager, then the Management Options screen displays. At the Management Options screen, you have the option of setting up your database so it can be managed with Enterprise Manager.
Enterprise Manager provides Web-based management tools for managing individual database instances, as well as central management tools for managing your entire Oracle environment, including multiple databases, hosts, application servers, and other components of your network. To set up your database to be managed with Enterprise Manager, select Configure the Database with Enterprise Manager and then select one of the following options:. If you select this option, then you must also select an Oracle Management Service from the Management Service drop-down list.
When you finish installing the Oracle Database software, the database is automatically available as a managed target within Oracle Enterprise Manager Grid Control.
If you are not centrally managing your Oracle environment, then you can still use Enterprise Manager to manage your database. When you install Oracle Database, you automatically install Oracle Enterprise Manager Database Control, which provides Web-based features for monitoring and administering the single-instance or cluster database you are installing.
Do the following steps if you want the SYSMAN user the default Super Administrator and owner of the Management Repository schema to receive E-mail notification when a metric for a specified condition reaches a critical or warning threshold:. For example, Enterprise Manager can send an e-mail when a target goes down or when there are database space usage problems. E-mail notifications are enabled immediately upon installation. Do the following steps to use the Oracle suggested backup strategy to back up your entire database with a minimum amount of configuration:.
Enter host credentials in the OS Username and Password fields. If you select the Enable Daily Disk Backup to Recovery Area option, then Enterprise Manager is configured to back up your database immediately after you finish upgrading Oracle Database.
0コメント