Ctx doing a Core Dump with OLS

Question

ConText is core dumping when trying to access (index) a BLOB in a column of a table with an Oracle Label Security (OLS) policy applied. Using Oracle8i EE 8.1.7.0.0 .
BACKGROUND:
I have created a table with a primary_key column, a blob, and a few other columns.
I have also created an index on the BLOB column of this table, w/ indextype is
ctxsys.context .
I inserted some rows, wrote some data directly to the BLOBs, and updated the index.
And then applied the policy. SQL works well; I get the expected results, also okay with the WHERE contains()>0 clause... all is (seemingly) happy.
Then I inserted some more rows, as above (while the policy was applied). No problem.
Since the ConText index MUST be explicitly updated/maintained, I issue the
alter index <index_name> rebuild online parameters ('sync')
command.
BOOM! core dump.
ATTEMPT TO RESOLVE CIRCUMVENT:
I remove the table policy, and the update ("ALTER") works fine.
I drop this index, re-apply the OLS policy, and try to CREATE the ConText index, and
BOOM!
. 1). any attempts for ConText to access the table when policy is applied... are
fatal.
. 2). remove the policy, and the exact same command(s) work fine!
I reconfigured the kernel to double the shared mem and semaphores allowable etc. (This
is a 4GB Sun server, Solaris 8, patched). I tried cranking up some init<>.ORA parameters. And try it again BOOM!
TRACE:
ksedmp: internal or fatal error
ORA-07445
PL/SQL Call Stack
Line#: Object:
245 pkg body CTXSYS.DRIDISP
372 pkg body CTXSYS.DRIDISP
330 pkg body CTXSYS.DRIDISP
580 pkg body CTXSYS.DRIDDL
55 CTXSYS.TEXTINDEXMETHODS
1 anonymous block
QUESTION:
Is there anything that you know of that precludes ConText from properly accessing
BLOBs in a table with OLS policy applied? IS there an additional OLS-specific step
that I should take? I installed OLS 8.1.7 after 8i and ctx; should I relink/re-install ConText?
Please help...
Ben Lowers
Georgia Tech Research Institute
null

Answer 1

Please open a TAR with Oracle support.