1/10

Contents

Expand All · Collapse All

Title and Copyright Information

Preface

• Audience
• Related documents
• Conventions
• Documentation Accessibility

What's New

• New features in release 11.2.2.7.0
• New features in release 11.2.2.5.0
• New features in release 11.2.2.1.0
• New features in release 11.2.2.0.0

1 Tools for Troubleshooting TimesTen

• Using the ttCapture utility
• Using the ttIsql utility
• Using the ttStatus 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
  • DEADLOCK 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 Databases

• 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 database in direct mode
  • Upgrading your database
  • Privileges to connect to database
  • Check file system permissions to access database
  • Check that the TimesTen daemon is running
  • Check DSN definition
    • Check DSN attributes
    • Check path name to database 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 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 database
• Application connects or disconnects are slow
  • Check if database is being recovered
  • Check ODBC tracing
• Application is disconnected unexpectedly
  • Check for ODBC, JDBC, OCI, Pro*C, and PL/SQL application 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
  • Check temporary DSN attribute
  • Check Overwrite DSN attribute
  • Check path name to database
• 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 database
    • Permanent memory region filling up
    • Temporary memory region filling up
  • Update query optimizer statistics
  • Check memory used by queries
  • Out of memory after fatal crash of the database
  • Check transaction log file use of disk space
  • Check if tracing is enabled
  • Check the semaphore limit
• Duplicate results from a SELECT statement
• Cannot attach PL/SQL shared memory

3 Troubleshooting TimesTen Application-Tier 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
  • Check NLS environment variables
• Recovering cache grid after unexpected system shutdown
  • A portion of the cache grid nodes are still running
  • All cache grid nodes exited unexpectedly
• Unable to resolve Oracle Service Name
• Unable to resolve connect identifier
• Incompatible Oracle Database Server and Client versions
• Unable to validate the Oracle database username and password
  • Check library path environment variable
  • Check status of TNS listener and Oracle Database Server
  • Check the Oracle database privileges
  • Check DSN definition
  • Reboot TimesTen machine
  • Set the cache administration user name 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 Database
• DDL on cached Oracle database 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
• Optimize performance for TimesTen Cache
• Avoid performance and memory problems for large batch jobs on Oracle database tables
• Autorefresh not refreshing cache at the specified interval
  • Reset autorefresh state
  • Recover and reset autorefresh for the Oracle database objects
  • Avoid a lock timeout condition when modifying autorefresh mode, state, or interval
• Incremental autorefresh not progressing
  • Validate autorefresh for the Oracle database 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 tablespace of the cache administration 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
  • Autorefresh cache group refresh with excessive waiting on resources
  • Abnormally large change log and base tables degrade autorefresh performance
  • Fragmented autorefresh change log table space
  • Performance degrades when autorefresh interval is small
• Declaring NOVALIDATE on constraints causes cache group creation failure
• AWR report showing lock contention with DBMS_LOCK

4 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 when changing the state of a replication receiver
  • Problems using ttRepAdmin -duplicate
    • Database created before duplication
    • Wrong database or host name
  • 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
• Problems with parallel replication

5 Troubleshooting AWT Cache Groups

• Replication agent not started
• AWT performance monitoring
  • Enable AWT performance monitoring
  • Display AWT performance results with the ttRepAdmin utility
  • Using system tables to monitor AWT operations
• Possible causes of poor AWT performance
  • Problems on the Oracle Database
  • UNLOAD CACHE GROUP requires row updates to complete propagation
• Oracle Database errors reported by TimesTen for AWT
  • Permanent Oracle Database errors reported by TimesTen
  • Transient Oracle Database errors reported by TimesTen

Index