ORA-07445 [dbgripuse_unpickle_section_elements] reported by MMON slaves
(Doc ID 1281997.1)
Last updated on MARCH 12, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.1 [Release 11.2 to 12.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 19-04-2013***
Symptoms
ORA-07445 [dbgripuse_unpickle_section_elements] is continuously reported by MMON slaves:
Sat Jan 08 15:02:02 2011
Exception [type: SIGBUS, Invalid address alignment] [ADDR:0xFFFFFFFF7DF7A1DF] [PC:0x107329544, dbgripuse_unpickle_section_elements()+1124] [flags: 0x0, count: 1]
Errors in file <diagnostic_dest>/diag/rdbms/<database name>/<instance name>/trace/<instance name>_m000_26636.trc (incident=36130):
ORA-07445: exception encountered: core dump [dbgripuse_unpickle_section_elements()+1124] [SIGBUS] [ADDR:0xFFFFFFFF7DF7A1DF] [PC:0x107329544] [Invalid address alignment] []
Exception [type: SIGBUS, Invalid address alignment] [ADDR:0xFFFFFFFF7DF7A1DF] [PC:0x107329544, dbgripuse_unpickle_section_elements()+1124] [flags: 0x0, count: 1]
Errors in file <diagnostic_dest>/diag/rdbms/<database name>/<instance name>/trace/<instance name>_m000_26636.trc (incident=36130):
ORA-07445: exception encountered: core dump [dbgripuse_unpickle_section_elements()+1124] [SIGBUS] [ADDR:0xFFFFFFFF7DF7A1DF] [PC:0x107329544] [Invalid address alignment] []
In this example, there was an earlier, 'insufficient space' error when trying to generate trace files in ADR HOME.
Sat Jan 08 14:20:02 2011
Trace dumping is performing id=[cdmp_20110108142002]
Non critical error ORA-00001 caught while writing to trace file "<diagnostic_dest>/diag/rdbms/<database name>/<instance name>/trace/cdmp_20110108142002/<instance name>_pmon_4704_bucket.trc"
Error message: SVR4 Error: 28: No space left on device
Trace dumping is performing id=[cdmp_20110108142002]
Non critical error ORA-00001 caught while writing to trace file "<diagnostic_dest>/diag/rdbms/<database name>/<instance name>/trace/cdmp_20110108142002/<instance name>_pmon_4704_bucket.trc"
Error message: SVR4 Error: 28: No space left on device
The call stack trace is similar to following:
dbgripuse_unpickle_section_elements
dbgripus_unpickle_section
dbgriprpss_read_pstaging_section
dbgripspsf_sweep_pstage_file
dbgripsto_sweep_staged_obj
dbgripgsilcb
dbgripricm_rltniter_wcbf_mt
dbgripritc_rltniter_wcbf
dbgripgsolx_get_stgoblst_wctx
dbgripsorx_swpobj_range_wctx
dbgripssor_sweep_stgobj_range
dbgrimswir2_sweep_inc_range_2
dbgrimswir_sweep_inc_range
dbke_mmon_sweep_inc_sl
kebm_slave_main
dbgripus_unpickle_section
dbgriprpss_read_pstaging_section
dbgripspsf_sweep_pstage_file
dbgripsto_sweep_staged_obj
dbgripgsilcb
dbgripricm_rltniter_wcbf_mt
dbgripritc_rltniter_wcbf
dbgripgsolx_get_stgoblst_wctx
dbgripsorx_swpobj_range_wctx
dbgripssor_sweep_stgobj_range
dbgrimswir2_sweep_inc_range_2
dbgrimswir_sweep_inc_range
dbke_mmon_sweep_inc_sl
kebm_slave_main
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |