Re: How to debug resource busy error
From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Mon, 2 May 2022 18:37:13 -0400
Message-ID: <391f4b14-9947-4255-ba67-ef311be8d118_at_gmail.com>
Date: Mon, 2 May 2022 18:37:13 -0400
Message-ID: <391f4b14-9947-4255-ba67-ef311be8d118_at_gmail.com>
On 5/2/22 16:29, Mark W. Farnham wrote:
Another strategic way is to have all DML controlled by a job management system and so it can be forced to read something (typically in a one row status table) before each job fires (including ad hoc queries, you just need to build the harness). This avoids the special synonyms and grants and people can still submit things, but those things can’t interfere. This may require substantial work to set up and build.
Yet another way would be to hire an application architect who
would be able to make recommendations and analyze the
requirements: when to update, when to have downtime and when to
upgrade. You gotta know when to hold them, when to fold them, when
to walk away and when to run. You never upgrade you structure when
there is an update on the table, there will time enough for
upgrading when the application is shut down.
-- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com-- http://www.freelists.org/webpage/oracle-l Received on Tue May 03 2022 - 00:37:13 CEST