Install Procob Oracle 11g
6.1.2 Relinking Precompiler Executables Use the $ORACLEHOME/precomp/lib/insprecomp.mk make file to relink all precompiler executables. To manually relink a particular precompiler executable, enter the following command: $ make -f insprecomp.mk relink exename = executablename This command creates the new executable in the $ORACLEHOME/precomp/lib directory, and then moves it to the $ORACLEHOME/bin directory. In the preceding example, replace executable with one of the product executables listed in. Lists the executables for Oracle Precompilers. 6.1.4 Issues Common to All Precompilers 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. Vendor Debugger Programs 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.
6.1.5 Static and Dynamic Linking 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 together 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: More than one application or call to the same application can use the same dynamic library.
Install procob for Oracle 11gR2 1. Procob does not in the. Installation guides for Oracle Database 11g and accompanying products on various platforms are. Install procob for Oracle 11gR2 1. Procob does not in the Oracle server installer, you must install Oracle client to get procob installed. Procob does not installed by default, it must be selected explicit.
Oracle 11g Installation Guide
Reduced main memory requirements: The same dynamic library image is loaded into main memory only once, and it can be shared by more than one application. 6.1.6 Client Shared and Static Libraries The client shared and static libraries are located in the $ORACLEHOME/lib or $ORACLEHOME/lib32 directories. If you use the Oracle-provided demo product.mk make 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 Can't 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 $ORACLEHOME/lib32 AIX (64-bit applications) LIBPATH $ORACLEHOME/lib HP-UX (32-bit applications) SHLIBPATH $ORACLEHOME/lib32 HP-UX (64-bit applications) and Linux LDLIBRARYPATH $ORACLEHOME/lib Solaris (32-bit applications) LDLIBRARYPATH $ORACLEHOME/lib32 Solaris (64-bit applications) LDLIBRARYPATH64 $ORACLEHOME/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: $ $ORACLEHOME/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 demordbms32.mk buildnopthread EXE=oci02 OBJS=oci02.o. For 64-bit applications: $ make -f demordbms.mk buildnopthread EXE=oci02 OBJS=oci02.o. 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 11 g release 1 (11.1) 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. 6.3.1 Pro.C/C Demonstration Programs 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 $ORACLEHOME/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 $ORACLEHOME/sqlplus/demo/demobld.sql script to exist in the JONES schema with the password.
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 demoproc.mk sample1 $ make -f demoproc.mk sample1 To create all the C demonstration programs for Pro.C/C, run the following command: $ make -f demoproc.mk samples To create all the C demonstration programs for Pro.C/C, run the following command: $ make -f demoproc.mk cppsamples To create all the Object demonstration programs for Pro.C/C, run the following command: $ make -f demoproc.mk objectsamples Some demonstration programs require you to run a SQL script, located in the $ORACLEHOME/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 $ORACLEHOME/precomp/demo/sql/sample9.sql script, run the following command: $ make -f demoproc.mk sample9 RUNSQL=run To create all the Object demonstration programs and run all the required SQL scripts, run the following command: $ make -f demoproc.mk objectsamples RUNSQL=run.
Note: 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 demoproc.mk make file, run a command similar to the following: $ make -f demoproc.mk target OBJS=' objfile1 objfile2.' Table 6-4 Pro.COBOL Naming Conventions Item Naming Convention Executable procob or procob32 Demonstration directory procob2 Make file demoprocob.mk or demoprocob32.mk 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 $ORACLEHOME/bin directory. This section contains the following topics:. 6.4.2 Pro.COBOL Oracle Runtime System 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. Note: You must unlock the JONES account and set the password before creating the demonstrations. See Also: The make file for more information about creating user programs To create a program using the demoprocob.mk make file, run a command similar to the following: $ make -f demoprocob.mk target COBS=' cobfile1 cobfile2.' Note: You must unlock the JONES account and set the password before creating the demonstrations.
To create the demonstration programs, use the demoprofor.mk make file, located in the $ORACLEHOME/precomp/demo/profor directory. For example, to precompile, compile, and link the sample1 demonstration program, run the following command: $ make -f demoprofor.mk sample1 To create the Pro.FORTRAN demonstration programs, run the following command: $ make -f demoprofor.mk samples Some demonstration programs require you to run a SQL script that is located in the $ORACLEHOME/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 $ORACLEHOME/precomp/demo/sql/sample11.sql script, run the following command: $ make -f demoprofor.mk sample11 RUNSQL=run To create the Pro.FORTRAN demonstration programs and run all the required SQL scripts, run the following command: $ make -f demoprofor.mk samples RUNSQL=run. See Also: The make file for more information about creating user programs To create a program using the demoproc.mk make file, run a command similar to the following: $ make -f demoprofor.mk target FORS=' forfile1 forfile2.' Note: You must unlock the JONES 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. 6.6.2 SQL.Module for Ada User Programs You can use the $ORACLEHOME/precomp/demo/modada/demomodada.mk make file to create user programs. To create a user program with the demomodada.mk make file, run a command similar to the following: $ make -f demomodada.mk ada OBJS=' module1 module2.' EXE= exename MODARGS= SQLModulearguments In this example:. modulen is a compiled Ada object. exename is the executable program.
SQLModulearguments are the command-line arguments to be passed to the SQL.Module. 6.7.1 OCI and OCCI Demonstration Programs Demonstration programs that show the features of OCI and OCCI are provided with the software through the Oracle Database 11 g Examples media. There are two types of demonstration programs: C and C.
All demonstration programs are located in the $ORACLEHOME/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 $ORACLEHOME/sqlplus/demo/demobld.sql script to exist in the JONES schema with the password. Some of the 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 JONES account and set the password before creating the demonstrations.
Use the demordbms.mk make file, which is located in the $ORACLEHOME/rdbms/demo directory, to create the demonstration programs. For example, to compile and link the cdemo1 demonstration program, run the following command: $ make -f demordbms.mk cdemo1 To create the C demonstration programs for OCI, run the following command: $ make -f demordbms.mk demos To create the C demonstration programs for OCCI, run the following command: $ make -f demordbms.mk occidemos.
6.9 Custom Make Files 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. If you want to add the library to the link line, then add it 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.
6.10 Correcting Undefined Symbols 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 demoproc.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 in.a,.o,.so - Command: /u01/app/oracle/product/11.1.0/bin/symfind sqlcex Local Directory: /u01/app/oracle/product/11.1.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. Table 6-5 Signals for Two-Task Communication Signal Description SIGCLD 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 wait routine to determine if a server process died. The Oracle process does not catch SIGCLD; the user process catches it. SIGCONT The pipe two-task driver uses SIGCONT to send out-of-band breaks from the user process to the Oracle process.
SIGINT Two-task drivers use SIGINT to detect user interrupt requests. The Oracle process does not catch SIGINT; the user process catches it. SIGIO Oracle Net protocols use SIGIO to indicate incoming networking events.
SIGPIPE 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. SIGTERM 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. SIGURG 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 more than one signal handle 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. 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.
Mar 23, 2014 Program za dizajniranje kuca. Kako napraviti ogradu za. Program za projektovanje kuca. Program za projektovanje kuca.
code is returned if an error occurs./ shows how to use the osnsui and the osncui routines in an application program. 6.13 XA Functionality 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.
Oracle 12c Processes Parameter
When building a TP-monitor XA application, ensure that the TP-monitor libraries (that define the symbols axreg and axunreg) 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 $ORACLEHOME/lib directory. Scripting on this page enhances content navigation, but does not change the content in any way.