Met ora-07445 on oracle 10.2.0.4 of Windows 2003

Question

Hello,
I was running an PL/SQL application using PL/SQL Developer and after a while, the application will be disconnected from the database with error 03113: end-of-file on communication channel. I checked the alert.log file of the database, at that time an ora-07445 error happened:
Errors in file c:\oracle\product\10.2.0\admin\dbtest1\udump\dbtest1_ora_4820.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x0] [ADDR:0x0] [UNABLE_TO_READ] []
My environment is oracle 10.2.0.4 on Microsoft Windows 2003(32bit).
My friends helped me search on metalink about this error and didn't find a similiar workaround. Can anybody take a look at this error or give some hint?
I want to upload the trace file but didn't find the entry to upload a file. Please let me know if I need to paste all the content of the trace file. it is too long.
Thank you very much.
Tony

Answer 1

I hope that I can log a SR because the metalink account is in our dba hands and till now, almost one month passed we got no answer form him.tough situation - Mystery Problem that you can't deal with directly, having to work through the powers that be second-hand to get support. Been there, done that :(
You probably haven't heard from the DBA because the DBA hasn't heard anything back from MOS - a pure guess on my part, but according to my experience in logging SRs quite possible.
You have some options - not good ones but they do exist. The ideas below are different variations based on the idea that if you can figure out where the program is having trouble you might be able to work around the problem.
There is no trace in PL/SQL as such, but there is a debugger. I'm not sure if you are using All-around Automations's PL/SQL developer or Oracle's SQL*Developer but both support the debugger. You can compile stored code in debug mode and use a GUI interface in both products (TOAD too, for that matter) to set stopping points to monitor your progress. There is information about the debugger in the Oracle documentation and elsewhere on-line. IF YOU CHOOSE TO USE THE DEBUGGER USE A GUI INTERFACE TO SET IT UP AND RUN IT - the command-line interface via PL/SQL APIs in SQL*PLUS is nearly impossible to use effectively.
Alternately and more easily you can put your own markers in the code and execute it. This can take the form of lines like DBMS_OUTPUT.PUT_LINE('Got to line 999') or more elegantly using dbms_application_info to set a column value in V$SESSION to put a message there (procedure name, line number, whatever you want within reason). You'll only see DBMS_OUTPUT.PUT_LINE data after the program(s) finish or crash so the dbms_application_info method might be a little bit more useful
Good Luck!