Oracle Text and Rolling Upgrade with Logical Standby

You can use a logical standby database to perform a rolling upgrade of Oracle Database. During a rolling upgrade, you can run different releases of Oracle Database on the primary and logical standby databases while you upgrade your databases, one at a time, incurring minimal downtime on the primary database. Oracle Text takes full advantage of upgrading Text indexes during a rolling upgrade.

All CTX PL/SQL procedures are fully replicated to the standby database and, therefore, are upgraded, except with certain limitations, as described, for these procedures:

See Also:

Oracle Data Guard Concepts and Administration for information on creating a logical standby database to perform rolling upgrades

CTX_DDL PL/SQL Procedures

Oracle Database uses rowids internally for the construction of indexes. The following CTX_DDL procedures are not fully replicated to the standby:

  • ADD_MDATA

  • REMOVE_MDATA

CTX_OUTPUT PL/SQL Procedures

Only CTX_OUTPUT.ENABLE_QUERY_STATS and CTX_OUTPUT.DISABLE_QUERY_STATS are replicated. This means that if Oracle Text logging is enabled on the primary database before running an operation that causes logging, then the operation will run with logging on the primary database, but will run without logging on the secondary database.

CTX_DOC PL/SQL Procedures

When the following CTX_DOC procedures are used with Oracle Text Result Tables, the data stored in the tables is replicated. When these procedures are used without Result Tables, they are not replicated.

  • CTX_DOC.SET_KEY_TYPE

  • CTX_DOC.FILTER

  • CTX_DOC.GIST

  • CTX_DOC.MARKUP

  • CTX_DOC.TOKENS

  • CTX_DOC.THEMES

  • CTX_DOC.HIGHLIGHT

  • CTX_DOC.FILTER_CLOB_QUERY

  • CTX_DOC.MARKUP_CLOB_QUERY

  • CTX_DOC.HIGHLIGHT_CLOB_QUERY

See Also:

Oracle Data Guard Concepts and Administration for information on performing a rolling upgrade for minimal downtime on the primary database