Skip Headers
Oracle® TimesTen In-Memory Database Troubleshooting Procedures Guide
Release 11.2.1
Part Number E13075-02
Home
Book List
Index
Master Index
Contact Us
Next
View PDF
Contents
Title and Copyright Information
Preface
Audience
Related documents
Conventions
Documentation Accessibility
Technical support
What's New
New features for release 11.2.1
1
Tools for Troubleshooting TimesTen
Using the ttIsql utility
Using the ttStatus utility
Using the ttCapture utility
Using the logs generated by the TimesTen daemon
Using the ttTraceMon utility
Starting a trace and reading the trace buffer
SQL tracing
API tracing
LOCK tracing
ERR tracing
AGING tracing
AUTOREFRESH tracing
Using the ttXactAdmin utility
Using ODBC tracing
Using SNMP traps to detect events
Monitoring the TimesTen system tables
Using the query optimizer
2
Troubleshooting TimesTen Applications and Data Stores
Unable to start or stop TimesTen daemon
No response from TimesTen daemon or subdaemon
Check the TimesTen user error log
Extract a stack trace from the core file
Unable to create shared segment
Application unable to connect to data store in direct mode
Upgrading your data store
Privileges to connect to data store
Check file system permissions to access data store
Check that the TimesTen daemon is running
Check DSN definition
Check DSN attributes
Check path name to data store and transaction log directories
Manage semaphores and shared memory segments
Check available swap space (virtual memory)
Increase the number of available file descriptors
Troubleshooting Client/Server problems
Cannot connect to the TimesTen Server
TimesTen Server failed
Cannot find TimesTen Server DSN
TimesTen Server failed to load DRIVER
Application times out when accessing TimesTen Server
TimesTen Client loses connection with TimesTen Server
Failed to attach to shared memory segment for IPC
Increasing the maximum server connections on Windows XP
Thread stack overflow when using multiple client connections
Out of space when DSN specifies new data store
Application connects or disconnects are slow
Check if data store is being recovered
Check ODBC tracing
Application becomes disconnected unexpectedly
Check for ODBC or JDBC errors
Check the user error log
Application is slow
Consider connection mode
Update statistics for your tables
Verify lock and isolation levels
Check trace settings
Check partition counts for the tables
Application unresponsive, appears hung
Check logs and gather trace information
Check for ODBC errors
Check for deadlocks and timeouts
Application unable to find previously created objects
Specify object owner
Check privilege to access tables
Check temporary DSN attribute
Check Overwrite DSN attribute
Check path name to data store
Troubleshooting OCI and Pro*C/C++ applications
Running out of a resource
Operating system tools and shared memory
Check the amount of memory allocated to the data store
Permanent segment filling up
Temporary segment filling up
Update query optimizer statistics
Check memory used by queries
Check available swap space (virtual memory)
Check transaction log file use of disk space
Check the semaphore limit
Duplicate results from a SELECT statement
Cannot attach PL/SQL shared memory
3
Troubleshooting Installation, Upgrades and Downgrades
Installing 32-bit TimesTen on 64-bit Windows
Downgrading a data store with Oracle data types to TimesTen 6.0
4
Troubleshooting Oracle In-Memory Database Cache
Unable to create a cache group
Unable to start or stop the cache agent
Check status of the cache agent
Check ORACLE_HOME environment variable
Unable to resolve Oracle Service Name
Unable to resolve connect identifier
Incompatible Oracle Server and Client versions
Unable to validate Oracle username and password
Check library path environment variable
Check status of TNS listener and Oracle Server
Check Oracle privileges
Check DSN definition
Reboot TimesTen machine
Set the cache administration user id and password
Check user and system environment
Verify the loaded dynamic libraries
OCI initialization failed
Unsupported data type mapping
Null constraint does not match Oracle
DDL operations on cached Oracle tables may cause cache group operations to fail
Changes not visible after updating object in cache group
Loading or refreshing fails
Monitoring autorefresh cache groups
Using the ttCacheAutorefreshStatsGet procedure
Displaying information from the change log tables
Understanding messages about autorefresh in the support log
Diagnosing autorefresh failure
Diagnosing autorefresh performance problems
Using SNMP traps for alerts about autorefresh problems
Autorefresh not refreshing cache at the specified interval
Reset autorefresh state
Recover and reset autorefresh oracle objects
Incremental autorefresh not progressing
Validate autorefresh Oracle objects
Incremental autorefresh becomes full autorefresh
Detecting when incremental autorefresh becomes full
Understanding the cache administration user tablespace
Diagnosing a full cache administration user tablespace
Monitoring the usage of the cache administration user's tablespace
Considerations when the cache administration user's tablespace is full
Poor autorefresh performance
Unresponsive or dead TimesTen database degrades autorefresh performance
Setting cached TimesTen database timeout
Configuring recovery method for certain cache groups
5
Troubleshooting AWT Cache Groups
Unable to start or stop replication agent
Replication does not work
Using SNMP traps for notification of replication events
Monitoring AWT performance
Possible causes of poor AWT performance
Permanent Oracle errors reported by TimesTen
Transient Oracle errors reported by TimesTen
6
Troubleshooting Replication
Unable to create a replication scheme
Unable to alter a replication scheme
Unable to start or stop replication agent
Using SNMP traps for notification of replication events
Replication does not work
Check status of TimesTen daemon and replication agents
Check that replication agents are communicating
Check replication state
Check replication scheme configuration
Check ttRepAdmin -showconfig
Check the TTREP.TTSTORES table
Check host names
Check owner names
Checking replication owner
Checking table owner
Check consistency between replicated tables
Replication unresponsive, appears hung
Check replication state
Check return receipt timeout setting
Poor replication or XLA performance
Check network bandwidth
Check use of return receipt blocking
Check replication configuration
Check size of log buffer
Check durability settings
Check for reads from transaction log files
Problems using ttRepAdmin
Problems using ttRepAdmin -duplicate
Returns 'Must specify -scheme' error
Problems with conflict checking
Column cannot be used for replication timestamp
Timestamp does not exist
Conflict reporting slows down replication
Index
Scripting on this page enhances content navigation, but does not change the content in any way.