"Snapshot too old" for a report program

We get "ORA-1555 error: snapshot too old" for a report job, NOT an update job.
We can add rollback segments to the DB.
Why we cannot increase the commit frequency to fix this issue?
Thanks!

> 1. create a big rollback segment. search the web for keyword PSAPROLLBIG.
> 2. convert to PSAPUNDO, as started by others, check SAP note 600141.
> 3. analyze the program and if it is a Z program, ask your program to add more commits in his program.
HI all,
of course Stefan and Eric have already given the right hints here.
But the main point here is not the configuration of the UNDO management.
I know that this kind of problems bears a big mental hurdle in it, which is also difficult to jump over for many supporters.
The notion of Undo/Rollback data beeing used mainly for ROLLBACK actions is unfortunately totally wrong.
The primary and main usage of this data is to deliver the consistent view (as already explained in this thread).
So the single big question here is: why does a single statement of your report needs to visit so many pages from a certain point in time?
In the wast majority of cases this is because the statement is badly tuned.
Maybe there is no appropriate index available.
Or it's just written badly, so that unnecessary data must be read by Oracle.
Maybe the CBO does something wrong which must be checked.
Maybe the data is scattered over too many blocks and clustering them together somehow could help
The core point here is: figure out what causes the statement to touch so many pages and fix that.
Then you are most likely to come over this problem.
All other recommendations, especially the move to automatic undo management: full ack.
But the solution to your problem is to fix your statement.
regards,
Lars

Similar Messages

ORA-01555 Snapshot too old - opening scheduled report

This seems to happen to long running scheduled reports - but not consistentlly. This one in particular ran for 14 hours and then ended with an this error - ORA-01555 snapshot too old: rollback segment number 2 with name "_SYSSMU2_1285383686$" too small. What does this mean?

Pl post details of OS, database and discoverer versions.
This is a common error - you will need to get your DBA team involved, and it is fixed easily. See these MOS Docs
ORA-01555: "Snapshot too old" - Overview (Doc ID 10630.1)
ORA-01555 "Snapshot too old" - Detailed Explanation (Doc ID 40689.1)
ORA-1555 Using Automatic Undo Management - How to troubleshoot (Doc ID 389554.1)
HTH
Srini

"Download ITunes 10 now." My Mac is too old for this new program...but I can't get by it. Advice??

But I cannot get past the Download page....and it won't let me purchase anything. Advice?

Try this version: iTunes 9.2.1, http://support.apple.com/kb/DL1056

Snapshot too old error occured, kindly need solution for it...

Dar friends
I got snapshot too old error on most used database
Kindly give me the solution....
my solution was
Alter rollback segment <rollback segmnt name>
datafile '<path>/filename.dbf' resize <no>k;
or
alter rollback segment <rollback segmnt name>
add datafile '<path>/filename.dbf' size <no>k
storage(initial 1k nxt 1k minextnts 2 maxextents unlimited)
Kindly suggest me wheather my code is currect or not...
Ur
Friend

I don't know what version of the database you are running? I'm only using 8.1.7.4. But where I come from, you add datafiles to the tablespace, not the rollback segment.
alter tablespace rollback
add datafile '<blah, blah>'
size 147m
autoextend on next 100m maxsize 2047m;
Make sure that you have a suitable number of rollback segments that are well-sized extents. But mostly, listen the Tom Best, and try and introduce some best practices (no pun intended) to reduce the likelihood of this situation arising.

Snapshot too old

I have written a procedure that populates a temp table which does a commit on every thousand rows. Now, this job has been running for 3 yrs now. Unfortunately though, lately, i have been getting the following error:
Declare
ERROR at line 1:
ORA-01555: snapshot too old: rollback segment number with name "" too small
ORA-06512: at line 189This program have been tuned through out those years, like doing a commit on every n thousand of rows, putting hints and some other things as suggested by our dba. It is also understood that new jobs.. big jobs.. have been created that runs a long side this process.
Now, my questions is, if i am doing a select on this table for example member_history table in a cursor then doing an insert. Then another job which is running at the same time as my job is doing a
INSERT /*+ append */ INTO temp_table (column1, column2, column3)
select column1, column2, column3
from member_history@dbprod.
where ... Would this have caused the problem? We are talking about number of rows 64,033,608 on this history table.
I would very much appreciate all your help!
Thanks,
Marilyn

Well, the primary reason for this error in my experience is fetching across commits. Which sounds exactly what your code is doing.
Thus for 3 years the code has been wrong. Violating ANSI SQL standards that say you are not allowed to fetch across commits. You were simply lucky that the rollbacks/undo did not wrap as there were little or no other transactions running at the same time.
Do not commit every n number of rows. Oracle is not SQL-Server or Ingres. It works very different ito concurrency as it has no lock manager and there are no locking overheads.
Refer to Metalink Note ORA-01555 "Snapshot too old" - Detailed Explanation, note id 40689.1.
Also refer to asktom.oracle.com on this:
http://asktom.oracle.com/pls/ask/f?p=4950:8:9219002089752914987::NO::F4950_P8_DISPLAYID,F4950_P8_CRITERIA:275215756923

The nature of "ORA-01555: snapshot too old..." error

Hi all,
Please help me to understand the nature of this error:
ORA-01555: snapshot too old: rollback segment number 23 with name "_SYSSMU23_755263746$" too small
One of reports returns this error. Yes, I googled it, but honestly I can't understand deeply what causes it. Usually I resolve it by performing sql request on yesterday's copy of production database. Is it correct to say that this error happens when I try to perform request on tables that are changed in the same moment? What is correct solution to resolve it other than using yesterday's copy of production database?

marco wrote:
Antonio,
The problem is generally small segments of undo, you need to add more space or put guaranty the tablespaces.
How do I describe it for our DBA (how much extra space do I need and what is the name of tablespace)?
Before you go to your DBA, you should figure out how much space your largest query/update uses. That is, your biggest transaction, how much space does it need? 10M? 100M? 1G? From there, your DBA can then size your UNDO properly (or at least "more better" ). Yes he "name of the tablespace" is just called "UNDO").
As mentioned before, the solution might not even be to increase your UNDO size, but rather to identify the "problem job", and fix it. That's not easy, however, talk to your DBA, he may be able to help with that as well.
Things to look for:
1) a job that issues a lot of commits. (suspicious - try to reduce # of commits).
2) a job that runs for a long time and updates along the way (suspicious - try to reduce run time).
3) a job that runs for a long time and has no updates (try to reduce run time - in this case, if this job starts running, and then takes a long time, a lot of other jobs may be reasonably doing updates, and this long run query needs to reference a row that was updated - it might lose it in the UNDO, though).
4) long running queries running at same time as updates on same table. (not always possible, but think about it: a "long running query" is often a "report" of some sort (not always, but often). Try to schedule the reports when less update activity is expected. Or, if the updates are part of the same batch, try to schedule them after each other so they don't overlap. (if the updates are online users, there isn't much you can do except try to decrease runtime of the long running query).
You DBA can help find candidates for those cases.

Snapshot too old error 1555

how to over come this problem practically

I can't speak for the original poster, of course.
But snapshot too old errors are what you get when, in order to produce the last piece of data at the finish time of some report, you have to roll the data you encounter in the buffer cache back to the state it was in at the start time.
A query which starts at 10.00am, for example, and finishes at 10.03 must see the data at 10.03 in the state it was at at 10.00am. So at the end of the query process, we have to do a '3 minute rollback'.
But if your query starts at 10.00am and doesn't finish until 10.53am, then you'd better hope 53 minutes of undo still exists in your database, because you're going to need to roll 10.53 data back to the state it was at 10.00.
The larger the time difference between the start and finish of a query, therefore, the more likely it becomes that the undo needed to generate a read consistent image won't be available, and that's when you get the 1555 signalled.
Most advice on 1555s say to increase the size of your rollback segments or your undo tablespace or increase the undo_retention time, so that the necessary undo **is** still available by the time you get to the query's finish time. But it's also a reasonable suggestion (though much harder to implement!) to tune the query so that the gap between start and finish time is much smaller than before. If a query used to take 53 minutes to complete but after tuning only takes 23 minutes to run, you've reduced the age of the undo you need available to produce the report by 30 minutes.
In other words, the common approach to 1555s is to increase the amount of undo that's available on the system. The approach being suggested here is to **reduce** the need for so much undo in the first place by reducing the length of time queries run for.

Reg: snapshot too old error

Hi Consultants ,
when i run requests iam getting below errors please advice me
ORA-01555: snapshot too old: rollback segment number 6 with name "_SYSSMU6$" too small
this is error getting for 2 programs.
Thanks,
Anu.

Hi,
What is the database version?
Please see if these documents help.
Note: 40689.1 - ORA-01555 "Snapshot too old" - Detailed Explanation
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=40689.1
Note: 1005107.6 - ORA-01555: snapshot too old - Causes and Solutions
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=1005107.6
Regards,
Hussein

Request got errror as ORA-01555: snapshot too old: rollback segment number

hi Consultants,
reqeust gor errores as ORA-01555: snapshot too old: rollback segment number 50 with name "_SYSSMU50$" too small ORA-06512: at line 90
anyone please advice me on this.
Thanks,
Anu.

Thanks for ur reply
Is this a standard or custom concurrent program?This is customer program it is working fine if run as individual
Thanks,
Anu

Oracle error: Ora-01555 : snapshot too old: rollback segment number 1......

System Error: Unknown Database error (type qqdb_ResourceException) on WMS_WH1: Execute failed for SQL statement ............... error from database is: ORA-01555: snapshot too old: rollback segment number 1 with name "_SYSSMU1$" too small...
Any ideas ? Please help.
Thank you.

You either have
- an UNDO tablespace that is way too small (rollback segments that are too small); or
- an application that does way too many COMMITs (common with apps ported from SQL Server)
From the added info, I would guess that the Java program has a major loop and does processing on each of the values it gets in that loop. At the end of each turn in the loop, it does a commit. Then it tries to look at the next record in the master list. After a while (say around 388 loops ;-) ) it dies.
The reason is that when it looks for information in the master query, it needs to rebuild that information to the moment that query was initiated. It uses rollback (AKA undo) to rebuild that. But rollback is not guaranteed to exist after a commit (unless forced) and once a commit happens, that area can be reused. When it is reused, the information is no longer there to rebuild the row, and that raises an ORA-01555
Edited by: Hans Forbrich on Sep 11, 2009 3:44 PM

About snapshot too old and undo tablespace

Hello,
version: 11.1.0.7
environment:
Database A contain some views from several tables located into database B.
When I query the views that join several tables located in a remote database B using a dblink the query intermittently notice me, the following errors:
ORA-12801: error signaled in parallel query server
ORA-01555: snapshot too old: rollback segment number too small
Some times after the I re-execute the query it run without any problems but it is bad because the Developers can not accurately test their app.
The undo tablespace have the following configuration:
guaranteed retention
unlimited
undo_retention is about 7200.
Also the undo tablespace are just using a 4% of total so I think the system should has honor to the old images from my distributed query.
Thank you in advance for your suggestion.

user12100209 wrote:
Hello,
version: 11.1.0.7
environment:
Database A contain some views from several tables located into database B.
When I query the views that join several tables located in a remote database B using a dblink the query intermittently notice me, the following errors:
ORA-12801: error signaled in parallel query server
ORA-01555: snapshot too old: rollback segment number too small
Some times after the I re-execute the query it run without any problems but it is bad because the Developers can not accurately test their app.
The undo tablespace have the following configuration:
guaranteed retention
unlimited
undo_retention is about 7200.
Also the undo tablespace are just using a 4% of total so I think the system should has honor to the old images from my distributed query.
Thank you in advance for your suggestion.session reporting ORA-01555 is victim.
some session is doing DML against same table as victim session & doing COMMIT (likely inside LOOP)

Snapshot too old when deleting from a "big" table

Hello.
I think this is a basic thing (release 8.1.7.4). I must say I don't know how rollback segments really work.
A table, where new records are continuously inserted and the old ones can be updated in short transactions, should be purged every day by deleting old records.
This purge has never been done and as a result it has now almost 4 million records, and when I launch the stored procedure that deletes the old records I get the "snapshot too old" error because of the read consistency.
If I launch the procedure after stopping the application that inserts and updates in the table, then I don't get the error. I guess the problem is that meanwhile the procedure is being executed other transactions also need to use rollback segments so that the rollback segment space that the snapshot needs isn't enough. Do you think this is the problem?
If this is the case then I suppose that the only solution is increasing the size of the only datafile of the only tablespace for my 4 rollback segments. Am I wrong?
(Three more questions:
- Could the problem be solved by locking some rollback segments for the snapshot? How could I do that?
- What is a discrete transaction?
I'm a developer, not a dba, but don't tell me to ask my dba because it isn't that easy. Thanks in advance.

"snapshot too old indicates the undo tablespace does not have enough free space for a long running query" what does this mean? why do I get the same error in two different databases, in the first the size of the datafile of the undo tablespace is 2GB whilst in the second it is only 2MB? How can I know how big the datafile has to be?
One possible solution could be not deleting the whole table at once but only a few records? Would this work? Why when I try "select count(*) from my_table where rownum = 1" I also get "snapshot too old" when other transactions are running.

ORA-01555: snapshot too old: rollback segment number 3 with name "_SYSSMU3$

A Materalized view is scheduled to update every 12 hours . When it has tried to update it has thrown the error ...
ORA-12008: error in materialized view refresh path
ORA-01555: snapshot too old: rollback segment number 3 with name "_SYSSMU3$"
too small
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 803
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 860
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 841
ORA-06512: at line 1

Hi,
Can you increase the size of the UNDO Tablespace ?
For more information, you can find on this link below:
http://forums.oracle.com/forums/search.jspa?threadID=&q=ORA-01555&objID=c84&dateRange=all&userID=&numResults=15
Cheers

ORA-01555: snapshot too old

Hi,
We have audit component, one responsibility of which is to archive audit messages from Oracle database. The component fails on a simple select statement (provided below) that retrieves number of records to be archived based on age parameter:
SELECT COUNT(*) FROM blobobjtable blbt, auditmessagetable msgt WHERE msgt.blobobjtablepk = blbt.blobobjtablepk AND trunc(to_number(substr((SYSTIMESTAMP-msgt.credtimeutc),1,instr(SYSTIMESTAMP-msgt.credtimeutc,' ')))) >= age
We tried the following 3 select statements directly from SQL Plus. The result was that the first two succeeded and the last one failed with "ORA-01555: snapshot too old" exception. We tried these select statements after restart of Oracle database but still got last select statement failed. One thing that we noticed was that the last select statement takes extremely long time to complete. Also, analyzing the index table used during the join failed with the same exception. The same is true when the primary key indices are analyzed.
1) select count(*) from blobobjtable
2) select count(*) from auditmessagetable
3) select count(*) from blobobjtable blbt, auditmessagetable msgt WHERE msgt.blobobjtablepk = blbt.blobobjtablepk
Can somebody explain what might be the cause of ORA-01555 exception for such simple select statement? Does Oracle persists information of UNDO buffers before restart? Is there any way to clean UNDO buffers manually?
If somebody has experience in resolving "ORA-01555: snapshot too old" exception problem please share you experience with us. Any help will be appreciated.
Thanks,
Aleks

how many rows in ur tables.
select count(*) from blobobjtable blbt
SQL> show parameter undo
NAME                                 TYPE        VALUE
undo_management                      string      AUTO
undo_retention                       integer     300
undo_tablespace                      string      UNDOTBS1
SQL> select count(*) from sm;
COUNT(*)
   1326661
Elapsed: 00:00:03.53
SQL> select count(*) from sm;
COUNT(*)
   1326661
Elapsed: 00:00:03.45
SQL> select count(*) from sm ss,ac_taj@taj ac
2 where ss.nserial = ac.nserial;
COUNT(*)
     88763
Elapsed: 00:00:38.35
SQL> show parameter db_name
NAME                                 TYPE        VALUE
db_name                              string      db02
SQL>i have some configuration of undo tbs. but i am not getting any error. also i am just startup my database if right know i am only one user connected to database.
SQL> select bytes/1024/1024 "UNTO MB" from dba_data_files
2 where tablespace_name = 'UNDOTBS1'
3 /
   UNTO MB
       930

Snapshot too old error

Hi All,
need suggestions for tuning a query failing with the error "Rollback segment too small; snapshot too old”. The query is taking a long time to run.

Here is the Explain plan (if you can understand !!!). Unable to generate the tkprof as the query is taking exceptionally long time.
EXECUTION_PLAN
0 SELECT STATEMENT Cost = 18675
1 NESTED LOOPS Cost = 1
100 TABLE ACCESS BY INDEX ROWID MTL_SYSTEM_ITEMS_B Cost = 2
101 INDEX UNIQUE SCAN MTL_SYSTEM_ITEMS_B_U1 UNIQUE
2 NESTED LOOPS Cost = 1
98 TABLE ACCESS BY INDEX ROWID WSH_NEW_DELIVERIES Cost = 2
99 INDEX UNIQUE SCAN WSH_NEW_DELIVERIES_U1 UNIQUE
3 NESTED LOOPS Cost = 1
96 TABLE ACCESS BY INDEX ROWID WSH_DELIVERY_ASSIGNMENTS Cost = 2
97 INDEX RANGE SCAN WSH_DELIVERY_ASSIGNMENTS_N3 NON-UNIQUE
4 NESTED LOOPS Cost = 1
94 TABLE ACCESS BY INDEX ROWID WSH_DELIVERY_DETAILS Cost = 2
95 INDEX RANGE SCAN WSH_DELIVERY_DETAILS_N3 NON-UNIQUE
5 NESTED LOOPS Cost = 1
92 TABLE ACCESS BY INDEX ROWID HZ_PARTIES Cost = 2
93 INDEX UNIQUE SCAN HZ_PARTIES_U1 UNIQUE
6 NESTED LOOPS Cost = 1
7 NESTED LOOPS Cost = 1
8 NESTED LOOPS Cost = 1
9 NESTED LOOPS Cost = 1
10 NESTED LOOPS Cost = 1
EXECUTION_PLAN
11 NESTED LOOPS Cost = 1
12 NESTED LOOPS Cost = 1
13 NESTED LOOPS Cost = 1
14 NESTED LOOPS Cost = 1
15 NESTED LOOPS Cost = 1
16 NESTED LOOPS Cost = 1
17 NESTED LOOPS Cost = 1
18 NESTED LOOPS Cost = 1
19 NESTED LOOPS Cost = 1
20 NESTED LOOPS Cost = 1
21 NESTED LOOPS Cost = 1
22 NESTED LOOPS Cost = 1
23 HASH JOIN Cost = 1
24 TABLE ACCESS BY INDEX ROWID OE_ORDER_HEADERS_ALL Cost = 1
25 NESTED LOOPS Cost = 1
26 NESTED LOOPS Cost = 1
27 NESTED LOOPS Cost = 1
28 HASH JOIN Cost = 1
29 TABLE ACCESS BY INDEX ROWID HR_ORGANIZATION_INFORMATION Cost = 1
30 INDEX RANGE SCAN HR_ORGANIZATION_INFORMATIO_IX1 NON-UNIQUE Cost = 1
31 NESTED LOOPS Cost = 2
EXECUTION_PLAN
32 NESTED LOOPS Cost = 1
33 NESTED LOOPS Cost = 1
34 NESTED LOOPS Cost = 1
35 NESTED LOOPS Cost = 1
36 NESTED LOOPS Cost = 1
37 NESTED LOOPS Cost = 1
38 NESTED LOOPS Cost = 1
39 TABLE ACCESS BY INDEX ROWID FND_FLEX_VALUE_SETS Cost = 1
40 INDEX UNIQUE SCAN FND_FLEX_VALUE_SETS_U2 UNIQUE Cost = 1
41 TABLE ACCESS BY INDEX ROWID FND_FLEX_VALUE_SETS Cost = 2
42 INDEX UNIQUE SCAN FND_FLEX_VALUE_SETS_U2 UNIQUE
43 TABLE ACCESS BY INDEX ROWID FND_FLEX_VALUES Cost = 2
44 INDEX RANGE SCAN FND_FLEX_VALUES_N3 NON-UNIQUE
45 TABLE ACCESS BY USER ROWID FND_FLEX_VALUES Cost = 2
46 TABLE ACCESS BY INDEX ROWID HZ_LOCATIONS Cost = 2
47 INDEX RANGE SCAN HZ_LOCATIONS_N5 NON-UNIQUE Cost = 1
48 TABLE ACCESS BY INDEX ROWID HZ_PARTY_SITES Cost = 2
49 INDEX RANGE SCAN HZ_PARTY_SITES_N2 NON-UNIQUE
50 TABLE ACCESS BY INDEX ROWID HZ_CUST_ACCT_SITES_ALL Cost = 2
51 INDEX RANGE SCAN HZ_CUST_ACCT_SITES_N1 NON-UNIQUE
52 TABLE ACCESS BY INDEX ROWID HZ_CUST_SITE_USES_ALL Cost = 2
EXECUTION_PLAN
53 INDEX RANGE SCAN HZ_CUST_SITE_USES_N1 NON-UNIQUE Cost = 1
54 INDEX UNIQUE SCAN HR_ORGANIZATION_UNITS_PK UNIQUE
55 TABLE ACCESS BY INDEX ROWID HR_ORGANIZATION_INFORMATION Cost = 2
56 INDEX RANGE SCAN HR_ORGANIZATION_INFORMATIO_FK2 NON-UNIQUE
57 INDEX UNIQUE SCAN HR_ALL_ORGANIZATION_UNTS_TL_PK UNIQUE
58 INDEX RANGE SCAN OE_ORDER_HEADERS_N4 NON-UNIQUE
59 TABLE ACCESS FULL FND_FLEX_VALUES Cost = 2
60 TABLE ACCESS BY INDEX ROWID FND_FLEX_VALUES Cost = 2
61 INDEX RANGE SCAN FND_FLEX_VALUES_N3 NON-UNIQUE
62 TABLE ACCESS BY INDEX ROWID OE_ORDER_LINES_ALL Cost = 2
63 INDEX RANGE SCAN OE_ORDER_LINES_N1 NON-UNIQUE
64 TABLE ACCESS BY INDEX ROWID MTL_PARAMETERS Cost = 2
65 INDEX UNIQUE SCAN MTL_PARAMETERS_U1 UNIQUE
66 TABLE ACCESS BY INDEX ROWID OE_ORDER_LINES_ALL Cost = 2
67 INDEX RANGE SCAN XXCTS_OE_OE_ORDER_LINES_ALL_N3 NON-UNIQUE
68 TABLE ACCESS BY INDEX ROWID OE_TRANSACTION_TYPES_TL Cost = 2
69 INDEX RANGE SCAN OE_TRANSACTION_TYPES_TL_U1 UNIQUE Cost = 1
70 TABLE ACCESS BY INDEX ROWID HZ_CUST_SITE_USES_ALL Cost = 2
71 INDEX UNIQUE SCAN HZ_CUST_SITE_USES_U1 UNIQUE
72 INDEX UNIQUE SCAN HR_ORGANIZATION_UNITS_PK UNIQUE
73 TABLE ACCESS BY INDEX ROWID HR_ORGANIZATION_INFORMATION Cost = 2
EXECUTION_PLAN
74 INDEX RANGE SCAN HR_ORGANIZATION_INFORMATIO_FK2 NON-UNIQUE
75 TABLE ACCESS BY INDEX ROWID HR_ORGANIZATION_INFORMATION Cost = 2
76 INDEX RANGE SCAN HR_ORGANIZATION_INFORMATIO_FK2 NON-UNIQUE
77 INDEX UNIQUE SCAN HR_ALL_ORGANIZATION_UNTS_TL_PK UNIQUE
78 TABLE ACCESS BY INDEX ROWID HZ_CUST_ACCT_SITES_ALL Cost = 2
79 INDEX UNIQUE SCAN HZ_CUST_ACCT_SITES_U1 UNIQUE
80 TABLE ACCESS BY INDEX ROWID XXCTS_OE_ORDER_HEADERS_ALL Cost = 2
81 INDEX UNIQUE SCAN XXCTS_OE_ORDER_HEADERS_ALL_U1 UNIQUE
82 TABLE ACCESS BY INDEX ROWID HZ_PARTY_SITES Cost = 2
83 INDEX UNIQUE SCAN HZ_PARTY_SITES_U1 UNIQUE
84 TABLE ACCESS BY INDEX ROWID HZ_LOCATIONS Cost = 2
85 INDEX UNIQUE SCAN HZ_LOCATIONS_U1 UNIQUE
86 TABLE ACCESS BY INDEX ROWID HZ_CUST_ACCOUNTS Cost = 2
87 INDEX UNIQUE SCAN HZ_CUST_ACCOUNTS_U1 UNIQUE
88 TABLE ACCESS BY INDEX ROWID HZ_PARTIES Cost = 2
89 INDEX UNIQUE SCAN HZ_PARTIES_U1 UNIQUE
90 TABLE ACCESS BY INDEX ROWID HZ_CUST_ACCOUNTS Cost = 2
91 INDEX UNIQUE SCAN HZ_CUST_ACCOUNTS_U1 UNIQUE
102 rows selected.

"Snapshot too old" for a report program

Similar Messages

Maybe you are looking for