Core dump on dbms_pickler

[engineer2100]

What is this dbms_pickler? Why scould it cause a core dump?

here is what I found in the trace file

ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [0x35E6786] [] [] [] []
Current SQL statement for this session:
begin :1 := dbms_pickler.get_type_shape(:2,:3,:4,:5,:6,:7); end;
----- PL/SQL Call Stack -----
  object      line  object
  handle    number  name
0BAC6390        18  package body SYS.DBMS_PICKLER
0BAC6390        58  package body SYS.DBMS_PICKLER
0B961AB4         1  anonymous block

 

[SantaMufasa]

Engineer,

I believe that in this case, "DBMS_PICKLER" is a "pickled red herring"...it is an "artifact" of the "ksedmp" error, which is the bigger issue.

A "ksedmp" error occurs when there has been an attempt to access memory that is "out-of-bounds" for what your process is authorised to access. Neither "DBMS_PICKLER" nor any other Oracle code should, in and of itself, trigger a "ksedmp" error.

If I encountered a "ksedmp" error, I would enlist help from Oracle Technical Support (OTS-MetaLink). It would be best, however, if you can create a scenario that reliably replicates the error. Replicating the problem would be very useful to OTS in

a) recreating the problem,
b) troubleshooting the problem, and
c) confirming that they have resolved the problem.

Therefore, try doing again what was occurring at the time that this error occurred. (Has the "ksedmp" error happened since the occurrence, above?)

BTW, DBMS_PICKLER is an Oracle package that relates to "pickling" data: the process by which an object is serialised or converted into a byte stream. "Unpickling" is the reverse process. Other Oracle packages can call DBMS_PICKLER if/when it needs to serialise or unserialise an object. So, I don't imagine that you, or any of your code, invoked DBMS_PICKLER explicitly/directly.


Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]

 

[engineer2100]

Yes Santa, our java code heavily uses Oracle Types and keep pumping (to/fro) data via types and I do see why this package would have been used inherently

I checked out the 7445 Lookup Tool on OTN Metalink. Its reported as a known issue. The function was kghfrf within the core dump log.

However the system has slowed down a lot. I even switched off the Audit Trail; though it improved the response time a bit but not that great.

We have the following setup

Weblogic 8.1 SP5
Oracle 10.1.0