Home » Server Options » Text & interMedia » Help requested - context cartridge
Help requested - context cartridge [message #366434] Thu, 15 June 2000 09:02 Go to next message
Sriram K
Messages: 1
Registered: June 2000
Junior Member
Hi,

I require a help regarding Context cartridge.

I have Oracle8i Release 8.1.5.0.0 (with Java option) installed on Sun OS 5.7 (Solaris 2.7)

I need to use Context Server for my search & other facilities in my application. I don't know whether I have included this context cartridge during the oracle installation.

I request your help in the following:
Is there any way to find out whether my database has context cartridge option turned on or not.
If not, how to add context cartridge to my database. (or should there be a reinstallation?)
Thanks in anticipation.

Sincerely,
Sriram K
Re: Help requested - context cartridge [message #366439 is a reply to message #366434] Mon, 07 August 2000 07:33 Go to previous message
sharan alva
Messages: 57
Registered: November 1999
Member
There are a couple of ways of doing this.
1. select in dba_users to see if you have a ctxsys user... If this user is present then context Intermedia is installed.
2. start up one server with M personality and this if this comes up it's header will show you the version.
Intermedia can be installed via the installer or can be manually installed using the scripts that come along with the installation..
I. Introduction
---------------

This guide describes the installation process of InterMedia Text on 8i. It is
originally written for 8.1.5 - but it also works for 8.1.6. Changes for 8.1.6
is marked with <8.1.6!> in the actual section.

Read this guide sequentially - section by section. Be aware that this
product may be installed automatic by the DB Assistant or manually. This means
you have to choose EITHER section II or section III for the installation itself.


II. Abbreviations
-----------------

IMT - InterMedia Text
DBCA - Database Configuration Assistant

III. Pre-Installation & Requirements
------------------------------------

Use these sections to ensure that the product InterMedia Text has been properly
installed by the Installer and to set the environment. It is assumed that the
requirements for the database are fullfilled (see the release note and the
installation guide for the database server.)

A)THE FILES HIERARCHY

Before starting, make sure that the Intermedia Software tree is installed.
Below is a description of the critical parts of this tree (there are others;
for instance sample, migrate, and docs directories):

On Unix:

- ?/bin/ctxsrv
Oracle8i still supports the ctxsrv server. However, the only valid
personality mask is M. You need to run it only when you want background
DML. Batch DML (sync) does not require a running server.

- ?/ctx/admin
Data dictionary scripts.

- ?/ctx/admin/defaults
Language-specific default preferences.

- ?/ctx/bin
This directory is for user-defined filters, which we'll talk about later.
This directory should also contain the ctxhx program which is used by the
INSO filter.

- ?/ctx/data
This directory has data files needed by interMedia Text, which includes the
linguistic lexicon files, the Xerox stemming files, and the Korean lexer
dictionary. If you get strange internal errors in linguistics, stemming,
etc., check this directory.

- ?/ctx/lib
This directory has platform-specific shared libraries and template files
used by the INSO filter. It also contains the safe callout used by indexing
and document services libctxx8.so (HP-UX: libctxx8.sl).

On NT:

- ?/bin/ctxsrv.exe
Oracle8i still supports the ctxsrv server. However, the only valid
personality mask is M. You need to run it only when you want background
DML. Batch DML (sync) does not require a running server.

- ?/ctx/admin
Data dictionary scripts. (<8.1.6!>: Upgrade scripts for ugrading from
8.1.5).

- ?/ctx/admin/defaults
Language-specific default preferences.

- ?/ctx/bin
This directory is for user-defined filters, which we'll talk about later.
This directory should also contain the ctxhx program which is used by the
INSO filter. It also has platform-specific shared libraries and template
files used by the INSO filter. It also contains the safe callout used by
indexing and document services oractxx8.dll.

- ?/ctx/data
This directory has data files needed by interMedia Text, which includes the
linguistic lexicon files, the Xerox stemming files, and the Korean lexer
dictionary. If you get strange internal errors in linguistics, stemming,
etc. check this directory.

B)INIT<SID>.ORA.

Check the values of the following parameters in the parameter file:

- text_enable.

This parameter had to be set to 'true' in Context(Pre interMedia Text
8.1.5). Ensure that the parameter now is set to false, as described below:

text_enable = false

- shared_pool_size.

The size of the shared pool SGA area is defined by the 'shared_pool_size'
parameter. You have to set this to at least 115343336. The DB Assistant
will even fail if this size is below this value.

shared_pool_size = 115343336

NOTE! This is the entry for the MINIMUM value of shared pool during
installation of IMT. After installation this size may be reduced.

- db_block_size.

To get the most of of your environment you should set the
value of this parameter to 8192. Be aware that you have to recreate the
database if you have to change this value later.

db-block_size = 8192

The size of the data buffer cache SGA area is defined by the two parameters
'db_block_size' and 'db_block_buffers'.

- compatible.

The installation (section II or III) will fail if the value of this
parameter is below 8.1.0.0.0. Ensure that the value of this parameter is
set to 8.1.0.0.0:

compatible = 8.1.0.0.0

C)THE CTXSYS' TABLESPACE.

The InterMedia Text system user is CTXSYS. In an installation with the DB
Assistant(section II) a DRSYS tablespace is created. CTXSYS' objects are
installed in the DRSYS tablespace.

If you are installing InterMedia Text manually in most cases it is
recommended to create a separate tablespace for CTXSYS - for instance named
DRSYS:

CREATE TABLESPACE DRSYS DATAFILE '<path>\dr01.dbf' SIZE <size>
DEFAULT STORAGE <storage clause>;

IV.AUTOMATIC INSTALLATION OF INTERMEDIA TEXT WITH THE DB ASSISTANT
------------------------------------------------------------------

You can use the DBCA to automatically create an IMT database. The two
following sections guides you through the steps of:

A)Create a new database
B)Modify an exixting database

NOTE: If you want to install InterMedia Text manually go directly to section
V.

<8.1.6!> When you use the DBCA to create the database automatic, the Java
Server will also be installed together with IMT - it's not possible to
exclude JServer.

A)USE THE DB ASSISTANT TO CREATE A NEW DATABASE OR TO CREATE THE SCRIPTS TO
CREATE THE NEW DATABASE.

Go through the steps below to create a new database. At the end of step 4
you decide whether to create the database now, or to save the information
to a batch file:

1.Start the Database Configuration Assistant.

2.Select the procedure 'Create a database'.

3.When prompted to 'select the type of database to create' - choose 'custom'.

4.The next steps allows you to configure your database. Go through these
steps and make the choices that suit your application. Be careful when
you come to the last step. The last form in the assistant prompts you for:
'Do you want the assistant to create the database now?'. Here it is
important that you DO SELECT 'Save information to a batch file' and then
push the 'Finish' button if you don't want to create the database now.

NOTE! Read the rest of this subsection if you have decided to 'Save
information to a batch file'. Otherwise go to section IV.

This will produce some scripts in the prefered directory. Among these
scripts the two important are <db_name>drsys.sql and <db_name>context.sql.
Where <db_name> is the name you chose for the database in db assistant.

-drsys.sql creates the drsys tablespace as described in I.C)

-context.sql performs the steps in III.A(manual data dictionary
installation) and III.C(default language installation).

<8.1.6> NOTE! You will also get the scripts for the configuration of
JSERVER and InterMedia(audio, video and sound). You do not have to install
this. The scripts for InterMedia are ordinst.sql and ordinst.sql.

B)USE THE DB ASSISTANT TO MODIFY AN EXISTING DATABASE.

<8.1.6!> When you use the DBCA to create the database automatic, the Java
Server will also be installed together with ImT - it's not possible to
exclude JServer.

Follow these steps:

1.Start the Database Configuration Assistant.

2.Select the procedure 'Modify a database'.

3.Select the available instance among the available list - the instance's
database has to be started.

4.Type the INTERNAL password.

5.Select "Oracle Intermedia" from the options list and push the "finish"
button. If the option is "grey shaded" a possible reason is that the
product is not properly installed.

The installation is now in progress and IM Text will be installed with
IM Text data dictionary(ref. III.A) and the default preferences(ref. III.B),
which is the default preferences for the U.S. language.

NOTE! If you in the install progress get ORA-1017, see <Note:101476.1>.

V.MANUAL INSTALLATION OF INTERMEDIA TEXT
----------------------------------------

A)MANUAL DATA DICTIONARY INSTALLATION.

1.Connected to sqlplus as SYS, run:

@<ORACLE_HOME>/ctx/admin/dr0csys.sql <ctxsys> <system> <temp>

Where:

<ctxsys> is the ctxsys password
<system> is the default tablespace for ctxsys
<temp> is the temporary tablespace for ctxsys

Comments:

This module creates the user CTXSYS and grants full privileges to CTXSYS in
order to create and insert into result tables, execute callbacks, rewrite
queries, and perform system cleanup.

2.Connected to sqlplus as CTXSYS, run:

@<ORACLE_HOME>/ctx/admin/dr0inst.sql <ORACLE_HOME>/ctx/lib/libctxx8.so
(on UNIX/Linux)

@<ORACLE_HOME>/ctx/admin/dr0inst.sql <ORACLE_HOME>/ctx/lib/libctxx8.sl
(on HP-UX)

@<ORACLE_HOME>/ctx/admin/dr0inst.sql <ORACLE_HOME>\bin\oractxx8.dll
(on NT)

Comments: This module installs all Oracle database objects required by the
TexTile system. This includes:

a) Data dictionary tables, views, sequence, packages
b) Server management tables, views and packages
c) Dispatcher packages
d) Service queue objects

NOTE! You can check at the end of the install that the library is correctly
installed by connecting as ctxsys and selecting from user_libraries:

select library_name,file_spec,dynamic,status from user_libraries;

LIBRARY_NAME FILE_SPEC D STATUS
------------ ---------------------------------------- - -------
DR$LIBX /oracle/db/dev118/ctx/lib/libctxx8.so Y VALID

The file extension depends on the OS.

B)MANUAL INSTALLATION OF THE LANGUAGE PREFERENCES.

The next step is to install appropriate language-specific default preferences.

When you use CREATE INDEX to create an index or ALTER INDEX to manage an index,
you can optionally specify indexing preferences in the parameter string. There
are seven preference classes:

- Lexer, defines the language being indexed. (<- LANG)
- Wordlist, defines the expantion of stem and fuzzy queries. (<- LANG)
- Stoplist, defines words and themes that are not be indexed. (<- LANG)
- Datastore, defines document storage.
- Filter, defines standards for converion of documents to plaintext.
- Storage, defines the storage of the index tables.
- Section group, enables possibilities to define document sections.

An installation with the Database Configuration Assistant install the US
default language preferences. To manually install the US default preferences,
log into sqlplus as CTXSYS, and run 'drdefus.sql', as described below:

@<ORACLE_HOME>/ctx/admin/defaults/drdefus.sql

Comments:

There are forty-odd scripts in ?/ctx/admin/defaults which create language-
specific default preferences. They are named in the form drdefXX.sql, where
XX is the language code. '?/ctx/admin/defaults' contents scripts for the
following supported languages: English(UK), Danish(DK), Dutch(NL),
Finnish(SF), French(FR), German(DE), Italian(IT), Portuguese(PR),
Spanish(ES), and Swedish(S).

NOTE! (<- LANG) refers to the language specific preference classes described
above.

VI.POST INSTALLATION
--------------------

A)NET CONFIGURATION.
1.Listener.ora.
a)Configure an IPC listener address. For instance, change:

LISTENER =
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=tcp)
(HOST=<hostname or IP address>)
(PORT=1521)
)
)

to:

LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = IPC)
(KEY = EXTPROC0)
)
(ADDRESS =
(PROTOCOL = TCP)
(HOST = <hostname or IP address>)
(PORT = 1521)
)
)
)
)

b)Add a system identifier (SID) name of PLSExtProc and a program name of
EXTPROC in the server's LISTENER.ORA file. For instance, in the
SID_LIST_LISTENER definition, insert:

(SID_DESC =
(SID_NAME=PLSExtProc)
(PROGRAM=extproc)
)

- PLSExtProc matches the CONNECT_DATA SID for extproc_connection_data in
the tnsnames.ora.

- The PROGRAM section tells the Net8 listener to start the external
procedure process.

- The ENVS section, may be set here for UNIX, to ensure that the
environment includes ?/ctx/lib in LD_LIBRARY_PATH. This is needed so that
indexing can use the INSO filters. You add this as follows:

(ENVS = 'LD_LIBRARY_PATH=<ORACLE_HOME>/ctx/lib')

- On NT, you may need to have ORACLE_HOME set in this section as well.

(ORACLE_HOME=<ORACLE_HOME>)

2.Tnsnames.ora.

Add a net service name description entry for EXTPROC0 in the server's
tnsnames.ora file, using SID rather than SERVICE_NAME in the CONNECT_DATA
section. For example, add this to the end of tnsnames.ora:

extproc_connection_data =
(DESCRIPTION=
(ADDRESS_LIST =
(ADDRESS=
(PROTOCOL=IPC)
(KEY=EXTPROC0)
)
)
(CONNECT_DATA=
(SID=PLSExtProc)
)
)

Remarks:

- PLSExtProc could really be named anything.

- The connect string 'extproc_connection_data' should not be changed(even
not be in upper case).


4.Sqlnet.ora.

Add or check your domain name entry to the Sqlnet.ora file on your server,
NAMES.DEFAULT_DOMAIN. So, for example, if 'world' is your default domain.
extproc_connection_data.world would be correct.

NAMES.DEFAULT_DOMAIN = uk.oracle.com

extproc_connection_data.uk.oracle.com


B)TEST THE NET CONFIGURATION

Since the extproc_connection_data ADDRESS section specifies ipc, make sure
that the ADDRESS_LIST of listener.ora accepts ipc connections. One way to
do this is to try to create a text index.

A quicker way to test the Net8 configuration is to do:

exec ctx_output.start_log('log')

from SQL*Plus. If you get the error: 'DRG-50704: Net8 listener is not
running or cannot start external procedures, then things are not set up
correctly. Recommended actions:

* Go through the configuration.

* Ensure that the listener is started with the new IPC settings:

type: lsnrctl status

-> The important service summary item to check here is the service
handler for PLSExtProc. This should return:

PLSExtProc has 1 service handler(s)

* Test the service handler for PLSExtProc with tnsping:

tnsping extproc_connection_data

* Check domain name configuration

C)TEST THE INSTALLATION.

Finally you may verify the whole InterMedia Text installation by creating
a text index.

* Create user(or use CTXSYS):

Create user ctxtest identified by ctxtest;
Grant connect, resource, ctxapp to ctxtest;

* Create a test table with a primary key:

Create table test(nr number primary key, test_text varchar2(500));

* Insert some rows into the table:

Insert into test values (1,'This is a test');
Insert into test values (2,'of the InterMedia text installation');
Commit;

* Create at IMT index(domain index) on the "text" column:

Create index test_idx on test(test_text) indextype is ctxsys.context;

* Perform a query on the table:

Select nr, test_text from test
where contains (test_text,'installation') > 0;

This should return:

nr test_text
-- ------------------------------------------
2 of the InterMedia text installation
Previous Topic: Why I can't create context index on ORACLE8i
Next Topic: Problem in Context option
Goto Forum:
  


Current Time: Wed Oct 01 13:00:49 CDT 2014

Total time taken to generate the page: 0.05713 seconds