Per the Spotlight on Oracle Release Notes:
Inability to open a STANDBY Oracle database after installing a Spotlight user on its PRODUCTION database: The need for reliable access to the information on a PRODUCTION ("live") Oracle database often means that the database, and all changes made to it, are copied to a STANDBY database. If the live database fails or is taken offline, the STANDBY database can be used in its place.
Spotlight makes changes to the SYS schema of the database by creating a number of x$ views. These views, when copied to the STANDBY database, are labeled as invalid, and will prevent a user from opening STAND database.
Oracle notes (8i)
Inability to open a STANDBY Oracle 8i database after installing a Spotlight user on its PRODUCTION database: The need for reliable access to the information on a PRODUCTION ("live") Oracle database often means that the database, and all changes made to it, are copied to a STANDBY database. If the live database fails or is taken offline, the STANDBY database can be used in its place.
When you create a Spotlight connection to the production database, you also install a Spotlight user on the database. In doing so, Spotlight makes changes to the SYS schema of the database by creating a number of x$ views. These new views, when copied to the STANDBY database, are labeled as invalid, and will prevent a user from opening the STANDBY database.
This is not a problem while you are using only the PRODUCTION database. However, if you intend to take the PRODUCTION database offline and use the STANDBY, we recommend that you first drop the Spotlight x$ views in the PRODUCTION database.
To obtain the list of x$ views that should be dropped, contact Quest Software support.
If the PRODUCTION database fails unexpectedly, and you need to use the STANDBY database, you must first log onto the STANDBY database via a SYSDBA account and drop the Spotlight x$ views.
Note:
Internal testing by Quest Software indicates that this problem does not occur in Oracle versions 9i and 10g. However, since Quest cannot test this for all versions of Oracle on all operating systems, you should thoroughly test your own standby databases.
Note:
If you want to switch from the production to the standby database, then you should drop the views in the production database prior to switching. If you just switch over without first dropping the views from the production database, then you will need to login to the standby as SYSDBA and drop the marked-as-invalid views.
If you then want to run Spotlight on the standby database, then you would need to re-create the objects via the Spotlight User Wizard.
The dropSoO_objects.sql attached shows which objects should be dropped (also see read me attached)
The SoO Objects.doc shows a list of database objects created for Spotlight
