Re: SNAPSHOT TOO OLD (1555) - SOLUTION ?

Hi,
This is a common problem when you run long query/transactions with high volumes of updates and transactions. For any query/transaction, you require read consistency. What happens when you run a long query/transaction, the rollback segs that require for this query to be read consistent, will be overwritten due to small rollback segs (also long running time during which many trancations/updates will occur).

There are two ways to work around this problem. 1. create large rollback segments for your work (which can be dropped

    later).
2. Run this program during the time when you have vwry minimum query/

    transactions (minimum database activity mostly in the night hours)

HTH Madhu Cherukuri

djose_at_att.com wrote in message <6d3sns$ibj$1_at_nnrp2.dejanews.com>...
>Hello everyone,I have a Pro*C program which churns through 4 tables and
>creates a flatfile. The program encounters oracle error code ORA-1555
>(SNAPSHOT TOOOLD ) causing it to exit.( I have an exit routine for non-zero
>return codes )The tables are as followsorderorder_detailsnameaddress
>* The program basically creates a cursor on order table which pulls out
 all
>rows in that table.* For each order it pulls out data from the other 3
>tables.* I use a host array for the FETCHES with a batch size of 2000.* I
>also use the PARALLEL QUERY OPTION.* The program currently takes about 4-5
>hours to run.* The volumes in these tables are very high and transactions
>are continously updating the above tables. My Question :Is there any
>way I can work around the snapshot too old error ?Any help with respect to
>handling this error wouldbe very much appreciated. Thanks for your time,
>Jude( djose_at_att.com )
>
>-----== Posted via Deja News, The Leader in Internet Discussion ==-----
>http://www.dejanews.com/ Now offering spam-free web-based newsreading
Received on Thu Feb 26 1998 - 00:00:00 CST