Traces generated with no error in alert.log, OER 8102 reported in the trace
(Doc ID 433773.1)
Last updated on JANUARY 07, 2025
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.1 to 10.2.0.1 [Release 9.2 to 10.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
This problem can occur on any platform.
Symptoms
- Alert.log shows that a trace has been created but no ORA-XXXXX error is generated
Errors in file /TEC/oracle9/admin/TEC9/bdump/tec9_s000_35888.trc
- In the trace, an OER 8102 is reported
*** 2007-05-25 07:16:10.348
*** SESSION ID:(22.352) 2007-05-25 07:16:10.134
oer 8102.2 - obj# 25298, rdba: 0x02c4aadc
kdk key 8102.2:
ncol: 2, len: 15
...
- The trace doesn't report any ORA-XXXXX error.
- The trace shows that there was DML being executed.
*** 2007-05-25 07:16:10.382
ksedmp: internal or fatal error
Current SQL statement for this session:
delete from tec_t_evt_rep where (to_char(......
....
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 |
| Cause |
| Solution |
| References |