IMPORTANT PRE-REQUISITES
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
> build_sampledb.batUnix/Linux: $ cd quickstart/sample_scripts/createdb
$ ./build_sampledb.sh2. 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 ODBC programs
To compile the sample programs in the sample_code/odbc 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 specific sample program in the sample_code/odbc 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 bulkinsert program, you do:
| [Windows] | > nmake bulkinsert.exe** | |
| [Linux/Unix] | $ make bulkinsert |
** 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 ODBC executables are built and shipped by default on Windows.
How to run the sample ODBC programs
| bulkinsert | This program implements and measures time needed for insertion of many rows into a table. Parameters allow you to specify whether there are indexes on the table and whether statistics should be computed after doing the inserts. You can also specify insertion of the rows in batches to achieve better performance. |
Examples:
(10,000 rows, batchsize 256, no indexes)
bulkinsert
(50,000 rows, batchsize 256, no indexes)
bulkinsert -r 50000
(5,000 rows, batchsize 512, 3 indexes)
bulkinsert -r 5000 -s 512 -i 3
For full syntax of the program, try "bulkinsert -help".
| plsqlODBC | This sample program uses ODBC 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 ODBC 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. |
Example usage:
(run the program using the default DSN and default user , it will prompt for the password)
plsqlODBC
(run the program specifying the DSN and username, it will prompt for the password)
plsqlODBC -connstr "DSN=sampledb_1121;UID=appuser"
(run the program specifying the DSN, username and password)
plsqlODBC -connstr "DSN=sampledb_1121;UID=appuser;PWD=mypassword"
For full syntax of the program, try "plsqlODBC -help".
| tpcb | This program implements a TPCB-like workload benchmark. The code populates the ACCOUNTS, BRANCHES, and TELLERS tables. It then executes a modified version of the TPCB benchmark, performing 25,000 transactions. Each transaction updates the balance in the ACCOUNTS, BRANCHES and TELLERS tables, fetches the new balance from the ACCOUNTS table, and appends a record to the HISTORY table. At termination, it prints the measured performance. |
Examples
(25,000 transactions, scale 1)
tpcb
(250,000 transactions, scale 2)
tpcb -xact 250000 -scale 2
For full syntax of the program, try "tpcb -help".
| tptbm | 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 can also be included in the transaction mix. The ratio of SELECTs, UPDATEs and INSERTs 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 tptbm.c. |
Examples:
(80% reads, 20% updates, 1 process, 10,000 transactions)
tptbm
(80% reads, 20% updates, 2 process, 100,000 transactions, random number generator uses 3 as the seed)
tptbm -proc 2 -xact 100000 -seed 3
(85% reads, 10% inserts, 5% updates, 1 process, 10,000 transactions)
tptbm -read 85 -insert 10
For full syntax of the program, try "tptbm -help").
| wiscbm | This program implements and measures a subset of queries from the Wisconsin benchmark. It will run about 30 queries, the first batch without indexes and the second batch with indexes. When finished, a report of the response time per query is generated. |
Example usage:
(scale 1, all queries, read-committed isolation)
wiscbm
(scale 5, all queries, read-committed isolation)
wiscbm -scale 2
(scale 2, only queries [1, 3, 5-7, 10-14, 25], read-committed isolation)
wiscbm -scale 2 -q 1,3,5-7,10-14,25
For full syntax, try "wiscbm -help".
| xlaSimple | This particular ODBC sample program is available in the quickstart/sample_code/odbc/xla directory. This program demonstrates the usage of the TimesTen Transaction Log API (XLA) for C developers using ODBC. This program requires a user with XLA privilege to subscribe to changes in the database. This program subscribes to the table APPUSER.MYDATA in the sampledb_1121 database. If running the program without any parameters, the program uses the default xlauser user (created in the build_sampledb script). To generate changes to the APPUSER.MYDATA, use ttIsql to connect to sampledb_1121 under appuser. Then execute database transactions on the MYDATA table. |
Example usage:
(run the program, default user is xlauser, default database is sampledb_1121)
xlaSimple
To exit the program, press CTRL-C.
For full syntax, try "xlaSimple -help".
For more information on how to use ODBC to develop database programs for the TimesTen database, see the Oracle TimesTen In-Memory Database C Developer's Guide.
| Home | Site Map | Contact Us | Copyright © 2011 |