ORA-07445: exception encountered: core dump [ph2sf_scan_fields()+594] [ACCESS_VIOLATION] [ADDR:0x8] [PC:0x7FFA9B633C52] [UNABLE_TO_READ] []
We’re getting the below error while running utlrp.sql script after we applied 19.9 patch to database 19.3 which is running on windows server 2016.
2021-01-05T23:16:39.538245+03:00
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x8] [PC:0x7FFA9B633C52, ph2sf_scan_fields()+594]
Errors in file D:\APP\ORACLE\diag\rdbms\ezymir\ezymir\trace\ezymir_j000_94264.trc (incident=136519):
ORA-07445: exception encountered: core dump [ph2sf_scan_fields()+594] [ACCESS_VIOLATION] [ADDR:0x8] [PC:0x7FFA9B633C52] [UNABLE_TO_READ] []
Incident details in: D:\APP\ORACLE\diag\rdbms\ezymir\ezymir\incident\incdir_136519\ezymir_j000_94264_i136519.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Initially we thinking that its seems to be bug. But After we analyzed the trace file, there is one package body having issue for compilations.
Trace file :
name=XXXXX.CLK_CLM_PROCESS
Symbol file D:\app\WINDOWS.X64_193000_db_home\BIN\orasql19.SYM does not match binary.
Symbol TimeStamp=5cef5a1d, Module TimeStamp=5f8f4599 are different
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x8] [PC:0x7FFA9B633C52, ph2sf_scan_fields()+594]
Encountered exception while getting args for function:0x00007FFA9B685811
Symbol file D:\app\WINDOWS.X64_193000_db_home\BIN\orasql19.SYM does not match binary.
Symbol TimeStamp=5cef5a1d, Module TimeStamp=5f8f4599 are different
Encountered exception while getting args for function:0x00007FFA9B690D40
Encountered exception while getting args for function:0x00007FFA9B685811
*** 2021-01-05T23:16:40.272618+03:00
2021-01-05T23:16:40.272618+03:00
Incident 136519 created, dump file: D:\APP\ORACLE\diag\rdbms\ezymir\ezymir\incident\incdir_136519\ezymir_j000_94264_i136519.trc
ORA-07445: exception encountered: core dump [ph2sf_scan_fields()+594] [ACCESS_VIOLATION] [ADDR:0x8] [PC:0x7FFA9B633C52] [UNABLE_TO_READ] []
Solution :
We found that we have master schema there . this schema having lot of objects. those objects having read/write permission to other schemas. But we have missed some permission to some particular schema when we’re creating or importing. once we provided the particular privilege to the schema. we can able to compile the packages using utlrp.sql as well.
permission given like
GRANT ALTER, DELETE, INDEX, INSERT, REFERENCES, SELECT, UPDATE, ON COMMIT REFRESH, QUERY REWRITE, READ, DEBUG, FLASHBACK ON MASTERSCHEMA.table to xxxxx;