DISC

Contents | What's New | Quick Links

 

Omnidex's PL/SQL Interface

Introduction

Software Installation

Concepts and Design

Designing Applications

Omnidex Environments

SQL Reference

Omnidex API's

Utilities

Interfaces

Performance Guide

Troubleshooting Guide

Appendix

 

 

Installation and Setup

PL/SQL InterfaceSyntax

 

The following is the detailed set up instructions for the Omnidex PL/SQL interface.

 

Oracle PL/SQL

Setup

Syntax

Sample

Environment Variables

Omnidex Data sources

Omnidex Network Services

 

Oracle Setup

Before starting the Oracle listener, there are two Oracle files that may have to be edited to work. These files control Oracle Networking and are called listener.ora and tnsnames.ora.

  • The first is the listener.ora file that is found in the following location: $ORACLE_HOME/network/admin/listener.ora, where $ORACLE_HOME is the directory where Oracle is installed. The listener.ora file can be modified using any text editor such as vi on Unix/Linux or notepad on Windows. Check to make sure the following lines in red are either present or add the appropriate lines.

LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
)
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = sun2.disc.com)(PORT = 1521))
)
)
)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /dbs1/ora902)
(PROGRAM = extproc32)
(ENVS = "EXTPROC_DLLS=ANY",
"OMNIDEX_HOME=/omnidex",
"OMNIDEX_LIBS=$OMNIDEX_HOME/lib",
"OMNIDEX_REG=$OMNIDEX_HOME/odxreg",
"OAGLOBAL=$OMNIDEX_HOME/oaglobal.env",
"LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$OMNIDEX_HOME/lib")
)
(SID_DESC =
(GLOBAL_DBNAME = v902)
(ORACLE_HOME = /dbs1/ora902)
)
)

  • The second Oracle file, tnsnames.ora, can also be found in the network/admin directory under the Oracle home directory, as follows: $ORACLE_HOME/network/admin/tnsnames.ora
    Make sure the following lines are added to this file.

 

EXTPROC_CONNECTION_DATA.DISC.COM =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
)
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
)
)

 

After these files have been properly edited, start the Oracle listener:

  • Make sure the ORACLE_HOME and ORACLE_SID environment variables are set.
  • EXTPROC_DLLS must be set to ANY or library name.

    export EXTPROC_DLLS=$OMNIDEX_LIBS/libodxplora.so

Isnrctl
> help (or) status (or) start (or) stop
> exit

top

 

Omnidex Setup

  • Make sure the Omnidex environment variables OAGLOBAL, OMNIDEX_REG, and OMNIDEX_LIBS are set.
  • DISC Recommends setting these variables in the listener.ora file. See example above.

  • Set up Omnidex Network Services. Please see the Omnidex Network Services section for setup instructions.
  • Create an Omnidex Data source File. PL/SQL will use the Data source file when connecting to an Omnidex enhanced database. Please see the Omnidex Data source Files section for setup instructions.
  • Make sure a valid Omnidex index environment exists.
  • Edit odxplora.sql, located in $OMNIDEX_HOME/demo/plsql. The first line must be changed to point to the location of the library libodxplora.so (UNIX) or libodxplora.sl (HPUX).
    create or replace library odx_lib as '$OMNIDEX_LIBS/libodxplora.so'

 

top

 

Verify That the Omnidex to PL/SQL Bridge is Properly Installed

At the SQL prompt, type the following select statement:

SQL> select owner, object_name, object_type from all_objects where object_name
like 'ODX%';

The results of this select should be something like the following:

OWNER

OBJECT_NAME

OBJECT_TYPE

----------------

-------------------

--------------------

PUBLIC

ODX

SYNONYM

SYSTEM

ODX

PACKAGE

SYSTEM

ODX

PACKAGE BODY

SYSTEM

ODX_LIB

LIBRARY

ORDERS

ODXTRANS

TABLE

ORDERS

ODXTRANS_SEQUENCE

SEQUENCE

XTABLE

ODX

TABLE

NCDEV

ODXTRANS

TABLE

  • There should be 4 entries in the ALL_OBJECTS table for the bride.
  • The ODX synonym is owned by PUBLIC so it can be used without the SYS prefix.
  • The ODX package and package body are owned by SYSTEM.
  • The ODX_LIB library is owned by SYSTEM.

 

top

 

Uninstall the Omnidex to PL/SQL Bridge

To uninstall the Omnidex to PL/SQL Bridge, issue the following DROP statements at the SQL prompt:

DROP PUBLIC SYNONYM ODX;

DROP PACKAGE ODX;

DROP LIBRARY ODX_LIB;

You must be logged on as SYSTEM in order to successfully execute these DROP statements.

 

top

Dynamic Information Systems Corporation - Omnidex Version 3.8 Build 6 J15.03-Copyright © 2003

DISC | Documentation Home