Look for error in Oracle log

[Eriovaldo Andrietta]

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

[Gus Spier]

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

Post by Eriovaldo Andrietta
Hi,
BEGIN
*
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 ?
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

[Eriovaldo Andrietta]

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

Post by Gus Spier
You don't actually which version of Oracle you're using.
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 <

Post by Eriovaldo Andrietta
Hi,
BEGIN
*
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 ?
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

[Mladen Gogala]

On Sun, 23 Jul 2017 13:12:14 -0300

Post by Eriovaldo Andrietta
Hi Gus,
I am using an Oracle 12.2.0.1.0 version.
It has the v$diag_alert_ext.

That table is available at least since 12.1:



Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> desc v$diag_alert_ext
Name Null? Type
----------------------------------------- -------- ----------------------------
ADDR RAW(8)
INDX NUMBER
INST_ID NUMBER
CON_ID NUMBER
ADR_PATH_IDX VARCHAR2(445)
ADR_HOME VARCHAR2(445)
ORIGINATING_TIMESTAMP TIMESTAMP(9) WITH TIME ZONE
NORMALIZED_TIMESTAMP TIMESTAMP(9) WITH TIME ZONE
ORGANIZATION_ID VARCHAR2(67)
COMPONENT_ID VARCHAR2(67)
HOST_ID VARCHAR2(67)
HOST_ADDRESS VARCHAR2(49)
MESSAGE_TYPE NUMBER
MESSAGE_LEVEL NUMBER
MESSAGE_ID VARCHAR2(67)
MESSAGE_GROUP VARCHAR2(67)
CLIENT_ID VARCHAR2(67)
MODULE_ID VARCHAR2(67)
PROCESS_ID VARCHAR2(35)
THREAD_ID VARCHAR2(67)
USER_ID VARCHAR2(67)
INSTANCE_ID VARCHAR2(67)
DETAILED_LOCATION VARCHAR2(163)
UPSTREAM_COMP_ID VARCHAR2(103)
DOWNSTREAM_COMP_ID VARCHAR2(103)
EXECUTION_CONTEXT_ID VARCHAR2(103)
EXECUTION_CONTEXT_SEQUENCE NUMBER
ERROR_INSTANCE_ID NUMBER
ERROR_INSTANCE_SEQUENCE NUMBER
MESSAGE_TEXT VARCHAR2(2051)
MESSAGE_ARGUMENTS VARCHAR2(515)
SUPPLEMENTAL_ATTRIBUTES VARCHAR2(515)
SUPPLEMENTAL_DETAILS VARCHAR2(515)
PARTITION NUMBER
RECORD_ID NUMBER
FILENAME VARCHAR2(515)
LOG_NAME VARCHAR2(67)
PROBLEM_KEY VARCHAR2(553)
VERSION NUMBER

Post by Eriovaldo Andrietta
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

Post by Gus Spier
You don't actually which version of Oracle you're using.
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 <

Post by Eriovaldo Andrietta
Hi,
BEGIN
*
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 ?
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

[Neil Chandler]

Eriovaldo,


An ORA-3113 error is a client-side error and it is unlikely that you will find reference to it within the database logs. It means that the client has unexpectedly lost connectivity to the database.

Much of the time these are due to the network problems and frequently due to a firewall between the client and the database terminating the connection due to timeout.


If it is the firewall, one potential solution used to be to set "sqlnet.expire_time" in the "sqlnet.ora" file to send a probe packet more frequently than the firewall timeout. The method implemented by Oracle for sqlnet.expire_time proble has changed in Oracle 12, and I don't know if it will have the same effect these days as I've not had chance to test it.


regards


Neil Chandler.


________________________________
From: oracle-l-***@freelists.org <oracle-l-***@freelists.org> on behalf of Eriovaldo Andrietta <***@gmail.com>
Sent: 23 July 2017 14:44
To: ORACLE-L
Subject: Look for error in Oracle log

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