On Sun, 23 Jul 2017 13:12:14 -0300
Eriovaldo Andrietta <ecandrietta@xxxxxxxxx> wrote:
Hi Gus,
I am using an Oracle 12.2.0.1.0 version.
It has the v$diag_alert_ext.
I got the message :
select INST_ID, to_char (ORIGINATING_TIMESTAMP, 'DD-MM-YYYY HH24:MI') data,
PROCESS_ID, MESSAGE_TEXT
from v$diag_alert_ext
where trim(process_id) = '3524';
Thanks
Eriovaldo
2017-07-23 10:54 GMT-03:00 Gus Spier <gus.spier@xxxxxxxxx>:
You don't actually which version of Oracle you're using.
If the view, v$diag_alert_ext is available, try:
select message_type, originating_timestamp, message_text from
v$diag_alert_ext where message_type in (2,3,4) and originating_timestamp >
sysdate - 2
If you run a describe on v$diag_alert_ext, you will see fields for trace
file and other tantalizing columns. Let us know how it works out for you.
As an additional alternative, take a look at ADRCI (automatic diagnostic
repository command interpretor) for another way to winkle out your
information.
Good luck!
Gus
On Sun, Jul 23, 2017 at 9:44 AM, Eriovaldo Andrietta <
ecandrietta@xxxxxxxxx> wrote:
Hi,
I got this error :
BEGIN
*
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Process ID: 3524
Session ID: 1161 Serial number: 23073
The last success command occured : ###### : 23-07-2017 02:29:1717
How and where can I search the error ?
in alert ? incident ? trace ?
I tried some queries without sucess, like that :
select to_char (ORIGINATING_TIMESTAMP, 'DD-MM-YYYY HH24:MI') data,
message_text
from x$dbgalertext
where ORIGINATING_TIMESTAMP > (SYSDATE -1)
and message_text like '%ORA-03113%' ;
Any suggestion ?
Regards
Eriovaldo
