Oracle® TimesTen In-Memory Database Troubleshooting Procedures Guide Release 11.2.1 Part Number E13075-02 |
|
|
View PDF |
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.
This guide has information about the following new features:
Monitoring the usage of the cache administration user's tablespace
Considerations when the cache administration user's tablespace is full
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".
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."
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".
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.
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.
There is a new method for improving autorefresh performance: "Unresponsive or dead TimesTen database degrades autorefresh performance".
Additional methods for improving replication or XLA performance were added to "Poor replication or XLA performance".