Oracle8i
Release 3 (8.1.7.0.0) Fixed Bugs


Copyright (C) Oracle Corporation 1993, 1998, 1999, 2000

Editors: Richard Powell, Paul Lane, Bridget Burke, Venkat Subramanian

This software/documentation contains proprietary information of Oracle Corporation. It is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited.

If this software/documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered with Restricted Rights and the following legend is applicable:

RESTRICTED RIGHTS LEGEND:

Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights in Technical Data and Computer Software (October 1988).

If this software/documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it is delivered with "Restricted Rights," as defined in FAR 52.227-14, Rights in Data - General, including Alternate III (June 1987).

Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

The information in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free.

Oracle is a registered trademark, and Net8, SQL*Plus, Oracle8i, Oracle Enterprise Manager, DBA Studio, Oracle Parallel Server, and PL/SQL are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.

All trade names referenced are the service mark, trademark, or registered trademark of the respective manufacturer.


Category BugNo Description
Corruption 993935* A non-unique reverse key index on a parent table cannot be used to enforce a foreign key constraint on the child table. Similarly, a referential constraint cannot be enforced when a non-unique reverse key index is defined on the foreign key column of a child table. Note: The symptoms of this bug which can cause logical corruption can be seen in duplicate <Bug:1120055>. See <NOTE:100195.1> on Metalink
1120055* If a reverse key index exists on the columns of a foreign key constraint then it is possible to delete parent rows while child rows exist. This can introduce logical corruption in the data. Workaround: Do not use REVERSE KEY indexes on columns making up a foreign key constraint. Note: This is really a duplicate of <Bug:993935>. See <NOTE:100195.1> on Metalink
950623+ This problem was introduced in 8.0.6 and 8.1.6 by the fix for <bug:702389> CREATE OR REPLACE VIEW loses granted permissions on that view. 
1000907+ SMON may crash ORA-600 [ktssdro_segment1] due to SEG$ / UET$ corruption which can be introduced by this bug. There is a small timing window where this dictionary corruption may occur. Support Notes: <Event:10061> may be used to stop SMON temp segment cleanup to look into the problem.
1082335+ If an update on a row forced the undo record to be split into two blocks, the undo record (an array of buffers) could become corrupted if one of the buffers itself had to be split. This corruption is highly unlikely to occur. Symptoms can vary but the problem replays on recovery
1250521+ COMPRESSED KEY INDEXes can become logically corrupt signalling one of a number of errors (eg: ORA-600 [6101], ORA-600 [6121] or similar). This problem can easily occur if using compressed key indexes. . Workaround: Do not use compressed key indexes This cannot occur in 8.0 as this is an 8.1 feature.
690443 With sqlldr, rows get inserted into the table even if an after statement trigger fails and table ends up with wrong rows. This happens if there is also a row level trigger that passes.
887509 Unix file size limit potentially can corrupt oracle blocks if an oracle block crosses the limit boundary. File size limits are usually specfied in units of 512 byte blocks which means that an oracle block can possibly begin below the limit and end above.
925105 If a file is added to the database without specifying the file size, resize operations could fail with internal error [2847] or [kcfnew_1]. The addition can leave a corrupt entry in the dictionary which may require a tablespace rebuild. See <NOTE:107591.1> on Metalink
939510 Direct-path loader sometimes caused corrupted data to be loaded if both the CONTINUEIF continuation clause and the PIECED field option are specified Workaround: Use conventional load.
1035754 Trigger IN-OUT bind variables may evaluate as NULL when all IN references to the variable (i.e. where the value of the bind is read rather than written) are parenthesized. Eg: IF (:new.colval) is null THEN :new.colval:='bad'; END IF; will always set :new.colval to 'bad' as (:new.colval) appears as NULL. This can cause logical data corruption if not noticed. Workaround: Do not put binds in parenthesis. Eg: IF :new.colval is null THEN :new.colval:='bad'; END IF; avoids the problem
1067602 Export of a partitioned table having multiple index constraints can generate incorrect syntax in the export dump file. This can lead to a subsequent failure upon import. Workaround: It is possible to work around this problem by pre-creating the table and associated constraints and use IGNORE=Y
1098422 Float / Double client side bind values may cause invalid Oracle numbers. This may result in ORA-6502 errors from PL/SQL or other symptoms due to corrupt numbers.
1116499 When using XA transaction having multiple branches in a transaction, ORA-600[6856] and data corruption could occur if the branches were simultaneously rolled back.
1143747 Under very specific conditions update of a column covered by a BTREE index may not update a row which should be updated. This is most likely to occur with very full shallow indexes where the update causes the root block to be split.
1146253 Direct load operations (direct load, CTAS, APPEND) may set the wrong space usage on a block if the table being loaded has more than 255 columns but the head pieces end up less than the "stub space" (9 bytes). This can introduce a silent corruption which is only detected later on, (or will crash the load session if block checking is enabled). . This cannot occur in Oracle7 as there cannot be > 255 columns . Analyze of affected objects typically show: "kdbchk: the amount of space used is not equal to block size "
1161906 last_analyzed column in the view *_tables is filled with a corrupt date when only an index is ana The problem occurs because the date field is not set when CREATE INDEX ... COMPUTE STATISTICS is used.
1171627 A direct load into an empty partition which has two or more subpartitions will corrupt the local indexes in all other partitions are truncated. Workaround: a. Insert at least one row into the partition you wish to load into or b. Re create all local indexes after the load
1179002 While processing an insert of a prefix key in a compressed index a data structure is allocated on a local stack. The structure may then be read outside the scope of the local stack. This is incorrect because the data structure may have been released and reused for another purpose before the insert has finished with it. This could cause corruption to COMPRESSED KEY INDEXES. Workaround: Do not compress the index.
1186914 Parallel direct load may set index status to VALID when no rows are loaded, even though a concurrent load job may have made the index invalid by loading rows. This can introduce a mismatch between index and table data. . Workaround: Recreate indexes after a load.
1228658 This problem was introduced in 8.1.6.0 Create INDEX on a snapshot / MVIEW can produce a corrupt index. This may show up as ORA-600 [13004] or an ORA-600 [25012] or ANALYZE TABLE snapshot_name VALIDATE STRUCTURE CASCADE reporting ORA-1499. This can easily occur if the index can be built from an existing index on the snapshot.
1231642 If timed_statistics is set to true, parallel queries and parallel CREATE TABLE AS SELECT could hang. Additionally Parallel CREATE TABLE AS SELECT can produce a corrupt table. Workaround: Disable TIMED_STATISTICS for parallel operations.
1245392 Fast refresh of a materialized view / snapshot may miss some rows when more than 1 snapshot is based on the same master table.
1248170 DML statements against object tables with common subexpressions and triggers (with OUT-binds) defined on the target table may produce incorrect results
1255474 Constraints are not enforced properly while doing an array insert. Duplicate rows may be inserted when enforcing uniqueness using non-unique index. This can cause logical corruption of the data.
1275263 DBVERIFY reports blocks containing all zeroes as a normal empty blocks when they should be considered corrupt unless the datafile has been migrated from Oracle7.
1283521 This problem was introduced in Oracle8.0 Operations on a table in a cluster which has previously been truncated can fail with ORA-8103 due to corrupt dictionary information. In particular DIRECT EXPORT will signal ORA-8103 for a cluster which has had truncate run against it in the past.. See <NOTE:109134.1> on Metalink
1312425 When a global partitioned index is created with the 'reverse', option for a partition table, the index table can be corrupted. Analyze table will show a mismatch with ORA-1499. Query against the table sometimes yields incorrect result.
1322944 While using SQL*Loader in direct mode with the SINGLEROW option, if the load fails then the Index may still be marked as USABLE, but the table and index are inconsistent.
Recovery 1045211 When doing media recovery using a backup controlfile (this includes using a standby database), if you have had added datafiles or tablespaces to the database that caused the controlfile to expand, then recovery can fail with ORA-1118 or ORA-1667, because media recovery does not automatically resize the datafile and/or tablespace areas of the controlfile. Workaround: Use a newer controlfile, or re-create the controlfile for the database being recovered.
1092759 In Oracle8i it is possible for a corruption in the online logs to be reported and then skipped in the archive stream. This can leave a gap in the valid archive log stream which has been skipped rather than manually acknowledged, making it impossible to fully recover the database at a later point in time.
1248580 The values for the init.ora parameters DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT are treated in a case sensitive manner, even on systems with case insensitive file names.
1311431 In standby environments with the primary database archiving to local and remote destinations, if the only local destination runs out of space, the local archiver may signal [kcrrmario.1].
Advanced Queuing 875427 ORA-02083 may occur exporting an AQ queue if there are remote subscribers.
1047150 The QMN process is not very aggressive at cleaning up AQ IOT's
1234770 AQ spins in first message if OCI_ATTR_CORRELATION is specified as a OCI_DTYPE_AQDEQ_OPTIONS attribute.
1288817 Snapshot process performing AQ propogation grows in size
1302846 If the destination database fails during propagation it is possible for propagation to never propagate some messages. The reason for this was because we did not rollback changes on the source correctly.
Bitmap Indexes 941018 UPDATE or DELETE statements with all the predicates resolved through bitmap index access could raise internal error ORA-600[13013] (CANNOT GET STABLE SET) if the predicates involve BITMAP OR/NOT.
953424 ora-1037 can occur with a large number of bitmap indexes and partitions on a table. For this problem to occur then: Number of bitmap indexes * Number of partitions must be GREATER THAN 8000 
956131 ORA-600[15819] can be signalled when rebuilding a bitmap index in parallel for larger block sizes ( > 4k )
967492 ORA-600[12403] can occur for queries using bit map indexes, specifically for BIMAP OR rowsources during Fetching In 8.1 the error ORA-600[20012] may be reported instead in the same scenario.
971769 Export does not export the statistics of bitmapped indexes.
1038883 When a query executes with "BITMAP KEY ITERATION" in the plan with SQL_TRACE or TIMED_STATISTICS enabled , the server process may crash with ORA-7445. BITMAP KEY ITERATION typically occurs when there are BITMAP indexes and STAR_TRANSFORMATION is enabled or hinted.
1051699 This problem was introduced in 8.1.5 Queries of the form: select ... from tab where NOT (c2 = 'x') may fail with ORA-600 [20083] if there is a bitmap index on C1 and a Btree index on C2 and the execution plan includes a BITMAP MINUS of C2s index (btree converted to bitmap) from C1 (bitmap index).
1110876 Parallel query slave accessing bitmap index sometimes dies with internal error ORA-600 [20040].
1131546 Statistics on bitmap index collected with CREATE BITMAP INDEX may be inconsistent with the ones collected with ANALYZE in certain situations.
1138308 Bitmap access path for a complicated where clause query may raise ORA-600 [17116] / coredump. Workaround: Set <Event:10114> to level 1. This can affect performance. See <Note:75713.1> before setting any event.
1195108 This problem was introduced in 8.1.5 Queries that perform count(*) with group by on columns that have a bitmap index may error with ORA-600[9999]
Crash - Issues likely to cause an Instance to crash 1168406* If db_block_ckecking is enabled and a block is corrupted on disk DBWR could error attempting to write the block and bring the instance down. Additionally a corruption on the system tablespace could bring the instance down. With this fix the block will be marked as soft corrupt.. See <NOTE:96117.1> on Metalink
959593 Cntrl-C during truncate could cause ORA-7445 SIGSEGV in ksqcmi() and ORA-00600[1100]
1061775 An assert ORA-00600 [kclcget_1] might be signalled by LMD process under certain heavy load situations and cause an instance to crash.
1121157 If a shared server dies during the establishment of a dblink, PMON may crash with an ora-7445 in kmcdlc() while trying to clean up the Virtual Circuit.
1123988 Dead process cleanup can cause LMON to die with ORA-600[29703] causing the instance to crash.
1172044 This problem was introduced in 8.1.5 If a member of the current online log group failed multiple times, LGWR errors and crashes with ORA-600 [2745] while closing the file. 
1247625 If an error occurs when opening an outbound circuit for an xa application, then it is possible for PMON to crash when trying to age out a branch whose sestm has expired or which has been killed by asynchronous xa_rollback.
1279964 PMON can die with ORA-600[4414] if it is unable to get a latch to delete branch information. This can cause the instance to crash.
1310142 During cleanup of OBJ$, SMON may crash the instance with an ORA-600[16224] Workaround: Set <Event:10052> to disable cleanup of OBJ$. Re-enable the cleanup at less critical times.
DB-Link / Distributed 974519+ This problem was introduced in 8.1.5 Selects over a DBLINK may raise ORA-1008 when there is a BIND variable involved. Various forms of statement show this problem. Eg-1: INSERT into LOCAL_TABLE SELECT .. FROM tab1@link1, tab2@link1 WHERE col=:BIND Eg-2: SELECT ename FROM (select distinct ename from emp@sun86link where ename=name group by ename); Workaround: Set EVENT:10127 to level 1 eg: event="10127 trace name context forever, level 1" ** Warning: See <Note:75713.1> before setting any event This prevents the query block optimization code for DB LINKS from being invoked and so avoids the problem.
648147 Temporary segments are not released after the failure of local DDL involving a query to a distributed database.
784046 PL/SQL does not accept the syntax function@dblink(). for parameterless calls. Local empty calls are acepted. OK: "select f() from dual;", Not OK: "select f@x() from dual;"
1007024 When using MTS w/outbound links, and 'alter system kill session', the shared server could core dump without a trace file.
1022399 This problem was introduced in 8.1.5. A remote collocated join may dump in <Function:MSQOPNWS> when there is a predicate of the form: ":bind variable BETWEEN column1 AND column2" Workaround: Remote co-located joins can be disabled with <Event:10176> Important: Always read <Note:75713.1> before setting any event.
1035278 If the OPEN_LINKS database parameter is greater than 255, then if a two-phase commit failure occurs, RECO may fail with the internal error ORA-600 [k2rcbk: null gti]. This can prevent the database from starting. Workaround: Set <Parameter:OPEN_LINKS> to 255 or less.
1046027 This problem was introduced in 8.1.5 A Query which leads to a remote colocated join may return incorrect results if the query has non simple join predicates on the remote tables. This only happens when using CBO. 
1046896 A compile-time error (PLS-707) can occur when PL/SQL code calls a remote procedure with default values of parameters that call a STANDARD function. Eg: Remote procedure REMOTE_PROC(X DATE := SYSDATE) is called as BEGIN REMOTE_PROC; END; on a PLSQL client side or BEGIN REMOTE_PROC@DBLINK; END; over database link. The problem occurs if the version of "STANDARD" differs between the 2 ends of the RPC. Eg: 8.0 calls 7.3. Workaround: Use a constant default (such as NULL) and use this to indicate that a functional value (such as SYSDATE) should be used.
1060189 This problem is introduced by the fix for bug:513430 A remote query would occasionally corrupt the session heap and result in ORA-600 [17182]. This is most likely to occur if the query expands (Eg: using the USE_CONCAT hint) to several UNION-ALL'ed SELECT statements.
1063571 This fixes a regression introduced by the fix for <Bug:790632> such that access to remote variables was overly restricted by that fix. This is a CLIENT SIDE bug and can affect forms or other PLSQL based clients.
1065010 From Oracle8.0 remote queries look up the histogram rowcache for remote columns which can sometimes lead to increased contention on the shared pool. With this fix <Event:10129> can be set (at level 1) to revert back to pre-8.0 behaviour. With this event set remote queries will have less information available to determine the best execution plan. Important: See <Note:75713.1> before setting any event .
1067030 ORA-600[QKARMTVIEW20] possible from views that select from REMOTE tables Workaround: Set <Event:10127> to disable remote query blocks. NB: This w/a may impact performance.
1079156 This problem is introduced by the fix for bug:893259 CTAS through the database link might fail with ORA-1401 in multi-byte environment.
1120798 This problem was introduced by the fix for Bug:622264. When a PLSQL query across a DBLINK uses bind variables it is possible for wrong results to be seen.
1121157 If a shared server dies during the establishment of a dblink, PMON may crash with an ora-7445 in kmcdlc() while trying to clean up the Virtual Circuit.
1230884 A database link to a V7 database may raise the errors: ORA-1011: Cannot use v7 compatibility mode when talking to v6 server ORA-2063: preceding line from XXXXXX on connection if the session has previously used , or tried to use, a database link to an Oracle8.1 instance. Workaround: Open all Oracle7 links before any 8.1 link.
1247625 If an error occurs when opening an outbound circuit for an xa application, then it is possible for PMON to crash when trying to age out a branch whose sestm has expired or which has been killed by asynchronous xa_rollback.
1251491 This problem is introduced in 8.1.5 When the local machine is 8.1.X you access tables via a database link to a remote dataabase and your query uses the EXISTS clause then the EXISTS clause returns false every time causing incorrect results. This occurs regardless of the remote database versions. Eg: select 1 from dual where exists (select * from local805a@TOV805 a ,local805b@TOV805 b where a.a1=b.b1); Workaround: Set <Event:10127> to level 1 to avoid this problem Important: Read <Note:75713.1> before setting any event on a database.
1259062 ora-600[12811] can occur if a cursor referencing a remote function in the WHERE clause is mapped locally. Workaround: Use the rule based optimizer (where possible) eg: alter session set optimizer_mode=rule
1262540 In certain cases when database links are used, it is possible to get a core dump in lxdunld with a stack indicating network code called from opirip from an MTS shared server. On NT this can result in an instance crash.
1265468 Remote Oracle7 database tables may still be accessed in parallel by a local Oracle8i database regardless of the SQL specifying hints to stop parallel access.
1281200 This problem was introduced in 8.1.5 A query involving the join of 2 or more remote tables (over a dblink) could return the wrong result. Workaround Set event:10176 to level 1 Events should NEVER be set by customers unless advised to do so by Oracle Support Services. See <Note:75713.1> for more details.
1333360 Some queries that use the UNION or UNION ALL structure can core dump when parsed, if one of the UNION [ALL] branches is executed remotely.
Export/Import 239492 Import fails when encountering ANSI style comments in check constraints. Also see <Bug:427043>
427043 Import fails when encountering ANSI style comments in CHECK constraints. This is due to a problem with the way EXPORT writes the export file. Also see <Bug:239492>.
655950 User or Table level export may raise an EXP-3 error when exporting a partitioned table if a partition of that table has been EXCHANGED with another users TABLE. Attempts to extend the partition once the original owner has been dropped can also result in ORA-1950 errors. Workarounds: Export as SYSTEM. Only EXCHANGE within the current schema. Notes: The fix ensures that the segment owner is changed on EXCHANGE As such existing EXCHANGED partitions with this problem are corrupt and the fix will not address these.
731848 Improved the performance of LOB export and import by virtue of reading and writing using the LOB chunksize.
875427 ORA-02083 may occur exporting an AQ queue if there are remote subscribers.
907241 Importing the metadata for a TRANSPORTABLE TABLESPACE which contatin a LOCAL PARTITIONED INDEX with SUBPARTITIONS which have been EXCHANGED can raise ORA-600 [6012].
947083 EXP-56 / ORA-1007 may occur on export of a NESTED TABLE / OBJECT TABLE.
971769 Export does not export the statistics of bitmapped indexes.
971776 Import does not import the table stats even if user and db charsets are identical for the FIRST table in a transportable tablespace export file.
975185 If a table is renamed after a trigger has been defined on it then export of that table followed by an import will attempt to put the trigger on the OLD tablename. Eg: Create table A. Put trigger on A. Rename A to B. Export the schema. Import schema attempts to put the trigger on A not B.
980810 Export raises exp-00006 when there are a relatively large number datafiles ( around 50 ) in a tablespace when a full database export is performed.
1044883 Export fails with ORA-1455 and EXP-8 when attempting to export a snapshot having a snapshot id > 32767
1058861 EXPORT of DB on different platform leaks memory in the Export process. This memory leak can cause the export to fail with errors of the form: "kgefec: fatal error 0"
1067602 Export of a partitioned table having multiple index constraints can generate incorrect syntax in the export dump file. This can lead to a subsequent failure upon import. Workaround: It is possible to work around this problem by pre-creating the table and associated constraints and use IGNORE=Y
1076041 Export may fail with EXP-2 if a FILESIZE parameter > 4GB is specified in conjunction with multiple dump files. eg: exp system/manager filesize=4100m file=\(a.dmp, b.dmp\) full=y will fail when the first dump file reaches 4Gb in size.
1080833 Export fails with EXP-3 when attempting to export a table owned by the DBA performing the export and an index belonging to another schema owner exists on the same table. In 8.0 the index is not exported at all (no error) Workaround: Export as system/manager rather than the table owner.
1092638 Using Direct Export with MTS may result in a dump (ORA-7445). Workaround: Do not use MTS for direct export.
1106255 This problem was introduced in 8.1.5 when export of statistical data was introduced. Export process may core dump when writing the DBMS_STATS package ANALSTATS command into the export dump file for tables where histogram values are being collected for one or more columns, and those histograms have more than 140 data values. Workaround: Export without statistics
1107109 Export fails with EXP-003 when attempting to export functional or bitmapped indexes built on temporary tables.
1170962 Export by a V7 client of a schema in an 8i database fails with ORA-1436 if the database contains Java objects.
1201360 ORA-600 [kkzhmvc] can occur during import if the snapshot base table is missing and snapshot has hidden columns. The fix raises ORA-942 during import to allow the import session to continue.
1206380 Import of analyzed table using the IMP_FULL_DATABASE role can fail with ORA-1031 as this role is missing 'analyze any' privilege.
1218370 This problem was introduced in 8.1.5 EXP-56/OCI-22303 exporting OBJECT table even with the fix for BUG:882543 in place if the 'not-exists' dictionary entry has been re-used as a synonym or other dictionary item.
1229557 Export may write incorrect sizes for datafiles which are larger than 4GB into the export dump file.
1243649 This problem was introduced in 8.1.6 Export silently fails to dump synonyms which exist against objects in remote databases.
1260483 IMPORT using "TABLES=*" silently imports no rows.
1289441 Import can fail with ORA-959 "tablespace doesn't exist" with NLS_LANG set to certain values if tables contain column names ending _TABLESPACE.
1296292 When using analyze command or executing a query after importing statistics made by DBMS_STATS into dictionary, the server process may crash with ORA-7445. Workaround: Do not import statistics
1298586 This problem was introduced in 8.1.5 A long-running session that creates a large number (>32767) PL/SQL objects (e.g., an import) may core dump while creating a PL/SQL object beyond the 32K limit. (Note this is not a size limit on individual objects but on the total number of objects created in the session) This is most likely to affect long running sessions creating lots of PLSQL objects, such as IMPORT
1308267 Export incorrectly exports constraint definitions for cartridge schemas that aren't supposed to be exported.
1308272 Import with SHOW=Y does not show all SQL required to recreate a schema. In particular it does not show ALTER TABLE ADD CONSTRAINT statements to add constraints to a table, but does include ENABLE CONSTRAINT SQL.
Gateways / Heterogeneous Services 968360 When using SQL*PLUS COPY command to copy to an FDS through HS, rows may get duplicated. Eg: If there are 5 rows, and the array size = 3, 6 rows will get inserted, (the last row is duplicated). This problem ONLY affects Heterogenious Services (gateways)
1010782 A SELECT over a DB LINK from a GATEWAY which uses a SQL function that is not implemented at the remote site fails with ORA-3113/ORA-7445. Eg: "select SYSDATE from dual@dblink" where dblink on a non oracle database will fail .
1092735 When an Oracle8 server opens a database link connection and the server process has fewer than 'open_links' connections already open, then the server process closes in-active database link connections and re-use their control structures instead of allocating new connection control structures. This is a change in behaviour over Oracle7.
1097268 "ORDER BY DESC" clause not sent to gateway when it should
1163677 This bug can occur when running queries against a transparent gateway version 8 and above (these gateways use the heterogeneous services module of the Oracle database server - the earlier ones do not). What will happen is that when the user-session contains a large number of queries that reference data dictionary tables at the non-Oracle system, the error 28506 will be issued.
1192943 "N" not added to NCHAR literal if the HAVING clause for the gateway is post processed.
1258942 Accessing FDS through HS through another Oracle may result in ORA-3113 Example, client accesses table emp@link1 (where link1 is an Oracle-Oracle link. emp is a synonym on the target Oracle to an FDS system., i.e emp = emp@hslink; Then there can be an ORA-3113.
Hangs / Spins 1186884+ The combination of temporary tables and temporary tablespaces could cause the server to error out or spin upon abnormal client termination. Workaround: Use PERMANENT tablespace for users TEMP tablespace when using TEMPORARY tables.
720024 Alter Trigger can possibly cause a deadlock if performed concurrenly with a RENAME on the base tale
882995 SQL*Loader hangs while loading a NULL value (as in "") into a table.
890656 This problem was introduced in 8.1.5 If there are leading whitespaces in the record in the datafile that shows the length of the record in VAR option, sqlldr hangs.
912711 While running your instance with a value more than 65535 for PARALLEL_EXECUTION_MESSAGE_SIZE, parallel execution fails with ORA-12801 or hangs.
943057 When using single quotes with a hint '--+' on multibyteDB, SELECT statements can hang Workarounds: - Use '/*+ */' instead of '--+' in the hint. - Do not quote the hint
952323 While loading a LONG column, using the sqlldr API, if the size of the column less than 4000 bytes, the interface may hang
958026 When using transparent application failover with an application that uses array fetching (such as SQL*PLUS), queries which fail over sometimes return incorrect results or hang. Workaround - disable array fetches.
1043831 Client side may hang due to mutex deadlock in the Net code layer. This shows up as a hang and is most likely to affect clients such as Microsoft Transaction Server clients.
1049660 SSL client may hang trying to connect to a GSI server
1096056 ORA-600 [17034] can occur while attempting to update a table with an invalid value (value too large for column) if the table has UPDATE TRIGGER defined. The server process may spin (appearing to hang) on disconnect.
1101568 In an OPS environment, if one instance issues the command ALTER SYSTEM ARCHIVE LOG THREAD n CURRENT, with the thread n open, the instance which issued the command may hang. Workaround: Go to the instance for thread N and issue the command: ALTER SYSTEM SWITH LOGFILE;
1119894 Use of ALTER USER and TRUNCATE statements can cause a deadlock to occur against the ST ENQUEUE and DC_USERS row cache enqueue resources.
1120120 A Pro/OCI client may hang or dump after a call to a PLSQL procedure which raises a user defined exception (RAISE_APPLICATION_ERROR). The hang / dump occurs when the statement is re-executed.
1134530 Parallel CTAS with a nested loops input may hang Workaround: Force a hash join. 
1166931 UTL_PG.NUMBER_TO_RAW_FORMAT behaves badly for a NULL input. Results can include inconsistent return results, dump or tight CPU spin. Workaround: wrap any call to this function with a check to ensure the input is not NULL
1189628 Foreground processes may hang attempting to connect to the LMD. If 2 or more processes try to connect to the DLM at the same time a hang may occur. This is a generic bug but the chance of it occuring is far higher on certain platforms. Eg: Tru64 and HPUX 64 bit are prone to this bug Solaris is not Workaround: Set _lm_direct_sends=lkmgr
1219869 PMON may be unable to clean up a dead process in an OPS environment if it dies at just the wrong time. This can leave the dead process holding critical resources which cannot then be cleaned up resulting in a possible hang scenario.
1223914 ORA-600[2103] can occur when using ALTER TABLESPACE READ ONLY and ALTER TABLESPACE READ WRITE in separate sessions concurrently against different tablespaces. This shows up as a hang for 900 seconds before the ORA-600 is signalled.
1227790 OPS may hang if there is a communication error on the interconnect.
1231642 If timed_statistics is set to true, parallel queries and parallel CREATE TABLE AS SELECT could hang. Additionally Parallel CREATE TABLE AS SELECT can produce a corrupt table. Workaround: Disable TIMED_STATISTICS for parallel operations.
1234770 AQ spins in first message if OCI_ATTR_CORRELATION is specified as a OCI_DTYPE_AQDEQ_OPTIONS attribute.
1239140 SELECT/DESCRIBE hang against a table with a TEXT index which is being ANALYZED
1261868 RMAN: If SKIP INACCESIBLE is specified for an ARCHIVELOG Backup RMAN can sometimes hang.
1278873 PCM lock request might hang in high concurrent situation.
1293269 Client/Server can hang/spin (nttrd) over an SSL connection
1304159 Insert into a GLOBAL TEMPORARY TABLE with INDEX may hang/spin. This can sometimes be avoided by using "ON COMMIT DELETE ROWS" rather than the default "ON COMMIT PRESERVE ROWS"
1307660 A Hang / spin can occur using DML against a GLOBAL TEMPORARY TABLE with an index
1325384 When a TABLE expression is used with predicates on the collection type, for certain large collections (>100K) the session may loop continuously or sometimes crash.
1329607 Stale shadow lock at master resource caused can cause the system to hang. Symptoms include waits for 'GLOBAL CACHE CR REQUEST' and messages of the form "convack->closed from 0:0x972b65ec(remote=0x96835c68,0x25b),0x20002" from the LMD trace file, and LMD consuming much CPU. 
1329898 Deadlock detection takes too long. The integrated DLM parameter _lm_dd_interval can only reduce deadlock detection time to one minute at lowest, even set to 3 seconds.
1337858 High parse times are possible for queries with long AND and OR chains in their WHERE clause. Workaround: set the following init.ora _OPTIM_ENHANCE_NNULL_DETECTION=false
Large file issues (Eg: 2GB) 1076041 Export may fail with EXP-2 if a FILESIZE parameter > 4GB is specified in conjunction with multiple dump files. eg: exp system/manager filesize=4100m file=\(a.dmp, b.dmp\) full=y will fail when the first dump file reaches 4Gb in size.
1229557 Export may write incorrect sizes for datafiles which are larger than 4GB into the export dump file.
1296369 For 64 bit architectures, the "large_pool_size" and "shared_pool_size" instance parameters are artificially limited to 4GB. With this fix this limitation is increased to 8GB on 64 bit platforms.
MTS (Multi Threaded Server) 1007024 When using MTS w/outbound links, and 'alter system kill session', the shared server could core dump without a trace file.
1092638 Using Direct Export with MTS may result in a dump (ORA-7445). Workaround: Do not use MTS for direct export.
1121157 If a shared server dies during the establishment of a dblink, PMON may crash with an ora-7445 in kmcdlc() while trying to clean up the Virtual Circuit.
1166178 MTS servers may crash when using ADTs
1220769 ALTER SYSTEM SET MTS_DISPATCHER does re-register all dispatchers with the newly named listener address.
1247625 If an error occurs when opening an outbound circuit for an xa application, then it is possible for PMON to crash when trying to age out a branch whose sestm has expired or which has been killed by asynchronous xa_rollback.
1256011 If ora-4031 is encountered during session creation in MTS, then in 8.0.x the shared server might die w/ ora-600[1113]. In 8.1.x an ora-600[730] (memory leak) will be raised when the instance is shut down.
1262540 In certain cases when database links are used, it is possible to get a core dump in lxdunld with a stack indicating network code called from opirip from an MTS shared server. On NT this can result in an instance crash.
1309641 When a) the client is much slower than the server and b) there is minimal activity on the dispatcher, there can be an intermittent 60 second delay in dispatcher processing.
Memory Corruption 914998 If a query on a GV$-view is interrupted by CTRL-C, ORA-600 [17182] can occur during the following query or during logoff.
1011232 <Parameter:STAR_TRANSFORMATION_ENABLED> can lead to memory corruption / dumps
1028288 For Sort merge join, queries involving views may core dump in <Function:qkarwo> under specific circumstances.
1060189 This problem is introduced by the fix for bug:513430 A remote query would occasionally corrupt the session heap and result in ORA-600 [17182]. This is most likely to occur if the query expands (Eg: using the USE_CONCAT hint) to several UNION-ALL'ed SELECT statements.
1120811 This problem was introduced in Oracle8i. Create index may cause a memory corruption (16 bytes zeroed out) It is unusual for this corruption to cause an error to be signalled.
1182496 Access via a unique index on an IOT can cause ORA-600 17XXX errors due to SGA heap corruption. This can crash the database. (Note this only occurs if there is a UNIQUE SECONDARY index on the IOT. Workaround is to drop such indexes then bounce the DB)
1185844 Scan of an IOT secondary index can corrupt memory and cause a dump.
1279398 Memory corruption under <Function:kxsfwa> can occur if CURSOR_SPACE_FOR_TIME is TRUE and a session performs an ALTER SESSION SET NLS... command (or changes an NLS value via dbms_session.set_nls).
Memory Leaks 553250 When the amount of memory to allocate for a bind buffer exceeds the maximum allowed, ORA-00600 [17176] or [733] are raised.
762114 Shadow processes may accumulate lots of process-private memory if they parse SQL statements that have large in-lists or large OR-chains. Queries with large in-lists could use excessive PGA memory when parsed the CBO. This can be now be avoided by setting the <Event:10191> (any level) so that we do not convert in-lists back to OR-expanded form. Note that the event will NOT take effect if <event:10157> is set or the AND_EQUALS hint is used. NB: Read <Note:75713.1> before setting any event.
918272 ORA-600 [729] space leak occurs for "Pvt. audit infor." memory chunks. 
1019306 The ANALYZE TABLE command with the COMPUTE STATISTICS option uses a lot of memory when analyzing a table with a lot of partitions.
1022696 Java code may leak excessive memory (notably with ORDER BY)
1023988 Also see Bug:1040353 for part-2 of this fix When a function creates a temporary LOB locator of session duration and returns, there are two temporary LOB leaks. In the calling block, when the returned temp LOB is freed, there are still 2 LOBs left. Workaround: Always create temporary LOBs in call duration in functions if the temp is to be returned. If a session duration temp LOB is needed, you can copy the returned temp LOB to one created with session duration.
1032904 XA client memory leak if OBJECTS=T and threads terminate. Affects Microsoft-MTS
1040353 See also Bug:1023988 which is part one of this bug. When a function creates a temporary LOB locator of session duration and returns, there are two temporary LOB leaks. In the calling block, when the returned temp LOB is freed, there are still 2 LOBs left. Workaround: Always create temporary LOBs in call duration in functions if the temp is to be returned. If a session duration temp LOB is needed, you can copy the returned temp LOB to one created with session duration.
1058861 EXPORT of DB on different platform leaks memory in the Export process. This memory leak can cause the export to fail with errors of the form: "kgefec: fatal error 0"
1068882 This problem was introduced in 8.1.5. Adding datafiles to a database leaks a file descriptor which can cause maximum-open-file limits at OS level to be reached far quicker than then should. This can result in ORA-19502 and ORA-27077 errors. Workaround: Shutdown and restart to add more files.
1079796 Excessive process memory may be consumed for some operations, particularily on 64 bit architectures.
1086146 SNP memory leak. (Fixed in 8.1.7 under <Bug:1288817>) Workaround: Periodically stop and restart the SNP processes.
1092621 ALTER TABLE DROP PARTITION may consume excessive shared_pool resource and also ran at a sub-optimal speed.
1105054 Too much memory is consumed during the parse and type checking stages of a SQL statement when the statement was issued against a partitioned table with local indexes. 
1125724 During database shutdown, ORA-600[723] may be reported for memory chunks of type "LGWR PIC ins ar" and similar. Workaround: Set <Event:10262> to a value to avoid the problem The level should be set above the number of leaked bytes. Important: Always read <Note:75713.1> before setting any event.
1163677 This bug can occur when running queries against a transparent gateway version 8 and above (these gateways use the heterogeneous services module of the Oracle database server - the earlier ones do not). What will happen is that when the user-session contains a large number of queries that reference data dictionary tables at the non-Oracle system, the error 28506 will be issued.
1247197 Client memory leak when repeatedly executing SELECT on LOBs
1251390 Client memory leak handling LOBs
1258916 Repeated calls to setTransactionIsolation with an invalid value could result in ORA-1000. Eg: conn.setTransactionIsolation(Connection.TRANSACTION_REPEATABLE_READ); is invalid for Oracle but will leak a cursor as well as raising an exception.
1288817 Snapshot process performing AQ propogation grows in size
1294960 Client memory leak may occur running dynamic Method 4 application in a loop.
1312984 OCIEnvCreate / OCIHandleFree in a loop leak memory (in the client)
Migrate 541021 When using Migration Utility, and the mutliplier option is not defined the Migration Utility sometimes issues ORA-1632 max # extents (1) reached in index on MIGRATE.I_FILE#_BLOCK#.
717372 ORA-600 [KCBRLS_1] is possible on a read-only tablespace migrated from Oracle7
956373 Migrating 64 bit database to 32 bit database with compatibilty set to 8.1 leads to server crash with ORA-7445 .
1049367 This bug causes the migration utility to produce an error while the convert file is being created. The error is "datafile number being processed is incorrect during creating convert file". If this error occurs there was no way to use the migration utility to migrate the database from 7 to 8 without the fix.
1154181 DBA_TAB_PRIVS contains duplicate rows after a migration.
1301273 ALTER TABLESPACE ADD DATAFILE can fail with ORA-600 [5106] when adding more than one datafile in a single operation. There is no corruption involved, just this error. This is most likely to occur on a database which has been migrated from Oracle7 to Oracle8.
NLS (National Language Support) 943057 When using single quotes with a hint '--+' on multibyteDB, SELECT statements can hang Workarounds: - Use '/*+ */' instead of '--+' in the hint. - Do not quote the hint
964100 PROCOB generates precompiler error for 73rd column, when multi-byte characters are used in source lines.
988057 On some multi-byte character set environment, for example JA16SJIS, the query result which contains LIKE operator with ESCAPE keyword may wrong.
1000405 This will occur only in a database where the character set if multibyte. When killing a session in the SNP process, the SNP process may coredump in <Function:kgespf>
1070347 A PL/SQL procedure run in the server which alters an NLS parameter via dbms_session.set_nls() does not demonstrate the altered behavior. Only when the procedure completes, and another procedure is executed, does the altered behavior start to occur.
1079156 This problem is introduced by the fix for bug:893259 CTAS through the database link might fail with ORA-1401 in multi-byte environment.
1289441 Import can fail with ORA-959 "tablespace doesn't exist" with NLS_LANG set to certain values if tables contain column names ending _TABLESPACE.
OCI 1142096+ A describe of a cursor obtained as a REFCURSOR by executing a definer's rights function could fail with ORA-942 or other permissions errors. This is a regression introduced in 8.1.5 which may cause upgrade problems for applications using REFCURSORS extensively.
770841 Implicit data conversion from null terminated string host variable to date, results in ORA-1861 'literal does not match format string' if the table is locked.
857811 The OCI demo OCIAQDEMO00 uses the OS function sleep() which is not an NT function.
869244 When the user sigaction handler for SIGINT , registered with siginfo flag, access the second input argument, the application may core dump.
882995 SQL*Loader hangs while loading a NULL value (as in "") into a table.
923663 With the introduction of fix#735563, ORA-3106 is obtained for a break from a piecewise fetch instead of ORA-1013.
933380 A direct path API program built under 8.1.5 and run using 8.1.6 shared libraries may dump if using DATE data due to new un-initialized attributes introduced in 8.1.6. Workaround: client program MUST CALL call OCIAttrSet() with OCI_ATTR_DATEFORMAT attribute FOR ALL DATE COLUMNS.
944913 Exception in a Multithreaded Application .
952323 While loading a LONG column, using the sqlldr API, if the size of the column less than 4000 bytes, the interface may hang
1056740 ORA-3106 may occur on re-execute (using OCIStmtExecute) when the re-bind size of a select list item exceeds the previous bind size. Eg: select :b from dual; Bind :b as string of length 25 characters; Execute. Bind :b as string of length 100 characters; Execute but OCI_ATTR_DATA_SIZE has not been increased.
1058446 8.1 clients executing DML repeatedly receive far more bytes of data from the server than pre-8.1 clients, causing higher CPU usage in the client. This fix reduces the amount of network data for common DML operations. Note: This is a client side fix.
1063104 All valid cursors are unusable in all previous sessions after ending a new session.
1087876 A spurious ORA-24347 may occur in OCI for statements not using aggregate functions.
1103036 ORA-24777 using DBLINKs in XA or migratable OCI transactions without MTS. Note: XA sessions MUST be migratable and so must use MTS for DBLINKS. However, OCI initiated transactions may state OCI_TRANS_NOMIGRATE and thus should be allowed to open a DBLINK.
1112313 ORA-1801 may occur fetching a DATE column into a large buffer in Pro/OCI. Eg: If there is a LONG column prior to the DATE column being selected then it is possible to get ORA-1801 on the date column if the LONG column has a defined maximum length of 1Mb.
1120120 A Pro/OCI client may hang or dump after a call to a PLSQL procedure which raises a user defined exception (RAISE_APPLICATION_ERROR). The hang / dump occurs when the statement is re-executed.
1178918 This problem was introduced in Oracle 8.1.5 ORA-24347 may be incorrectly raised during the execute of a statement from Pro* / OCI if the statement handle previously had a null-query executed in it.
1230846 Compiling an application including ociap.h or ocikp.h may fail with a compiler error on multibyte platforms due to an 8bit character (0xa0) in the source file.
1237107 OCISubscriptionRegister() cannot be used multiple times for the same event - only the last registered callback is fired. With this fix all registered subscription handles are called.
1239470 Pro / OCI client side performance can be slower than earlier releases due to un-necessary lookup of ORA-1403 errors at the end of a series of fetches. The actual impact depends on the number of ORA-1403 errors received. This fix reduces the number of times we look up the error details.
1263903 ORA-1435 can be raised by OCISubscriptionRegister as the username is not converted to language independent format before being used.
1312984 OCIEnvCreate / OCIHandleFree in a loop leak memory (in the client)
Optimizer 1006563+ The optimizer does not pick a domain index for a query when the table is referenced via a synonym.uery.
870413 Sorts do not use an index unless hinted if columns could be NULL, even though the predicates ensured they were NOT NULL.
923793 For predicates involving bind variables with < . > , <=, >= and LIKE operations CBO uses a default selectivity value. However, in some cases this could make the predicate seem more selective than an equality (= :bind). This fix ensures that the selectivity is never less than an equality based on the table statistics. This fix is DISABLED by default in 8.1.6.2 and 8.0.6.2 To enable the new behaviour then: 8.1.6.2 Set Event:10133 to level 1 8.0.6.2 Set Event:10125 to level 1 See <Note:75713.1> before setting any event.
929403 When a view is created on an object table which references objects from another object table, the explain plan will show that a full table scan is used when querying the view, while an index scan is used when selecting from the base table.
955927 Expensive plan may be generated for query with like predicate with escape clause. Eg: LIKE '\_BBB%' ESCAPE '\' costed as if '_' was a wildcard.
983811 If a table T has a domain index on column c which supports a user-defined operator op(), then the optimizer does not pick the index with a key which looks like the following: "op(c, f('abc')) = 1" where f is a function, even though it is legal to use the index.
984132 If automatic replacement of literals with bind variables is enabled by using cursor_sharing = FORCE (either in the init.ora or by issuing an alter system or alter session), then statements with literals in a cursor expression can core dump. There is no workaround for this problem, other than disabling replacement of literals. Eg: "select cursor(select 'a' from dual) from po" may dump
1000432 ANALYZE ... ESTIMATE would in many circumstances choose a sample to analyse much smaller than that requested, resulting in incorrect sample results. 
1001840 ORA-600 [16550] / ORA-600 [QERFXARRAYMAXSIZE: NOT A FIXED TABLE] [SYS_ALIAS_0000] occurs with stored outlines enabled when a query has the same fixed table appearing more than once. Eg: alter session set CREATE_STORED_OUTLINES=TRUE; Select 'X' From v$nls_parameters a, v$nls_parameters b;
1002975 @This change is present for applications 11i CBO limits the number of join orders that it considers based on <parameter:OPTIMIZER_SEARCH_LIMIT> and so may not find the "BEST" plan. This fix changes the algorithm used to choose the initial join orders in an attempt to improve the chance of finding the best plan. To enable the fix then 8.1.7: Set _New_Initial_Join_Orders=true <Parameter:New_initial_join_orders> 8.1.6.1: Set <EVENT:10131> to level 1 or higher 
1039347 CBO uses the wrong cardinality for queries which are known to access a single partition but where that partition is not known until execution time. Eg: Where partitioned_date= some_function( SYSDATE )
1045707 A correlated column on a NOT IN list and a HASH or MERGE anti join may result in ORA-7445 [KKOAJT]. Eg: select b.BCD from TBL_1 b,TBL_2 a where not exists ( select * from TBL_2 a where b.CDNO not in (select a.CDNO from TBL_2 a)); Note that b.CDNO is correlated . Workaround: Set <Parameter:ALWAYS_ANTI_JOIN> to NESTED_LOOPS 
1070764 NOT IN optimization is not enabled for view columns. Eg: select * from xx where col1 not in (select c from vw) Workaround: Manually as IS NOT NULL predicates in the subquery. Eg: select * from xx where col1 not in (select c from vw where c is not null)
1086489 When "_complex_view_merging"=true and a functional indexes is on a table, subqueries can cause crashes.
1102605 Query with "LEADING" hint and "ORDERED" hint may DUMP in kkoiqb(). Eg: select /*+ LEADING (e) ORDERED */ e.empno,e.ename,e.sal,e.deptno,d.dname from emp e, dept d where e.deptno=d.deptno order by e.ename
1108002 ORA-600 [25012] is signaled when DBMS_STATS tries to gather statistics for a GLOBAL TEMPORARY table.
1111400 When a query contains lots of tables in the FROM clause the choice of join orders does not properly take into account single row tables in the query, potentially causing poor choice of initial join orders.
1113673 Under FIRST_ROWS optimizer mode, sometimes the correct domain index (which could eliminate an ORDER BY sort) is not picked by the optimizer.
1114064 Statistics for composite partitions do not appear in INDEX_STATS.
1157199 This fix allows CBO to use selectivity of individual columns in an outer join where one of the columns in the join has a complex expression rather than using default selectivity. To enable this fix: 8.1.7: ALTER SESSION SET "_ONESIDE_COLSTAT_FOR_EQUIJOINS"=TRUE; 8.1.6.1: Set <Event:10129> to level 1
1162839 CBO does not favour UNIQUE indexes on cost-tie With this fix CBO will favour the UNIQUE index if there are equal costs computed between UNIQUE and NON-UNIQUE index range scan
1168533 OR-expansion of a query involving a view with a PLSQL function may dump core. 
1192012 dbms_stats.gather_schema_stats() may skip a table and not recalculate the table's statistics when the 'GATHER STALE' and 'GATHER EMPTY' options are used.
1193115 Predicates of the form "e.empno=e.empno" which eliminate no rows from a query have the wrong selectivity and may hence affect which execution plan is chosen. This only occurs where for COLUMN=COLUMN predicates - constant equalities are handled correctly.
1215372 With complex view merging turned on, queries containing HAVING COUNT(column) may dump if "column" has a NOT NULL constraint on it.
1225256 There are 2 parts to this bug: INSERT INTO <TABLE> SELECT ... FROM <VIEW> should use CBO if the OPTIMIZER_GOAL is CHOOSE and tables inside <VIEW> have statistics on them or if <VIEW> has a hint in it. This bug causes RBO to be used instead. In Oracle7 hints in the VIEWs are not noticed but statistics do cause CBO In Oracle8 neither hints nor statistics cause CBO to be used. The only workarounds are: 1. To use ALL_ROWS or FIRST_ROWS optimizer goals or 2. Explicitly HINT the query or 3. Select direct from the table
1245019 Internal errors such as ORA-600 [19004] may occur from queries after statistics have been loaded using DBMS_STATS from a user stats table.
1251887 A select with literals as well as MIN or MAX is not able to use the INDEX MIN/MAX access path. This can result in slower performance than is possible. Eg: SELECT 'literal', MAX(COL) FROM TABLE does not use the INDEX MAX/MIN access path.
1273042 If you have a predicate like: op1(c1, op2(c2, 1)) = 2 and there is a domain index on the column c1 supporting the operator op1, then the optimizer sometimes chooses the domain index with this predicate as the key even if column c2 belongs to the same table as c1 or to a table that hasn't been joined yet.
1314506 Parse error can be returned if COMPLEX_VIEW_MERGING=TRUE and STAR_TRANSFORMATION_ENABLED=TRUE
1326515 ORA-907 ( Missing right parenthesis ) is signalled while running DBMS_STATS.GATHER_TABLE_STATS, if any of the column names in the table has spaces e.g. "Column 1"
1331694 When compiling a query joining to a partitioned table on which partition pruning (elimination) is not possible, Oracle may fail with ORA-7445 [MSQOR()]. The workaround is to set the following parameter to FALSE: _SUBQUERY_PRUNING_ENABLED.
1337858 High parse times are possible for queries with long AND and OR chains in their WHERE clause. Workaround: set the following init.ora _OPTIM_ENHANCE_NNULL_DETECTION=false
Oracle8 Datatypes 731848 Improved the performance of LOB export and import by virtue of reading and writing using the LOB chunksize.
780572 Usage of objects in XA applications can generate random and often non-existent runtime errors.
848744 CREATE TYPE statements ending with semicolon(;) and slash (/) as terminating characters encountered ORA-911 invalid character.
929403 When a view is created on an object table which references objects from another object table, the explain plan will show that a full table scan is used when querying the view, while an index scan is used when selecting from the base table.
933703 When using SQL*Loader in conventional mode to load tables containing LOB columns, the server sometimes returns the error ORA-22990: LOB locators cannot span transactions
947083 EXP-56 / ORA-1007 may occur on export of a NESTED TABLE / OBJECT TABLE.
980209 Secondary index-based scan for index-organized tables uses a range scan followed by range scan instead of range scan followed by unique scan.
1023988 Also see Bug:1040353 for part-2 of this fix When a function creates a temporary LOB locator of session duration and returns, there are two temporary LOB leaks. In the calling block, when the returned temp LOB is freed, there are still 2 LOBs left. Workaround: Always create temporary LOBs in call duration in functions if the temp is to be returned. If a session duration temp LOB is needed, you can copy the returned temp LOB to one created with session duration.
1040353 See also Bug:1023988 which is part one of this bug. When a function creates a temporary LOB locator of session duration and returns, there are two temporary LOB leaks. In the calling block, when the returned temp LOB is freed, there are still 2 LOBs left. Workaround: Always create temporary LOBs in call duration in functions if the temp is to be returned. If a session duration temp LOB is needed, you can copy the returned temp LOB to one created with session duration.
1082630 When an ADT type (having a nested table type embedded inside it) is used as column of a base table, it is not possible to use fine grained access control on the base table.
1087888 PL/SQL compiler did not allow inserting into a clob or blob column with character data through a subquery, or updating a set of columns containing one or more clob or blob columns.
1116304 This problem was introduced in 8.1.5 The combination the following 3 things: -- inserting into a view. -- the insert statement returning a "clob" col. -- modifying in a trigger a column not part of the original insert (e.g., doc_size in the test case below. causes ORA-00932 error. When using INSERT..RETURNING into a view with lob columns, the server would in some cases return an ORA-932 (inconsistent datatypes error)
1140587 Eg: select * from iot_table partition(xxx) where global_index_col<100 may return data from more than the specified partition giving incorrect query results.
1166178 MTS servers may crash when using ADTs
1185844 Scan of an IOT secondary index can corrupt memory and cause a dump.
1190845 The exception table used for an IOT stores the primary key column values from the table. The recursive SQL string used for this exception table is wrong when the IOT has one or more hidden columns (due to Functional indexes or Nested table). This causes ORA-604 / ORA-3001 when attempting to enable a foreign key constraint on the IOT.
1191683 ORA-22922 if multiple temporary LOBS returned from a query
1193075 Passing a very large object type or collection type value from a PL/SQL program to a java method (JSP) can lead to ORA-22813 errors and internal errors/dumps in some cases.
1222619 When using DBMS_LOB.APPEND to write CLOB data to a temporary CLOB it is possible for the write to fail with ORA-00600 [kdlseek-kgbtnscb].
1239889 ORA-3113 and error 21779 may occur trying to pass a temporary LOB back from an extproc callout.
1242873 When a CAST(MULTISET()) query is used in a INSERT statement or inside a view, and if the CAST query block has ORDER, GROUP BY, aggregates, DISTINCT etc the server may crash or raise an ORA-932 error. 
1245638 EXPLAIN PLANs of SQL statements with bind variables of object/collection types sometimes produce ORA-932 errors.
1248170 DML statements against object tables with common subexpressions and triggers (with OUT-binds) defined on the target table may produce incorrect results
1261753 When a temp lob is selected from a function into a local LOB variable in a query executed in a plsql block an ORA-22922 is raised.
1270820 Common subexpressions are not used for functions in a subquery. Eg: Statements of the form: "update point_table x set x.g2 = (select /*+ NO_MERGE +*/ Identity(x.g1) from dual);" where G2 is an object type will execute the Identify() function once for each attribute. Note the function MUST be created with the DETERMINISTIC pragma.
1294998 Creation of an IOT where all columns in the table comprised the mandatory primary key may fail with ORA-1429
1305188 If foo() is a plsql function returning a temp lob then SELECTing foo() in a query with an 'order by' clause will raise an ORA-22922 error.
1306577 When more than one user session issues an identical statement involving either object types or collection types, in some cases it works in one session and raises an ORA-904 in the other - even though both have identical privileges.
1325384 When a TABLE expression is used with predicates on the collection type, for certain large collections (>100K) the session may loop continuously or sometimes crash.
1360802 When updating a scalar attribute of an object type column, the server occasionally returns a spurious ORA-2309 (atomic null violation) error
Parallel Query (PQO) 532570 A class of SQL statements fails with an ORA-600 [15804] when executed in parallel due to incorrectly sharing Data Flow Operator SQL. Workaround is to Flush the Shared Pool
752740 If instance A is recovering a dead thread from instance B, using parallel transaction receovery, and Instance A isssues a shutdown, ORA-00600 [15753] can be signalled in one of the PQ Slaves.
896863 select distinct ... with group by may return non-distinct values for a distinct column if run in parallel and the GROUP BY list has keys other than DISTINCT keys
912711 While running your instance with a value more than 65535 for PARALLEL_EXECUTION_MESSAGE_SIZE, parallel execution fails with ORA-12801 or hangs.
936214 This problem was introduced in 8.1.5 Parallel CTAS with UNION ALL query branches may core dump (in <Function:kkfdmrk>) if one of the branches cannot be parallelized. Workaround: The problem only occurs if the branch which cannot be parallelized is not the first in the UNION ALL list. Hence a workaround is to re-order the UNION ALL branches so that non-parallelizable branches all occur first.
953471 This problem was introduced in 8.1.5 Parallel select with group by, with trunc() or round() in group by expression may result in a parallel slave process returning 'ora-979 not a GROUP BY expresson' followed by ora-12801. For this to occur the TRUNC or ROUND must have 2 arguments. Workaround: A possible way to avoid this problem is to use TO_DATE/TO_CHAR operators to mimick the TRUNC / ROUND behaviour. Eg: TRUNC(col,'YYYY') can be replaced by the (obscure) construct TO_DATE(decode(TO_CHAR(<COLUMN>,'YYYY')||'0101', '0101',null, TO_CHAR(<COLUMN>,'YYYY')||'0101'),'YYYYMMDD')
956131 ORA-600[15819] can be signalled when rebuilding a bitmap index in parallel for larger block sizes ( > 4k )
992350 ORA-00600 [kkfdjoi] is raised when parsing certain parallelisable statements especially when PARALLEL_BROADCAST_ENABLED=TRUE is in effect. . Workaround is to set PARALLEL_BROADCAST_ENABLED=FALSE
998575 This problem was introduced in 8.1.5. Select with group-by may result in ORA-600[XTYCSR3] if the select list involves aggregation functions and group by list involves constants and the query is parallelized.
1015291 If you have a group-by clause that matches a join column, then the optimizer may pick a sort-merge join when the join is in parallel even though hash join is a better choice.
1055497 Parallel Queries may error with ORA-12801 / ORA-960 for queries of the form: SELECT DISTINCT nr alias_a, nr alias_b FROM test ORDER BY alias_b; where a column is referenced more than once in the select list, and one of the aliases is used in the ORDER BY clause. Workaround: Apply a function to one of the duplicate columns to make them different. Eg: Use "nr+0 alias_a" in the example.
1064998 This problem was introduced in 8.1.5 Selects using aggregates of aggregates from an inline view may raise ORA-600 [kqassf2.3] when executed in parallel. Eg: select sum(total_1) total_1, sum(total_2) total_2 from (select sum(empno) total_1, sum(empno) total_2 from emp group by deptno);
1082299 Parallel CTAS may produce an incorrect result set in the target table if the driving select has columns of type CHAR used both in the select list and in the predicates.
1110876 Parallel query slave accessing bitmap index sometimes dies with internal error ORA-600 [20040].
1134530 Parallel CTAS with a nested loops input may hang Workaround: Force a hash join. 
1138239 Direct reads (such as used when performing a parallel select) on a plugged-in tablespace may cause ORA-600 [25012].
1175373 Wrong results possible from UNION ALL of partitioned tables if some of them have a degree of parallelism and some are NOPARALLEL.
1195108 This problem was introduced in 8.1.5 Queries that perform count(*) with group by on columns that have a bitmap index may error with ORA-600[9999]
1217243 Parallel queries can dump with ORA-600 [15805][1]
1220997 Select from a PARTITIONED TABLE in a READ ONLY DATABASE may result in ORA-7445 core dump if the query gets parallelized [with stack: kcrfss(), kcrflog(), kxfrFlushObjs(), kxfralo(), qerpxStart(), qersoStart(), selexe(),opiexe().. ]
1231642 If timed_statistics is set to true, parallel queries and parallel CREATE TABLE AS SELECT could hang. Additionally Parallel CREATE TABLE AS SELECT can produce a corrupt table. Workaround: Disable TIMED_STATISTICS for parallel operations.
1253281 ORA-600 [kkfdjoi4] may be raised for some statements that involve a join when executed in parallel. 
1253654 This problem was introduced in 8.1.5 Parallel query may return the wrong results if a GROUP BY clause is used with a function rather than a column. The wrong results may also occur if a parallel plan is run serially.
1274666 ORA-600 [15793] may be reported when an internode parallel query is interrupted This may cause the instance to crash.
1289533 Some classes of SQL using the UNION operator can fail with an ora-600 [kkfdjoi4] when executed in parallel. Workaround: Run serially, or try recoding to use a UNION ALL construct
1290569 Some SQL statements that execute against partitioned objects may fail with ora-600 [msqopnws_sys] if executed in parallel. Workaround: Execute serially Where possible try using UNION ALL in place of UNION - this can help for certain circumstances.
1296682 Parallel DML (PDML) runs serial from DBMS_SQL / PLSQL EXECUTE
1312233 This problem was introduced in 8.1.5 A Star query on partititioned tables with parallel degree >1 may result in internal errors ORA-600[25012] or ORA-600[KCBCUR_1) Workaround: Set <parameter:star_transformation_enabled>=false
1322914 This problem was introduced in 8.1.5 PQ may return ora-979 when slave sql generates bind variables.
Parallel Server 752740 If instance A is recovering a dead thread from instance B, using parallel transaction receovery, and Instance A isssues a shutdown, ORA-00600 [15753] can be signalled in one of the PQ Slaves.
906374 ora-7445 may occurwhen gv$views are joined with predicates containing instance id.
926536 This fix improves OPS resilience. If there is a protocol violation the Oracle shadow process aborts. If the shadow is LMD this could bring the instance down. LMD is now more resilient to protocol violations.
958026 When using transparent application failover with an application that uses array fetching (such as SQL*PLUS), queries which fail over sometimes return incorrect results or hang. Workaround - disable array fetches.
978970 A core dump occurred while freeing environment handle using OCIHandleFree() in an OPS, Failover configuration.
1000209 In parallel server waits for ROW CACHE LOCK could wait needlessly for 60 seconds before timing out. 
1042600 Shutdown of an OPS instance can signal ORA-600 [2658] or ORA-600 [1621] if the CKPT process of the instance being shutdown receives a cross instance call at the time of the shutdown.
1061775 An assert ORA-00600 [kclcget_1] might be signalled by LMD process under certain heavy load situations and cause an instance to crash.
1078972 The TNS_ADMIN environment variable is not passed to instances as they are being started by the OPSCTL command in an OPS environment.
1088158 The fairness down convert does not work if the exclusive holder for the lock is not on the resource master node.
1101568 In an OPS environment, if one instance issues the command ALTER SYSTEM ARCHIVE LOG THREAD n CURRENT, with the thread n open, the instance which issued the command may hang. Workaround: Go to the instance for thread N and issue the command: ALTER SYSTEM SWITH LOGFILE;
1105185 Some platforms close TCP end points if there has been no activity for a very long time. Keepalive can be used to prevent this default action by ensuring a connection is still valid. This fix causes TCP DLM interconnect to open connections with KeepAlive enabled to prevent unwanted timeouts. The implementation of this fix may vary between platforms.
1107871 An assert ORA-00600 [KJUOCL10] might be signalled by a process and cause the process to die when under heavy load in an OPS environment.
1123988 Dead process cleanup can cause LMON to die with ORA-600[29703] causing the instance to crash.
1129004 LMON intermittently dies with ORA-600[KJPRSEM:INUSE&!C] during domain cleanup.
1155042 When using Transparent application failover in the type=select mode, the application may leak memory
1155977 An assert ORA-00600 [KJDDOPR:PP] might be hit by the LMD process during deadlock detection causing the instance to crash.
1187868 ORA-54 is more likely to occur in Oracle8 OPS (than in Oracle7) for NOWAIT operations. (Eg: select .. for update nowait)
1189628 Foreground processes may hang attempting to connect to the LMD. If 2 or more processes try to connect to the DLM at the same time a hang may occur. This is a generic bug but the chance of it occuring is far higher on certain platforms. Eg: Tru64 and HPUX 64 bit are prone to this bug Solaris is not Workaround: Set _lm_direct_sends=lkmgr
1219869 PMON may be unable to clean up a dead process in an OPS environment if it dies at just the wrong time. This can leave the dead process holding critical resources which cannot then be cleaned up resulting in a possible hang scenario.
1223971 When using RMANs DUPLICATE command in an OPS database with 2 or more instances an ORA-2112 error is signalled by RMAN
1227790 OPS may hang if there is a communication error on the interconnect.
1243387 Out of shared pool memory might cause an ORA-600[KSIPGET_3] on OPS
1278873 PCM lock request might hang in high concurrent situation.
1314812 This problem was introduced in 8.1.5 "kjcvcrb: retry kjcvmsc" and performance problems on OPS with the 8i CR server.
1318308 This problem was introduced in 8.1.5 Referencing items in a readonly tablespace might cause ORA-600 [2251] in an OPS environment.
1320874 This problem was introduced in 8.1.5 OPS in CR-server mode might cause ORA-600[KCLBCPY2-1].
1329607 Stale shadow lock at master resource caused can cause the system to hang. Symptoms include waits for 'GLOBAL CACHE CR REQUEST' and messages of the form "convack->closed from 0:0x972b65ec(remote=0x96835c68,0x25b),0x20002" from the LMD trace file, and LMD consuming much CPU. 
1329898 Deadlock detection takes too long. The integrated DLM parameter _lm_dd_interval can only reduce deadlock detection time to one minute at lowest, even set to 3 seconds.
Partition Views (PV) 910876 A query against union-all view with a correlated subquery in the where clause may return an incorrect result if the subquery is NL joined and the subquery predicate is used for the index key.
1280318 Partition view filter does not work if a the query uses bind variable against for the partition key value.
Partitioned Tables 655950 User or Table level export may raise an EXP-3 error when exporting a partitioned table if a partition of that table has been EXCHANGED with another users TABLE. Attempts to extend the partition once the original owner has been dropped can also result in ORA-1950 errors. Workarounds: Export as SYSTEM. Only EXCHANGE within the current schema. Notes: The fix ensures that the segment owner is changed on EXCHANGE As such existing EXCHANGED partitions with this problem are corrupt and the fix will not address these.
898867 ORA-14101 errors may occur / not when a synonym exists on a partitioned table and partition extended naming is being used. NB: This bug only applies when explicitly using: <tablename> partition ( <partname> ) and <tablename> is a synonym for the user using this clause.
911777 Direct path loader incorrectly reports that rows have been successfully loaded when loading was actually aborted due to a PARTITION being readonly.
953424 ora-1037 can occur with a large number of bitmap indexes and partitions on a table. For this problem to occur then: Number of bitmap indexes * Number of partitions must be GREATER THAN 8000 
962964 Select from partitioned table with some of the partitions empty may raise ORA-7445 and dump in <Functio:KKEHBS> when column histograms are present. This bug was introduced by the enhancement in <Bug:707884> Hence a workaround is to set <Event:10158> at level 1 in Oracle 8.0 or set <Event:10169> at level 1 in Oracle 8.1
1006349 CBO may estimate the cost for local index access wrongly if a local index column predicate uses bind variables and the first partition is not representative of all partitions (eg: if it is empty). This can lead to sub-optimal plan.
1024478 Query which has inlist predicate and range predicate on partition columns may result in an incorrect result Eg: A table with "Partition by range (dt1,dt2)" can return wrong results for a query of the form: select * from dt where dt1 in (1,2) and dt2 >= 4 and dt2 <= 5 order by 1,2;
1039347 CBO uses the wrong cardinality for queries which are known to access a single partition but where that partition is not known until execution time. Eg: Where partitioned_date= some_function( SYSDATE )
1067602 Export of a partitioned table having multiple index constraints can generate incorrect syntax in the export dump file. This can lead to a subsequent failure upon import. Workaround: It is possible to work around this problem by pre-creating the table and associated constraints and use IGNORE=Y
1092621 ALTER TABLE DROP PARTITION may consume excessive shared_pool resource and also ran at a sub-optimal speed.
1095949 A select from a range partitioned table may error with ORA-600 [KKPAMFLIST] if there is no partition with MAXVALUE specified. Workaround: Ensure there is a partition covering up to MAXVALUE
1096441 A query on a partitioned table may fail with ORA-600 [12337] if when there is a partition key inlist and the partition key is used in other predicates. eg: Where pk in (1,2) and pk=ot.key Workaround: Set <Event:10157> to disable the Inlist iterator (see <Note:75713.1> before setting any event)
1105054 Too much memory is consumed during the parse and type checking stages of a SQL statement when the statement was issued against a partitioned table with local indexes. 
1114064 Statistics for composite partitions do not appear in INDEX_STATS.
1140381 Using SQL_TRACE against sessions accessing partitioned tables could dump core. This problem was introduced in 8.1.6 with the fix to include partition pruning information in SQL_TRACE trace files (Bug:714369)
1140587 Eg: select * from iot_table partition(xxx) where global_index_col<100 may return data from more than the specified partition giving incorrect query results.
1147272 A query on a partition table with a group by and an order by descending clause returned rows in the wrong order when the group by and order by columns are the same as the partition key
1171627 A direct load into an empty partition which has two or more subpartitions will corrupt the local indexes in all other partitions are truncated. Workaround: a. Insert at least one row into the partition you wish to load into or b. Re create all local indexes after the load
1175373 Wrong results possible from UNION ALL of partitioned tables if some of them have a degree of parallelism and some are NOPARALLEL.
1220997 Select from a PARTITIONED TABLE in a READ ONLY DATABASE may result in ORA-7445 core dump if the query gets parallelized [with stack: kcrfss(), kcrflog(), kxfrFlushObjs(), kxfralo(), qerpxStart(), qersoStart(), selexe(),opiexe().. ]
1251013 Analyze partition(ESTIMATE) produces inaccurate result of num_rows for correcponding index_partition. Workaround: Analyze index partition separately
1290569 Some SQL statements that execute against partitioned objects may fail with ora-600 [msqopnws_sys] if executed in parallel. Workaround: Execute serially Where possible try using UNION ALL in place of UNION - this can help for certain circumstances.
1305119 The following changes have been made under this bug number in order to improve performance in handling partitions at compile and partition maintenance time: - Partition maintenance operations no longer re-aggregate and derive the statistics from its subordinates to reflect the changes made by the operations. It is most recommended to collect the GLOBAL statistics with dbms_stats and periodically re-collect them as they become out dated. However, derived statistics can be updated by collecting the statistics of any one of its subordinates with dbms_stats or analyze. This is to save time in cases of applying such operations to multiple partitions at once. - If utilization of histograms is desired, they must be collected for all the partitions, except for the queries accessing only single known partition with the partitioning keys. This is to avoid loading unnecessary partition level statistics.
1312233 This problem was introduced in 8.1.5 A Star query on partititioned tables with parallel degree >1 may result in internal errors ORA-600[25012] or ORA-600[KCBCUR_1) Workaround: Set <parameter:star_transformation_enabled>=false
1312425 When a global partitioned index is created with the 'reverse', option for a partition table, the index table can be corrupted. Analyze table will show a mismatch with ORA-1499. Query against the table sometimes yields incorrect result.
1331694 When compiling a query joining to a partitioned table on which partition pruning (elimination) is not possible, Oracle may fail with ORA-7445 [MSQOR()]. The workaround is to set the following parameter to FALSE: _SUBQUERY_PRUNING_ENABLED.
Performance 1066827+ DML or Fetch operations raising NO DATA FOUND (ORA-1403 / ANSI error 100) can cause an extra shadow process to be spawned to handle the error text. This can severely impact performance of PRO* clients. Main Symptoms: Server trace shows long gaps between "SQL*Net message from client" Client SQL*Net trace shows new connections established SQL*Net trace shows ORA-1013 and ORA-1019 errors after each ORA-1403 Client TRUSS / TRACE shows unexpected fork() or connect() operations
731848 Improved the performance of LOB export and import by virtue of reading and writing using the LOB chunksize.
887571 Enabling a PK for which the columns are known to be NOT NULL and a unique index already exists for the PK keys performs a full table scan which is not needed.
904133 DBMS_PIPE is slower in 8.X than 7.3 (more CPU used)
914797 Views with INSTEAD-OF triggers may now be merged during query optimization
955705 DML on updatable join views with rowid predicates use full table scan access, rather than the more efficient rowid access.
1000209 In parallel server waits for ROW CACHE LOCK could wait needlessly for 60 seconds before timing out. 
1000432 ANALYZE ... ESTIMATE would in many circumstances choose a sample to analyse much smaller than that requested, resulting in incorrect sample results. 
1033706 The tkprof utility can core dump when it needed to grow its internal cursor array. This can typically occur if there are over 300 cursors in the trace file.
1040651 Queries against the DBA_DML_LOCKS view can be slow.
1042955 Queries using TO_DATE on binds can be slower than queries using to_date on literals. Eg: where DT > to_date(:d1,'MMYYYY') uses more CPU during row fetching than where DT > to_date('101999','MMYYYY')
1058446 8.1 clients executing DML repeatedly receive far more bytes of data from the server than pre-8.1 clients, causing higher CPU usage in the client. This fix reduces the amount of network data for common DML operations. Note: This is a client side fix.
1065010 From Oracle8.0 remote queries look up the histogram rowcache for remote columns which can sometimes lead to increased contention on the shared pool. With this fix <Event:10129> can be set (at level 1) to revert back to pre-8.0 behaviour. With this event set remote queries will have less information available to determine the best execution plan. Important: See <Note:75713.1> before setting any event .
1114711 PL/SQL performance slower than required because NLS data structures are not cached.
1115424 Cursor checking may insert duplicate entries in the authorization and dependency lists adding load to the shared pool.
1131535 SMON can take a long time to clean up temp segments in TEMPORARY TABLESPACES. This fix skips the steps to flush blocks from the buffer cache during the SMON cleanup to save time.
1140381 Using SQL_TRACE against sessions accessing partitioned tables could dump core. This problem was introduced in 8.1.6 with the fix to include partition pruning information in SQL_TRACE trace files (Bug:714369)
1146729 This problem was introduced in 8.1.5 Updates/deletes can take a long time when indexes are present on the table and the indexes are modified.
1153691 Faster type checking for TO_DATE expressions during parse. This is mainly for partition tables where the partition key is a date column.
1193003 This problem was introduced in Oracle 8.1.5 SQL statements may not be shared when they should be. This can increase shared pool latch and library cache latch contention
1210242 This problem was introduced in Oracle 8.1.5 Cursors are not shared if both TIMED_STATISTICS and SQL_TRACE are set to TRUE. Also see Bug:918002 
1239470 Pro / OCI client side performance can be slower than earlier releases due to un-necessary lookup of ORA-1403 errors at the end of a series of fetches. The actual impact depends on the number of ORA-1403 errors received. This fix reduces the number of times we look up the error details.
1259631 A sort-merge join is used instead of nested loops in the materialized aggregate view refresh query when the table has been modified by a direct load. This affects the performance of refresh.
1270820 Common subexpressions are not used for functions in a subquery. Eg: Statements of the form: "update point_table x set x.g2 = (select /*+ NO_MERGE +*/ Identity(x.g1) from dual);" where G2 is an object type will execute the Identify() function once for each attribute. Note the function MUST be created with the DETERMINISTIC pragma.
1329899 If 'ALTER VIEW COMPILE' may take a long time compared with recreating the view, espacially if partitioned tables are involved.
Query Rewrite (including Materialized Views) 860708 Query rewrite not performed when grouping on a query delta column
1200005 Create materialized view on a prebuilt table having columns of type FLOAT raises ORA-12060
1206933 The server sometimes allows creation of materialized views which are fast refreshable with expressions on aggregates in the select list. This could lead to incorrect results in case of a full text based rewrite.
1219363 Fast Refresh is not allowed for materialized view on a join if there is a simple filter predicate on one of the columns (eg: column=constant). This fix allows such queries to produce fast refreshable materialized views rather than raising ORA-12015 
1228658 This problem was introduced in 8.1.6.0 Create INDEX on a snapshot / MVIEW can produce a corrupt index. This may show up as ORA-600 [13004] or an ORA-600 [25012] or ANALYZE TABLE snapshot_name VALIDATE STRUCTURE CASCADE reporting ORA-1499. This can easily occur if the index can be built from an existing index on the snapshot.
1243417 Materialized views may remain INVALID after successful refresh. This can cause performance problems as clients each try to recompile the materialized view.
1245392 Fast refresh of a materialized view / snapshot may miss some rows when more than 1 snapshot is based on the same master table.
1257713 Query rewrite may signal ORA-932 when BINDS are used
1259631 A sort-merge join is used instead of nested loops in the materialized aggregate view refresh query when the table has been modified by a direct load. This affects the performance of refresh.
RMAN (Recovery Manager) 977412 RMAN does not remove a backup script if after "delete script" some other command is executed (e.g. "list incarnations").
1040149 The RMAN "DUPLICATE" command does not handle READONLY tablespaces correctly Workaround: Use SKIP READONLY
1058508 RMAN is unable to create a snapshot controlfile if the ORACLE_HOME of the target database has changed (e.g. due to an upgrade). Workaround: Several. Eg: set snapshot controlfile name to '/<path>/<snpshot_file_name>'
1164440 The RMAN command "release channel" reports RMAN-20020 if there are "set until" and "alter database open reset logs" commands in the same "run" block.
1171700 RMAN command "RECOVER ... DELETE ARCHIVELOG" does not work properly in an OPS enviroment. The command may delete archive logs before they are applied.
1186564 The RMAN command DUPLICATE causes RMAN-600 [14019] if MAXLOGHISTORY > 9999.
1186598 RMAN catalog upgrade from 8.1.5 to 8.1.6 fails (eg: RMAN-6444) Workaround: See <Note:99922.1>
1188620 When several hundreds of records are purged from the catalog with the prgrmanc.sql script, users may receive ORA-1001
1218454 RMAN was unable to find archived log backups or copies which really did exist (during certain commands such as CROSSCHECK BACKUP OF ARCHIVELOG ALL).
1223971 When using RMANs DUPLICATE command in an OPS database with 2 or more instances an ORA-2112 error is signalled by RMAN
1228207 RMAN: When user specifies a TIME for duplication, the time is rounded to a log boundary, thus restore to the middle of a log is not possible.
1256226 RMAN does not allow parameters > 255 characters in an ALLOCATE CHANNEL PARMS clause.
1261868 RMAN: If SKIP INACCESIBLE is specified for an ARCHIVELOG Backup RMAN can sometimes hang.
1279094 Files restored by rman will contain checksums even when db_block_checksum=FALSE
Replication 859195 ORA-24324 can be obtained when ConText is used with Replication.
922509 ORA-3113 during create_snapshot_repgroup or drop_snapshot_repgroup if snapshot is on a pre 8.1 version and master is on 8.1.5 or higher.
960119 If a database at a master site had an SCN that is big enough to have a non-zero wrap number, then doing a snapshot refresh generates an ORA-7445 error and a core dump on the master site, and an ORA-2055 on the snapshot site. This happens regardless of the mechanism used to do the refresh, whether with the DBMS_SNAPSHOT.REFRESH() procedure, or with automatic snapshot updating (via SNPn processes and the init.ora parameters JOB_QUEUE_PROCESSES and JOB_QUEUE_INTERVAL). It also happened regardless of the method used, whether fast, complete, or force. This problem was introduced in Oracle 8.1.5
978980 CREATE SNAPSHOT may raise ORA-955 during snapshot index creation if there are a sufficient number of snapshot indices created in the schema.
1070909 ORA-1436 when running add_master_database in a JVM environment.
1116610 Coredump may occur during simultaneous refresh of Java RepAPI snapshots or during offline instantiation of a Java RepAPI refresh group template
1185585 Incorrect INSERT statements are generated when offline instantiating templates containing VARCHAR2/CHAR/NCHAR etc.. strings with quotes in them.
1232902 RepSample.java demo program is missing from the 8.1.6 installation
1244117 This problem affects snapshots created in 8.1.5 onwards. ORA-12028 "snapshot type is not supported by master site XXX" may occur if you attempt to create a snapshot in Oracle 8.1 when the master table is on V7X or V80. (The create snapshot may also fail with ORA-600 [15459]) The problem occurs when the snapshot is not a primary key or rowid snapshot.
1273886 This problem was introduced in Oracle release 8.1.6.0 ORA-00904 "invalid column name" can occur while executing dbms_snapshot.create_snapshot_repobject in 8.1.6 if the master object is in an 8.0 or Oracle7 database
1281599 Java RepAPI session crashes on LOB PUSH when MTS_SERVERS>1
SQL*Loader 620277 Sqlldr in direct mode rejects records if the NULLIF/DEFAULTIF clause length is greater than the column size. Users receive ORA-2359: Field in data file exceeded maximum specified length
690443 With sqlldr, rows get inserted into the table even if an after statement trigger fails and table ends up with wrong rows. This happens if there is also a row level trigger that passes.
709485 When file='datafile' option is used in the command line for parallel direct load with table-name given in double quotes in the control file Loader gives SQL*Loader-927: Table does not exist error.
882995 SQL*Loader hangs while loading a NULL value (as in "") into a table.
883867 Sql*Loader raises ORA-600[6971] when loading data of size >64K with "CONTINUEIF NEXT" option in direct mode.
890656 This problem was introduced in 8.1.5 If there are leading whitespaces in the record in the datafile that shows the length of the record in VAR option, sqlldr hangs.
896493 SQL*Loader crashes when long error messages ( > 256 ) are generated by raise_application_error() in the table's triggers or associated procedures.
911777 Direct path loader incorrectly reports that rows have been successfully loaded when loading was actually aborted due to a PARTITION being readonly.
918211 SQL*Loader dumps using VARCHARC/VARRAWC with LENGTH>10 Eg: Using a control column specification of (col1 VARCHARC(11,20)) will dump.
933703 When using SQL*Loader in conventional mode to load tables containing LOB columns, the server sometimes returns the error ORA-22990: LOB locators cannot span transactions
939510 Direct-path loader sometimes caused corrupted data to be loaded if both the CONTINUEIF continuation clause and the PIECED field option are specified Workaround: Use conventional load.
944009 Loader may report ORA-1722 when loading zoned data. This problem was introduced in 8.1.5
1001227 This problem was introduced in 8.1.5 If SQL*Loader uses the ENCLOSED BY clause along with TERMINATED BY X'09' (the TAB character) then records are rejected with a "NO TERMINATOR FOUND" error.
1012544 THis problem was introduced in 8.1.5 Sql*Loader may return 'SQL*Loader-941: Error during describe of table' and 'ORA-04043: object does not exist' when loading data through a view Workaround: Load the base table directly.
1050045 ORA-2363 may be signalled and valid data discarded when: - termination and optional enclosure delimiters are defined ('CONTINUEIF' and 'FIELDS TERMINATED BY' clauses in use) - a logical record consists of some physical records - a field (column) is split into these physical records and the field does not use the enclosure delimiters. - these physical records are split into separate read buffers
1083887 SQL*Loader does not the handle maximum errors parameter (ERRORS) correctly on multiple table inserts.
1084068 This problem was introduced in 8.1.5.0 Using conventional path loader to load packed decimals from EBCIDIC data file would result in error LDR-641: Invalid zoned decimal nibble Workaround: Use direct path load
1115758 Conventional path loader may sometimes reject good records containing zoned/packed decimals depending on the order of the records.
1146253 Direct load operations (direct load, CTAS, APPEND) may set the wrong space usage on a block if the table being loaded has more than 255 columns but the head pieces end up less than the "stub space" (9 bytes). This can introduce a silent corruption which is only detected later on, (or will crash the load session if block checking is enabled). . This cannot occur in Oracle7 as there cannot be > 255 columns . Analyze of affected objects typically show: "kdbchk: the amount of space used is not equal to block size "
1171627 A direct load into an empty partition which has two or more subpartitions will corrupt the local indexes in all other partitions are truncated. Workaround: a. Insert at least one row into the partition you wish to load into or b. Re create all local indexes after the load
1186914 Parallel direct load may set index status to VALID when no rows are loaded, even though a concurrent load job may have made the index invalid by loading rows. This can introduce a mismatch between index and table data. . Workaround: Recreate indexes after a load.
1271684 SQL*Loader does not read data from the standard input stream when using the INFILE "-" clause in the control file. There are several related bugs for this problem in earlier Oracle releases.
1311077 Direct path loader put rows into the blocks with very poor space utilization when a number of columns was more than 255 and a DB block size was big enough to store 2 and more rows in a block.
1322944 While using SQL*Loader in direct mode with the SINGLEROW option, if the load fails then the Index may still be marked as USABLE, but the table and index are inconsistent.
Security 1082630 When an ADT type (having a nested table type embedded inside it) is used as column of a base table, it is not possible to use fine grained access control on the base table.
1139334 OS Authentication over SQL*Net may cause the Oracle shadow to dump (ORA-7445) in nau_ctl or similar.
1285808 Changes of application context inside a trigger or a procedure is not seen by the subsequent SQL ( query or DML ) until the next time the trigger or procedure is invoked again.
Space Management 648147 Temporary segments are not released after the failure of local DDL involving a query to a distributed database.
986928 DBMS_SPACE.UNUSED_SPACE yields an internal error when issued against a temporary table (or an index on such a table). The fix is to issue an external error - ORA-3211 (since such an operation is not supported).
1311077 Direct path loader put rows into the blocks with very poor space utilization when a number of columns was more than 255 and a DB block size was big enough to store 2 and more rows in a block.
1325540 Migration of a dictionary managed tablespace to bitmapped can fail with ORA-600 [KTTMUPD_SEGMENT-] (from DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL)
Wrong Results 1120715+ This problem was introduced in 8.1.6 Standard date/time functions may give unexpected results when used in PLSQL. This can show up in lots of forms. The problem is that certain functions / operators now default to datatype TIMESTAMP in PLSQL rather than DATE. Eg-1: "declare cursor c is select nvl(sysdate,'11-JAN-99') from dual;" returns a TIMESTAMP. Eg-2: ALTER SESSION SET NLS_DATE_FORMAT = 'DD-MON-YY'; declare mydate DATE; BEGIN mydate := '12-JAN-95'; if (mydate = '12-JAN-95') then AAA else BBB end if; END; Will run BBB rather than AAA as both sides of '=' are converted to a TIMESTAMP. Workaround: Use explicit datatype casting (TO_DATE)
641756 A select from ALL_SYNONYMS may not find the complete set of accessible synonyms for the user performing the query. (This has been the case at least since Oracle 7.1.6)
644176 If a startup parameter value exceeds 512 characters, a select from V$PARAMETER returns a NULL value for the parameter. The parameter value is also not printed to the alert log on startup.
896863 select distinct ... with group by may return non-distinct values for a distinct column if run in parallel and the GROUP BY list has keys other than DISTINCT keys
908985 UID, LEVEL and ROWNUM are unsigned numbers within the server yet are incorrectly converted to signed numbers when passed to the client. This causes unwelcome effects such as negative user numbers e.g. in 'select uid from dual;'
910876 A query against union-all view with a correlated subquery in the where clause may return an incorrect result if the subquery is NL joined and the subquery predicate is used for the index key.
958026 When using transparent application failover with an application that uses array fetching (such as SQL*PLUS), queries which fail over sometimes return incorrect results or hang. Workaround - disable array fetches.
968360 When using SQL*PLUS COPY command to copy to an FDS through HS, rows may get duplicated. Eg: If there are 5 rows, and the array size = 3, 6 rows will get inserted, (the last row is duplicated). This problem ONLY affects Heterogenious Services (gateways)
974742 Oracle does not report an error if (+) is specified in select-list. The OUTER JOIN operator (+) is only valid in WHERE clause predicates. As this is not flagged as an error the query can give unexpected results. The correct action to avoid this problem is to fix the query.
988057 On some multi-byte character set environment, for example JA16SJIS, the query result which contains LIKE operator with ESCAPE keyword may wrong.
1024478 Query which has inlist predicate and range predicate on partition columns may result in an incorrect result Eg: A table with "Partition by range (dt1,dt2)" can return wrong results for a query of the form: select * from dt where dt1 in (1,2) and dt2 >= 4 and dt2 <= 5 order by 1,2;
1031050 Sort-Merge join may return incorrect results for certain forms of query when an incorrect assumption that the driving table is trivially ordered and no transitive predicate is generated for expressions. Eg: SELECT /*+ ordered use_merge(B) */ ac, bc FROM A,B WHERE B.bc = 2 AND A.ac + 0 = B.bc; (A holds 3,2,1; B hold 2) Plan incorrectly omits a sort on A: MERGE JOIN FULL SCAN of A SORT FULL SCAN of B
1044557 RBO may return incorrect results if a query compares ROWNUM to an aggregate in an inline view. Eg: select rownum,empno from scott.emp, (select max(2.8) mx from dual) where rownum<mx; Workaround: Use CBO.
1044800 SELECT ROWID FROM <TABLE> returns nonsense if the server is EBCDIC and the client is ASCII. Note: This is a CLIENT SIDE fix.
1046027 This problem was introduced in 8.1.5 A Query which leads to a remote colocated join may return incorrect results if the query has non simple join predicates on the remote tables. This only happens when using CBO. 
1082299 Parallel CTAS may produce an incorrect result set in the target table if the driving select has columns of type CHAR used both in the select list and in the predicates.
1096399 The LAST_DDL_TIME field in ALL|DBA|USER_OBJECTS is not updated following a rebuild of a non-partitioned index.
1105194 When cost based optimizer is used a query may return the wrong number of rows when the INLIST ITERATOR is used against user supplied ROWIDS and there is a join to another table. Eg: select .. from A, B where a.c1=b.c1 and B.ROWID in ('AAAA2BAAEAAAALYAAA','AAAA2BAAEAAAALYAAB','AAAA2BAAEAAAALYAAC');
1115720 DBMS_SQL.BIND_ARRAY processed twice as many rows as in the bound PL/SQL table for specific input table sizes (related to internally determined collection page size). Example: For DBMS_SQL.VARCHAR2_TABLE type, the size happens to be 12231; if user binds a VARCHAR2_TABLE table using DBMS_SQL.BIND_ARRAY to a DML statement, then the DML statement will be executed 24460 times (should be 12231 times).
1120798 This problem was introduced by the fix for Bug:622264. When a PLSQL query across a DBLINK uses bind variables it is possible for wrong results to be seen.
1122703 Wrong results possible with "_OR_EXPAND_NVL_PREDICATE" and zero length strings. Eg: '' should be treated the same as NULL when this parameter is TRUE but it may not. The fix addresses this problem.
1136037 Wrong results can occur under CBO if INLIST contains a correlated variable. Eg: t.col IN (t2.col, t2.col_b)
1140587 Eg: select * from iot_table partition(xxx) where global_index_col<100 may return data from more than the specified partition giving incorrect query results.
1147272 A query on a partition table with a group by and an order by descending clause returned rows in the wrong order when the group by and order by columns are the same as the partition key
1150775 Queries that SELECT from a VIEW which contains more than one predicate, and where one of the predicates is based on ROWNUM, may return fewer rows than expected.
1170095 When passing an _EXPRESSION_ as an actual parameter to a subroutine IN formal parameter, if the expression is of type CHAR and the formal parameter is VARCHAR2, or vice versa, the parameter's type is not changed to that of the actual. This results in the parameter having incorrect semantics in the called function which can result in incorrect behaviour. (We should use the semantics of the PASSED IN type)
1175373 Wrong results possible from UNION ALL of partitioned tables if some of them have a degree of parallelism and some are NOPARALLEL.
1176886 This bug is effectively a duplicate of <Bug:385681> re-introduced in 8.1 If an SMJ and unique index scan and the index scan is known to return only a single row then a query may either dump or return incorrect results. Workaround: Use CBO
1185618 STAR_TRANSFORMATION can cause wrong result if fact and dimension table are joined on more than one column. This can also cause core dumps as opposed to incorrect results
1208080 m/n gives the wrong result for these two numbers m=2787433692433919301962350007441968 n=1099511627776 (ie: 2^40)
1210899 Wrong result could be returned if a subquery has MIN(trailing index column) in the select list. Workaround: Set <event:10167> to disable index min/max scan Important: Read <Note:75713.1> before setting any event on a database.
1223775 PUSH_JOIN_PREDICATE into a view which includes a sort-merge-join can result in incorrect results. Workarounds: Disable pushing of join predicates ie: Set <Parameter:PUSH_JOIN_PREDICATE> to FALSE. This parameter is hidden in Oracle8i or Ensure there is no SMJ in the view.
1232884 INSERT /*+ APPEND */ does not blank pad CHAR columns
1251196 Wrong result can be returned , or coredump can occur if a query joins a complex view to a table (or other view) on aggregation column, and a query has filter predicate on the same aggregation column: Eg: CREATE VIEW V as select acol ,... from T1 groub by acol; select acol from V,T2 where V.acol=T2.col and V2.col RELOP const
1251491 This problem is introduced in 8.1.5 When the local machine is 8.1.X you access tables via a database link to a remote dataabase and your query uses the EXISTS clause then the EXISTS clause returns false every time causing incorrect results. This occurs regardless of the remote database versions. Eg: select 1 from dual where exists (select * from local805a@TOV805 a ,local805b@TOV805 b where a.a1=b.b1); Workaround: Set <Event:10127> to level 1 to avoid this problem Important: Read <Note:75713.1> before setting any event on a database.
1253654 This problem was introduced in 8.1.5 Parallel query may return the wrong results if a GROUP BY clause is used with a function rather than a column. The wrong results may also occur if a parallel plan is run serially.
1259714 A query with a descending order-by clause that involved a sort-merge join between two views returned incorrect results. 
1281200 This problem was introduced in 8.1.5 A query involving the join of 2 or more remote tables (over a dblink) could return the wrong result. Workaround Set event:10176 to level 1 Events should NEVER be set by customers unless advised to do so by Oracle Support Services. See <Note:75713.1> for more details.
1324092 This problem was introduced in 8.1.6.0 A query with outer joins and a descending order-by clause on one of the join columns returns incorrect results.
1329211 Group by cube operator can return incorrect results. The grouping function used in conjunction with the cube operator to distinguish between aggreagate NULL and real values returns wrong values. The query returns NULL where real values are expected and vice versa.
XA 670827 When using an Oracle8 XA client to connect to an Oracle7 database, XA_RECOVER gets ORA-942 trying to read V$XATRANS$.
780572 Usage of objects in XA applications can generate random and often non-existent runtime errors.
951528 If a prepared XA transaction had more than two transactions branches, then xa_recover could fail to find the transaction, or could fail with ORA-1722.
966392 XA clients may crash if using connection caching from a V8 client to a V7 database. 
976768 If ax XA transaction was suspended, and if a second transaction was then executed in the same server including an xa_end with TMSUCCESS flags, then the fetch state for cursors in the first transaction would be reset. When the process resumed the first transaction, it would get ORA-1002 if it tried to fetch again from the cursors.
1020305 If an error occrred in xaoclose, the XA trace file is written to the directory in which the program was launched rather than in the specified LogDir.
1032904 XA client memory leak if OBJECTS=T and threads terminate. Affects Microsoft-MTS
1103036 ORA-24777 using DBLINKs in XA or migratable OCI transactions without MTS. Note: XA sessions MUST be migratable and so must use MTS for DBLINKS. However, OCI initiated transactions may state OCI_TRANS_NOMIGRATE and thus should be allowed to open a DBLINK.
1116499 When using XA transaction having multiple branches in a transaction, ORA-600[6856] and data corruption could occur if the branches were simultaneously rolled back.
1247625 If an error occurs when opening an outbound circuit for an xa application, then it is possible for PMON to crash when trying to age out a branch whose sestm has expired or which has been killed by asynchronous xa_rollback.
1266632 When running an XA application with database links, it is occasionally possible to get ORA-600 [16352] / ORA-00600 [16377]. This can occur as it is incorrectly possible for a DEDICATED XA session to use a database link if it has previously been opened by an MTS connection. Dedicated connections should raise ORA-24777 when an attempt is made to use a database link.
1279964 PMON can die with ORA-600[4414] if it is unable to get a latch to delete branch information. This can cause the instance to crash.
1285882 This problem was introduced in 8.1.5 XA client with V8OCI connection from a Pro* client may get an ORA-3113
1328999 Multiple branches in a global transaction may signal a false deadlock between each other. This typically shows up as an ORA-60 between a DX lock and an 'enqueue hash chains' latch .
PL/SQL 1120715+ This problem was introduced in 8.1.6 Standard date/time functions may give unexpected results when used in PLSQL. This can show up in lots of forms. The problem is that certain functions / operators now default to datatype TIMESTAMP in PLSQL rather than DATE. Eg-1: "declare cursor c is select nvl(sysdate,'11-JAN-99') from dual;" returns a TIMESTAMP. Eg-2: ALTER SESSION SET NLS_DATE_FORMAT = 'DD-MON-YY'; declare mydate DATE; BEGIN mydate := '12-JAN-95'; if (mydate = '12-JAN-95') then AAA else BBB end if; END; Will run BBB rather than AAA as both sides of '=' are converted to a TIMESTAMP. Workaround: Use explicit datatype casting (TO_DATE)
1142096+ A describe of a cursor obtained as a REFCURSOR by executing a definer's rights function could fail with ORA-942 or other permissions errors. This is a regression introduced in 8.1.5 which may cause upgrade problems for applications using REFCURSORS extensively.
553250 When the amount of memory to allocate for a bind buffer exceeds the maximum allowed, ORA-00600 [17176] or [733] are raised.
563584 PLS-999 may occur when: (1) a cursor selects NULL, (2) a record variable (explicit (c%rowtype) or implicit (cursor for loop)) is based on that cursor. (3) The NULL field of the record is passed as a parameter to a function. and compilation fails with PLS-00999 with "pdtptv_char_info:Problem compiling CHARSET"
696531 ORA-1002 *NOT* Being returned - commit in a fetch loop with select for update
782989 Position of the arguments from 'DESCRIBE PROCEDURE' is reversed after compile. This may also cause ORA-7445 with stack trace containing 'kqlalb'.
784046 PL/SQL does not accept the syntax function@dblink(). for parameterless calls. Local empty calls are acepted. OK: "select f() from dual;", Not OK: "select f@x() from dual;"
854842 PLS-801 or core dump can occur when a long SQL statement has single quotes at a 2k internal boundary.
897267 CREATE TABLE followed by CREATE OR REPLACE PROCEDURE / PACKAGE which references the table may dump core in ph1gla / ph1sca. This can happen if a describe of the table has been issued before executing the CREATE TABLE command. Workaround: Re-issue the CREATE or REPLACE in a new session.
944508 While a SQL statement is being issued in a LOOP inside of a PL/SQL block which has a LONG somewhere in the middle of the bind variables, if the length of the LONG was longer than 4K, the wrong address reference is sometimes used when reusing the cursor.
986962 Certain constructs in stored PL/SQL can cause the errors "ORA-6553: PLS-707: unsupported construct or internal error [2601]" after the DB has been bounced OR when the shared pool is flushed.
1034486 If you pass a CHAR actual parameter to a routine with an IN VARCHAR2 formal parameter, that parameter will behave as a CHAR-typed value in the routine. In particular, it will use CHAR (variable length, blank padded) comparison semantics when compared with a CHAR-typed value. The same problem holds with VARCHAR2 actuals and IN CHAR formals. Workaround: 1) Change the type of the formal parameter in the called function to match the type of the actual argument. 2) Assign the formal argument to a local variable of the same type inside the called routine, and use the local variable instead of the parameter. 3) Change the declaration of the formal parameter to be IN OUT rather than IN. 
1046896 A compile-time error (PLS-707) can occur when PL/SQL code calls a remote procedure with default values of parameters that call a STANDARD function. Eg: Remote procedure REMOTE_PROC(X DATE := SYSDATE) is called as BEGIN REMOTE_PROC; END; on a PLSQL client side or BEGIN REMOTE_PROC@DBLINK; END; over database link. The problem occurs if the version of "STANDARD" differs between the 2 ends of the RPC. Eg: 8.0 calls 7.3. Workaround: Use a constant default (such as NULL) and use this to indicate that a functional value (such as SYSDATE) should be used.
1063571 This fixes a regression introduced by the fix for <Bug:790632> such that access to remote variables was overly restricted by that fix. This is a CLIENT SIDE bug and can affect forms or other PLSQL based clients.
1070347 A PL/SQL procedure run in the server which alters an NLS parameter via dbms_session.set_nls() does not demonstrate the altered behavior. Only when the procedure completes, and another procedure is executed, does the altered behavior start to occur.
1073277 When a FETCH is done in a PLSQL LOOP then a second FETCH on the same cursor after the exception may dump.
1087888 PL/SQL compiler did not allow inserting into a clob or blob column with character data through a subquery, or updating a set of columns containing one or more clob or blob columns.
1114711 PL/SQL performance slower than required because NLS data structures are not cached.
1120120 A Pro/OCI client may hang or dump after a call to a PLSQL procedure which raises a user defined exception (RAISE_APPLICATION_ERROR). The hang / dump occurs when the statement is re-executed.
1125143 This bug happens during an assignment in PL/SQL. If the target has a number attribute with precision 0, then we do not need to check for precision constraint violation. This can cause an erroneous ORA-6502 error.
1140444 When index tables contained more than 255 columns an internal error is raised. This mostly affects PLSQL clients such as FORMS which try to base a forms block on a server procedure with an IN OUT parameter of a RECORD type containing more than 255 fields.
1157754 PLSQL may dump for certain SQL statements with UNIONs in inline views. Example: create table t1(n number); create table t2(n number); insert into tt(n) select n from (select 0 as n from t2 union select decode(0, 1, 0, 1) from t2);
1170095 When passing an _EXPRESSION_ as an actual parameter to a subroutine IN formal parameter, if the expression is of type CHAR and the formal parameter is VARCHAR2, or vice versa, the parameter's type is not changed to that of the actual. This results in the parameter having incorrect semantics in the called function which can result in incorrect behaviour. (We should use the semantics of the PASSED IN type)
1175540 A Dump may occur when using constructs of the form RECORD (x TAB.COL%TYPE := const) if TAB cannot be resolved to a valid table.
1182323 A procedure called "ARG" causes PLS-371, as does trying to reference objects in a schema called ARG from PLSQL.
1197218 ORA-7445 encountered when executing a PLSQL package.
1243982 Missing tablespace name etc. in error messages raised via trusted callouts.
1249760 Nested tables or VARRAYS of PL/SQL records with default attribute values initalize the table element to defaults every time an element is modified. Eg: declare type r is record(a varchar(10) := 'dflt', b number); type t is table of r; x t := t(); begin x.extend; x(1).a := 'nondflt'; /* print x(1).a here and it shows 'nondflt' */ x(1).b := 1; /* print x(1).a here and it shows 'dflt' */ end;
1261753 When a temp lob is selected from a function into a local LOB variable in a query executed in a plsql block an ORA-22922 is raised.
1287535 PROBE may not stop at a breakpoint when more than one schema is involved.
1298586 This problem was introduced in 8.1.5 A long-running session that creates a large number (>32767) PL/SQL objects (e.g., an import) may core dump while creating a PL/SQL object beyond the 32K limit. (Note this is not a size limit on individual objects but on the total number of objects created in the session) This is most likely to affect long running sessions creating lots of PLSQL objects, such as IMPORT
1300758 This problem was introduced in 8.1.6 Bulk SQL statements executed in a loop in PL/SQL programs can raise dump (eg: with ORA-7445 in <Function:pfr_v3_tab_handler> )
1301936 LOADPSP may return an ORA-6502 error when the input file exceeds 32K.
1306873 The NVL function as implemented by PL/SQL returns the wrong data type in some cases, which can result in incorrect output. Eg: NVL(varchar, number) returns NUMBER in PLSQL but should return VARCHAR2
PL/SQL (DBMS Packages) 176114 File dbmsutil.sql does not say which schema to run in. It should be run as SYS
895238 DBMS_UTILITY.COMPILE_SCHEMA can fail with ORA-1436 in 8.1 releases when any Java objects exist. This problem was introduced in Oracle 8.1.
904133 DBMS_PIPE is slower in 8.X than 7.3 (more CPU used)
968942 ORA-7445 using DBMS_SQL.BIND_VARIABLE without calling DBMS_SQL.PARSE
969814 When running DBMS_UTILITY.ANALYZE_DATABASE or ANALYZE_SCHEMA, the dictionary tables FET$ and UET$ are analyzed also.
974558 session dumps when a user is binds to a cursor which has not yet been parsed. Eg: DECLARE C INTEGER; BEGIN C := DBMS_SQL.OPEN_CURSOR; DBMS_SQL.BIND_VARIABLE(C, ':1', 'X'); END; ORA-01041: internal error. hostdef extension doesn't exist . In the fixed version, ORA-1003 ( No statement parsed ) is raised
986928 DBMS_SPACE.UNUSED_SPACE yields an internal error when issued against a temporary table (or an index on such a table). The fix is to issue an external error - ORA-3211 (since such an operation is not supported).
1099387 This problem was introduced in Oracle 7.3.4.4 / 8.0.4.0 DBMS_ALERT does not work with Parallel Server - registering an alert on any node in an OPS clusted deregisters alerts on all other nodes.
1108002 ORA-600 [25012] is signaled when DBMS_STATS tries to gather statistics for a GLOBAL TEMPORARY table.
1115720 DBMS_SQL.BIND_ARRAY processed twice as many rows as in the bound PL/SQL table for specific input table sizes (related to internally determined collection page size). Example: For DBMS_SQL.VARCHAR2_TABLE type, the size happens to be 12231; if user binds a VARCHAR2_TABLE table using DBMS_SQL.BIND_ARRAY to a DML statement, then the DML statement will be executed 24460 times (should be 12231 times).
1166931 UTL_PG.NUMBER_TO_RAW_FORMAT behaves badly for a NULL input. Results can include inconsistent return results, dump or tight CPU spin. Workaround: wrap any call to this function with a check to ensure the input is not NULL
1182131 ORA-02399 may occur when running a job if CONNECT_TIME is set to any value other than UNLIMITED.
1192012 dbms_stats.gather_schema_stats() may skip a table and not recalculate the table's statistics when the 'GATHER STALE' and 'GATHER EMPTY' options are used.
1239254 The function WRITE_RAW_DATA of the PL/SQL package UTL_SMTP is not defined in that package and the compilation of PL/SQL programs that use this function will fail.
1245019 Internal errors such as ORA-600 [19004] may occur from queries after statistics have been loaded using DBMS_STATS from a user stats table.
1288563 Using DBMS_SQL to truncate or ANALYZE a table might cause ORA-4020. 
1296682 Parallel DML (PDML) runs serial from DBMS_SQL / PLSQL EXECUTE
1326515 ORA-907 ( Missing right parenthesis ) is signalled while running DBMS_STATS.GATHER_TABLE_STATS, if any of the column names in the table has spaces e.g. "Column 1"
Dumps / Abends 936193+ A delete statement with delete cascade constraints and triggers on the table may cause ORA-7445. Stack trace usually includes 'kxtlpt()', 'kglpnp()'. 
837625 ORA-7445 may occur on all platforms when raising ORA-1. Stack trace includes 'kxccani'.
845382 An update of an updatable view, which contains a GROUP BY clause in the view definition (and hence needs an INSTEAD OF trigger) can core dump
854842 PLS-801 or core dump can occur when a long SQL statement has single quotes at a 2k internal boundary.
883002 Client executable might core dump on connect if the executable is invoked using an absolute filename that exceeds 54 characters.
887509 Unix file size limit potentially can corrupt oracle blocks if an oracle block crosses the limit boundary. File size limits are usually specfied in units of 512 byte blocks which means that an oracle block can possibly begin below the limit and end above.
1030584 INSERT INTO table AS SELECT MAX('string') FROM table can cause the server to crash if the value selected is larger than the maximum size for the target column. This also affects the functions DISTINCT() and UNIQUE(). The statement should return ORA-1401 in these cases.
1034840 If an Oracle server process is starting up at the same time the database is being shut down, it can get a core dump. There is no serious side effect from this, just errors in the alert log and trace files from the failure.
1051252 Create view "with check option" causes a core dump if at least one of base tables is a remote table
1078551 Execution of table triggers on child tables in a delete cascade statement may dump. (eg: ORA-7445)
1157654 Dump may occur in <Function:KKSFBC>
1182720 If "_push_join_union_view" is set to TRUE and a view is used which contains the same columns over and over again then the session may crash in <Function:kkoixo> Workaround: Set "_push_join_union_view" to FALSE
1226609 If a table contains a composite index which includes the primary key of the table, and there is a self referential foreign key constraint (referencing the primary key) then update of the foreign key column and a non-primary key column of the composite index can cause a dump in <Function:kxccexi>.
1257064 TKPROF may core dump when large cursor numbers are encountered and the malloc() system call does not zero memory.
1333360 Some queries that use the UNION or UNION ALL structure can core dump when parsed, if one of the UNION [ALL] branches is executed remotely.
Errors & Internal Errors 980664+ This bug was introduced in 8.1.5 If total size of all columns appearing in the Non-Distinct aggregate functions exceeds the DB block size , the sort refuses to perform comparison there-by giving (ORA-1467) error. This is correct behaviour. However, queries containing MAX() or MIN() operators can treat these as DISTINCT aggregate functions (MAX(a) is the same as MAX(DISTINCT a)). In Oracle8.1 MAX is not being converted to MAX(DISTINCT..) causing a higher likelyhood of an ORA-1467 error.
1186884+ The combination of temporary tables and temporary tablespaces could cause the server to error out or spin upon abnormal client termination. Workaround: Use PERMANENT tablespace for users TEMP tablespace when using TEMPORARY tables.
936976 Concurrent CREATE and DROP statements can cause the DBWR process to report ORA-600 [kcbcxx_1] and terminate the instance. This is due to a very small race condition.
969413 Ora-600 [16606] and / or [12819] errors can raised when the shared pool is heavily loaded. The errors indicate problems in the constraint lookup code
1010422 ORA-600[12325], [4] occurs if a view column is based on the GROUPING function and query has predicate involving this column. Eg: create view V as SELECT DECODE (GROUPING(id),1,0,id) id ....; select * from V where id=1;
1033417 64 bit platforms may raise ORA-1037 errors for queries which work fine on the same data on a 32 bit platforms. Note: Some backports of this fix to earlier releases are broken. See the alert in <Note:116764.1>
1096056 ORA-600 [17034] can occur while attempting to update a table with an invalid value (value too large for column) if the table has UPDATE TRIGGER defined. The server process may spin (appearing to hang) on disconnect.
1152302 Incorrect error message for error code ORA-3219
1155964 Incorrect position may returned when querying a view returns an error
1165009 Delete operation against a table which results in triggers being fired may ultimately fail with ORA-600 [12700] if the trigger code results in DML against the same table as the original delete and statement buffering is in effect.
1168317 ORA-4020 is possible from CREATE INDEX ... INDEXTYPE
1178821 Explain plan of a query using Star transormation with temporary tables may give ORA-1790 errors or dump core in <Function:rworirw>
1252970 Queries that perform a "top n" operation, that is, that have a subquery with an order by and a "rownum < n" clause in the outer query, sometimes fail with an ORA-600[SRDMER_1] error.
1259450 ORA-600 [kcbgtcr_13] can occur.
1270861 If a call type trigger calls a procedure as its body. and If the status of both the trigger and the procedure are "invalid" then an "alter trigger compile" signals ORA-600 [4882]. Workaround: Manually fix up and recompile the procedure, then recompile the trigger.
1273347 ORA-600 [12333] can occur
1294923 This problem was introduced in 8.1.5 Inserts into clusters or indexes may report ORA-600 [ktbgfi2] if 2 sessions try to insert into the same cluster / index block at the same time and all transaction slots in the block are already in use. This can also affect DDL statements such as DROP that update the data dictionary.
1297674 ANALYZE TABLE ESTIMATE STATISTICS can fail with ORA-600 [25012].
1301273 ALTER TABLESPACE ADD DATAFILE can fail with ORA-600 [5106] when adding more than one datafile in a single operation. There is no corruption involved, just this error. This is most likely to occur on a database which has been migrated from Oracle7 to Oracle8.
1328709 Processes can die with an ORA-600 [15428] when the shared pool is under heavy load and doing synonym translation. This is actually masking an ORA-4031 error.
Miscellaneous 601567 Column LOCK_ELEMENT_ADDR of V$LOCK_ELEMENT is incorrectly defined.
696462 DBA_KEEPSIZES does not show the size of triggers
852425 8.1 dbstart does not start up version 7.3.4 databases
889678 The length of the terminal string in the fixed view V$SESSION is only 10 characters
1059067 Selecting from v$logmnr_contents for logfiles of databases with block size > 2K may return ORA-7445 if they contain redo records corresponding to LONG data type. . Workaorund: (1) Do not select SQL_REDO and SQL_UNDO columns from v$logmnr_contents (2) If SQL_REDO and SQL_UNDO is needed, then use start_session with SCN range that does not include the offending records.
1150688 For long values of ORACLE_HOME the call stack written to trace files is broken Solaris.
1154931 The DBSTART script does not start 8.1.6 and higher instances
1175426 Running catalog.sql reports several ORA-942 errors due to incomplete schema object names within statements in the file. In particular the table names gv$dlm_traffic_controller and v$dlm_traffic_controller are split across lines.
1219425 The dbstart script does not work correctly with mixed versions (eg: 7.3.4 and 8.0) and can set LD_LIBRARY_PATH to the wrong location.
1237128 V$SESSION may contain a blank PROGRAM column due to an error passing program information during client/server logon.
1262942 The hash function used to generate the key for semaphore set allocation generates duplicates for similar ORACLE_SID/ORACLE_HOME combinations. This can cause problems when there are several databases on the same server using similar ORACLE_SIDs as if the keys are the same only one of the instances can be running at a time. Workaround: Rename the ORACLE_SID of one of the clashing instances.
1265445 The upper limit for the <Parameter:DB_BLOCK_LRU_LATCHES> is too high.
1323236 This problem was introduced in 8.0.5.2 The lock_date column in dba_users view only contains the date of account lock, not the date and time.
1337908 ORACLE_HOME/bin/relink script fails to relink utilities such as exp,imp, sqlldr, tkprof, etc. when 'relink all' was invoked. Workaround: (a) relink utilities ; (b) relink all