Oracle Text Release 11.2.0.3.0 Mandatory Patches (Doc ID 1386945.1)

Last updated on MARCH 12, 2017

Applies to:

Oracle Text - Version 11.2.0.3 to 11.2.0.3 [Release 11.2]
Information in this document applies to any platform.

Symptoms

After upgrading to 11.2.0.3.0 customers using Oracle Text could run into the following severe issues:

  1. Unable to create new indexes using Section Groups which were created pre-11.2.0.3.0 release. Trying to create an index using a section group that existed before upgrade fails with core dump

    ORA-07445: exception encountered: core dump [druhfind()+370]

    Note:
    This issue is NOT specific to FIELD sections. It can happen for all types of sections).
     

  2. You encounter a crash in function drftchkupdmdata() while calling ctx_ddl.add_mdata(), if the index in question has been upgraded from 11.2.0.2 to 11.2.0.3

  3. Oracle Text data-dictionary corruption for CTXSYS.CONTEXT index types using any section group besides NULL_SECTION_GROUP (Please note: This issue is NOT specific to FIELD sections. It can happen for all types of sections.)

    ORA-20000: Oracle Text error:
    DRG-50857: oracle error in textindexmethods.ODCIIndexInsert
    ORA-20000: Oracle Text error:
    DRG-10607: index meta data is not ready yet for queuing DML
    DRG-50857: oracle error in drdmlv
    ORA-01426: numeric overflow
    ORA-30576: ConText Option dictionary loading error
    ORA-06512: at "CTXSYS.DRUE", line 160
    ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 752

Applies to both fresh install of 11.2.0.3.0 as well as upgrade scenario (i.e. deployment was upgraded from an older release to 11.2.0.3.0) because the root causes are not related to upgrade script(s):

  1. Oracle Text data-dictionary corruption for CTXSYS.CONTEXT index type using any section group besides NULL_SECTION_GROUP (Please note: This issue is NOT specific to FIELD sections. It can happen for all types of sections). This happens only for deployments that have created a very large number of indexes or preferences (even if they have already been dropped) i.e. sequence dr_id_seq.nextval has exceeded 65535 even though the total number of indexes in the systems is not very high.
    Any operations using the index fails with following errors:

Changes

Database was upgraded to 11.2.0.3.0.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms