Oracle9i Database Server

10.1 Bugs 2033385 and 2181830

Using a database link to connect to a read-only database to select data from a view fails, and returns errors ORA-4052, ORA-604, ORA-372, ORA-1110, and ORA-2063. You cannot use a database link to select data from a view using a cursor loop.

Avoid using the database link to query views using a cursor loop. This problem only occurs with a view. It does not occur when using a SELECT statement directly from the view using a cursor loop to select from a table.

10.2 Bugs 2301915, 2318295 and 2326341

When using the Oracle Streams Wizard, through Oracle Management Server or in standalone mode, to configure replication, the generated scripts are incorrect and may produce errors such as "ORA-26687 Instantiation SCN not set" or "ORA-1403 no data found". Contact Oracle Support Services for an Oracle Enterprise Manager and Oracle Management Server patch that will produce the correct scripts. Use the bug numbers as a patch reference.

10.3 Bug 2602782

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

10.4 Bug 2629196

In 9.2.0.2 patch set while using XML DB, character set conversion does not take place when NLS_LANG is not the same as the database character set. With this patch set, clients must set their NLS_LANG to the database character set, otherwise incorrect data is returned with no error or warning whenever character conversion is required.

10.5 Bug 2659230

Oracle Data Guard Concepts and Administration, Oracle part number A96553-02, only describes how to instantiate a logical standby database for a single-instance primary database. To register a log for multiple threads of an Oracle Real Applications Clusters primary database, use the following query in place of the one that is documented in "Section 4.2.2, Step 8 Identify the latest archived redo log:"

SQL r



  1 SELECT NAME FROM V$ARCHIVED_LOG

  2    WHERE FIRST_CHANGE# <= (SELECT MAX(FIRST_CHANGE#) FROM V$ARCHIVED_LOG

  3  WHERE DICTIONARY_BEGIN = 'YES' AND STANDBY_DEST= 'NO')

  4      AND NEXT_CHANGE#    (SELECT MAX(FIRST_CHANGE#) FROM V$ARCHIVED_LOG

  5  WHERE DICTIONARY_BEGIN = 'YES' AND STANDBY_DEST= 'NO') 

 

NAME

--------------------------------------------------------------------------------

/arch/prim/arch_-1306740637_2_0000000004.log

/arch/prim/arch_-1306740637_1_0000000278.log

tpcc 

 

SQL r



  1  SELECT MAX(FIRST_CHANGE#) FROM V$ARCHIVED_LOG

  2* WHERE DICTIONARY_BEGIN = 'YES' AND STANDBY_DEST= 'NO' 

 

MAX(FIRST_CHANGE#)

------------------

           1378506

The query will return the sequence number that should be specified in "Section 4.2.17, Register the Archived Redo Log and Start SQL Apply Operations."

10.6 Bug 2831333

If you run the Database Configuration Assistant and select the database installation option General Purpose or Transaction Processing in the configuration assistant to install a 9.2.0.4 database after applying the patch set to an Oracle home without a database, then Ultra Search will not function after the installation.

Use one of the following two approaches:

If you run the Database Configuration Assistant and select the database installation option General Purpose or Transaction Processing in the configuration assistant to install a 9.2.0.4 database after applying the patch set to an Oracle home without a database, then Ultra Search will not function after the installation. Oracle Corporation has assigned bug identification number 2831333 to track this problem. To workaround the problem, use either one of the following two approaches:

• Install a preconfigured database optimized for general purpose usage.

  • Install the 9.2.0.1 database using the General Purpose option.

  • Install the 9.2.0.4 patch set using the instructions in this patch set note.

• Build a new database. It will take longer to complete the installation.

  • Install the 9.2.0.1 database using the Software Only option.

  • Install the 9.2.0.4 patch set using the instructions in this patch set note.

  • Launch Database Configuration Assistant.

  • Create the 9.2.0.4 database using the New Database option.

10.7 Bug 3047541

There is a known limitation on Windows 2000 where the size of the CLASSPATH variable can grow too large. If this happens, the shortcuts to the following products may not display:

• Change Manager

• Performance Manager

• SQLPlus Worksheet

• Enterprise Manger Console

Reduce the size of the system CLASSPATH environment variable.

10.8 CORE Version Displays 9.2.0.3 in V$VERSION

The CORE version in V$VERSION displays 9.2.0.3 after successful upgrade of the database. This does not cause any problems and can be ignored.

11.1 Database Upgrade for Oracle E-Business Suite

If you are an Oracle E-Business Suite customer wishing to upgrade your Oracle E-Business Suite release 11i database server to this patch set, then please check for the latest certification status and Interoperability Notes on OracleMetaLink. All other customers wanting to upgrade their databases directly to this patch set should read Migrating Directly to an Oracle9i Release 2 Patch Set Notes available on OracleMetaLink, document 214887.1

dbms_stats.delete_schema_stats('SYS'); 

dbms_stats.gather_schema_stats('SYS'); 

11.2 Standard Edition Upgrade

If you are using an Oracle9i 9.2.0 preconfigured database with Standard Edition, then the database contains several components, such as OLAP Catalog, that are not supported by Standard Edition. The catpatch.sql script will encounter errors when attempting to upgrade these components using Standard Edition. To avoid these errors, do the following:

1. Connect as SYSDBA prior to running the catpatch.sql script.

2. Remove the unsupported components as follows:

   execute dbms_registry.removed(’AMD’);
   
   execute dbms_registry.removed(’APS’);
   
   execute dbms_registry.removed(’XOQ’);
   
   execute dbms_registry.removed(’ODM’);
   
   

The component dictionary objects will still be in the database, but the script will not apply the patch to them.

11.3 Oracle Streams

The following items apply to Oracle Streams:

• All databases that use any features of Oracle Streams must be upgraded to Oracle9i version 9.2.0.2 or later. Operation between version 9.2.0.1 and version 9.2.0.2 is not supported for databases using Streams features.

• The optional capture process of Oracle Streams requires the SHARED_POOL_SIZE initialization parameter be set to a minimum value of 100 MB, and the database be running in ARCHIVELOG mode. The database initialization parameter, TRANSACTION_AUDITING, must be set to its default value. The default value is TRUE.

• The first capture process created on a database builds the Oracle Streams dictionary. If the initial dictionary build is interrupted, then an error indicating that the dictionary is invalid may occur. The typical cause of an interrupted dictionary build is a shutdown abort operation. All other shutdown modes will wait for the dictionary build to complete. If you encounter this error, then drop and re-create the capture process.

• JMS Types and XMLType access to the Oracle Streams queue table is not enabled by default to minimize the impact of bug 2248652 that causes export of the Streams queue table to fail. Users can enable this access by calling the DBMS_AQADM.ENABLE_JMS_TYPES (queue_table) procedure, where the VARCHAR2 parameter queue_table is the name of the queue table. This procedure should be invoked after the call to DBMS_STREAMS_ADM.SET_UP_QUEUE.

  
  

  Note: Databases dependent on the Export utility as their backup strategy should avoid enabling this access.

  
  

• A capture process cannot capture changes made to tables that use function-based or descending indexes. If a capture process tries to capture a change to a table that uses a function-based or descending index, then it writes the LCR that caused the error into its trace file, raises an ORA-00902 error, and becomes disabled.

• Oracle Streams support for CLOB datatypes in multibyte character sets is limited to non-variable size multibyte character sets. If the character set uses a variable-width multibyte encoding scheme, then Streams does not support CLOB datatypes. Refer to the Oracle9i Database Globalization Support Guide for additional information about encoding schemes.

• The TRANSACTION_AUDITING initialization parameter must be set to TRUE for Oracle Streams to function correctly.

• A capture process cannot process logs that include DML update statements using the BUFFER hint. The BUFFER hint disables supplemental logging for the update operation which causes the capture process to stop.

• Currently, Oracle Streams supports Oracle to non-Oracle heterogeneous information sharing only with the following Oracle Transparent Gateways:

  • Transparent Gateway for Sybase (TG4SYBS) release 9.2 and later

  • Transparent Gateway for Microsoft SQL Server (TG4MSQL) release 9.2 and later

  • Transparent Gateway for IBM DB2 (TG4DB2) release 9.2 and later

  • Transparent Gateway for IBM DRDA (TG4DRDA) release 9.2 and later

11.4 Oracle Data Guard

The following issues apply to Oracle Data Guard:

• DBMS_LOGSTDBY Package is Case Sensitive

• Subheaps and Logical Standby Databases

• Skipping GRANT DLL

• LOG_ARCHIVE_DEST_STATE=DEFER Ignored after Failover

• Wait Events

execute dbms_logstdby.skip(’DML’, ’oe’, ’test’, null);

execute dbms_logstdby.skip(’DML’, ’OE’, ’TEST’, null);

SQL> EXECUTE DBMS_LOGSTDBY.APPLY_SET(’MAX_SGA’, 40)

Error 12514 Creating archive log file to '<service_name>'

Timing out on NetServer %d prod=%d,cons=%d,threshold=%d"

11.5 Java VM and XML DB Requirements

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.

11.6 Oracle Text INSO Updates

Oracle Text uses the INSO filter during the indexing of binary documents. This filtering technology is based on Stellent Chicago Corporation's HTML Export technology and is licensed from Stellent Chicago Corporation.

INSO 7.5 is included with this patch set and supports additional platforms and document types. A full list of supported platforms and document types is documented in Note 212584.1 in OracleMetaLink.

11.7 Oracle Advanced Queuing

Customers running Oracle Applications release 11.5.7 or 11.5.8 with Advanced Queuing Configured with multi-consumer queues may encounter corruption problem after upgrading their database to 9.2.0.x from any Oracle8i database.

11.8 Event 10499

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 non-zero setting of the event level will enable the old behavior.

Prior to 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.

Client 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, one needs to test for a scale of -127 and a non-zero precision to identify a FLOAT.

Client applications that rely on the old behavior can still work as before if the event is set but will need to be corrected prior to upgrading to the next major release of the Oracle database.

11.9 Oracle XDK

Oracle9i release 9.2.0.4 patch set contains XDK version 9.2.0.6.

11.10 Oracle Real Application Clusters and Oracle Data Guard During a Network Outage

This section describes Oracle Data Guard configurations running in maximum protection mode with physical standby databases. If you configured Oracle Data Guard to support a primary database in a Oracle Real Application Clusters environment and the primary database is running in maximum protection mode, the network outage between the primary database and all of its physical standby databases will disable the primary database until the network connection is restored. The maximum protection mode dictates that if the last participating physical standby database becomes unavailable, processing halts on the primary database.

If you expect the network to be down for an extended period of time, consider changing the primary database to run in either the maximum availability or the maximum performance mode until network connectivity is restored. If you change the primary database to maximum availability mode, then it is possible for a lag between the primary and standby databases, but you gain the ability to use the primary database until the network problem is resolved.

If you choose to change the primary database to the maximum availability mode, then it is important to use the following procedures to prevent damage to your data.

Perform the following steps if the network goes down, and you want to change the protection mode for the Oracle Real Application Clusters configuration.

1. Shut down the physical standby database.

2. Follow the instructions in Oracle Data Guard Concepts and Administration to change the mode from the maximum protection mode to either maximum availability or maximum performance mode.

3. Open the Oracle Real Application Clusters primary database for general access.

4. Restart the network.

5. Shut down the Oracle Real Application Clusters primary database.

6. Mount the primary database without opening it for general access.

7. Mount the physical standby database.

8. Change mode on the Real Application Clusters primary database from its current maximum availability or maximum performance mode to the maximum protection mode.

9. Open the Oracle Real Application Clusters primary database.

11.11 ALTER TABLE SET COLUMN UNUSED not Supported by Logical Standby Databases

Do not issue the ALTER TABLE SET COLUMN UNUSED statement on a primary database that has logical standby databases. Using the ALTER TABLE statements to set a column unused may fail and return the "ORA-26689: column datatype mismatch in LCR" error. After this error occurs, use the DBMS_LOGSTDBY.INSTANTIATE_TABLE procedure for the table listed in the DBA_LOGSTDBY_EVENTS view, and restart SQL apply operations.

While the DBMS_LOGSTDBY.INSTANTIATE_TABLE procedure will refresh the logical standby database's copy of the table, all subsequent updates to the table will fail. The following is the workaround for this problem:

1. Drop the column on the primary database.

2. Run the DBMS_LOGSTDBY.INSTANTIATE_TABLE PL/SQL procedure to re-create the table on the logical standby database.

3. Restart the SQL apply operations on the logical standby database.

11.12 Creating Nested Tables on Logical Standby Databases

For this release of Oracle Data Guard, logical standby databases do not support creating nested tables. Attempting to create a nested table on the logical standby database will result in the "ORA-02320: failure in creating storage table for nested table column" error.

If the DDL statement causes SQL apply operations to stop on the logical standby database, then provide the transaction ID information (obtained by querying the DBA_LOGSTDBY_EVENTS view) to the DBMS_LOGSTDBY.SKIP_TRANSACTION procedure, and restart SQL apply operations. Although you can create the table on the logical standby database, rows will not be maintained for it.

11.13 DDL Statements that Use Database Links

SQL statements, such as CREATE TABLE tablename AS SELECT * FROM bar@dblink, may fail on logical standby databases. Avoid issuing this type of statement, because there are many errors that can arise from this type of operation.

When the statement is executed on the logical standby database, it will access the database link at that time and it's not possible to know if the information on the logical standby database is the same as it was at the time the statement was executed on the primary database. For example, additional columns may have been added or dropped that would make it impossible to apply the rows that follow. Assuming the network was set up so that the initial creation succeeded, you might see the following error: "ORA-26689: column datatype mismatch in LCR" for a table containing nested table columns. Also, the "ORA-02019: connection description for remote database not found" error may be returned if the database link or the TNS service was undefined on the logical standby database.

When this happens, use the DBMS_LOGSTDBY.INSTANTIATE_TABLE procedure for the table being created, and restart SQL apply operations.

11.14 Logical Standby Databases on the Same Node as the Primary Database

If a logical standby database is located on the same computer system as the primary database, it's likely both Oracle instances will have access to the same directory structure. There are Oracle commands that reuse datafiles. If Oracle commands that reuse datafiles are applied on the primary database, then the commands may also be applied on the logical standby database. If that happens while the primary database is shut down, then it is possible for the logical standby database to claim the file as part of its database and possibly cause damage to the primary database.

For this reason only, Oracle Corporation recommends using the following settings when running the primary and logical standby databases on the same computer system.

EXECUTE DBMS_LOGSTDBY.SKIP('ALTER TABLESPACE'); 

11.15 Granting Privileges to SYS Returns Error ORA-01749

If SQL apply operations fail on a logical standby database and return the "ORA-01749 you may not GRANT/REVOKE privileges to/from yourself" error message, then it is probably caused by an attempt to execute a GRANT DDL statement to grant a privilege or a role to SYS. To verify this is the problem, query the DBA_LOGSTDBY_EVENTS view to see the failed DDL statement along with its transaction ID shown in the XIDUSN, XIDSLT, XIDSQN columns in the view. The following describes how to fix the problem:

1. Execute the DBMS_LOGSTDBY.GUARD_BYPASS_ON PL/SQL procedure.

2. Execute the failed DDL statement.

3. Enter the XIDUSN, XIDSLT, XIDSQN column values as parameters to the DBMS_LOGSTDBY.SKIP_TRANSACTION PL/SQL procedure.

4. Restart SQL apply operations on the logical standby database.

11.16 Refreshing Materialized Views on a Logical Standby Database

Materialized views must be refreshed separately on a logical standby database using the GUARD_BYPASS_ON and GUARD_BYPASS_OFF procedures of the DBMS_LOGSTDBY package. For example:

EXECUTE DBMS_LOGSTDBY.GUARD_BYPASS_ON; 

EXECUTE DBMS_MVIEW.REFRESH ( 'BMVIEW', 'F', '',TRUE,FALSE,0,0,0,FALSE); 

EXECUTE DBMS_LOGSTDBY.GUARD_BYPASS_OFF;

If you are using the DBMS_LOGSTDBY.APPLY_SET procedure but you are not using the default value FULL for the TRANSACTION_CONSISTENCY parameter, then you should stop SQL apply operations before refreshing materialized views on the logical standby database.

11.17 Initially Starting Logical Standby Fails with Error ORA-1652

LogMiner uses temporary tables to stage its internal dictionary as it is mining it out of the redo stream. If the temporary tablespace is not configured adequately, such as it does not have enough space or is not backed up by a temporary file, then the initialization phase of a logical standby database will fail with the following errors:

ORA-1652: unable to extend segment by 512 in tablespace TEMP 

ORA-01332: internal Logminer Dictionary error

To work around the problem, increase the size of the temporary tablespace and start the logical standby database.

11.18 Verify Warning is Incorrect

Occasionally when performing Data Guard broker operations, you may see the following message in the Data Guard configuration log file:

RSM: error in accessing metadata.

You can ignore this message. It is benign and does not indicate any operational problem with the broker or the databases included in the broker configuration.

11.19 Using Multiple Domain Names in CONNECT Command

When connecting to a database using the Data Guard command-line interface (DGMGRL), a connect string that includes multiple domains separated by dots may result in the "invalid username/password; logon denied" message being returned. For example, the following CONNECT command can be problematic:

DGMGRL> CONNECT sys/change_on_install@standby.acme.com

Use one of the following solutions to work around this problem:

• Use double quotation marks, such as the following:

  DGMGRL> CONNECT sys/change_on_install@"standby.acme.com"
  
  

• Use connect strings that do not have multiple domains. This solution might require that you edit the tnsnames.ora file.

11.20 Manually Finding an Archive Group

In Appendix B, Section B.3.2 "Determining Whether an Archive Gap Exists," the text recommends querying the V$ARCHIVE_GAP view to determine whether there is an archive gap.

Instead, you should query the V$ARCHIVED_LOG and V$LOG views, which more accurately reflect if there is a gap on a particular standby destination.

For example, the following query shows there is a difference in the RECD and SENT sequence numbers for the destination specified by DEST_ID=2, indicating that there is a gap:

SQL> SELECT MAX(R.SEQUENCE#) LAST_SEQ_RECD, MAX(L.SEQUENCE#) LAST_SEQ_SENT FROM 

  2> V$ARCHIVED_LOG R, V$LOG L WHERE 

  3> R.DEST_ID=2 AND L.ARCHIVED='YES'; 

 

LAST_SEQ_RECD LAST_SEQ_SENT 

------------- ------------- 

            7            10 

Use the following query to determine the names of the archived redo logs on the local system that must be copied to the standby system that has the gap:

SQL> SELECT NAME FROM V$ARCHIVED_LOG WHERE THREAD#=1 AND DEST_ID=1 AND 

  2> SEQUENCE# BETWEEN 7 AND 10; 

 

NAME 

-------------------------------------------------------------------------------- 

/primary/thread1_dest/arcr_1_7.arc 

/primary/thread1_dest/arcr_1_8.arc 

/primary/thread1_dest/arcr_1_9.arc 

/primary/thread1_dest/arcr_1_10.arc 

11.21 DBMS_LOGSTDBY.INSTANTIATE_TABLE

The DBMS_LOGSTDBY PL/SQL procedure does not support the BLOB data type even though BLOB data types are supported by logical standby databases. Also, the order of the parameters for the INSTANTIATE_TABLE procedure is incorrect in the Oracle Data Guard Concepts and Administration and in the Oracle9i Supplied PL/SQL Packages and Types Reference. The correct parameter order is as follows:

DBMS_LOGSTDBY.INSTANTIATE_TABLE 

     schema_name IN VARCHAR2, 

     table_name  IN VARCHAR2, 

     dblink      IN VARCHAR2);

11.22 New Oracle C++ Call Interface Libraries Available for Windows

In the 9.2.0.4 patch set, new Oracle C++ Call Interface (OCCI) libraries for Microsoft CRT debugging and for developing applications with Microsoft Visual C++ 7.0 (.NET) are available. Table 1 lists the new OCCI libraries and their installed locations.

ORACLE_BASE\ORACLE_HOME\oci\lib\msvc\vc6

ORACLE_BASE\ORACLE_HOME\oci\lib\msvc\vc7

ORACLE_BASE\ORACLE_HOME\oci\lib\msvc\vc7

11.23 SQL Apply Does Not Support Tables with Function-based or Descending Indexes

Logical standby databases do not support tables with function-based or descending indexes in Oracle9i release 2. This information should have been included in Oracle Data Guard Concepts and Administration, Oracle part number A96653-02. There is currently no workaround for this problem.

11.24 Oracle Fail Safe

If you use Oracle Fail Safe, please refer to Doc.Id: 223709.1 available through OracleMetalink. This note has additional, required patch installation and upgrade information for databases running in an Oracle Fail Safe environment. To find this document, log in to OracleMetalink, enter 223709.1 in the search field, and click Search.

11.25 Oracle XML DB

Oracle XML DB users must use version 9.2.0.3 or higher. Earlier versions are no longer supported.

12.1 Advanced Queuing Bugs

The following table lists the Advanced Queuing bugs addressed in this patch set:

12.2 Advanced/Secure Network Bugs

The following table lists the advanced/secure network bugs addressed in this patch set:

12.3 Analytic SQL Bugs

The following table lists the ANSI joins bugs addressed in this patch set:

12.4 ANSI Joins Bugs

The following table lists the ANSI joins bugs addressed in this patch set:

12.5 Application Context Bugs

The following table lists the application context bugs addressed in this patch set:

12.6 Authentication Privileges Auditing Bugs

The following table lists the authentication privileges auditing bugs addressed in this patch set:

12.7 Bitmap Index Bugs

The following table lists the bitmap index bugs addressed in this patch set:

12.8 Change Data Capture Bugs

The following table lists the change data capture bugs addressed in this patch set:

12.9 Compressed Data Storage Bugs

The following table lists the compressed data storage bugs addressed in this patch set:

12.10 Compressed Key Index Bugs

The following table lists the compressed key index bugs addressed in this patch set:

12.11 Connection Manager Bugs

The following table lists the Connection Manager bugs addressed in this patch set:

12.12 Constraint Related Bugs

The following table lists the constraint related bugs addressed in this patch set:

12.13 Corruption Bugs

This section describes the corruption bugs addressed in this patch set. It includes the following categories:

• General Corruption

• Bad Backup

• Corruption Dictionary

• Index Corruption

• Logical Corruption

• Physical Corruption

• Memory Corruption

12.14 Database Link Bugs

The following table lists the database link bugs addressed in this patch set:

12.15 Datatypes Bugs

The following describes the datatypes bugs addressed in this patch set:

• Any Data Bugs

• LOB Bugs

• Objects Bugs

• Special Datatype Bugs

• Timestamp Bugs

12.16 DBLINK Bugs

The following table lists the DBLINK bugs addressed in this patch set:

12.17 Deadlock Bugs

The following table lists the deadlock bugs addressed in this patch set:

12.18 Distributed Network Authentication Bugs

The following table lists the distributed network authentication bugs addressed in this patch set:

12.19 Distributed Oracle Names Bugs

The following table lists the distributed Oracle names bugs addressed in this patch set:

12.20 Domain Index Bugs

The following table lists the domain index bugs addressed in this patch set:

12.21 Error Occurs Bugs

The following table lists the error occurs bugs addressed in this patch set:

12.22 Excessive CPU Usage Bugs

The following table lists the excessive CPU usage bugs addressed in this patch set:

12.23 Export/Import Bugs

The following table lists the export/import bugs addressed in this patch set:

12.24 External Tables Bugs

The following table lists the external tables bugs addressed in this patch set:

12.25 Function-based Index Bugs

The following table lists the function-based index bugs addressed in this patch set:

12.26 Gateways/Heterogeneous Services Bugs

The following table lists the gateways/heterogeneous services bugs addressed in this patch set:

12.27 Globalization Bugs

The following table lists the globalization, formerly known as national language support, bugs addressed in this patch set:

12.28 Hash Join Bugs

The following table lists the hash join bugs addressed in this patch set:

12.29 Index Only Tables Bugs

The following table lists the index only tables bugs addressed in this patch set:

12.30 Instance May Crash Bugs

The following table lists the system halt process spin bugs addressed in this patch set:

12.31 Instance Startup Bugs

The following table lists the instance startup bugs addressed in this patch set:

12.32 Intelligent Agent Bugs

The following table lists the Intelligent Agent bugs addressed in this patch set:

12.33 Interoperability Bugs

The following table lists the interoperability bugs addressed in this patch set:

12.34 Java Bugs

The following table lists the Java bugs addressed in this patch set:

12.35 JDBC Bugs

The following table lists the JDBC bugs addressed in this patch set:

12.36 Job Queue Bugs

The following table lists the job queue bugs addressed in this patch set:

12.37 Large File Bugs

The following table lists the large file bugs addressed in this patch set:

12.38 LDAP/Oracle Internet Directory Bugs

The following table lists the LDAP/Oracle Internet Directory bugs addressed in this patch set: