Oracle 8i Data Server Patch Set
for Sun Sparc Solaris (32 bit database)

Patch Set Notes

This note accompanies the 8.1.7.4.0 patch set for the Oracle Database Server. It includes patches for the RDBMS, PL/SQL, Precompiler, Networking, interMedia Text, JDBC, JavaVM, Enterprise Java Beans, Corba and Java Server Pages products. This is not a complete software distribution and you must install it over an existing 8.1.7 Oracle Server installation.

This patch set has been regression tested by Oracle.  However, it is advisable to check the Oracle Metalink website for related information (such as problems discovered after delivery) prior to installing this patch set in a production environment.  Customers unable to utilize this Web site should contact Oracle Support.

Post Release Issues Issues that are discovered after release of this patch set are documented on the Oracle Metalink website. Customers should check here for the latest status prior to installing this patch set in a production environment.  To see the latest Status and Alerts for this patch set, please read Doc.Id: 120607.1 available through Metalink.To find this document on Metalink, simply type 120607.1 in the search field and click on the 'Search' Button after logging in. Customers unable to utilize this Web site should contact Oracle Support.

Patch Sets on 32-bit and 64-bit Operating Systems (HP, IBM AIX and Sun SPARC).

For certain platforms Oracle provides both 32-bit and 64-bit versions of its Database Software. The 32-bit version of the Database can be run on the 32-bit or 64-bit versions of the Operating Systems as per certification. The 64-bit version of the Database can only be run on the 64-bit version of the Operating System. The 32-bit version of a Patch Set MUST ONLY be installed on the 32-bit version of the Database (regardless of whether the Operating System is 32-bit or 64-bit). The 64-bit Patch Set MUST ONLY be installed on the 64bit version of the Database (which will be running on the 64-bit Operating System).

Document History

Patch Set README Contents

This patch set note contains the following information:

• System Requirements
• Patch Set Components
• How to Install This Patch Set
• Known Restrictions
• Bugs Addressed in this Patch Set
• Error Message Files
• Patch Set Note File
• Oracle Corporation Patch Set Overview

System Requirements

Patch Set components

How to Install This Patch Set

As with any maintenance operation, Oracle Corporation recommends that you back up your Oracle software before making any changes to it.

Important Notes

• Database Migration
  • If you are an Oracle Applications customer wishing to upgrade your Oracle Applications Release 11i Database Server directly from Oracle 8i Enterprise Edition Release 8.1.6 to this patch set, please read the Interoperability Notes available on Metalink under Document 148903.1
  • All other customers wanting to upgrade their Oracle 8i Enterprise Edition Release 8.1.6 databases directly to this patch set should read the 'Migrating Directly to an 8.1.7 Patch Set' Notes available on Metalink under Document 188061.1
  • Any customers wishing to migrate from a database version prior to 8.1.6 must complete the database migration to the 8.1.7 release prior to applying this patch set.  You cannot perform the 8.1.7 migration after this patch set has been installed.
• Oracle Parallel Server Install
  This patchset allows you to install the included patches onto multiple nodes in a cluster when the base release (8.1.7.0.0) is already installed on those nodes. The Oracle Universal Installer will detect whether the machine where you are installing is part of cluster. If it is, you will be prompted to select the nodes from the cluster onto which you would like the patchset installed.
  
  
• Customers running iAS-based mod_PLSQL applications (like Oracle Portal), please note that this patchset will reinstall the default OWA packages provided with the database. Hence, you will need to reinstall the OWA packages from the iAS shiphome at the end of the post-install actions. Please refer to bug#1745320 for more details. Another workaround (after install but before running the post-install scripts) is to edit the $ORACLE_HOME/rdbms/admin/catproc.sql file and comment out the "@@owacomm.sql" line which loads OWA packages. By doing this catalog.sql will not reload the database provided default OWA packages; instead the OWA packages already loaded in the database from iAS shiphome will be preserved.

Installing
 

1. Log in to the oracle account and make sure the environment is set to the correct ORACLE_HOME and ORACLE_SID.
2. Uncompress and untar the downloaded patch set file into a new directory.
3. Shut down the existing Oracle Server instance with normal or immediate priority. I.e.: Shutdown all instances (cleanly) if running Parallel Server. Stop all listener, agent and other processes running in or against the ORACLE_HOME to be installed into.
4. Start the installer:
• If the Installer was installed during the installation of the base 8.1.7.0.0 release, then run the installer from within the $ORACLE_HOME/bin directory.
• If the Installer was not installed during the installation of the base 8.1.7.0.0 release, then run the installer from within the top-level directory on the base 8.1.7.0.0 CD.
5. You may install the Patch Set through either an interactive or a silent installation.
• To perform an interactive installation using the Oracle Universal Installer graphical interface:
1. Start the installer from whichever of the above directories is appropriate on your installation:

          % ./runInstaller

2. Follow the steps given below within the installer:
1. On the Welcome screen, click the Next button. This will display the File Locations screen.
2. Click the Browse button for the Source... entry field and navigate to the stage directory where you unpacked the Patch Set tar file.
3. Select the products.jar file. Click the Next button

The products file will be read and the installer will load the product definitions. The products to be loaded will be displayed.
4. Verify the products listed and then click on the Install button.
5. Once the installation has completed successfully, it will display End of Installation. Click on Exit and confirm to exit the installer.
• To perform a silent installation requiring no user intervention:
1. Copy the response file template provided in the response directory where you unpacked the Patch Set tar file.
2. Edit the values for all fields labeled as "<Value Required>" according to the comments and examples in the template.
3. Start the installer from whichever of the directories described in Step 4 applies to your situation passing as the last argument the full path of the response file template you have edited locally with your own value of ORACLE_HOME and FROM_LOCATION:
 
% ./runInstaller -silent -responseFile <full_path_to_your_response_file>
 
6. If you have previously installed Oracle Label Security then add object files to library. This step is necessary because the installation of this patch set removes Oracle Label Security object files from RDBMS library.

   Link in ols .o files using the following steps:
   cd $ORACLE_HOME/lbac/lib
   make -f lbac.mk xkzl
   make -f lbac.mk ilbac
   cd $ORACLE_HOME/rdbms/lib
   make -f ins_rdbms.mk ioracle

7. Disabling system triggers.
   Before performing the next step, you must first set _SYSTEM_TRIG_ENABLED = FALSE in the initialization parameter file. To do this add the following line to your init<sid>.ora file and restart the database (see Note 149948.1 in Metalink for more information on this issue).
   _system_trig_enabled=false
   
   
8. Invoke SQL*Plus (sqlplus), connect as internal and run the following:
   select * from duc$ where PACK='JIS$INTERCEPTOR$' ;
   If no rows were returned go to the next step. If a row was returned delete it using the following:
   delete from duc$ where PACK='JIS$INTERCEPTOR$' ;
   commit;
   
   
9. Invoke SQL*Plus (sqlplus), connect as internal and run the following SQL scripts with event 10520 set. NOTE: This event is not intended for regular database operation and when turned on below by the 'ALTER SESSION' command will automatically be turned off by the subsequent 'CONNECT' command.
   
   ALTER SESSION SET EVENTS '10520 TRACE NAME CONTEXT FOREVER, LEVEL 10';
   ?/rdbms/admin/catalog.sql
   ?/rdbms/admin/catproc.sql
   ?/rdbms/admin/catrep.sql (This only needs to be run if you are using symmetric/advanced replication. This is not necessary for sites using dblinks and read-only snapshots if symmetric/advanced replication is not installed)
   CONNECT / AS SYSDBA;
   update obj$ set status=5 where type#=29 and owner#!=0;
   commit;
   
   
10. You can ignore this step if you have already executed it as part of a previous 8.1.7 patch set install.
    If Java has previously been loaded into the database, invoke SQL*Plus (sqlplus), connect as internal and run the following SQL DDL command(* Note:If Java has not previously been loaded into the database, skip this step).:
       SQL> create or replace java system
            2    /
    (Note that the / (slash) is important to ensure the execution of the command).
    To ensure the correct installation of the XDK in the database run the following 2 scripts (Bug 2115227):
    $ORACLE_HOME/oracore/admin/initxml.sql
    $ORACLE_HOME/rdbms/admin/catxsu.sql
    

    * To determine whether Java has previously been loaded into the database: invoke SQL*Plus (sqlplus), connect as internal and run the following:    SQL> select count(*) from all_objects where object_type like 'JAVA%'; Java is installed if you get a non zero result returned from the query.

    
    
    
11. You can ignore this step if you have already executed it as part of a previous 8.1.7 patch set install:
    If Java has previously been loaded into the database, invoke SQL*Plus (sqlplus), connect as internal and run the following scripts which are located in $ORACLE_HOME/javavm/install ( Note: If Java has not previously been loaded into the database, you can skip this step):
    load_jis.sql
    jisja.sql
    initjsp.sql
    jspja.sql
    
    Notes:
    When running the $ORACLE_HOME/javavm/install/jisja.sql script the following error may be reported and can be ignored:
    call jis_exit_java_session(0)
    ERROR at line 1:
    ORA-29515: exit called from Java code with status 0
    Bug 1459233 was filed against this problem which is fixed in 9i.
    
    
12. If you deleted a row from duc$ in step 8 then reinsert it again. Invoke SQL*Plus (sqlplus), connect as internal and run the following SQL:
    
    insert into duc$ (OWNER, PACK, PROC, FIELD1, OPERATION#, SEQ) values ('SYS', 'JIS$INTERCEPTOR$', 'USER_DROPPED', 0, 1, 1);
    commit;
    
    
13. Enabling system triggers.
    You must either remove _SYSTEM_TRIG_ENABLED from the initialization parameter file or explicitly set it to TRUE before attempting any other patch set post-install steps. Restart the database.
    
    
14. This step is optional - it will recompile all invalid PL/SQL packages now rather than when accessed for the first time - you can also use utlrcmp.sql to parallelize this. Invoke SQL*Plus (sqlplus), connect as internal and run the following SQL script:
• ?/rdbms/admin/utlrp.sql
  
  
15. Execute the following steps only if you have installed Oracle interMedia Text in the database you are attempting to modify:
• If you have not previously unlocked the ctxsys account and supplied a password for that account, you need to do so. (If you have needed to use Oracle Text in any way prior to applying the patchset, you will have already performed this step, and you can skip this.) Do so by issuing the following statement:

ALTER USER ctxsys IDENTIFIED BY <passwd> ACCOUNT UNLOCK;

1. If you have already installed 8.1.7.2 or 8.1.7.3, go directly to step 7 below.
2. If you have already installed 8.1.7.1, go directly to step 5 below.
3. CONNECT ctxsys/<passwd>;
4. @?/ctx/admin/upgrade/u0801071.sql
5. CONNECT ctxsys/<passwd>;
6. @?/ctx/admin/upgrade/u0801072.sql
7. CONNECT / AS SYSDBA;
8. @?/ctx/admin/upgrade/s0801074.sql
9. CONNECT ctxsys/<passwd>
10. @?/ctx/admin/dr0pkh.sql
11. @?/ctx/admin/dr0plb.sql
12. @?/ctx/admin/dr0type.plb
13. @?/ctx/admin/dr0typec.plb
    
    
16. You can ignore this step if you have already executed it as part of a previous 8.1.7 patch set install:
    The installation of this patch set fixes a potential security hole in the XSQL Servlet - see here for more detail. The patchset installation does not, however, modify any of the Oracle HTTP Server configuration files to reflect changes to the XSQL Servlet installation. If you have previously installed the Oracle HTTP Server, you will need to update one of the configuration files manually after the patchset installation is complete. If you do not do so, the XSQL Servlet may not work in the context of the Oracle HTTP Server after the patchset is installed. To update your Oracle HTTP Server configuration, perform the following steps:
    1) Edit the file: $ORACLE_HOME/Apache/Jserv/conf/jserv.properties
    2) Search for the string: "XSQLConfig.xml File location"
    3) Modify the parameter wrapper.classpath on the line immediately following the above string to read: $ORACLE_HOME/oracore/admin
    4) Save the file.
    
    
17. You can ignore this step if you have already executed it as part of a previous 8.1.7 patch set install:
    The installation of this patch set fixes a potential security hole in the PL/SQL XML parser - see here for more detail. To load the new XML parser in to the database, run the following script as user SYS:
    ? /xdk/plsql/parser/bin/load.sql
    
18. If you are using the RMAN catalog then upgrade it as follows:
    • rman catalog <user/passwd@alias>
    • upgrade catalog;
    • upgrade catalog;
      
      
19. The post install actions are now complete and the database is now ready for use.
    
    

Known Restrictions

• none known at time of release

Bugs Addressed in this Patch Set

Generic Bugs Fixed

* indicates that an alert exists for this bug.
+ indicates a particularly notable bug.

"OERI" is used as a short notation for ORA-600 in this listing.

Bug Fixes by Category

• Corruption
• Recovery
• Advanced / Secure Networking
• Advanced Queuing
• Bitmap Indexes
• Crash - Issues likely to cause an Instance to crash
• DB-Link / Distributed
• Domain Indexes
• Export/Import
• Function Based Index (including DESC indexes)
• Gateways / Heterogeneous Services
• Hangs / Spins
• Hash Join
• Index Only Tables (IOT)
• JDBC
• Java / SQLJ / JSP / Corba etc..
• LDAP / Oracle Internet Directory
• LOB Related (CLOB/BLOB/BFILE)
• Large file / memory issues (Eg: 2Gb)
• LogMiner
• MTS (Multi Threaded Server)
• Memory Corruption
• Migration / Upgrade / Downgrade
• NLS (National Language Support)
• Network
• OCI
• Objects (Types/Collections)
• Optimizer
• Oracle Label Security
• Oracle Names
• PL/SQL (DBMS Packages)
• PL/SQL
• PLSQL External Procedures (EXTPROC)
• Parallel Query (PQO)
• Parallel Server
• Partition Views (PV)
• Partitioned Tables
• Performance
• Pro* Precompiler
• Query Rewrite (including Materialized Views)
• RMAN (Recovery Manager)
• Replication
• Resource Leaks (eg: Memory Leak)
• SQL*Loader
• Security
• Shared Pool
• Space Management - Bitmap Managed
• Space Management
• Special Datatypes
• Star Transformation
• Transportable Tablespaces
• Wallet Manager
• Wrong Results
• XA / Distributed Transactions
• XML / XDK
• Year 2000 / Date limit Issues
• interMedia Text
• Dumps / Abends
• Errors & Internal Errors
• Miscellaneous