ORA-12008: error in materialized view refresh path

ORA-12012: error on auto execute of job 85223
ORA-12008: error in materialized view refresh path
ORA-01555: snapshot too old: rollback segment number 11 with name "_SYSSMU11$" too small
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2251
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2457
ORA-06512: at "SYS.DBMS_IREFRESH", line 685
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1


Received above error.  

ACTUAL UNDO SIZE [MByte] UNDO RETENTION [Sec]      NEEDED UNDO SIZE [MByte]
------------------------                        ------------------------- ------------------------
                   30000                        900                                     3756.25781


Had received similar error before and we increased the undo tablespace.   before we increased the undo tablespace it was
ACTUAL UNDO SIZE [MByte] UNDO RETENTION [Sec]      NEEDED UNDO SIZE [MByte]
------------------------                                  ------------------------- ------------------------
                   15000                                   900                                     3233.03906


Please advise.
NoreenaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

slightwv (䄆 Netminder) Commented:
Please provide more information about your systems.

Is the Materialized View based on local or remote tables?

If local, maybe increase the undo retention.

If remote, the issue may be in that database.  Check the alert log and any trace files to see if it is actually the remote DB causing the issue.

There is a discussion about that here:
https://community.oracle.com/thread/627825?tstart=0
0
sdstuberCommented:
>>> Had received similar error before and we increased the undo tablespace.

Unless your MV query is excessively slow, increasing the undo is the only option.

If you can't make the undo bigger, then you'll need to reduce the number of transactions that occur between the time the refresh starts and when it finishes.

You can do that either by doing less work in other sessions (which is not usually an option)
or, by making the refresh query faster so it finishes before your undo space fills due to those other transactions.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.