| Oracle® Database Administrator's Reference 11g Release 2 (11.2) for Linux and UNIX-Based Operating Systems Part Number E10839-02 |
|
|
View PDF |
| Oracle® Database Administrator's Reference 11g Release 2 (11.2) for Linux and UNIX-Based Operating Systems Part Number E10839-02 |
|
|
View PDF |
This chapter describes how to use Oracle precompilers and the Oracle Call Interface. It contains the following sections:
Note:
To use the demonstrations described in this chapter, install the Oracle Database Examples included on the Oracle Database 11g Examples media.Oracle precompilers are application development tools that are used to combine SQL statements for an Oracle Database with programs written in a high-level language. Oracle precompilers are compatible with ANSI SQL and are used to develop, open, customized applications that run with Oracle Database or any other ANSI SQL database management system.
This section contains the following topics:
Note:
ORACLE_HOME in this section refers to ORACLE_HOME that is created while installing Oracle Database Client 11g by using the Administrator Install type.Configuration files for the Oracle precompilers are located in the $ORACLE_HOME/precomp/admin directory.
Table 6-1 lists the names of the configuration files for each precompiler.
Use the $ORACLE_HOME/precomp/lib/ins_precomp.mk make file to relink all precompiler executables. To manually relink a particular precompiler executable, enter the following command:
$ make -f ins_precomp.mk relink exename = executable_name
This command creates the new executable in the $ORACLE_HOME/precomp/lib directory, and then moves it to the $ORACLE_HOME/bin directory.
In the preceding example, replace executable with one of the product executables listed in Table 6-2.
Table 6-2 lists the executables for Oracle Precompilers.
Table 6-2 Executables for Oracle Precompilers
| Product | Executable |
|---|---|
|
Pro*C/C++ |
|
|
Pro*COBOL (AIX, HP-UX, and Solaris SPARC (64-bit)) |
|
|
Pro*COBOL 32-bit (AIX, HP-UX PA-RISC, and Solaris SPARC (64-bit)) |
|
|
Pro*FORTRAN (AIX, HP-UX, and Solaris) |
|
|
Pro*FORTRAN 32-bit (HP-UX PA-RISC) |
|
|
SQL*Module for Ada (AIX) |
|
The README files describe changes made to the precompiler since the last release.
Table 6-3 lists the location of the precompiler README files.
The following issues are common to all precompilers:
Uppercase to Lowercase Conversion
In languages other than C, the compiler converts an uppercase function or subprogram name to lowercase. This can cause a No such user exists error message. If you receive this error message, then verify that the case of the function or subprogram name in the option file matches the case used in the IAPXTB table.
Precompilers and vendor-supplied debuggers can be incompatible. Oracle does not guarantee that a program run using a debugger performs the same way when it is run without the debugger.
Value of IRECLEN and ORECLEN parameters
The IRECLEN and ORECLEN parameters do not have maximum values.
You can statically or dynamically link Oracle libraries with precompiler and OCI or OCCI applications. With static linking, the libraries and objects of the whole application are linked into a single executable program. As a result, application executables can become very large.
With dynamic linking, the executing code is partly stored in the executable program and partly stored in libraries that are linked dynamically by the application at run time. Libraries that are linked at run time are called dynamic or shared libraries. The benefits of dynamic linking are:
Reduced disk space requirements: Multiple applications or calls to the same application can use the same dynamic librararies.
Reduced main memory requirements: The same dynamic library image is loaded into main memory only once, and it can be shared by multiple application.
The client shared and static libraries are located in the $ORACLE_HOME/lib or $ORACLE_HOME/lib32 directories. If you use the Oracle-provided demo_product.mk file to link an application, then the client shared library is linked by default.
If the shared library path environment variable setting does not include the directory that contains the client shared library, then you may see an error message similar to one of the following lines when starting an executable:
Cannot load library libclntsh.a cannot open shared library: .../libclntsh.sl.10.1 libclntsh.so.10.1: can't open file: errno=2 can't open library: .../libclntsh.dylib.10.1 Cannot map libclntsh.so
To avoid this error, set the shared library path environment variable to specify the appropriate directory. The following table shows sample settings for this environment variable name. If the platform supports both 32-bit and 64-bit applications, then ensure that you specify the correct directory, depending on the application that you want to run.
| Platform | Environment Variable | Sample Setting |
|---|---|---|
| AIX (32-bit applications) | LIBPATH |
$ORACLE_HOME/lib32 |
| AIX (64-bit applications) | LIBPATH |
$ORACLE_HOME/lib |
| HP-UX (32-bit applications) | SHLIB_PATH |
$ORACLE_HOME/lib32 |
| HP-UX (64-bit applications) and Linux | LD_LIBRARY_PATH |
$ORACLE_HOME/lib |
| Solaris (32-bit applications) | LD_LIBRARY_PATH |
$ORACLE_HOME/lib32 |
| Solaris (64-bit applications) | LD_LIBRARY_PATH_64 |
$ORACLE_HOME/lib |
The client shared library is created automatically during installation. If you must re-create it, then:
Quit all client applications that use the client shared library, including all Oracle client applications such as SQL*Plus and Oracle Recovery Manager.
Log in as the oracle user, and run the following command:
$ $ORACLE_HOME/bin/genclntsh
Nonthreaded Client Shared Library
Note:
The information in this section applies to HP-UX systems.On HP-UX, you can use a non-threaded client shared library. However, you cannot use this library with any OCI application that uses or has a dependency on threads.
To use this library for applications that do not use threads, run one of the following commands to build the OCI application:
For 32-bit applications:
$ make -f demo_rdbms32.mk build_nopthread EXE=oci02 OBJS=oci02.o
For 64-bit applications:
$ make -f demo_rdbms.mk build_nopthread EXE=oci02 OBJS=oci02.o
The following table identifies the bit lengths (31-bit, 32-bit, or 64-bit) supported for client applications:
| Client Application Type | Supported Platforms |
|---|---|
| 32-bit only | Linux x86 |
| 32-bit and 64-bit | AIX, HP-UX PA-RISC, Linux x86-64, and Solaris SPARC |
| 64-bit only | HP-UX Itanium |
On AIX, HP-UX, and Solaris SPARC, all demonstrations and client applications provided with Oracle Database 11g Release 2 (11.2) link and run in 64-bit mode. On AIX, Solaris SPARC, and HP-UX, you can build 32-bit and 64-bit client applications in the same Oracle home directory.
The following table lists the 32-bit and 64-bit client shared libraries:
| Platform | 32-Bit (or 31-Bit) Client Shared Library | 64-Bit Client Shared Library |
|---|---|---|
| AIX |
$ORACLE_HOME/lib32/libclntsh.a $ORACLE_HOME/lib32/libclntsh.so |
$ORACLE_HOME/lib/libclntsh.a $ORACLE_HOME/lib/libclntsh.so |
| HP-UX PA-RISC |
$ORACLE_HOME/lib32/libclntsh.sl |
$ORACLE_HOME/lib/libclntsh.sl |
| Linux x86-64 and Solaris |
$ORACLE_HOME/lib32/libclntsh.so |
$ORACLE_HOME/lib/libclntsh.so |
To implement a mixed word-size installation:
Run the following command to generate the 32-bit and 64-bit client shared libraries:
$ $ORACLE_HOME/bin/genclntsh
Include the paths of the required 32-bit and 64-bit client shared libraries in one of the following environment variables, depending on the platform:
| Platform | Environment Variable |
|---|---|
| AIX | LIBPATH |
| HP-UX (32-bit client applications) | SHLIB_PATH |
| HP-UX, Linux x86, Linux x86-64, and Solaris | LD_LIBRARY_PATH |
Building 32-Bit Pro*C and OCI Customer Applications
If the operating system supports both 32-bit and 64-bit Pro*C and Oracle Call Interface (OCI) customer applications, then you can find more information about building 32-bit Pro*C and OCI applications in the following files:
| For Information About. . . | Refer to the Following Make Files. . . |
|---|---|
| Building 32-bit Pro*C applications | $ORACLE_HOME/precomp/demo/proc/demo_proc32.mk |
| Building 32-bit OCI applications | $ORACLE_HOME/rdbms/demo/demo_rdbms32.mk |
32-Bit Executables and Libraries
Note:
Information in this section applies to the AIX, HP-UX, and Solaris SPARC platforms.If the platform supports both 32-bit and 64-bit applications, then the $ORACLE_HOME/bin directory contains both 32-bit and 64-bit executables. In addition, the following directories contain 32-bit libraries:
$ORACLE_HOME/lib32
$ORACLE_HOME/rdbms/lib32
$ORACLE_HOME/hs/lib32
$ORACLE_HOME/network/lib32
$ORACLE_HOME/precomp/lib32
Before you use the Pro*C/C++ precompiler, verify that the correct version of the operating system compiler is properly installed.
See Also:
Oracle Database Installation Guide for information about supported compiler versions
Pro*C/C++ Programmer's Guide for information about the Pro*C/C++ precompiler and interface features
This section contains the following topics:
Demonstration programs are provided to show the features of the Pro*C/C++ precompiler. There are three types of demonstration programs: C, C++, and Object programs. All demonstration programs are located in the $ORACLE_HOME/precomp/demo/proc directory. By default, all programs are dynamically linked with the client shared library.
To run the demonstration programs, the programs require the demonstration tables created by the $ORACLE_HOME/sqlplus/demo/demobld.sql script to exist in the SCOTT schema with the password TIGER.
Note:
You must unlock the SCOTT account and set the password before creating the demonstrations.Use the demo_proc.mk make file, which is located in the $ORACLE_HOME/precomp/demo/proc/ directory, to create the demonstration programs. For example, to precompile, compile, and link the sample1 demonstration program, run the following command:
Note:
On AIX systems, to ensure that the demonstration programs compile correctly, include the-r option of the make command in the following examples. For example:
$ make -r -f demo_proc.mk sample1
$ make -f demo_proc.mk sample1
To create all the C demonstration programs for Pro*C/C++, run the following command:
$ make -f demo_proc.mk samples
To create all the C++ demonstration programs for Pro*C/C++, run the following command:
$ make -f demo_proc.mk cppsamples
To create all the Object demonstration programs for Pro*C/C++, run the following command:
$ make -f demo_proc.mk object_samples
Some demonstration programs require you to run a SQL script, located in the $ORACLE_HOME/precomp/demo/sql directory. If you do not run the script, then a message prompting you to run it is displayed.
To build a demonstration program and run the corresponding SQL script, include the make macro argument RUNSQL=run at the command line. For example, to create the sample9 demonstration program and run the required $ORACLE_HOME/precomp/demo/sql/sample9.sql script, run the following command:
$ make -f demo_proc.mk sample9 RUNSQL=run
To create all the Object demonstration programs and run all the required SQL scripts, run the following command:
$ make -f demo_proc.mk object_samples RUNSQL=run
You can use the $ORACLE_HOME/precomp/demo/proc/demo_proc.mk make file to create user programs. This make file builds either 32-bit or 64-bit user programs. You can also use the demo_proc32.mk make file to build 32-bit user programs. The following table shows the make files that you can use to build 32-bit and 64-bit user programs with Pro*C/C++:
| Platform | 64-bit Make File | 32-Bit Make File |
|---|---|---|
| AIX, HP-UX, Linux x86-64, Solaris x86-64 and Solaris SPARC | demo_proc.mk |
demo_proc32.mk |
| Linux x86 | NA | demo_proc.mk |
See Also:
The make file for more information about creating user programsNote:
On AIX systems, to ensure that the programs compile correctly, specify the-r option for the make command used in the following examples.To create a program by using the demo_proc.mk make file, run a command similar to the following:
$ make -f demo_proc.mk target OBJS="objfile1 objfile2 ..." EXE=exename
In this example:
target is the make file target that you want to use
objfilen is the object file to link the program
exename is the executable program
For example, to create the program myprog from the Pro*C/C++ source file myprog.pc, run one of the following commands, depending on the source and the type of executable that you want to create:
For C source dynamically linked with the client shared library, run the following command:
$ make -f demo_proc.mk build OBJS=myprog.o EXE=myprog
For C source statically linked with the client shared library, run the following command:
$ make -f demo_proc.mk build_static OBJS=myprog.o EXE=myprog
For C++ source dynamically linked with the client shared library, run the following command:
$ make -f demo_proc.mk cppbuild OBJS=myprog.o EXE=myprog
For C++ source statically linked with the client shared library, run the following command:
$ make -f demo_proc.mk cppbuild_static OBJS=myprog.o EXE=myprog
Table 6-4 shows the naming conventions for the Pro*COBOL precompiler.
Table 6-4 Pro*COBOL Naming Conventions
| Item | Naming Convention |
|---|---|
|
Executable |
|
|
Demonstration directory |
|
|
Make file |
|
Pro*COBOL supports statically linked, dynamically linked, or dynamically loadable programs. Dynamically linked programs use the client shared library. Dynamically loadable programs use the rtsora executable (or the rtsora32 executable for 32-bit COBOL compilers) located in the $ORACLE_HOME/bin directory.
This section contains the following topics:
This section describes the environment variables required by Pro*COBOL:
To use the Micro Focus Server Express COBOL compiler, you must set the COBDIR and PATH environment variables and the shared library path environment variable.
See Also:
The "Client Shared and Static Libraries" section for information about the shared library path environment variableIf the shared library path environment variable setting does not include the $COBDIR/coblib directory, then an error message similar to the following is displayed when you compile or run a program:
On Linux:
rtsora: error while loading shared libraries: libcobrts_t.so: cannot open shared object file: No such file or directory
On HP-UX PA-RISC and Solaris SPARC:
ld.so.1: rts32: irrecoverable: libfhutil.so.2.0: Can't open file: errno=2
On AIX:
ld: rts32: irrecoverable: libfhutil.so: Can't open file: errno=2
On HP-UX Itanium:
/usr/lib/hpux64/dld.so: Unable to find library 'libcobrts64_t.so.2'. stoped
Set the COBDIR environment variable to the directory where the compiler is installed. For example, if the compiler is installed in the /opt/lib/cobol directory, then run the following command:
Bourne, Bash, or Korn shell:
$ COBDIR=/opt/lib/cobol $ export COBDIR
C shell:
% setenv COBDIR /opt/lib/cobol
Set the PATH environment variable to include the $COBDIR/bin directory:
Bourne, Bash, or Korn shell:
$ PATH=$COBDIR/bin:$PATH $ export PATH
C shell:
% setenv PATH ${COBDIR}/bin:${PATH}
Set the LIBPATH, LD_LIBRARY_PATH, or SHLIB_PATH environment variable to the directory where the compiler library is installed. For example, if the platform uses the LD_LIBRARY_PATH environment variable and the compiler library is installed in the $COBDIR/coblib directory, then run the following command:
Bourne, Bash, or Korn shell:
$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$COBDIR/coblib
$ export LD_LIBRARY_PATH
C shell:
% setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$COBDIR/coblib
To use the Acucorp ACUCOBOL-GT COBOL compiler, you must set the A_TERMCAP, A_TERM, PATH, and LD_LIBRARY_PATH environment variables. If the LD_LIBRARY_PATH environment variable setting does not include the correct directory, then an error message similar to the following is displayed when you compile or run a program:
runcbl: error while loading shared libraries: libclntsh.so: cannot open shared object file: No such file or directory
Set the A_TERMCAP environment variable to specify the location of the a_termcap file and set the A_TERM environment variable to specify a supported terminal from that file. For example:
Bourne, Bash, or Korn shell:
$ A_TERMCAP=/opt/COBOL/etc/a_termcap $ A_TERM=vt100 $ export A_TERMCAP A_TERM
C shell:
% setenv A_TERMCAP /opt/COBOL/etc/a_termcap % setenv A_TERM vt100
Set the PATH environment variable to include the /opt/COBOL/bin directory:
Bourne, Bash, or Korn shell:
$ PATH=/opt/COBOL/bin:$PATH $ export PATH
C shell:
% setenv PATH opt/COBOL/bin:${PATH}
Note:
On AIX, theLIBPATH variable is the LD_LIBRARY_PATH variable equivalent. You must use the LIBPATH variable on AIX instead of the LD_LIBRARY_PATH variable in the following commands.Set the LD_LIBRARY_PATH environment variable to the directory where the compiler library is installed. For example, if the compiler library is installed in the /opt/COBOL/lib directory, then run the following command:
Bourne, Bash, or Korn shell:
$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/opt/COBOL/lib
$ export LD_LIBRARY_PATH
C shell:
% setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/opt/COBOL/lib
Oracle provides its own complete run-time system, called rtsora (or rtsora32 for 32-bit COBOL compilers on 64-bit systems), to run dynamically loadable Pro*COBOL programs. Use the rtsora (or rtsora32) run-time system instead of the cobrun run-time system to run dynamically loadable Pro*COBOL programs. If you attempt to run a Pro*COBOL program with cobrun, then an error message similar to the following is displayed:
$ cobrun sample1.gnt Load error : file 'SQLADR' error code: 173, pc=0, call=1, seg=0 173 Called program file not found in drive/directory
Demonstration programs are provided to show the features of the Pro*COBOL precompiler. The demonstration programs are located in the $ORACLE_HOME/precomp/demo/procob2 directory. By default, all programs are dynamically linked with the client shared library.
To run the demonstration programs, the programs require the demonstration tables created by the $ORACLE_HOME/sqlplus/demo/demobld.sql script to exist in the SCOTT schema with the password TIGER.
Note:
You must unlock the SCOTT account and set the password before creating the demonstrations.Use the following make file to create the demonstration programs:
$ORACLE_HOME/precomp/demo/procob2/demo_procob.mk
To precompile, compile, and link the sample1 demonstration program for Pro*COBOL, run the following command:
$ make -f demo_procob.mk sample1
To create the Pro*COBOL demonstration programs, run the following command:
$ make -f demo_procob.mk samples
To create and run a dynamically loadable sample1.gnt program to be used with the rtsora run-time system, run the following command:
$ make -f demo_procob.mk sample1.gnt $ rtsora sample1.gnt
Some demonstration programs require you to run a SQL script, which is located in the $ORACLE_HOME/precomp/demo/sql directory. If you do not run the script, then a message requesting you to run it is displayed.
To build a demonstration program and run the corresponding SQL script, include the make macro argument RUNSQL=run in the command. For example, to create the sample9 demonstration program and run the required $ORACLE_HOME/precomp/demo/sql/sample9.sql script, run the following command:
$ make -f demo_procob.mk sample9 RUNSQL=run
To create the Pro*COBOL demonstration programs and run all required SQL scripts, run the following command:
$ make -f demo_procob.mk samples RUNSQL=run
You can use the $ORACLE_HOME/precomp/demo/procob2/demo_procob.mk make file to create user programs. This make file builds either 32-bit or 64-bit user programs. You can also use the demo_procob_32.mk make file to build 32-bit (or 31-bit) user programs. The following table shows the make files that you can use to build 32-bit (or 31-bit) and 64-bit user programs with Pro*COBOL:
| Platform | 64-bit Make File | 32-Bit Make File |
|---|---|---|
| AIX, HP-UX, Linux x86-64, and Solaris SPARC | demo_procob.mk |
demo_procob_32.mk |
| Linux x86 | Not applicable | demo_procob.mk |
See Also:
The make file for more information about creating user programsTo create a program using the demo_procob.mk make file, run a command similar to the following:
$ make -f demo_procob.mk target COBS="cobfile1 cobfile2 ..." EXE=exename
In this example:
target is the make file target that you want to use
cobfilen is the COBOL source file for the program
exename is the executable program
For example, to create the program myprog, run one of the following commands, depending on the source and type of executable that you want to create:
For COBOL source, dynamically linked with the client shared library, run the following command:
$ make -f demo_procob.mk build COBS=myprog.cob EXE=myprog
For COBOL source, statically linked, run the following command:
$ make -f demo_procob.mk build_static COBS=myprog.cob EXE=myprog
For COBOL source, dynamically loadable for use with rtsora (or rtsora32 for 32-bit COBOL compilers), run the following command:
$ make -f demo_procob.mk myprog.gnt
The FORMAT precompiler option specifies the format of input lines for COBOL. If you specify the default value ANSI, then columns 1 to 6 contain an optional sequence number, column 7 indicates comments or continuation lines, paragraph names begin in columns 8 to 11, and statements begin in columns 12 to 72.
If you specify the value TERMINAL, then columns 1 to 6 are dropped, making column 7 the left most column.
Before you use the Pro*FORTRAN precompiler, verify that the correct version of the compiler is installed. This section contains the following topics:
See Also:
Oracle Database Installation Guide for information about supported compiler versions
Pro*FORTRAN Supplement to the Oracle Precompilers Guide for information about the Pro*FORTRAN precompiler and interface features
Demonstration programs are provided to show the features of the Pro*FORTRAN precompiler. All demonstration programs are located in the $ORACLE_HOME/precomp/demo/profor directory. By default, all programs are dynamically linked with the client shared library.
To run the demonstration programs, the demonstration tables created by the $ORACLE_HOME/sqlplus/demo/demobld.sql script must exist in the SCOTT schema with the password TIGER.
Note:
You must unlock the SCOTT account and set the password before creating the demonstrations.To create the demonstration programs, use the demo_profor.mk make file, located in the $ORACLE_HOME/precomp/demo/profor directory. For example, to precompile, compile, and link the sample1 demonstration program, run the following command:
$ make -f demo_profor.mk sample1
To create the Pro*FORTRAN demonstration programs, run the following command:
$ make -f demo_profor.mk samples
Some demonstration programs require you to run a SQL script that is located in the $ORACLE_HOME/precomp/demo/sql directory. If you do not run the script, then a message prompting you to run it is displayed.
To build a demonstration program and run the corresponding SQL script, include the make macro argument RUNSQL=run on the command line. For example, to create the sample11 demonstration program and run the required $ORACLE_HOME/precomp/demo/sql/sample11.sql script, run the following command:
$ make -f demo_profor.mk sample11 RUNSQL=run
To create the Pro*FORTRAN demonstration programs and run all the required SQL scripts, run the following command:
$ make -f demo_profor.mk samples RUNSQL=run
You can use the $ORACLE_HOME/precomp/demo/profor/demo_profor.mk make file to create user programs. This make file builds either 32-bit or 64-bit user programs. You can also use the demo_profor_32.mk make file to build 32-bit user programs. The following table shows the make files that you can use to build 32-bit and 64-bit user programs with Pro*FORTRAN:
| Platform | 64-bit Make File | 32-Bit Make File |
|---|---|---|
| AIX, HP-UX, and Solaris SPARC | demo_profor.mk |
demo_profor_32.mk |
See Also:
The make file for more information about creating user programsTo create a program using the demo_proc.mk make file, run a command similar to the following:
$ make -f demo_profor.mk target FORS="forfile1 forfile2 ..." EXE=exename
In this example:
target is the make file target that you want to use
forfilen is the FORTRAN source for the program
exename is the executable program
For example, to create the program myprog from the Pro*FORTRAN source file myprog.pfo, run one of the following commands, depending on the type of executable that you want to create:
For an executable dynamically linked with the client shared library, run the following command:
$ make -f demo_profor.mk build FORS=myprog.f EXE=myprog
For an executable statically linked with the client shared library, run the following command:
$ make -f demo_profor.mk build_static FORS=myprog.f EXE=myprog
Note:
The information in this section applies to the AIX platform.Before using SQL*Module for Ada, verify that the correct version of the compiler is installed.
See Also:
Oracle Database Installation Guide for information about required compiler versions
Oracle SQL*Module for Ada Programmer's Guide for information about SQL*Module for Ada
This section contains the following topics:
Demonstration programs are provided to show the features of SQL*Module for Ada. All demonstration programs are located in the $ORACLE_HOME/precomp/demo/modada directory. By default, all programs are dynamically linked with the client shared library.
To run the ch1_drv demonstration program, the demonstration tables created by the $ORACLE_HOME/sqlplus/demo/demobld.sql script must exist in the SCOTT schema with the password TIGER.
Note:
You must unlock the SCOTT account and set the password before creating the demonstrations.The demcalsp and demohost demonstration programs require that the sample college database exists in the MODTEST schema. You can use the appropriate make command to create the MODTEST schema and load the sample college database.
Run the following command to create the SQL*Module for Ada demonstration programs, run the necessary SQL scripts to create the MODTEST user, and create the sample college database:
$ make -f demo_modada.mk all RUNSQL=run
To create a single demonstration program (demohost) and run the necessary SQL scripts to create the MODTEST user, and create the sample college database, run the following command:
$ make -f demo_modada.mk makeuser loaddb demohost RUNSQL=run
To create the SQL*Module for Ada demonstration programs, without re-creating the sample college database, run the following command:
$ make -f demo_modada.mk samples
To create a single demonstration program (demohost), without re-creating the sample college database, run the following command:
$ make -f demo_modada.mk demohost
To run the programs, you must define an Oracle Net connect string or alias named INST1_ALIAS that is used to connect to the database where the appropriate tables exist.
You can use the $ORACLE_HOME/precomp/demo/modada/demo_modada.mk make file to create user programs. To create a user program with the demo_modada.mk make file, run a command similar to the following:
$ make -f demo_modada.mk ada OBJS="module1 module2 ..." \ EXE=exename MODARGS=SQL_Module_arguments
In this example:
modulen is a compiled Ada object
exename is the executable program
SQL_Module_arguments are the command-line arguments to be passed to the SQL*Module
See Also:
Oracle SQL*Module for Ada Programmer's Guide for information about SQL*Module for AdaBefore you use the Oracle Call Interface (OCI) or Oracle C++ Call Interface (OCCI), verify that the correct version of C or C++ is installed.
See Also:
Oracle Database Installation Guide for information about supported compiler versions
Oracle Call Interface Programmer's Guide or Oracle C++ Call Interface Programmer's Guide for information about OCI and OCCI
This section contains the following topics:
Demonstration programs that show the features of OCI and OCCI are provided with the software through the Oracle Database 11g Examples media. There are two types of demonstration programs: C and C++. All demonstration programs are located in the $ORACLE_HOME/rdbms/demo directory. By default, all programs are dynamically linked with the client shared library.
To run the demonstration programs, the programs require the demonstration tables created by the $ORACLE_HOME/sqlplus/demo/demobld.sql script to exist in the SCOTT schema with the password TIGER. Some demonstration programs require specific .sql files to be run, as mentioned in the demonstration source files. OCCI demonstration programs require occidemo.sql to be run.
Note:
You must unlock the SCOTT account and set the password before creating the demonstrations.Use the demo_rdbms.mk make file, which is located in the $ORACLE_HOME/rdbms/demo directory, to create the demonstration programs. For example, to compile and link the cdemo1 demonstration program, run the following command:
$ make -f demo_rdbms.mk cdemo1
To create the C demonstration programs for OCI, run the following command:
$ make -f demo_rdbms.mk demos
To create the C++ demonstration programs for OCCI, run the following command:
$ make -f demo_rdbms.mk occidemos
You can use the $ORACLE_HOME/rdbms/demo/demo_rdbms.mk make file to build user programs. This make file builds either 32-bit or 64-bit user programs. You can also use the demo_rdbms32.mk to build 32-bit user programs on a 64-bit operating system. The following table shows the make files that you can use to build 32-bit and 64-bit user programs with Pro*FORTRAN:
| Platform | 64-bit Make File | 32-Bit Make File |
|---|---|---|
| AIX, HP-UX, Solaris SPARC, and Linux x86-64 | demo_rdbms.mk |
demo_rdbms32.mk |
| Linux x86 | NA | demo_rdbms.mk |
See Also:
The make file for more information about building user programsNote:
The information in this section applies to AIX, HP-UX, Linux x86-64, and Solaris SPARC platforms.
You can use the instructions and make files described in this section to create JDBC/OCI user programs that use a 64-bit driver.
To run JDBC/OCI demonstration programs with a 64-bit driver:
Add $ORACLE_HOME/jdbc/lib/ojdbc5.jar to the start of the CLASSPATH environment variable value for each of the following files:
jdbc/demo/samples/jdbcoci/Makefile jdbc/demo/samples/generic/Inheritance/Inheritance1/Makefile jdbc/demo/samples/generic/Inheritance/Inheritance2/Makefile jdbc/demo/samples/generic/Inheritance/Inheritance3/Makefile jdbc/demo/samples/generic/JavaObject1/Makefile jdbc/demo/samples/generic/NestedCollection/Makefile
In the $ORACLE_HOME/jdbc/demo/samples/generic/Makefile file, modify the JAVA and JAVAC variables to specify the JDK location and the -d64 flag as follows:
JAVA=${ORACLE_HOME}/java/bin/java -d64
JAVAC=${ORACLE_HOME}/java/bin/javac -d64
Set the LD_LIBRARY_PATH_64 environment variable to include the $ORACLE_HOME/lib directory.
Note:
On AIX, theLIBPATH variable is the LD_LIBRARY_PATH_64 variable equivalent. You must use the LIBPATH variable on AIX instead of the LD_LIBRARY_PATH_64 variable.Oracle recommends that you use the demo_product.mk make files provided with the software to create user programs as described in the product-specific sections of this chapter. If you modify the provided make file or if you choose to use a custom-written make file, then remember that the following restrictions apply:
Do not modify the order of the Oracle libraries. Oracle libraries are included on the link line more than once so that all the symbols are resolved during linking.
Except for AIX, the order of the Oracle libraries is essential on all platforms for the following reasons:
Oracle libraries are mutually referential. For example, functions in library A call functions in library B, and functions in library B call functions in library A.
The HP-UX linkers are one-pass linkers. The AIX, Linux, and Solaris linkers are two-pass linkers.
Add the library to the beginning or to the end of the link line. Do not place user libraries between the Oracle libraries.
If you choose to use a make utility such as nmake or GNU make, then you must be aware of how macro and suffix processing differs from the make utility provided with the operating system. Oracle make files are tested and supported with the make utility.
Oracle library names and the contents of Oracle libraries are subject to change between releases. Always use the demo_product.mk make file that ships with the current release as a guide to determine the required libraries.
Oracle provides the symfind utility to assist you in locating a library or object file where a symbol is defined. When linking a program, undefined symbols are a common error that produce an error message similar to the following:
$ make -f demo_proc.mk sample1 Undefined first referenced symbol in file sqlcex sample1.o sqlglm sample1.o ld: irrecoverable: Symbol referencing errors. No output written to sample1
The error occurs when the linker cannot find a definition for a referenced symbol. If this error message is displayed, then verify that the library or object file containing the definition exists on the link line and that the linker is searching the correct directories for the file.
The following example shows the output from the symfind utility, which is used to locate the sqlcex symbol:
$ symfind sqlcex
SymFind - Find Symbol <sqlcex> in <**>.a, .o, .so
------------------------------------------------------
Command: /u01/app/oracle/product/11.2.0/bin/symfind sqlcex
Local Directory: /u01/app/oracle/product/11.2.0
Output File: (none)
Note: I do not traverse symbolic links
Use '-v' option to show any symbolic links
Locating Archive and Object files ...
[11645] | 467572| 44|FUNC |GLOB |0 |8 |sqlcex
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ./lib/libclntsh.sl
[35] | 0| 44|FUNC |GLOB |0 |5 |sqlcex
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ./lib/libsql.a
The Oracle libraries provided with this release are thread-safe, they support multithreaded applications.
Oracle Database uses signals for two-task communication. Signals are installed in a user process when the process connects to the database and are removed when it disconnects.
Table 6-5 describes the signals that Oracle Database uses for two-task communication.
Table 6-5 Signals for Two-Task Communication
| Signal | Description |
|---|---|
|
The pipe driver uses SIGCLD, also referred to as SIGCHLD, when an Oracle process terminates. The operating system kernel sends a SIGCLD signal to the user process. The signal handler uses the |
|
|
The pipe two-task driver uses SIGCONT to send out-of-band breaks from the user process to the Oracle process. |
|
|
Two-task drivers use SIGINT to detect user interrupt requests. The Oracle process does not catch SIGINT; the user process catches it. |
|
|
Oracle Net protocols use SIGIO to indicate incoming networking events. |
|
|
The pipe driver uses SIGPIPE to detect end-of-file on the communications channel. When writing to the pipe, if no reading process exists, then a SIGPIPE signal is sent to the writing process. Both the Oracle process and the user process catch SIGPIPE. SIGCLD is similar to SIGPIPE, but it applies only to user processes, not to Oracle processes. |
|
|
The pipe driver uses SIGTERM to signal interrupts from the user to the Oracle process. This occurs when the user presses the interrupt key, Ctrl+C. The user process does not catch SIGTERM; the Oracle process catches it. |
|
|
Oracle Net TCP/IP drivers use SIGURG to send out-of-band breaks from the user process to the Oracle process. |
The listed signals affect all precompiler applications. You can install one signal handler for SIGCLD (or SIGCHLD) and SIGPIPE when connected to the Oracle process. If you call the osnsui() routine to set it up, then you can have multiple signal handles for SIGINT. For SIGINT, use osnsui() and osncui() to register and delete signal-catching routines.
You can also install as many signal handlers as you want for other signals. If you are not connected to the Oracle process, then you can have multiple signal handlers.
Example 6-1 shows how to set up a signal routine and a catching routine.
Example 6-1 Signal Routine and Catching Routine
/* user side interrupt set */ word osnsui( /*_ word *handlp, void (*astp), char * ctx, _*/) /* ** osnsui: Operating System dependent Network Set User-side Interrupt. Add an ** interrupt handling procedure astp. Whenever a user interrupt(such as a ^C) ** occurs, call astp with argument ctx. Put in *handlp handle for this ** handler so that it may be cleared with osncui. Note that there may be many ** handlers; each should be cleared using osncui. An error code is returned if ** an error occurs. */ /* user side interrupt clear */ word osncui( /*_ word handle _*/ ); /* ** osncui: Operating System dependent Clear User-side Interrupt. Clear the ** specified handler. The argument is the handle obtained from osnsui. An error ** code is returned if an error occurs. */
Example 6-2 shows how to use the osnsui() and the osncui() routines in an application program.
Example 6-2 osnsui() and osncui() Routine Template
/*
** User interrupt handler template.
*/
void sig_handler()
{
...
}
main(argc, argv)
int arc;
char **argv;
{
int handle, err;
...
/* Set up the user interrupt handler */
if (err = osnsui(&handle, sig_handler, (char *) 0))
{
/* If the return value is nonzero, then an error has occurred
Take appropriate action for the error. */
...
}
...
/* Clear the interrupt handler */
if (err = osncui(handle))
{
/* If the return value is nonzero, then an error has occurred
Take appropriate action for the error. */
...
}
...
}
Oracle XA is the Oracle implementation of the X/Open Distributed Transaction Processing XA interface. The XA standard specifies a bidirectional interface between resource managers that provide access to shared resources within transactions, and between a transaction service that monitors and resolves transactions.
Oracle Call Interface has XA functionality. When building a TP-monitor XA application, ensure that the TP-monitor libraries (that define the symbols ax_reg and ax_unreg) are placed in the link line before the Oracle client shared library. This link restriction is required when using the XA dynamic registration (Oracle XA switch xaoswd).
Oracle Database XA calls are defined in both the client shared library (libclntsh.a, libclntsh.sl, libclntsh.so, or libclntsh.dylib depending on the platform) and the client static library (libclntst11.a). These libraries are located in the $ORACLE_HOME/lib directory.
|
 Copyright © 2006, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|