Oracle 8i Server Patch Set
for 

Patch Set Notes

This note accompanies the 8.1.7.2.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.

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

Notes:

• In 8.1.7.1 an important performance fix for bug 1410679 was included. As a result of this fix you may encounter a problem which, so far, shows itself as increased or excessive memory usage, or, at worst, a core dump (bug 1818530). These problems can be avoided by rebuilding (precompile, compile and link) your applications. If your precompiler applications are dynamically linked (i.e. linked to libclntsh on Unix platforms) and:
  • you suspect your code is performing "exec sql fetch" statements into scalar rather than array variables, or
  • you see your application consuming a large amount of memory after installing this patch set, or
  • your application unexpectedly starts to core dump after installing this patch set
  then you should re-precompile, compile and link your application.

If you wish to avoid rebuilding your applications, then you will need apply one-off fix for bug 1818530 (check availability in Metalink) - by applying this one-off you will lose the significant performance benefits of the fix for bug 1410679. If subsequent to applying this one-off patch you wish to take advantage of the performance improvements, you will have to back out the patch and rebuild your applications.

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

• 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 upgrade. 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:
   1) cd $ORACLE_HOME/lbac/lib
   2) make -f lbac.mk xkzl
   3) make -f lbac.mk ilbac
   4) cd $ORACLE_HOME/rdbms/lib
   5) 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 SQL scripts with event 10520 set. NOTE: This event is not intended for regular database operation and MUST be turned off as indicated below:
   
   ALTER SESSION SET EVENTS '10520 TRACE NAME CONTEXT FOREVER, LEVEL 10' (turn event on)
   ?/rdbms/admin/catalog.sql
   ?/rdbms/admin/catproc.sql
   ?/rdbms/admin/catrep.sql (only applicable for sites running Oracle Replication)
   ?/rdbms/admin/utlrp.sql (optional - will recompile all PL/SQL packages now rather than when accessed for the first time - can also use utlrcmp.sql).
   ALTER SESSION SET EVENTS '10520 TRACE NAME CONTEXT OFF' (turn event off)
   
   
9. Enabling system triggers.
   After completing the previous step, 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 such as those for Oracle JServer. Restart the database.
10. If you previously installed 8.1.7.1b, then you can skip this step:
    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 determine whether Java has previously been loaded into the database: invoke SQL*Plus (sqlplus), connect as internal and run the following:    SQL> describe dbms_java If the result is:    ERROR:    ORA-04043: object dbms_java does not exist then java has not previously been loaded in the database. If the result is a long package description, then java has previously been loaded in the database.

    
    
    
11. If you previously installed 8.1.7.1b, then you can skip this step:
    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
    
    
12. Users of interMedia Text must run each of the following scripts in SQL*Plus, as CTXSYS, in the following order.
    1. ?/ctx/admin/upgrade/u0801071.sql
    2. ?/ctx/admin/upgrade/u0801072.sql
    3. ?/ctx/admin/dr0pkh.sql
    4. ?/ctx/admin/dr0plb.sql
    5. ?/ctx/admin/dr0type.plb
    6. ?/ctx/admin/dr0typec.plb
       
       
13. If you previously installed 8.1.7.1.0 or 8.1.7.1b, then you can skip this step:
    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/etc/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.
14. 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/parser/plsql/sql/load.sql
    

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

Fixed Bug Descriptions

• interMedia Text

 The default value of the TIMEOUT attribute of the INSO_FILTER
 is 0 (seconds) instead of 120 (seconds).

• JDBC

oracle.jpub.runtime.MutableStruct's contructor does not set sqlTypes

• Migrate
• Performance

This enhancement introduces a parallel version of utlrp.sql
to recompile all packages but to do this in parallel.
The new file is called utlrcmp.sql

• Miscellaneous

ENHANCEMENT:
Admin scripts should use CREATE OR REPLACE instead of DROP / CREATE .

• Corruption

DROP USER CASCADE may drop a different users TRIGGERS.
This requires that the object id of another users table
is the same as the userid to be dropped, and that there is
a trigger on that table.

• interMedia Text

 When using INSO_FILTER on Tru64 UNIX or Red Hat Linux or Intel x86
 platform, the filter output is sometimes incorrect for a few
 specific database character sets.

• interMedia Text
• NLS (National Language Support)
• Wrong Results

WITHIN queries that should be finding documents are returning matching rows.
This affects XML documents containing numeric character entities
such as   or 
 when the database character set is
variable-width such as UTF-8

• Network

9i has the ability to create an Oracle Context at the root of an LDAP directory.
It is not possible to do this in 8.1.6 and 8.1.7.
8.1.6 and 8.1.7 Net8 clients using directory naming will fail to resolve a net
service name in the (LDAP) directory if the Oracle Context is at the root of
the directory, a Root Oracle Context (DN is cn=OracleContext).

• DB-Link / Distributed
• Pro*
• XA

This problem is introduced with the fix for bug:1390597.
When using impicit cursors with release_cursor=yes,
the cursors are not closed when there is an error
(even for errors like no data found). For cursors
accessing remote tables this can cause XA_END to return 100.

• Corruption

Index block corruption can occur.
This is trapped with an ORA-600 [KCOAPL_BLKCHK] if block checking
is enabled, but can lead to an actual corruption if block checking is
not turned on.

• Errors & Internal Errors

This problem is introduced in 8.1.7.1 and onyl shows up on
some platforms (eg: HPUX).
ORA-600 [1114] can occur with more than about 536 sessions.

• interMedia Text

8.1.7.1.B Patchset is missing some interMedia Text files

• interMedia Text

ORA-2291 can occur when creating a relation with ctx_thes package.

• Memory Leaks
• XA

Multi-threaded XA client which spawns threads which do xa_end(TMSUSPEND)
leak memory. This leak occurs in the client and is most noticable
if threads are repeatedly spawned , do work, do TMSUSPEND then exit.

• Optimizer
• Function Based Index (including DESC indexes)

Functional indexes may not get pushed into non-mergable views
when there is an outer join.

• Network

NT: NET initialisation is not thread safe on NT

• Partitioned Tables
• Partition Views (PV)

 ORA-7445 errors in KKECCF are possible from queries or analyze statements using
 partitioned tables or views.

• DB-Link / Distributed
• Memory Corruption
• PL/SQL

RPC between 9i <-> 8i with CHAR data can corrupt memory
if the CHAR data size is over 100 characters in length

• Wrong Results

This problem is introduced in Oracle 8.1.7.1.
Oracle tries to eliminate un-necessary predicates , but this can cause
wrong results when a SQL statement uses BIND variables with the same
name, but the application uses bind by position to set different values
for the identically named bind variables.
eg: col = :b1 or col > :b1  would be converted into ">=:b1"
    but this is wrong if these contain different values.
.
Contact Oracle Support for details of activating this fix.
It is deactivated by default.

• interMedia Text
• Wrong Results

If a document contains one or more terms of the 'ACCUM' query but the section
we are searching against does not contain any term of ACCUM query, the
document receives very high score when it should not be a match. For example
.
<doc>cat<body>dog</body></doc> will receive very high score for
'(cat,horse) within body' even though the doc should not match for this query.

• RMAN (Recovery Manager)

RMAN deletes existing an backup piece after an ORA-27038 (file exists)

• PL/SQL

This is an enhancement. With this fix the package STANDARD is split
across 2 files so that the package body can be reloaded without
the header, minimising invalidations.

• Export/Import
• interMedia Text

Import re-creates context indexes, but the indexes are empty.
This causes contains queries get 'no rows returned'.
Workaround:
  alter index <indexname> rebuild; after the import

• Wrong Results

Wrong results from a query on a table with check constraints
and nullable columns if there are predicates on the columns
and these predicates get into a transitive relation with the
constraint predicates.

• interMedia Text
• LOB Related (CLOB/BLOB/BFILE)
• Performance

This problem is introduced in 8.1.7
Text indexing can be slow when using user datastore with a CLOB or BLOB
parameter.
To fix this problem in 817 you need only the fix for related bug:1748791

• Memory Leaks
• PL/SQL

A memory leak of private shadow memory , or ultimately an ORA-4030,
can occur if a long running PLSQL block repeatedly binds in a loop.

• interMedia Text
• Performance

Indexing a table with many NULL values, with a low index memory, may
taking a long time because the index flushes one document at a time.

• XA

When an XA application calls a stored procedure and the stored
procedure queries a remote database, an ORA-24779 is possible
Workaround:
Do not use stored procedure which accesses remote database from xa
application.

• Pro*
• XA

This problem is introduced in 8170.
XA clients calling xaocommit() (via a TPM call) in a Pro*C program
compiled using MODE=ANSI may dump with a call stack including:
  .. -> xaocommit -> sqlxcac -> sqlcac -> sqlclst

• Java / SQLJ / JSP / Corba etc..
• Advanced / Secure Networking

Multi Threaded Server (MTS) crashes when an SSL Callout spans multiple
sessions.  The stack trace contains calls to nzjsWrite() or nzjsRead().

• Parallel Server

 If timed_statistics or resource_limit parameter  is set to
 TRUE, BSP might encounter a ORA-7445 while shutting down the
 instance.

• Parallel Server

ORA-600 [KJXRRI4] possible in OPS during DLM reconfiguration

• Bitmap Indexes
• Hangs / Spins
• Partitioned Tables
• Parallel Query (PQO)

PDML to bitmap key of a partition table with row movement hangs.
The fix causes the statement to execute serially.
Workaround:
  Run the statement serially.

• JDBC
• Advanced / Secure Networking

Cannot connect using the encryption 'RC4_128', 'RC4_256' in the Thin
JDBC Driver

• Corruption
• Security

ALTER TABLE to modify a table which has Row Level Security
applied to it may put the table into an inconsistent state
as only rows passing the Row Level Security Policy are
touched by the ALTER TABLE command.
Eg: ALTER TABLE to set a column to NOT NULL will only
    check the visible rows, allowing NULL data in the
    NOT NULL column.
    ALTER TABLE to add a column with a supplied DEFAULT
    value will only put the default in the visible rows.

• Replication

ORA-26572 can occur when DEFERRED transactions are pushed

• Security

Oracle Label Security logons fail after upgrading to 8171

• Hangs / Spins
• interMedia Text

DRG-11711 using ctxkbtc to compile a knowledge base
or hang using ctxkbtc with more than 65535 terms.

• JDBC

Segmentation violation in client in
getOracleTypeADT() against 8.0/8i server

• Bitmap Indexes
• Memory Corruption

ORA-600 [KDIBR2R2R BITMAP] / memory corruption possible from
bitmap AND operation.

• Hangs / Spins

When a shadow reports ORA-600 [kcblibr_1], no new buffers are read into
the cache and the instance eventually hangs. With the fix buffer gets are
not suspended.

• Migrate
• PL/SQL

This is an enhancement.
CREATE OR REPLACE <OBJ> currently invalidates all dependent objects
even if the object being replaced has not changed.
With this enhancement Oracle should not INVALIDATE any dependents
if the object being replaced has not changed.

• Optimizer
• interMedia Text

Poor execution plans possible for CONTAINS queries containing
NOT, OR , MINUS or PHRASE text query operators.

• Java / SQLJ / JSP / Corba etc..

JVM upgrades / RMJVM may fail due to bad rollback segment size

• Query Rewrite (including Materialized Views)

ORA-600 [16609] possible on CREATE SUMMARY

• JDBC

When using pre-9i Jdbc-Thin to talk to a 9i (or post-9i)
database, you will see an ORA-600 exception on almost
everything you do. eg: ORA-600 [ttcgcshnd-1 ].

• interMedia Text

Using SEE in a thesaurus file and loading the file with -thes can
result in DRG-11706.

• interMedia Text
• NLS (National Language Support)

CONTAINS queries are slow when NLS_SORT is set to non-binary, even
after creation of a function-based index

• Replication

ORA-600 [KKZFCBSU] possible on refresh of a REFRESH GROUP
especially if there are over 256 snapshots in the group.
Workaround:
  Refresh snapshots individually or don't have more than 256
  snapshots per refresh group.

• Parallel Query (PQO)

ORA-600 [RUAALO:1] possible from PQ on partitioned table/index

• OCI

Multithreaded OCI7 clients may dump (notable Microsofts ODBC driver)

• JDBC
• Memory Leaks

A cursor used for querying object types is left open.
This is a cursor leak, which can result in an ORA-1000 if
called repeatedly.

• Optimizer

Some Star queries are slow when the fix for bug:1490373 is in place

• Pro*

PARSE=partial generates a precomp error, for trigraphs used as directives.

• Network

Dump possible in ncrorou() or ncrodsc()

• Corruption
• LOB Related (CLOB/BLOB/BFILE)
• Replication

A dictionary mismatch can be introduced if a ROWID SNAPSHOT is created
on a table with a LOB column. This can result in an
ORA-600 [KOKLISHDL104] at a later point in time.

• interMedia Text
• Wrong Results

Performing a ctx_doc.filter operation on binary data or text data with
stray 0-bytes may result in parts of the document missing in the
result, or ORA-22282 errors.

• interMedia Text

 Core dump in dreb_likeq or drpnrlex or drpzgsib executing queries
 with multiple wordlist operators (wildcard, fuzzy, stemming, soundex)

• Crash - Issues likely to cause an Instance to crash
• LOB Related (CLOB/BLOB/BFILE)

ALTER SYSTEM KILL session can cause an ORA-600 [1113] on
clean up of a SORT SEGMENT HANDLE if the session is using
TEMPORARY LOBS.
This can cause PMON to ultimately crash bringing down the instance.

• Parallel Query (PQO)

ORA-600[QKAGBY0.4] from PQ SELECT with DEGREE > 1 and GROUP BY
if it contains any duplicate columns or  duplicate aggregate
functions on duplicate columns and if it also has a group by clause.
eg: SELECT c1, c2, SUM(c3), SUM(c4)
      FROM ( SELECT 1 c1, col c2, min(1) c3, min(1) c4 FROM t1
             GROUP BY 1, col
           )
      GROUP BY c1, c2;

• Parallel Query (PQO)
• Wrong Results

 Wrong results are possible from INSERT ... SELECT run in parallel if
 the SELECT uses a sequence.
Workaround:
  Do not use PDML

• Space Management

When creating a table with many FREELIST GROUPS groups in a locally managed
tablespace (with autoallocate) an ORA-600[ktfbbssearch-7]
can occur.
Workaround: Use a smaller number of FREELIST GROUPS

• Index Only Tables (IOT)

Delete triggers on an IOT may signal an ORA-600[delrow:iot2]
error when :NEW.rowid is used in the body of trigger.

• interMedia Text
• Wrong Results

CTXCAT/CATSEARCH may give wrong results when there
is a stopword in a phrase.

• Corruption
• Parallel Query (PQO)

INSERT with /*+ APPEND */ may not blank pad CHAR columns to the
correct length when the driving SELECT is parallelised.
This introduces data corruption in the CHAR column as the actual
data length is incorrect. This can result in subsequent ORA-600
errors.

• Migrate

UTLRP.SQL does not recompile OPERATOR , INDEXTYPE or JAVA CLASS objects.
With this bug fix it does recompile these objects.

• Optimizer

push_join_predicate=TRUE and _push_join_union_view=true
can cause an ORA-600[12325][4]

• DB-Link / Distributed
• NLS (National Language Support)

CTAS between different character set databases might not add
the padding character for CHAR columns if the database character sets
differ and at least one character set is multibyte.

• Export/Import

IMP-17, ORA-2430 possible importing with CONSTRAINTS=N.
Workaround:
  Ignore the errors, they are just due to IMPORT trying to enable
  constraints which have not been imported.

• Pro*

This problem is introduced in 8.1.7.
Pro*C application using dynamic 4 sql and other implicit or
explicit cursors may dump core when the number of cursors exceeds
maxopencursors.

• Parallel Server

ORA-600 [KJRM2C:LEVEL] possible from LCK0

• Wrong Results

If a non-default CPU_PER_CALL is in effect, the CPU time logged by Oracle
may be up to twice the actual CPU time used by the program.
(ie: The value in V$SESSTAT for 'CPU used by this session' may be up to
     twice the correct value).

• interMedia Text
• Performance

DML statements on ctxcat-indexed tables perform a small
amount of unneeded work.

• interMedia Text
• Performance

DML statements on ctxcat-indexed tables may take a long
time to complete due to a poor internal select on dr$index.

• interMedia Text

Oracle core dumps with drne/drnd in the trace stack when you index
an invalid XML/HTML document using html/xml/auto/path sectioner.

• Bitmap Indexes
• Wrong Results

 Query with a Nested loop outer Join may give incorrect results
 when count star push down is done on bitmap index.
 The count gives the count of the inner join, without counting
 the non-matching records.
Eg: Plans containing the form:
     NESTED LOOPS (OUTER)
       TABLE ACCESS (FULL) OF 'EMP'
       BITMAP CONVERSION (COUNT)
         BITMAP INDEX (SINGLE VALUE) OF 'DEPT_B1'

• JDBC

JDBC Thin limits VARCHAR/CHAR binds to 2000 characters rather than 4000

• Hangs / Spins

This problem is introduced in 8.1.5.
Deadlock can occur between library cache and row cache
during concurrent 'alter table disable constraint' and 'truncate table'
commands.

• Security

REVOKE ALL PRIVILEGES from a ROLE fails with ORA-1952.

• Optimizer

 When the initialization parameter 'PARTITION_VIEW_ENABLED'
 is set to 'TRUE' and tables have been analyzed,
 'ORA-979' can occur for queries involving
 literals.

• Errors & Internal Errors

REVOKE REFERENCES may fail with ORA-604 and ORA-1406
 the "owner"."tablename" string for any tables depending on the
 grant being revoked are longer than 30 characters
(including quotes and dot).

• Crash - Issues likely to cause an Instance to crash

DBWR may die with ORA-27062 after one AIOWAIT timeout warning.
The AIO warning implies there is a slow IO problem, but the instance
should remain up for diagnosis of the problem and not crash after
the warning.

• Wrong Results

This problem is introduced in 815.
Wrong results can occur for index range scan when composite indexes
are used. The stopkey is formed wrongly in this case when we
have a composite index with keys such as (c1,c2) and
some predicate such as c1 > v1 and an equality predicate
c2 = v2 present together. The query may return too many rows.
Eg: SELECT B.col_from ,A.col ,B.col_to
      FROM B ,A
     WHERE A.col > B.col_from
       AND B.col_to > A.col
       AND A.id='ZIP';
    when there is a composite index on A(col,id)

• interMedia Text

Context index may fail to index a tagged document that
has a very long attribute value, using the auto section group

• RMAN (Recovery Manager)

This bug covers three scenarios:
 (1) If a database has been migrated from version 7;
 and some datafile blocks have never been re-written
 after the migration; and you make a copy of the datafile
 using the RMAN COPY command; then the copied file
 might not be useable for media recovery.
 (2) If a datafile has a block that is media corrupt;
 and you either take a backup of the datafile
 with the RMAN BACKUP command, or make a copy
 with the RMAN COPY command; then the copied file
 might not be useable for media recovery.
 In both cases, the media recovery may fail
 with ORA-1547 and ORA-1194, even though all redo
 had been applied.
 (3) If a datafile has a block with one of the conditions
 above; and the database is in NOARCHIVELOG mode;
 and you try to make a copy with the RMAN COPY command;
 then the COPY might fail with ORA-19602.
 Workaround:
  If you can identify the blocks that cause the problem,
  then you can try to force the rdbms to re-write those
  blocks in the original datafile (e.g., by updating the
  data, or by allocating those blocks for a new object),
  and then repeating the BACKUP or COPY.

• Errors & Internal Errors

An ORA-1555 may be signalled with graceful switchover / back of STANDBY
against an index block. This is very rare and requires a STANDBY
database to be involved.

• interMedia Text

 Spurious issue of DRG-00100 after DRG-50937 possible for complex
CONTAINS queries

• Corruption

A recoverable corruption of a data buffer in the cache can introduce a
permanent inconsistency between the table and the index.
Eg: An ORA-600 [2032] (in memory buffer corruption) can lead to
    a permanent ORA-600 [12700] error.
Workaround:
  Once encountered, rebuild the index.
  There is no preventative workaround, but this scenario is very rare
   as is requires there to be an in-memory corruption occuring.

• interMedia Text

ORA-942 when running ctx_query.browse_words

• LOB Related (CLOB/BLOB/BFILE)

This problem is introduced in 8.1.7.0.
ORA-600[25012] / ORA-600[4142] possible on TRUNCATE of a table
with a CLOB column.

• Memory Leaks
• MTS (Multi Threaded Server)

MTS dispatcher memory leak

• Gateways / Heterogeneous Services

HS distributed query may dump

• Export/Import

8.0.x export client silently fails to export triggers from an 8.1
database.

• interMedia Text

 Using ctx_doc.markup(..) or ctx_doc.highlight(..) and a
 lexer with composite preference, compound words are not highlighted

• interMedia Text
• NLS (National Language Support)

BROWSE_WORDS is very slow when NLS_SORT parameter is set to
  linguistic sort (non-binary).  Instituting workaround from
  bug 1673505 speeds up descending browse words (BROWSE_BEFORE)
  but not BROWSE_AFTER or BROWSE_AROUND.

• Wrong Results

 A query containing a BETWEEN clause on a constant expression AND a
 subquery expression could may dump or return wrong results.
Workaround:
  Replace BETWEEN with a '>= and <=' predicate

• Memory Leaks
• OCI

Client leak using OCI PUBLISH/SUBSCRIBE notification (OCI_ATTR_SUBSCR_CALLBACK).
Memory is leaked on each event notification received.

• Index Only Tables (IOT)

Update of an IOT with CONCATENATION using a SECONDARY index signals ORA-8102

• Bitmap Indexes
• Wrong Results

sort-merge/hash join involving BITMAP indexes and rowid predicates
can give wrong results.
Workaround: Force the use of nested loops join

• JDBC

This problem occurs when using a connection cache.
If a shadow process is killed in OracleCachedRowSet, future Connections
fail.  This occurs only in the case of JDBC OCI8 driver.  In thin the
connection fails for the subsequent request and afterwards it succeeds.
Workaround:
  Use thin driver.

• OCI

OCI Direct Path API client dumps in OCI_THREADED mode

• PL/SQL

False ORA-6502 possible assigning to PLSQL table record if the
RECORD TYPE is weakly defined and the source data is a cursor
record or a %ROWTYPE.
Workaround: Copy each element of the record seperately

• Pro*

The fix in Bug:1292638 missed out the case of VARCHAR variables.
When using the array fetch with VARCHAR string types, and the string is
null, the return buffer is not set properly as per Oracle8.0/Oracle7 releases. set the length field properly for blank or null

• interMedia Text

InterMedia queries can take a very long time to notice an interrupt
when there are two or more CONTAINS clauses.

• XA

This problem is introduced by the fix for bug 1328999.
Starting multiple global txns in the same process without comitting might
cause false deadlock (ORA-60).

• Java / SQLJ / JSP / Corba etc..
• Advanced / Secure Networking

Exception in oracle.security.o3logon.O3LoginClientHelper

• Advanced / Secure Networking

Listener with SSL PROTOCOL=TCPS dumps unless tracing is enabled

• Advanced Queuing

ORA-24054 occurs trying to propogate between Oracle8i and 9i

• Errors & Internal Errors

Queries containing the TRUNC function and using
star tranformation with temp tables may signal
false ORA-1008, ORA-604 errors.

• Network

Corrupt NET header packet can cause TNSLSNR listener to dump.
See <Note:151260.1> on Metalink

• Dumps / Abends

Dump possible in <Function:koputilassert> recompiling PLSQL
especially if running UTLRP. The current SQL statement in the
dump is typically:
  update "SYS"."KOTTB$" set SYS_NC_ROWINFO$ = :1 where SYS_NC_OID$ = :2

• Advanced / Secure Networking

BCERT cannot handle Certificates from  Microsoft Certificate Authority

• Pro*

This problem is introduced in 8.1.6.3 / 8.1.7.0.
PROCOB can generate incorrect code when sqlcheck=FULL or SEMANTICS.

• Memory Leaks

LIBAGTSH.SO is built including several PLSQL files from libpls8.
These PLSQL files are not compiled as position independent code (PIC)
and hence can cause libagtsh.so not to be properly shared, resulting
in larger than expectedly large swap reservation when using this library.
This mostly affects EXTPROC and other Heterogeneous services on
Unix platforms.

• Corruption
• Index Only Tables (IOT)

Heavy concurrent update / delete of the same row in an IOT leaf can
lead to KEY NOT FOUND errors or an IOT corruption.

• Wrong Results

This problem is introduced in 8.1.7.
Wrong results are possible from queries with multiple OR branches if
the branches contain subqueries.
eg:
     select /*+ ALL_ROWS */ * from sys.dual
     where (dummy is null and not exists (select * from sys.dual))
        or (exists (select * from sys.dual)) ;
Workaround:
   Set _eliminate_common_subexpr = false

• interMedia Text
• Wrong Results

Missing text,  or tag or entities appearing as part of the
text in html_section_group/auto_section_group output.

• DB-Link / Distributed
• MTS (Multi Threaded Server)

ORA-600 [12206] [7] possible when using Shared Database Links

• Corruption

ROLLBACK to user SAVEPOINT followed by an ERROR can cause CORRUPTION.
Eg: This sort of construct will hit this bug:
      SAVEPOINT A;
      insert ... /*DML*/;
      begin
        rollback to A;
        raise no_data_found /*raise error*/
      end;

• Migrate
• RMAN (Recovery Manager)

RMAN users lose the RECOVERY_CATALOG_OWNER role when
you upgrade a database and rman catalog from 8.0 to 8i.

• interMedia Text

ctx_query.count_hits with exact=>true is noticeably slower than
"select count(*) where contains()" for large numbers of hits.

• Function Based Index (including DESC indexes)
• Wrong Results

A query containing a subquery/inline view and involving a self-join
of a table that has a functional index returns no rows.

• RMAN (Recovery Manager)

RMAN cannot open database using a backup controlfile with missing logs.
Workaround:
  Use Server Manager to cancel the recovery session and open resetlogs.

• PL/SQL
• Wrong Results

 Consider a PL/SQL subroutine running on the server which contains a SQL
 statement that contains references to PL/SQL package variables.  If the
 execution of that SQL statement fires a before-statement or before-row
 trigger which causes those PL/SQL variables to be updated before the
 actual execution of the SQL statement, then the SQL statement may see the
 new (post-trigger) versions of the variables.  This is incorrect: the
 values of the variables used in the SQL statement should be those as of
 the time the SQL statement was executed.

• Space Management

Continual segment growth - space remains on PROCESS free lists and
does not get used.

• XA

A Multithreaded XA client leaks memory when DbgFl is set

• PL/SQL (DBMS Packages)
• Performance

With this fix DBMS_SESSION.RESET_PACKAGE only resets the minimum required
to reset package state rather than freeing all package instantiations.
This mainly benefits web based applications.

• interMedia Text

When using the FILE_ACCESS_ROLE interMedia system parameter,
schemas with the file access role get
 "DRG-10758: index owner does not have the privilege to use this preference"
when trying to create an index using a FILE datastore.

• Memory Leaks

This problem is introduced in 8.1.6.
And-Equal access may use up free SGA memory and result in an ORA-4031
error for no apparent reason. There may also be heavy "cache buffer chain"
latch contention.
Note that this fix also includes the fix for <Bug:1577067>

• OCI

ORA-0000 when fetching from a ref cursor during  failover.

• Miscellaneous

CREATE VIEW FORCE may not create view for some errors (eg: ORA-1730)

• interMedia Text
• LOB Related (CLOB/BLOB/BFILE)

Using ctx_doc.gist(..) with a clob for the third parameter instead of
a result table and a null document, will get error message:
ERROR at line 1:
ORA-20000: interMedia Text error:
ORA-21560: argument 3 is null, invalid, or out of range
ORA-6512: at "CTXSYS.DRUE", line 157
ORA-6512: at "CTXSYS.CTX_DOC", line 794
ORA-6512: at line 4

• interMedia Text

Trying to alter a CTXCAT index to add a stopword results
in warnings, with ORA-904: invalid column name errors in
the CTX_USER_INDEX_ERRORS table.

• interMedia Text

Any attempt to rename a CTXCAT index will fail with the
errors DRG-50857 / ORA-942: table or view does not exist

• Network

SQLPLUS reports ORA-0000 after failover after rollback issued

• DB-Link / Distributed
• Security

Database links using OS authentication may fail with ORA-28150

• interMedia Text

DRG-10848 if structured clause of CATSEARCH() has leading blanks (spaces)

• Gateways / Heterogeneous Services

Queries over Heterogeneous Services may dump / ORA-3113

• interMedia Text
• Wrong Results

Wrong results from NL join with CONTAINS() filter on the INNER table

• Recovery

A query against standby database in read-only mode may signal an
ORA-600[kclsfla_1].

• Bitmap Indexes
• Function Based Index (including DESC indexes)

ORA-7445 errors (in kkoapk) are possible from queries which use LIKE
against an expression with a functional bitmap index.
eg: select Count(*) from tab where Func_Temp(Name) like 'XXX%';

• Export/Import

This problem is introduced in 8.1.5.
Import cannot import the data which has been exported to multiple
tapes. The import session errors with IMP-35 / IMP-2 errors.

• Performance

Identical SQL referencing SCHEMA.SEQUENCE.NEXTVAL not shared by different users.
Workaround:
  Create a public synonym with the same name as the sequence pointing
  at SCHEMA.SEQUENCE.

• Errors & Internal Errors

There are various scenarios where an ORA-4020 may be needlessly signalled.
The ORA-4020 graph shows a session waiting S mode for a lock it already
holds S mode.
The library cache locking mechanism has been changed so that it is more
relaxed with regard to multiple lock requests against the same object by
the same process eliminating a number of possible ORA-4020 scenarios.

• Optimizer

Temporary table transformation (STAR_TRANSFORMATION_ENABLED=TRUE) may
coredump in kkosbpp, or show a performance degradation in comparison with
STAR_TRANSFORMATION_ENABLED=temp_disable
Workaround:
  Set STAR_TRANSFORMATION_ENABLED=temp_disable

• Index Only Tables (IOT)

ORA-600 [KCBGTCR_4] can occur when selecting from an IOT via a
secondary index. This is most li

• Corruption

A CTAS statement with CASE expressions can create a "corrupt" table
if the CASE statement returns different length string literals.
The resultant table gets a column definition of CHAR (instead of VARCHAR2)
but the data in the column is varying length VARCHAR2 data.
This mismatch can cause subsequent ORA-600 errors, especially with
parallel query operations.
Workaround:
  Use a TO_CHAR operator around the CASE statement.
  eg: create table test2 as select
       to_char((case when col1='a' then 'a' when col1='b' then 'lots' end)) n
      from test1;

• Advanced Queuing

Dequeue of a message may not use the index resulting in poor performance
of message dequeueing.

• Performance

This problem is introduced in 8.1.5.
The presence of hints in the dba_data_files definition can cause
performance degradation over earlier releases.

• Partitioned Tables
• Wrong Results

A query against partitioned fact table will yield a wrong result
if one of partition keys is semijoin subquery, and another key is
range predicate.

• Errors & Internal Errors

This problem is introduced in 8.1.6.3.
Manipulating an object with complex dependencies may cause an Ora-4020
to be raised where the deadlock graph shows a self-deadlock.

• Query Rewrite (including Materialized Views)
• Security

Query rewrite may signal an ORA-600 [VOPRVL1] when using Row Level Security

• Index Only Tables (IOT)

ORA-600 [KCFRBD_2] / ORA-600 [OERI:KCBGTCR_4] selecting from an IOT via a
secondary index.

• DB-Link / Distributed
• Security

ORA-12534: TNS:operation not supported possible trying to use
REMOTE_OS_AUTHENT=TRUE across a database link for OS authenticated users.
Note: Oracle does not recommend using REMOTE_OS_AUTHENT=TRUE as it
      gives a huge security risk.

• Parallel Query (PQO)

Joins containing set operations can return ORA-600[15574] ORA-600[15803] when
executed as a Parallel Query.
This can occur if the query contains a join between a table and
a set operator (such as UNION ALL) and under that branch we
have 2 joins.

• Memory Leaks
• OCI

This problem is introduced in 8.1.6.2.
An OCI client may leak cursors possibly resulting in an ORA-1000 error.

• interMedia Text
• Wrong Results

The multi_column_datastore truncates varchar2 column values whose
length is equal to the maximum length of the column.
This can result in rows not being found by TEXT queries for the
truncated tokens.

• Pro*

Apps, reports, forms may error with ora-900, ora 1023 or core dump
when using USER EXITS.

• Miscellaneous

ORA-1424 is not generated on  illegal use of escape character.
 when using aggregate functions (like MIN, MAX, AVG). The query gets
 executed without the expected ORA-1424.
Eg: create or replace view test_view as
     select min('000') test_col01 from dual;
    select test_col01 from test_view
     where test_col01 like 'J00\' escape '\';

• interMedia Text

Core dump doing a contains() query utilizing the soundex operator (!)
against text containing cedille (cedilla).

• Errors & Internal Errors

Shutdown may signal an ORA-600[730] for "active checkpoint entry"
items.
Workaround:
  Use <Event:10262> to level 2000 to disable the space leak check
  for small leaks of less than 2000 bytes. See <Note:21235.1>
  for details of this event.

• Crash - Issues likely to cause an Instance to crash

"alter system set log_archive_dest_state_n .." causes an instance crash
when the ARCH process is not running.

• Migrate

Running CATPROC when downgrading from 9.0 to 8.1.7 can produce
the errors:
 ORA-947: not enough values
 ORA-6512: at "SYS.DBMS_RMIN", line 55

• Performance

Performance fix to reduce sleeps on "library cache latch"
in the case where the majority of sleeps are for "kglhdgn: child" and
"kglget: child: KGLDSBRD" (in v$latch_misses).

• Advanced / Secure Networking

KERBEROS authentication may fail with ORA-1004 / ORA-12631 using V5 Kerberos server

• Optimizer

INSERT ... SELECT can cause a coredump during buffer allocation if
STAR_TRANSFORMATION_ENABLED=TRUE and SELECT list column belongs
to a temporary table
Workaround:
 Set STAR_TRANSFORMATION_ENABLED=temp_disable

• Parallel Server

If there are more than 129 rollback segments then the default
value of GC_ROLLBACK_LOCKS does not provide coverage for the
extra rollback segments which can result in extra
'global cache lock open x' waits.
Workaround:
   Set GC_ROLLBACK_LOCKS to "0-<max rollback segment id>=8!REACH"

• PL/SQL

Attempting to execute certain routines in serially reusable (SR) packages
can result in an ORA-600 [PFRI.C:KGI_SRCTX] error if the package
contains or references package variables.

• Hangs / Spins
• MTS (Multi Threaded Server)

MTS dispatcher may hang for 60 seconds during low activity on multi-processor server

• Optimizer
• Hangs / Spins
• Security

_push_join_union_view or star_transformation_enabled=true(temp_disable)
can cause a memory access error or spinning at optimization
if a query has a bind variable and a table with RLS (Row Level Security)
enabled.

• JDBC

Client may hang / spin with statement caching (a featured introduced in 8.1.7)

• JDBC
• Advanced / Secure Networking

OracleSSLCipher is no longer PUBLIC

• Optimizer
• PL/SQL (DBMS Packages)
• Function Based Index (including DESC indexes)

DBMS_STATS.GATHER_SCHEMA_STATS can fail with "ORA-1465 invalid hex number"
if a table has a DESC index on it.
In Oracle8i a DESC index is a functional index.
Workaround:
  Set _ignore_desc_in_index = TRUE and rebuild the indexes.

• Errors & Internal Errors

 Truncating a synonym returns an Ora-4020 "deadlock detected" message
 under 8.1.7 and above, rather than the correct Ora-942 "table or view does
 not exist".

• Advanced / Secure Networking

ORA-12641 Cybersafe Adapter ORANGSS8.DLL is invalid in 817

• interMedia Text
• Performance

Queries involving DOMAIN indexes, especially interMedia Text indexes,
may perform queries slower than expected when a join is involved.
In particular a HASH join over an interMedia index when using the
SCORE function may perform sub-optimally.

• Wrong Results

This problem is introduced in 8.1.7.
Wrong results are possible from ORed non-correlated subquery predicates.
Eg: "select * from tab1
      where (tab1.col1 = 1 and exists (select * from tab2)) or
            (tab1.col1 = 2 and exists (select * from tab3))".
Workaround:
 Set one of the following init.ora parameters:
  "optimizer_features_enable = 8.1.6"
  -or-
  "_eliminate_common_subexpr = false"
 OR ensure the RULE based optimizer is used.

• interMedia Text
• LOB Related (CLOB/BLOB/BFILE)

This is an enhancement.
The fix introduces two new values for the OUTPUT_TYPE of the
USER_DATASTORE object: BLOB_LOC and CLOB_LOC.
When set to either of these values the user datastore procedure
can return a permanent LOB locator rather than populating a
temporary LOB as is required without this enhancement.

• JDBC

When updating a Result Set object using a select statement with a
FOR UPDATE clause an ORA-907 "missing right parenthesis" is generated
by the server.

• Wrong Results

NL having UNION view with pushed predicate as its right input
may return the wrong results.
To encounter this problem the following must be true:
  _push_join_union_view=true
  The UNION view is on the right side of NL
  There is a SORT on the top union view
Workaround:
  Set _push_join_union_view=false (init.ora parameter)

• Function Based Index (including DESC indexes)
• Hangs / Spins

A HANG and then Ora-4020 "deadlock detected" can occur
when a table with functional indexes is dropped.

• Errors & Internal Errors

This problem is introduced in 8163 with the fix for bug:1468034.
ORA-379 possible from UPDATE with AND-EQUAL.
This bug is fixed in 8171 by the fix for <Bug:1640583>

• interMedia Text

CTXLOAD errors with ORA-1403 immediately on Personal Oracle only.

• Crash - Issues likely to cause an Instance to crash

With BACKUP_TAPE_IO_SLAVES set a failure to start an IO slave may cause
a number of ORA-600 errors and possibly an instance CRASH.

• SQL*Loader

This problem is introduced in Oracle 8.1.5.
Direct path load enables a constraint despite invalid data
violating the constraint being present.

• OCI

Multi threaded client with environment variable ORA_OCI_CACHE set
can crash if server does not support caching.

• Performance
• Pro*

This problem is a regression in performance introduced in 8.1 .
In Pro*C a FETCH in a loop issues un-necessary DEFINE calls for each
host variable for every iteration. With this fix DEFINE is only
done on the first iteration.

• Advanced Queuing
• Export/Import

IMP-3 / ORA-24021 when importing non-persistent AQ definitions

• Export/Import

IMP-15 using FROMUSER/TOUSER when table has a CONSTRAINT using an INDEX
if TOUSER does not have privilege on the tablespace used by FROMUSER.
Workaround:
  Pre-create the objects and use IGNORE=Y on import.

• Oracle Names

DUMP_TNSNAMES reports NNC-00408 and produces as 0 byte TNSNAMES.ORA

• Hangs / Spins
• OCI

Multi threaded OCI may hang if one thread has long running query
when running in OBJECT mode.

• Miscellaneous

 If a background process encounters a fatal error,
 such as LGWR or ARCH encountering an I/O error,
 then it may fail to dump enough information
 to diagnose the root cause.
 Workaround: None.  This bug causes no real damage,
 but root cause analysis becomes more difficult or impossible.
 In some cases, examining OS logs for signs of OS-level
 problems may help.

• Replication

ORA-600[729] / ORA-600[kghxhdr1] using DEFERRED TRANSACTION PROPAGATION
with AUDITING enabled

• interMedia Text

ORA-600 [6033] can occur on ALTER INDEX .. REBUILD ONLINE
PARAMETERS ('OPTIMIZE FULL') of an intermedia text index.

• PL/SQL (DBMS Packages)

UTL_TCP is slow
Workaround: Use UTL_HTTP if POST method is not required.

• Function Based Index (including DESC indexes)
• Wrong Results

Dumps can occur, especially in evaopn2, when using DESC functional
indexes.
This fix consolidates a number of other bugs with DESC indexes
into a single fix.

• Advanced / Secure Networking

Dump when using a certificate in which the "Certificate
serial Number" in the extension Authority Key Identifier is negative.

• JDBC
• XA

ORA-600 [18092] possible with JDBC XA when the JDBC program
performs an operation on TX2 from within TX1. (eg: COMMIT TX2
while in TX1)

• Memory Leaks
• OCI

OCIEnvCreate leaks client memory if called repeatedly with OCI_OBJECT

• Errors & Internal Errors

ORA-600 [KCBNFY_BP_ERROR] possible on NUMA platforms with more than one
Processor Group

• Network

This problem is introduced on 8.1.7 on NT.
Setting USE_SHARED_SOCKET option in WINDOWS registry , for an ORACLE_HOME
causes oracle error ORA-12537 when attempting to connect

• Corruption

This problem is introduced in 8.1.6 when DBV is modified
to check UNDO blocks in addition to datablocks (before 816
DBV does not check UNDO blocks). If the UNDO block is Oracle7
format (from a migrated database) then DBV often reports the
block as corrupt when it should not.

• Hangs / Spins

SMON may stop recovering dead transactions causing sessions to hang.
SMON looks like it is waiting on SMON timer as normal but it never
gets to clean up the dead transaction.
Workaround: Shutdown and restart the instance.

• Java / SQLJ / JSP / Corba etc..

NT: NCOMP does not work on NT (ORAJOX8.LIB missing)

• Advanced Queuing

QMN processes may use excessive CPU

• interMedia Text

Incorrect SCORE() for some MULTI-BYTE character data
(eg: Japanese or Chinese)

• interMedia Text
• Wrong Results

A TEXT CATSEARCH() predicate with more than five terms
may error with ORA-600 [20084] errors or produced duplicate rows
in the query result set.

• interMedia Text
• LOB Related (CLOB/BLOB/BFILE)
• NLS (National Language Support)
• OCI
• Wrong Results

OCILobRead may return incorrect data from UTF-8 (multibyte) database.
This can affect interMedia Text text indexing of CLOB data in
a UTF-8 database.

• interMedia Text

Dump in LXSCOP possible using a wordlist operator
(stem, wildcard, fuzzy, soundex)
on two identical subexpressions.

• Index Only Tables (IOT)
• Partitioned Tables

Partition Independence violated for partitioned IOTS

• PL/SQL

Long sql statements in forms user exits may result in an ORA-900 error.
This is a client side fix.

• Hangs / Spins
• interMedia Text

Text queries using MINUS in a CONTAINS clause may hang / spin
in <Function:drysftc>.

• Gateways / Heterogeneous Services
• PL/SQL

 Compiling a package which has a procedure with a parameter whose type is a
 remote object type on a heterogeneously versioned database, where that
 object type has an instance method, fails with PLS-905: object
 USER.REMOTE_TYPE is invalid.  Note that the instance method need not be
 referred to.

• interMedia Text

Text indexing can fail with ORA-7445 errors when using
NEWS_SECTION_GROUP in a multi-byte character set database.

• JDBC
• Memory Leaks

JDBC OCI driver may leak memory

• Optimizer

When the hidden parameter "_like_with_bind_as_equality" is set to TRUE
Oracle treats "col LIKE :bind" as an equality for costing purposes.
With this enhancement Oracle now also treates OPER(col) LIKE OPER(:bind)
as an equality for costing to allow functional indexes to be used
efficiently.
Eg: WHERE upper(col) like upper(:bind)
See <Note:94051.1> for more details of this parameter.

• Hangs / Spins

Users concurrently executing ANALYZE on the same base object may see an
ORA-4020 "deadlock detected" error.

• Optimizer

 High parse times are possible for queries with long OR chains if
 optimizer_features_enable is set to 8.1.6 or higher.
Workaround:
  Set _improved_row_length_enable=false

• Performance

Beginning a tablespace backup can result in the CKPT process using
substantially more CPU time in 8.1 than 8.0

• JDBC

Inserting into an empty Updateable Resultset causes an
SQLException:
java.sql.SQLException: Invalid argument(s) in call: setRowBufferAt

• Optimizer
• interMedia Text

When the interMedia Text index is not analyzed or the first
argument to the CONTAINS() operator is a bind variable then
sometimes the query optimizer can choose a poor execution
plan.

• Errors & Internal Errors

This problem is introduced in 8.1.7
ORA-979 when using cursor_sharing=force with group by and literals.
eg: SELECT ename||'NN' from emp group by ename||'NN' order by ename||'NN';
Workaround: Set cursor_sharing=EXACT;

• Parallel Query (PQO)

The statistics "session pga memory max" and "session uga memory max" are
incorrectly calculated for the QC when commands where executed in parallel.

• Parallel Query (PQO)

Parallel Query may sometime report an ORA-12842

• Crash - Issues likely to cause an Instance to crash

There is a small timing window which can cause the DB to crash
when using the command "ALTER SYSTEM SET JOB_QUEUE_PROCESSES=Nnn"

• Gateways / Heterogeneous Services
• OCI
• Wrong Results

Using Bind by Position can cause incorrect results for queries over
Heterogeneous Services.
Eg: Using OCIBindbyPos or PLSQL EXECUTE IMMEDIATE ... USING with
    identical bind names.

• Corruption
• interMedia Text

 When INSO_FILTER is used and the database character-set is
 other than:
 US7ASCII ;      WE8ISO8859P1 ;  EE8ISO8859P2 ;
 SE8ISO8859P3 ;  NEE8ISO8859P4 ; CL8ISO8859P5 ;
 AR8ISO8859P6 ;  EL8ISO8859P7 ;  IW8ISO8859P8 ;
 WE8ISO8859P9 ;  WE8MACROMAN8 ;  EE8MACCE ;
 EL8MACGREEK ;   CL8MACCYRILLIC; TR8MACTURKISHS ;
 ZHS16CGB231280; ZHT16BIG5 ;     JA16SJIS ;
 EE8MSWIN1250 ;  CL8MSWIN1251 ;  WE8MSWIN1252 ;
 EL8MSWIN1253 ;  TR8MSWIN1254 ;  IW8MSWIN1255 ;
 AR8MSWIN1256 ;  BLT8MSWIN1257 ; KO16KSC5601 ;
 CL8KOI8R ;      JA16EUC ;       TH8TISASCII ;
 UTF8 ;
 then the character data in the created index can be corrupted.

• interMedia Text
• Wrong Results

Deleting/Updating rows when there is TEXT index can result in
an ORA-600 [12700] (for delete) or duplicate rows from queries
(for updates). This problem only occurs on some platforms and
only when the DOCID of the deleted/updated row is greater than
1002000.

• XA

XA_RECOVER may not show a PREPARED transaction

• Corruption
• Oracle8 Datatypes

Dump in <Function:kdiexi> or foreign keys not being found
when using KEY COMPRESSION with Constraints. Foreign Key not
being found can result in logical corruption of the data.

• Export/Import

Export/Import of a NESTED TABLE in a bitmap tablespace errors with:
IMP-00017: following statement failed with ORACLE error 2203:
  "ALTER TABLE ..."
IMP-00003: ORACLE error 2203 encountered
ORA-02203: INITIAL storage options not allowed

• Errors & Internal Errors

star_transformation or push_join_union_view enabled may
cause an ORA-600 [KGLCHK2_1] to be signalled if a query references
a sequence (SEQ.NEXTVAL).

• Wrong Results

SQL_TRACE can incorrectly show very large numbers of rows processed
in the trace file on 64bit platforms.

• Index Only Tables (IOT)

ORA-600 [15201] during insert into IOT (especially with 32K blocksize).
Only workaround is to use a smaller block size (<8K)

• Java / SQLJ / JSP / Corba etc..
• Memory Leaks

In Enterprise Java Beans(EJB) the EJB container starting a transaction
leaks on each call which can causes the garbage collector (GC) to run
and slow performance.

• PL/SQL (DBMS Packages)

DBMS_LDAP package may dump (ORA-3113)

• OCI
• Pro*

This problem is introduced in 8.1.6.
A core dump can occur during fetch in case of a
define done with indp/rcode/rlen set and then
a re-define with indp/rcode/rlen set to NULL.
The dump typically occurs with <Function:ttcfour>
in the stack.

• Memory Leaks

This problem is introduced by the fix for Bug:1189628.
The process which accepts the connection request may leak the
accept handler.

• Errors & Internal Errors

An ORA-600[2865] error can occur during index scan on a temporary
table.

• LOB Related (CLOB/BLOB/BFILE)

ORA-3124 may occur INSERTing a NULL into a CLOB column

• Hangs / Spins

 High parse times are possible for queries with long OR chains if
 query_rewrite_enabled is set to true.

• Corruption
• Partitioned Tables

ALTER TABLE SPLIT PARTITION for composite range-hash partition can corrupt dictionary.
This occurs if (1) Partition is composite and (2) the higher resulting partition
has the same name as the partition being split.
Workaround: Use a different name for the new partitions.

• Bitmap Indexes
• Corruption
• Partitioned Tables

If a partitioned table has LOCAL BITMAP INDEXES and the partition key
is updated such that the row moves to a different partition
then the bitmap index is not updated correctly causing subsequent errors
(eg: ORA-600 [25012]) when accessing table data via the bitmap index.

• JDBC

Fetching objects to a JDBC client gets progressively slower as
more rows are returned from a cursor.

• Java / SQLJ / JSP / Corba etc..

In Java Server Pages(JSP). A stack overflow can occur when an included
file caused an exception.

• DB-Link / Distributed
• Performance

This problem is introduced in 8.1.5.
CTAS over a DBLINK slow if the SELECT list contains a LITERAL
as the remote query block is executed locally.
eg: create table t as
    select 1 one,e.ename,d.dname
      from e@db e, d@db d where e.deptno=d.deptno;
    executes the join locally even though the tables are at
    the same remote location.

• JDBC

A NullPointerException is possible when closing statements after the
connection has been closed, when using statement caching.

• interMedia Text

This is actually a bug which could affect any server-side trusted callout
but is most likely to affect interMedia text index creation where the
indexed column is a LONG or LONG RAW column. The trusted callout can see
incorrect garbage data for piecewise fetches from the trusted callout.

• interMedia Text

CTX_DOC.FILTER on a binary document on a multi-byte character set db,
treating a document as text can dump core.

• Oracle8 Datatypes

Selecting ROWID from a collection in a TABLE() expression
eg: select rowid from table(cast(func1() as NumSet));
    will dump.

• PL/SQL

PL/SQL may ORA-3113/shadow process core dump in kocedd if there is:
    A trigger on 'alter on database';
    An invalid stored library unit in the database; and
    Execution of a procedure that invokes a procedure from the invalid
    library unit.

• Java / SQLJ / JSP / Corba etc..

The "-addclasspath" option of several scripts is broken.

• interMedia Text

ORA-7445 in DREDSEEK can occur on complex Text CONTAINS() queries

• Advanced Queuing

SNP process may deadlock if they concurrently try to clean up aq$_pending_messages

• Oracle8 Datatypes
• Wrong Results

Queries using TABLE(CAST(member_method AS type)) may return wrong results.

• Oracle8 Datatypes
• PL/SQL

 Execution of code containing a SQL statement containing a TABLE()
 expression whose parameter is of a local (non-top-level) collection type
 may return ORA-600 [15435], ORA-6544 [pfrrun.c:pfrbnd1()], ORA-6553.

• Hangs / Spins
• Replication

Contention for SR enqueue possible with replication under heavy load.

• PL/SQL

CONVERT function can raise a false VALUE_ERROR (ORA-6502)

• Advanced Queuing
• Hangs / Spins

A database running AQ propagation may either lock up with a permanently
busy 'channel handle operations parent latch' or else may crash with
ORA-00600 [545] whilst accessing the 'message pool operations parent latch'.

• Errors & Internal Errors

CREATE or REPLACE FORCE VIEW may signal an ORA-600 [16221] if the
view depends on a package which does not yet exist.
Workaround:
 Set _push_join_union_view=FALSE

• Dumps / Abends

Dump in PTG_TX possible

• Pro*

PROCobol: SQLMOV is always called with quotes (") even if LITDELIM=APOST

• Miscellaneous

ORA-64 for very large SESSIONS or TRANSACTIONS init.ora settings

• Corruption
• OCI

Client data corruption can occur using array fetches if ARRAY size
is less than OCI_ATTR_PREFETCH_ROWS.
Workaround:
  Ensure the arraysize matches OCI_ATTR_PREFETCH_ROWS.