Re: Ora-8103 error

“The parameter enable_ddl_logging comes under the extra cost "Lifecycle Management" option.
Don't do it unless you've paid for the licence.” Oh! I was basing my advise thinking I’d had this enabled, having seen DDL in my alerts logs forever. Thankfully the logging was through audit_sys_operations instead of DDL logging. Thanks for the heads up.

On Mon, 28 Jun 2021 at 12:43, Jonathan Lewis <jlewisoracle_at_gmail.com> wrote:

>
> Checking to see if I'd written anything about ddl triggers - the code
> fragement I supplied was alread part of an old blog note:
> https://jonathanlewis.wordpress.com/2012/09/08/ddl-triggers/
>
> Reading that reminded me of two things:
>
> a) the alert log will automatically capture SOME of the partition
> maintenance operations
> b) if Oracle does an implicit add partition on an interval partitioned
> table it's not captured as DDL
>
> Regards
> Jonathan Lewis
>
>
>
> On Mon, 28 Jun 2021 at 11:51, Pap <oracle.developer35_at_gmail.com> 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
>>
>

--
http://www.freelists.org/webpage/oracle-l