Oracle Full-text Indexing Setup Steps

Several project groups have already started using Oracle's Full-text indexing. Oracle's lexical analyzer is not smart enough for the lexical analysis of the ZHS16GBK character set, and can only be mechanically matched to the word unit. There is a new Chinese parser chinese_lexer for the UTF8 character set, and the efficiency has been greatly improved. The validated and collated documentation on how to set up the Oracle Full-text indexing is available to all, for 8i, 9i platforms.

For DB2, there is a plug-in called tie (text information Extend) that can be full-text indexed, but it is said to have a primitive syntax analysis. It is reported that using cm (Content Manager) can do a good full text search, but need to install a lot of software, is not suitable for simple application.

I. Creating a Database

1, choose Jserver and Intermedia two options when you use Dbassist to create a database.

2, check whether your database installed Intermedia, you can check whether there are Ctxsys users and Ctxapp roles (role).

3. Without this user and role, it means that the Intermedia feature is not installed when the database is created. You must modify the database to install this feature. Modify Process:

Run the $ORACLE _home/bin/dbassist, select ' Modify database ', and then select Jserver and intermedia when you choose DB Features (Installation intermedia must be installed jserver at the same time).

Two. Set Extproc

Oracle implements intermedia through the ' External invoke function ' (external procedure), so setting Extproc correctly is a key step. After the general database has been installed jserver and intermedia, Extproc has been set up in Listener.ora and Tnsnames.ora.

1, test extproc is normal

Restart the listener, and then use tnsping to test whether the configuration is correct,

Run under command line

Tnsping Extproc_connection_data or

Tnsping Extproc_connection_data.world

If configured correctly, it will display:

Attempting to Contacts (address= (PROTOCOL=IPC) (Key=extproc) OK (140 ms)

If correct, you can skip 2, 3 steps. Otherwise, set the Listener.ora and Tnsnames.ora files in steps 2, 3, and make sure that you restart the listener after you modify it, but you do not need to restart the database.

2, set Listerner.ora

If tnsping fails, you need to configure listener to enable it to listen for requests for Intermedia calls. You can configure it by running $oracle_home/bin/netassit, or you can modify the configuration file manually: $ORACLE _home/network/admin/listener.ora, and then restart Listener.

The following is an example of how to manually modify a configuration file:

Open the Listener.ora file, and before you modify it, it usually has the following contents (assuming the default LISTENER is used): LISTENER =
(DESCRIPTION =
(address = (PROTOCOL = TCP) (HOST = MYDATABASE) (PORT = 1521))
)
Sid_list_listener =
(Sid_desc =
(Global_dbname = Mydatabase.world)
(Oracle_home =/u01/app/oracle/product/8.1.6)
(Sid_name = MyDatabase)
)

This listener has not yet been configured with Extproc, so it is necessary to increase the monitoring of extproc by adding description and Sid_desc separately. The modified Listner.ora is as follows: LISTENER =
(Description_list =
(DESCRIPTION =
(address = (PROTOCOL = TCP) (HOST = MYDATABASE) (PORT = 1521))
)
(DESCRIPTION =
(address = (PROTOCOL = IPC) (KEY = Extproc))
) )
Sid_list_listener =
(Sid_list =
(Sid_desc =
(Global_dbname = Mydatabase.world)
(Oracle_home =/u01/app/oracle/product/8.1.6)
(Sid_name = MyDatabase))
(Sid_desc =
(program = Extproc)
(Sid_name = Plsextproc)
(Oracle_home =/u01/app/oracle/product/8.1.6)
) )

Note that the host above, Global_dbname,sid_name,oracle_home should fill in the actual value of your database, but program a must fill in extproc.