Skip Headers
Oracle® TimesTen In-Memory Database Troubleshooting Procedures Guide
Release 11.2.1

Part Number E13075-07
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

What's New

This section summarizes the new features and functionality of Oracle TimesTen In-Memory Database Release 11.2.1 that are documented in this guide, providing links into the guide for more information.

New features in release 11.2.1.7.0

This guide has information about the following new enhancements:

New features in release 11.2.1.6.0

This guide now has more information about improving performance for the IMDB cache, which are described in the following sections:

New features in release 11.2.1.0

This guide has information about the following new features:

Issues with the NLS_LANG environment variable

On Windows, if the NLS_LANG environment variable is set to an unsupported value, such as NA, you could experience problems connecting. See "Troubleshooting OCI and Pro*C/C++ applications".

Cannot attach PL/SQL memory

See "Cannot attach PL/SQL shared memory" on how to recover if you receive error 8517 "Cannot attach PL/SQL shared memory; PLSQL_MEMORY_ADDRESS not valid or already in use."

Changes not visible after updating object in cache group

If you modify an object in a cache group and then the changes do not appear on a subsequent SQL statement, then see "Changes not visible after updating object in cache group".

Monitoring the usage of the cache administration user's tablespace

To monitor the cache administration user tablespace, you can use either Oracle Enterprise Manager alerts or set the TimesTen tablespace threshold parameter. See "Monitoring the usage of the cache administration user's tablespace" for details.

Considerations when the cache administration user's tablespace is full

With Oracle tables that are cached in a TimesTen database, you can configure them to use incremental automatic refresh. See "Considerations when the cache administration user's tablespace is full" on how to specify what is to occur when the cache administration user's tablespace is full.

Poor autorefresh performance

There is a new method for improving autorefresh performance: "Unresponsive or dead TimesTen database degrades autorefresh performance".

Poor replication or XLA performance

Additional methods for improving replication or XLA performance were added to "Poor replication or XLA performance".