Oracle Text: Re-installation and Rebuilding of Applications R12 Oracle Text Indexes
(Doc ID 743720.1)
Last updated on JUNE 07, 2021
Applies to:Oracle Applications DBA - Version 12.0.4 to 12.1.3 [Release 12 to 12.1]
Oracle Product Hub - Version 12.1.2 to 12.1.2 [Release 12.1]
Oracle Common Applications Calendar - Version 12.2.8 to 12.2.8 [Release 12.2]
Information in this document applies to any platform.
This article addresses the steps that must be completed in order to rebuild the Oracle Applications Oracle Text indexes after re-installing Oracle Text in Oracle Applications Release 12 (12.0.x). Text index re-installation in R12.1.x using this document has not been validated by the author. Text index re-installation requirements for releases prior to R12 can be found in Note 185414.1 and Note 312640.1.
If it is necessary to drop the Oracle Text user CTXSYS for any reason, then all of the Oracle Applications Oracle Text indexes must be rebuilt. Dropping the CTXSYS user should only be performed under the advise of Oracle Support Services.
This procedure is for use by Applications DBA's, and should be used when it is necessary to re-install Oracle Text in Oracle Applications R12 (12.0.4 and higher). The steps outlined here address re-creating the Applications' Oracle Text indexes only, and do not address any of the related maintenance requirements (sync and/or optimize operations required in order to maintain Oracle Text indexes).
The Oracle Text indexes identified and steps outlined in this procedure are based on an Applications 12.0.4 Vision database environment. Although each Oracle Applications, Production install will vary in the use and installation of Oracle Text indexes, and associated functionality specific to the modules, the steps outlined here will apply across all environments.
Use of this procedure is intended under the direction of Oracle Support Services only.
Also note requirements for client connectivity based on RDBMS release as outlined in Note 207303.1. Unsupported clients may produce extraneous errors when attempting to execute these procedures.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document