分类： Oracle
2008-10-10 23:04:10
Patch Set Notes
Release 2 (9.2.0.8) Patch Set 7for Microsoft Windows (32-Bit)
August 2006
These patch set notes accompany the Oracle9irelease 2 (9.2.0.8) patch set.
This document contains the following sections:
Patch sets are a mechanism for delivering fully tested and integrated product fixes. Patch sets provide bug fixes only; they do not include new functionality and they do not require certification on the target system.
Patch sets include all of the libraries that have been rebuilt to implement the bug fixes in the set. All of the fixes in the patch set have been tested and are certified to work with each other. Because patch sets include only low impact fixes, you are not required to certify applications or tools against the unless directed to by the operating system vendor.
Patch sets are cumulative. Patch set release 9.2.0.8 includes all fixes in patch sets 9.2.0.8 and earlier as well as new fixes for patch set 9.2.0.8. This means that unless the patch set documentation indicates otherwise, you can apply this patch set to any earlier release 9.2 installation. You do not have to install intermediate patch sets.
Patch sets contain generic fixes that apply to all platforms. Patch sets may also include additional platform-specific patches.
|
Note: Oracle provides both 32-bit and 64-bit versions of Oracle9ifor Windows. Currently, the 32-bit version of the patch set must only be installed on the 32-bit version of the database. The 64-bit version of the patch set must only be installed on the 64-bit version of the database. |
For a list of products included in this patch set, see the"Patch Set Components"section.
This patch set includes Oracle Universal Installer release 10.1.0.5. You must use this Oracle Universal Installer to install this patch set and not Oracle Universal Installer from the 9.2.0.xmaintenance release media or Oracle home.
This is not a complete software distribution. You must install it in an existing Oracle9irelease 2 (9.2.0.x.x) installation. Users applying this patch setmustuse Oracle Universal Installer release 10.1.0.5 (provided as part of this patch set) or later to ensure that their Oracle home can be patched in the future. Oracle Universal Installer release 10.1.0.5 is also installed when you install this patch set.
There are two documents related to this release of the Oracle9irelease 2 patch set:
Oracle9i Patch Set Notes, Release 2 (9.2.0.8) Patch Set 7 forMicrosoft Windows (32-Bit)(this document)
This document provides:
System requirements and information about how to install or reinstall the patch set
A list of all bugs fixed to date that are specific to Oracle9irelease 2 for Microsoft Windows (32-Bit)
A list of known issues relating to Oracle9irelease 2 for Microsoft Windows (32-Bit)
Oracle9i List of Bugs Fixed, Release 2 (9.2.0.8) Patch Set 7
TheList of Bugs Fixedis a list of all generic bugs related to Oracle9irelease 2 that have been fixed in this release.
Both of these documents are included with the patch set. TheOracle9i List of Bugs Fixedis also available on OracleMetalink, from document 189908.1,
ALERT: Oracle9i Release 2 (9.2) Support Status and Alertsat:
To locate document 189908.1:
ClickAdvancedat the top of the OracleMetalinkpage.
Enter 189908.1 in theDocument IDfield, then clickSubmit.
The following are the system requirements for this patch set:
System Architecture:
Intel Pentium and AMD processors
Operating System
Windows Server 2003
Windows 2000 (Service Pack 2 or higher)
Windows XP Professional
|
Note: Windows 98 and Windows NT are no longer supported. See OracleMetalinknotes 166748.1 and 166751.1 for more information. |
Oracle9i
Oracle9irelease 2 (9.2.0.1.0) or later
Complete the following preinstallation tasks before installing the patch set:
New Oracle C++ Call Interface Libraries Available for Windows
Preinstallation Considerations for Oracle Real Application Clusters
Review the information in the following sections. If any of the issues apply to your Oracle installation, follow the instructions before installing the patch set.
If you are an Oracle E-Business Suite customer and you want to upgrade your Oracle E-Business Suite release 11idatabase server to this patch set, then you must check the latest certification status and Interoperability Notes available on the OracleMetalinkWeb site at:
All other customers wanting to upgrade their databases directly to this patch set should readUpgrading Directly to a 9.2.0 Patch Setavailable in document 214887.1 on the OracleMetaLinkWeb site.
For information about applying a patch set to a current release of Oracle9irelease 2 for a configuration that includes one or more physical standby databases, refer to notes available in OracleMetaLinkdocument 187242.1.
Anyone desiring to use the OLAP option must have the Enterprise Edition of 9.2.0.1.0 with the OLAP option installed as their original base release, prior to installing any of the 9ipatch sets, up to and including 9.2.0.8.0. Oracle highly recommends the Data Warehouse configuration type to optimize the database for OLAP.
If you are moving your Oracle database from a 32-bit operating system to a 64-bit operating system, either prior to applying the patch set or after applying the patch set, review document 352306.1 on the OracleMetalinkWeb site:
To locate document 352306.1:
Log on to OracleMetalink.
ClickAdvancedat the top of the OracleMetalinkpage.
Enter 352306.1 in theDocument IDfield, then clickSubmit.
If you are using an Oracle9irelease 2 (9.2) preconfigured Standard Edition database, then the database contains the following components that are not supported by the Standard Edition:
Oracle Data Mining
Oracle OLAP Catalog
Oracle OLAP Analytic Workspace
Oracle OLAP API
Thecatpatch.sqlscript. does not run the
patch scripts for these components. It sets the component STATUS toOPTION OFFin the DBA_REGISTRY view. The original versions
of the dictionary objects for the components remain in the database but
thecatpatch.sqlscript. does not apply the
patch to them.
All databases that use any features of Oracle Streams must be upgraded to release 9.2.0.2 or later. Operation between release 9.2.0.1 and release 9.2.0.2 is not supported for databases using Oracle Streams features.
Before you install the patch set software, review OracleMetalinknote 283565.1.
Several known issues relate to the following components of Oracle Data Guard:
Redo Apply (Physical Standby Databases)
Apply (Logical Standby Databases)
Data Guard Broker
Data Guard Broker Failover
Refer to OracleMetalinkdocument 259804.1 for a complete set of release notes applicable to Oracle Data Guard in Oracle9irelease 2.
Before you install the patch set software, review OracleMetalinknote 283565.1.
There are two known issues while upgrading from Oracle8ito Oracle9irelease 2:
Customers running Oracle Applications release 11.5.7 or 11.5.8 with Advanced Queuing configured with multiconsumer queues may encounter corruption problems after upgrading their database from any Oracle8idatabase to 9.2.
|
Note: Refer to OracleMetalinknote 231074.1 for more information. |
Oracle Streams Advanced Queuing (AQ) propagations that were previously
scheduled must be unscheduled before upgrading an Oracle8idatabase. To unschedule AQ propagations, run theDBMS_AQADM.UNSCHEDULE_PROPAGATION PL/SQLprocedure.
|
See Also: PL/SQL Packages and Types Referencefor more information about this procedure |
Oracle Data Mining customers must ensure that the Oracle Data Mining account (ODM) is unlocked before applying the patch set. If the ODM account is locked, the patch installation generates an error and one of the Oracle Data Mining tables will be empty.
Event 10499 was introduced in release 9.2.0.3 to allow customers to revert to the earlier behavior. of NUMBER datatypes that have no explicit setting of their scale value. Any nonzero setting of the event level enables the old behavior.
Before the introduction of this event, server code could return zero for the scale if a NUMBER datatype was created without specifying the scale. Other code paths would return -127. With this event, all code paths return -127, as this is the correct behavior.
applications may rely on the previous (incorrect) behavior. Typically, client applications will test for a scale of -127 to distinguish between NUMBER and FLOAT datatypes. It is not sufficient to test the scale alone to distinguish between these two datatypes. You must test for a scale of -127 and a nonzero precision to identify a FLOAT.
Client applications that rely on the old behavior. can still work as before if the event is set. However, these applications must be corrected before upgrading to the next major release of the Oracle database.
The Oracle9irelease 2 (9.2.0.8) patch set contains XDK release 9.2.0.10.
The Japanese characters display square boxes in Oracle Universal Installer when JRE 1.3.1 is used.
Workaround:
Perform. the following steps:
Install JRE 1.4.2 on your local computer.
Use the following command to run Oracle Universal Installer:
./runInstaller -jreLoc/usr/java/jreBeginning with patch set release 9.2.0.7, INSO software is no longer shipped with Oracle Text. It is replaced with Verity KeyView Export from Verity, Inc. There are a number of differences between the old and the new filters. If you intend to use Oracle Text, review document 296405.1 on the OracleMetalinkWeb site:
To locate document 296405.1:
ClickAdvancedat the top of the OracleMetalinkpage.
Enter 296405.1 in theDocument IDfield, then clickSubmit.
Beginning with the 9.2.0.5 patch set, new Oracle C++ Call Interface (OCCI) libraries for Microsoft C-Runtime debugging and for developing applications with Microsoft Visual C++ 7.0 .NET 2002 are available.Table 1lists the new OCCI libraries and their installed locations.
Table 1 Oracle C++ Call Interface Library Files
| OCCI Library Filename | Installed Location | Description |
|---|---|---|
|
|
|
Applications requiring to link with |
|
|
|
Applications developed in Visual C++ .NET 2002 should use this OCCI library.
The currently shipped OCCI DLL is built with Microsoft Visual C++ 6.0 and cannot
be used from an Microsoft Visual C++ 7.0 .NET 2002 compiled application. This
OCCI DLL links with the nondebug version of Microsoft C-Runtime ( |
|
|
|
Applications requiring to link with |
|
Note: The current Oracle C++ Call Interface library for Microsoft Visual C++ 6.0 is available as in previous releases.
|
LIB and PATH Environment Variables
Set theLIBandPATHenvironment variables for the Visual C++ compiler
version being used. For example, if you are using Microsoft Visual C++ 7.0 .NET
2002, add the following directory to theLIBandPATHvariables:
ORACLE_BASEORACLE_HOMEocilibmsvcvc7
You can set environment variables from the Windows Control Panel or use
theSETcommand.
During database creation using Database Configuration Assistant, you may encounter an ORA-01430 error message. This error message can be ignored. The following is an example error message:
(SDO_ROOT_MBR mdsys.sdo_geometry) *ERROR at line 2: ORA-01430: column being added already exists in table
This issue is tracked with Oracle bug 3955522.
If you plan to install this patch in an Oracle Real Application Clusters environment, read the following section before proceeding:
This patch set enables you to install the included patches on multiple nodes in a cluster if release 9.2.0.1 or higher is already installed on those nodes. Oracle Universal Installer detects whether the system where you are installing the software is part of a cluster environment. If it is, then the Oracle Universal Installer displays the available nodes from the cluster.
Oracle provides clusterware and a cluster file system for Real Application Clusters running on Windows platforms. Patches to these components are provided in a separate patch (Patch 5388107). You must install this patch separately from the 9.2.0.8 patch set.
To locate this patch on OracleMetalink:
ClickPatchesfrom the left-hand column.
Enter the patch number 5388107 in the search field.
ClickSearch.
OracleMetalinkis available at the following URL:
|
Note: It is important that you install the patch set on the same set of nodes, which had the base release installation. Choosing a different set of nodes during the patch set installation than were chosen during the base release installation will cause unwanted results in your Real Application Clusters environment, as some nodes will be upgraded to the new software versions, while others will not. |
This is not a complete software distribution. You must install it in an existing Oracle9iOracle home. To identify Oracle home directories, use Oracle Universal Installer. From the Welcome screen, clickInstalled Products,then clickEnvironmenttab.
If you are installing this patch set on an existing Oracle RAC installation, you must run Oracle Universal Installer from the same node from which you performed the initial installation.
Before installing this patch set in a production environment, review document 189908.1,ALERT: Oracle9i Release 2 (9.2) Support Status and Alerts, available on the OracleMetalinkWeb site at:
To locate this document:
ClickAdvancedat the top of the OracleMetalinkpage.
Enter 189908.1 in theDocument IDfield, then clickSubmit.
This document is created by Oracle Support Services and provides information about the status of issues discovered after this patch set was released. If you are unable to access this site, then contact Oracle Support Services before installing this patch set in a production environment.
Download and extract thep4547809_9208_WINNT.zippatch set installation archive to
a directory that is not the Oracle home directory or under the Oracle home
directory. For example,Oracle_patch.
Shut down any existing Oracle database instances with normal or immediate priority. On Oracle RAC systems, shut down all instances on each node.
Stop all listener and other processes running in the Oracle home directory where you want to install the patch set.
When performing an Oracle RAC installation, shut down all Oracle services except the following services, if present:
Oracle Object Service
OracleClusterVolumeService
OracleCMService9i
Oracle recommends that you create a backup of the Oracle9iinstallation before you install the patch set.
You can install the patch set either interactively or noninteractively. See one of the following sections for information about how to complete the installation:
To install the patch set interactively, see the"Installing the Patch Set Interactively"section.
To install the patch set noninteractively, see the"Installing the Patch Set Noninteractively"section.
|
Note: You must use Oracle Universal Installer release 10.1.0.5 or later to install this patch set. |
|
Note: If you attempt to install this patch set in an Oracle home directory that does not contain an Oracle9iinstallation, Oracle Universal Installer displays a warning dialog with the following error:There are no patches that need to be applied from the
patchset Oracle9ipatch set 9.2.0.8.0
The Oracle Universal Installer does not allow the installation to proceed. ClickOK, then clickCancelto end the installation. |
The following procedure describes how to install the patch set interactively:
Log on as a member of the Administrators group to the computer on which to install Oracle components. If you are installing on a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC), log on as a member of the Domain Administrators group.
Start Oracle Universal Installer release 10.1.0.5 located in the unzipped
area of the patch set. For example,Oracle_patchsetup.exe.
On the Welcome screen, clickNext.
On the Specify File Locations screen, clickBrowsenext to thePathfield in theSourcesection.
Select theproducts.xmlfile from the stage
directory where you unpacked the patch set files, then clickNext. For example:
Oracle_patchstageproducts.xml
In theNamefield in theDestinationsection, select the name of the Oracle home that you want to update from the drop down list, then clickNext.
If you are installing the patch set on an Oracle RAC cluster, clickNextwhen the Selected Nodes screen appears.
|
Note: The Selected Nodes screen lists the existing Oracle9iRAC release 2 (9.2) nodes. The first node in the list is the node from where Oracle9iRAC release 2 (9.2) was installed. You must install the patch set software from this node. If this is not the node where you are running Oracle Universal Installer, then exit Oracle Universal Installer and install the patch set software from the first node in the list of nodes. |
On the Summary screen, clickInstall.
This screen lists all of the patches available for installation.
On the End of Installation screen, clickExit, then clickYesto exit Oracle Universal Installer.
The following procedure describes how to install the patch set noninteractively:
Log on as a member of the Administrators group to the computer on which to install Oracle components.
Copy the response file template provided in theresponsedirectory where you unpacked the patch set
archive file.
Edit the values for all fields labeled as
|
Note: For Oracle RAC installations, make sure theCLUSTER_NODESvariable specifies all of the nodes used in
the original Oracle RAC installation. |
Enter a command similar to the following to start Oracle Universal Installer
in noninteractive mode. If Oracle Universal Installer is located inOracle_patchsetup.exe, then pass the full path of the
response file template you have edited locally as the last argument:
C:Oracle_patch> setup.exe -silent -responseFileresponse_file_path
whereOracle_patchis the location of the
patch set you downloaded andresponse_file_pathis the full path of the locally
edited response file.
Review the information in this section before using the upgraded software. This section lists required and optional postinstallation tasks, depending on the installation type and the products that you want to use.
To upgrade Oracle databases from a previous release directly to Oracle9irelease 2 (9.2.0.8) follow the instructions in OracleMetalinknote 214887.1,Upgrading Directly to a 9.2.0 Patch Set.
|
See Also: For more information about upgrading a database, see theOracle9i Database Migrationguide. |
By default, theOracleGSDServiceis
configured to run under theLocalSystemaccount. Manually configureOracleGSDServiceto run under a user account that is a
member of theORA_DBAgroup.
Complete the following tasks after installing the patch set software:
Review the following sections before upgrading a database.
If JServer is part of the installation ensure that there is at least 10 MB of free space allocated to the SYSTEM tablespace.
For Oracle RAC installations, ensure that there is at least 50 MB of free space allocated to the XDB tablespace.
SHARED_POOL_SIZEandJAVA_POOL_SIZEInitialization ParametersUsers who have JVM ( enabled) or
JVM and XDB installed on their 9.2.0.1 databases should make sure that
theinit.oraparametersSHARED_POOL_SIZEandJAVA_POOL_SIZEare each 150 MB or more before running
thecatpatch.sqlupgrade script. Failure to do
so could result in an unrecoverable memory failure while running of the script.
Please note that JVM and DB was shipped
as part of the default 9.2.0.1 seed database, and will be present unless the
user explicitly installed a 9.2.0.1 instance without them.
Set the value of theSHARED_POOL_SIZEand
theJAVA_POOL_SIZEinitialization parameters as
follows:
Use SQL*Plus to login to the database as theSYSuser withSYSDBAprivileges:
C:> sqlplus /NOLOG
SQL> CONNECT SYS/SYS_passwordAS SYSDBA
Start the database:
SQL> STARTUP
If necessary, enter the following command to determine whether the system
uses an initialization parameter file (initsid.ora) or a server
parameter file (spfiledbname.ora):
SQL> SHOW PARAMETER PFILE;
This command displays the name and location of the server parameter file or the initialization parameter file.
Determine the current values of these parameters:
SQL> SHOW PARAMETER SHARED_POOL_SIZE SQL> SHOW PARAMETER JAVA_POOL_SIZE
If the system is using a server parameter file:
If necessary, set the value of theSHARED_POOL_SIZEinitialization parameter to at least 150
MB:
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
If necessary, set the value of theJAVA_POOL_SIZEinitialization parameter to at least 150
MB:
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;If the system uses an initialization parameter file, if necessary change the
values of theSHARED_POOL_SIZEand
theJAVA_POOL_SIZEinitialization parameters to
at least 150 MB in the initialization parameter file (initsid.ora).
Shut down the database:
SQL> SHUTDOWN
After you install the patch set, you must perform. the following steps on every database associated with the upgraded Oracle home:
Log on as a member of the Administrators group to the computer where the Oracle components are installed.
For Oracle RAC installations, start the Global Services Daemon (GSD) on each node of the cluster as follows:
C:> gsdctl start
Start the Oracle Net listener as follows:
C:> lsnrctl start
|
Note: For Oracle RAC installations, start the listener on each node of the cluster. |
For single-instance installations, use SQL*Plus to login to the database as
theSYSuser withSYSDBAprivileges:
C:> sqlplus /NOLOG
SQL> CONNECT SYS/SYS_passwordAS SYSDBA
For Oracle RAC installations:
Start the database as follows, wheredb_nameis the database name:
C:> srvctl start database -ddb_name
Use SQL*Plus to login to the database as theSYSuser withSYSDBAprivileges:
C:> sqlplus /NOLOG
SQL> CONNECT SYS/SYS_passwordAS SYSDBA
Set theCLUSTER_DATABASEinitialization
parameter toFALSE:
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
|
Note: If the system uses an initialization parameter file, change the value of theCLUSTER_DATABASEinitialization parameter toFALSEin the initialization parameter file (initsid.ora). |
Exit SQL*Plus and shut down the database:
SQL> EXIT
C:> srvctl stop database -ddb_name
Use SQL*Plus to login to the database as theSYSuser withSYSDBAprivileges:
C:> sqlplus /NOLOG
SQL> CONNECT SYS/SYS_passwordAS SYSDBAEnter the following SQL*Plus commands:
SQL> STARTUP MIGRATE SQL> SPOOL patch.log SQL> @ORACLE_BASEORACLE_HOMErdbmsadmincatpatch.sql SQL> SPOOL OFF
Review thepatch.logfile for errors and
inspect the list of components that is displayed at the end ofcatpatch.sqlscript.
This list provides the version and status of eachSERVERcomponent in the database.
If necessary, rerun thecatpatch.sqlscript.
after correcting any problems.
Restart the database:
SQL> SHUTDOWN SQL> STARTUP
Run theutlrp.sqlscript. to recompile all
invalid PL/SQL packages now instead of when the packages are accessed for the
first time. This step is optional but recommended.
SQL> @ORACLE_BASEORACLE_HOMErdbmsadminutlrp.sql
For Oracle RAC installations:
Set theCLUSTER_DATABASEinitialization
parameter toTRUE:
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
|
Note: If the system uses an initialization parameter file, change the value of theCLUSTER_DATABASEinitialization parameters toTRUEin the initialization parameter file (initsid.ora). |
Restart the database:
SQL> SHUTDOWN
SQL> EXIT
C:> srvctl start database -ddb_nameIf you are using the Oracle Recovery Manager catalog, enter the following command:
C:> rman catalog username/password@alias RMAN> UPGRADE CATALOG;
If Oracle Internet Directory release 9.2.0 is installed, then complete the steps in the "Upgrading Oracle Internet Directory 9.2.0.x.x" section
|
Note: If you are using the Oracle OLAP option, then you must runcatpatch.sqlandutlrp.sqlon any additional instance created from your
main 9.2.0.8 database. Yourcatpatchlog should
show the status of the three OLAP components as follows:OLAP Analytic Workspace UPGRADED 9.2.0.8.0 Oracle OLAP API UPGRADED 9.2.0.8.0 OLAP Catalog VALID 9.2.0.8.0 |
Complete the following steps only if Oracle Internet Directory version 9.2.0.x.xwas installed in the Oracle home.
|
Note: Make sure that the database and database listener are running, and all parameters for theoidpatchca.batscript. are specified before to running the
script. |
Temporarily set theORACLE_HOMEandORACLE_SIDenvironment variables. For example:
C:> set ORACLE_HOME=D:oracleora92 C:> set ORACLE_SID=sales
Verify that theWINDIRsystem variable is
set. For example:
C:winnt
Verify that thePATHsystem variable
contains the Oracle homebindirectory. For
example:
D:oracleora92bin
Ensure that the database and database listener are running, and
alloidpatchca.batparameters are specified
correctly before you run the script.
ORACLE_BASEORACLE_HOMEbinoidpatchca.bat -connectConnect_String-lsnrportListener_Port-systempwdSYSTEM_Password-odspwdODS_Password-sudnSuper-User_DN-supwdSuper-User_Password-dippwdPassword_to_register_DIP_Server-windir%windir%
In the preceding command,Password_to_register_DIP_Servermust conform. to
the password policy in the Oracle Internet Directory
server.
Starting in 9.2.0.7.0, there is a new script. calledcatbkout.sql. This script. enables the user to restore
the Oracle9iinstallation of the database back to the
original 9.2 patch release (as long as it is 9.2.0.4 or greater) that the user
backed up before applying the patch set. Perform. the following steps for
backing out from the 9.2.0.8 patch release:
Before restoring the Oracle home to the original release, perform. the following steps:
For Oracle RAC installations:
Use SQL*Plus to log in to the database as theSYSuser withSYSDBAprivileges:
C:> sqlplus /nolog
SQL> CONNECT SYS/SYS_passwordAS SYSDBA
Set theCLUSTER_DATABASEinitialization
parameter toFALSE:
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
Exit SQL*Plus and shut down the database:
SQL> EXIT
C:> srvctl stop database -ddb_nameC:> sqlplus /nolog SQL> CONNECT SYS/SYS_password AS SYSDBA SQL> STARTUP MIGRATE SQL> SPOOL catbkout.out SQL> @ORACLE_BASEORACLE_HOMErdbmsadmincatbkout.sql SQL> SPOOL OFF SQL> SHUTDOWN IMMEDIATE
For Single Instance:
C:> sqlplus /nolog SQL> CONNECT SYS/SYS_password AS SYSDBA SQL> SHUTDOWN SQL> STARTUP MIGRATE SQL> SPOOL catbkout.out SQL> @ORACLE_BASEORACLE_HOMErdbmsadmincatbkout.sql SQL> SPOOL OFF SQL> SHUTDOWN IMMEDIATE
Restore the Oracle9iinstallation that you backed up before applying the patch set.
After restoring the original Oracle home, perform. the following steps:
C:> sqlplus /nolog SQL> CONNECT SYS/SYS_password AS SYSDBA SQL> STARTUP MIGRATE SQL> SPOOL catpatch.out SQL> @ORACLE_BASEORACLE_HOMErdbmsadmincatpatch.sql SQL> SPOOL OFF
If Oracle Spatial is installed with the database, perform. the following steps:
SQL> alter session set current_schema = mdsys; SQL> @ORACLE_BASEORACLE_HOMEmdadminprvtmd.plb SQL> @ORACLE_BASEORACLE_HOMEmdadminprvtmd2.plb SQL> @ORACLE_BASEORACLE_HOMEmdadminsdopidx.sql SQL> @ORACLE_BASEORACLE_HOMEmdadminprvtpidx.plb SQL> @ORACLE_BASEORACLE_HOMEmdadminprvtsidx.plb SQL> @ORACLE_BASEORACLE_HOMEmdadminsdogeom.sql SQL> @ORACLE_BASEORACLE_HOMEmdadminprvt3glh.plb SQL> @ORACLE_BASEORACLE_HOMEmdadminprvtgeom.plb SQL> @ORACLE_BASEORACLE_HOMEmdadminprvt3gl.plb SQL> alter session set current_schema = sys;
Shut down the database:
SQL> SHUTDOWN IMMEDIATE
Start the database and recompile the remaining invalid objects:
SQL> STARTUP SQL> @ORACLE_BASEORACLE_HOMErdbmsadminutlrp.sql
Reviewcatbkout.outandcatpatch.outfor errors.
Restart the database:
For Oracle RAC installations:
Set theCLUSTER_DATABASEinitialization
parameter toTRUE:
|
Note: If the system uses an initialization parameter file, change the value of theCLUSTER_DATABASEinitialization parameters toTRUEin the initialization parameter file ( |