ORA-7445 [qmxarFindPartition] during database upgrade to 11.2 (Doc ID 1326522.1)

Last updated on FEBRUARY 07, 2013

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.2 [Release 11.2]
Information in this document applies to any platform.
***Checked for relevance on 08-Feb-2013***

Symptoms

catupgrd.sql terminates with an ORA-03113 when upgrading a 10.2.0.5 database to 11.2.0.1 or 11.2.0.2.

The upgrade.log spool file shows errors during XDB upgrade:

SQL> Rem DOCUMENT_LINKS VIEW
SQL> create or replace view XDB.DOCUMENT_LINKS
  2 (source_id,
  3 target_id,
 ...
 26 <read-properties/>
 27 <read-contents/>
 28 </privilege>')) = 1;
 xmltype('<privilege
 *
 ERROR at line 20:
 ORA-31093: null or invalid value specified for parameter : privilege

 ...

SQL> declare
  2 isCreatedBln boolean := false;
  3 roleset_ResConfig VARCHAR2(2048) :=
  4 '<ResConfig
  5 xmlns="http://xmlns.oracle.com/xdb/XDBResConfig.xsd"
  6 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 ...
 47 xmlns:rc=http://xmlns.oracle.com/xdb/XDBResConfig.xsd"')
 48 where equals_path(r.res, '/sys/xs/rolesetrc.xml') = 1;
 49 end if;
 50 end;
 51 /
 declare
 *
 ERROR at line 1:
 ORA-03113: end-of-file on communication channel
 ERROR:
 ORA-03114: not connected to ORACLE

 SP2-1519: Unable to write to the error log table sys.registry$error
 Process ID: 3617
 Session ID: 191 Serial number: 3


The alert.log shows an internal error, ORA-7445 [qmxarFindPartition], was generated during the upgrade:

Mon May 30 11:55:50 2011
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x1FFFFFFC8] [PC:0x40000000122EA531, qmxarFindPartition()+113] [flags: 0x0, count: 1]
Errors in file /usr1/apl/ora11202/admin/diag/rdbms/mydb/MYDB/trace/MRDWDEV_ora_3617.trc (incident=3756):
ORA-07445: exception encountered: core dump [qmxarFindPartition()+113] [SIGSEGV] [ADDR:0x1FFFFFFC8] [PC:0x40000000122EA531] [Address not mapped to object] []
Incident details in: /usr1/apl/ora11202/admin/diag/rdbms/mydb/MYDB/incident/incdir_3756/MYDB_ora_3617_i3756.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.


Running dbms_metadata.get_ddl for XDB.XDB$PROPNUM_SEQ on the database shows that its start value is > 65,535:

SQL> set long 99999
SQL> select dbms_metadata.get_ddl('SEQUENCE', 'XDB$PROPNUM_SEQ' , 'XDB')
  2 from dual;

DBMS_METADATA.GET_DDL('SEQUENCE','XDB$PROPNUM_SEQ','XDB')
--------------------------------------------------------------------------------
CREATE SEQUENCE "XDB"."XDB$PROPNUM_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 264253 CACHE 20 NOORDER NOCYCLE

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