Have a look at MOS note 8103.1 - your symptoms sounds like “Expected Behaviour”
- DDL happening during your SELECT like many others on this list have pointed
out.
On 28 Jun 2021, at 8:51 pm, Pap <oracle.developer35@xxxxxxxxx> wrote:
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
