Skip to main content

How to Install and Deinstall Oracle Text CTXSYS in 11g

How to Install and Deinstall Oracle Text CTXSYS in 11g


Below are the steps to install Oracle Text on our Oracle Database 11gR2
My DB version is 11.2.0.4

Installation Steps


  • Execute following script to install oracle text and CTXSYS user while connecting as sysdba.
            
sqlplus ‘/as sysdba’

spool /local/oracle/admin/tmp/text_install.txt
@$ORACLE_HOME/ctx/admin/catctx.sql oracle123 SYSAUX TEMP NOLOCK


Where :

oracle123 – is the ctxsys user password

SYSAUX – is the default tablespace for ctxsys

TEMP – is the temporary tablespace for ctxsys

LOCK|NOLOCK – ctxsys user account will be locked or not

  • The next step is to install appropriate language-specific default preferences.There is script which creates language-specific default preferences for every language Oracle Text supports in $O_H/ctx/admin/defaults directory, such as English(US), Danish(DK), Dutch(NL), Finnish(SF), French(F), German(D), Italian(IT), Portuguese(PT), Spanish(E), and Swedish(S). They are named in the form drdefXX.sql, where XX is the international license plate code. To manually install American default preferences, for example, log into sqlplus as CTXSYS, and run following statement:

sqlplus “CTXSYS”/”change_on_install”

@?/ctx/admin/defaults/dr0defin.sql “AMERICAN”;

connect /as sysdba

alter user ctxsys account lock password expire;

spool off

  • Verification Steps

Check to make sure that all Text objects were created in CTXSYS schema and correct version is installed also make sure you have no invalid objects
 
sqlplus ‘/as sysdba’

set pages 1000

col object_name format a40

col object_type format a20

col comp_name format a30

column library_name format a8

column file_spec format a60 wrap

spool text_install_verification.log

— check on setup

select comp_name, status, substr(version,1,10) as version from dba_registry where comp_id = ‘CONTEXT’;

select * from ctxsys.ctx_version;

select substr(ctxsys.dri_version,1,10) VER_CODE from dual;

select count(*) from dba_objects where owner=’CTXSYS’;
— Get a summary count

select object_type, count(*) from dba_objects where owner=’CTXSYS’ group by object_type;

— Any invalid objects

select object_name, object_type, status from dba_objects where owner=’CTXSYS’ and status != ‘VALID’ order by object_name;

spool off

De-installation Steps:


Text dictionary is removed by calling following script from SQL*Plus connected as SYSDBA:
 

spool /local/oracle/admin/tmp/oracletxt-remove.log
set lines 200 pages 1000

select comp_name, status, substr(version,1,10) as version from dba_registry where comp_id = ‘CONTEXT’;

select * from ctxsys.ctx_version;

select substr(ctxsys.dri_version,1,10) VER_CODE from dual;

select count(*) from dba_objects where owner=’CTXSYS’;

select object_type, count(*) from dba_objects where owner=’CTXSYS’ group by object_type order by 1;

select object_name, object_type, status from dba_objects where owner=’CTXSYS’ and status != ‘VALID’ order by object_name;

select * from dba_registry;

SQL> @?/ctx/admin/catnoctx.sql
SQL> drop procedure sys.validate_context;

select * from dba_registry;

spool off;

 

References
For Full instructions on oracle text install/deinstall you can refer to oracle support website notes: 979705.1 (10gR2) and 579601.1(11g)



If you like please follow and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

EBS 12.2 ADOP Interview Questions With Scenarios

EBS 12.2 ADOP Interview Questions With Scenarios Note: Check the patch cycle log is important to fix any issues.  Location: $ADOP_LOG_HOME Useful Adop Commands Click here 1.What is ADOP concept in oracle apps Online patching is the most important new feature in Oracle E-Business Suite Release 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied. 'adop' is the utility we use to apply patches in R12.2 2.What is PATCH_TOP directory in R12.2 In R12.2 there is a new directory location environment variable called $PATCH_TOP which points to $NE_BASE/EBSapps/patch $NE_BASE points to <Non-Editioned-filesystem-directory> Download the patch into the patch top directory and unzip it. This is the default location where the adop will look for patch files. If you are planning to put patches in non-defualt location then you need to use adop parameter 'patchtop=<patch_path>' to...