注册 登录  
 加关注
查看详情
   显示下一条  |  关闭
温馨提示!由于新浪微博认证机制调整,您的新浪微博帐号绑定已过期,请重新绑定!立即重新绑定新浪微博》  |  关闭

帅小伙的博客

希望能在这里交到更多的朋友

 
 
 

日志

 
 
 
 

linux(AMD64) 从9204到9207升级文档(2)

2006-09-19 13:48:35|  分类: oracle |  标签: |举报 |字号 订阅

  下载LOFTER 我的照片书  |

7 Installation Tasks

You can install the patch set either interactively or noninteractively. See one of the following sections for information about how to complete the installation:

7.1 Installing the Patch Set Interactively


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  patchset Oracle9i patch set 9.2.0.7.0    

The Oracle Universal Installer does not allow the installation to proceed. Click OK, then click Cancel to end the installation.


The following procedure describes how to install the patch set interactively:

  1. Log in as the Oracle software owner (typically oracle).

  2. If you are not installing the software on the local system, enter the following command to direct X applications to display on the local system:

    • Bourne, Bash, or Korn shell:

      $ DISPLAY=local_host:0.0 ; export DISPLAY    
    • C shell:

      % setenv DISPLAY local_host:0.0    

    In this example, 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).

  3. Enter the following command to set the LD_LIBRARY_PATH environment variable:

    • Bourne, Bash, or Korn shell:

      $ LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib; export LD_LIBRARY_PATH    
    • C shell:

      % setenv LD_LIBRARY_PATH $LD_LIBRARY_PATH:$ORACLE_HOME/lib    
  4. For RAC installations, enter the following commands where oracle_home is the Oracle home where you installed Oracle Universal Installer 10.1.0.4:

    $  cd oracle_home/oui/bin  $ ./runInstaller -updateNodeList -noClusterEnabled -local  ORACLE_HOME=$ORACLE_HOME CLUSTER_NODES=node1,node2,node3    
  5. Enter following commands to start the Installer where patchset_directory is the directory where you unzipped the patch set software:

    $ patchset_directory/Disk1  $ ./runInstaller    
  6. On the Welcome screen, click Next.

  7. On the Specify File Locations screen, click Browse next to the Path field in the Source section.

  8. Select the 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    
  9. In the Name field in the Destination section, select the name of the Oracle home that you want to update from the drop down list, then click Next.

  10. If you are installing the patch set on an RAC cluster, click Next when the Selected Nodes screen appears.


    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.

  11. On the Summary screen, click Install.

    This screen lists all of the patches available for installation.

  12. When prompted, run the $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.

  13. On the End of Installation screen, click Exit, then click Yes to exit from the Installer.

7.2 Installing the Patch Set Noninteractively

The following procedure describes how to install the patch set noninteractively:

  1. Log in as the Oracle software owner (typically oracle).

  2. Copy the response file template provided in the response directory where you unpacked the patch set archive file.

  3. Edit the values for all fields labeled as <Value Required> as described by the comments and examples in the template.

  4. To run the Installer, enter a command similar to the following, where response_file is the full path to the response file that you edited:

    $ cd patchset_directory/Disk1  $ ./runInstaller -silent -responseFile response_file    
  5. After the installation, run the $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.

8 Postinstallation Tasks

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.

8.1 Upgrading Databases from Previous Releases Directly to Oracle9i Release 2 (9.2.0.7)

To upgrade Oracle databases from a previous release directly to Oracle9i release 2 (9.2.0.7) follow the instructions in OracleMetalink note 214887.1 Upgrading Directly to a 9.2.0 Patch Set.


See Also:

For more information about upgrading a database, see the Oracle9i Database Migration guide.

8.2 Required Postinstallation Tasks

Complete the following tasks after installing the patch set software:

8.2.1 Check Tablespace Sizes and Set Parameter Values

Review the following sections before upgrading a database.

8.2.1.1 Check SYSTEM Tablespace Size

If JServer is part of the installation ensure that there is at least 10 MB of free space allocated to the SYSTEM tablespace.

8.2.1.2 Check XDB Tablespace Size

For RAC installations, ensure that there is at least 50 MB of free space allocated to the XDB tablespace.

8.2.1.3 Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters

Users who have JVM (Java enabled) or JVM and XDB installed on their 9.2.0.1 databases should make sure that the 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.

Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters as follows:

  1. Start the database:

    SQL> STARTUP    
  2. 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.

  3. Determine the current values of these parameters:

    SQL> SHOW PARAMETER SHARED_POOL_SIZE  SQL> SHOW PARAMETER JAVA_POOL_SIZE    
  4. If the system is using a server parameter file:

    1. If necessary, set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:

      SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;     
    2. If necessary, set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB:

      SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;     
  5. If the system uses an initialization parameter file, if necessary change the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters to at least 150 MB in the initialization parameter file (initsid.ora).

  6. Shut down the database:

    SQL> SHUTDOWN    

8.2.2 Upgrade the Database

After you install the patch set, you must perform the following steps on every database associated with the upgraded Oracle home:

  1. Log in as the Oracle software owner (typically oracle).

  2. For RAC installations, start the Global Services Daemon (GSD) on each node of the cluster as follows:

    $ gsdctl start    
  3. Start the Oracle Net listener as follows:

    $ 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.


  4. For single-instance installations, use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:

    $ sqlplus /nolog  SQL> CONNECT / AS SYSDBA    
  5. For RAC installations:

    1. Start the database as follows, where db_name is the database name:

      $ srvctl start database -d db_name    
    2. Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:

      $ sqlplus /nolog   SQL> CONNECT / AS SYSDBA    
    3. Set the 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 (initsid.ora).

    4. Exit SQL*Plus and shut down the database:

      SQL> EXIT  $ srvctl stop database -d db_name    
    5. Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:

      $ sqlplus /nolog  SQL> CONNECT / AS SYSDBA     
  6. Enter the following SQL*Plus commands:

    SQL> STARTUP MIGRATE  SQL> SPOOL patch.log  SQL> @?/rdbms/admin/catpatch.sql  SQL> SPOOL OFF    
  7. Review the patch.log file for errors and inspect the list of components that is displayed at the end of catpatch.sql script.

    This list provides the version and status of each SERVER component in the database.

  8. If necessary, rerun the catpatch.sql script after correcting any problems.

  9. Restart the database:

    SQL> SHUTDOWN  SQL> STARTUP    
  10. Run the 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    
  11. For RAC installations:

    1. Set the 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 (initsid.ora).

    2. Restart the database:

      SQL> SHUTDOWN  SQL> STARTUP    
  12. If you are using the Oracle Recovery Manager catalog, enter the following command:

    $ rman catalog username/password@alias  RMAN> UPGRADE CATALOG;     
  13. If Oracle Internet Directory release 9.2.0 is installed in the Oracle home, run the following shell script:


    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   -lsnrport Listener_Port   -systempwd SYSTEM_Password   -odspwd ODS_Password   -sudn Super-User_DN   -supwd Super-User_Password   -dippwd Password_to_register_DIP_Server     

    In the preceding example, Password_to_register_DIP_Server must conform to the password policy in the Oracle Internet Directory server.

8.2.3 Download the Latest Version of OPatch

You must install OPatch version 1.0.0.0.53 in order to apply patches on top of 9.2.0.7. Download and unzip patch 2617419.


See Also:

OracleMetaLink Note 224346.1 and Note 189489.1 for more information.

8.3 mod_plsql Postinstallation Steps

Complete the following steps only if mod_plsql is installed. The following steps should be repeated with all the database instances associated with this 9.2.0.7 Oracle home.

  1. Run owa_patch.sql to update owa packages from mod_plsql patch directory:

    • Change to the $ORACLE_HOME/Apache/modplsql/patch directory. For example,

      $ cd $ORACLE_HOME/Apache/modplsql/patch  
    • Connect to the database instance as sysdba:

      $ sqlplus " / as sysdba"  SQL> @@owa_patch.sql  

      Check owa_patch_sid.log file for any errors.

  2. Run the 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    

9 Removing the Patch Set Software

Starting in 9.2.0.7.0, there is a new script called 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:

  1. Before restoring the Oracle home to the original release, perform the following steps:

    $ sqlplus /nolog  SQL> connect / AS SYSDBA  SQL> SHUTDOWN  SQL> STARTUP MIGRATE  SQL> SPOOL catbkout.out  SQL> @?/rdbms/admin/catbkout.sql  SQL> SHUTDOWN IMMEDIATE    
  2. Restore the Oracle9i installation and Central Inventory (see /etc/oraInst.loc) that you backed up before applying the patch set

  3. After restoring the original Oracle home, perform the following steps:

    $ sqlplus /nolog  SQL> connect / AS SYSDBA  SQL> STARTUP MIGRATE  SQL> SPOOL catpatch.out  SQL> @?/rdbms/admin/catpatch.sql    
  4. If Oracle Spatial is installed with the database, perform the following steps:

    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;    
  5. Shut down the database:

    SQL> SHUTDOWN IMMEDIATE    
  6. Start the database and recompile the remaining invalid objects:

    SQL> STARTUP  SQL> @?/rdbms/admin/utlrp.sql    
  7. Review catbkout.out and catpatch.out for errors

10 Reinstalling the Patch Set Software

If necessary, you can reinstall a patch set that has been applied to an Oracle9i installation. You must reinstall the patch set interactively.

To reinstall the patch set:

  1. Log in as the Oracle software owner (typically oracle).

  2. If you are not installing the software on the local system, enter the following command to direct X applications to display on the local system:

    • Bourne, Bash, or Korn shell:

      $ DISPLAY=local_host:0.0 ; export DISPLAY    
    • C shell:

      % setenv DISPLAY local_host:0.0    

    In this example, 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).

  3. Enter the following commands to start the Oracle Universal Installer, where patchset_directory is the directory where you unzipped the patch set software:

    $ cd patchset_directory/Disk1  $ ./runInstaller    
  4. If you are installing the patch on an RAC cluster, click Next on the Selected Nodes screen.

  5. On the Specify File Locations screen, click Browse next to the Path field in the Source section.

  6. Select the products.xml file from the stage directory where you unpacked the patch set files. For example:

    patchset_directory/Disk1/stage/products.xml    
  7. Select the Oracle home that you want to upgrade in the Name field in the Destination section, then click Next.


    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.

    The Available Product Component screen appears. This screen contains a list of all components that have been patched by the original patch set installation. These components are grayed out, indicating they cannot be selected for installation.

  8. Expand the nodes for each component listed in the tree to display the patch that corresponds to each component.

  9. Select the patches that you want to install.

    When you select a patch, the Install Status column changes to Reinstall.

  10. Repeat the process for each patch bundled in the patch set, then click Next.

  11. On the Summary screen, verify the list of patches to be reinstalled, then click Install.

  12. On the End of Installation screen, click Exit, then click Yes to exit from the Installer.

11 Known Issues

Review the following known issues after you apply the patch set.The following known issues apply to this patch set release:

11.1 Running XDK Demonstrations

Before running the XDK demonstrations, make sure that the patch for bug 3821678 is installed.

11.2 Procedural Gateway for APPC or Transparent Gateway for IBM DRDA: Unspecified Error Message

During the installation of Procedural Gateway for APPC or Transparent Gateway for IBM DRDA, you may encounter an error message regarding an unspecified target of the makefile. The error message can be ignored. The following is an example of a message that can be ignored:

Error while invoking target <blank> of makefile  /oracle/9.2.0.7/gateway/lib/gateway.mk    

The following is an example of a valid error message. Notice that the target of the makefile is identified. Messages similar to the following should not be ignored, and you should contact Oracle Support Services.

Error while invoking target install of makefile  /oracle/9.2.0.7/gateway/lib/gateway.mk  

11.3 Oracle Procedural Gateway for APPC Configuration Parameters

If you use Oracle Procedural Gateway for APPC, comment out the following parameters if they are present in the gateway shell script or initsid.ora files:

  • FDS_CLASS

  • FDS_CLASS_VERSION

  • FDS_INSTANCE

11.4 Bug 2602782

Scrollable ResultSet returns 3 times NCHAR character byte size when database Ncharset is UTF8. This problem occurs only with the JDBC Thin driver.

11.5 Bug 3259636

If you use DBCA to create a new database using the seed database option, some of the components will be from an older version. This is because the seed database was created before the patch release.

To update all the components, ensure that you have followed the steps described in the "Upgrade the Database" section .

11.6 Bug 3785754

If you are using Oracle Streams, SQL Apply with a logical standby database, or the LogMiner query tool using the 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.    

This warning indicates that problems were detected in the LogMiner dictionary. See Oracle MetaLink note 283565.1 for information about these problems.

Depending on the application that you are running, do the following:

  • Oracle Streams

    Destroy and re-create captures.

  • Logical Standby

    Reinstantiate the standby database.

If it is not practical to take these actions, contact Oracle Support for alternative instructions to repair the LogMiner dictionary.


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.

11.7 Bug 4270038

When using Database Configuration Assistant in standalone mode to create a database, the following error will occur:

ORA-29807: specified operator does not exist  

Workaround:

Click Ignore.

11.8 Building Pro*C Applications if PostgreSQL is Installed

When building Pro*C applications, you may encounter errors similar to the following in the linking phase:

sample6.o(.text+0x91): In function `main':: undefined reference to `ECPGget_sqlca'    

Workaround:

If the 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  

11.9 Running catpatch.sql during postinstallation steps

When running 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    


 

 

  评论这张
 
阅读(310)| 评论(0)
推荐 转载

历史上的今天

评论

<#--最新日志,群博日志--> <#--推荐日志--> <#--引用记录--> <#--博主推荐--> <#--随机阅读--> <#--首页推荐--> <#--历史上的今天--> <#--被推荐日志--> <#--上一篇,下一篇--> <#-- 热度 --> <#-- 网易新闻广告 --> <#--右边模块结构--> <#--评论模块结构--> <#--引用模块结构--> <#--博主发起的投票-->
 
 
 
 
 
 
 
 
 
 
 
 
 
 

页脚

网易公司版权所有 ©1997-2018