Re: Snapshot too old but UNDO_RETENTION very high

From: DBA Infopower Support <support_at_dbainfopower.com>
Date: Fri, 6 Feb 2004 02:08:33 -0800
Message-ID: <SfqdnWR3AeGu-77d4p2dnA_at_comcast.com>


Hello Firehawk,

  Since production is impacted and ORA-1555 is happening despite normal undo setting this is what can be done for fast restoration:

    [Quoted]
  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.
  2. Open TAR on metalink and involve Oracle into resolution

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.

"Firehawk®" <firehawk-brazil_at_gmx.net> wrote in message news:Xns9486A07016DBEfirehawkcom_at_130.133.1.17...
> My developers made a UPDATE from ONE table with 9 Million of lines.
> Script read a line, make many consistencies and update same line in
another
> column that was empty before.
> Ok, tipical case of ORA 1555, but:
> 1) Oracle 9i
> 2) My undo tablespace has 30 Gb !!!
> 3) undo_management='AUTO'
> 4) undo_retention=489600 (very high, no ?)
> I am with a important production process stopped because this problem
>
> Oracle 9.2.0.4
> AIX 5.2.0.0
>
> Any hint ?
>
Received on Fri Feb 06 2004 - 11:08:33 CET

Original text of this message