Introduction to "Bug Description" Articles [ID 245840.1]

This is a customer overview of the "Bug Description" documents which can be seen in My Oracle.

What are "Bug Description" Articles ?

Each article is a placeholder note for a summary description of a bug (defect) in an Oracle product. The articles give the following summary information on an individual bug:
  • Affects - Product version/s affected
  • Fixed - Product version/s where the bug is fixed
  • Symptoms - Key symptoms of the bug
  • Related To - Key features / product areas / parameters / views etc.. which the issue is related to
  • Description - A short description of the problem, sometimes including an example and/or a workaround
Many of the articles will show very little information against the description of the problem but may still be useful as they show which versions are likely to be affected and can give some idea of the impact of the bug.

IMPORTANT:

These short articles will not usually give enough information to identify that you are hitting, or may hit, a specific issue. Always check with Oracle Support if a particular issue is of interest. Also please note that some of the workarounds given may be very specific, or may have side effects. Again contact Oracle Support for information about any particular bug.

Please note that not all bugs have a bug description present. The aim is to have a description for all customer related bugs which appear in RDBMS Patch Sets. Other products do not have these summaries present.

Affects

This section shows the product that the bug is reported against, the range of version believed to be affected, the versions which are confirmed as being affected and details of the platforms affected. If the issue is believed to be a
regressionthan that is indicated also.

Product (Component)

The product / component shows the code area that the bug is filed against. In some cases the tools affected may differ from the actual code area where the fix occurs. Eg: An Oracle Server (CORE) fix may only show up as an Export / Import issue. You are advised to see the "Related To" section of the bug description for features / products believed to be affected.

Versions believed to be affected

Oracle does not test every version of a product for a given bug. When a bug is reported it is typically tested against the version it is reported in and the latest version. The values here give an idea of the range of versions the bug is believed to affect.

Versions confirmed as affected

These are versions where the bug is known to reproduce.

Platforms affected

If the bug is specific to certain platforms this is indicated here. If the bug is "Generic" this is shown. A generic bug is one which affects all or most platforms, although the exact symptoms and chance of hitting the bug may differ between platforms. eg: Some bugs may affect only big or little endian platforms but the bug itself is marked as generic if the issue is in code which is common to all platforms.

Regressions

A regression is a problem which is introduced in a particular release but does not affect the default behaviour in lower releases. Hence it is something to watch out for if upgrading. Problems with new features are NOT considered as regressions unless the feature is enabled by default in the new release and it is not obviously controlled by some compatibility related parameter. The most serious regressions are those introduced by application of a Patch Set.

Changes in behaviour

Some bug fixes intentionally introduce a change in documented behaviour. Ideally such changes should be protected by some event or parameter to allow them to be turned off but this is not always the case.

More Information about Versions Affected

Patch Set Update
Consider using any workaround if given. It may be possible to get an interim patch if the issue has serious enough impact and business justification. Current Patch Set.
Consider using any workaround if given. It may be possible to get an interim patch. Patch Set Update
Consider using any workaround if given. It may be possible to get an interim patch if the issue has serious enough impact and business justification. First 11.2 Patch Set.
Consider using any workaround if given. It may be possible to get an interim patch. Patch Set Update
Consider using any workaround if given. Interim patches are no longer created for 11.2.0.1 releases, including PSU versions. Current Base release.
Consider using the current patch set (11.2.0.3) or any workaround if given. Interim patches are no longer created for this release. Patch Set Update
Consider using any workaround if given. It may be possible to get an interim patch if the issue has serious enough impact and business justification. Current Patch Set.
Consider using any workaround if given. It may be possible to get an interim patch. Current Base release
Consider using the current patch set or any workaround if given. Interim patches are no longer created for this release. Patch Set Update
Consider using any workaround if given. It may be possible to get an interim patch if the issue has serious enough impact and business justification. Current Patch Set.
Consider using any workaround if given. If you have purchased Extended Support then it may be possible to get an interim patch if the issue has serious enough impact and business justification. Patch Set Update
Consider using latest patch set or any workaround if given. Interim patches are no longer created for these releases except for specific platforms where noted in the support policy. Consider using latest patch set or any workaround if given. Interim patches are no longer created for this release except for specific platforms where noted in the support policy. Consider using latest patch set or any workaround if given. Interim patches are no longer created for this release. Consider using latest patch set. Interim patches are no longer created for this release. Current Patch Set.
Consider using 10.2 or 11g or any workaround if given. If you have purchased Extended Support then it may be possible to get an interim patch if the issue has serious enough impact and business justification. Consider using latest patch set (10.1.0.5) or 10.2 or 11g. Interim patches are no longer created for this release. Terminal Patch Set.
Consider using 10g or 11g or any workaround if given. If you have purchased Extended Support then it may be possible to get an interim patch if the issue has serious enough impact and business justification. Consider using a newer release or any workaround. Interim patches are no longer created for these releases.
The support status of various releases can be seen in Consider using a newer release or any workaround. Interim patches are no longer created for these releases.
The support status of various releases can be seen in

Fixed

This lists the releases where the bug has been fixed.
Interim / one-off patches are NOT listed in this section. You can search the "Patches" section of My Oracle using the bug number to check for one-off / interim emergency patch availability.
Note that if an issue is listed as fixed in a particular patch set then the fix should also be included in all subsequent Patch Sets for that release. Eg: If a bug is listed as fixed in 9.2.0.3 then the fix will also be included in the 9.2.0.4 Patch Set. It is advisable always to use the latest Patch Set rather than a specific patch set version.

Fixed in version Release InformationThis fix has not been included in any full database release nor any Patch Set and is only available as an interim (one off) patch. Typically such issues are addressed in some other manner in a later release and so the fix is not applicable to versions other than those detailed in the bug description. The issue may be fixed at some point in the future but the fix may be done under some other bug number or even under some separate project. This is just a marker version for a future version of Oracle. There is currently no such version. A fixed of 12.1 just means that the issue has been fixed in the current development code line. See for details of Patch Set Updates (PSU).
See for details of fixes in each 11.2.0.3 PSU See See for details of Patch Set Updates (PSU).
See for details of fixes in each 11.2.0.2 PSU See See for details of Patch Set Updates (PSU).
See for details of fixes in each 11.2.0.1 PSU See See for details of Patch Set Updates (PSU).
See for details of fixes in each 11.1.0.7 PSU See See See for details of Patch Set Updates (PSU).
See for details of fixes in each 10.2.0.5 PSU See See for details of Patch Set Updates (PSU).
See for details of fixes in each 10.2.0.4 PSU
Note that 10.2.0.4.5 onwards PSU are supplied as an overlay patch which must be applied on top of the 10.2.0.4.4 Patch Set Update. See for details of Patch Set Updates (PSU).
See for details of fixes in each 10.2.0.4 PSU See See See See See See See See See These are old 9.2 releases. It is advisable to use 9.2.0.8 or a newer release such as 10g or 11g. Summary 9.2 information can be seen in These are old 9i releases. It is advisable to use a newer release such as 10g or 11g. Summary 9.0 information can be seen in These releases are no longer supported for error correction. A summary of releases and they current status can be seen in

Note: If a release is shown as "does not exist yet" then this indicates a planned future base release or Patch Set. A patch set or base release with the indicated version is expected to be released at some time in the future but this is not a guarantee that there will be such a release - plans are subject to change.

Symptom

Code Improvement

The code fix in this bug is considered as an enhancement. This may be as simple as enhanced diagnostics or may be a small enhancement to functionality.

Corrupt/Bad Backup

The problem can result in a bad backup being produced, such that restore from that backup may be impossible or not restore data to be the same as it was at the time of the backup.

Corruption

A corruption issue which does not fit into one of the corruption issues below.

Corruption (Corrupt Export)

The export file produced is corrupt in some form. This may make the export totally unusable, or it may only affect a small part of the export file.

Corruption (Dictionary)

The Oracle data dictionary can end up containing incorrect or inconsistent data. Sometimes such issues can be repaired with the help of Oracle Support, and sometimes it requires the database to be rebuilt or restored. Never attempt to repair dictionary corruptions by yourself. Doing so can make your database unsupportable.

Corruption (Incorrect / Missing Corruption Checks)

Either a false corruption error is reported or code which checks for corrupt blocks / data is incorrect and may not notice that bad data really is corrupt.

Corruption (Index)

This issue can cause an index / table data mismatch where the problem can typically be resolved by rebuilding the index.
Note: When an index is built / rebuilt is may be built based on data in the corrupt index itself. Hence it is very important to drop ALL corrupt indexes before recreating them.

Corruption (Logical)

This issue can cause logical corruption to data. This category is typically used where data itself can get corrupted but the underlying table structure is intact.
Eg: "DBVERIFY" or "ANALYZE VALIDATE" may not report any problems for any table affected.

This category is closely related to

Wrong Results in that wrong results issues can cause logical corruption if used to update data or take decisions. The "Corruption" category is typically used where the corrupt data is persistent (stored).

Corruption (Physical)

This issue can cause physical corruption. Physical corruption is typically taken to mean that the underlying structure of datablocks or files can be corrupted.
Eg: "DBVERIFY" or "ANALYZE VALIDATE" is likely to report a problem.

Deadlock

This issue can either lead to a deadlock scenario, or a deadlock situation may go unnoticed. In some cases a false deadlock may be reported.

Diagnostic Output Problem / Improvement

Diagnostic output relates to output in Oracle trace files etc.. used by Oracle Support to diagnose a problem. The diagnostic information may not be sufficiently detailed, or may contain incorrect , misleading or incomplete output. This sort of issue does not normally affect normal day to day running of a database but can hamper diagnosis when things go wrong.

Error May Occur

The issue causes an unexpected or incorrect error to be reported. Details of the actual error/s appear in the description of the bug.

Excessive CPU Usage

This issue can cause high CPU usage but is not typically a spin scenario - just excessive CPU use. For CPU spinning issues see
Hang / Spin.

Feature Unusable

This bug makes a particular feature unusable.

Hang (Involving Shared Resource)

A process may hold a shared resource a lot longer than normally expected leading to many other processes having to wait for that resource. Such a resource could be a lock, a library cache pin, a latch etc.. The overall symptom is that typically numerous processes all appear to be stuck, although some processes may continue unhindered if they do not need the blocked resource.

Hang (Process Hang)

A process may hang, typically in a wait state. Note that this is different to a process which is spinning and consuming CPU.

Hang (Process Spins)

A process enters a tight CPU loop so appears to hang but is actually consuming CPU.

Install/Patching Is Not Performed Correctly

Installation or patching of a product or option is not performed correctly.
eg: Files may be missing or permissions changed incorrectly.

Instance May Crash

This issue can cause an instance to crash.

Internal Error May Occur (ORA-600)

An internal error (ORA-600) may occur. Details of the actual error/s appear in the description of the bug.

Latch Contention

This issue can result in latch contention within the database.

Leak (Memory Leak / Growth)

Memory is continually consumed appearing as a memory leak. Some memory leaks are not "true" leaks in that the memory may be freed up when a long running operation completes but the issue is still marked as a leak if the operation should run without the memory growth.

Leak (Resources Eg: File Handles)

The issue leaks some form. of resource (other than memory or CPU).
Examples are cursor leaks , file handle leaks etc...

Memory Corruption

This issue can result in memory corruption. Memory corruptions can have side effects of signalling unexpected errors, unexpected internal errors or can even produce incorrect results depending on how the memory gets corrupted. The text description of the bug usually indicates if the issue affects private or shared memory and whether the issue is a client or server side memory corruption issue.

Mutex Contention

Mutex contention may be seen. Typically mutex contention is focused around specific objects or SQL statements . As mutexes can use very tight loops with only a yield of the CPU between iterations then mutex contention may often be accompanied by increased CPU usage.

Optimizer Bad Cardinality

The optimizer estimates a bad cardinality when evaluating the best execution plan. This can typically lead to a suboptimal execution plan being chosen as the cost computation are based on bad estimates.

Parsing SQL is expensive / slow

This issue can cause parsing of a SQL statement to take excessive resource and time. In this context "parsing" includes time taken in the optimizer to choose the best plan for a statement. If a SQL statement takes a long time or a lot of resource during the parse / optimize operations this can cause waits in other sessions wanting to execute the same SQL statement.

One can typically help the optimizer portion of parse time by use of hints or outlines to reduce the number of options that the optimizer has to consider.

Performance Affected (General)

The issue can affect performance generally.

Performance Of Certain Operations Affected

Performance of specific operations may be affected.

Performance Of Query/ies Affected

Query performance is affected. This may be due to a poor execution plan or due to un-necessary operations to execute the query.

Process May Dump (ORA-7445) / Abend / Abort

The process may die unexpectedly. More details on the likely functions or error at the time of the dump should appear in the bug description.

Security Or Service Denial Vulnerability

This issue is either a security loophole or a vulnerability to denial of service attacks. Such issues are typically either alerted and/or are included in Oracle Critical Patch Updates .

Shared Pool Affected

The shared pool may be affected. Issues which affect the shared pool may lead to wider problems for other users such as ORA-4031 errors, very slow performance, increased CPU etc..

Storage Space Usage Affected

The amount of space used for the storage of database objects is affected by this issue. Typically more space than expected is used. Note that this relates to the "on disk" storage space in the database and not to memory space used.

Unstable Execution Plan

This issue can cause an execution plan for a statement to change suddenly. ie: The plan is not stable and the SQL may execute quickly sometimes and poorly at other times.

Unwanted or Excess Trace / Alert messages

This issue can cause unwanted tracefiles , tracefile content, alert log entries or other extraneous output which might be considered a nuisance. Such files / entries can typically be deleted at regular intervals but be careful not to also remove useful trace / output.

Wrong Results

This bug can cause wrong results to be returned. If the source of the wrong results is used in any form. of data update or decision this issue could lead to permanent logical corruption.

Wrong/Bad Shared Cursor

A wrong version of a shared cursor may be used. eg: A wrong child cursor may be used. This sort of problem can show as strange errors (such as ORA-942) or can lead to logically incorrect behaviour, such as accessing data from tables in the wrong schema.

HCHECK script. reports this corruption

"hcheck.sql" is a custom script. available in
Note:136697.1which can be executed to help check for potential DB data dictionary inconsistencies. The script. specifically includes checks for dictionary inconsistencies that could be caused by this bug and reports any found with an HCKE-nnnn or HCKW-nnnn message.

Task Related

Instance Startup

This issue can occur when attempting to start a database or ASM instance.

Migration / Upgrade / Downgrade

This issue can affect upgrade, downgrade or migration of a database between releases.

Performance Monitoring

Performance monitoring may be affected.
eg: performance monitoring views may not show correct information to identify a problem.

Recovery

Issues which affect database recovery operations of some form.

SQL Commands / Features Used

Adaptive Cursor Sharing

This issue is related to the Adaptive Cursor Sharing functionality introduced in 11g. See
Note:836256.1 for details of this feature.

Analytic SQL (Windowing etc..)

Relates to the use of analytic SQL constructs such as the windowing functions.

ANSI Joins

Relates to the use of ANSI joins. Often a workaround for problems with ANSI SQL is to recode the SQL to Oracle conventional format.

Application Context

Relates to the use of application context. eg: the use of SYS_CONTEXT()

Connect By / Hierarchical Queries

This issue affects SQL which uses the "CONNECT BY" SQL clause.

Constraint Related

This issue is related to the use of constraints. The description should clarify which kinds of contraint the problem may relate to. eg: CHECK constraints, use of Foreign key constraints etc..

Datatypes (AnyData)

Relates to the use of the ANYDATA datatype

Datatypes (LOBs/CLOB/BLOB/BFILE)

Relates to one of the large object (LOB) datatypes such as CLOB, BLOB or BFILE.

Datatypes (Objects/Types/Collections)

Relates to object data types such as TYPEs or collections.

Datatypes (Special Datatypes)

Special datatypes which are only available in Oracle8 onwards.

Datatypes (TIMESTAMP)

Relates to use of the TIMESTAMP datatype, or timezone data as used for timestamp datatypes.

Direct Path Operations

Direct path operations may be affected. Direct path operations can occur in various places. eg: INSERT /*+APPEND*/ type operations use direct path access at SQL level, whilst direct path SQL Load and direct path OCI APIs can also use this form. of data access. For issues affecting direct path operations a workaround can often be to use the equivalent non-direct path option.

Expression Filters / Rules

This issue relates to the use of rules / expression filters. eg: As created by DBMS_RLMGR

Global Temporary Tables

Can affect the use of global temporary tables.

Globalization Support (NLS)

Related to the use of NLS (Globalization support).

Hash Join

A HASH Join is a specific form. of join of row sources. This issue relates to this specific join method. Hash joins can typically be disabled and other join methods used.

Literal Replacement (CURSOR_SHARING)

This issue relates to the use of literal replacement , which is used when the parameteer CURSOR_SHARING is set to either SIMILAR or FORCE. A workaround for such issues is to disable literal replacement by setting CURSOR_SHARING=EXACT for any problem statement, although this can then result in increased load on the shared pool in systems with high concurrency.

Merge SQL (MERGE .. USING)

Relates to use of the MERGE SQL statement.

Multi Table Insert SQL

Relates to the use of Multi table insert statements.

Online DDL

Relates to the use of ONLINE DDL operations. Often a workaround for such issues is to use the non-online equivalent, although that may then need an short outage to allow the operation to run.

Optimizer

This problem is related to the SQL optimizer which determines the execution plan for a given SQL statement.

Optimizer (Bind Peeking)

Relates specifically to the use of bind peeking by the Cost Based Optimizer.

Optimizer (SQL Plan Management)

This issue affects, or is related to, the use of the SQL Plan Management (SPM) feature within Oracle which was introduced in Oracle 11g. SQL Plan Management (SPM) is intended to allow controlled plan evolution by only using a new plan after it has been verified to be perform. better than the current plan. The feature is typically controlled via: See the "Performance Tuning Guide" for more details of this feature.

Optimizer (Stored Outlines)

Relates to the use of stored outlines.

Optimizer (Subquery Factoring - WITH clause)

Relates to the use of WITH clauses within SQL statements. Most statements which use a WITH clause can be recoded into equivalent SQL which does not use the WITH clause.

Parallel Query (Auto DOP)

Parallel query automatic degree of parallelism (Auto DOP) is a Parallel Query feature introduced in 11.2 which is enabled when the parameter PARALLEL_DEGREE_POLICY=AUTO .
If you encounter problems with this feature it can be disabled by setting PARALLEL_DEGREE_POLICY to MANUAL .

Parallel Query (PQO)

Relates to the use of Parallel Query or Parallel DML. A workaround for such issues may be to run the statement serially.

Query Rewrite (Including Materialized Views)

Relates to the use of materialized views / snapshots and / or query rewrite.

Regular Expressions

Related to the use of Regular expressions. eg: the REGEXP_LIKE operator

Result Cache

This issue affects, or is related to, the use of the Result Cache feature within Oracle which was introduced in Oracle 11g. When the result cache is enabled then a query execution plan may include a RESULT CACHE node in the plan. When such a query executes the database looks in the cache memory to determine whether the result exists in the cache. If the result exists, then the database retrieves the result from memory instead of executing the query. If the result is not cached, then the database executes the query, returns the result as output, and stores the result in the result cache.

The result cache can be controlled by the following:

The /*+ RESULT_CACHE */ or /*+ NO_RESULT_CACHE */ hintsSee the "Performance Tuning Guide" for more details of this feature.

Securefiles

Relates to the use of Secure File LOBS. Often a workaround may be to use the equivalent BASICFILE lob.

Star Transformation

Relates to using STAR transformation in SQL statements. Sometimes such issues can be avoided by disabling star transformation for the problem SQL.
eg: Set STAR_TRANSFORMATION_ENABLED=FALSE

Star Transformation With Temp. Tables

Relates to using STAR temporary table transformations. Often such issues can be avoided by using STAR transformation but without the temp table transformation.
eg: Set STAR_TRANSFORMATION_ENABLED=TEMP_DISABLE

Triggers

Relates to the use of TRIGGERs.

Truncate

Relates to use of the TRUNCATE SQL statement.

Virtual Columns

This issue is related to the use of Virtual Columns. A virtual column is a column that is not stored on disk but has a queryable value which is the result of some expression.

Virtual columns may be defined explicitly in the table definition or may be used implicitly by some SQL operations (such as when a function based index is defined or used).

How Things Are Stored / Defined

ASSM Space Management (Bitmap Managed Segments)

Relates to the use of ASSM segments. eg: SEGMENT SPACE MANAGEMENT AUTO

Automatic Storage Management (ASM)

Relates to ASM storage or instances.

BIGFILE Tablespaces

Relates to BIGFILE tablespaces.

Bitmap Indexes

Relates to the use of bitmap indexes.

Compressed Data Storage

Relates to the use of compressed data storage in tables.
ie: Use of the COMPRESS keyword on the table itself.
Note that this is differnt to compressed key storage in indexes / IOTs.

Compressed Key Index / IOT

Relates to the use of COMPRESS KEY indexes or IOTs.

Domain Indexes

Relates to domain indexes in general.

External Tables

Relates to the use of External Tables.

Function Based Index (Including DESC Indexes)

Relates to the use of function based indexes, including DESC indexes.

Index Organized Tables (IOT)

Relates to the use of Index Only Tables. ie: Created with ORGANIZATION INDEX

Oracle Disk Manager

Relates to use of Oracle Disk Manager

Partition Views (PV)

Relates to the use of partition views.

Partitioned Tables

Relates to use of partitioned or composite partitioned tables.

Read Only Tablespace/s

Relates to the use of read only tablespaces. eg: ALTER TABLESPACE READ ONLY

Space Management

Relates to dictionary based space management .

Space Management (Locally Managed Tablespaces)

Relates to space management within locally managed tablespaces. ie: Tablespaces created with "EXTENT MANAGEMENT LOCAL"

System Managed Undo (SMU)

Relates to the use of System Managed Undo (SMU). ie: As is used when UNDO_MANAGEMENT is set to AUTO.

Transparent Data Encryption

Related to the use of Transparent Data Encryption (TDE).

Net / Connectivity / Authentication / Distributed

Advanced / Secure Networking

This issue is related to Advanced or Secure Networking. Such issues may relate to a specific encryption or advanced Net feature.
eg: The use of a specific secure network protocol such as Kerberos or SSL etc..

Database Link / Distributed

The issue is related to the use of a database link between Oracle databases. Note that this does NOT include database links to Heterogenious Services / Gateways but only those between Oracle instances.

Gateways / Heterogeneous Services

Related to the use of Oracle Gateways / Heterogeneous Services generally (as opposed to a specific gateway / HS service)

Gateways / MGW Message Gateway

Related specifically to the MGW Message Gateway.

Gateways / ODBC

Related specifically to the ODBC Gateway

Gateways / Procedural Gateway For APPC

Related specifically to the Procedural Gateway For APPC

Gateways / Procedural Gateway For MQ Series

Related specifically to the Procedural Gateway For MQ Series

Gateways / Transparent Gateway For DRDA

Related specifically to the Transparent Gateway For DRDA

Gateways / Transparent Gateway For Informix

Related specifically to the Transparent Gateway For Informix

Gateways / Transparent Gateway For SQL Server

Related specifically to the Transparent Gateway For SQL Server

Interoperability (Between Releases)

Related to interoperability between different Oracle versions.

Network

Related to the Net layer of communication between processes.

Network (Connection Manager)

Related to the use of Connection Manager (CMAN).

Oracle Data Providedr for .NET (ODP)

Related to Oracle Data Providedr for .NET (ODP)

Oracle Names

Related to the use of Oracle Names.

Security ( Authentication / Privileges / Auditing )

This issue relates to auditing , authentication or privileges used in the database.

Transparent Application Failover

This issue is related to Transparent Application Failover (TAF) . This is a feature of the client that enables an application to automatically reconnect to a database if the database instance to which the connection is made fails.
See
Note:453293.1 for more details of TAF.

XA / Distributed Transactions

Database Options / Major Features

Active Dataguard (ADG)

This issue is related to Active Data Guard.
See
Note:1101938.1 for information about Data Guard.

Advanced Queuing

This issue relates to use of the Advanced Queue features in the Oracle database.

Automatic Memory Management

This issue relates to use of the Automatic Memory Management feature of Oracle.
eg: As used when MEMORY_TARGET parameter is used .
Problems in this area can often be avoided by manually configuring memory for the database.

Change Data Capture

This issue relates to use of Change Data Capture features.

Database File System (DBFS)

This issue relates to use of Database File System (DBFS), including the DBFS client.

Editions

This issue relates to the use of Oracle Editions which allows editioned objects to be used. See the documentation for details of Oracle Editions.

Flashback

This issues relates to some Flashback feature/s in the database.
See
Note:1138253.1 for details of the flashback features.

Flashback Data Archive (Oracle Total Recall)

This issue relates to use of the Flashback Data Archive feature.
See
Note:470199.1 for details of this feature.

JavaVM / JSP / Corba etc..

This issue relates to the use of stored Java in the database. Note that this is separate from general JDBC and Java issues outside of the database.

Job Queues

This issue relates to the use of job queues or the Database job scheduler options in the database, including DBMS_JOB and DBMS_SCHEDULER pacakges.

LogMiner

This issues relates to the use of LogMiner, particularly adhoc LogMiner for manually mining redo. Note that issues in LogMiner can also affect other options which use the LogMiner code, such as Streams and Logical Standby.

Multimedia (Formerly interMedia) (Image)

This issue relates to use of Oracle Multimedia for handling Images.
See
Note:1078222.1 for details of Multimedia options.

Multimedia (Formerly interMedia) (Video)

This issue relates to use of Oracle Multimedia for handling Video.
See
Note:1078222.1 for details of Multimedia options.

Oracle Data Vault

This issue relates to use of Oracle Data Vault.

Oracle Database Smart Flash Cache

This issue relates to use of Oracle Smart Flash Cache.
For more details of Database Smart Flash Cache see the 11.2 documentation.

Oracle Label Security

This issue is related to the use of Oracle Label Security in the database.

Oracle OLAP

This issue is related to the Oracle OLAP product.

Oracle Text (Formerly interMedia Text)

This issue relates to use of Oracle Text which allows text indexing of table content within the database .
See
Note:1087143.1 for details of Oracle Text.

Oracle Text Filters

This issue relates specifically to use of the Text filters within Oracle Text . The filters allow non-ascii documents to be text indexed.
See
Note:1087143.1 for details of Oracle Text, including links to supported document formats and filters.

Physical Standby Database / Dataguard

This issues is related to Standby databases, either manually configured or part of a Data Guard configuration.
See
Note:1101938.1 for information about Data Guard.

RAC (Real Application Clusters) / OPS

This issue is related to the use of RAC , or for older releases is related to the use of Parallel Server.

Read Only Database

This issue is related to a database opened in READ ONLY mode.

Recycle Bin

This issue is related to the Recycle Bin in the database.

Replication

This issue is related to the use of Advanced Replication in the database.

Resource Manager

Row Level Security / FGA

This issue is related to the use of Row Level Security (RLS) or Fine Grain Auditing (FGA) against tables / views in the database.

Shared Server (formerly MTS)

This issue relates to the use of shared servers in the database. Often one can avoid problems with shared servers by using dedicated connections instead.

Spatial Data

This issue is related to the Oracle Spatial product.

Spatial RTREE

This issue is related specifically to the use of Spatial RTREE indexes.

Streams / Logical Standby

This issue is related to the use of Streams and/or Logical Standby. Such issues can affect any product / feature built on top of the Streams architecture.

Supplemental Logging

This issue affects, or is related to, the use of the Supplemental Logging. When enabled Supplemental Logging logs additional data into the redo stream - such data is typically need for redo-based applications such as LogMiner, Streams, Logical Standby etc.. An issue which affects supplemental logging can have downstream effects on these other features.

Transportable Tablespaces

This issue is related to the use of transportable tablespaces. It may be directly related to the transport operation, or may be some effect seen later in time which relates to transported data.

Trusted Oracle

This issue relates to the use of Trusted Oracle.

Workload repository / reporting

This issue relates to use of the workload repository or related reporting features.

XDB

This issue relates to the use of Oracle XML DB .

Programming Languages

JDBC

This issue relates to the use of JDBC .

NCOMP

This issues relates to the use of the NCOMP Native Compilation option for PLSQL. Such issues can typically be avoided by not "ncomp"ing the code.

OCCI

This issue is related to OCCI clients.

OCI

This issue is related to the use of the Oracle Call Interface on the client side. Such issues can affect various clients which use OCI to interface to the database. eg: OCI issues can affect pre-compiler based clients, client SQLPLUS etc..

ODBC Driver

This issue is related to use of the Oracle ODBC driver.

PL/SQL

This issue is related to the use of PL/SQL.

PL/SQL (DBMS Packages)

This issue affects the use of certain packages in the database. The actual packages affected will typically be listed in the bug description note.

PL/SQL External Procedures (EXTPROC)

This issue affects the use of PLSQL External procedures as can be executed by the "extproc" process from PLSQL.

Pro* Precompiler

This issue is related to the use of one of the Precompilers.

SQLJ

This issues is related to the use of SQLJ

XDK

This issues affects the Oracle XDK .

XML

This issue is related to the processing of XML data.

Product Related

Advanced Clustered File System

This issue realtes to Oracle Automatic Storage Management Cluster File System (Oracle ACFS). This is a multi-platform. file system and storage management technology that extends Oracle Automatic Storage Management (Oracle ASM) functionality to support customer files maintained outside of the Oracle Database. See the "Automatic Storage Management Administrator's Guide" for more information.

Automatic Diagnostic Repository

This issue relates to the Automatic Diagnostic Repository introduced in Oracle 11g. The Automatic Diagnostic Repository (ADR) is a file-based repository that stores database diagnostic data such as trace files, the alert log, and Health Monitor reports. Key characteristics of ADR include: Unified directory structure Consistent diagnostic data formats Unified tool setSee the documentation for further details.

Cluster Ready Services / Parallel Server Management

This issue relates to the Cluster Ready Services / Parallel Server Management / Grid Infrastructure elements of Oracle as used in as RAC environment.

Database Configuration Assistant

This issue relates to use of the Oracle Database Configuration Assistant (DBCA). Often one can use manual steps to perform. the same task as DBCA.

Database Replay

This issue relates to use of Database Replay .

Database Upgrade Assistant

This issue relates to use of the Oracle Database Upgrade Assistant (DBUA). Often one can use manual steps to perform. the same task as DBUA.

Datapump Export/Import

This issues relates to the use of the Datapump Export / Import utilities of the Oracle Database. ie: The "expdp" and/or "impdp" executables.
Note that this is different to conventional Export / Import which it replaces.
In some cases a workaround to Datapump export / import issues can be to use conventional export / import.

DBVerify Utility

This issues relates to the DBVERIFY (DBV) utility used to check the consistency of database files.
See
Note:35512.1 for details of the DBVERIFY utility.

Exadata

This issues is related to the use of Oracle Database Machine (Exadata).

Export/Import

This issues relates to the use of the conventional Export / Import utilities of the Oracle Database. ie: The "exp" and/or "imp" executables.
Note that this is different to Datapump Export / Import which replaces conventional export / import .
In some cases a workaround to conventional export / import issues can be to use Datapump export / import.

FailSafe

This issues is related to use of the Oracle Failsafe product (OPFS)

Intelligent Agent

This issue relates to the Intelligent Agent process.

J-Publisher

This issues relates to use of the J-Publisher product.

LDAP / Oracle Internet Directory

This issue is related to the use of LDAP features in the database, inclusing the use of Oracle Internet Directory from the database. This includes the DBMS_LDAP package and the use of Enterprise Users configured in OID.

Net Configuration Assistant

This issue is related to the use of the Net Configuration Assistant.

OLEDB

This issue relates to the OLEDB product.

Oracle Administration Assistant

This issue is related to the use of the Oracle Administration Assistant

Oracle COM Automation

This issue relates to use of Oracle COM Automation

Oracle Counters for Windows Performance Monitor

This issue relates to the Oracle Counters for Windows Performance Monitor product.

Oracle Data Mining

This issue relates to the use of Oracle Data Mining.
See
Note:1087643.1 for details of this feature.

Oracle Enterprise Manager

This issue affect Enterprise Manager .

Oracle Lite

This issue relates to the Oracle Lite product.

Oracle ONS

This issue relates Oracle ONS

Oracle Type Translator

This issue relates to use of Oracle Type Translator

Oracle Univeral Installer

This issue relates to use of Oracle Universal Installer product. Note that this is different to an issue where an install / patch operation is not performed correctly.

Portal (MOD_PLSQL)

This issue is related to the use of MOD_PLSQL in the database.

RMAN (Recovery Manager)

This issue relates to use of Recovery Manager (RMAN).
See
Note:1116484.1 for details of RMAN.

Spatial / Spatial Advisor

This issue relates to use of Spatial Advisor

SQL*Loader

This issue is related to the use of SQLLOADER utility.

SQL*Plus

This issue relates to use of the SQLPLUS client.

Ultra Search

This issue is related to the use of Oracle UltraSearch.

Wallet Manager

This issue relates to use of Wallets in Oracle, and especially to issues with Oracle Wallet Manager itself..

Workspace Manager

This issue relates to the use of Oracle Workspace Manager.

Miscellaneous

Critical Patch Update molecule

This bug# is a special marker bug for a molecule in a Critical Patch Update. Refer to the relevant Critical Patch Update documentation for details of what security issues the molecule addresses.
See
Note:467881.1 for details of the latest Critical Patch Update.

Fine Grained Dependencies

From 11g the Oracle database records more detailed information about dependencies between objects. For example if table T has columns C1, C2 and C3 but view V selects only columns C1 and C2 then adding a fourth column C4 to T or changing the definition of C3 has no need to invalidate the view. Prior to 11g any change to T would cause V to be invalidated. From 11g, only changes that affect the parts of T that V depends on will cause V to be invalidated. Similar fine grained dependency checking applies to other types of objects too, especially PL/SQL library units, and is known as fast validation.

If you have problems with Fine Grained Dependencies see help notes in

Note:1061696.1 under "11g and Fine Grained Dependency Checking"

Large File / Memory Issues (Eg: 2Gb)

This issue relates to number boundary issues such as 2Gb limits for filesize, memory size etc..

NUMA Related

This issue is related to the use of NUMA features within the Oracle database.

Year 2000 / Date limit Issues

This issues is related to data limits, particularly year 2000 issues.

Miscellaneous

Description

This is a brief description of the bug itself, including any workaround if known. Sometimes this will be very short such as "A dump can occur in XXXXX" and sometimes this will include a good description with an example. Any workaround should be treated with caution. Any hidden parameters or events mentioned should not be used unless clarified with Oracle Support.

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/17252115/viewspace-740828/,如需转载,请注明出处,否则将追究法律责任。

转载于:http://blog.itpub.net/17252115/viewspace-740828/

你可能感兴趣的