Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.2.0.3 - Release: 10.2 to 11.2
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.2.0.3   [Release: 10.2 to 11.2]
Information in this document applies to any platform.
Symptoms

 When running a select statement an incorrect ORA-01555 with query_duration=0 is reported 
as a side effect of an PK index corruption under the following conditions:

* The error ORA-01555 is reported even if the database has just been restarted

* The error is always reproducible when running the select statement

* The "analyze validate structure cascade" command returns the same error:

SQL> analyze table MIPI_OWNER.MIPI_PUBL_OBJ_DATA validate structure cascade;
analyze table MIPI_OWNER.MIPI_PUBL_OBJ_DATA validate structure cascade
*
ERROR at line 1:
ORA-01555: snapshot too old: rollback segment number 12 with name "_SYSSMU12$" too small

* Without cascade option the analyze command doesn't report the error:
SQL> analyze table MIPI_OWNER.MIPI_PUBL_OBJ_DATA validate structure;
Table analyzed

* The "analyze validate structure" command executed for the PK index generates the same ORA-01555

* The trace file generated as a result of ORA-01555 with the following events set: 
SQL>alter system set events '10442 trace name context forever, level 1';
SQL>alter system set events '1555 trace name errorstack level 10';

contains the following information:

*** SERVICE NAME:(SYS$USERS) 2009-12-04 04:21:45.777
*** SESSION ID:(537.68) 2009-12-04 04:21:45.776
ORA-01555 occurred - Dump of diagnostics information
--- This does not indicate any errors
SSOLD: SQL ID: at4t8hum4xctr, Statement:
SELECT * FROM MIPI_PUBL_OBJ_DATA WHERE PUBLICATION_OBJECT_ID 
IN ('PUBOB19','PUBOB20') AND APPLICABLE_FOR=TRUNC(SYSDATE) ORDER BY 1 DESC
SSOLD: Query Length = 0 (sttm=1259900505, fchtm=1259900505, curtime=1259900505) 
SSOLD: Undo Retention = 10854
SSOLD: Scan Time Dump
env: (scn: 0x0219.2e46e8a8 xid: 0x0000.000.00000000 uba: 0x00000000.0000.00 
statement num=0 parent xid: xid: 0x0000.000.00000000 
scn: 0x0000.00000000 0sch: scn: 0x0000.00000000)
................
*** 2009-12-04 04:21:51.140
ksedmp: internal or fatal error
Current SQL statement for this session:
SELECT * FROM MIPI_PUBL_OBJ_DATA WHERE PUBLICATION_OBJECT_ID IN
 ('PUBOB19','PUBOB20') AND APPLICABLE_FOR=TRUNC(SYSDATE) ORDER BY 1 DESC
----- Call Stack Trace -----
calling call entry argument values in hex 
location type point (? means dubious value) 
-------------------- -------- -------------------- ----------------------------
ksedmp ktussto kturbk ktrgcm ktrget kdifxs1 qerixtFetch qertbFetchByRowID qerilFetch 
opifch2 kpoal8 opiodr ttcpip opitsk opiino opiodr opidrv sou2o opimai_real main start

Cause

The Primary Key Index is corrupted and ORA-01555 in this case is a false error.
Solution

Disable and enable the PK constraint in order to recreate the PK index associated with 
the primary key constraint and to solve the primary key index corruption.
Example :
SQL> alter table MIPI_OWNER.MIPI_PUBL_OBJ_DATA disable primary key;
SQL> alter table MIPI_OWNER.MIPI_PUBL_OBJ_DATA enable primary key;