7 Building and Running Demonstrations

7.1.1 PL/SQL Kernel Demonstrations

The following PL/SQL kernel demonstrations are available:

EXAMP1.SQL
EXAMP2.SQL
EXAMP3.SQL
EXAMP4.SQL
EXTPROC.SQL
EXAMP5.SQL
EXAMP6.SQL
EXAMP7.SQL
EXAMP8.SQL
EXAMP11.SQL
EXAMP12.SQL
EXAMP13.SQL
EXAMP14.SQL
SAMPLE1.SQL
SAMPLE2.SQL
SAMPLE3.SQL
SAMPLE4.SQL

To build and run the PL/SQL kernel demonstrations, enter the following commands:

1. Run SQL*Plus and connect as SCOTT/TIGER:

   $ SET DEFAULT ORA_ROOT:[PLSQL.DEMO]
   $ SQLPLUS SCOTT/TIGER
   
   

2. To load the demonstrations, enter the following command:

   SQL> @EXAMPn.SQL
   
   

   In this command, n denotes a unique integer value for each demonstration file.

   Note:

   Build the demonstrations as any Oracle user with sufficient permissions. Run the demonstrations using the same Oracle user account.

To run the EXTPROC demonstration:

1. Add the following lines to the TNSNAMES.ORA file:

   (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=plsff))(CONNECT_DATA=(SID=extproc)))
   
   

2. Add the following line to the LISTENER.ORA file:

   SID_LIST_LISTENER=(SID_LIST=(SID_DESC= - 
   (SID_NAME:extproc)(PROGRAM=disk:[<oraclehome>NETWORK.ADMIN]EXTPROC)))
   
   

3. From SQL*Plus, enter the following commands:

   SQL> CONNECT SYSTEM/MANAGER
   Connected.
   SQL> GRANT CREATE LIBRARY TO SCOTT;
   Grant succeeded.
   SQL> CONNECT SCOTT/TIGER
   Connected.
   SQL> CREATE LIBRARY DEMOLIB AS 'ora_root:[bin]extproc.exe';
   Library created.
   
   

4. To run the demonstration, enter the following command:

   SQL> @extproc
   

7.1.2 PL/SQL Precompiler Demonstrations

The following precompiler demonstrations are available:

EXAMP9.pc
EXAMP10.pc
SAMPLE5.pc
SAMPLEl6.pc

To build a single demonstration, perform the following steps for the examp9 example.

$ PROC EXAMP9.PC
$ DEFINE RT_INCLUDES ORA_PROGINT_INCL,ORA_PROGINT_VMS_HDRS,ORA_PROGINT_DECC_HDRS
$ CC/NOWARN/INCLUDE=RT_INCLUDES EXAMP9.C
$ LNPROC EXAMP9

To run the EXAMP9 demonstration, enter the following command:

$ RUN EXAMP9

7.2.1 Extensible Indexing Demonstrations

To run the Extensible Indexing demonstrations:

1. Use the same command for compiling the C file as described in the earlier procedure.

2. For extdemo, extdemo2, extdemo4 and extdemo5, you must create an opt file with the specific entry points for the shared image. The opt file contents for each demonstration are as follows:

   • EXTDEMO.OPT

     case_sensitive=YES
     symbol_vector = (-
     Initialize=PROCEDURE,INITIALIZE/Initialize=PROCEDURE-
     ,Iterate=PROCEDURE,ITERATE/Iterate=PROCEDURE-
     ,Terminate=PROCEDURE,TERMINATE/Terminate=PROCEDURE-
     ,Merge=PROCEDURE,MERGE/Merge=PROCEDURE-
     ,Delete=PROCEDURE,DELETE/Delete=PROCEDURE-
     ,WrapContext=PROCEDURE,WRAPCONTEXT/WrapContext=PROCEDURE-)
     case_sensitive=NO
     
     

   • EXTDEMO2.OPT

     case_sensitive=YES
     symbol_vector = (-
     qxiqtbi=PROCEDURE,QXIQTBI/qxiqtbi=PROCEDURE-
     ,qxiqtbd=PROCEDURE,QXIQTBD/qxiqtbd=PROCEDURE-
     ,qxiqtbu=PROCEDURE,QXIQTBU/qxiqtbu=PROCEDURE-
     ,qxiqtbs=PROCEDURE,QXIQTBS/qxiqtbs=PROCEDURE-
     ,qxiqtbf=PROCEDURE,QXIQTBF/qxiqtbf=PROCEDURE-
     ,qxiqtbc=PROCEDURE,QXIQTBC/qxiqtbc=PROCEDURE-)
     case_sensitive=NO
     
     

   • EXTDEMO5.OPT

     case_sensitive=YES
     symbol_vector = (-
     qxiqtbpi=PROCEDURE,QXIQTBPI/qxiqtbpi=PROCEDURE-
     ,qxiqtbpd=PROCEDURE,QXIQTBPD/qxiqtbpd=PROCEDURE-
     ,qxiqtbpu=PROCEDURE,QXIQTBPU/qxiqtbpu=PROCEDURE-
     ,qxiqtbps=PROCEDURE,QXIQTBPS/qxiqtbps=PROCEDURE-
     ,qxiqtbpf=PROCEDURE,QXIQTBPF/qxiqtbpf=PROCEDURE-
     ,qxiqtbpc=PROCEDURE,QXIQTBPC/qxiqtbpc=PROCEDURE-)
     case_sensitive=NO'
     
     

3. To build and run EXTDEMO3 demonstrations, the CLASSPATH should be:

   $define classpath ".:/jdbc_lib/classes12.jar:/sqlj_lib/runtime12.jar:/
   ora_rdbms_
   jlib/xdb.jar:/ora_xdk_lib/
   xmlparserv2.jar:/jdbc_lib/jndi.jar:/jis_lib/jta.jar:/
   ora_rdbms_jlib/ODCI.jar:/ora_rdbms_jlib/CartridgeServices.jar:."
   
   

4. Link the executable with LOUTL using the shared option along with the option file that corresponds to the demonstration you are building. For example:

   LOUTL EXTDEMO2 EXTDEMO2.OPT/OPT,EXTDEMO2.OBJ EXTDEMO2 I 
   
   

5. Create the user for the demonstration and grant the necessary privileges to the user as follows:

   SQL> connect system/manager
   SQL> drop user extdemo2 cascade;
   SQL> create user extdemo2identified by extdemo2
   default tablespace system quota unlimited on system ;
   SQL> grant connect, resource to extdemo2 ;
   SQL> grant create library to extdemo2 ;
   SQL> grant create any directory to extdemo2 ;
   SQL> grant drop any directory to extdemo2 ;
   SQL> grant create any operator to extdemo2 ;
   SQL> grant create indextype to extdemo2 ;
   SQL> grant create table to extdemo2 ;
   
   

6. As mentioned in the step 4 of extdemo2.sql, create the associated library in the user schema as follows:

   connect extdemo2/extdemo2
   CREATE OR REPLACE LIBRARY extdemo2l IS
   'vqat5:[10ghome.rdbms.demo]extdemo2.exe' ;
   

7. Run the following SQL script:

   SQL>@extdemo2.sql
   
   

8. For extended EXTDEMO4.SQL, replace the path in the CREATE LIBRARY command with the path for the generated executable.

7.4.1 aqjms Demonstrations

To build and run the AQJMS demonstrations:

1. While performing the steps outlined in the AQJMSREADME.TXT file, make the following changes:

   Note:

   The AQJMSREADME.TXT can be found under ORA_ROOT:[RDBMS.DEMO].

   1. Replace $ORACLE_HOME in the CLASSPATH specification with the corresponding OpenVMS logical name or the abbreviated logical name for the referenced directory. You must set up the JDK version before performing this step. For example:

      Replace $ORACLE_HOME/rdbms/jlib/aqapi13.jar

      with /ORACLE_HOME/rdbms/jlib/aqapi13.jar

      or use /ora_rdbms_jlib/aqapi13.jar

2. In certain cases, the abbreviated form may have to be used to circumvent command line length limitations. Alternatively, the -V option may be used on OpenVMS java, and all parameters (including the CLASSPATH) can be placed in a DAT file.

   Note:

   In the current release, the following demonstrations do not support the oci8 driver on OpenVMS:

   • AQJMSDEMO01.JAVA

   • AQJMSDEMO02.JAVA

   • AQJMSDEMO05.JAVA

   • AQJMSDEMO06.JAVA

   • AQJMSDEMO08.JAVA

7.4.2 rmanpipe.sql Demonstrations

The RMANPIPE.SQL script uses VMS_RMAN_PIPE.COM, the OpenVMS-specific COM file, to emulate the UNIX operator, which creates a separate, detached process to run the specified command. The COM file dynamically creates a VMSPIPE.COM file. When it is run, the VMSPIPE.COM file creates a corresponding log VMSPIPE.LOG in the ORA_RDBMS_DEMO directory.

7.4.3 JavaVM Demonstrations

The JavaVM demonstrations are available in the following directory:

ORA_ROOT:[JAVAVM.DEMO.EXAMPLES.JSPROC.BASIC]

For each sample, scripts are provided with a name of the form BUILD_RUN_*.COM. When you run these scripts, the corresponding demonstrations are built and run. The output of all demonstrations is directed to SYS$OUTPUT

The NCOMP JavaVM demonstrations are not currently supported on OpenVMS.

7.5.1 Java Demonstrations

To build and run the Java demonstrations, use the scripts provided in the subdirectories of the ORA_ROOT:[XDK.DEMO.JAVA] directory. The names of these scripts are in the form of BUILD_RUN_*.COM. When you run these scripts, the corresponding demonstrations are built and run. You must set the default to the specific demonstration program directory before running any particular script. The result of running the demonstrations are directed to SYS$OUTPUT and are also saved in files that have names of the form *.OUT.

7.5.2 C Programming Language Demonstrations

To build and run the C programming language demonstrations, use the generic scripts provided in the top-level ORA_ROOT:[XDK.DEMO.C] directory:

• COMPILE_SAMPLE.COM

  This script compiles a sample C programming language source file and produces an object file, given the name of the script (without the file name extension) as parameter P1.

• LINK_SAMPLE.COM

  This script links a sample demonstration, given the name of the object file produced by the COMPILE_SAMPLE.COM script as parameter P1.

• BUILD_SAMPLE.COM

  This script combines the actions of the COMPILE_SAMPLE.COM and LINK_SAMPLE.COM scripts.

  To run the demonstration, you must run the executable produced by linking the sample. No arguments are required. The expected output is provided under each sample subdirectory with a file name extension of STD.

7.7.1 Oracle Text

Refer to the ORA_ROOT:[CTX.SAMPLE.APJ]INDEX.HTML file and Oracle Text Reference for information about the Oracle Text code samples.

7.7.2 Oracle Spatial

Refer to the ORA_ROOT:[MD.DOC]README.TXT file for information about the Oracle Database 10g Spatial demonstration. Refer to Oracle Spatial User's Guide and Reference for information about Oracle Database 10g Spatial.

For the Spatial Motif demonstration, refer to ORA_ROOT:[MD.DEMO.UNIX.MOTIF]README.

$! On OpenVMS at DCL to build SDO Motif demo, run:
$ SQLPLUS/NOLOG
SQL> CONNECT MDSYS/MDSYS
SQL> @ORA_ROOT:[MD.ADMIN]SDOWIN.SQL
SQL> @ORA_ROOT:[MD.ADMIN]PRVTWIN.PLB
SQL> @ORA_ROOT:[MD.DEMO.UNIX.MOTIF.SRC.SQL_SCRIPTS]MY_WINDOW.SQL
SQL> @ORA_ROOT:[MD.DEMO.UNIX.MOTIF.SRC.SQL_SCRIPTS]MY_WIN.SQL
SQL> EXIT
$! OpenVMS Logicals and Symbols already setup for MD_VIEWER, XENVIRONMENT, motifdemo in:
$ @ORA_ROOT:[MD.PORT.VMS.INSTALL]DEMO_MOTIF.COM ALL

7.7.3 Spatial Network Demonstrations

Before running Spatial Network demonstrations, read ORA_ROOT:[MD.DEMO.NETWORK...]README.TXT for each demonstration to be run.

Following are example runs for the PL/SQL, SQL*Loader Logical, SQL*Loader Spatial, Java, and Network Editor demonstrations.

SDO Network Example PL/SQL Demonstration

To run the SDO Network Example PL/SQL demonstration, run the following at the DCL command prompt:

$ SET DEFAULT ORA_ROOT:[MD.DEMO.NETWORK.EXAMPLES.PLSQL]
$ SQLPLUS SCOTT/TIGER @CREATE_LOGICAL.SQL

SDO Network Example SQL*Loader Logical Demonstration

To run SDO Network Example SQL*Loader Logical demonstration, run the following commands at the DCL command prompt:

$ SET DEFAULT ORA_ROOT:[MD.DEMO.NETWORK.EXAMPLES.SQLLDR.LOGICAL]
$ @ORA_ROOT:[MD.PORT.VMS.INSTALL]LOAD_TEST_NET.COM

SDO Network Example SQL*Loader Spatial Demonstration

To run SDO Network Example SQL*Loader Spatial demonstration on OpenVMS, run the following commands at the DCL command prompt:

$ SET DEFAULT ORA_ROOT:[MD.DEMO.NETWORK.EXAMPLES.SQLLDR.SPATIAL]
$ @ORA_ROOT:[MD.PORT.VMS.INSTALL]LOAD_SPATIAL_NET.COM

SDO Network Example Java Demonstration

To run SDO Network Example Java demonstration on OpenVMS, run the following commands at the DCL command prompt:

$ @ORA_ROOT:[JDBC]JDBC_SETUP_JDK14.COM
SQL> create user MDNETWORK identified by MDNETWORK;
$ SET DEFAULT ORA_ROOT:[MD.DEMO.NETWORK.EXAMPLES.JAVA.DATA]
$ SQLPLUS/NOLOG
SQL> connect / as sysdba

The following is for illustrative purposes only. Contact the Security Manager or DBA for information about the correct security settings.

SQL> grant all privileges to MDNETWORK with admin option;
SQL> exit
$ SQLPLUS MDNETWORK/MDNETWORK @REMOVE_BI_TEST.SQL
SQL> exit
$ SQLPLUS MDNETWORK/MDNETWORK @REMOVE_UN_TEST.sql
SQL> exit
$ IMP MDNETWORK/MDNETWORK FILE=BI_TEST.DMP TABLES="'BI_TEST_NODE$'"
$ IMP MDNETWORK/MDNETWORK FILE=BI_TEST.DMP TABLES="'BI_TEST_LINK$'"
$ SQLPLUS MDNETWORK/MDNETWORK @BI_TEST_META.SQL
SQL> exit
$ IMP MDNETWORK/MDNETWORK FILE=UN_TEST.DMP TABLES="'UN_TEST_NODE$'"
$ IMP MDNETWORK/MDNETWORK FILE=UN_TEST.DMP TABLES="'UN_TEST_LINK$'"
$ SQLPLUS MDNETWORK/MDNETWORK @UN_TEST_META.SQL
SQL> exit
$ SET DEFAULT ORA_ROOT:[MD.DEMO.NETWORK.EXAMPLES.JAVA]
$ EDIT ORA_ROOT:[MD.DEMO.NETWORK.EXAMPLES.JAVA]LOADANDANALYZE.JAVA

Change host, port, sid using values from the tnsnames.ora file.

$ ! Enter each java command as all one line
$ JAVAC -CLASSPATH .:'F$TRNLNM("ORACLE_HOME_UNIX")'/JDBC/LIB/
CLASSES12.JAR:'F$TRNLNM("ORACLE_HOME_UNIX")'/
LIB/XMLPARSERV2.JAR:'F$TRNLNM("ORACLE_HOME_UNIX")'/
MD/LIB/SDOAPI.JAR:'F$TRNLNM("ORACLE_HOME_UNIX")'/MD/LIB/SDONM.JAR LOADANDANALYZE.JAVA
$ JAVA -CLASSPATH .:'F$TRNLNM("ORACLE_HOME_UNIX")'/JDBC/LIB/
CLASSES12.JAR:'F$TRNLNM("ORACLE_HOME_UNIX")'/
LIB/XMLPARSERV2.JAR:'F$TRNLNM("ORACLE_HOME_UNIX")'/MD/LIB/
SDOAPI.JAR:'F$TRNLNM("ORACLE_HOME_UNIX")'/MD/LIB/SDONM.JAR "LOADANDANALYZE"
$ EDIT ORA_ROOT:[MD.DEMO.NETWORK.EXAMPLES.JAVA]CREATEANDSTORE.JAVA

Change host, port, sid using values from the tnsnames.ora file.

$ ! Enter each java command as all one line
$ JAVAC -CLASSPATH .:'F$TRNLNM("ORACLE_HOME_UNIX")'/
JDBC/LIB/CLASSES12.JAR:'F$TRNLNM("ORACLE_HOME_UNIX")'/LIB/XMLPARSERV2.JAR
:'F$TRNLNM("ORACLE_HOME_UNIX")'/MD/LIB/SDOAPI.JAR:'F$TRNLNM("ORACLE_HOME_UNIX")'/
MD/LIB/SDORNM.JAR CREATEANDSTORE.JAVA
$ JAVA -CLASSPATH .:'F$TRNLNM("ORACLE_HOME_UNIX")'/JDBC/LIB/
CLASSES12.JAR:'F$TRNLNM("ORACLE_HOME_UNIX")'/
LIB/XMLPARSERV2.JAR:'F$TRNLNM("ORACLE_HOME_UNIX")'/
MD/LIB/SDOAPI.JAR:'F$TRNLNM("ORACLE_HOME_UNIX")'/MD/LIB/SDONM.JAR "CREATEANDSTORE"

SDO Network Editor Demonstration

On OpenVMS at DCL to run SDO Network Editor demonstration:

1. Prior to running the SDO Network Editor demonstration, set up an X Window emulator.

2. Load the sample data by running commands similar to the following:

   ORA_ROOT:[MD.DEMO.NETWORK.EXAMPLES.JAVA.DATA] above.
   $ SET DEFAULT ORA_ROOT:[MD.DEMO.NETWORK.EDITOR]
   $ @ORA_ROOT:[MD.PORT.VMS.INSTALL]STARTNETWORKEDITOR.COM
   

7.7.4 Spatial Example Demonstrations

For information about running the Spatial example demonstrations, read the ORA_ROOT:[MD.DEMO.EXAMPLES]PARALLEL.DOC file. The following is an example of a Spatial demonstration:

1. To run SDO Example Scripts demonstration, run the following at the at DCL command prompt:

   $ SET DEFAULT ORA_ROOT:[MD.DEMO.EXAMPLES.SCRIPTS]
   $ SQLPLUS /NOLOG
   SQL> connect / as sysdba
   SQL> create user SDO_USR identified by SDO_USR;
   
   

   The following is for illustrative purpose only:

   Note:

   Contact the site Security Manager or DBA for information about the appropriate security settings.

   SQL> grant all privileges to SDO_USR with admin option;
   SQL> create Tablespace SDO_DATA DATAFILE 'ORA_DB:SDO_DATA.F' SIZE 50M;
   SQL> connect sdo_usr/sdo_usr
   SQL> @ORA_ROOT:[MD.DEMO.EXAMPLES]PARTITION_POINTS.SQL
   
   

2. To compile, link, and run SDO Example demonstrations, run the following commands at the DCL command prompt:

   Note:

   Before running the SDO Example demonstrations, set up an X Window emulator as described in Section 7.7.2.1, "Running the Spatial Demonstration".

   $ SET DEFAULT ORA_ROOT:[MD.DEMO.EXAMPLES]
   $ @ORA_ROOT:[MD.PORT.VMS.INSTALL]DEMO_SDO.COM
   $ READGEOM:= $ORA_ROOT:[MD.DEMO.EXAMPLES]READGEOM.EXE
   $ READGEOM parameter_list
   $ WRITEGEOM := $ORA_ROOT:[MD.DEMO.EXAMPLES]WRITEGEOM.EXE
   $ WRITEGEOM parameter_list
   $ RUN MIGCTL
   $ RUN MIGOCI
   

7.7.5 Spatial Georaster Demonstrations

Before running the Spatial Georaster demonstrations, read the ORA_ROOT:[MD.DEMO.GEORASTER...]README file for each demonstration to be run. The following is an example of how to run a Spatial Georaster demonstration:

1. Run the following commands on OpenVMS at DCL to run the SDO Georaster PL/SQL demonstrations:

   $ set default ORA_ROOT:[MD.DEMO.GEORASTER.PLSQL]
   $ sqlplus/nolog @GEORASTER_DEMO.SQL
   SQL> exit
   
   

2. After all Spatial Georaster demonstrations have been run, enter the following commands to remove the Georaster PL/SQL demonstrations:

   $ sqlplus herman/password @DROP_GEORASTER_TABLE.SQL
   SQL> exit
   
   

To run SDO Georaster Java demonstrations, follow the instructions in the ORA_ROOT:[MD.DEMO.GEORASTER.JAVA]README file. Before running the SDO Georaster Java demonstrations, set up an X Window emulator as described in Section 7.7.2.1, "Running the Spatial Demonstration". The GeoRasterExporter portion of the GeoRaster demo is unsupported.

7.8.1 Administering SQL*Loader

SQL*Loader is used by both database administrators and Oracle Database 10g users. It loads data from standard operating system files into Oracle Database tables.

The SQL*Loader control file includes the following additional file processing option strings, the default being str, which takes no argument:

[ "str" | "fix n" | "var n" ]

Table 7-1 describes the processing options used in the preceding example.

If you do not select the file processing option, then the information is processed by default as a stream of records (str). You may find that fix mode gives better performance than the default str mode because it does not scan for record terminators.

AAA<cr>
BBB<cr>
CCC<cr>

load data
infile xyz.dat "fix 4"
into table abc
( dept position(01:03) char )