Technical data

Troubleshooting OCI and Pro*C/C++ applications
2-16 Oracle TimesTen In-Memory Database Troubleshooting Procedures Guide
Troubleshooting OCI and Pro*C/C++ applications
On Windows, the NLS_LANG setting is taken from the registry if it is not in the
environment. If NLS_LANG is set to an unsupported value, such as NA, an OCI
connection failed error or an ORA-12705 error is thrown. If your OCI or Pro*C/C++
program has trouble connecting to TimesTen, verify that the setting of HKEY_LOCAL_
MACHINE\Software\ORACLE\NLS_LANG is valid and indicates a character set
supported by TimesTen. This is likely only an issue on machines that previously had
Oracle9i or earlier Oracle versions installed.
Refer to the "Globalization support" section in the OCI chapter of the Oracle TimesTen
In-Memory Database C Developer's Guide for more information on NLS_LANG.
Running out of a resource
This section describes what to check if TimesTen runs out of resources such as
memory space, disk space, file descriptors, and semaphores.
Operating system tools and shared memory
Operating system tools such as top, vmstat, and sar provide statistics about
processes and memory usage. The output from these tools can be misleading as an
indicator of TimesTen memory consumption because they report shared memory
usage for each process but do not report total shared memory usage. Adding together
various memory statistics for TimesTen processes overestimates the amount of
memory used by TimesTen because shared memory is by definition shared.
Check the amount of memory allocated to the data store
TimesTen uses both permanent and temporary data partitions. The amount of
memory allocated for these partitions is set by the PermSize and TempSize attributes
in the DSN definition for the data store.
Symptom See...
Memory consumption seems high. "Operating system tools and shared memory" on
page 2-16
Running out of memory space
■ "Operating system tools and shared memory" on
page 2-16
■ "Check the amount of memory allocated to the data
store" on page 2-16
■ "Update query optimizer statistics" on page 2-18
■ "Check memory used by queries" on page 2-18
■ "Check available swap space (virtual memory)" on
page 2-18
Running out of disk space "Check transaction log file use of disk space" on
page 2-18
Running out of transaction log
space
"Check transaction log file use of disk space" on
page 2-18
Running out of file descriptors "Increase the number of available file descriptors" on
page 2-6
Running out of semaphores "Check the semaphore limit" on page 2-20
Running out of CPU Obtain a stack trace and contact Technical support.