分类: LINUX
2009-03-23 10:48:51
Note: You must use Oracle Universal Installer release 10.1.0.4 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 Oracle9i installation, the Installer displays a warning dialog with the following error: There are no patches that need to be applied from the The Oracle Universal Installer does not allow the installation to proceed. Click OK, then click Cancel to end the installation. |
$ DISPLAY=local_host
:0.0 ; export DISPLAY
% setenv DISPLAYlocal_host
:0.0
local_host
is the host name or IP address of the system that you want to use to display the Installer (your workstation or PC). LD_LIBRARY_PATH
environment variable: $ LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib; export LD_LIBRARY_PATH
% setenv LD_LIBRARY_PATH $LD_LIBRARY_PATH:$ORACLE_HOME/lib
oracle_home
is the Oracle home where you installed Oracle Universal Installer 10.1.0.4: $ cdoracle_home
/oui/bin
$ ./runInstaller -updateNodeList -noClusterEnabled -localORACLE_HOME
=$ORACLE_HOME
CLUSTER_NODES=node1,node2,node3
patchset_directory
is the directory where you unzipped the patch set software: $patchset_directory
/Disk1
$ ./runInstaller
products.xml
file from the stage directory where you unpacked the patch set files, then click Next. For example: patchset_directory/Disk1/stage/products.xml
Note: The Selected Nodes screen lists the existing Oracle9i RAC release 2 (9.2) nodes. The first node in the list is the node from where Oracle9i
RAC 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
the Installer, exit the Installer and install the patch set software
from the first node in the list of nodes. |
$ORACLE_HOME/root.sh
script as the root user. If you are applying the patch set to an RAC installation, then run the root.sh
script on each node of the cluster. response
directory where you unpacked the patch set archive file.
as described by the comments and examples in the template. response_file
is the full path to the response file that you edited: $ cd patchset_directory/Disk1
$ ./runInstaller -silent -responseFileresponse_file
$ORACLE_HOME/root.sh
script as the root user. If you are applying the patch set to an RAC installation, then run the root.sh
script on each node of the cluster.
See Also: For more information about upgrading a database, see the Oracle9i Database Migration guide. |
init.ora
parameters SHARED_POOL_SIZE
and JAVA_POOL_SIZE
are each 150 MB or more before running the catpatch.sql
upgrade script. Failure to do so could result in an unrecoverable
memory failure while running of the script. Please note that JVM and
XML 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. SHARED_POOL_SIZE
and the JAVA_POOL_SIZE
initialization parameters as follows: SQL> STARTUP
init
sid
.ora
) or a server parameter file (spfile
dbname
.ora
): SQL> SHOW PARAMETER PFILE;
SQL> SHOW PARAMETER SHARED_POOL_SIZE
SQL> SHOW PARAMETER JAVA_POOL_SIZE
SHARED_POOL_SIZE
initialization parameter to at least 150 MB: SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
JAVA_POOL_SIZE
initialization parameter to at least 150 MB: SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;
SHARED_POOL_SIZE
and the JAVA_POOL_SIZE
initialization parameters to at least 150 MB in the initialization parameter file (init
sid
.ora
). SQL> SHUTDOWN
oracle
). $ gsdctl start
$ lsnrctl start
Note: For RAC installations, start the listener on each node of the cluster.
If you are using the Oracle OLAP option, make sure that the listener is running. |
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
db_name
is the database name: $ srvctl start database -d db_name
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
CLUSTER_DATABASE
initialization parameter to FALSE: SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
Note: If the system uses an initialization parameter file, change the value of the CLUSTER_DATABASE initialization parameter to FALSE in the initialization parameter file (init sid .ora ). |
SQL> EXIT
$ srvctl stop database -d db_name
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP MIGRATE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catpatch.sql
SQL> SPOOL OFF
patch.log
file for errors and inspect the list of components that is displayed at the end of catpatch.sql
script. catpatch.sql
script after correcting any problems. SQL> SHUTDOWN
SQL> STARTUP
utlrp.sql
script 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> @?/rdbms/admin/utlrp.sql
CLUSTER_DATABASE
initialization parameter to TRUE: SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
Note: If the system uses an initialization parameter file, change the value of the CLUSTER_DATABASE initialization parameters to TRUE in the initialization parameter file (init sid .ora ). |
SQL> SHUTDOWN
SQL> STARTUP
$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;
Note: Make sure that the database and database listener are running, and all parameters for the oidpatchca.sh script are specified before running the script. |
$ORACLE_HOME
/bin/oidpatchca.sh
-connect Connect_String
-lsnrportListener_Port
-systempwdSYSTEM_Password
-odspwdODS_Password
-sudnSuper-User_DN
-supwdSuper-User_Password
-dippwdPassword_to_register_DIP_Server
Password_to_register_DIP_Server
must conform to the password policy in the Oracle Internet Directory server.
See Also: OracleMetaLink Note 224346.1 and Note 189489.1 for more information. |
mod_plsql
is installed. The following steps should be repeated with all the database instances associated with this 9.2.0.7 Oracle home. owa_patch.sql
to update owa
packages from mod_plsql
patch directory: $ORACLE_HOME/Apache/modplsql/patch
directory. For example, $ cd $ORACLE_HOME
/Apache/modplsql/patch
sysdba
: $ sqlplus " / as sysdba"
SQL> @@owa_patch.sql
owa_patch_sid.log
file for any errors. utlrp.sql
script 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> @?/rdbms/admin/utlrp.sql
catbkout.sql
. This script enables the user to restore the Oracle9i
installation 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 9207 patch release: $ sqlplus /nolog
SQL> connect / AS SYSDBA
SQL> SHUTDOWN
SQL> STARTUP MIGRATE
SQL> SPOOL catbkout.out
SQL> @?/rdbms/admin/catbkout.sql
SQL> SHUTDOWN IMMEDIATE
/etc/oraInst.loc
)
that you backed up before applying the patch set $ sqlplus /nolog
SQL> connect / AS SYSDBA
SQL> STARTUP MIGRATE
SQL> SPOOL catpatch.out
SQL> @?/rdbms/admin/catpatch.sql
SQL> alter session set current_schema = mdsys;
SQL> @?/md/admin/prvtsidx.plb
SQL> @?/md/admin/prvt3glh.plb
SQL> @?/md/admin/prvt3gl.plb
SQL> alter session set current_schema = sys;
SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP
SQL> @?/rdbms/admin/utlrp.sql
$ DISPLAY=local_host
:0.0 ; export DISPLAY
% setenv DISPLAYlocal_host
:0.0
local_host
is the host name or IP address of the system that you want to use to display the Installer (your workstation or PC). patchset_directory
is the directory where you unzipped the patch set software: $ cd patchset_directory/Disk1
$ ./runInstaller
products.xml
file from the stage directory where you unpacked the patch set files. For example: patchset_directory/Disk1/stage/products.xml
Note: If you are not sure of the name of the Oracle home, click Installed Products to determine the name of the Oracle home that you want to upgrade. |
Error while invoking targetof makefile
/oracle/9.2.0.7/gateway
/lib/gateway
.mk
Error while invoking target install of makefile
/oracle/9.2.0.7/gateway
/lib/gateway
.mk
init
sid
.ora
files: DICT_FROM_REDO_LOGS
option, you might see a warning similar to the following when you run the catpatch.sql
script: ***WARNING*** At 21-SEP-04 09:52:09 problems related to bug 3785754
were encountered. See Patch or Upgrade Notes.
Call Oracle support.
Note: If
you receive this warning, you must fix the problems in the LogMiner
dictionary before resuming normal operations. If you do not immediately
fix the problems, you may not be able to fix the problems in the
future. |
ORA-29807: specified operator does not exist
sample6.o(.text+0x91): In function `main':: undefined reference to `ECPGget_sqlca'
postgresql-devel
package is installed on the system, add the following directory to the beginning of the SYS_INCLUDE
parameter in the $ORACLE_HOME/precomp/admin/pcscfg.cfg
file before building Pro*C applications: $ORACLE_HOME/precomp/public
catpatch.sql
as part of the postnstallation process, the following error may occur: create type XMLTypePI OID '0000000000000000000000000002014F' as *
ERROR at line 1:
ORA-04021: timeout occurred while waiting to lock object SYS.XMLTYPEPI