Ora-01555 when export DB on RAC 11GR2

Hi all,
I run a full export on my 11GR2 DB and i have 6 errors on sysman tables :
ORA-31693: Table data object "SYSMAN"."MGMT_POLICY_ASSOC_EVAL_SUMM" failed to load/unload and is being skipped due to error:
ORA-02354: error in exporting/importing data
ORA-01555: snapshot too old: rollback segment number 21 with name "_SYSSMU21_2772229671$" too small
Do you have an idea ?
Thanks.

$ oerr ora 1555
01555, 00000, "snapshot too old: rollback segment number %s with name \"%s\" too small"
// *Cause: rollback records needed by a reader for consistent read are
// overwritten by other writers
// *Action: If in Automatic Undo Management mode, increase undo_retention
// setting. Otherwise, use larger rollback segmentsIf you increase undo_retention parameter you may also need to increase undo tablespace datafiles.

Similar Messages

ORA-39126 when exporting with expdp

Hi there,
I'm getting a crash on 11g 11.1.0.7 when exporting a schema using expdp:
expdp
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 3.096 GB
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA [TABLE_DATA:"NSNPL"."SYS_EXPORT_SCHEMA_02"]
ORA-22813: operand value exceeds system limits
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 7839
----- PL/SQL Call Stack -----
object      line object
handle    number name
0x14d81a160     18237 package body SYS.KUPW$WORKER
0x14d81a160      7866 package body SYS.KUPW$WORKER
0x14d81a160      2744 package body SYS.KUPW$WORKER
0x14d81a160      8504 package body SYS.KUPW$WORKER
0x14d81a160      1545 package body SYS.KUPW$WORKER
0x14d81db88         2 anonymous block
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA []
ORA-22813: operand value exceeds system limits
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.KUPW$WORKER", line 7834
----- PL/SQL Call Stack -----
object      line object
handle    number name
0x14d81a160     18237 package body SYS.KUPW$WORKER
0x14d81a160      7866 package body SYS.KUPW$WORKER
0x14d81a160      2744 package body SYS.KUPW$WORKER
0x14d81a160      8504 package body SYS.KUPW$WORKER
0x14d81a160      1545 package body SYS.KUPW$WORKER
0x14d81db88         2 anonymous block
Job "NSNPL"."SYS_EXPORT_SCHEMA_03" stopped due to fatal error at 00:57:23
This look awfully similar to bug 6991626 (cf ID 737618.1), however the database has already been successfully patched (and in fact even repatched) for this bug:
$ORACLE_HOME/OPatch/opatch lsinventory
Invoking OPatch 11.1.0.6.2
Oracle Interim Patch Installer version 11.1.0.6.2
Copyright (c) 2007, Oracle Corporation. All rights reserved.
Oracle Home       : /opt/oracle/db11g
Central Inventory : /opt/oracle/inventory
   from           : /etc/oraInst.loc
OPatch version    : 11.1.0.6.2
OUI version       : 11.1.0.7.0
OUI location      : /opt/oracle/db11g/oui
Log file location : /opt/oracle/db11g/cfgtoollogs/opatch/opatch2010-06-02_08-23-53AM.log
Lsinventory Output file location : /opt/oracle/db11g/cfgtoollogs/opatch/lsinv/lsinventory2010-06-02_08-23-53AM.txt
Installed Top-level Products (2):
Oracle Database 11g                                                  11.1.0.6.0
Oracle Database 11g Patch Set 1                                      11.1.0.7.0
There are 2 products installed in this Oracle Home.
Interim patches (6) :
Patch 6991626      : applied on Tue Jun 01 22:35:32 WET 2010
   Created on 14 Oct 2008, 23:25:07 hrs PST8PDT
   Bugs fixed:
     6991626
[...]Does anyone have an idea on what might be the culprit here?
Thanks for your help,
Chris

Hi Prathmesh,
in fact I saw this very thread before and I made sure that both solutions were applied. Moreover as I said patch 6991626 had already been applied earlier, precisley to fix this problem, and I've had been able to successfully export other albeit somewhat smaller schemas (500M instead of 3GB) in the last few months. This is why I was so puzzled to see that exact bug raise its ugly head again. As far as I can tell I didn't do any modification to the DB since that last patch in nov. 2009. In fact the DB has been running pretty much untouched since then.
I even tried yestereday to reinstalled the patch again; opatch does the operation gracefully, first rolling back the patch then reapplying it again, with only a warning about the patch being already present. However the pb does not get fixed any better.
Thanks a lot for your help,
Chris

ORA-01555 when performing refresh of materialized views via DBMS_JOB

All,
With this project needing to be finished soon and an issue occuring on the local database, I am hopefuly one of you will have the answer or resolution so that I may complete this project soon....
Here is the setup..
10g database (remote)
9i database (local
DB Link from local to remote database
103 materialized views in local database that are refreshed by pulling data from dblink to remote database.
A PL/SQL procedure has been created which sets the v_failures variable = 0 and then performs a check to see if the current job has a failure and if so, inserts that value into the v_failures variable. When that reaches "1", then the procedure does nothing and closes out. If the failures are equal to "0" then it performs a DBMS_MVIEW.REFRESH procedure for each materialized view.
This worked the first time but its continually failing now with the ORA-01555 error (snapshot too old). From what I can tell, the dbms_job duration is 4 seconds and the Last_Exec is 2m 7s after it starts (8:30 PM). With that said, our DBAs working o nthe project have increased the Undo_Retention settings and assure us that shouldn't be the problem. Odd thing is, this never happened in the dev environment when we were developing/testing - only in the production environment once it got migrated.
I am looking for possible causes and possible solutions to the ORA-01555 error. A sample of the code in my procedure is below:
CREATE OR REPLACE PROCEDURE Ar_Mviews IS
V_FAILURES NUMBER := 0;
BEGIN
BEGIN
          SELECT FAILURES INTO V_FAILURES FROM USER_JOBS WHERE SCHEMA_USER = 'CATEBS' AND WHAT LIKE '%DISCO_MVIEWS%';
          IF V_FAILURES = 1 THEN NULL;
          ELSE
DBMS_MVIEW.REFRESH ('AR_BATCH_RECEIPTS_V', 'C');
          DBMS_OUTPUT.PUT_LINE(V_FAILURES); END IF;
END;
BEGIN
     SELECT FAILURES INTO V_FAILURES FROM USER_JOBS WHERE SCHEMA_USER = 'CATEBS' AND WHAT LIKE '%DISCO_MVIEWS%';
          IF V_FAILURES = 1 THEN NULL;
          ELSE
DBMS_MVIEW.REFRESH ('AR_BATCHES_ALL_V', 'C');
          DBMS_OUTPUT.PUT_LINE(V_FAILURES); END IF;
END;
END Ar_Mviews;
---------------------------------------------------------------------------------------------------------------

We are doing complete refreshes and doing it that way for consistency in the data presented. Because some materialized views are dependent upon data in other materialized views, we have them ordered in a procedure so that when one finishes, the next starts and they are also in a specific order as to ensure accurate data.
The condition for v_failures is done so that the job doesn't get, lets say, 90% finished and hit an error and start over again. We do the IF statement which results in NULL (do nothing) so that the job doesn't repeat itself over and over again. If one MV fails, we have to consider the job a failure and do nothing else because the one MV that failed may have been a dependency of another MV down the line. (i.e. MV7 calls MV3 and MV3 fails, so the whole job fails because MV7 can't be accurate without the most current data from MV3).
As well, this is being performed in off-business hours after backup to tape, etc. and prior to start of business so that no one is using the system when we run this job. That won't always be the case when we move to high availability with this system for varying time-zone end-users.
I hope I have answered your question and look forward to continued feedback.
Thanks!

ORA-01555 when UNDO Management is Auto

Hi,
I am using Oracle 10g 10.2.0.3 on linux 64 bit
My UNDO_MANAGEMENT is AUTO and Tablespace size is Auto
Undo_retention=15
Today morning, I have received following error in Alert log
ORA-01555 caused by SQL statement below (SQL ID: 9yfaam0vn51b5, Query Duration=1257324485 sec, SCN: 0x0000.084ad6ea):
EM is showing following
Snapshot Too Old Error detected: SQL ID 9yfaam0vn51b5, Snapshot SCN 0x0000.084ad6ea, Recent SCN 0x0000.084e39df, Undo Tablespace UNDOTBS1, Current Undo Retention 943.
How dio i find that which query created a problem as SQL ID: 9yfaam0vn51b5 is not in table v$sql
Do i need to do anything or Oracle will take care of UNDO?
Regards

a mock up
SQL> select max(maxquerylen)
2            from v$undostat;
MAX(MAXQUERYLEN)
62057
SQL> show parameter undo
NAME                                 TYPE        VALUE
undo_management                      string      AUTO
undo_retention                       integer     25000
undo_tablespace                      string      UNDOTBS1
SQL> select (62057/60)/60 query,(25000/60)/60 retention
2    from dual
3 /
     QUERY RETENTION
17.2380556 6.94444444Above query executing tenure is 17 hours while undo retention is approximate 7 hours,either change retention period to 20% extra with yours query execution tenure and then check yours query again.
at least set undo retention to 75000,also better approach to tune query why its too taking so much time?
Khurram

ORA-12560 when logging as SYSDBA in 11gR2 db installed in Windows 7

I have installed Oracle 11gR2 in Windows 7. I setup all listener and tnsname file and can login to the database like following:
sqlplus cisadm/cisadm@demo
However, it throws ORA-12560 error when loggin as sysdba as below:
sqlplus / as sysdba
I have read some previous post and already set ORACLE_SID=DEMO. But it still doesn't work.
I wonder if my 11gR2 was not installed properly as I also cannot use Administartion Assistant for Windows which throws "MMC could not create snap-in" error.

This because of previously installed database.
I feel that you have un installed but you have not completely removed Oracle Instances.
After the deinstall from Oracle Installer, Oracle leaves some services still running and some folders which wont be deleted .
You have to manually delete these folders.
Or follow these steps and try.
1) First step is to stop all the services relevant to Oracle database 11g. In windows 7 navigate from Start->Control Panel->Administrative Tools->Services
2) Click on Oracle Service OracleServiceORACLE_SID,OracleDBConsoleOracle_SID,OracleOraDB11g_homeTNSListener and Click on Link stop. Also stop these services if they are enabled - OracleMTSRecoveryService, OracleJobSchedulerOracle_SID
3) Now its time to remove references from Registry. In Windows 7 search box type regedit. This opens the Registry Editor
4) Click on HKEY_LOCAL_MACHINE. Click on Software. Choose Oracle Folder. Delete it completely. Also Remove HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services and remove oracle relevant entries from there (All will have either Oracle or Ora prefix)
5) Remove the PATH variable from environment variables if set
6) Delete the database files manually from the local machine
In this process of deleting files I got an error which said windows process WmiPrvSE.exe process makes use of certain dlls such as oracell11.dll,oraldapclnt11.dll etc. I renamed the bin folder to bin_old. I restarted the system and it fixed the issue
Regards,
Tirumala Dixit.

ORA-00904 when exporting job queues

Hi!
I have a 8.1.6.3.7 database (although you only see 8.1.6.3.0) when you log in) which I'm trying to export.
Everything is fine until the time comes to export job queues. I then get the following error messages:
EXP-00008: ORACLE error 904 encountered
ORA-00904: invalid column name
EXP-00000: Export terminated unsuccessfully
Now, I've just spent my morning looking through the discussion forums to see if anyone else had this error, but no luck.
What I've done:
- Rerun catexp: no change
- ensured that I'm running the same version of the RDBMS and export (v8.1.6.3(.7) and 8.1.6.3.0): ok?
Any ideas anyone?
Thanks,
Kevin

Hi Prathmesh,
in fact I saw this very thread before and I made sure that both solutions were applied. Moreover as I said patch 6991626 had already been applied earlier, precisley to fix this problem, and I've had been able to successfully export other albeit somewhat smaller schemas (500M instead of 3GB) in the last few months. This is why I was so puzzled to see that exact bug raise its ugly head again. As far as I can tell I didn't do any modification to the DB since that last patch in nov. 2009. In fact the DB has been running pretty much untouched since then.
I even tried yestereday to reinstalled the patch again; opatch does the operation gracefully, first rolling back the patch then reapplying it again, with only a warning about the patch being already present. However the pb does not get fixed any better.
Thanks a lot for your help,
Chris

RME-02105 AND ORA-00955 WHEN EXPORTING APPLICATION SYSTEM

WHEN TRYING TO EXPORT APPLICATION SYSTEM FROM RON.
and after resbonding to the messsage "Export tables are already populated,you want to clear them?" by "yes" ,I RECIEVED THE ABOVE ERRORS .
I USE ORACLE databse 8.1.7 with Oracle Designer 6i Version 6.5.52.1.0.
is ther any help?

OK,
I have read the link and I have talked with our DBA. He says taht we are working with a 9.2 (9.2.0.7 exactly) version. In this version he believes taht the only way to use the flashback query feature was through the use of the utility package DBMS_FLASHBACK. Therefore, the sentence ALTER database flashback that would work on a 10g version off does'nt have sense on 9.2.
Anyone knows how to avoid the flashback error in a 9.2 environment?

ORA-01555?

I am trying to create an index on a huge table around(200gigs). I have 10gigs undo which is autoextensible to 50 gigs.
Earlier the undo_retention was 900, and i tried to create the index. It failed with ORA-01555.
I increased the undo_retention to 7200 but again it failed. I am running 10g with undo_management=auto
What should i do?

Libra DBA wrote:
I looked into the delayed block cleanout and ran
I am using UNDO_MANAGEMENT=AUTO and the UNDOTBS1 and UNDOTBS2 of 5 gigs with autoextend upto 50 gigs.There are servral things that could cause ORA-01555 when using Automatic Undo Management. However, there are simply things that need to be checked when using it.
First of all, one mistake we make is to use AUTO EXTEND for UNDO and TEMPORARY Segments. Please calculate/estimate and allocate the required space to UNDO and TEMP and turn off AUTO EXTEND on them.
Secondly, check your UNDO_RETENTION setting and see if it is correctly set for your longest running transactions.
Thirdly, check the application code for the DOs and DONTs to pervent ORA-01555. If you do not get all these right, 100GB will not be enough for you to complete your transactions. But if you get them right, only 20GB out of the 50GB may be sufficient for you.
I would suggest you read more on Automatic Undo Management. If you are using Enterprise Manager, Undo Advisor will help you to estimate your UNDO Space allocation.

ORA-01555: snapshot too old: - export- RAC

We are getting ORA-01555: snapshot too old: rollback segment number , in 3 node RAC while doing export for multiple schemas. undo rentention is set more than a day for all nodes,. undo tablespace has got enough space. Can anyone tell me what i need to look here.

hi,
can you please post below details...
oracle version,os version?
and what export command your using...
hope your using consistent =y ..while using this parameter we require big size of undo tablespace size....
refer metalink note...113450.1
thanks,
DBC,
Sr DBA,
Oracle certified expert.

ORA-00354, ORA-00353 on RAC 11gR2

Hello All,
I have a database Oracle RAC 11gR2 on OEL linux 5.5 32bit.
When i am trying startup my database I am facing the below errors: this error is occuring on the startup of any node
ERROR at line 1:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 2651 change 1172351 time 10/12/2011
13:22:43
ORA-00312: online log 1 thread 1: '+DATA/orcl/onlinelog/group_1.261.761845161'It seems that my online redo log is corrupted. how can i solve that ?
knowing that my database is running in NOARCHIVELOG mode and i do not have any backup.
and why i am not able to start up any of the nodes? redo logs is not related to each node seperately ?
I tried: srvctl start instance -d orcl -i orcl1 or srvctl start instance -d orcl -i orcl2
but the same error, where is the High Availibilty in that case, the redo log file group_1 is for thread 1 only. SHould not be able to start Instance 2?
Regards,
Edited by: NB on Oct 13, 2011 5:12 PM

since my database is runing in NOARCHIVELOG mode and i have no backups and the current is logfile was the corrupted one and my database was not starting.
I solved that by ceating a pfile and adding the : allowresetlogs_corruption=TRUE
regards,

ORA-01555 error when assigning values based on geometry

Hello,
I have a table with 220,000+ records with street information, and I am trying to assign a municipal area (stored in another table) based on the geometry of the road line and the geometry of the municipal boundary.
CREATE TABLE TEMP AS SELECT A.ID, B.AREA FROM ROADS A, PLACES B WHERE B.TYPE IN (33,35,36,37) AND mdsys.sdo_relate (a.geometry,b.geometry,'
mask=inside querytype = window')='TRUE';
This took a long time to run and it came back with a series of errors, one of which was ORA--01555 'snapshot too old'. I was running other queries on the table (in a separate SQL window) because I'm under a deadline, so i figured that doing multiple things at one time while the spatial query was running was causing the problem. I didn't have time to run it again (it was the end of the day when the error came up, conveniently) so I am trying to work out a solution to this issue.
Would it be better if I: a) ran the statement again on the whole dataset and did nothing else while it is running, even though it will still take a while, or
b) broke it up into groups of 50,000 records and run the statement on one group at a time and hope for the best.
Thanks in advance!

Assuming you have less municipal areas than roads, the query should perform better by specifying the join order:
CREATE TABLE TEMP AS (
     SELECT /*+ ORDERED */ A.ID, B.AREA
     FROM PLACES B, ROADS A
     WHERE B.TYPE IN (33,35,36,37)
     AND mdsys.sdo_relate (a.geometry, b.geometry,'mask=inside querytype = window') = 'TRUE');Also, are you sure 'inside' is the right mask to use here? What if a road intersects the edge of the municipality? In that case it wouldn't be returned by this query.

ORA-01555 with ORA-02063 when submitted Concurrent Requests

Hello,
My development team has reported some CM Requests got failed with some errors.When i checked the request log file i saw :java.sql.SQLException: ORA-01555: snapshot too old: rollback segment number with name "" too small ORA-02063: preceding line from EIHFDM .Could you please help me out this to solve this issue.
We are on Oracle Database 10g Release 10.2.0.5.0 - 64bit
Application 11.5.10
I have checked the UNDO Parameter values
ACTUAL UNDO SIZE (MEGS) UNDO RETENTION (Secs)                OPTIMAL UNDO RETENTION (Secs)
                                 304849                               40000                4860
Thanks,
Prabhat.

Hi Asif,
This is a customized program.
I have checked the UNDO Parameter values
SQL> show parameter undo
NAME                                 TYPE        VALUE
_in_memory_undo                 boolean     TRUE
_undo_debug_usage              integer     2
undo_management                 string      AUTO
undo_retention                       integer     40000
undo_tablespace                    string      APPS_UNDOTS
SQL>
ACTUAL UNDO SIZE (MEGS) UNDO RETENTION (Secs)                OPTIMAL UNDO RETENTION (Secs)
                                 304849                               40000                4860

Listener.ora file on RAC 11gR2 with SCAN

Hello,
I have 11.2.0.1 Rac with 2 nodes configured to work with SCAN.
The following listener.ora file was created during the rac installation.
(I only changed the name of the instance to XYZ in the output bellow).
There is only one listener.ora file for both the rdbms instance and the ASM instance.
Is it a good best practice or should i consider to create a seperate listener.ora
to the rdbms instance and to the ASM instance ?
The listener.ora is look as follow:
LISTENER=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))) # line added by Agent
LISTENER_XYZ_=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_XYZ)))) # line added by Agent
LISTENER_SCAN3=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN3)))) # line added by Agent
LISTENER_SCAN2=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN2)))) # line added by Agent
LISTENER_SCAN1=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN1)))) # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN1=ON # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN2=ON # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN3=ON # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_XYZ=ON # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON # line added by AgentLSNRCTL> show current_listener
Current Listener is LISTENER
LSNRCTL> services
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:9195 refused:0 state:ready
LOCAL SERVER
Service "XYZ_SRV" has 1 instance(s).
Instance "XYZ_1", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:803987 refused:0 state:ready
LOCAL SERVER
Service "XYZ" has 1 instance(s).
Instance "XYZ_1", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:803987 refused:0 state:ready
LOCAL SERVER
Service "XYZ_XDB" has 1 instance(s).
Instance "XYZ_1", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: xyzdb-11-1, pid: 11923>
(ADDRESS=(PROTOCOL=tcp)(HOST=xyz-11-1)(PORT=36594))
The command completed successfullyThanks

Is it a good best practice or should i consider to create a seperate listener.ora to the rdbms instance and to the ASM instance ?No, you should not be creating separate listener for each Grid & DB. Listener is node specific resource. Oracle recommends in RAC environment the listener should be configured from GRID home and it will be able to serve both Grid and DB services.
It also helps in maintenance where as you can upgrade DB without bothering Listener, can have several db instances, and can have several versions of DB supported by a single listener.
I hope this answers your question. if yes please mark the question as answered and do not forget marking answer as a Correct answer.
Edited by: pgoel on Mar 5, 2011 10:50 PM

When will ora-01555 error not be recorded in alert file?

Application side repeatably gets ora-01555 error, but from alert log, there is no such error recorded. I recalled normally this error will be recorded, so under which condition we can't find this error in alert file?

You would get ORA-0155 on a LOB if
a) the LOB storage has been defined with PCTVERSION which is low (Oracle doesn't use Undo Segments but uses space in the LOB Segment itself and if this is inadequate for multiple updates, an ORA-0155 is raised, which is not really related to Undo Segments but the space in the LOB segment)
b) the LOB storage has been defined with RETENTION which is low
(Even if you increase undo_retention, you'd have to modify the LOB segment to PCTVERSION and then back to RETENTION for it to use the new undo_retention value).
See MetaLink Notes 162345.1, 66431.1 and 563470.1
Since the ORA-01555 error doesn't really relate to Undo segments, I believe that it would not be reported in the alert.log file -- but I haven't verified this.
Hemant K Chitale
http://hemantoracledba.blogspot.com

ORA-01555 in RAC

Hello experts,
I am having 4 node oracle 9i on IBM AIX .
We are having different size of undo tablespace but same value of undo_retention in each node .
In our application we are running reports from a particular node and getting ORA - 01555 frequently. what if i increase the undo_retention in this node only ?
Regards
Mals

Thank you Hoek,
Our application is designed such that maximum load/ activity in on node one thats why undo tablespace of 50 GB.
Rest of the nodes are not much active so have less size of undo 15 GB each .
So longest running queries are different on each node ( node one 90036 and node four 12948 ) Than how the same undo_retention = 25000 solves the purpose ?
Regards

Ora-01555 when export DB on RAC 11GR2

Similar Messages

Maybe you are looking for