The release notes discuss the following restriction about the Standby database:
"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.
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."
Is this still the case in the latest version and if so, will there be fix or a workaround, because if the primary database crashes you cannot drop the x$ views anymore?