Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

hard to fix ORA-01555 snapshot too old: rollback segment number 26 with name "_SYSSMU26_1457499210$"

User_83ESOMar 5 2020 — edited Mar 9 2020

Hello,

We upgraded from 11gR2 to 12cR1.

We have 300GB of undo and 28800 undo retention

SQL> show parameter undo

NAME                                 TYPE                             VALUE

------------------------------------
-------------------------------- -----------------

temp_undo_enabled                    boolean                          FALSE

undo_management                      string                           AUTO

undo_retention                       integer                          28800

undo_tablespace                      string                           UNDOTBS

There is a particular query using a table say t1 with 540,453,510 rows and 20 indexes in 11g. It was not performing very well during 12cR1 upgrade test so that I created the following index

Idx_new (col1,col2,col3,col4) compress 3;

Instead of the existing index

Idx_old (col1,col2,col3)

I put the idx_old index invisible

The added column col4 in the new index allowed the query to do not filter anymore on table t1

However, since we went live in PROD, and after a couple of days of successful execution of that query it started failing with ORA-01555

Do you think that adding an index can provoke this new situation?

What do you suggest?

Thanks

Comments
Post Details
Added on Mar 5 2020
23 comments
2,897 views