Re: Snapshot too old but UNDO_RETENTION very high

Dear Sybrand,

   Here is one of the professional production Oracle DBAa rules that should be taken very seriously:

    If production is impacted due to unexpected Oracle behavior Oracle TAR should be open immediately and problem escalated.

    Oracle support has much more internal information on Oracle then average DBA can imagine.

    Problem that seem very innocent (like this one) potentially can cause even more serious issues and Oracle support usually aware and can help.

    In regards to an issue:

[Quoted]        Frequent commits would greatly reduce probability of ORA-1555, since [Quoted] consistent data required by transaction would have much less chance to be lost in rollback segments.

Regards,
Support

DBA Infopower

https://www.dbainfopower.com

The advice provided by DBA Infopower are provided "as is" with no warranty. DBA Infopower expressly disclaims any warranty, regarding the advice including any implied warranty of merchant fitness for a particular purpose aviating course of dealing and/or performance. DBA Infopower does not warrant that the advices provided by DBA Infopower will be free from bias, detests, errors, eavesdropping or listening. DBA Infopower shall not be responsible for the quality of information or the authentication of the services or details given by experts on the advice. By using this advice the user of the advice accepts the terms and conditions of this statement.

"Sybrand Bakker" <gooiditweg_at_nospam.demon.nl> wrote in message news:3iv620h1satgjk5k5ibaciocufko4mknhi_at_4ax.com...
> On Fri, 6 Feb 2004 02:08:33 -0800, "DBA Infopower Support"
> <support_at_dbainfopower.com> wrote:
>
> > 1) Ask if developers can commit updates (every 500-1000 records for
> >example). This should take you through the table update with no 1555s.
> > Single update SQL can be changed to PL/SQL block.
>
> Again unprofessional advice. Ora-1555 are being *CAUSED* by
> incremental commits.
> Opening a TAR is also useless, as Metalink is flooded with articles
> how to deal with ora-1555 and it's causes. Oracle is definitely not
> going to address this one.
>
>
> --
> Sybrand Bakker, Senior Oracle DBA
Received on Fri Feb 06 2004 - 20:03:29 CET