Ora-8103 error
From: Pap <oracle.developer35_at_gmail.com>
Date: Mon, 28 Jun 2021 16:21:15 +0530
Message-ID: <CAEjw_fg3S05qn=3HuMsjKqN34qOPOcvPONnajf-jVca-hgppug_at_mail.gmail.com>
This question came from a friend in a forum for version 19.9.0.0.0 of oracle , stating, one of the SELECT query is failing with ora-08103 object no longer exists error intermittently and rerun makes that query finish without any error. And the query does have some partition tables used but they aren't able to find any partition maintenance activities during this period. But there must be some DDL happening and thus the SELECT query is failing. And it might be that the DDL is too quick that it's not logged in ASH/AWR views. So is there any method to get hold of the DDL statement and its source ? I saw enabling DDL_LOGGING at the system level is one approach, but thinking if it's having any negative sides if it's set at system level for a long duration and if any other possible approach exists?
Date: Mon, 28 Jun 2021 16:21:15 +0530
Message-ID: <CAEjw_fg3S05qn=3HuMsjKqN34qOPOcvPONnajf-jVca-hgppug_at_mail.gmail.com>
This question came from a friend in a forum for version 19.9.0.0.0 of oracle , stating, one of the SELECT query is failing with ora-08103 object no longer exists error intermittently and rerun makes that query finish without any error. And the query does have some partition tables used but they aren't able to find any partition maintenance activities during this period. But there must be some DDL happening and thus the SELECT query is failing. And it might be that the DDL is too quick that it's not logged in ASH/AWR views. So is there any method to get hold of the DDL statement and its source ? I saw enabling DDL_LOGGING at the system level is one approach, but thinking if it's having any negative sides if it's set at system level for a long duration and if any other possible approach exists?
Regards
Pap
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Jun 28 2021 - 12:51:15 CEST