My Oracle Support Banner

CTXCRIND.SQL Fails With ORA-3113 Errors and ORA-7445 In lxscop() (Doc ID 554981.1)

Last updated on MARCH 08, 2017

Applies to:

Portal - Version to [Release 10gR2]
Information in this document applies to any platform.
Checked for relevance on 17-Feb-2015


The script ctxcrind.sql and logctxcrind.sql fail with ORA-3114 and ORA-3113 errors when creating the index wwsbr_url_ctx_indx :

SQL> @logcrind ctxindex
Creating Context Preferences and Indexes...

PL/SQL procedure successfully completed.

old   5:     p_logfile    varchar2(100) := '&1';
new   5:     p_logfile    varchar2(100) := 'ctxindex';
ORA-03114: not connected to ORACLE

ERROR at line 1:
ORA-03113: end-of-file on communication channel

At the same time, a trace file with an ORA-7445 error condition is created in the user dump destination of the Portal metadata repository database. The format and the references in the dump file may vary :

Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x0, PC: [0xa89a7e6, lxscop()+26]
%eax: 0x00000000 %ebx: 0x0cceab18 %ecx: 0x02020040
%edx: 0xbffe91c2 %edi: 0xbffe91a4 %esi: 0xbffe91c2
%esp: 0xbffe9138 %ebp: 0xbffe9144 %eip: 0x0a89a7e6
%efl: 0x00210246
  lxscop()+12 (0xa89a7d8) mov 0x10(%ebp),%ecx
  lxscop()+15 (0xa89a7db) mov 0x1c(%ecx),%ecx
  lxscop()+18 (0xa89a7de) test $0x8000000,%ecx
  lxscop()+24 (0xa89a7e4) jne 0xa89a81c
> lxscop()+26 (0xa89a7e6) movzb (%eax),%ecx
  lxscop()+29 (0xa89a7e9) test %ecx,%ecx
  lxscop()+31 (0xa89a7eb) je 0xa89a809
  lxscop()+33 (0xa89a7ed) mov %esi,0xfffffff8(%ebp)
  lxscop()+36 (0xa89a7f0) mov %edi,0xfffffffc(%ebp)
*** 2008-02-25 17:02:09.954
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [lxscop()+26] [SIGSEGV] [Address not mapped to object] [0x0] [] []
Current SQL statement for this session:
                              idx_name        => :a,
                              memory          => :b,
                              parallel_degree => :c );


Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x0, PC: [0x351eec4, lxscop()+16]
*** 2008-02-12 11:06:25.019
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [lxscop()+16] [SIGSEGV] [Address not mapped to object] [0x000000000] [] []
Current SQL statement for this session:
    l_message  varchar2(4000);
      -- Drop and recreate Text index preferences (other than the Lexer prefs)
      -- Drop any indexes that are invalid
      wwv_context.createindex( p_message => l_message );

All manifestations of this issue share a common PL/SQL Call Stack :

----- PL/SQL Call Stack -----
  object      line  object
  handle    number  name
0x28d8174c         5  package body CTXSYS.DRVDISP
0x28d8174c       246  package body CTXSYS.DRVDISP
0x2b9884d0       217  package body CTXSYS.DRVDML
0x41630018      2636  package body CTXSYS.DRVDDL
0x416e3210       530  package body CTXSYS.CTX_DDL

The server side trace file may contain additional functions on the Call Stack Trace :

lxscop()+26          signal   00000000             B ? B747EC90 ? B747ED10 ?
lxscat()+123         call     lxscop()             BFFE91C2 ? 0 ? B72F16BC ?
                                                   B72C00B0 ?
drsparAbsoluteURL()  call     lxscat()             BFFE91A4 ? 0 ? B72F16BC ?
+307                                               B72C00B0 ? BFFE91A4 ?
                                                   CC8B968 ? B72F16BC ?
                                                   B72C00B0 ?
drsugopen()+779      call     drsparAbsoluteURL()  BFFEC4F8 ? BFFEB3D0 ?
                                                   B72F1598 ?
drsiuopen()+147      call     drsugopen()          BFFEEB48 ? B716E01C ?


URL items have been added to portal pages


To view full details, 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 a vibrant support community of peers and Oracle experts.