1. Set up sample database and user accounts
The following build_sampledb script should be run once to set up the sample database and user accounts
Windows: > cd quickstart/sample_scripts/createdb
Unix/Linux: $ cd quickstart/sample_scripts/createdb
2. Set up environment to compile and run the sample programs
The following script must be run for each of the terminal session:
Windows: > quickstart/ttquickstartenv.bat Unix/Linux: $ . quickstart/ttquickstartenv.sh OR
$ source quickstart/ttquickstartenv.csh
How to compile the sample OCI programs
To compile the sample programs in the sample_code/oci directory, you simply run the makefile supplied in the same directory. Note that the appropriate makefile is made available based on the platform of your TimesTen installation.
To build a sample program in the sample_code/oci directory, use the following command:
|[Windows]||> nmake <program-name>.exe**|
|[Linux/Unix]||$ make <program-name>|
|where <program-name> is the program you want to compile.|
For example, to compile the addemp program, you do:
|[Windows]||> nmake addemp.exe**|
|[Linux/Unix]||$ make addemp|
** On Windows, the "nmake" command must be run on a Visual Studio Command Prompt. If you do not use the Visual Studio Command Prompt, you must run the appropriate vcvars*.bat script to set the appropriate environment variables to support command line builds.
All of the OCI executables are built and shipped by default on Windows.
How to run the sample OCI programs
|addemp||This is an OCI program that prompts the users for information and inserts the corresponding data into a new employee into the EMP table.
You are prompted for the username and password at runtime.
The ‘servicename’ can be either an entry in the TNSnames.ora file or an easy connect string.
The EMP table needs to exist for this program to work.
A sample tnsnames.ora file is available at <install_dir>/network/admin/samples/tnsnames.ora.
(run the program using default DSN sampledb_1122 and default user appuser. For TNS Service Name, enter sampledb_1122; alternatively, using Easy Connect string, enter localhost/sampledb_1122:timesten_direct)
|plsqlOCI||This sample program uses OCI to access common PL/SQL packages (emp_pkg and sample_pkg) in four different ways:
- Calls a stored procedure with IN and OUT parameters
- Calls a stored function with IN and OUT parameters
- Calls an anonymous block and passes host variables into and out of the block
- Calls a store procedure to open a ref cursor and uses OCI to process the result-set of the ref cursor
The EMP table and the emp_pkg and sample_pkg PL/SQL packages need to exist for this program to work.
(run the program using the default user appuser and the default TNS Service Name sampledb_1122, will prompt for the password)
(run the program specifying the username, password and service name)
> plsqlOCI -user <myuser> -password <mypassword> -service <myservice>
For full syntax of the program, try "plsqlOCI -help".
|tptbmOCI||This program implements a multi-user throughput benchmark. By default, the transaction mix consists of 80% SELECT (read) transactions and 20% UPDATE (write) transactions. In addition to SELECTs and UPDATEs, INSERTs and DELETES can also be included in the transaction mix. The ratio of SELECTs, UPDATEs and INSERTs and DELETES is specified at the command line. Each transaction consists of one or more SQL operations.
The benchmark initially populates the data store, and then executes the transaction mix on it. The number of rows inserted as part of the transaction mix cannot exceed the number of rows with which the database is populated initially.
The measurement error for the benchmark is at most 2 seconds. This will be negligible at loads with a duration in excess of 200 seconds. A suggested load for the benchmark is one which lasts at least 600 seconds.
The schema for this test is described in the program source file tptbmOCI.c.
(80% reads, 20% updates for appuser@sampledb_1122 with 10,000 transactions in a database with 10,000 rows.)> tptbmOCI
(60% reads, 10% updates, 5% insert and 25% deletes with 1 SQL operation per transation for appuser@sampledb_1122)
> tptbmOCI -read 60 -update 10 -insert 5 -delete 25
(Use a workload with 3 selects, 1 insert and 1 update per transaction for appuser@sampledb_1122)
> tptbmOCI -multiop
(Use a client/server workload with 10 * (3 reads, 1 insert and 1 update) per transaction for appuser@sampledbCS_1122)
>tptbmOCI -multiop -min 10 -max 10 -service sampledbCS_1122
(80% reads, 20% updates for <myuser>@<myservice> with 1,000 transactions in the database with 332 (1,089) rows.)
> tptbmOCI -user <myuser> -service <myservice> -xact 1000 -key 33
For full syntax of the program, try "tptbmOCI -help".
For more information on OCI, refer to the OCI chapter in the .