This section summarizes the new features and functionality of Oracle TimesTen In-Memory Database Release 11.2.2 that are documented in this guide, providing links into the guide for more information.
If you try to change the state of a replication receiver when replication has been configured to use a secondary IP address, a misconfiguration of the /etc/hosts file may cause ttRepAdmin to print an error. See "Problems when changing the state of a replication receiver" for more information.
If you provide an incorrect host name for a subscriber or have made an error entering the subscriber database name or host name in the replication scheme, you may see an error. See "Wrong database or host name" for more information.
Additional information was added about possible causes for a loss in AWT performance. For more details, see "AWT performance monitoring".
The error log messages for the cache agent daemon were modified as follows:
The TimesTen ORA component was often misunderstood to be the Oracle standard for Oracle messages. Now, the TimesTen ORA component is renamed to CAC.
Previously, the TimesTen error message was printed, but the message number was not identified. Now, the message number is included in all messages, so that the user can reference the error message guide for further details.
For an example of these changes, see "Understanding messages about autorefresh in the support log".
The following sections provide information to help you diagnose and remedy some of the problems encountered while using a TimesTen database:
|
Note: If you are still having problems with your database after following the troubleshooting recommendations in this chapter, please contact technical support. |
This section describes what to check if you are unable to start or stop the TimesTen main daemon.
| Possible cause | What to do |
|---|---|
| Incorrect privilege | You need the ADMIN privilege to start or stop the TimesTen daemon. Ensure that you are using the ttDaemonAdmin utility to start the daemon. The output from ttDaemonAdmin shows whether you have the correct privilege. |
| Another process is using the TimesTen daemon port. | Use the ttVersion utility to verify what port number the TimesTen daemon is expected to use. Use an operating system command like netstat to check whether another process is listening on the port. If there is a conflict, either change the port number used by the other process or use ttmodinstall to change the port used by TimesTen. |
| TimesTen daemon is already running. | Ensure that you are using the ttDaemonAdmin utility to start the daemon. The output from ttDaemonAdmin shows whether the daemon is already running. |
| Other problems | Inspect the user error log produced by the daemon. See "Using the logs generated by the TimesTen daemon". |
The following sections describe what to do if one or more of the TimesTen processes appears to be unavailable:
If you receive an error that indicates the TimesTen subdaemon has stopped, inspect the user error log, as described in "Using the logs generated by the TimesTen daemon".
If the TimesTen daemon crashes, it cannot send anything to the user error log, but the subdaemons send a 'main daemon vanished' message to the log before exiting:
09:24:13 Err : 4375 ------------------: Main daemon has vanished
Restart the daemon. The next connection to each database causes TimesTen to recover from the checkpoint and transaction log files. See "Working with the Oracle TimesTen Data Manager Daemon" in the Oracle TimesTen In-Memory Database Operations Guide.
If you experience a crash by one of the TimesTen processes on a UNIX system and have exhausted all of the diagnostic options, check to see if TimesTen has generated a core file. Use the ttVersion utility to find the core file. Look for a line in the output that shows a path for the daemon home directory:
TimesTen Release (ttuser:40732) 2011-04-04T17:53:04Z Instance admin: ttuser Instance home directory: /node1/ttuser/ttcur/TTBuild/linux86_dbg/install Daemon home directory: /node1/ttuser/ttcur/TTBuild/linux86_dbg/install/info
After locating the core file, attach to the debugger on the system and extract the stack trace from the core file and send the trace results to technical support.
On Windows systems you can obtain diagnostic information for a service failure by enabling the 'allow service to interact with desktop' option in the properties dialog for the TimesTen data manager in the Service menu. If a fatal fault occurs in the TimesTen data manager service, a pop-up asks if you would like to start the debugger. Contact technical support and provide the stack trace.
You may receive an error that indicates that a shared segment could not be created:
4671: TT14000: TimesTen daemon internal error: Error 28 creating shared segment, KEY 0x0201f7eb 4671: -- OS reports too many shared segments in use 4671: -- Confirm using 'ipcs' and take appropriate action 4671: 18538 ------------------: subdaemon process exited
Using the Linux ipcs command may display information like this:
------ Shared Memory Segments -------- key shmid owner perms bytes nattch status 0x00000000 1098350592 user1 777 10624 2 dest 0x00000000 1084817409 user1 777 2439680 2 dest 0x911fc211 1098383362 user2 666 67108864 1 0x2814afba 170721285 root 666 1048576 1
A status of dest means the memory segment is marked to be destroyed. nattch shows the number of processes still attached to the memory segment. The ipcrm command cannot free the shared memory until the processes detach from the segment or exit. If an application connects to TimesTen and then becomes inactive, nothing can free the shared memory until the user exits or stops the application.
This section describes what to check if your application is unable to connect to a database in direct mode.
| Possible cause | See... |
|---|---|
| Mismatch between the release of TimesTen and database | "Upgrading your database" |
User does not have the CREATE SESSION privilege. | "Privileges to connect to database" |
| Incorrect file permissions | "Check file system permissions to access database" |
| TimesTen daemon or Data Manager service not running | "Check that the TimesTen daemon is running" |
| Incompatible connection attributes or incorrect path name for database set in the DSN | "Check DSN definition" |
| No available shared memory segment or maximum size of shared memory segment too small | "Manage semaphores and shared memory segments" |
| Not enough swap space | "Check available swap space (virtual memory)" |
| Inadequate number of file descriptors | "Increase the number of available file descriptors" |
| Other possible causes | "Using the logs generated by the TimesTen daemon" |
A database is only guaranteed to be accessible by the same minor release of TimesTen that was used to create the database. When you upgrade the TimesTen software and you would like to use the new release to access a database that was previously created, create a database with the new release. Then use the ttMigrate utility to copy the tables, indexes, and table data from the old database to the new one.
See "TimesTen Upgrades" in the Oracle TimesTen In-Memory Database Installation Guide for details.
The user must have the CREATE SESSION privilege to connect to the database. If you do not have access, the administrator must use the GRANT statement to grant you the CREATE SESSION privilege. See "Granting privileges to connect to the database" in the Oracle TimesTen In-Memory Database Operations Guide.
A "permission denied" error is generated if you attempt to connect to a database and you do not have the proper permissions to access the checkpoint or transaction log files or the directory where those files reside. Check the file system permissions on the files located in the directory specified in the DataStore attribute in your DSN.
If the TimesTen daemon or Data Manager service is not running, an attempt to connect to a database generates TimesTen error 799 "Unable to connect to daemon; check daemon status."
Use the ttStatus utility as described in "Check the TimesTen user error log" to check the status of the TimesTen daemon.
In your DSN description, perform the following:
Certain connection options or DSN attribute settings combinations are not compatible. In cases where incompatible settings are used, an error is returned to the application when it attempts to connect to a database.
Confirm that you have specified the correct path names in the DataStore and LogDir attributes in your DSN. Also confirm that the path names are absolute path names, rather than relative. Otherwise, the path name will be relative to the directory where the application was started.
On Windows, be careful to distinguish between User and System DSNs in the ODBC Data Source Administrator. Do not create user DSNs because they are visible only to the user who defines them. System DSNs are visible to all users. In particular, if you run a TimesTen application as a Windows service, it runs as the user SYSTEM by default and does not see any User DSNs. Make sure that you are not using a mapped drive in the database path name.
An error is generated if you attempt to connect to or create a shared database whose size is larger than the maximum size of shared memory segments configured on your system. Also, an error is generated if the system cannot allocate any more shared memory segments.
On UNIX systems, use commands similar to the following:
ipcs -ma to check if you have other shared memory segments using up memory, such as Oracle instances or other instances of TimesTen.
ipcrm to remove a message queue, semaphore set or shared memory segment identifier. Use ipcrm to clean up semaphores or shared memory segments after a faulty TimesTen shutdown, instance crash, daemon crash or other application issues that use shared memory segments and semaphores. Use -m to remove a shared memory segment. Use -s to remove a semaphore.
ps -eafl to see how much memory is being used by running processes.
ulimit -a to see if there are any limits on the maximum amount of memory one process can address, maximum file size, and the maximum number of open files.
If a shared memory segment is available but is too small to hold your database, use the ttSize utility to estimate the amount of memory required for your tables and then check the values of the PermSize and TempSize attributes to verify the amount of memory established for your database. "Monitoring PermSize and TempSize attributes" in the Oracle TimesTen In-Memory Database Operations Guide describes guidelines for setting the size of your permanent and temporary data partitions. If the amount of memory established for your database is too large, reset PermSize and TempSize to smaller values. See "Check the amount of memory allocated to the database" for more information. Another option is to increase the maximum size of the shared memory segment, as described below.
If a database becomes invalidated because of a system or application failure, a subsequent connection recovers the database. If recovery fails because you have run out of database space, then reconnect to the database with a larger PermSize and TempSize value than the ones that are currently in effect. If recovery fails because you do not have enough shared memory, then you should increase the maximum size of the shared memory segments for the system.
For more information on how to configure shared memory for TimesTen, see "Installation prerequisites" in the Oracle TimesTen In-Memory Database Installation Guide.
There must be enough swap space to back up shared memory.
On UNIX systems, use the swap command to check and add virtual memory to your system.
On Windows systems, check and reset the size of your virtual memory from the Advanced tab in your Computer Management Properties dialog window.
Each process connected to a TimesTen database keeps at least one operating system file descriptor open. Additional file descriptors may be opened for each connection if checkpoints are issued, and transactions are committed or rolled back. If you receive an error that all file descriptors are in use when attempting to connect to a database, then increase the allowable number of file descriptors. See your operating system documentation for limits on file descriptors and information about changing the number of file descriptors.
This section includes the following topics:
Thread stack overflow when using multiple client connections
Also consider the topics described in "Application unable to connect to database in direct mode".
You have not correctly identified the system where the TimesTen Server is running.
On a Windows client machine, select the TimesTen Server in the TimesTen Data Source Setup dialog that is displayed as part of the ODBC Data Source Administrator. To verify the TimesTen Server:
On the Windows Desktop, choose Start > Settings > Control Panel.
Double click the ODBC icon. This opens the ODBC Data Source Administrator.
Click the System DSN tab. This displays the System Data Sources list.
Select the TimesTen Client data source. This opens the TimesTen Client DSN Setup dialog.
Click Servers. This opens the TimesTen Logical Server List.
Select the TimesTen Server from the list. This opens the TimesTen Logical Server Name Setup dialog.
Verify that the values for the Network Address and Port Number are correct. If necessary, change the values.
|
Note: If you typed the hostname or network address directly into the Server Name field of the TimesTen Client DSN Setup, the Client tries to connect to the TimesTen Server using the default port. |
If the Network Address and Port Number values are correct, the TimesTen Server may not be running. See "Starting and stopping the Oracle TimesTen Data Manager service on Windows" in the Oracle TimesTen In-Memory Database Operations Guide for information about starting the server manually. See "Testing connections" in the Oracle TimesTen In-Memory Database Operations Guide for more information about identifying this problem.
On UNIX, specify the TimesTen Server with the TTC_Server connection attribute in the odbc.ini file on the client machine. If the value specified for TTC_Server is an actual hostname or IP address, the client tries to connect to the TimesTen Server using the default port. In TimesTen, the default port is associated with the TimesTen release number. If the value specified for TTC_Server is a logical ServerName, this logical ServerName must be defined in the ttconnect.ini file. The ttconnect.ini entry for this ServerName needs to correctly define the hostname/IP address and port number on which the TimesTen Server is listening.
If the Network Address and Port Number values are correct, the TimesTen Server may not be running or did not start. See "Starting and stopping the daemon on UNIX" in the Oracle TimesTen In-Memory Database Operations Guide for information about starting the server manually. See "Testing connections" in the Oracle TimesTen In-Memory Database Operations Guide for more information about identifying this problem.
Check the server's log file. Server log messages are stored in the files specified by the -userlog and -supportlog options in the ttendaemon.options file. See "Creating and configuring Client DSNs on UNIX" and "Managing TimesTen daemon options" in the Oracle TimesTen In-Memory Database Operations Guide.
The maximum number of concurrent IPC connections to the Server of a particular TimesTen instance is 24,999. However, TimesTen has a limit of 2043 connections (direct or client/server) to a single DSN.
Client/server users can change the file descriptor limit to support a large number of connections. For an example, see "Installation prerequisites" in the Oracle TimesTen In-Memory Database Installation Guide.
On UNIX, verify that the Server DSN is defined in the sys.odbc.ini file on the machine running the TimesTen Server.
On Windows, verify that the Server DSN is defined as a System DSN in the ODBC Data Source Administrator on the machine running the TimesTen Server. See "Creating and configuring a logical server name on Windows" in the Oracle TimesTen In-Memory Database Operations Guide.
This error only occurs on UNIX platforms. Open the sys.odbc.ini file on the machine running the TimesTen Server and locate the Server DSN you are trying to connect. Verify that the dynamic library specified in the DRIVER attribute for the Server DSN exists and is executable.
The default TimeOut interval is 60 seconds.
To increase this interval on UNIX, change the value of the TTC_Timeout attribute in the odbc.ini file.
To set the timeout interval on Windows, see the instructions in "Setting the timeout interval and authentication" in the Oracle TimesTen In-Memory Database Operations Guide.
Check to see if the error was due to the Client timing out. Check the TimesTen Server's log to see why the Server may have severed connection with the Client. Use ping to determine if your network is up or try using telnet to connect to the TimesTen Server port number.
While using shared memory segment (SHM) as IPC, the application may see the following error message from the TimesTen Client ODBC Driver if the application reaches the system-defined per-process file-descriptor-limit.
SQLState = S1000, Native Error = 0, Message = [TimesTen][TimesTen 11.2.2 CLIENT]Failed to attach to shared memory segment for IPC. System error: 24
This may happen during a connect operation to the Client DSN when the shmat system call fails because the application has more open file descriptors than the system-defined per-process file descriptor limit. To correct this problem, you must increase your system-defined per-process file descriptor limit. For more information about file descriptor limits, see "System Limits" in the Oracle TimesTen In-Memory Database Reference.
On Windows XP, by default, there can be approximately 47 child server processes. You can increase the number of connections by setting the MaxConnsPerServer connection attribute in the ttendaemon.options file or in the DSN. This increases the number of connections to 47 times the MaxConnsPerServer value.
On Solaris, you may receive messages in the user error log about thread stack overflow. On other platforms, you may receive messages about a segmentation fault that mention a possible thread stack overflow.
If these messages occur, increase the server stack size by one of the following methods:
Specify the -ServerStackSize option in the ttendaemon.options file. The ttendaemon.options file applies to all DSNs in the TimesTen instance.
Specify the ServerStackSize connection attribute for a specific DSN. This takes precedence over the value in the ttendaemon.options file.
Increasing the server stack size decreases the number of concurrent connections that can be made before running out of swap space.
See "Working with the TimesTen Client and Server" in the Oracle TimesTen In-Memory Database Operations Guide.
You may receive "out of space" messages if you change a DSN to specify a new database while there are existing connections to the original database in a system with multiple client connections. This can happen on 32-bit platforms if either database is close to 2 GB.
Close all connections to the original database. This causes a new server process to be created for connections to the database that is now specified in the DSN. Use the ttStatus utility to list the connections for the old database. Alternatively, you can restart the server by using the ttDaemonAdmin utility with the -restartServer option, which resets all client connections on all DSNs in the instance.
This section describes what to check if you encounter slow connects and disconnects to a database.
| Possible cause | See... |
|---|---|
| Database is being recovered. | "Check if database is being recovered" |
| ODBC tracing is enabled. | "Check ODBC tracing" |
| Other possible causes | "API tracing" |
A slow connect may indicate that a TimesTen database is being recovered. This happens only for a first connect.
On Windows platforms, if ODBC tracing is enabled, it can slow connect and disconnect speeds. Double-click ODBC in the Control Panel to open the ODBC Data Source Administrator. Select the Tracing tab and confirm tracing is disabled. See "Using ODBC tracing".
If an application becomes disconnected from a TimesTen database, one of the following events occurs:
If there was no outstanding transaction, the connection is cleanly removed by the TimesTen daemon. Other existing connections continue processing as if no problem had occurred.
If there was an outstanding transaction but the application was not in the middle of executing code in the TimesTen library, the transaction is rolled back and the connection is cleanly removed by the TimesTen daemon. Other existing connections continue processing as if no problem had occurred.
This section describes what to check if your application unexpectedly disconnects from the database.
| Possible cause | See... |
|---|---|
| Internal application error. | "Check for ODBC or JDBC errors" |
| Failure of a concurrent application thread. | "Check for ODBC or JDBC errors"
|
| If using a client/server connection, the client may have disconnected from the application. | "Troubleshooting Client/Server problems" |
| An error in the TimesTen library | Contact technical support. |
Check for the following types of errors:
ODBC errors returned by the SQLError function
JDBC errors returned by the SQLException class
The application may have encountered a problem that caused it to exit prematurely, which in turn may have caused other connections to be forced to disconnect. Call SQLError after each ODBC call to identify error or warning conditions when they first happen. Examples of SQLError usage can be found in the demo programs and in "Retrieving errors and warnings" in the Oracle TimesTen In-Memory Database Error Messages and SNMP Traps.
In more extreme cases, it may be helpful to use ttTraceMon to generate a level 4 ERR trace for the application and review all of the errors messages that are pushed in the TimesTen direct driver. See "ERR tracing" for details.
If a TimesTen application disconnects without returning an ODBC error or any other warning, look through the user error log. See "Using the logs generated by the TimesTen daemon".
For details on how to maximize the performance of your application and TimesTen database, see:
"TimesTen Database Performance Tuning" in the Oracle TimesTen In-Memory Database Operations Guide
"Application Tuning" in the Oracle TimesTen In-Memory Database C Developer's Guide
"Application Tuning" in the Oracle TimesTen In-Memory Database Java Developer's Guide
This section describes some of the issues that impair performance.
| Possible cause | See... |
|---|---|
| Using client/server mode | "Consider connection mode" |
| Outdated database statistics | "Update statistics for your tables" |
| Committing transactions too frequently | "Turn off autocommit mode" in the Oracle TimesTen In-Memory Database Operations Guide |
DurableCommits attribute enabled | "Use durable commits appropriately" in the Oracle TimesTen In-Memory Database Operations Guide |
| Not preparing SQL statements used more than once | "Prepare statements in advance" in the Oracle TimesTen In-Memory Database Operations Guide |
| Wrong kind of index, too many indexes, wrong size for hash index | "Select hash, range, or bitmap indexes appropriately" in the Oracle TimesTen In-Memory Database Operations Guide
"Size hash indexes appropriately" in the Oracle TimesTen In-Memory Database Operations Guide |
| Inefficient use of locks | "Verify lock and isolation levels" |
| Improperly configured materialized view | "Performance implications of materialized views" and "Materialized view tuning" in the Oracle TimesTen In-Memory Database Operations Guide |
| If replication is used, configuration of replication scheme or network environment may be impacting application. | "Poor replication or XLA performance" |
| If IMDB Cache is used, IMDB Cache configuration or environment may be impacting application. | "Poor autorefresh performance" |
| Too many table partitions | "Check partition counts for the tables" |
| Tracing is unnecessarily enabled for one or more TimesTen components. | "Check trace settings" |
Client/server connections are slower than direct connections to TimesTen databases. Driver manager connections can also moderately impact performance. The performance overhead imposed by client/server connections can be significant because of the network latencies involved in all communication with the database.
If your application must run on a different machine from the one hosting the database, see "Client/Server tuning" in the Oracle TimesTen In-Memory Database Operations Guide.
The TimesTen query optimizer in general is very good at choosing the most efficient query plan. However, it needs additional information about the tables involved in complex queries in order to choose the best plan. By knowing the number of rows and data distributions of column values for a table, the optimizer has a much better chance of choosing an efficient query plan to access that table.
Before preparing queries that will access a TimesTen table, use the ttOptUpdateStats procedure to update the statistics for that table. When updating the statistics for a table, you get the best results if you update statistics on your tables after loading them with data, but before preparing your queries. For example, if you update statistics on a table before populating it with data, then your queries are optimized with the assumption that the tables contain no rows (or very few). If you later populate your tables with millions of rows and then execute the queries, the plans that worked well for the situation where your tables contained few rows may now be very slow.
For more information about updating statistics, see "The TimesTen Query Optimizer" in the Oracle TimesTen In-Memory Database Operations Guide.
The manner in which multiple applications concurrently access the database can have a major impact on performance.
An application can acquire locks on the entire database, individual tables, and individual rows. Additionally, applications can set an isolation level that determines whether they hold read and update locks until their transactions commit or roll back.
Check the SYS.MONITOR table or use the ttXactAdmin utility to detect whether an application is spending time waiting for locks. See "Check for deadlocks and timeouts" and "Using the ttXactAdmin utility".
If lock contention is high, you may be able to improve the overall performance of your system by implementing the following:
Set the LockLevel configuration attribute or use the ttLockLevel procedure to place locks on rows, rather than on the entire database. Row locking is the default.
Use the ttOptSetFlag procedure to prevent the query optimizer from placing locks on tables. Table locks are sometimes the default, particularly for updates that affect many rows.
Use read-committed isolation level (Isolation=1, the default) for those applications do not require serializable access to the transaction data.
If you see a lot of lock contention, but the above settings are all set to minimize contention, then the contention may be related to the application itself. For example, concurrent threads may be repeatedly accessing the same row. The ttXactAdmin utility can sometimes help you detect this sort of contention. Tracing can also be useful in this situation.
For more information about locks and isolation levels, see "Concurrency control through isolation and locking" in the Oracle TimesTen In-Memory Database Operations Guide.
Use ttTraceMon -e show as described in "Using the ttTraceMon utility" to confirm tracing is off on all TimesTen components. ERR should be set to 1; all other components should be set to 0. Trace levels are preserved when a database is reloaded.
On Windows platforms, confirm that ODBC tracing is disabled. Double-click ODBC in the Control Panel to open the ODBC Data Source Administrator. Select the Tracing tab and confirm tracing is disabled. See "Using ODBC tracing".
When a table is created, it has one partition. When you use ALTER TABLE ... ADD COLUMN to add new columns, a new partition is added to the table. Adding multiple columns with a single ALTER TABLE ... ADD COLUMN statement only adds one partition.
There is a limit of 999 partitions per table. Exceeding this number generates error 8204. An extra read for each new partition slightly degrades performance for each of the new partitions. A high partition count should be avoided. On replicated tables that have multiple partitions, additional space is used for each update on the subscriber side, proportional to the number of partitions. This can result in the subscribers using slightly more perm space than the master.
The partition value for each table is tracked in the SYS16 column of the system table, SYS.TABLES. Obtain the partition counts for tables by using the following query:
SELECT tblname, sys16 FROM SYS.TABLES;
If you discover that a table has too many partitions, do one of the following:
Re-create the table
Save and restore the table. Use ttMigrate -c to create a migration file. Then restore the table without additional partitions by using ttMigrate -r -relaxedUpgrade.
ALTER TABLE ... DROP COLUMN does not remove partitions from a table. On replicated systems, all master and subscriber databases must be migrated using the -relaxedUpgrade option. Replication does not occur for tables that have different partition structures.
This section describes what to check if your application is unresponsive and appears to be hung.
| Possible cause | See... |
|---|---|
| All causes | "Check logs and gather trace information" |
| Internal application error | "Check for ODBC errors" |
| Inconsistent connection attributes set in DSN | "Consider connection mode" |
| Excessive lock contention | "Check for deadlocks and timeouts" |
If your application hangs, check the transaction log by using the ttXactAdmin utility. See "Using the ttXactAdmin utility".
Also check the user error log for errors, as described in "Using the logs generated by the TimesTen daemon" .
You can also generate a trace log to detect the activities on various TimesTen components as described in "Using the ttTraceMon utility" .
Check the ODBC errors returned by the SQLError function in all applications to determine whether one of them has encountered a problem that caused it to hang. Call SQLError after each ODBC call to identify error or warning conditions when they first happen. Examples of SQLError usage can be found in the demo programs and in "Retrieving errors and warnings" in the Oracle TimesTen In-Memory Database Error Messages and SNMP Traps.
If the problem is repeatable, use ttTraceMon to generate a SQL trace to determine where the application is hanging. See "SQL tracing" for details. In more extreme cases, it may be helpful to generate a level 4 ERR trace for the application and review all of the errors messages that are pushed in the TimesTen direct driver. See "ERR tracing" for details.
If there is no connect problem, a deadlock or timeout may be the problem. The SYS.MONITOR table records information about deadlocks and timeouts. See "Monitoring the TimesTen system tables" for information on how view the contents of this table. You can also use the ttXactAdmin utility to detect the types of locks currently held by uncommitted transactions and the resources on which they are being held.
If a deadlock occurs, the TimesTen subdaemon negotiates the problem by having an application involved in the deadlock generate TimesTen error 6002, "Lock request denied because of deadlock." The error message contains the SQL that the lock holder is running, which can help you diagnose the cause of the deadlock. If your application encounters this error, it should roll back the transaction and then reissue the statements for that transaction. Deadlocks can be caused if your application issues statements in a particular order that results in a circular wait, and can sometimes be prevented by changing the order in which the statements are issued.
An application encounters TimesTen error 6003, "Lock request denied because of timeout," if it is unable to acquire a lock within the time period defined by the lock timeout interval set by the LockWait attribute in the DSN or by the ttLockWait procedure in your application. Upon encountering a timeout error, your application can reissue the statement. Keeping transactions short reduces the possibility of lock timeout errors.
System tables are a common source of lock contention. Reduce contention on the system tables by executing prepared statements, rather than executing the same statements directly each time.
In multi-threaded applications, a thread that issues requests on different connection handles to the same database may encounter lock conflict with itself. TimesTen resolves these conflicts with lock timeouts.
This section describes what to check if your application is unable to locate previously created tables, indexes, sequences or views in the database.
| Possible cause | See... |
|---|---|
| No owner or incorrect owner specified | "Specify object owner" |
User does not have SELECT privileges to tables. | "Check privilege to access tables" |
| Database is temporary. | "Check temporary DSN attribute" |
| Overwrite attribute is enabled. | "Check Overwrite DSN attribute" |
| Path name specified in DSN is relative. | "Check path name to database" |
Tables, indexes and sequences can be created either with a single name, such as PARTS, or with a qualified name incorporating an owner and table name, such as STAN.PARTS. When accessing a table or index, if no owner is specified, TimesTen first assumes that the owner is the login ID of the user (the value of the UID attribute). If TimesTen cannot find the table or index under the user's login ID, it then assumes that the owner is user SYS.
If applications need to connect to a database as different users and share objects, explicitly specify the owners of the objects when they are created and referenced.
All privileges for the user can be viewed in the SYS.n5USER_SYS_PRIVS table, which contains all of the system-level privileges for a given user, and the SYS.USER_TAB_PRIVS table, which contains all of the object-level privileges for a given user. Check these tables to verify if you have SELECT privilege for the tables. If you do not have SELECT privilege for the tables, the privilege may be granted with the GRANT statement. The method for granting privileges is described in the "Managing Access Control" chapter in the Oracle TimesTen In-Memory Database Operations Guide.
Temporary databases (DSN attribute: Temporary=1) persist until all connections to the database have been removed. When attempting to access a table in a temporary database and the table does not exist, it is possible that the database in which the table resided in has been dropped.
If the Overwrite and AutoCreate DSN attributes are enabled and the database already exists, TimesTen drops that database and creates a new one. Any tables that were created in the old database are dropped.
To ensure that you are always accessing the same database when connecting to a particular DSN, use an absolute database path name instead of a relative one. For example, if the demo database is in the datastore directory, specify:
DataStore=/datastore/demo
rather than:
DataStore=demo
In the latter case, the database path name is relative to the directory where the application was started. If you are unable to find a table and you are using a relative database path name, it is possible that the database in which the table resides in does exist but the database (checkpoint and log) files are in a different directory than the one that you are accessing.
See "Specifying Data Source Names to identify TimesTen databases" in the Oracle TimesTen In-Memory Database Operations Guide.
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.
This section describes what to check if TimesTen runs out of resources such as memory space, disk space, file descriptors, and semaphores.
| Symptom | See... |
|---|---|
| Memory consumption seems high. | "Operating system tools and shared memory" |
| Running out of memory space |
|
| Running out of disk space | "Check transaction log file use of disk space"
|
| Running out of transaction log space | "Check transaction log file use of disk space" |
| Running out of file descriptors | "Increase the number of available file descriptors" |
| Running out of semaphores | "Check the semaphore limit" |
| Running out of CPU | Obtain a stack trace and contact technical support. |
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.
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 database.
When the TimesTen database fills up, it is important to determine whether it is the permanent or the temporary segment that is filling up. Use the ttIsql dssize command to list allocated, in-use, and high water mark sizes for the permanent and temporary data partitions. The dssize command selects the following values from SYS.MONITOR:
PERM_ALLOCATED_SIZE
PERM_IN_USE_SIZE
PERM_IN_USE_HIGH_WATER
TEMP_ALLOCATED_SIZE
TEMP_IN_USE_SIZE
TEMP_IN_USE_HIGH_WATER
The permanent segment consists of table and index data, while the temporary segment consists of internal structures, such as locks, sorting areas, and compiled commands.
Keeping transactions short and making sure there is enough temporary space in the database prevents locks from occupying all of the remaining temporary space. You can also use table locks if transactions are acquiring tens of thousands of row locks.
For tips on how to estimate the size of your database, see "Size your database correctly" in the Oracle TimesTen In-Memory Database Operations Guide.
Consider whether you can drop any indexes. You may want to look at query plans to see which indexes are actually used. See "Viewing and changing query optimizer plans" in the Oracle TimesTen In-Memory Database Operations Guide. You can also use the ttRedundantIndexCheck procedure to discover redundant indexes. The procedure returns suggestions about which indexes to drop.
Use the ttSize utility to estimate the amount of memory used by each table in the database. If the amount of data you need to store is too big, you may need to reset the PermSize attribute for the database to increase the size of the permanent segment. Alternatively, you may need to partition your data into several different databases if, for example, you cannot shrink the temporary segment or create a bigger database because of limits on the memory segment size.
Sometimes when the permanent segment fills up, copying the data out of the database, deleting all the data, and copying it back in frees up space. This can be done more efficiently by using the ttMigrate utility with the -relaxedUpgrade option to migrate the data out, destroy and re-create the database, and migrate the data back in. This operation is described in "Reducing database size" in the Oracle TimesTen In-Memory Database Installation Guide.
Finally, you may have to configure the operating system to allow a larger amount of shared memory to be allocated to a process. You may also have to allocate more swap space for virtual memory. See "Check available swap space (virtual memory)".
Some commands may be allocating too much space because of out-of-date statistics. See "Update query optimizer statistics".
If updating the statistics does not reduce temporary segment memory usage, disconnect all connections and then reconnect them. Verify that all connections have been disconnected by using the ttStatus utility. That frees up all temporary space, but you must reprepare commands.
Diagnose memory usage by queries. See "Check memory used by queries".
If the problem is chronic, monitor the database to try to identify the source of the problem. Use the ttWarnOnLowMemory procedure to enable warnings in the user log that indicate that the database is filling up.
If the database seems to have enough free space but runs out of database space when executing a query, make sure you have updated the optimizer statistics with the ttOptUpdateStats or ttOptEstimateStats procedure. To execute some queries, TimesTen needs to allocate temporary space. The amount of temporary space required is estimated from statistics about the tables used by the query. Without correct statistics, the temporary space required may be underestimated.
You can check the memory that a query uses by observing the high water mark for temporary memory usage. The high water mark represents the largest amount of in-use temporary space used since the high water mark was initialized or reset.
Complete the following tasks:
Use the ttIsql dssize command to check TEMP_IN_USE_SIZE and TEMP_IN_USE_HIGH_WATER. Alternatively, you can query the SYS.MONITOR table for these values.
Call the ttMonitorHighWaterReset procedure to reset the TEMP_IN_USE_HIGH_WATER to the current value for TEMP_IN_USE_SIZE.
Execute a query.
Use dssize to check TEMP_IN_USE_HIGH_WATER for peak memory usage for the query.
If you receive an error indicating that you have run out of swap space, you may need to increase the amount of available swap space (also referred to as "virtual memory").
On UNIX systems, use the swap command to check and reset the amount of virtual memory currently established for your system.
On Windows systems, check and reset the size of your virtual memory by choosing Control Panel > System > Advanced.
Fatal errors, such as errors 846 and 994, invalidate a TimesTen database. However, the database remains in memory, which is only freed after all users have disconnected from the database. If the database is restarted while users are connected to the invalidated database, both old and new instances exist in memory at the same time. In this case, users could receive out-of-memory conditions. To prevent an "Out of memory" error, disconnect all active connections at the time of the fatal error before reconnecting.
TimesTen saves a copy of the database in one of two checkpoint files, which are stored in the directory specified by the DataStore attribute. Each checkpoint file can grow on disk to be equivalent to the size of the database in shared memory. For each permanent database, you must have enough disk space for the two checkpoint files and for transaction log files.
Transaction log files accumulate in the directory specified by the LogDir attribute and are only deleted when checkpoints are performed. If the LogDir attribute is not specified in the DSN, transaction log files accumulate in the directory specified by the DataStore attribute. The maximum size of your transaction log files is set by the LogFileSize attribute.
When a disk fills up with TimesTen data, it is most often due to a build-up of transaction log files. Transaction log files are used for numerous purposes in TimesTen, including checkpointing, backups, and replication. It is important to determine which operation is putting a "hold" on the transaction log files, so that appropriate action can be taken to enable the transaction log files to be purged. This can be done by using the ttLogHolds built-in procedure. There are six types of log holds. They are discussed in detail below.
Checkpoint - If a TimesTen application crashes and the database needs to be recovered, the checkpoint files and transaction log files are used to recover the data. The "most recent" transaction log files are used -- those written since the checkpoint was done. Transaction log files accumulate during the interval between checkpoints. Your application should periodically call the ttCkpt or ttCkptBlocking procedure to checkpoint the data and free up the space on the disk. If checkpoints are done very infrequently, a large number of transaction log files may accumulate, particularly if many changes are made to the database during that interval. See "Checkpoint operations" in the Oracle TimesTen In-Memory Database Operations Guide.
Replication -TimesTen replication transmits changes to one database to one or more other databases. It does this by reading the log and sending any relevant changes. If replication is paused, the transaction log files build up. To prevent log build-up, avoid pausing replication for too long. Delete subscriptions entirely, and reset replication where appropriate. See "Setting the replication state of subscribers" in Oracle TimesTen In-Memory Database Replication Guide for more information on pausing and restarting or resetting replication.
Backup - TimesTen supports an incremental backup facility that uses transaction log files to augment a backup with changes made since the last backup. Transaction log files accumulate during the interval between incremental backups. To avoid a large log build-up, do incremental backups at relatively frequent intervals. If desired, disable incremental backups and do full backups instead. See "Migration, Backup, and Restoration" in the Oracle TimesTen In-Memory Database Installation Guide.
XLA - TimesTen's persistent XLA facility reports changes to the database by using transaction log files. Transaction log files are kept until the corresponding transactions have been acknowledged using the ttXlaAcknowledge C function. Call ttXlaAcknowledge frequently enough to prevent transaction log files building up. See "Retrieving update records from the transaction log" in the Oracle TimesTen In-Memory Database C Developer's Guide.
XA - TimesTen's XA support uses transaction log files to resolve distributed transactions. If these transactions are not resolved in a timely manner, transaction log files build up. See "Distributed Transaction Processing: XA" in the Oracle TimesTen In-Memory Database C Developer's Guide.
Long-running transactions - TimesTen uses the transaction log to roll back transactions. A log hold is placed for the duration of a transaction. Transactions that are active for a long time result in log file building up if the transaction has written at least one log record. (That is, it is not a read-only transaction.) Commit write transactions with reasonable frequency to avoid significant log file build-up. See "Size transactions appropriately" in the Oracle TimesTen In-Memory Database Operations Guide for more information on transaction length.
The following attributes are related to disk use:
The LogPurge attribute indicates whether transaction log files that no longer have a hold on them are purged (removed from the disk) or simply archived (renamed). If the LogPurge attribute is set to the default value of 0, TimesTen renames transaction log files that it no longer needs by appending the string .arch to the name. Once renamed, you must delete the transaction log files manually when they are no longer needed. If transaction log files are not purged, they continue to accumulate space, even when no longer needed by TimesTen.
The Preallocate attribute indicates whether disk space should be reserved for checkpoint files at connect time. This is useful for big databases, to ensure that the disk always has room for the checkpoint files as data is added to the database.
When tracing to a file has been enabled, the file may grow so large that a process attempting an operation may exceed the file limits. Tracing always appends to an existing file.
On certain platforms, the file size is limited to 2G. If you reach this limit, the process is terminated unless you catch the SIGXFSZ signal. The error shown is the "FILESIZE LIMIT EXCEEDED" error. Ensure that you want tracing enabled when using environments with strict file size limits.
When creating multiple client/server connections to a TimesTen database configured to allow shared memory segment as IPC, you may encounter errors that indicate TimesTen was unable to create a semaphore.
Semaphore limits are platform-dependent. See your operating system documentation.
Using read-committed isolation level can lead to duplicates in a result set. A SELECT statement selects more or fewer rows than the total number of rows in the table if some rows are added or removed and committed in the range in which the SELECT scan is occurring. This may happen when an UPDATE, INSERT or DELETE statement adds or deletes a value from an index and the SELECT scan is using this index. This can also happen when an INSERT or DELETE adds or deletes rows from the table and the SELECT operation is using an all-table scan.
Index values are ordered. An UPDATE of an index value may delete the old value and insert the new value into a different place. In other words it moves a row from one position in the index to another position. If an index scan sees the same row in both positions, it returns the row twice. This does not happen with a serial scan because table pages are unordered and rows do not need to be moved around for an UPDATE. Hence once a scan passes a row, it will not see that same row again.
The only general way to avoid this problem is for the SELECT statement to use Serializable isolation. This prevents a concurrent INSERT, DELETE or UPDATE operation. There is no reliable way to avoid this problem with INSERT or DELETE by forcing the use of an index because these operations affect all indexes. With UPDATE, this problem can be avoided by forcing the SELECT statement to use an index that is not being updated.
For more information about Serializable isolation, see "Concurrency control through isolation and locking" in the Oracle TimesTen In-Memory Database Operations Guide.
The PLSQL_MEMORY_ADDRESS first connection attribute determines the virtual address at which the PL/SQL shared memory segment is loaded into each process that uses the TimesTen direct drivers. Since each operating system platform has different mappings for its address space, the default values for the PL/SQL address space defined in the PLSQL_MEMORY_ADDRESS connection attribute are different for each platform, which avoids conflict with operating system mapped address space.
However, if your application overlaps with the PL/SQL mapped address space, you may receive error 8517 "Cannot attach PL/SQL shared memory; PLSQL_MEMORY_ADDRESS not valid or already in use." In this case, modify the setting for the PLSQL_MEMORY_ADDRESS connection attribute to eliminate the overlap. The reasons for receiving error 8517 can be one of the following:
User allocated memory already uses that address.
Some shared memory already uses that address.
A shared library already uses that address.
To recover, specify a virtual address that is free for all processes that may connect to the database. If you have a 32-bit program that allocates large amounts of memory before connecting to TimesTen, it may clash with the PL/SQL shared memory segment. In this case, either allocate memory after connecting to TimesTen or use a 64-bit application. In a 64-bit environment, the options for reassigning to another memory address are less complicated than for a 32-bit operating system, where options are limited and potential for overlap is more common.
If an application accesses two or more TimesTen databases at the same time, you must modify the default setting for the PLSQL_MEMORY_ADDRESS attribute in all but one of the TimesTen databases, since the default settings would map the PL/SQL memory address to the same address for all TimesTen databases.
Troubleshooting Guide
11g Release 2 (11.2.2)
E21636-06
October 2012
Oracle TimesTen In-Memory Database Troubleshooting Guide, 11g Release 2 (11.2.2)
E21636-06
Copyright © 2011, 2012, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Creating an asynchronous writethrough (AWT) cache group automatically creates a replication scheme that enables the database to communicate with the Oracle database. You must start the replication agent after you create an AWT cache group and before you start the cache agent. See "Creating an AWT cache group" in the Oracle In-Memory Database Cache User's Guide for more details.
This chapter contains the following troubleshooting sections:
The replication agent must be started in order for the AWT cache group to work. If the replication agent is not starting, use the information in Chapter 5, "Troubleshooting Replication " to troubleshoot the replication agent.
If you are unable to get replication working, the problem may solved by one or more of the following sections:
| Possible Cause | See... |
|---|---|
| Replication agent will not start | "Unable to start or stop replication agent" |
| SNMP traps for monitoring replication events | "Using SNMP traps for notification of replication events" |
| TimesTen daemon or replication agents not running | "Check status of TimesTen daemon and replication agents" |
| Replication agents not communicating | "Check that replication agents are communicating" |
| Replication not in Start state | "Check replication state" |
You can monitor the performance of asynchronous writethrough (AWT) cache groups to determine how much time is spent performing tasks in the AWT workflow.
The following sections describe how to enable the monitoring and the tools for viewing the results:
Use the ttCacheAwtMonitorConfig built-in procedure to enable monitoring for AWT cache groups. Ensure that the replication agent is running before calling ttCacheAwtMonitorConfig.
The following example enables monitoring and sets the sampling frequency to 16. A sampling factor of 16 is recommended for accuracy and performance.
Command> CALL ttCacheAwtMonitorConfig('ON',16);
< ON, 16 >
1 row found.
Use the ttRepAdmin utility with the -awtmoninfo and -showstatus commands to display the monitoring results. The AWT monitoring statistics include the following:
TimesTen processing time: The total number of milliseconds spent in processing AWT transaction data since monitoring was enabled.
Oracle bookmark management time: The total number of milliseconds spent in managing AWT metadata on Oracle since monitoring was enabled.
Oracle execute time: The total number of milliseconds spent in OCI preparation, binding and execution for AWT SQL operations since monitoring was enabled. This statistic includes network latency between TimesTen and Oracle.
Oracle commit time: The total number of milliseconds spent in committing AWT updates on Oracle since monitoring was enabled. This statistic includes network latency between TimesTen and Oracle.
Time since monitoring was started.
Total number of TimesTen row operations: The total number of rows updated in AWT cache groups since monitoring was enabled.
Total number of TimesTen transactions: The total number of transactions in AWT cache groups since monitoring was enabled.
Total number of flushes to Oracle: The total number of times that TimesTen data has been sent to Oracle.
The percentage of time spent on TimesTen processing, Oracle bookmark management, Oracle execution and Oracle commits.
For example:
ttRepAdmin -showstatus -awtmoninfo myDSN
[other -showstatus output]
...
AWT Monitoring statistics
-------------------------
TimesTen processing time : 8443.424000 millisecs (44.064958 )
Oracle execute (SQL execution) time : 8930.320000 millisecs (46.605994 )
Oracle execute (PL/SQL execution) time : 0.000000 millisecs (0 )
Oracle commit time : 1787.568000 millisecs (9.329048 )
Time since monitoring was started: 21954.410000 millisecs
CacheAwtMethod mode : 0
Cache-connect Operational Stats :
SQL Operations sent to Oracle : 143556
Number of update operations : 58
Number of update batches : 58
Number of insert operations : 143498
Number of insert batches : 1146
Number of delete operations : 0
Number of delete batches : 0
Total number of batches sent: 1204
Number of bytes sent : 4769094
Number of TimesTen Transactions sent to Oracle (includes retries) :
143556
Number of retries on TimesTen due to errors on Oracle : 0
Number of round trips to Oracle (includes executes, commits and
rollbacks) : 2290
Number of commits on Oracle : 1086
Number of rollbacks on Oracle : 0
Number of rxbatches: 244
Number of rxskips: 0
Peer name Host name Port State Proto
---------------- ------------------------ ------ ------- -----
_ORACLE MYHOST Auto Start 27
Last Msg Sent Last Msg Recv Latency TPS RecordsPS Logs
------------- ------------- ------- ------- --------- ----
00:00:00 - 2.35 6311 6311 1
To determine whether asynchronous writethrough operations are keeping up with the rate of updates on cache tables in AWT cache groups, query the LAST_LOG_FILE, REPHOLD_LOG_FILE and REPHOLD_LOG_OFF columns of the SYS.MONITOR system table. If the difference between the value in the LAST_LOG_FILE column and the value in the REPHOLD_LOG_FILE column is increasing over time, and the value in the REPHOLD_LOG_OFF column is increasing slowly or not changing, then the tables are being updated at a faster rate than the updates are being replicated.
Then run a ttRepAdmin -receiver -list utility command and find the row where _ORACLE is in the Peer name field. View the values in the Last Msg Sent, Last Msg Recv, Latency and TPS fields within the same row to determine if the replication activity that is falling behind is asynchronous writethrough operations.
For more information about monitoring log files, see "Monitoring accumulation of transaction log files" in Oracle TimesTen In-Memory Database Operations Guide.
The SYS.SYSTEMSTATS system table has a variety of statistics about AWT performance. See "SYS.SYSTEMSTATS" in Oracle TimesTen In-Memory Database System Tables and Views Reference.
This section addresses issues that may degrade AWT cache group performance.
| Possible cause | See... |
|---|---|
| Slow network | "Check network bandwidth" |
| Log buffer too small | "Check size of log buffer" |
| Frequent or inefficient disk writes | "Check durability settings" |
| Reading from transaction log files on disk instead of the log buffer | "Check for reads from transaction log files" |
| Problems on the Oracle Database | "Problems on the Oracle Database" |
| Replication agent is down | "Unable to start or stop replication agent" or "Replication does not work" |
UNLOAD CACHE GROUP cannot complete if row updates are not propagated to the Oracle database. | "UNLOAD CACHE GROUP requires row updates to complete propagation" |
If an AWT cache group cannot propate updates to the Oracle database, the causes can include network failure, an Oracle database failure, I/O bottlenecks and CPU bottlenecks. See Oracle Database Performance Tuning Guide for information about analyzing Oracle Database performance.
AWT propagation to the Oracle database can also fail because the replication agent is stopped. See "Unable to start or stop replication agent" and "Replication does not work".
Execution of the UNLOAD CACHE GROUP statement for an AWT cache group waits until updates on the rows have been propagated to the Oracle database. However, the UNLOAD CACHE GROUP statement may fail if data propagation to Oracle is stopped for any reason, such as network failure, the Oracle database is down, or the replication agent is stopped.
The following sections describe both permanent and transient Oracle errors that can be reported by TimesTen for an AWT cache group:
Insert, update, or delete errors that occur while applying changes to Oracle are saved in an error file located in the database directory with the following name:
<DataSourceName>.awterrs
Errors reported to this file are permanent errors. TimesTen does not retry the transaction. The errors may be reported in the AWT error file long after the commit to TimesTen occurs.
The format of the messages in the AWT error file is similar to those generated for conflict and transaction errors in replication, as shown in Example 6-1. Oracle error messages are also reported in the support log and the user log. The Oracle errors are prefixed with 'ORA-.' The TimesTen error messages are prefixed with 'TT.' For example, in Example 6-1, TimesTen errors 5210 and 5025 are shown as TT5210 and TT5025. These can be looked up in the Oracle TimesTen In-Memory Database Error Messages and SNMP Traps guide.
Example 6-1 Cache violation occurs when update is propagated to Oracle
If a constraint violation occurs when a cache group update is propagated to Oracle, the message in the AWT error file is similar to the following:
Error occurred 14:48:55 on 03-22-2011 Datastore: c:\temp\cgDSN Oracle Id: system1 Transmitting name: cgDSN Error message: TT5210: Oracle unique constraint violation error in OCIStmtExecute(): ORA-00001: unique constraint (GUSER.SYS_C00357240) violated rc = -1 -- file "bdbTblH.c", lineno 1205, procedure "ttBDbStmtForce()" TT5025: Commit failure in Oracle. Transaction must be rolled back in TimesTen. -- file "bdbConnect.c", lineno 885, procedure "ttBDbXact()" Operation that caused the error: Insert into table TESTUSER.T1 <9,1000> Failed transaction: Insert into table TESTUSER.T1 <9, 1000> End of failed transaction
Example 6-2 An object that TimesTen has placed on Oracle is dropped
If an object that TimesTen has placed on Oracle is dropped, the message in the AWT error file is similar to the following:
May 04 18:12:36 HOST1 TimesTen Replication 11.2[2136]: [Err ] DEFAULT:meta.c(639): TT16062: Failed to compile command: select p.commit_timestamp, p.commit_seqnum, p.protocol from owner1.TT_06_REPPEERS p where p.replication_name = :rname and p.replication_owner = :rowner and p.tt_store_id = :oid and p.subscriber_id = :sid May 04 18:12:36 HOST1 TimesTen Replication 11.2[2136]: [Err ] DEFAULT:meta.c(639): TT5221: TT5221: Oracle syntax error in OCIStmtExecute(): ORA-00942: table or view does not exist rc = -1 -- file "bdbStmt.c", lineno 1041, procedure "getOraOutTypesNLengths()"
In this example, the TT_06_REPPEERS table does not exist. To recover from this error, perform the following tasks:
Stop the replication agent.
Drop and re-create the cache group.
Restart the replication agent.
The support log for databases with AWT cache groups may contain Oracle errors if the replication agent encounters a problem on the Oracle database. If the replication agent encounters one of these errors, AWT rolls back the transaction and retries it. If the support log becomes full, the oldest messages are deleted and replaced by new messages.
The Oracle errors in the support log are considered transient because AWT retries the transaction.
Some transient errors indicate an underlying problem on the Oracle database must be solved before AWT operations can continue. For example:
ORA-01536: space quota exceeded for tablespace ORA-01034: ORACLE not available
After the underlying problem has been fixed, AWT retries the operation.
For more information about the Oracle errors, see Oracle Database Error Messages for the Oracle release you are using.
The following Oracle errors are transient:
ORA-00018: maximum number of sessions exceeded ORA-00019: maximum number of session licenses exceeded ORA-00020: maximum number of processes (%s) exceeded ORA-00025: failed to allocate %s ORA-00028: your session has been killed ORA-00038: Cannot create session: server group belongs to another user ORA-00051: timeout occurred while waiting for a resource ORA-00052: maximum number of enqueue resources (%s) exceeded ORA-00053: maximum number of enqueues exceeded ORA-00054: resource busy and acquire with NOWAIT specified ORA-00055: maximum number of DML locks exceeded ORA-00057: maximum number of temporary table locks exceeded ORA-00058: DB_BLOCK_SIZE must be %s to mount this database (not %s) ORA-00059: maximum number of DB_FILES exceeded ORA-00060: deadlock detected while waiting for resource ORA-00063: maximum number of LOG_FILES exceeded ORA-00064: object is too large to allocate on this O/S (%s,%s) ORA-00099: timed out while waiting for resource, potential PDML deadlock ORA-00104: deadlock detected; all public servers blocked waiting for resources ORA-00107: failed to connect to ORACLE listener process ORA-00115: connection refused; dispatcher connection table is full ORA-00125: connection refused; invalid presentation ORA-00126: connection refused; invalid duplicity ORA-00284: recovery session still in progress ORA-00370: potential deadlock during kcbchange operation ORA-00371: not enough shared pool memory ORA-00376: file %s cannot be read at this time ORA-00379: no free buffers available in buffer pool %s for block size %sK ORA-00384: Insufficient memory to grow cache ORA-00568: Maximum number of interrupt handlers exceeded ORA-00579: osndnt: server received malformed connection request ORA-00600: internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s] ORA-00603: ORACLE server session terminated by fatal error ORA-01000: maximum open cursors exceeded ORA-01012: not logged on ORA-01014: ORACLE shutdown in progress ORA-01019: unable to allocate memory in the user side ORA-01031: insufficient privileges ORA-01033: ORACLE initialization or shutdown in progress ORA-01034: ORACLE not available ORA-01035: ORACLE only available to users with RESTRICTED SESSION privilege ORA-01037: maximum cursor memory exceeded ORA-01046: cannot acquire space to extend context area ORA-01073: fatal connection error: unrecognized call type ORA-01089: immediate shutdown in progress - no operations are permitted ORA-01090: shutdown in progress - connection is not permitted ORA-01092: ORACLE instance terminated. Disconnection forced ORA-01094: ALTER DATABASE CLOSE in progress. Connections not permitted ORA-01109: database not open ORA-01147: SYSTEM tablespace file %s is offline ORA-01154: database busy. Open, close, mount, and dismount not allowed now ORA-01155: the database is being opened, closed, mounted or dismounted ORA-01219: database not open: queries allowed on fixed tables/views only ORA-01237: cannot extend datafile %s ORA-01456: may not perform insert/delete/update operation inside a READ ONLY transaction ORA-01536: space quota exceeded for tablespace '%s' ORA-01539: tablespace '%s' is not online ORA-01542: tablespace '%s' is offline, cannot allocate space in it ORA-01562: failed to extend rollback segment number %s ORA-01573: shutting down instance, no further change allowed ORA-01628: max # extents (%s) reached for rollback segment %s ORA-01629: max # extents (%s) reached saving undo for tablespace %s ORA-01630: max # extents (%s) reached in temp segment in tablespace %s ORA-01631: max # extents (%s) reached in table %s.%s ORA-01632: max # extents (%s) reached in index %s.%s ORA-01650: unable to extend rollback segment %s by %s in tablespace %s ORA-01651: unable to extend save undo segment by %s for tablespace %s ORA-01652: unable to extend temp segment by %s in tablespace %s ORA-01653: unable to extend table %s.%s by %s in tablespace %s ORA-01654: unable to extend index %s.%s by %s in tablespace %s ORA-01655: unable to extend cluster %s.%s by %s in tablespace %s ORA-01656: max # extents (%s) reached in cluster %s.%s ORA-01658: unable to create INITIAL extent for segment in tablespace %s ORA-01659: unable to allocate MINEXTENTS beyond %s in tablespace %s ORA-01680: unable to extend LOB segment by %s in tablespace %s ORA-01681: max # extents (%s) reached in LOB segment in tablespace %s ORA-01683: unable to extend index %s.%s partition %s by %s in tablespace %s ORA-01684: max # extents (%s) reached in table %s.%s partition %s ORA-01685: max # extents (%s) reached in index %s.%s partition %s ORA-01686: max # files (%s) reached for the tablespace %s ORA-01688: unable to extend table %s.%s partition %s by %s in tablespace %s ORA-01691: unable to extend lob segment %s.%s by %s in tablespace %s ORA-01692: unable to extend lob segment %s.%s partition %s by %s in tablespace %s ORA-01693: max # extents (%s) reached in lob segment %s.%s ORA-01694: max # extents (%s) reached in lob segment %s.%s partition %s ORA-03113: end-of-file on communication channel ORA-03114: not connected to ORACLE ORA-03134: Connections to this server version are no longer supported. ORA-03135: connection lost contact ORA-03136: inbound connection timed out ORA-03232: unable to allocate an extent of %s blocks from tablespace %s ORA-03233: unable to extend table %s.%s subpartition %s by %s in tablespace %s ORA-03234: unable to extend index %s.%s subpartition %s by %s in tablespace %s ORA-03235: max # extents (%s) reached in table %s.%s subpartition %s ORA-03236: max # extents (%s) reached in index %s.%s subpartition %s ORA-03237: Initial Extent of specified size cannot be allocated ORA-03238: unable to extend LOB segment %s.%s subpartition %s by %s in tablespace %s ORA-03239: maxextents (%s) reached in LOB segment %s.%s subpartition %s ORA-04020: deadlock detected while trying to lock object %s%s%s%s%s ORA-06019: NETASY: invalid login (connect) string ORA-06021: NETASY: connect failed ORA-06030: NETDNT: connect failed, unrecognized node name ORA-06031: NETDNT: connect failed, unrecognized object name ORA-06032: NETDNT: connect failed, access control data rejected ORA-06033: NETDNT: connect failed, partner rejected connection ORA-06034: NETDNT: connect failed, partner exited unexpectedly ORA-06035: NETDNT: connect failed, insufficient resources ORA-06036: NETDNT: connect failed, no response from object ORA-06037: NETDNT: connect failed, node unreachable ORA-06039: NETDNT: connect failed ORA-06040: NETDNT: invalid login (connect) string ORA-06108: NETTCP: connect to host failed ORA-06113: NETTCP: Too many connections ORA-06114: NETTCP: SID lookup failure ORA-06143: NETTCP: maximum connections exceeded ORA-06315: IPA: Invalid connect string ORA-06316: IPA: Invalid database SID ORA-06317: IPA: Local maximum number of users exceeded ORA-06318: IPA: Local maximum number of connections exceeded ORA-06319: IPA: Remote maximum number of users exceeded ORA-06320: IPA: Remote maximum number of connections exceeded ORA-06404: NETCMN: invalid login (connect) string ORA-06413: Connection not open. ORA-10435: enable tracing of global enqueue service deadlock detetction ORA-10626: specify timeout for online index rebuild to wait for DML ORA-10906: Unable to extend segment after insert direct load ORA-12150: TNS:unable to send data ORA-12151: TNS:received bad packet type from network layer ORA-12152: TNS:unable to send break message ORA-12153: TNS:not connected ORA-12154: TNS:could not resolve service name ORA-12155: TNS:received bad datatype in NSWMARKER packet ORA-12156: TNS:tried to reset line from incorrect state ORA-12157: TNS:internal network communication error ORA-12158: TNS:could not initialize parameter subsystem ORA-12159: TNS:trace file not writeable ORA-12160: TNS:internal error: Bad error number ORA-12161: TNS:internal error: partial data received ORA-12162: TNS:service name is incorrectly specified ORA-12163: TNS:connect descriptor is too long ORA-12166: TNS:Client can not connect to HO agent. ORA-12168: TNS:Unable to contact Directory Server. ORA-12169: TNS:Net service name given as connect identifier is too long ORA-12170: TNS:Connect timeout occurred ORA-12171: TNS:could not resolve connect identifier: %s ORA-12196: TNS:received an error from TNS ORA-12197: TNS:keyword-value resolution error ORA-12198: TNS:could not find path to destination ORA-12200: TNS:could not allocate memory ORA-12201: TNS:encountered too small a connection buffer ORA-12202: TNS:internal navigation error ORA-12203: TNS:unable to connect to destination ORA-12204: TNS:received data refused from an application ORA-12205: TNS:could not get failed addresses ORA-12206: TNS:received a TNS error during navigation ORA-12207: TNS:unable to perform navigation ORA-12208: TNS:could not find the TNSNAV.ORA file ORA-12209: TNS:encountered uninitialized global ORA-12210: TNS:error in finding Navigator data ORA-12211: TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA ORA-12212: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA ORA-12213: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA ORA-12214: TNS:missing local communities entry in TNSNAV.ORA ORA-12215: TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA ORA-12216: TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA ORA-12217: TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA ORA-12218: TNS:unacceptable network configuration data ORA-12219: TNS:missing community name from address in ADDRESS_LIST ORA-12221: TNS:illegal ADDRESS parameters ORA-12222: TNS:no such protocol adapter ORA-12223: TNS:internal limit restriction exceeded ORA-12224: TNS:no listener ORA-12225: TNS:destination host unreachable ORA-12226: TNS:operating system resource quota exceeded ORA-12227: TNS:syntax error ORA-12228: TNS:protocol adapter not loadable ORA-12229: TNS:Interchange has no more free connections ORA-12230: TNS:Severe Network error ocurred in making this connection ORA-12231: TNS:No connection possible to destination ORA-12232: TNS:No path available to destination ORA-12233: TNS:Failure to accept a connection ORA-12235: TNS:Failure to redirect to destination ORA-12236: TNS:protocol adapter not loaded ORA-12316: syntax error in database link's connect string ORA-12326: database %s is closing immediately; no operations are permitted ORA-12329: database %s is closed; no operations are permitted ORA-12500: TNS:listener failed to start a dedicated server process ORA-12501: TNS:listener failed to spawn process ORA-12502: TNS:listener received no CONNECT_DATA from client ORA-12504: TNS:listener was not given the SID in CONNECT_DATA ORA-12505: TNS:listener could not resolve SID given in connect descriptor ORA-12506: TNS:listener was not given the ALIAS in CONNECT_DATA ORA-12507: TNS:listener could not resolve ALIAS given ORA-12508: TNS:listener could not resolve the COMMAND given ORA-12509: TNS:listener failed to redirect client to service handler ORA-12510: TNS:database temporarily lacks resources to handle the request ORA-12511: TNS:service handler found but it is not accepting connections ORA-12512: TNS:service handler found but it has not registered a redirect address ORA-12513: TNS:service handler found but it has registered for a different protocol ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor ORA-12515: TNS:listener could not find a handler for this presentation ORA-12516: TNS:listener could not find available handler with matching protocol stack ORA-12517: TNS:listener could not find service handler supporting direct handoff ORA-12518: TNS:listener could not hand off client connection ORA-12519: TNS:no appropriate service handler found ORA-12520: TNS:listener could not find available handler for requested type of server ORA-12521: TNS:listener could not resolve INSTANCE_NAME given in connect descriptor ORA-12522: TNS:listener could not find available instance with given INSTANCE_ROLE ORA-12523: TNS:listener could not find instance appropriate for the client connection ORA-12524: TNS:listener could not resolve HANDLER_NAME given in connect descriptor ORA-12525: TNS:listener has not received client's request in time allowed ORA-12526: TNS:listener: all appropriate instances are in restricted mode ORA-12527: TNS:listener: all instances are in restricted mode or blocking new connections ORA-12528: TNS:listener: all appropriate instances are blocking new connections ORA-12529: TNS:connect request rejected based on current filtering rules ORA-12531: TNS:cannot allocate memory ORA-12532: TNS:invalid argument ORA-12533: TNS:illegal ADDRESS parameters ORA-12534: TNS:operation not supported ORA-12535: TNS:operation timed out ORA-12536: TNS:operation would block ORA-12537: TNS:connection closed ORA-12538: TNS:no such protocol adapter ORA-12539: TNS:buffer over- or under-flow ORA-12540: TNS:internal limit restriction exceeded ORA-12541: TNS:no listener ORA-12542: TNS:address already in use ORA-12543: TNS:destination host unreachable ORA-12544: TNS:contexts have different wait/test functions ORA-12545: Connect failed because target host or object does not exist ORA-12546: TNS:permission denied ORA-12547: TNS:lost contact ORA-12549: TNS:operating system resource quota exceeded ORA-12550: TNS:syntax error ORA-12551: TNS:missing keyword ORA-12552: TNS:operation was interrupted ORA-12554: TNS:current operation is still in progress ORA-12555: TNS:permission denied ORA-12556: TNS:no caller ORA-12557: TNS:protocol adapter not loadable ORA-12558: TNS:protocol adapter not loaded ORA-12560: TNS:protocol adapter error ORA-12561: TNS:unknown error ORA-12562: TNS:bad global handle ORA-12564: TNS:connection refused ORA-12566: TNS:protocol error ORA-12569: TNS:packet checksum failure ORA-12570: TNS:packet reader failure ORA-12571: TNS:packet writer failure ORA-12574: TNS:redirection denied ORA-12582: TNS:invalid operation ORA-12583: TNS:no reader ORA-12585: TNS:data truncation ORA-12589: TNS:connection not bequeathable ORA-12590: TNS:no I/O buffer ORA-12591: TNS:event signal failure ORA-12592: TNS:bad packet ORA-12593: TNS:no registered connection ORA-12595: TNS:no confirmation ORA-12596: TNS:internal inconsistency ORA-12600: TNS: string open failed ORA-12602: TNS: Connection Pooling limit reached ORA-12606: TNS: Application timeout occurred ORA-12607: TNS: Connect timeout occurred ORA-12608: TNS: Send timeout occurred ORA-12609: TNS: Receive timeout occurred ORA-12612: TNS:connection is busy ORA-12615: TNS:preempt error ORA-12623: TNS:operation is illegal in this state ORA-12624: TNS:connection is already registered ORA-12636: Packet send failed ORA-12637: Packet receive failed ORA-12829: Deadlock - itls occupied by siblings at block %s of file %s ORA-12993: tablespace '%s' is offline, cannot drop column ORA-14117: partition resides in offlined tablespace ORA-14268: subpartition '%s' of the partition resides in offlined tablespace ORA-16000: database open for read-only access ORA-16003: standby database is restricted to read-only access ORA-16403: shutdown in progress - remote connection is not permitted ORA-16724: the intended state for resource has been set to OFFLINE ORA-16903: Unable to connect to database ORA-16914: Missing connect string. Try \"help\" ORA-18014: deadlock detected while waiting for resource %s ORA-21521: exceeded maximum number of connections in OCI (object mode only) ORA-21522: attempted to use an invalid connection in OCI (object mode only) ORA-23317: a communication failure has occurred ORA-24401: cannot open further connections ORA-24418: Cannot open further sessions. ORA-24778: cannot open connections ORA-25400: must replay fetch ORA-25401: can not continue fetches ORA-25402: transaction must roll back ORA-25403: could not reconnect ORA-25405: transaction status unknown ORA-25407: connection terminated ORA-25408: can not safely replay call ORA-25409: failover happened during the network operation,cannot continue ORA-25425: connection lost during rollback ORA-29306: datafile %s is not online ORA-30006: resource busy; acquire with WAIT timeout expired ORA-30036: unable to extend segment by %s in undo tablespace '%s' ORA-30040: Undo tablespace is offline ORA-31443: deadlock detected while acquiring lock on %s ORA-37013: (XSACQUIRE_DEADLOCK) Cannot wait to acquire object %j since doing so would cause a deadlock. ORA-44317: database open read-only
Oracle TimesTen In-Memory Database is a memory-optimized relational database. Deployed in the application tier, Oracle TimesTen In-Memory Database operates on databases that fit entirely in physical memory using standard SQL interfaces. High availability for the in-memory database is provided through real-time transactional replication.
This guide describes how to troubleshoot some of the problems users encounter when using the Oracle TimesTen In-Memory Database.
To work with this guide, you should understand how database systems work and have some knowledge of SQL (Structured Query Language).
TimesTen documentation is available on the product distribution media and on the Oracle Technology Network:
http://www.oracle.com/technetwork/products/timesten/documentation/
TimesTen supports multiple platforms. Unless otherwise indicated, the information in this guide applies to all supported platforms. The term Windows refers to all supported Windows platforms and the term UNIX applies to all supported UNIX platforms and also to Linux. Refer to the "Platforms" section in Oracle TimesTen In-Memory Database Release Notes for specific platform versions supported by TimesTen.
|
Note: In TimesTen documentation, the terms "data store" and "database" are equivalent. Both terms refer to the TimesTen database unless otherwise noted. |
This document uses the following text conventions:
| Convention | Meaning |
|---|---|
| boldface | Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. |
| italic | Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. |
monospace | Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. |
italic monospace | Italic monospace type indicates a variable in a code example that you must replace. For example:
Replace |
| [ ] | Square brackets indicate that an item in a command line is optional. |
| { } | Curly braces indicated that you must choose one of the items separated by a vertical bar ( | ) in a command line. |
| | | A vertical bar (or pipe) separates alternative arguments. |
| . . . | An ellipsis (. . .) after an argument indicates that you may use more than one argument on a single command line. |
| % | The percent sign indicates the UNIX shell prompt. |
| # | The number (or pound) sign indicates the UNIX root prompt. |
TimesTen documentation uses these variables to identify path, file and user names:
| Convention | Meaning |
|---|---|
install_dir | The path that represents the directory where the current release of TimesTen is installed. |
TTinstance | The instance name for your specific installation of TimesTen. Each installation of TimesTen must be identified at install time with a unique alphanumeric instance name. This name appears in the install path. |
bits or bb | Two digits, either 32 or 64, that represent either the 32-bit or 64-bit operating system. |
release or rr | The first three parts in a release number, with or without dots. The first three parts of a release number represent a major TimesTen release. For example, 1122 or 11.2.2 represents TimesTen 11g Release 2 (11.2.2). |
jdk_version | Two digits that represent the version number of the major JDK release. Specifically, 14 represent JDK 1.4; 5 represents JDK 5. |
timesten | A sample name for the TimesTen instance administrator. You can use any legal user name as the TimesTen administrator. On Windows, the TimesTen instance administrator must be a member of the Administrators group. Each TimesTen instance can have a unique instance administrator name. |
DSN | The data source name. |
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
The following sections in this chapter describe how to troubleshoot some of the problems you may encounter when using Oracle In-Memory Database Cache (IMDB Cache):
DDL operations on cached Oracle tables may cause cache group operations to fail
Avoiding performance and memory problems for large batch jobs on Oracle tables
Declaring NOVALIDATE on constraints causes cache group creation failure
If you are having problems with an AWT cache group, see Chapter 6, "Troubleshooting AWT Cache Groups".
This section describes some of the problems you might encounter when executing the CREATE CACHE GROUP statement.
| Possible cause | What to do |
|---|---|
| User does not have the correct Oracle privileges to create the cache group type. | See "Check Oracle privileges". |
| User has insufficient access to database. | You must have CACHE_MANAGER privilege to create a cache group. |
| The internal/external user does not match the Oracle user. | The TimesTen user name must be the same as the Oracle user name. |
| Cannot connect to Oracle | See:
Check the network status. |
| Cache administration user ID or password not set (when trying to create AWT or autorefresh cache groups) | See "Set the cache administration user name and password". |
| Unsupported data type mapping | See "Unsupported data type mapping". |
| Different nullability setting in Oracle | See "Null constraint does not match Oracle". |
| Failure to specify primary key in root table | The root table of a cache group must have a primary key. See "Defining Cache Groups" in the Oracle In-Memory Database Cache User's Guide. |
This section describes some of the problems you might encounter when starting or stopping the cache agent.
| Possible cause | What to do |
|---|---|
| Cache agent already running | See "Check status of the cache agent". |
| Unable to locate Oracle libraries |
|
ORACLE_HOME is invalid. | See "Check ORACLE_HOME environment variable". |
| Insufficient privileges | You must have CACHE_MANAGER privilege to start or stop the cache agent. |
Wrong OracleNetServiceName | Ensure that the OracleNetServiceName set in your DSN definition matches the Oracle Service Name for the Oracle instance that contains the tables to cache in TimesTen. |
Check the status of the cache agent by using the ttStatus utility as described in "Using the ttStatus utility" to check the status of the cache agent.
If the cache agent is not running, start it as described in "Starting the cache agent" in the Oracle In-Memory Database Cache User's Guide. If attempts to start the cache agent fail, then investigate the possible causes and reboot the machine before attempting to start the cache agent.
On UNIX or Linux platforms, check that the ORACLE_HOME environment variable is set correctly for the shell from which you are starting the cache agent and the TimesTen daemon. Use the ttmodinstall utility if you need to change the setting for ORACLE_HOME.
See "Environment variables" in Oracle TimesTen In-Memory Database Installation Guide.
NLS environment variables are set in the environment where the TimesTen application is running, even though TimesTen is not using the NLS environment variables. Unset the NLS environment variables and restart the TimesTen daemon, the cache agent, and the replication agent.
The server may experience a system failure or an unexpected reboot, such as with a power outage. In this case, the cache grid exits unexpectedly without the normal shutdown procedure.
The following sections describe how to recover when the system unexpectedly shuts down for two scenarios:
When the server shuts down, some of the cache grid notes exited unexpectedly, but others are still active. In this case, you must detach the dead nodes first by executing ttGridDetachList from an attached node, as follows:
Connect to a surviving grid node and execute ttGridDetachList to force a detach of all dead nodes from the grid.
Connect to the databases on the rebooted server. Start the replication agent by executing ttRepStart.
Attach the cache grid nodes by executing ttGridAttach.
Resume normal database operations.
If all cache grid nodes exited unexpectedly when the server shut down, perform the following tasks to recover the cache grid:
Log on to each grid node by connecting to the databases on the rebooted server. Start the replication agent by executing ttRepStart. The replication agent will flush the existing log, even if the log is current.
Call ttGridAttach on each node, which will fail with a communication error because it cannot communicate with other members. The failed attach cleans up the node information.
The last node on which you execute the ttGridAttach should succeed. At this point you have cleaned up all nodes, so execute ttGridAttach on all nodes again to attach each node to the grid.
Resume normal database operations.
If you receive error ORA-12514 indicating "could not resolve service name":
Use the Oracle TNSPING utility to verify that the service can be reached.
Ensure that the OracleNetServiceName set in your DSN definition matches the Oracle Service Name for the Oracle instance that contains the tables to cache in TimesTen.
Ensure that there is a service name defined. If it is a Windows Oracle client, use Oracle Net Configuration Assistant to configure a service name. In Oracle Net Configuration Assistant, navigate to Oracle Net Configuration -> Local -> Service Naming, select your Oracle server and confirm that there is a service name or a SID that identifies the Oracle server. If you add or modify a service name, you may need to reboot.
Check the cache administration user name and password on Oracle with SQL*Plus to make sure this service name works. For example:
%sqlplus cache_admin_user/cache_admin_pwd@OracleHost
cache_admin_user is the cache administration user name, cache_admin_pwd is the cache administration user password, and OracleHost is the OracleNetServiceName specified in your DSN definition.
|
Note: Your cache administration user may be different from your regular Oracle user. See "Create the Oracle users" in the Oracle In-Memory Database Cache User's Guide. |
Ensure that there is only one copy of tnsnames.ora on your TimesTen machine. Also check the permission on tnsnames.ora.
If you are running TimesTen on a UNIX system, check that the ORACLE_HOME environment variable points to the correct Oracle installation directory. For example:
ORACLE_HOME=/products/oracle10g
Check the Oracle client and server versions. See "Incompatible Oracle Server and Client versions".
You may receive ORA-12154 "TNS:could not resolve the connect identifier specified" when you try to connect to a a database.
This can occur when you are trying to use IMDB Cache and Oracle on the same machine and the TNS_ADMIN environment variable does not point to the proper tnsnames.ora file for Oracle. For example, you may have several instances of the Oracle Database running on a laptop.
In a production environment, you typically have TimesTen and Oracle running on different machines. In this case, do not reset the TNS_ADMIN environment variable to point to a tnsnames.ora file on the machine where TimesTen is running. The Oracle client uses the TNS_ADMIN setting to resolve the connection, but the TimesTen main daemon, the cache agent, the Web server, and the replication agent are unaware of the TNS_ADMIN setting. IMDB Cache cannot operate properly when the Oracle client and TimesTen use different tnsnames.ora files.
On Windows, set the TNS_ADMIN environment variable as follows:
Right-click My Computer and choose Properties.
On the Advanced tab, choose Environment Variables.
Add or edit TNS_ADMIN as a system environment variable so that it points to the directory that contains the tnsnames.ora file that you wish to use. You can include other tnsnames.ora files with the INAME command inside the tnsnames.ora file.
If you receive connection timeout errors such as ORA-12170 or ORA-12535, or if you receive ORA-03134 (server version not supported), verify that you are using an Oracle client and Oracle server whose versions are compatible.
Metalink Documentation Note 207303.1, "Client/Server/Interoperability Support Between Different Oracle Versions", lists the client/server combinations supported by Oracle.
See Oracle and TimesTen release notes for known problems with client/server versions.
This section describes some of the problems you might encounter when using the Oracle username and password.
| Possible cause | See... |
|---|---|
| The library environment variable is not set correctly | "Check library path environment variable". |
| Oracle processes not running | "Check status of TNS listener and Oracle Server". |
| User does not have the correct Oracle privileges | "Check Oracle privileges". |
| Incorrectly configured DSN | "Check DSN definition". |
| Problems with cache administration user ID or password | "Set the cache administration user name and password". |
| Inconsistent user and system environments | "Check user and system environment". |
| Dynamic libraries not loading | "Verify the loaded dynamic libraries". |
Check the library path environment variable on your platform.
| On this platform... | Check this variable... |
|---|---|
| UNIX | LD_LIBRARY_PATH
On 64-bit platforms, |
| Windows | PATH |
The library path environment variable must include the following information:
| TimesTen and platform bit combination | Setting |
|---|---|
| 64-bit TimesTen or 32-bit TimesTen on 32-bit platform | $ORACLE_HOME/LIB and $ORACLE_HOME/NETWORK/LIB |
| 32-bit TimesTen on 64-bit platform | $ORACLE_HOME/LIB32 and $ORACLE_HOME/NETWORK/LIB32 |
Try to connect to the Oracle database by using SQL*Plus or use Oracle Enterprise Manager to verify the status.
From an Oracle SQL*Plus command prompt, list the current Oracle privileges granted to you by entering:
SELECT * FROM SESSION_ROLES; SELECT * FROM SESSION_PRIVS;
Compare the privileges listed against the required privileges for the various IMDB Cache operations that are specified in "Grant privileges to Oracle users" in the Oracle In-Memory Database Cache User's Guide. Contact your Oracle Administrator if you require additional privileges.
Confirm you have correctly set the DSN attributes as described in "DSN for a TimesTen database that caches data from an Oracle database" in the Oracle In-Memory Database Cache User's Guide.
Confirm that the DSN definition for IMDB Cache is a system DSN.
Confirm that the DSN for IMDB Cache is defined only once.
Confirm Oracle user name and password. Use SQLPlus and connect to Oracle using the same OracleNetServiceName and OraclePWD used in your DSN definition to confirm they are correct.
If the Oracle client was installed and the machine has not been restarted, then the TimesTen daemon is still running under the "old" environment before the Oracle client install. Reboot your machine so the TimesTen can start under the "new" environment.
The cache administration user name and password needs to be set only once in a TimesTen database. However, it needs to be changed if the TimesTen database is destroyed and re-created or if the cache administration user name is dropped and re-created in the Oracle database.
The cache administration user name and password cannot be changed if the cache agent is running on the TimesTen database or there are cache groups in the database. The cache groups must be dropped before you can change the cache administration user name and password. You must also stop the cache agent before you change the cache administration user name and password, and then restart the cache agent after the user name and password have been changed.
From a ttIsql session, connect to the database as the cache manager user and call the ttCacheUidPwdSet built-in procedure to set the Oracle cache administration user name and password, as follows:
Command> call ttCacheUidPwdSet('cacheuser','oracle');
If it returns an error, check the Oracle ID, the cache administration user ID and cache administration password. In addition, check whether the Oracle instance is running.
You can also set the user name and password by executing the ttAdmin -cacheUidPwdSet utility command as a TimesTen external user with the CACHE_MANAGER privilege:
% ttAdmin -cacheUidPwdSet -cacheUid cacheuser -cachePwd oracle cachealone1
If you do not specify the -cachePwd option, the ttAdmin utility prompts for the cache administration user's password. For more information about the utility, see "ttAdmin" in Oracle TimesTen In-Memory Database Reference.
Test to see if the problem is due to differences in user and system environment. This procedure requires two session windows (Command Prompt windows in Windows or shell windows in UNIX).
Stop the TimesTen daemon.
In one session window, start the Timesten daemon as a regular user.
On Windows:
% install_dir/srv/ttsrv1122.exe -d -verbose
On UNIX:
% install_dir/srv/timestend -d verbose
Some messages will flash by, and then it goes into a wait state.
In another session window, try to restart the cache agent.
If Step 3 succeeds, then use Ctrl-C on Windows or the kill command on UNIX to stop the TimesTen daemon you started for the other session in Step 2.
Compare the user environment and system environment. For example, do both user and system see the same copy of oci.dll? Are there any differences in the path name to the oci.dll library between the user and system environments?
If you detect differences, make the necessary modifications.
Reboot the system and restart the TimesTen daemon.
If you are running on a Windows system with Visual C++ installed, verify the loaded dynamic libraries. This works only if you can start the cache agent without autorefresh:
Make sure TimesTen is started.
Start the cache agent without autorefresh.
Command> call ttCacheStart; Command> create cache group cg1 from t1(c1 int not null primary key);
Open the Windows Task Manager, find process ttora1122.exe and highlight it. Right-click on it and select Debug. This brings you into Visual C++ and you should see the loaded DLL in the debug window, as described in "Unable to resolve Oracle Service Name".
Load the cache group to force an cache connection from the cache agent:
Command> load cache group cg1 commit every 100 rows;
Compare the loaded DLL in your debug window with the partial list shown in Example 4-1.
Example 4-1 List of loaded dlls
This partial list was created with the Oracle client.
Loaded 'E:\TimesTen\tt1121_32\bin\timestenorad1121.exe', no matching symbolic information found. Loaded 'C:\WINDOWS\SYSTEM32\ntdll.dll', no matching symbolic information found. Loaded 'C:\WINDOWS\SYSTEM32\kernel32.dll', no matching symbolic information found. Loaded 'E:\TimesTen\tt1121_32\bin\tten1121.dll', no matching symbolic information found. Loaded 'E:\TimesTen\tt1121_32\bin\ttcommon1121.dll', no matching symbolic information found. Loaded 'C:\WINDOWS\SYSTEM32\wsock32.dll', no matching symbolic information found. Loaded 'C:\WINDOWS\SYSTEM32\ws2_32.dll', no matching symbolic information found. Loaded 'C:\WINDOWS\SYSTEM32\msvcrt.dll', no matching symbolic information found. Loaded 'C:\WINDOWS\SYSTEM32\ws2help.dll', no matching symbolic information found. Loaded 'C:\WINDOWS\SYSTEM32\advapi32.dll', no matching symbolic information found. Loaded 'C:\WINDOWS\SYSTEM32\rpcrt4.dll', no matching symbolic information found. ...
Error 5105, "OCI initialization failed," may occur when an operation requires contact with the Oracle database. For example, the error might occur in the following situations:
Starting the cache agent
Setting the cache administration user ID or password
Entering a SQL statement in TimesTen when autocommit=0 and PassThrough=3
Error 5105 contains additional information about its cause:
OCI is unable to find an Oracle library. See "Check library path environment variable" and check the permissions on the library specified in the error message.
ORACLE_HOME is invalid. See "Check ORACLE_HOME environment variable".
NLS environment variables are set in the environment where the TimesTen application is running, even though TimesTen is not using the NLS environment variables. Unset the NLS environment variables and restart the TimesTen daemon, the cache agent, and the replication agent.
When you try to create a cache group, you may receive the following error:
5115: Unsupported type mapping for column name
For example, table tab on Oracle can be described as follows:
COL1 NUMBER(38) NOT NULL COL2 NUMBER(38)
Try to create the cache group as follows:
CREATE CACHE GROUP cg FROM tab(col1 CHAR(10) NOT NULL PRIMARY KEY);
Error 5119 is displayed and the cache group is not created because the statement attempts to map a column of NUMBER data type to a column of CHAR data type.
See "Data type mappings allowed for key columns" in the Oracle In-Memory Database Cache User's Guide.
When you try to create a cache group, you may receive the following warning:
Warning 5119: Column name has different nullability setting in Oracle
For example, table tab on Oracle can be described as follows:
COL1 NUMBER(38) NOT NULL COL2 NUMBER(38)
Try to create the cache group as follows:
CREATE CACHE GROUP cg
FROM tab(col1 INTEGER NOT NULL PRIMARY KEY, col2 INTEGER NOT NULL);
Warning 5119 is displayed because col2 on Oracle does not have a NULL constraint, but col2 in the cache group is defined as NOT NULL.
DDL operations that are performed on an Oracle table that is being cached in TimesTen may cause a failure on the cache group. For example, the user drops a column on the Oracle table that is being cached in TimesTen. When the cache group is propagated or flushed, TimesTen will update the column that no longer exists in the Oracle table. When the cache group loads or refreshes, then TimesTen attempts to retrieve data from the column that has been dropped.
The following cache group operations may fail:
Autorefresh does not occur.
AWT cache group operations are not propagated or refreshed to/from Oracle.
Cache group load or propagate fails.
If you suspect the cache group operations are not working properly because of a DDL operation on the Oracle base table, then use DDL tracking to diagnose the issue. DDL tracking saves the change history for all the cached Oracle tables. The SQL statement and when it was executed are each written to a TimesTen table in the cache administrator user schema on Oracle.
For more information on how to create the DDL tracking objects and how to enable DDL tracking for the base table within Oracle, see "Tracking DDL statements issued on cached Oracle tables" in the Oracle In-Memory Database Cache User's Guide. For details on the built-in procedures used for initializing and enabling DDL tracking, see the Oracle TimesTen In-Memory Database Reference.
If you modify an object in a cache group and then the changes do not appear on a subsequent SQL statement, then one of the following may have occurred:
The object was dropped from the Oracle database or was somehow damaged.
The Oracle database was restored or recovered to a time before the object was created.
The Oracle database was down.
The user modified the OracleNetServiceName DSN or connection attribute after creating the cache group, which points to an Oracle database other than the one that the cache group was created upon.
For example, if the user creates an AWT cache group. Then, the user added rows to a table. When the user performs a SELECT * FROM the table, the rows did not appear. The ttmesg.log error file does not display an error that Oracle is not available. Instead, it displays the following messages:
12:09:02.10 Err : REP: 29934: CACHE1:meta.c(904): TT5221: TT5221: Oracle syntax error in OCIStmtExecute(): ORA-00942: table or view does not exist rc = -1 -- file "bdbStmt.c", lineno 1535, procedure "getOraOutTypesNLengths()" 12:09:02.27 Err : REP: 29934: CACHE1:receiver.c(1978): TT5250: Awt Initialization Failure. Could not compile meta data sql. 12:09:02.27 Warn: REP: 29934: CACHE1:transmitter.c(6505): TT16060: Failed to read data from the network. select() timed out
To recover, perform the following:
Stop all updates to the cache group.
If you are using an AWT cache group, then flush the cache group.
Recreate the cache group with the drop and create.
If the LOAD CACHE GROUP or REFRESH CACHE GROUP statement fails when you specify COMMIT EVERY n ROWS and n is greater than 0, the contents of the target cache group could be in an inconsistent state. Some cache instances may be partially loaded.
Unload the cache group and then load it again. In some situations, it may be easier to drop and re-create the cache group.
This section includes the following topics:
The ttCacheAutorefreshStatsGet procedure returns information about the last ten autorefresh operations on a specified cache group.
The ttCacheAutorefreshStatsGet procedure returns information only when the cache agent is running and the autorefresh state is ON or PAUSED. All of the return fields are set to 0 when the cache agent is restarted or the autorefresh state is changed to OFF.
Example 4-2 Calling ttCacheAutorefreshStatsGet
This example uses testcache, which is a READONLY cache group with one table and an incremental autorefresh interval of 10 seconds.
Command> call ttcacheautorefreshstatsget('user1','testcache');
< 1164260, 2007-07-23 15:43:52.000000, 850280, 44, 0, 75464, 528255, 75464, 310, 110, 6800,
1890912, 12439795, 1890912, 160020, InProgress >
< 1164260, 2007-07-23 15:43:33.000000, 831700, 43, 13550, 108544, 759808, 108544, 1030, 230,
12290, 1815448, 11911540, 1815448, 160020, Complete >
< 1164260, 2007-07-23 15:43:12.000000, 810230, 42, 17040, 115712, 809984, 115712, 610, 330,
16090, 1706904, 11151732, 1706904, 146470, Complete >
< 1164260, 2007-07-23 15:42:52.000000, 790190, 41, 14300, 94208, 659456, 94208,560, 320,
13410, 1591192, 10341748, 1591192, 129430, Complete >
< 1164260, 2007-07-23 15:42:32.000000, 770180, 40, 12080, 99328, 695296, 99328,450, 290,
11340, 1496984, 9682292, 1496984, 115130, Complete >
< 1164260, 2007-07-23 15:42:12.000000, 750130, 39, 10380, 86016, 598368, 86016,430, 230,
9720, 1397656, 8986996, 1397656, 103050, Complete >
< 1164260, 2007-07-23 15:41:52.000000, 730130, 38, 13530, 112640, 700768, 112640, 530, 220,
12780, 1311640, 8388628, 1311640, 92670, Complete >
< 1164260, 2007-07-23 15:41:32.000000, 710120, 37, 9370, 56320, 326810, 56320, 310, 160,
8900, 1199000, 7687860, 1199000, 79140, Complete >
< 1164260, 2007-07-23 15:41:22.000000, 700120, 36, 2120, 10240, 50330, 10240, 50, 200, 1870,
1142680, 7361050, 1142680, 69770, Complete >
< 1164260, 2007-07-23 15:41:12.000000, 690110, 35, 0, 0, 0, 0, 0, 0, 0, 1132440, 7310720,
1132440, 67650, Complete >
10 rows found.
Table 4-1 describes the results from the first row of output.
Table 4-1 ttCacheAutorefreshStatsGet results from last autorefresh operation
| Result | Field name | Description |
|---|---|---|
1164260 |
|
Cache group ID |
2007-07-23 15:43:52.000000 |
|
Timestamp when autorefresh started for this interval |
850280 |
|
Number of cache agent clock ticks in milliseconds at the time the autorefresh transaction started for this interval. This value is cumulative and is reset when the cache agent process starts. |
44 |
|
Autorefresh number |
0 |
|
The number of milliseconds spent in this autorefresh operation. It is zero because the operations is in progress. |
75464 |
|
The number of rows autorefreshed in this autorefresh operation. This would include all rows in the root table and child tables if the cache group had child tables. Note: This information is not provided for full autorefresh. |
528255 |
|
The number of bytes transferred from Oracle in this autorefresh operation. Note: This information is not provided for full autorefresh. |
75464 |
|
The number of root table rows autorefreshed in this autorefresh operation. |
310 |
|
The duration in milliseconds for the autorefresh query to execute on Oracle. Note: This information is not provided for full autorefresh. |
110 |
|
The duration in milliseconds for the autorefresh query to fetch rows from Oracle. Note: This information is not provided for full autorefresh. |
6800 |
|
The duration in milliseconds for TimesTen to apply the updated rows to the cache group. Note: This information is not provided for full autorefresh. |
1890912 |
|
The total number of rows autorefreshed since the cache agent started. Note: This information is not provided for full autorefresh. |
12439795 |
|
The total number of bytes transferred from Oracle since the cache agent started. Note: This information is not provided for full autorefresh. Note: This information is not provided for full autorefresh. Note: This information is not provided for full autorefresh. |
1890912 |
|
The total number of root table rows autorefreshed since the cache agent started. |
160020 |
|
The total autorefresh duration in milliseconds since the cache agent started. |
InProgress |
|
Status. The status can also be Complete or Failed. |
Note that the total number of autorefreshed rows (1890912) is the same as the total number of autorefreshed root table rows in this example because there are no child tables.
The number of autorefreshed rows in TimesTen does not necessarily reflect the number of rows updated on Oracle. The Oracle updates may be applied in TimesTen more than once, or multiple Oracle updates on the same row may be applied as one update in TimesTen.
TimesTen provides the cacheInfo SQL script that gathers information from the change log tables that exist on the Oracle database for autorefresh cache groups. See "Managing a caching environment with Oracle objects" in the Oracle In-Memory Database Cache User's Guide for more information about change log tables.
Run the script as the cache administration user on the Oracle database using SQL*Plus. If you run the script as a different user, it reports that the change log tables do not exist.
The script is in the following location:
install_dir/oraclescripts/cacheInfo.sql
The cacheInfo script displays the following information for each cached table:
% cd TimesTen_install_dir/oraclescripts % sqlplus cacheuser/oracle SQL> @cacheInfo *************Autorefresh Objects Information *************** Host name: sys1 Timesten datastore name: /users/OracleCache/alone1 Cache table name: ORATT.ORDERS Change log table name: tt_06_69245_L Number of rows in change log table: 100000 Maximum logseq on the change log table: 38 Timesten has autorefreshed updates up to logseq: 38 Number of updates waiting to be autorefreshed: 0 Number of updates that has not been marked with a valid logseq: 0 ****************************
The information returned for each change log table includes the name of the change log table, the name of its corresponding TimesTen cache table, the number of rows in the change log table, and the number of updates in the change log table that have not been automatically refreshed into the cache table.
The log sequence number (logseq) acts as a marker for the autorefresh operation.
The support log contains messages that show the progress of autorefresh. For example, testcache is a readonly cache group with an autorefresh interval of 10 seconds (10,000 milliseconds).
The support log shows when autorefresh starts:
15:43:33.96 Info: CAC: 5264: TT47118-5264-5676-refresh03918: Starting autorefresh number 43 for interval 10000ms
The message includes the following information:
Message number: TT47118
Timestamp (15:43:33.96)
Cache agent process ID (5264)
Thread ID (5676)
You can look up the message number in the Oracle TimesTen In-Memory Database Error Messages and SNMP Traps. For example, in the log message above, TT47118 is error message number 47118.
The thread ID is important because autorefresh numbers are unique only for a specific interval. Always check both the thread ID and the autorefresh number when you are tracking a specific autorefresh operation.
The support log also contains a longer message that reports information similar to the ttCacheAutorefreshStatsGet procedure. 108544 rows were updated in this autorefresh interval, and 1815448 rows have been updated since the cache agent was started. Note that the total number of rows and the total number of root table rows are the same in this message because there is only one table in the cache group. Number refers to the autorefresh number. All times are expressed in milliseconds.
15:43:51.81 Info: CAC: 5264: TT47087-5264-5676-refresh04387: Cache agent refreshed cache group USER1.TESTCACHE: Number - 43, Duration - 13550, NumRows - 108544, NumRootTblRows - 108544, NumOracleBytes - 759808, queryExecDuration - 230, queryFetchDuration - 1030, ttApplyDuration - 12290, totalNumRows - 1815448, totalNumRootTblRows - 1815448, totalNumOracleBytes - 11911540, totalDuration - 160020
Additional messages show that the autorefresh operation completes successfully:
15:43:51.81 Info: CAC: 5264: TT47119-5264-5676-refresh04449: Autorefresh number 43 finished for interval 10000ms successfully 15:43:51.81 Info: CAC: 5264: TT47119-5264-5676-fresher01619: Autorefresh number 43 succeeded for interval 10000 milliseconds
Inspect the timestamps to determine whether autorefresh is progressing as expected.
See "Managing TimesTen daemon options" in the Oracle TimesTen In-Memory Database Operations Guide for information about setting the support log location.
If ttCacheAutorefreshStatsGet shows that the status of an autorefresh operation is Failed, check the support log for messages related to the autorefresh operation with number the number shown in the ttCacheAutorefreshStatsGet output. Look for errors that occurred after the autorefresh operation started.
Example 4-3 ttCacheAutorefreshStatsGet output shows autorefresh failure
This row of output from ttCacheAutorefreshStatsGet shows a failed autorefresh operation.
< 1164260, 2007-08-01 14:56:36.000000, 959350, 9, 0, 0, 0, 0, 0, 0, 0, 1, 7,
1, 50, Failed >
The autorefresh number is 9.
The support log shows the start message for autorefresh number 9:
14:56:36.10 Info: CAC: 5988: TT47118-5988-4724-refresh03926: Starting autorefresh number 9 for interval 15000ms
The thread ID for autorefresh number 9 is 4724. Look for error messages with this thread ID.
The following messages appear in the support log:
14:56:36.10 Info: CAC: 5988: TT47117-5988-4724-refresh03953: Autorefresh thread for interval 15000ms is connected to instance inst1 on host host1. Server handle 231976252 14:56:36.12 Err : CAC: 5988: TT40018-5988-4724-refresh07567: TimesTen error code:5901, msg The Oracle refresh log table, "USER2"."TT_06_81799_L", for base table, USER2.READTAB2, cannot be found. 14:56:36.12 Info: CAC: 5988: TT47055-5988-4724-refresh05559: Autorefresh rolled back. 14:56:36.12 Info: CAC: 5988: TT47119-5988-4724-refresh04458: Autorefresh number 9 finished for interval 15000ms with error. 14:56:36.12 Err : CAC: 5988: TT40035-5988-4724-fresher01606: Autorefresh number 9 failed for cache groups with interval 15000 ms after 10 retries.
The error message for thread ID 4724 shows that the change log table, TT_06_81799_L, is missing. The introduction to "Autorefresh not refreshing cache at the specified interval" has a table entry that describes what to do in this situation.
You can use the ttTraceMon utility to diagnose autorefresh performance problems. See "AUTOREFRESH tracing".
TimesTen tracing severely impacts application performance and consumes a great deal of disk space if trace output is directed to a file. When you are finished, reset tracing to the default values.
Enable SNMP traps to alert you when autorefresh problems occur.The SNMP traps related to autorefresh include:
ttCacheAutoRefQueFullTrap
ttCacheIncAutoRefFailedTrap
ttCacheValidationErrorTrap
ttCacheValidationWarnTrap
ttCacheValidationAbortedTrap
See "Diagnostics through SNMP Traps" in the Oracle TimesTen In-Memory Database Error Messages and SNMP Traps.
The following recommendations may optimize performance for the IMDB Cache:
|
Note: Each of these suggestions involve performance trade-offs, which may not always be beneficial for optimal use. Consider and test each performance suggestion for your own configured environment. |
Pin the IMDB Cache meta tables and cache group base tables in the SGA. by executing the ALTER TABLE <table_name> CACHE statement to indicate to the Oracle database that these tables should be stored in the keep portion of the SGA buffer cache. Pinning IMDB Cache tables in the SGA increases the probability that any given datablock needed for a IMDB Cache refresh operation will be available in the SGA when the refresh is performed and will not force a disk read. This minimizes physical disk reads executed during TimesTen cache refresh operations. For more information about Oracle buffer cache management, see "Configuring and Using Memory" in the Oracle Database Performance Tuning Guide.
Pin IMDB Cache triggers into the shared pool using the dbms_shared_pool.keep procedure. Pinning triggers into the shared pool for applications where updates to the cache group base tables are infrequent keeps the trigger from having to be reloaded and reparsed. This is not necessary for highly volatile tables where the trigger will be executed frequently and will remain in the shared pool under any circumstances.
Enable parallel query. For very large base tables with 10 million rows or more, consider using the Oracle database parallel query facility. The primary join query between the log table and the base table is the kind of query which the Oracle database parallel query is designed to handle. When parallel processing is enabled, the parallel query optimizer generates a query plan that enables the original query to be broken into sections to be worked concurrently by different parallel query slave processes. When using parallel query, users should assign a default degree of parallelism of (2*N) to the cache group base table, where "N" is the number of CPUs on the machine. Then, experiment to understand what level of parallelism works best for their environment. Experiment with different table structures for base tables, as follows:
Use a standard heap table with default degree of parallelism assigned during table creation or by use of the ALTER TABLE PARALLEL command. Build an N-partition primary key index against the table.
Use an N-way partitioned table structure with partition range key based either on the table primary key or, in the case of a concatenated primary key, the high-order column of the primary key. The number of partitions should be set to the degree of parallelism. Use a local primary key index with the same number of partitions.
Use an N-way hashed partition structure using the primary key as the hash key, a local partitioned primary key index, and both index and table partitions equal to the degree of parallelism. The log table should not be partitioned, as the cardinalities of the log table should never be large enough that a partitioned log table would have any performance benefit. Further, given the continuously increasing value of the log table primary key column, range partitions cannot be used.
Customers sometimes run large batch jobs at month-end or year-end on Oracle tables that are cached in read-only cache groups with incremental autorefresh. This can cause performance and memory problems for autorefresh operations and replication unless preventative steps are taken.
The tasks described in this section are supported for these components in an IMDB Cache configuration:
Read-only cache groups that are not in a cache grid and are not replicated by an active standby pair
Cache grid
Active standby pair replication
Active standby pair with a return service specified
Active standby pair with a disaster recovery subscriber
Physical, synchronous Oracle Data Guard
Oracle RAC
Perform these tasks when large batch jobs must be run on cached Oracle tables:
Set the autorefresh state to PAUSED for cache groups with the AUTOREFRESH attribute that are affected by the batch job. Perform this task on each standalone cache grid node and on the active node of an active standby pair grid member. For example:
ALTER CACHE GROUP sampecg SET AUTOREFRESH STATE PAUSED; COMMIT;
Set the autorefresh state to PAUSED for cache groups with the AUTOREFRESH attribute that are not directly affected by the batch job. This ensures that there is a consistent view of the data during batch processing. Perform this task on each standalone cache grid node and on the active node of an active standby pair grid member.
Run the batch job on the cached Oracle tables.
Make sure all autorefresh change log records have been assigned a valid log sequence number (logseq). Call the cacheInfo.sql script:
% cd TimesTen_install_dir/oraclescripts
% sqlplus cacheuser/oracle
SQL> @cacheInfo
Look for the number of updates that have not been marked with a valid log sequence number. Ideally, the number should be zero or small (less than 100) for all tables in cache groups for which the autorefresh state was paused. For example:
*************Autorefresh Objects Information *************** Host name: host1 Timesten datastore name: /scratch/ttuser/ds/mydsn Cache table name: TTUSER.NOTAFFECTED Change log table name: tt_05_460491_L Number of rows in change log table: 1 Maximum logseq on the change log table: 1 Timesten has autorefreshed updates up to logseq: 1 Number of updates waiting to be autorefreshed: 0 Number of updates that has not been marked with a valid logseq: 0 **************************** Host name: host2 Timesten datastore name: /scratch/ttuser/ds/mydsn Cache table name: TTUSER.AFFECTED Change log table name: tt_05_460489_L Number of rows in change log table: 100 Maximum logseq on the change log table: 213 Timesten has autorefreshed updates up to logseq: 213 Number of updates waiting to be autorefreshed: 10000 Number of updates that has not been marked with a valid logseq: 0 ****************************
If the configuration includes active standby pair grid members, verify that the standby state is set to PAUSED on all standby nodes. Use the ttIsql cachegroups command.
For each cache group that was altered in step 1, manually refresh the cache group in parallel mode. Select appropriate values for the transaction size (number of rows committed at a time) and degree of parallelism. Perform this task on each standalone cache grid node and on the active node of an active standby pair grid member. For example:
REFRESH CACHE GROUP samplecg COMMIT EVERY n ROWS PARALLEL m; COMMIT;
Note that this operation automatically resets the autorefresh state to ON.
For each cache group that was altered in step 2, set the autorefresh state to ON. Perform this task on each standalone cache grid node and on the active node of an active standby pair grid member. For example:
ALTER CACHE GROUP sampecg2 SET AUTOREFRESH ON; COMMIT;
It is good practice to periodically coalesce the indexes on the autorefresh log tables. See "ALTER INDEX" in Oracle Database SQL Language Reference.
The following table shows possible causes for autorefresh problems.
| Possible cause | What to do |
|---|---|
| Cache agent not started with a cache administration user | Specify a cache administration user ID and password when starting the cache agent, as described in "Starting the cache agent" in the Oracle In-Memory Database Cache User's Guide. |
| Object ID of the base table has changed. | See "Recover and reset autorefresh Oracle objects". |
| Autorefresh trigger not enabled | See "Recover and reset autorefresh Oracle objects". |
Current log sequence number recorded in the TT_version_USER_COUNT table is less than to the maximum log sequence number in the autorefresh log table. | See "Recover and reset autorefresh Oracle objects". |
There is no row in the TT_version_USER_COUNT table with usercount > 0 for every active incremental autorefresh table | See "Recover and reset autorefresh Oracle objects". |
| Change log table is empty. | See "Recover and reset autorefresh Oracle objects". |
User count is less than 0 or any TT_version_USER_COUNT log sequence anomalies | See "Recover and reset autorefresh Oracle objects". |
| Autorefresh log table, trigger, or sequence associated with a cached table does not exist or is not valid. | Check whether the cache agent was started with the correct cache administration user ID. If the cache administration user ID is correct, follow the procedure described in "Recover and reset autorefresh Oracle objects".
Check the user error log for messages about "fatal anomalies". This indicates corrupt or missing Oracle objects. |
TT_version_USER_COUNT table is missing. | Check whether the cache agent was started with the correct cache administration user ID. If the cache administration user ID is correct, follow the procedure in "Recover and reset autorefresh Oracle objects".
Check the user error log for messages about "fatal anomalies". This indicates corrupt or missing Oracle objects. |
If the current log sequence number in the TT_version_USER_COUNT table changes, is different from the bookmark and the associated cached table is not refreshed by the next committed autorefresh. | Restart the cache agent. If that does not work, follow the procedure in "Recover and reset autorefresh Oracle objects". |
| Resource problem | Restart the cache agent. |
Incremental autorefresh does not work if the TRUNCATE statement is used on an Oracle base table. If TRUNCATE is used on an Oracle base table, then you must reset autorefresh by using the ALTER CACHE GROUP statement to set the autorefresh state to OFF followed by another ALTER CACHE GROUP to reset the autorefresh state to ON.
If you know or suspect the Oracle objects used by autorefresh are the cause of the problem, use the following procedure to re-create the Oracle objects.
Use ALTER CACHE GROUP to reset the autorefresh state to OFF on all cache groups on all databases that have the affected cached table:
ALTER CACHE GROUP cache_group_name SET AUTOREFRESH STATE OFF;
Shut down all cache agents on all affected databases.
Check if the user count is zero for each table in the cache group.
On the Oracle database, execute the following statement:
SELECT usercount FROM autorefresh_id.tt_version_user_count WHERE tablename ='owner.tablename';
If the count is not zero, set the count to zero:
UPDATE autorefresh_id.tt_version_user_count SET usercount = 0 WHERE tablename ='owner.tablename';
Start one of the cache agents. The cache agent performs a clean up operation. It displays the following message to the support log after it has completed the cleanup:
Cleanup of the Oracle objects completed
After the cache agent has completed the clean up, use ALTER CACHE GROUP to reset the autorefresh state back to ON:
ALTER CACHE GROUP cache_group_name SET AUTOREFRESH STATE ON;
Start all other cache agents.
Use ALTER CACHE GROUP to reset the autorefresh state back to ON for all of the affected cache groups on all databases.
If incremental autorefresh is not progressing, verify that:
Autorefresh state is ON
Cache agent is running
Inspect the support log for the conditions described in the following table:
Table summary is in the first heading cell.
| Condition | What to do |
|---|---|
| Oracle server connection errors or warnings | See "Troubleshooting Client/Server problems" for information about resolving connection problems. |
| Lock timeout errors or warnings on TimesTen | This usually occurs because of an open DDL transaction on the cache group. Commit the DDL transaction so that autorefresh can get the necessary locks. |
| Insufficient permanent data partition errors on TimesTen | Increase PermSize. |
| Autorefresh Oracle object validations errors or warnings | See "Recover and reset autorefresh Oracle objects". |
| Cache agent exits unexpectedly. | Contact Technical support. |
| Core files in main daemon directory | Contact Technical support. |
| Warnings about incremental autorefresh becoming full refresh | See "Incremental autorefresh becomes full autorefresh". |
| Warnings that autorefresh has not finished for a long time | The autorefresh transaction can take a long time if many transactions have occurred since the last autorefresh.
Note: Cache groups with the same autorefresh interval are autorefreshed in one transaction. |
The cache agent automatically verifies that Oracle objects exist and that they are valid so that autorefresh can progress. In normal operation, you should not see object validation errors or warnings in the user error log. If you see object validation errors, contact Technical support.unless one of the following conditions has occurred:
The TimesTen database has been destroyed without using the DROP CACHE GROUP statement.
A customer application inadvertently modifies the objects directly in the Oracle database.
A DDL operation occurs on the base table on the Oracle database. This disables the trigger that controls autorefresh operations.
The cache group needs to be re-created if one of the preceding conditions has occurred.
Incremental autorefresh can become full autorefresh if the cache administration user tablespace becomes full.
This section includes the following topics:
Monitoring the usage of the cache administration user's tablespace
Considerations when the cache administration user's tablespace is full
You can detect when incremental autorefresh becomes full refresh by several methods:
Check for messages in the support log that indicate full autorefresh operations are occurring. For example:
2007-08-08 08:06:51.35 Warn: CAC: 11384: TT47166-11384-1087179104-lMarker01403: A full autorefresh will be performed for Incremental autorefresh table USER1.READTAB because change log table TT_06_55555_L on Oracle has been truncated.
Use the ttCacheAutorefreshStatsGet procedure.
If autorefresh is InProgress for longer than usual, full autorefresh may be occurring.
If a much larger number of rows (autoRefNumRows) was autorefreshed than usual, full autorefresh may have occurred.
Check the support log for messages about full autorefresh.
If SNMP traps are enabled, the ttCacheRecoveryAutorefreshTrap SNMP trap indicates a full autorefresh.
TimesTen strongly recommends creating a separate tablespace for the cache administration user. This tablespace is used as the cache administration user's default tablespace. The tablespace contains autorefresh triggers for each Oracle table, change log tables for each Oracle table, and other objects that TimesTen needs for each cache administration user. If you do not specify a separate tablespace, then these objects are placed in the Oracle system tablespace.
Specify the tablespace when you create the cache administration user on Oracle. You can also specify the tablespace after user creation with the DEFAULT TABLESPACE clause of the Oracle ALTER USER statement.
Change log tables for each of the cached Oracle tables reside in the cache administration user tablespace. For each update on an Oracle table, one row (a change log record) is inserted into the change log table for that Oracle table. The size of a change log record in bytes is as follows:
size of change log record = size of primary key on Oracle table + 250
The number of records in a change log table depends on the update rate on the Oracle table and on the autorefresh interval on TimesTen. Every 20 seconds, TimesTen removes change log records that have been applied to all databases that cache the associated Oracle table.
When change logs are removed, a message similar to the following is displayed in the support log:
16:32:26.73 Info: CAC: 5652: TT47112-5652-4756-ogTblGC01036: Garbage collector deleted 1 rows from TT_06_383270_L where logseq < 1
There are options on how to manage what happens when the cache administration user tablespace is filled. See "Considerations when the cache administration user's tablespace is full" for more information.
Check for the following conditions if the cache administration user tablespace is full:
Is the autorefresh state set to PAUSED? Change log records accumulate when the state is PAUSED.
Has the cache group been created but not loaded? The default autorefresh state for cache group creation is PAUSED.
Is a cache group being created or is a database being duplicated? Both of these operations temporarily stop clean-up operations on the change log table.
Are the cache agents on all TimesTen databases running? If a cache agent is not running, change log records accumulate.
Has a database been abandoned without dropping autorefresh cache groups in the database? Abandoned databases result from scenarios such as the following:
The database is destroyed by ttDestroy -force.
The application connected to the database with the Overwrite connection attribute set to 1, but the cache groups that were in the old database are not re-created.
If the database still exists, connect to the abandoned database and drop the cache group.
Use the cacheInfo.sql script to find out how large the change log tables are for each cached Oracle table. Use the output to verify that the databases are still in use. See "Displaying information from the change log tables".
If the databases are still in use, verify that the cache agents are running.
Compare the autorefresh progress on TimesTen to the maximum log sequence number on the change log table. If TimesTen is behind, then call the ttCacheAutorefreshStatsGet procedure to see whether the autorefresh operations are successful. See "Using the ttCacheAutorefreshStatsGet procedure".
If the status is InProgress longer than seems reasonable, see "Poor autorefresh performance".
You may need to decrease the autorefresh interval or increase the size of the cache administration user tablespace.
There are options on how to manage what happens when the cache administration user tablespace is filled. See "Considerations when the cache administration user's tablespace is full" for more information.
To monitor the cache administration user tablespace, you can use either Oracle Enterprise Manager alerts or set the TimesTen tablespace threshold parameter.
The cache agent can be configured to periodically monitor the tablespace usage and issue a warning when it exceeds a specified threshold. Set the tablespace threshold percentage with the TblspaceThreshold parameter of the ttCacheConfig built-in procedure. For example, if you set the TblspaceThreshold parameter to 80, then a warning is issued when more than 80% of the tablespace is used.
If the threshold is set to zero, then no warning is issued. This is the default.
If the threshold is set between 1 and 99, a warning is issued when the tablespace threshold exceeds that number.
If the threshold is set to 100, then a warning is issued when the tablespace is full.
For example, to configure for a warning to be issued if the tablespace exceeds 80%, execute the following:
call ttCacheConfig('TblspaceThreshold',,,'80');
For full details of the ttCacheConfig built-in procedure, see the "ttCacheConfig" section in the Oracle TimesTen In-Memory Database Reference.
With Oracle tables that are cached in a TimesTen database, you can configure them to use incremental automatic refresh. For these tables, you can specify which one of the following is to occur when the cache administration user's tablespace is full:
The application performing the DML is to fail. This is the default.
The tablespace full recovery is set to none. The application receives an "Out of Tablespace" error from Oracle when the tablespace is full. At that point, the application will need to rollback the transaction.
Setting the tablespace full recovery to none is configured when you set the Param parameter to TblSpaceFullRecovery and the Value parameter to None with the ttCacheConfig built-in procedure. For example, the following configures Param to TblSpaceFullRecovery and Value to None for the employees table that is owned by terry:
call ttCacheConfig('TblSpaceFullRecovery','terry', 'employees','None');
Truncate the change log table to free up space and cause a full autorefresh.
When the cache administration user's tablespace is full, any application that is executing DML statements on the autorefresh cached Oracle tables continues to execute. A trigger executes to free up space for new change log records by deleting existing change log records. This can result in a full automatic refresh on cache groups that have the incremental automatic refresh mode configured. However, if the Oracle table is not configured for incremental automatic refresh, then no trigger executes.
To set the operation to enable the application to continue and cause an autorefresh, set the Param parameter to TblSpaceFullRecovery and the Value parameter to Reload with the ttCacheCon fig procedure. The user will see stale data until the full autorefresh is complete.
However, even if the user sets the cache configuration parameter TblSpaceFullRecovery with the value of Reload, the tablespace may not be able to be emptied enough to handle the case of a growing index. Deleting rows from the change log table may not free up enough space for the index that is on the change log table. If the index is growing so fast that it uses all the tablespace to the point where purging the change log tables does not help, then the user's application may receive the following error:
ORA-01654: unable to extend index <index> by 128 in tablespace <tblspace>
For full details of the ttCacheConfig built-in procedure, see the "ttCacheConfig" section in the Oracle TimesTen In-Memory Database Reference.
Poor autorefresh performance is usually the result of large autorefresh operations. Use the ttCacheAutorefreshStatsGet procedure to check the autorefresh duration and observe whether the status remains InProgress for a long time.
Factors that can cause large autorefresh operations include:
Unresponsive or dead TimesTen database degrades autorefresh performance
Autorefresh cache group refresh with excessive waiting on resources
Abnormally large change log and base tables degrade autorefresh performance
Large autorefresh interval
Large number of cache groups with the same interval
High rate of changes to the Oracle tables
The number of generations of child tables in a cache group
The number of rows in the cached Oracle tables
The size of the rows in the cached Oracle tables
Enable an AUTOREFRESH trace to diagnose autorefresh performance problems. See "AUTOREFRESH tracing".
|
Note: Automatic recovery for TimesTen cache groups only applies to read-only and user managed cache groups that use theAUTOREFRESH cache group attribute. In this section, all references to autorefresh cache groups are read-only and user managed cache groups that use the AUTOREFRESH cache group attribute. |
If any TimesTen databases containing autorefresh cache groups are destroyed or no longer in use, TimesTen continues to track autorefresh changes to the Oracle tables for the TimesTen database for which the cache agent is not running. This causes automatic refresh to cache groups in active TimesTen databases to slow down.
The cache agent is responsible for detecting if a database is unresponsive or no longer in use. You can specify if and how a dead TimesTen database is to be recovered. However, you cannot recover a TimesTen database if all of the Oracle objects have been removed.
The following sections describe how you can avoid a degraded autorefresh performance for inactive TimesTen databases:
You can instruct TimesTen to mark the database as dead and no longer accepting updates if the cache agent has not communicated with the Oracle server within a specific timeout period.
Set the timeout for the TimesTen database and the recovery method for each autorefresh cache group with the AgentTimeOut parameter in the ttCacheConfig built-in procedure. The timeout value applies to the all TimesTen databases that use the same cache administration user. You should set the timeout value greater than the time necessary to load the TimesTen database into memory on first connect and start the cache agent. Otherwise, the TimesTen database could be incorrectly marked as dead. For any planned maintenance for the TimesTen instance, you could temporarily set the AgentTimeOut value to zero to disable the timeout. For full details of the ttCacheConfig built-in procedure, see the "ttCacheConfig" section in the Oracle TimesTen In-Memory Database Reference.
For example, the following sets the timeout value for the TimesTen database to 6000 seconds or 100 minutes. If the cache agent does not contact the Oracle server within a 100-minute period, then the TimesTen database is marked as dead.
ttIsql> call ttCacheConfig('AgentTimeOut',,,'6000');
You can recover a TimesTen database and autorefresh cache groups if they are not synchronizing with the Oracle database. If there is no synchronization, then updates on the Oracle tables are not automatically refreshed to the corresponding TimesTen cache tables.
You can configure the DeadDbRecovery parameter of the ttCacheConfig built-in procedure to specify how to recover the synchronization for the TimesTen database and all autorefresh cache groups. The setting for DeadDbRecovery applies to all TimesTen databases that use the same cache administrator user. Set the DeadDbRecovery parameter to Normal, Manual or None to describe how TimesTen is to recover the database and all autorefresh cache groups. The DeadDbRecovery setting applies to all TimesTen databases that use the same cache administration user. While TimesTen is recovering the database and its autorefresh cache groups, there is an autorefresh status for the TimesTen database and the autorefresh cache groups that describes the recovery status for each of these entities. The TimesTen database can have an automatic refresh status of Alive, Dead or Recovering. The autorefresh cache groups can have an automatic refresh status of OK, Dead or Recovering. The TimesTen database status changes are linked to changes in the status for the autorefresh cache groups, as follows:
If the recovery method is set to Normal, then when TimesTen starts a full automatic refresh on an autorefresh cache group, the cache group's status is set to Recovering and the database's status is also set to Recovering.
The TimesTen database's status is only set to Alive when all of the autorefresh cache groups have either been recovered to OK or have been dropped.
When the database status is set to Dead, then all of its autorefresh cache groups are also set to Dead.
|
Note: You can determine the autorefresh status of the TimesTen database and autorefresh cache groups with thettCacheDbCgStatus built-in procedure, which is described in the "ttCacheDbCgStatus" section in the Oracle TimesTen In-Memory Database Reference. |
When communication between the cache agent and the Oracle server is re-established, TimesTen determines how to recover the autorefresh cache groups. TimesTen follows the recovery method you configured in the DeadDbRecovery parameter in the ttCacheConfig built-in procedure. This parameter can be set to one of the following:
Normal: This is the default. The autorefresh cache groups will each be recovered with a full automatic refresh. After the first full refresh, the cache group is recovered and will incrementally perform autorefresh.
The autorefresh cache groups within the same automatic refresh interval will be transactionally consistent. Because it is a full refresh, it is not as performant as an incremental refresh.
The autorefresh sets the status to Recovering. When the full autorefresh is completed successfully, the autorefresh cache group status is set to OK.
Manual: You must manually refresh an autorefresh cache group to recover it, or unload it if the cache group is dynamic.
None: The autorefresh cache group will never be recovered by a TimesTen autorefresh. Drop and recreate the cache group to recover it.
The database status changes as the first autorefresh cache group status changes. If there is at least one cache group that is in the process of recovery, then the database status is set to Recovering. Once all cache groups have been recovered, the status of the TimesTen database is marked as Alive.
The following example sets the DeadDbRecovery parameter to Normal for all autorefresh cache groups. The dead TimesTen database will be recovered when all of its autorefresh cache groups have each been recovered with a full automatic refresh.
ttIsql> call ttCacheConfig('DeadDbRecovery',,,'Normal');
When TimesTen databases participating in an active standby pair replication scheme contains cache groups, if the autorefresh status of the active master database is Dead and the autorefresh status of the standby master database is Alive, the standby master does not automatically assume the role of the active master. The recovery requires that you manually ensure that the cache and replication agents are executing. The specifics for each situation is as follows:
Table 4-2 Recovery for cache groups involved in active standby replication pair
| DeadDbRecovery Setting | Active Master | Standby Master | Resulting Behavior |
|---|---|---|---|
|
Normal |
Alive |
Dead |
Make sure that the cache and replication agents are executing on the standby master. Once the cache agent can connect to the Oracle Database, then the status of all autorefresh cache groups is set to Recovering. This sets the database to Recovering. Once a single cache group has received enough data to resume autorefresh, the status is set to OK. After all cache group are set to OK, the database is set to Alive. Alternatively, you can fail the standby master and rollout a new standby master. |
|
Normal |
Dead |
Alive |
Make sure that the cache and replication agents are executing on the active master. Once the cache agent can connect to the Oracle Database, then the status of all autorefresh cache groups is set to Recovering. This sets the database to Recovering. Once a single cache group has received enough data to resume autorefresh, the status is set to OK. After all cache group are set to OK, the database is set to Alive. Alternatively, you can fail the active master, switch the standby master as the new active and then rollout a new standby master. |
|
Normal |
Dead |
Dead |
Make sure that the cache and replication agents are executing on both masters. Once the cache agent can connect to the Oracle Database, then the status of all autorefresh cache groups is set to Recovering. This sets the database to Recovering. Once a single cache group has received enough data to resume autorefresh, the status is set to OK. After all cache group are set to OK, the database is set to Alive. Alternatively, you can rollout new masters. |
|
Manual |
Alive |
Dead |
Make sure that the cache and replication agents are executing on the standby master. Once the cache agent can connect to the Oracle Database, then the status of all autorefresh cache groups is set to Recovering. This sets the database to Recovering. Once a single cache group has received enough data to resume autorefresh, the status is set to OK. After all cache group are set to OK, the database is set to Alive. Alternatively, you can fail the standby master and rollout a new standby master. |
|
Manual |
Dead |
Alive |
Make sure that the cache and replication agents are executing on the active master. Use a manual refresh to recover the autorefresh cache groups on the active master. After all cache group are set to OK or have been dropped, the database is set to Alive. |
|
Manual |
Dead |
Dead |
Make sure that the cache and replication agents are executing on the active master. Use a manual refresh to recover the autorefresh cache groups on the active master. After all cache group are set to OK or have been dropped, the database is set to Alive. Changes are then replicated to the standby master. |
|
None |
Alive |
Dead |
Mark the standby master as failed. Execute |
|
None |
Dead |
Alive |
Destroy the dead active master with the |
|
None |
Dead |
Dead |
Rollout new masters. |
During an autorefresh cache group refresh, there can be excessive buffer busy waits, row lock waits, and deadlocks on updates in the Oracle database, which can negatively affect the throughput performance. When there are multiple deadlocks on updates in the Oracle database involving the autorefresh log tables, the following may appear in the support log:
Oracle native error code = 60, msg = ORA-00060: deadlock detected while waiting for resource An error occurred while preparing or executing the following Oracle sql statement: <some statement involving <cache admin user>.TT_##_#######_L where the # is some number>
You can improve your performance by modifying the INITRANS and FREELISTS settings, which can affect the concurrent inserts into the autorefresh log table as well as internal maintenance of these tables. The application updating the base table that is being autorefreshed encounters a throughput performance hit when these settings are not appropriately configured.
You can automatically or manually manage these settings as follows:
Use ASSM tablespace, which automatically manages FREELISTS.
Manually adjust FREELISTS and INITRANS for the autorefresh log table on the Oracle database.
The following details how to manually modify INITRANS and FREELISTS for the autorefresh log table on the Oracle database:
Retrieve the name of the autorefresh log table that is on the Oracle database.
Under the cache administration user login, execute the SQL*Plus script cacheInfo.sql that lists the autorefresh change log table name, along with other items. The following example executes the cacheInfo.sql script that lists the autorefresh change log table name as tt_06_1216726_L, as shown in bold:
SQL> @cacheInfo.sql
*************Autorefresh Objects Information ***************
Host name: syst
Timesten datastore name: /users/OracleCache/alone1
Cache table name: ORATT.ORDERS
Change log table name: tt_06_1216726_L
Number of rows in change log table: 1
Maximum logseq on the change log table: 2
Timesten has autorefreshed updates upto logseq: 1
Number of updates waiting to be autorefreshed: 1
Number of updates that has not been marked with a valid logseq: 0
****************************
Host name: consyst
Timesten datastore name: /users/OracleCache/alone1
Cache table name: ORATT.ITEMS
Change log table name: tt_06_1279699_L
Number of rows in change log table: 7
Maximum logseq on the change log table: 0
Timesten has autorefreshed updates upto logseq: 0
Number of updates waiting to be autorefreshed: 5
Number of updates that has not been marked with a valid logseq: 5
****************************
Manually alter the table on the Oracle database. The following example uses the table from the previous example. This example alters the INITRANS and FREELISTS settings for the bar.tt_06_1279699_L table.
|
Note: See "INITRANS integer" and "FREELISTS" in the Oracle Database SQL Language Reference for details on what are the correct values for configuring these settings. |
ALTER TABLE BAR.TT_06_1279699_L INITRANS 10; ALTER TABLE BAR.TT_06_1279699_L STORAGE(FREELISTS 5); or ALTER TABLE BAR.TT_06_1279699_L MOVE STORAGE(FREELISTS 5);
Alter the INITRANS and FREELISTS settings for the index for this table, which have the same name as the autorefresh change log table with an additional "L" at the end of it. For example, the index for table bar.tt_06_1279699_L is bar.tt_06_1279699_LL.
These settings should be the same as what you set for the autorefresh change log table.
ALTER INDEX BAR.TT_06_1279699_LL INITRANS 10; ALTER INDEX BAR.TT_06_1279699_LL STORAGE(FREELISTS 5);
The cache thread SQL refresh joins the change log table and the base table, which identifies rows needed to be refreshed into TimesTen. The larger the cardinalities of the base table and the change log table, the longer the time necessary to perform this join. Performance degradation may occur if either the change log table or the base table is abnormally large.
The following describe scenarios where the change log table can become abnormally large:
If the change log table is never purged in configurations where cache groups from multiple DSNs all reference the same base table, it increases in size indefinitely. If one or more of the cache agents for these groups are turned off, those DSNs will not properly refresh their cache groups and the change log tables will not be purged. If the autorefresh state is turned to paused on one of multiple nodes, the other nodes may slow down.
The change log table can grow abnormally large if some of the cache agents have been shut down. Resolve this issue by restarting the cache, which will purge all of the backlogged log rows to be purged and all of the cache groups to be synchronized after the completion of the refresh cycle for all cache groups.
The change log table can be abnormally large if rows inserted into the change log table are never purged and can never be purged by normal processing. This occurs when one or more DSNs are destroyed or rebuilt without first removing the cache groups. The cache group tables on the Oracle database have no information that the cache groups have been destroyed, which corrupts the entire cache group. Rebuild and reinitialize all of the cache groups associated with this base table. Alternatively, never destroy a DSN with cache groups. Instead, always drop the cache groups before destroying a DSN.
Change log tables can become fragmented when a high water mark occurs as the result of change logs building up when TimesTen is shut down, for example. If change log tables have become fragmented, you can:
Coalesce their indexes. This can be done without preventing DML changes to the base tables.
Perform an online segment shrink. This can be done without preventing DML changes to the base tables. See Oracle Database Administrator's Guide.
Rebuild the change log tables.
Check to see whether space is being wasted:
Determine the name of the change log table by running the cacheInfo.sql script on the Oracle database.
Calculate the size of the change log table. Call the result A. Adapt the name of the change log table in this example.
SELECT table_name, ROUND((BLOCKS*8),2)||'KB' "size" FROM user_tables WHERE table_name LIKE 'TT_05_%_L";
Calculate the size of the data in the change log table. Call the result B. Adapt the name of the change log table in this example.
SELECT table_name, ROUND((num_rows*avg_row_length/1024),2)|| 'KB' "size" FROM user_tables WHERE table_name LIKE 'TT_05_%_L';
If (B/A)*100 is greater than 50 percent, then there is at least 40 percent space wasted (assuming a PCTFREE storage parameter set to 10). If there is at least 40 percent space wasted, defragmenting the change log table is recommended.
Perform these steps to defragment the change log table:
Alter the cache group to set the autofresh state to PAUSED.
Copy the rows in the change log table to a temporary table.
Truncate the change log table.
Insert the rows from the temporary table to the change log table.
Alter the cache group to set the autorefresh state to ON.
When a relatively short refresh interval, such as a few hundred milliseconds, is combined with a large number of entries in the log table or in the base table, a cache refresh operation does not complete before the next refresh operation is scheduled to begin. In this case, the entries in the log table can be un-marked when the current autorefresh cycle finishes.
Thus, the same rows can be refreshed from the base table to the cache group in the next autorefresh cycle, by which time the rows will be marked. Make sure that the time it for the refresh is greater than the refresh interval. Set the refresh interval to a value where redundant refreshes will not occur.
If the Oracle table on which you want to create the cache group declares NOVALIDATE on columns with primary key, UNIQUE or NOT NULL constraints, the creation of the cache group fails.
|
Note: This does not apply to any foreign key constraints. However, TimesTen recommends that any matching foreign key is in the enabledVALIDATE state. Your workload performance may be affected when you alter a foreign key column to the enabled VALIDATE state. |
TimesTen perceives a NOVALIDATE on a primary key or NOT NULL table column definition as a NULL and, therefore, not qualified as a column on which to build the cache group. Thus, all columns with the primary key, UNIQUE and NOT NULL column constraints must be enabled with the VALIDATE state when creating a cache group from the Oracle table.
When you create a cache group from an Oracle table with one or more of these constraints, the following errors are thrown:
5124: Autorefresh/propagate are not allowed on restricted cache group 5168: Restricted cache groups are deprecated 5120: No matching unique index with not null columns, unique key constraint with not null columns, or primary key constraint on table EVENTLOG, cache operations are restricted.
If you receive these errors, you can perform a SELECT statement to verify any existing NOVALIDATE constraints on the Oracle table. The following SELECT statement shows all constraints on the MyTable table:
SQL> select constraint_name, constraint_type, validated, status from
all_constraints where table_name = 'MyTable';
CONSTRAINT_NAME C VALIDATED STATUS
------------------------------ - ------------- --------
REFID_CONSTRAINT C VALIDATED ENABLED
PKEY_CONSTRAINT P NOT VALIDATED DISABLED
If the table column that is to be the primary key for the cache table is enabled as NOVALIDAT
E, perform the following steps to enable the column with the VALIDATE state:
Enable the NOVALIDATE state for the primary key column.
SQL> alter table MyTable modify constraint PKEY_CONSTRAINT
enable novalidate;
Table altered.
SQL> select constraint_name, constraint_type, validated, status
from all_constraints where table_name = 'MyTable';
CONSTRAINT_NAME C VALIDATED STATUS
------------------------------ - ------------- --------
REFID_CONSTRAINT C VALIDATED ENABLED
PKEY_CONSTRAINT P NOT VALIDATED ENABLED
Enable the VALIDATE state for the primary key column.
SQL> alter table MyTable modify constraint PKEY_CONSTRAINT validate;
Table altered.
SQL> select constraint_name, constraint_type, validated, status
from all_constraints where table_name = 'MyTable';
CONSTRAINT_NAME C VALIDATED STATUS
------------------------------ - ------------- --------
REFID_CONSTRAINT C VALIDATED ENABLED
PKEY_CONSTRAINT P VALIDATED ENABLED
There may be some concern about lock contention when seeing DBMS_LOCK in the Automated Workload Repository (AWR) Report. However, this DBMS_LOCK wait event does not affect the application performance in an IMDB cache grid, even though the database time consumption in the AWR report seems high. This wait event is the garbage collector session trying to place a hold on a resource that another garbage collector session from another database has already locked. Thus, only the current garbage collector session waits. The wait for the garbage collector process does not block other processes, except other garbage collectors.
For example, the following shows a contention event in the AWR report:
AWR Top 5 Timed Events Avg %Total ~~~~~~~~~~~~~~~~~~ wait Call Event Waits Time (s) (ms) Time Wait Class ------------------------------ ------------ ----------- ------ ------ ---------- enq: UL - contention 2,388 6,997 2930 72.0 Application
In addition, only a small amount of CPU time is used for the garbage collector, as shown in the "SQL ordered by CPU Time" section in the PERF AWR report.
SQL ordered by CPU Time DB/Inst: REM0LNX/REM Snaps: 14976-14977
-> Resources reported for PL/SQL code includes the resources used by all SQL
statements called by the code.
-> % Total DB Time is the Elapsed Time of the SQL statement divided
into the Total Database Time multiplied by 100
CPU Elapsed CPU per % Total
Time (s) Time (s) Executions Exec (s) DB Time SQL Id
---------- ---------- ------------ ----------- ------- -------------
0 3,508 120 0.00 36.1 0mt5pk2501gph
Module: timestenorad@etcpro01.oracle.com (TNS V1-V3)
DECLARE v_lockHandle VARCHAR2(200); BEGIN dbms_lock.allocate_unique(
'ORATT$ORA_GC1_CACHEADMIN', v_lockHandle); :retval := dbms_lock.request(
v_lockHandle, dbms_lock.x_mode, 30, FALSE); END;
0 3,499 120 0.00 36.0 bb07h2a1v817x
Module: timestenorad@etcpro01.oracle.com (TNS V1-V3)
DECLARE v_lockHandle VARCHAR2(200); BEGIN dbms_lock.allocate_unique(
'ORATT$ORA_DDSMONITOR1_CACHEADMIN', v_lockHandle); :retval :=
dbms_lock.request(v_lockHandle, dbms_lock.x_mode, 30, FALSE); END;
Copyright © 1994-2012, Oracle and/or its affiliates. All rights reserved.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
If this document is in prerelease status:
This documentation is in prerelease status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.
The following sections in this chapter describe how to use the TimesTen utilities and other tools that are used to diagnose problems with the TimesTen database:
The ttIsql utility enables you to interactively execute SQL statements and report status information on your TimesTen database.
All TimesTen SQL operations can be executed from a ttIsql Command> prompt.
Example 1-1 Using the ttIsql utility
To start the ttIsql utility for the demo database, enter:
% ttIsql demo
You should see output similar to the following:
Copyright (c) 1996-2011, Oracle. All rights reserved. Type ? or "help" for help, type "exit" to quit ttIsql. connect "DSN=demo"; Connection successful: DSN=demo;UID=ttuser;DataStore=c:\temp\demo; DatabaseCharacterSet=US7ASCII;ConnectionCharacterSet=US7ASCII; DRIVER=C:\WINDOWS\system32\ttdv70.dll;Authenticate=0;PermSize=20;TypeMode=0; (Default setting AutoCommit=1) Command>
You can then execute SQL statements or ttIsql commands at the Command> prompt.
"Using the ttIsql Utility" in the Oracle TimesTen In-Memory Database Operations Guide describes how to use the most common ttIsql commands. The following ttIsql commands are commonly used when troubleshooting:
monitor formats the contents of the SYS.MONITOR table.
See "Displaying database structure information" in the Oracle TimesTen In-Memory Database Operations Guide.
dssize prints database size information.
See "Displaying database structure information" in the Oracle TimesTen In-Memory Database Operations Guide.
showplan prints the optimizer execution plans for selects, updates, and deletes in this transaction.
See "Viewing and changing query optimizer plans" in the Oracle TimesTen In-Memory Database Operations Guide.
isolation sets or displays the isolation level.
See "Working with transactions" in the Oracle TimesTen In-Memory Database Operations Guide.
timing prints query timing.
See "Timing ODBC function calls" in the Oracle TimesTen In-Memory Database Operations Guide.
optprofile prints the current optimizer flag settings and join order.
See "Viewing and changing query optimizer plans" in the Oracle TimesTen In-Memory Database Operations Guide.
For the full list of ttIsql features, see the lists of options and commands under the description of the ttIsql utility in the Oracle TimesTen In-Memory Database Reference.
Use the ttStatus utility to check the status of the TimesTen daemon and the state of all TimesTen connections.
Example 1-2 ttStatus shows TimesTen daemon is not running
In this example, the output from ttStatus indicates that no TimesTen daemon is running. If the daemon has stopped unexpectedly, see "No response from TimesTen daemon or subdaemon" for troubleshooting information.
On Windows:
C:\>ttStatus ttStatus: Could not connect to the TimesTen service. If the TimesTen service is not running, please start it by running "ttDaemonAdmin -start".
On UNIX platforms:
$ ttStatus ttStatus: Could not connect to the TimesTen daemon. If the TimesTen daemon is not running, please start it by running "ttDaemonAdmin -start".
Example 1-3 ttStatus shows TimesTen daemon is running
In this example, the output from ttStatus indicates that the TimesTen daemon is running. It recognizes one database named demo.
The first line indicates that the TimesTen daemon is running as process 884 on port 17000 for the TimesTen instance MYINSTANCE. The second line indicates the TimesTen Server is running as process 2308 on port 17002.
There are currently seven connections to the database: one user and six subdaemon connections. You may see up to 2047 connections.
The restart policies for the cache agent and the replication agent in the database are set to manual.
|
Note: This example was produced on Windows. The results are the same on UNIX platforms except for the formats of the database path and the shared memory key. |
C:\>ttStatus TimesTen status report as of Mon Aug 6 22:03:04 2012 Daemon pid 884 port 17000 instance MYINSTANCE TimesTen server pid 2308 started on port 17002 ------------------------------------------------------------------------ Data store c:\temp\demo There are 7 connections to the data store Replication policy : Manual Cache Agent policy : Manual PL/SQL enabled. ------------------------------------------------------------------------ Data store c:\temp\demo Shared Memory KEY Global\DBI45b94095.1.SHM.4 HANDLE 0x278 Type PID Context Connection Name ConnID Process 4616 0x00d08820 demo 1 Subdaemon 2136 0x00526768 Worker 2042 Subdaemon 2136 0x0072e750 Flusher 2043 Subdaemon 2136 0x007348b8 Checkpoint 2044 Subdaemon 2136 0x067b0068 Aging 2045 Subdaemon 2136 0x067c0040 Monitor 2047 Subdaemon 2136 0x068404c8 HistGC 2046 Replication policy : Manual Cache agent policy : Manual ------------------------------------------------------------------------ End of report
Example 1-4 ttStatus shows replication information
In this example, the output from ttStatus indicates that the TimesTen daemon is running. It recognizes three databases: demo, subscriber1ds, and masterds. The subscriber1ds and masterds databases are replicated databases. In this example, the output from ttStatus indicates that the replication agents for the replicated databases have been started. Bidirectional replication has been configured between masterds and subscriber1ds. Each replication agent has five connections to the database.
C:\>ttStatus TimesTen status report as of Mon Aug 6 22:03:04 2012 Daemon pid 5088 port 17000 instance MYINSTANCE TimesTen server pid 4344 started on port 17002 ------------------------------------------------------------------------ Data store c:\temp\subscriber1ds There are 12 connections to the data store Shared Memory KEY Global\DBI45b9471c.2.SHM.2 HANDLE 0x280 Type PID Context Connection Name ConnID Process 1244 0x00d08fb0 subscriber1ds 1 Replication 4548 0x00aed2f8 LOGFORCE 4 Replication 4548 0x00b03470 TRANSMITTER 5 Replication 4548 0x00b725a8 RECEIVER 6 Replication 4548 0x00b82808 REPHOLD 2 Replication 4548 0x00b98980 REPLISTENER 3 Subdaemon 2752 0x00526768 Worker 2042 Subdaemon 2752 0x0072a758 Flusher 2043 Subdaemon 2752 0x007308c0 Checkpoint 2044 Subdaemon 2752 0x00736a28 HistGC 2046 Subdaemon 2752 0x067f02f8 Aging 2045 Subdaemon 2752 0x068364a0 Monitor 2047 Replication policy : Manual Replication agent is running. Cache agent policy : Manual ------------------------------------------------------------------------ Data store c:\temp\masterds There are 12 connections to the data store Shared Memory KEY Global\DBI45b945d0.0.SHM.6 HANDLE 0x2bc Type PID Context Connection Name ConnID Process 5880 0x00d09008 masterds 1 Replication 3728 0x00aed570 LOGFORCE 4 Replication 3728 0x00b036e8 TRANSMITTER 5 Replication 3728 0x00b168b8 REPHOLD 3 Replication 3728 0x00b1ca20 REPLISTENER 2 Replication 3728 0x00b22b88 RECEIVER 6 Subdaemon 3220 0x00526768 Worker 2042 Subdaemon 3220 0x0072e768 Flusher 2043 Subdaemon 3220 0x007348d0 Checkpoint 2044 Subdaemon 3220 0x067b0068 Aging 2045 Subdaemon 3220 0x067c0040 Monitor 2047 Subdaemon 3220 0x068404c8 HistGC 2046 Replication policy : Manual Replication agent is running. Cache agent policy : Manual ------------------------------------------------------------------------ Data store c:\temp\demo There are no connections to the data store Replication policy : Manual Cache agent policy : Manual ------------------------------------------------------------------------ End of report
Example 1-5 ttStatus shows cache group information
This example shows the cache agent running on rep1 database. There is one cache group in the database. The cache agent has five connections to the database.
C:\>ttStatus TimesTen status report as of Mon Aug 6 22:03:04 2012 Daemon pid 1012 port 17000 instance MYINSTANCE No TimesTen server running ---------------------------------------------------------------- Data store c:\data\rep1 There are 12 connections to the data store Shared Memory KEY Global\DBI45ef98ac.1.SHM.56 HANDLE 0x260 Type PID Context Connection Name ConnID Cache Agent 3380 0x00bbddf0 Handler 2 Cache Agent 3380 0x00c3f318 Aging 3 Cache Agent 3380 0x07380398 Timer 4 Cache Agent 3380 0x073cfa18 ttora70 6 Cache Agent 3380 0x073ff010 ttora70 7 Process 2084 0x00c48ee8 rep1 1 Subdaemon 1632 0x006bc430 Worker 2042 Subdaemon 1632 0x06630458 Flusher 2045 Subdaemon 1632 0x0664f978 Checkpoint 2044 Subdaemon 1632 0x0665ee60 HistGC 2043 Subdaemon 1632 0x066de720 Aging 2046 Subdaemon 1632 0x0670dc78 Monitor 2047 Replication policy : Manual Cache agent policy : Manual TimesTen's Cache agent is running for this data store ----------------------------------------------------------------- End of report
Example 1-6 ttStatus shows connection to old instance
This example shows a connection to an old instance of a database. This can occur when a database is invalidated, but some users have not disconnected from the invalidated copy of the database still in memory. After all users disconnect, the memory can be freed.
C:\>ttStatus TimesTen status report as of Mon Aug 6 22:03:04 2012 Daemon pid 5088 port 17000 instance MYINSTANCE TimesTen server pid 4344 started on port 17002 ----------------------------------------------------------------- Data store c:\temp\sample There are no connections to the data store Obsolete or not yet active connection(s): Process 4696 context 0xd08800 name sample connid 1, obsolete connection, shmKey 'Global\DBI45b94c6f.3.SHM.4' Replication policy : Manual Cache agent policy : Manual ----------------------------------------------------------------- End of report
The ttCapture utility captures information about the configuration and state of your TimesTen system into a file that provides technical support with a snapshot of your system at the time the ttCapture utility is running. The ttCapture utility generates a file named ttcapture.date.time.log. By default, the file is written to the directory from which you invoke the ttCapture utility. Use the ttCapture -dest option to direct the output file to be written to another directory.
If you run ttCapture again, it writes the information to a new file.
On Windows platforms, running ttCapture also produces an XML file named ttcapture.date.time.nfo that contains output from the msinfo32 utility.
When you experience a problem with a TimesTen database, run ttCapture with the DSN option for the database as soon as possible, either when you are encountering the problem or immediately afterward.
|
Note: Always double-quote directory and file names in case there are spaces in the names. |
When you contact technical support, upload the ttcapture.date.number.log file to the Service Request. Windows users should also upload the ttcapture.date.time.nfo file.
See "ttCapture" in the Oracle TimesTen In-Memory Database Reference for information about additional options.
TimesTen uses a TimesTen daemon to manage access to the databases. As the daemon operates, it generates error, warning and informational messages. These messages may be useful for TimesTen system administration and for debugging applications.
By default, informational messages are stored in:
A user error log that contains information you may need to see. Generally, these messages contain information about actions you may need to take.
A support log containing everything in the user error log plus information for use by technical support.
See "Modifying informational messages" in the Oracle TimesTen In-Memory Database Operations Guide for information about configuring the logs, including their location and size.
Use the ttTraceMon utility to log various trace information on a number of TimesTen components. Each TimesTen component can be traced at different levels of detail. You can list all of the traceable TimesTen components and their current tracing level by specifying ttTraceMon with the show subcommand. The full list of options for ttTraceMon is described in the "ttTraceMon" section in the Oracle TimesTen In-Memory Database Reference.
TimesTen tracing severely impacts application performance and consumes a great deal of disk space if trace output is directed to a file. In addition, when using AWT cache groups, you must restart the replication agent when trying to trace the ORACON component with ttTraceMon. Use the ttTraceMon utility only when diagnosing problems. When you are finished, reset tracing to the default values.
Example 1-7 Default trace levels for components
This example shows that the levels for most tracing components are set to level 0 (off) for the demo database. Both the ERR and DEADLOCK components are set to 1 for tracing by default. See "ERR tracing".
% ttTraceMon -e show demo AGING ... 0 API ... 0 ASYNCMV ... 0 AUTOREFRESH ... 0 CG ... 0 CGRID ... 0 CGRIDC ... 0 CKPT ... 0 DEADLOCK ... 1 EE ... 0 ERR ... 1 FLOW ... 0 HEAP ... 0 LATCH ... 0 LOCK ... 0 LOG ... 0 LOGF ... 0 OPT ... 0 ORACON ... 0 PLOAD ... 0 PT ... 0 REPL ... 0 SM ... 0 SQL ... 0 TEST ... 0 TRACE ... 0 XA ... 0 XACT ... 0
The output for most TimesTen components is of interest only to technical support. However, the output for the SQL, API, LOCK, ERR, AGING and AUTOREFRESH components may be useful to you when you are troubleshooting application problems.
The rest of this section includes the following topics:
Start a new trace by specifying ttTraceMon datastore. For example, to start a trace on the demo database, enter:
% ttTraceMon demo Trace monitor; empty line to exit Trace >
At the Trace prompt, specify the type of trace and its level. For example, to start tracing the SQL component at level 3, enter:
Trace > level sql 3
At this point you can run your application and the TimesTen trace information is written to a trace buffer. There are two ways to read the contents of the trace buffer:
From the Trace prompt, use the outfile command to direct the trace buffer data to a file. You must do this before running your application. When writing tracing information to a file, new trace information is concatenated to the existing contents of the file.
From the Trace prompt, use the dump command to display the trace buffer data to your screen.
|
Note: The contents of the trace buffer accumulate with each new trace. To clear the trace buffer, use theflush command from a ttTraceMon prompt. Clear the buffered trace records for a specific component by specifying the component with the flush command. |
Each record from the trace buffer has the following format:
timestamp sequence component level connection processid operation
The fields in the records are defined as follows:
timestamp is the time at which the operation was executed.
sequence is the incremental number that identifies the trace line.
component is the TimesTen component being traced (such as SQL, API, LOCK, or ERR).
level is the trace level associated with the trace line. The range of trace levels differs by component, but for all components, the lowest trace level generates the least verbose output and highest trace level generates the most verbose output. For example, if you are tracing SQL at level 4, your output includes lines for levels 2 (prepare), 3 (execute), and 4 (open, close, fetch).
|
Note: Trace levels for some components are not a continuous range of numbers. If you enter a number that does not correspond to a supported level for a component, tracing occurs at the highest supported level that is less than the number you entered. For example, if tracing levels for a component are 1, 2, 3, 4, and 6 and you enter 5, tracing events for level 1, 2, 3, and 4 are generated. |
connection is the internal connection ID identifying the connection that generated the trace. This number corresponds to the ConnID shown in the ttStatus output. The connection ID is also used as the first element of the transaction ID.
processid is the operating system process ID for the process that generated the trace.
operation is the operation that occurred (such as SQL statement, API operation, or error message).
For example, a line from the trace buffer after a SQL trace at level 3 might look like this:
10:39:50.231 5281 SQL 2L 1C 3914P Preparing: select cust_num from customer
Using ttTraceMon with the SQL component provides information about the SQL being prepared or executed by the TimesTen engine. Table 1-1 describes the levels for SQL tracing. Each level with a '+' sign includes the trace information described for that level, plus all levels preceding it.
Table 1-1 SQL tracing levels
| Level | Output |
|---|---|
|
2 |
SQL commands being prepared. |
|
3 |
+ SQL commands being executed |
|
4 |
+ The effect of command pooling (prepares not being done because the prepared command already exists in the pool), the need for reprepares (for example, because an index was created), and commands being destroyed. At this level, |
|
5 |
+ Some internal data, such as command numbers, which are not generally useful for customer-level debugging. |
|
Note: TimesTen recommends tracing SQL at level 3 or 4. SQL tracing does not show any information about the optimizer. Optimizer tracing is managed by a separate component (OPT) at level 4 only, and is not designed for customer use. |
Example 1-8 SQL trace
In this example, we execute ttTraceMon to do a SQL trace at level 4 on the demo database. We direct the output from the SQL trace to the SQLtrace.txt file. We then flush the buffer so that the trace does not report past SQL statements.
% ttTraceMon demo Trace monitor; empty line to exit Trace > outfile SQLtrace.txt Trace > level sql 4 Trace > flush
At this point, we execute an application that includes the following SQL statement:
SELECT * FROM departments WHERE department_id = 10;
The trace information is written to the SQLtrace.txt file:
12:19:36.582 269 SQL 2L 3C 29570P Preparing: select * from departments where department_id = 10 12:19:36.583 270 SQL 4L 3C 29570P sbSqlCmdCompile ()(E): (Found already compiled version: refCount:01, bucket:28) cmdType:100, cmdNum:1000146. 12:19:36.583 271 SQL 4L 3C 29570P Opening: select * from departments where department_id = 10; 12:19:36.583 272 SQL 4L 3C 29570P Fetching: select * from departments where department_id = 10; 12:19:36.583 273 SQL 4L 3C 29570P Closing: select * from departments where department_id = 10; 5 records dumped
When the application has completed, we turn off SQL tracing and exit ttTraceMon.
Trace > level sql 0
Trace > {press ENTER – blank line}
API traces are generated for database operations such as connecting to a database, changing a connection attribute, and committing a transaction. Table 1-2 describes the levels for API tracing. Each level with a '+' sign includes the trace information described for that level, plus all levels preceding it.
Table 1-2 API tracing levels
| Level | Output |
|---|---|
|
1 |
All rollback attempts by the subdaemon. This occurs if an application exits abruptly and the subdaemon recovers its connection. |
|
2 |
+ Some low-on-space conditions. |
|
3 |
+ Create, connect, disconnect, checkpoint, backup, and compact operations for the database, as well as commit and rollback for each connection, and a few other operations. |
|
4 |
+ Most other operations conducted at TimesTen's internal API level. It does not show numerous operations on the storage manager and indexes that are done internally. |
|
Note: TimesTen recommends tracing at level 3. |
Example 1-9 API trace
In this example, we execute ttTraceMon to do a API trace at level 3 on the demo database. The output from the API trace is written to the APItrace.txt file. Before saving the API trace to the buffer, we use the flush command to empty the buffer.
% ttTraceMon demo Trace monitor; empty line to exit Trace> outfile APItrace.txt Trace> level api 3 Trace > flush
At this point, we execute the application. When the application has completed, we turn off API tracing and exit ttTraceMon:
Trace > level api 0
Trace > {press ENTER – blank line}
The contents of APItrace.txt are similar to the sample output shown below. The output shows connection to the database, setting the connection character set, setting the isolation level, and committing a transaction.
11:54:26.796 1016 API 3L 2C 4848P sb_dbConnect()(X) 11:54:26.796 1017 API 3L 2C 4848P sb_dbConnCharsetSet()(E) 11:54:26.796 1018 API 3L 2C 4848P sb_dbConnSetIsoLevel()(E) 11:54:39.795 1019 API 3L 2C 4848P sb_dbConnSetIsoLevel()(E) 11:54:45.253 1020 API 3L 2C 4848P sb_xactCommitQ()(E)
Use the DEADLOCK component to trace the occurrences of all deadlocks for all applications.
Table 1-3 describes the DEADLOCK tracing levels. Each level with a '+' sign includes the trace information described for that level, plus all levels preceding it.
Table 1-3 DEADLOCK tracing levels
| Level | Output |
|---|---|
|
1 |
Logs deadlock cycles as they are discovered. |
|
4, 6 |
+ Provides detail information about how the deadlock is detected. |
Example 1-10 DEADLOCK trace
In this example, we execute ttTraceMon to do a DEADLOCK trace at level 1, which is the default, on myDSN database.
We make two connections to myDSN. For the first connection, autocommit is on. We create table test and insert two rows. Then, we set autocommit off and update the x1=1 row of table test. Because autocommit is off, the row is not inserted into the table until we commit. A lock is held until we commit or roll back the transaction.
Command> create table test (x1 int unique, y1 int); Command> insert into test values (1,1); 1 row inserted. Command> insert into test values (2,2); 1 row inserted. Command> autocommit 0; Command> update test set y1=y1 where x1=1; 1 row updated.
For the second connection to myDSN, autocommit is set to off. We update the x1=2 row of table test.
Command> autocommit 0; Command> update test set y1=y1 where x1=2;1 row updated.
Now, we create a deadlock situation by executing update statements in both connections for rows that are locked by each other. The first connection executes an update against the row where x1=2.
Command> update test set y1=y1 where x1=2; 6003: Lock request denied because of time-out Details: Tran 2.1 (pid 32750) wants Un lock on rowid BMUFVUAAAAaAAAAETk, table ME.TEST. But tran 3.2 (pid 32731) has it in Xn (request was Xn). Holder SQL (update t1 set y1=y1 where x1=2) The command failed.
The second connection executes an update against the row where x1=1.
Command> update test set y1=y1 where x1=1; 6002: Lock request denied because of deadlock Details: Tran 3.2 (pid 32731) wants Un lock on rowid BMUFVUAAAAaAAAADzk, table ME.TEST. But tran 2.1 (pid 32750) has it in Xn (request was Xn). Holder SQL (update t1 set y1=y1 where x1=1) The command failed.
We use the flush command to empty the buffer.
% ttTraceMon myDSN Trace monitor; empty line to exit Trace> flush
The trace buffer contains the following information showing all level 1 deadlock traces, as evidenced by '1L'.:
Trace> dump 09:50:26.444 13 DEADLOCK 1L 2036C 3484P edge 1: xid 3.2, cid 3, <Row BMUFVUAAAAaAAAADzk,0x8c5 74(574836)> 0 cnt=1 , Tbl 'T1', SQL='update t1 set y1=y1 where x1=1' 09:50:26.455 14 DEADLOCK 1L 2036C 3484P edge 0: xid 2.1, cid 2, <Row BMUFVUAAAAaAAAAETk,0x8c5 74(574836)> 0 cnt=1 , Tbl 'T1', SQL='update t1 set y1=y1 where x1=2' 09:50:26.455 15 DEADLOCK 1L 2036C 3484P Victim: xcb:3.2, SQL='update t1 set y1=y1 where x1=1'
If you want more information, set DEADLOCK tracing to a higher value. For example, the following sets DEADLOCK tracing to level 4 in ttTraceMon:
Trace > level deadlock 4
Use the LOCK component to trace the locking behavior of your application to detect trouble with deadlocks or lock waits. LOCK tracing generates a great deal of volume, so it is important to choose the appropriate level of tracing. Level 3, for example, begins to generate a large number of traces, as traces are written for fairly common events. In addition, the traces themselves may be somewhat hard to read in places. If you cannot discern enough information for your purposes, contact technical support for more information.
Table 1-4 describes the LOCK tracing levels. Each level with a '+' sign includes the trace information described for that level, plus all levels preceding it.
Table 1-4 LOCK tracing levels
| Level | Output |
|---|---|
|
1 |
Deadlock cycles as they are discovered. |
|
2 |
+ Failures to grant locks for any reason. |
|
3 |
+ Lock waits (which may or may not be granted). |
|
4 |
+ All lock grants/releases, some routine calls, and the mechanism of the deadlock detector. |
|
6 |
+ Each step in cycle traversal. |
Example 1-11 LOCK trace
In this example, we execute ttTraceMon to do a LOCK trace at level 4 on myDSN database.
We make two connections to myDSN. For the first connection, we set autocommit on. We create table test and insert three rows. We create a materialized view using table test.
We turn on tracing at level 4 and use the flush command to empty the buffer.
% ttTraceMon myDSN Trace monitor; empty line to exit Trace> level lock 4 Trace> flush
For the second connection to myDSN, we set autocommit off. We insert a row into table test. Because autocommit is off, the row is not inserted into the table until we commit. A lock is held until we commit or roll back the transaction.
If we use the dump command to display the contents of the trace buffer, we see that there are no records in the trace buffer:
Trace> dump 0 records dumped
From the first connection, we try to drop the materialized view. We cannot drop the view because there is a transaction that has not been committed or rolled back:
Command> drop materialized view v; 6003: Lock request denied because of time-out Details: Tran 3.71 (pid 24524) wants Sn lock on table TTUSER.TEST. But tran 1.42 (pid 24263) has it in IXn (request was IXn). Holder SQL (insert into test values (100);) The command failed.
The trace buffer contains the following information:
Trace> dump 20:09:04.789 174759 LOCK 3L 3C 24524P ENQ: xcb:00003 <Tbl 0x9b894,0x0> 0+Sn=>SL activity 0 Sn cnt=0; Holder xcb:00001 IXn 20:09:04.789 174760 LOCK 3L 3C 24524P Connection 3 scheduled for sleep 20:09:04.789 174761 LOCK 3L 3C 24524P Connection 3 sleeping 20:09:14.871 174762 LOCK 3L 2047C 24237P Connection 3 timed out 20:09:14.871 174763 LOCK 3L 2047C 24237P Connection 3 woken up 20:09:14.871 174764 LOCK 3L 3C 24524P Connection 3 awake 20:09:14.871 174765 LOCK 2L 3C 24524P ENQ: xcb:00003 <Tbl 0x9b894,0x0> 0+Sn=>TM activity 0 Sn cnt=1; Holder xcb:00001 IXn 7 records dumped
When finished with the trace, we set LOCK tracing back to its default setting (0) and exit ttTraceMon:
Trace > level lock 0
Trace > {press ENTER – blank line}
It may be useful to trace the ERR component. For example, an ERR trace at level 4 shows all of the error messages that are pushed in the TimesTen direct driver (not all errors are output to the user because they are handled internally). ERR tracing at level 1 is the default. No output is written for ERR tracing at level 2 and 3.
Table 1-5 describes ERR tracing levels. Each level with a '+' sign includes the trace information described for that level, plus all levels preceding it.
Table 1-5 ERR tracing levels
| Level | Output |
|---|---|
|
1 (set by default) |
Fatal errors |
|
4 |
+ All other error messages, many of which are handled internally by TimesTen. |
Example 1-12 ERR trace
In this example, we execute ttTraceMon to do a ERR trace at level 4 on myDSN database.
First we create a table:
Command> create table test (id tt_integer);
Next we turn on tracing at level 4. Rather than direct the trace output to a file as in the previous examples, we read it directly from the trace buffer. Before saving the ERR trace to the buffer, we use the flush command to empty the buffer.
% ttTraceMon myDSN Trace monitor; empty line to exit Trace> level err 4 Trace> flush
Now we execute a SQL script with three errors in it. The errors are:
Creating a table with the same name as an existing table
Using incorrect syntax to insert values into the table
Inserting CHAR data into a TT_INTEGER column
Command> create table test (id tt_integer);
2207: Table TEST already exists
The command failed.
Command> insert into test values 'abcd');
1001: Syntax error in SQL statement before or at: "'abcd'", character position:
25
insert into test values 'abcd');
^^^^^^
The command failed.
Command> insert into test values ('abcd');
2609: Incompatible types found in expression
The command failed.
The trace information is written to the trace buffer. We display it by using the dump command.
Trace> dump
19:28:40.465 174227 ERR 4L 1C 24263P TT2207: Table TEST already exists
-- file "eeDDL.c", lineno 2930, procedure "sbEeCrDtblEval()"
19:28:51.399 174228 ERR 4L 1C 24263P TT1001: Syntax error in SQL
statement before or at: "'abcd'", character position: 25
insert into test values 'abcd');
^^^^^^
-- file "ptSqlY.y", lineno 6273, procedure "reserved_word_or_syntax_error"
19:29:00.725 174229 ERR 4L 1C 24263P TT2609: Incompatible types found
in expression -- file "saCanon.c", lineno 12618, procedure "sbPtAdjustType()"
3 records dumped
Set ERR tracing back to its default setting (1) and exit ttTraceMon:
Trace > level err 1
Trace > {press ENTER – blank line}
Use the ttTraceMon utility to obtain the following information:
When aging starts and ends
How many rows have been deleted by the aging subdaemon
See "Implementing aging in your tables" in the Oracle TimesTen In-Memory Database Operations Guide.
Table 1-6 describes the AGING tracing levels. Each level with a '+' sign includes the trace information described for that level, plus all levels preceding it.
Table 1-6 AGING tracing levels
| Level | Description |
|---|---|
|
1 |
Displays messages about the following events:
|
|
2 |
+ Displays messages about the following events for each table:
|
|
3 |
+ Detailed report on how many rows were deleted during each aging cycle. |
|
4 |
+ Message every time the aging subdaemon wakes up. |
Example 1-13 AGING trace
In this example, we execute ttTraceMon to do an AGING trace on myDSN database. The database contains TTUSER.MYTAB table, which has a time-based aging policy. The table is described as follows:
Command> describe TTUSER.MYTAB;
Table TTUSER.MYTAB:
Columns:
*ID TT_INTEGER NOT NULL
TS TIMESTAMP (6) NOT NULL
Aging use TS lifetime 3 minutes cycle 1 minute on
1 table found.
(primary key columns are indicated with *)
The table contains the following rows before the aging cycle begins:
Command> select * from TTUSER.MYTAB; < 1, 2007-03-21 12:54:06.000000 > < 3, 2010-03-17 08:00:00.000000 > < 4, 2007-03-21 12:59:40.000000 > < 5, 2007-03-21 13:00:10.000000 > < 6, 2007-03-21 13:01:22.000000 > 5 rows found.
We execute ttTraceMon to do an AGING trace at level 3. Rather than direct the trace output to a file, we read it directly from the trace buffer. Before saving the AGING trace to the buffer, we use the flush command to empty the buffer.
% ttTraceMon myDSN Trace monitor; empty line to exit Trace> level aging 3 Trace> flush
Display the trace information in the buffer by using the dump command.
Trace> dump 13:16:56.802 1247 AGING 1L 2045C 17373P Entering sbAgingTB(): curTime=78 13:16:56.803 1248 AGING 2L 2045C 17373P Entering sbAgingOneTable(): curTime=78, ltblid= 637140 13:16:56.804 1249 AGING 3L 2045C 17373P curTime=78, 4 deleted, 1 remaining, tbl = TTUSER.MYTAB 13:16:56.804 1250 AGING 2L 2045C 17373P Exiting sbAgingOneTable(): curTime=78, reason = 'no more rows', 4 deleted, 1 remaining, tbl = TTUSER.MYTAB 13:16:56.804 1251 AGING 1L 2045C 17373P Exiting sbAgingTB(): curTime=78 5 records dumped
We set AGING tracing back to its default setting (0) and exit ttTraceMon:
Trace > level aging 0
Trace > {press ENTER – blank line}
Use the ttTraceMon utility to obtain information about the progress of autorefresh operations for cache groups with the AUTOREFRESH cache group attribute.
See "AUTOREFRESH cache group attribute" in the Oracle In-Memory Database Cache User's Guide.
Table 1-7 describes AUTOREFRESH tracing levels. Each level with a '+' sign includes the trace information described for that level, plus all levels preceding it.
Table 1-7 AUTOREFRESH tracing levels
| Level | Description |
|---|---|
|
1 |
Autorefresh summary for the interval:
Note: Times and information about root table rows are reported for full autorefresh. |
|
2 |
+ Autorefresh summary at the cache group level:
Note: Times and information about root table rows are reported for full autorefresh. |
|
3 |
+ Autorefresh summary at the table level:
|
|
4 |
+ Autorefresh details for each table:
|
Example 1-14 AUTOREFRESH trace
In this example, we use the ttTraceMon utility to trace autorefresh operations on the cgDSN database. When we set the trace level to 1, we see information that is similar to the output of the ttCacheAutorefreshStatsGet built-in procedure.
% tttracemon cgDSN Trace monitor; empty line to exit Trace> level autorefresh 1 Trace> dump 08:56:57.445 19398 AUTOREFRESH 1L 5C 32246P Autorefresh number 1415 started for interval 60000 08:56:57.883 19419 AUTOREFRESH 1L 5C 32246P Duration For Interval 60000ms: 420 08:56:57.883 19420 AUTOREFRESH 1L 5C 32246P Num Rows For Interval 60000ms: 0 08:56:57.883 19421 AUTOREFRESH 1L 5C 32246P Num Root Rows For Interval 60000ms: 0 08:56:57.883 19422 AUTOREFRESH 1L 5C 32246P Cumulative Rows for Interval 60000ms: 11587 08:56:57.883 19423 AUTOREFRESH 1L 5C 32246P Cumulative Root Rows for Interval 60000ms: 1697 08:56:57.883 19424 AUTOREFRESH 1L 5C 32246P Autorefresh number 1415 ended for interval 60000ms successfully. 7 records dumped
Tracing at level 4 produces additional information about autorefresh operation 1415. Information about autorefresh is provided for the testuser.readcache cache group, the testuser.readtab root table and the autorefresh interval.
Trace> level autorefresh 4 Trace> dump 08:56:57.445 19398 AUTOREFRESH 1L 5C 32246P Autorefresh number 1415 started for interval 60000 08:56:57.471 19399 AUTOREFRESH 2L 5C 32246P Autorefresh started for cachegroup TESTUSER.READCACHE 08:56:57.471 19400 AUTOREFRESH 3L 5C 32246P Incremental autorefresh started for table TESTUSER.READTAB 08:56:57.471 19401 AUTOREFRESH 4L 5C 32246P Autorefresh Query: SELECT L."COL_10", X."COL_20", X.ft$NotDelete, Z.rowid FROM (SELECT DISTINCT "COL_10" FROM "TESTUSER"."TT_06_454854_L" WHERE logseq >:logseq AND ft_cacheGroup <> 100000000000*1844259679+-299200618) L,(SELECT "TESTUSER"."READTAB"."COL_10", "TESTUSER"."READTAB"."COL_20", 1 AS ft$NotDelete FROM "TESTUSER"."READTAB", "TESTUSER"."T1" WHERE "TESTUSER"."READTAB"."COL_10" = "TESTUSER"."T1"."COL_10") X, "TESTUSER"."READTAB" Z WHERE L ."COL_10" = X."COL_10" (+) AND X."COL_10" = Z."COL_10" (+), logseq: 7 08:56:57.870 19402 AUTOREFRESH 3L 5C 32246P Duration for table TESTUSER.READTAB: 70 08:56:57.870 19403 AUTOREFRESH 3L 5C 32246P Num Rows for table TESTUSER.READTAB: 1 08:56:57.870 19404 AUTOREFRESH 3L 5C 32246P Cumulative rows for table TESTUSER.READTAB: 1559 08:56:57.870 19405 AUTOREFRESH 4L 5C 32246P Autorefresh Query Execute duration for table TESTUSER.READTAB: 60 08:56:57.870 19406 AUTOREFRESH 4L 5C 32246P Autorefresh Query Fetch duration for table TESTUSER.READTAB: 0 08:56:57.870 19407 AUTOREFRESH 4L 5C 32246P Autorefresh Query Apply duration for table TESTUSER.READTAB: 0 08:56:57.870 19408 AUTOREFRESH 4L 5C 32246P Max logseq applied for table TESTUSER.READTAB: 8 08:56:57.870 19409 AUTOREFRESH 4L 5C 32246P Autorefresh Query Execute duration for 7 child(ren) table(s): 32 08:56:57.870 19410 AUTOREFRESH 4L 5C 32246P Autorefresh Query Fetch duration for 7 child(ren) table(s): 0 08:56:57.870 19411 AUTOREFRESH 4L 5C 32246P Autorefresh Query Apply duration for 7 child(ren) table(s): 0 08:56:57.870 19412 AUTOREFRESH 3L 5C 32246P Incremental autorefresh ended for table TESTUSER.READTABW( 08:56:57.872 19413 AUTOREFRESH 2L 5C 32246P Duration For Cache Group TESTUSER.READCACHE: 1020 08:56:57.872 19414 AUTOREFRESH 2L 5C 32246P Num Rows For Cache Group TESTUSER.READCACHE: 1 08:56:57.872 19415 AUTOREFRESH 2L 5C 32246P Num Root Rows For Cache Group TESTUSER.READCACHE: 0 08:56:57.872 19416 AUTOREFRESH 2L 5C 32246P Cumulative Rows for Cache Group TESTUSER.READCACHE: 11776 08:56:57.872 19417 AUTOREFRESH 2L 5C 32246P Cumulative Root Rows for Cache Group TESTUSER.READCACHE: 1697 08:56:57.872 19418 AUTOREFRESH 2L 5C 32246P Autorefresh ended for cache group TESTUSER.READCACHE 08:56:57.883 19419 AUTOREFRESH 1L 5C 32246P Duration For Interval 60000ms: 420 08:56:57.883 19420 AUTOREFRESH 1L 5C 32246P Num Rows For Interval 60000ms: 0 08:56:57.883 19421 AUTOREFRESH 1L 5C 32246P Num Root Rows For Interval 60000ms: 0 08:56:57.883 19422 AUTOREFRESH 1L 5C 32246P Cumulative Rows for Interval 60000ms: 11587 08:56:57.883 19423 AUTOREFRESH 1L 5C 32246P Cumulative Root Rows for Interval 60000ms: 1697 08:56:57.883 19424 AUTOREFRESH 1L 5C 32246P Autorefresh number 1415 ended for interval 60000ms successfully. 27 records dumped
We set AUTOREFRESH tracing back to its default setting (0) and exit ttTraceMon:
Trace > level autorefresh 0
Trace > {press ENTER – blank line}
The ttXactAdmin utility displays ownership, status, log and lock information for each outstanding transaction. You can also use it to show all current connections to a database. The ttXactAdmin utility is useful for troubleshooting problems with replication, XLA, and asynchronous writethrough cache groups.
Example 1-15 Using ttXactAdmin to diagnose a lock timeout
Use ttXactAdmin to diagnose a lock timeout. Consider two connections that are trying to update the same row. The following transaction by Connection 1 is in progress:
UPDATE table1 SET c1 = 2 WHERE c1 = 1;
Connection 2 attempts to make the following update:
UPDATE table1 SET c1 = 3 WHERE c1 = 1;
Connection 2 receives the following error:
6003: Lock request denied because of time-out Details: Tran 2.3 (pid 2880) wants Un lock on rowid 0x00156bbc, table TTUSER.TABLE1. But tran 1.21 (pid 2564) has it in Xn (request was Xn). Holder SQL (update table1 set c1 = 2 where c1 = 1;) The command failed.
The details of the error indicate that transaction 1.21 has a lock on row 0x00156bbc, the row that transaction 2.3 wants to update. ttXactAdmin displays this information in output that pertains to actions in the entire database:
$ ttXactAdmin myDSN
2011-03-07 12:57:41.237
c:\datastore\myDSN
TimesTen Release 11.2.2.0.0
Outstanding locks
PID Context TransID TransStatus Resource ResourceID Mode Name
Program File Name: ttIsql
2564 0xeeb9a8 1.21 Active Database 0x01312d00 IX
Row 0x00156bbc Xn TTUSER.TABLE1
Table 1910868 IXn TTUSER.TABLE1
Program File Name: ttIsql
2880 0xeeb9a8 2.3 Active Database 0x01312d00 IX
Table 1910868 IXn TTUSER.TABLE1
Command 19972120 S
Awaiting locks
PID Context TransID Resource ResourceID RMode HolderTransID HMode Name
2880 0xeeb9a8 2.3 Row 0x00156bbc Un 1.21 Xn TTUSER.TABLE1
2 outstanding transactions found
See "ttXactAdmin" in the Oracle TimesTen In-Memory Database Reference.
On Windows, use the ODBC trace facility to verify the sequence and content of your commands. The ODBC trace facility works only if you have linked your application with the ODBC Driver Manager. Enable tracing by double-clicking ODBC in the Control Panel. This opens the ODBC Data Source Administrator. Choose the Tracing tab.
On UNIX platforms, ODBC tracing is available only when using a driver manager. To turn on tracing, set the Trace and TraceFile attributes.
Network management software uses SNMP (Simple Network Management Protocol) to query or control the state of network devices such as routers and switches. These devices can generate alerts called traps to inform the network management systems of problems.
TimesTen sends SNMP traps for particular critical events to help facilitate user recovery mechanisms. These events are also recorded in the support log. Exposing them through SNMP traps enables network management software to take immediate action.
How to configure TimesTen to generate SNMP traps as well as how to receive the traps is described in "Diagnostics through SNMP Traps" in the Oracle TimesTen In-Memory Database Error Messages and SNMP Traps.
Each TimesTen database contains a group of system tables that store metadata about the current state of the database. The system tables are described in "System Tables" in the Oracle TimesTen In-Memory Database System Tables and Views Reference.
|
Note: You can executeSELECT statements on a system table, but you cannot execute a statement such as INSERT, UPDATE or DELETE on these tables. |
Of particular interest when troubleshooting is the SYS.MONITOR table, which contains statistics about certain events that have occurred since the first connection to the database. For example, the SYS.MONITOR table contains information about the number of connections to the database; the number of checkpoints taken; the size of the database; and the amount of memory currently in use. Check the contents of the SYS.MONITOR table by executing SELECT statements on the columns or by using the ttIsql monitor command. For an example of how to use the ttIsql monitor command, see "Using the ttIsql Utility" in the Oracle TimesTen In-Memory Database Operations Guide.
The SYS.MONITOR table is useful for troubleshooting performance problems. See "Reading query plan from the PLAN table" in the Oracle TimesTen In-Memory Database Operations Guide for details. Check the contents of the SYS.MONITOR table by executing SELECT statements on the columns or by using the ttIsql showplan command, as described in "Viewing and changing query optimizer plans" in the Oracle TimesTen In-Memory Database Operations Guide.
The query optimizer is an important tool for performance tuning.
For details about using the query optimizer, see:
"The TimesTen Query Optimizer" in the Oracle TimesTen In-Memory Database Operations Guide
"Viewing and changing query optimizer plans" in the Oracle TimesTen In-Memory Database Operations Guide
If you find that a given query runs more slowly than expected, confirm that the query optimizer has the latest statistics for the tables in your query, as described in "Update query optimizer statistics". If, after updating your statistics, your query still runs too slowly, it is possible that the TimesTen optimizer is not choosing the optimal query plan to answer that query. Under these circumstances, you can adjust how the optimizer generates a plan by using the ttOpt procedures described in "Modifying plan generation" in the Oracle TimesTen In-Memory Database Operations Guide.
This chapter includes the following topics:
The default ODBC Data Source Administrator on 64-bit Windows does not show TimesTen 32-bit drivers and DSNs. If Windows is installed in the default location (C:\WINDOWS), use C:\WINDOWS\SysWOW64\odbcad32.exe for the ODBC Data Source Administrator when you are installing 32-bit TimesTen on a 64-bit Windows machine.
In rare situations, after upgrading a database from TimesTen 6.0, you may find that you need to downgrade a TimesTen 7.0 or later database back to TimesTen 6.0 after the data types are already converted to Oracle types. However, the ttMigrate utility for TimesTen 6.0 does not understand Oracle data types, and this can lead to problems when downgrading databases from TimesTen 7.0 or later. To avoid any pitfalls in the downgrade process, you should convert the Oracle data types back to TimesTen types using TimesTen 7.0 or later first, and only then downgrade the database to TimesTen 6.0, using the following steps:
Create a migration file using TimesTen 7.0 or later ttMigrate.
ttMigrate -c datastore datastore.migrate
Destroy the database using TimesTen 7.0 or later ttDestroy.
ttDestroy datastore
Convert the data types to TimesTen types using TimesTen 7.0 or later ttMigrate.
ttMigrate -r -noRepUpgrade -convertTypesToTT datastore datastore.migrate
Create a new migration file using TimesTen 7.0 or later ttMigrate.
ttMigrate -c datastore datastore.migrate
Destroy the database using TimesTen 7.0 or later ttDestroy.
ttDestroy datastore
In another terminal, with the environment set correctly for TimesTen 6.0, restore the database as a TimesTen 6.0 database using TimesTen 6.0 ttMigrate.
ttMigrate -r datastore datastore.migrate
|
Note: Before restoring the database with TimesTen 6.0ttMigrate, you must modify the DSN attributes appropriately for using with TimesTen 6.0. |
The following sections in this chapter describe how to troubleshoot some of the problems you may encounter when replicating databases:
This section describes what to check if you are unable to use CREATE REPLICATION to create a replication scheme.
| Possible cause | What to do |
|---|---|
You do not have ADMIN privilege | You must have ADMIN privilege to use the CREATE REPLICATION or DROP REPLICATION statements. |
| Incorrect database name, host name, or element name. |
|
| The local host is not part of the replication scheme. | Create the replication scheme on a host that will be part of the replication scheme. |
Replication tables defined in the CREATE REPLICATION statement do not exist. | The name, owner, and column definitions of the tables participating in the replication scheme must be identical on both the master and subscriber databases. Use CREATE TABLE to create tables on the database, or use the ttRepAdmin -duplicate utility or the ttRepDuplicateEx C function to duplicate the entire database to be replicated. |
| Other problems | Review the procedures and requirements described in "Defining Replication Schemes" in the Oracle TimesTen In-Memory Database Replication Guide. |
This section describes what to check if you are unable to use ALTER REPLICATION to alter a replication scheme.
| Possible cause | What to do |
|---|---|
You do not have ADMIN privilege | You must have ADMIN privilege to use the ALTER REPLICATION statement. |
| Replication agent in Start state | Most ALTER REPLICATION operations are supported only when the replication agent is stopped (ttAdmin -repStop). Stop the replication agents on both master and subscriber databases, alter the replication scheme on both master and subscriber databases, then restart both replication agents. |
| Incorrect database name, host name, or element name |
|
Replication table defined in the ALTER REPLICATION statement does not exist | Use CREATE TABLE to create a table on the database. |
| Other problems | Review the procedures and requirements described in "Altering Replication" in the Oracle TimesTen In-Memory Database Replication Guide. |
This section describes what to check if you are unable to start or stop a replication agent.
| Possible cause | What to do |
|---|---|
You do not have ADMIN privileges | You must have ADMIN privileges to use the ttAdmin utility or the ttRepStart or ttRepStop procedures to start or stop a replication agent. |
| TimesTen daemon not started | Check the state of the TimesTen daemon, as described in "Check the TimesTen user error log". If necessary, start the TimesTen daemon as described in "Working with the Oracle TimesTen Data Manager Daemon" in the Oracle TimesTen In-Memory Database Operations Guide. |
| Database does not participate in a replication scheme. | If a database does not participate in a replication scheme, attempts to start a replication agent for that database will fail. Use CREATE REPLICATION to create a replication scheme for the database. |
TimesTen can send SNMP traps for certain replication events to enable network management software to take immediate action. TimesTen can send the following traps for replication events:
ttRepAgentExitingTrap
ttRepAgentDiedTrap
ttRepAgentStartingTrap
ttRepCatchupStartTrap
ttRepCatchupStopTrap
ttRepReturnTransitionTrap
ttRepSubscriberFailedTrap
ttRepUpdateFailedTrap
These traps are described in "Diagnostics through SNMP Traps" in the Oracle TimesTen In-Memory Database Error Messages and SNMP Traps.
If you are unable to get replication working between a master and subscriber database, the problem may be one or more of the following:
| Possible cause | See... |
|---|---|
| TimesTen daemon and/or replication agents not running | "Check status of TimesTen daemon and replication agents" |
| Master and subscriber agents not communicating | "Check that replication agents are communicating" |
| Replication not in Start state | "Check replication state" |
| Error in replication scheme | "Check replication scheme configuration" |
| Inconsistent owner names for replication scheme and tables | "Check owner names" |
| Inconsistent replication tables | "Check consistency between replicated tables" |
Use the ttStatus utility to confirm the main TimesTen daemon is running and the replication agents are started for all of your master and subscriber databases. The output from a simple replication scheme using a single master and subscriber database should look like that shown in Example 5-1.
If the TimesTen daemon is running, but the replication agents are not, the output looks like that shown in Example 5-2. In this case, start the replication agents as described in "Starting and stopping the replication agents" in the Oracle TimesTen In-Memory Database Replication Guide.
If neither the TimesTen daemon or replication agents are running, the output looks like that shown in Example 5-3. In this case, confirm you have correctly installed TimesTen and the Data Manager service is started, as described in "TimesTen Installation" in the Oracle TimesTen In-Memory Database Installation Guide.
Example 5-1 ttStatus output for one master and one subscriber
C:\>ttStatus TimesTen status report as of Mon Aug 6 22:07:53 2012 Daemon pid 5088 port 17000 instance MYINSTANCE TimesTen server pid 4344 started on port 17002 ------------------------------------------------------------------------ Data store c:\temp\subscriber1ds There are 12 connections to the data store Data store is in shared mode Shared Memory KEY Global\DBI45b9471c.2.SHM.2 HANDLE 0x280 Type PID Context Connection Name ConnID Process 1244 0x00d08fb0 subscriber1ds 1 Replication 4548 0x00aed2f8 LOGFORCE 4 Replication 4548 0x00b03470 TRANSMITTER 5 Replication 4548 0x00b725a8 RECEIVER 6 Replication 4548 0x00b82808 REPHOLD 2 Replication 4548 0x00b98980 REPLISTENER 3 Subdaemon 2752 0x00526768 Worker 2042 Subdaemon 2752 0x0072a758 Flusher 2043 Subdaemon 2752 0x007308c0 Checkpoint 2044 Subdaemon 2752 0x00736a28 HistGC 2046 Subdaemon 2752 0x067f02f8 Aging 2045 Subdaemon 2752 0x068364a0 Monitor 2047 Replication policy : Manual Replication agent is running. Cache agent policy : Manual ------------------------------------------------------------------------ Data store c:\temp\masterds There are 12 connections to the data store Data store is in shared mode Shared Memory KEY Global\DBI45b945d0.0.SHM.6 HANDLE 0x2bc Type PID Context Connection Name ConnID Process 5880 0x00d09008 masterds 1 Replication 3728 0x00aed570 LOGFORCE 4 Replication 3728 0x00b036e8 TRANSMITTER 5 Replication 3728 0x00b168b8 REPHOLD 3 Replication 3728 0x00b1ca20 REPLISTENER 2 Replication 3728 0x00b22b88 RECEIVER 6 Subdaemon 3220 0x00526768 Worker 2042 Subdaemon 3220 0x0072e768 Flusher 2043 Subdaemon 3220 0x007348d0 Checkpoint 2044 Subdaemon 3220 0x067b0068 Aging 2045 Subdaemon 3220 0x067c0040 Monitor 2047 Subdaemon 3220 0x068404c8 HistGC 2046 Replication policy : Manual Replication agent is running. Cache agent policy : Manual ------------------------------------------------------------------------ Data store c:\temp\demo There are no connections to the data store Replication policy : Manual Cache agent policy : Manual ------------------------------------------------------------------------ End of report
Example 5-2 Replication agent is not running
> ttStatus TimesTen status report as of Mon Aug 6 22:07:53 2012 Daemon pid 3396 port 15000 instance MYINSTANCE TimesTen server pid 3436 started on port 15002 ----------------------------------------------------------------- Data store c:\temp\subscriberds There are no connections to the data store cache agent restart policy: manual ----------------------------------------------------------------- Data store c:\temp\masterds There are no connections to the data store cache agent restart policy: manual ----------------------------------------------------------------- End of report
Use ttRepAdmin -receiver -list to see that the replication agents are communicating with each other. If the masterds database is replicating to subscriberds, the output should look similar to the following:
Example 5-4 Check that the replication agents are communicating
> ttRepAdmin -receiver -list masterDSN Peer name Host name Port State Proto ---------------- ------------------------ ------ ------- ----- SUBSCRIBERDS MYHOST Auto Start 10 Last Msg Sent Last Msg Recv Latency TPS RecordsPS Logs ------------- ------------- ------- ------- --------- ---- 0:01:12 - 19.41 5 52 2
Use the ttReplicationStatus procedure to check the state of the subscriber database with respect to its master. If the subscriber is in the Stop, Pause, or Failed state, use the ttReplicationStatus procedure to reset the subscriber state to Start, as described in "Setting the replication state of subscribers" in the Oracle TimesTen In-Memory Database Replication Guide.
Example 5-5 Obtain status of the subscriber database from the master database
Use ttReplicationStatus to obtain the status of the subscriberds database from its master database, masterDSN, enter:
> ttIsql masterDSN
Command> CALL ttReplicationStatus ('subscriberds');
< SUBSCRIBERDS, MYHOST, 0, pause, 1, 10, REPSCHEME, REPL >
1 row found.
To reset state to Start call the ttRepSubscriberStateSet procedure:
Command> CALL ttRepSubscriberStateSet('REPSCHEME', 'REPL', 'SUBSCRIBERDS', 'MYHOST', 0)
Command> CALL ttReplicationStatus ('subscriberds');
< SUBSCRIBERDS, MYHOST, 0, start, 1, 152959, REPSCHEME, REPL >
1 row found.
This section describes some procedures you can use to confirm the correct configuration of the various components in your replicated system. The basic procedure categories are:
Use ttRepAdmin -showconfig to confirm the configuration of your replication scheme.
What to look for:
Are all of the subscriber agents started and reported to be in the Start state? If not, reset the agents to the Start state. See "Setting the replication state of subscribers" in the Oracle TimesTen In-Memory Database Replication Guide.
Do the reported Peer names match the names given in the DataStore attributes in the DSN definitions for the replicated databases? Replication does not work if you specified the names given for the Data Source Name attributes.
Is there anything under List of subscribers? If not, confirm the database names you specified in the DSN definition are consistent with those you specified in your replication scheme configuration file.
Are the Host names correct? If in doubt, see "Check host names".
Are the correct table names displayed under Table details? If not, correct the table names in your replication scheme configuration file.
Example 5-6 Confirm the configuration of the replication scheme
> ttRepAdmin -showconfig masterDSN Self host "MYHOST", port auto, name "MASTERDS", LSN 4/2970276, timeout 120, threshold 0 List of subscribers ----------------- Peer name Host name Port State Proto ---------------- ------------------------ ------ ------- ----- SUBSCRIBERDS MYHOST Auto Start 10 Last Msg Sent Last Msg Recv Latency TPS RecordsPS Logs ------------- ------------- ------- ------- --------- ---- 0:01:12 - 19.41 5 52 2 List of tables and subscriptions -------------------------------- Table details ------------- Table : REPL.TAB Master Name Subscriber Name ----------- ------------- MASTERDS SUBSCRIBERDS
Check the TTREP.TTSTORES table to confirm that replication associates the replication scheme with the local database.
Example 5-7 Confirm that the replication scheme is associated with the local database
Connect to the database and enter:
SELECT * FROM ttrep.ttstores WHERE is_local_store <> 0x0;
Command> select * from ttrep.ttstores where is_local_store <> 0x0; < -5193371075573733683, MYHOST, MASTERDS, 01, 0, 0, 4, 0 > 1 row found.
There should be exactly one row returned. If more than one row is returned, contact technical support. If no rows are returned, then none of the hosts returned by the following statement is perceived to be a local system by TimesTen replication:
SELECT DISTINCT host_name FROM ttrep.ttstores;
It may also be that none of the database names specified in your replication scheme match those specified in your DSN descriptions.
Some hosts or IP addresses specified in a replication scheme cannot be resolved by the replication agent because:
Host names or IP addresses specified in the replication scheme are wrong or misspelled.
Host names or IP addresses cannot be resolved or found by DNS or in the /etc/hosts file
Entries in the /etc/hosts file are incorrectly ordered in appearance. This error is most common when multiple NICs are used. You must have root privilege to make changes to the /etc/hosts files.
See "Configuring host IP addresses" in the Oracle TimesTen In-Memory Database Replication Guide for details on how to configure DNS and /etc/hosts files for host machines used for replication.
To check if a host name in the replication scheme matches the host name of the local machine, write an application to perform these tasks:
Use a gethostname OS function call to determine the host name of the running host.
Call gethostbyname with the output from Step 1.
Call gethostbyname with the host name specified in the replication scheme.
Compare output of Step 2 and Step 3. If there is a match, then the running host is involved in replication. Otherwise, it is not involved in replication.
As described in "Table requirements and restrictions for replication schemes" and "Owner of the replication scheme and replicated objects" in the Oracle TimesTen In-Memory Database Replication Guide, the owner names of your replication scheme and your replicated tables must be consistent across all participating databases.
Check the owner name assigned to your replication scheme by calling the ttIsql repschemes command or by listing the contents of the TTREP.REPLICATIONS table.
Example 5-8 shows that the replication scheme name, REPSCHEME, has a consistent owner name (REPL) in the databases on both SYSTEM1 and SYSTEM2. Example 5-9 shows the scheme name with inconsistent owner names. This can occur if you omit the owner name from the replication scheme definition and the system uses the Id of the replication scheme creator.
Example 5-8 Consistent owner names for replication scheme
On SYSTEM1:
> ttIsql masterDSN Command> select * from ttrep.replications; < REPSCHEME , REPL , C, 0, 0, -1 > 1 row found.
On SYSTEM2:
> ttIsql -connStr "dsn=subscriberDSN" Command> select * from ttrep.replications; < REPSCHEME , REPL , C, 0, 0, -1 > 1 row found.
Example 5-9 Inconsistent owner names for replication scheme
On SYSTEM1:
> ttIsql masterDSN Command> select * from ttrep.replications; < REPSCHEME , SYSTEM1 , C, 0, 0, -1 > 1 row found.
On SYSTEM2:
> ttIsql -connStr "dsn=subscriberDSN" Command> select * from ttrep.replications; < REPSCHEME , SYSTEM2 , C, 0, 0, -1 > 1 row found.
Check the owner names assigned to the tables in each database by using the ttIsql tables command.
Example 5-10 Consistent table owner names
This example shows that the TAB table has a consistent owner name (REPL) in the databases on both SYSTEM1 and SYSTEM2.
| Output for SYSTEM1 | Output for SYSTEM2 |
|---|---|
SYS.CACHE_GROUP |
SYS.CACHE_GROUP |
SYS.COLUMNS |
SYS.COLUMNS |
SYS.COL_STATS |
SYS.COL_STATS |
SYS.INDEXES |
SYS.INDEXES |
SYS.MONITOR |
SYS.MONITOR |
SYS.PLAN |
SYS.PLAN |
SYS.TABLES |
SYS.TABLES |
SYS.TBL_STATS |
SYS.TBL_STATS |
SYS.TRANSACTION_LOG_API |
SYS.TRANSACTION_LOG_API |
|
|
TTREP.REPELEMENTS |
TTREP.REPELEMENTS |
TTREP.REPLICATIONS |
TTREP.REPLICATIONS |
TTREP.REPPEERS |
TTREP.REPPEERS |
TTREP.REPSTORES |
TTREP.REPSTORES |
TTREP.REPSUBSCRIPTIONS |
TTREP.REPSUBSCRIPTIONS |
TTREP.REPTABLES |
TTREP.REPTABLES |
TTREP.TTSTORES |
TTREP.TTSTORES |
Example 5-11 Inconsistent table owner names
This example shows the TAB table with inconsistent owner names, which were automatically assigned for each host.
| Output for SYSTEM1 | Output for SYSTEM2 |
|---|---|
SYS.CACHE_GROUP |
SYS.CACHE_GROUP |
SYS.COLUMNS |
SYS.COLUMNS |
SYS.COL_STATS |
SYS.COL_STATS |
SYS.INDEXES |
SYS.INDEXES |
SYS.MONITOR |
SYS.MONITOR |
SYS.PLAN |
SYS.PLAN |
SYS.TABLES |
SYS.TABLES |
SYS.TBL_STATS |
SYS.TBL_STATS |
SYS.TRANSACTION_LOG_API |
SYS.TRANSACTION_LOG_API |
|
|
TTREP.REPELEMENTS |
TTREP.REPELEMENTS |
TTREP.REPLICATIONS |
TTREP.REPLICATIONS |
TTREP.REPPEERS |
TTREP.REPPEERS |
TTREP.REPSTORES |
TTREP.REPSTORES |
TTREP.REPSUBSCRIPTIONS |
TTREP.REPSUBSCRIPTIONS |
TTREP.REPTABLES |
TTREP.REPTABLES |
TTREP.TTSTORES |
TTREP.TTSTORES |
Replicated tables on both master and subscriber databases must be exactly the same.
Example 5-12 Check consistency between replicated tables
This output from the user error log shows a mismatch on the number of columns for the subscriber table TTUSER.MYDSN.
11:37:58.00 Info: REP: 9430: REP1:transmitter.c(4936): TT16136: Sending definition for table TTUSER.MYDSN (1 column) 11:37:58.00 Info: REP: 9412: REP2:receiver.c(5928): TT16193: Adding definition for table: TTUSER.MYDSN 11:37:58.00 Info: REP: 9412: REP2:meta.c(5580):TTUSER.MYDSN ptn 0: srcoff 0, destoff 0, length 8 11:37:58.00 Info: REP: 9412: REP2:meta.c(5580):TTUSER.MYDSN ptn 1: srcoff 8, destoff 12, length 12 11:37:58.00 Err : REP: 9412: REP2:receiver.c(6203): TT16198: Table definition mismatch on number of columns for table TTUSER.MYDSN. Local definition: 2; transmitting peer: 1 11:37:58.00 Err : REP: 9412: REP2:receiver.c(6380): TT16204: Table TTUSER.MYDSN marked invalid. Will not apply transactions received for it until a valid definition is received 11:37:58.00 Err : REP: 9412: REP2:receiver.c(7200): TT16078: Table definition for ID 637068 is invalid (Original failure 11:37:58 REP2:receiver.c(6203): TT16198: Table definition mismatch on number of columns for table TTUSER.MYDSN. Local definition: 2; transmitting peer: 1) 11:37:58.00 Err : REP: 9412: REP2:receiver.c(5002): TT16187: Transaction 1173958671/2; Error: transient 0, permanent 1
Table summary is in the first heading cell.
| Possible cause | See... |
|---|---|
| Failed subscriber | "Check replication state" |
| Return-receipt timeout period too long | "Check return receipt timeout setting" |
Use the ttReplicationStatus procedure to check state of the subscriber database with respect to its master. If the subscriber is in the Failed state, see "Managing Database Failover and Recovery" in the Oracle TimesTen In-Memory Database Replication Guide for information on how to deal with failed databases.
Use the ttRepSyncGet procedure to check the return receipt timeout setting. A value of -1 indicates the application is to wait until it receives an acknowledgement from the subscriber. Network latency or other issues might delay receipt of the subscriber acknowledgment. You either address these issues or use the ttRepSyncGet procedure to reset the return receipt timeout period.
See "Checking the status of return service transactions" in the Oracle TimesTen In-Memory Database Replication Guide for more information.
Most of this section addresses issues that may impact replication performance. Some issues, such as log buffer too small and reading from the transaction log files on disk, can impact the performance of both replication and XLA applications.
| Possible cause | See... |
|---|---|
| Slow network | "Check network bandwidth" |
Using RETURN RECEIPT | "Check use of return receipt blocking" |
| Inefficient replication scheme | "Check replication configuration" |
| Log buffer too small | "Check size of log buffer" |
| Frequent or inefficient disk writes | "Check durability settings" |
| Reading from transaction log files on disk rather than the log buffer | "Check for reads from transaction log files" |
| High rate of conflicts | "Conflict reporting slows down replication" |
Replication agents typically communicate over some type of network connection. If replicating over a network slower than 10 MB per second (such as common with a 100 Base-T Ethernet typical in a LAN), you must be careful to match the transaction load to the available bandwidth of the network. see "Network bandwidth requirements" in the Oracle TimesTen In-Memory Database Replication Guide for details.
Unless you need receipt confirmation for all your transactions, disable RETURN RECEIPT BLOCKING. If you require receipt confirmation for some transactions, then set RETURN RECEIPT BY REQUEST and call the ttRepSyncSet procedure to enable the return receipt service for specific transactions. See "RETURN RECEIPT BY REQUEST" in the Oracle TimesTen In-Memory Database Replication Guide for details.
|
Note: The performance degradation caused by return-receipt becomes less of an issue when multiple applications (or threads) are updating the database. If you must use return-receipt in a transaction, you can improve the performance of your application by using multiple threads to update the database. Though each thread must block for receipt confirmation, the other threads are free to make updates. |
In addition to return-receipt setting described above, other factors related to the configuration of your replication scheme could impact replication performance. As described in "Making decisions about performance and recovery tradeoffs" in the Oracle TimesTen In-Memory Database Replication Guide, you often have to weigh the ability to efficiently failover and recover a database against replication performance.
For more information about direct replication, see "Direct replication or propagation" in the Oracle TimesTen In-Memory Database Replication Guide.
Setting your log buffer too small may impact replication performance. Instead, Set the LogBufMB DSN attribute to a larger size. For more information on this DSN attribute, see "Setting connection attributes for logging" in the Oracle TimesTen In-Memory Database Replication Guide
You can improve replication performance by setting TRANSMIT NONDURABLE on the replication ELEMENT to eliminate the flush-log-to-disk operation from the replication cycle. See "Setting transmit durability on data store elements" in the Oracle TimesTen In-Memory Database Replication Guide for details.
Enabling the DURABLE COMMIT option in your replication scheme also impacts performance. See "DURABLE COMMIT" in the Oracle TimesTen In-Memory Database Replication Guide for more information.
In some situations a "log reader," such as a master replication agent 'transmitter' thread or a ttXlaNextUpdate call in an XLA application, may not be able to keep up with the update rate of the applications writing to the database. Normally, replication and XLA readers get update records from the log buffer in memory. When the readers fall behind the application update rate, transaction log files can accumulate on the disk until the backlog can be cleared. This forces the readers to read transactions from the transaction log files on disk, which is much slower. Should you detect reads from the transaction log files, you may want to respond by decreasing the rate of application updates to that sustainable by the log readers.
Applications can monitor whether log readers are obtaining update records from transaction log files on disk rather than from the log buffer in memory by tracking the SYS.MONITOR table entry LOG_FS_READS. For example, you can check the value of LOG_FS_READS for the database, MASTERDSN, with the following ttIsql command:
% ttIsql -v1 -e "select log_fs_reads from monitor; quit;" -connStr dsn=MASTERDSN
If the LOG_FS_READS counter is increasing, the log readers are falling behind or clearing out a backlog in the transaction log files.
For more complete monitoring of replication progress, create a simple shell script like the following:
!/bin/sh trap exit 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 DSN=$1 while [ 1 ] ; do date ttRepAdmin -receiver -list -connStr dsn=$DSN echo -n "Log reads from disk: " ttIsql -v1 -e "select log_fs_reads from monitor; quit;" -connStr dsn=$DSN echo ttRepAdmin -bookmark -connStr dsn=$DSN sleep 15 done
Example 5-14 Check the status of the transaction log
For example, you name the above script monitorLog and your replication scheme replicates from the MASTERDSN database to the SUBSCRIBER1DSN database. You can then check the status of the transaction log by entering:
$ monitorLog masterdsn
This generates output similar to the following:
Mon Aug 2 10:44:40 2004 Peer name Host name Port State Proto ---------------- ------------------------ ------ ------- ----- SUBSCRIBER1DSN MYHOST Auto Start 12 Last Msg Sent Last Msg Recv Latency TPS RecordsPS Logs ------------- ------------- ------- ------- --------- ---- 00:00:05 - -1.00 -1 -1 1 Log reads from disk: < 0 > Replication hold LSN ...... 10/2656136 Last written LSN .......... 10/4015824 Last LSN forced to disk ... 10/3970152
The output from the script displays an updated status every 15 seconds until you enter Ctrl-C to exit.
Following the date in the output in Example 5-14 is the name of the subscriber, its host, and so on. Next is latency and rate information, as well as the number of transaction log files being retained on behalf of this subscriber. The specific meaning of each value is described in "Using ttRepAdmin to display subscriber status" in the Oracle TimesTen In-Memory Database Replication Guide. The main interest here is the 'Last Msg Sent' and 'Logs' values. The 'Last Msg Sent' value indicates the elapsed time since the last message was sent by the master to the subscriber and 'Logs' indicates how many transaction log files behind the replication log reader is from the current log insertion point used by the writers (Last written LSN).
Normally the 'Logs' value should be '1', as shown in Example 5-14. A steadily increasing 'Logs' value indicates latency is increasing and eventually log reads are satisfied from disk.
|
Note: If theLogBufMB is larger than the LogFileSize, an increase in the 'Logs' value does not necessarily mean the log readers are reading from the transaction log files. This is because the log manager does not allow more than one log file's worth of data to be outstanding before writing it to the file system. After the log manager writes the data, the data remains in the log buffer to be read directly by the log readers. So, when the LogBufMB is larger than the LogFileSize, the 'Logs" value alone may not be the best measure of whether log readers are reading from memory or from disk. |
The output from the following command displays the number of the transaction log files and the location of the bookmarks set by the log manager.
ttRepAdmin -bookmark -connStr dsn=$DSN
For more information, see "Using ttRepAdmin to display bookmark location" in the Oracle TimesTen In-Memory Database Replication Guide. The difference between the Replication hold LSN and the last written LSN indicates the number of records in the transaction log that have not yet been transmitted to the subscribers. A steady increase in the difference between these values is another indication that replication latency is increasing and log file reads are likely to occur.
Example 5-15 Log reader must read from transaction log files
In this example, assume the LogBufMB is 16MB and the LogFileSize is 8MB. The following output indicates the log reader is approximately 1.8 MB behind the capacity of the log buffer and must read from the transaction log files, 14 and 15.
Peer name Host name Port State Proto ---------------- ------------------------ ------ ------- ----- SUBSCRIBER1DSN MYHOST Auto Start 12 Last Msg Sent Last Msg Recv Latency TPS RecordsPS Logs ------------- ------------- ------- ------- --------- ---- 00:00:03 - -1.00 -1 -1 4 Log reads from disk: <20> Replication hold LSN ...... 14/7007464 Last written LSN .......... 17/465336 Last LSN forced to disk ... 17/456152
This section includes the following topics:
If you try to change the state of a replication receiver when replication has been configured to use a secondary IP address, a misconfiguration of the /etc/hosts file may cause ttRepAdmin to print the following error:
Alter replication with 'ALTER REPLICATION...port 0' failed: TT0907: Unique constraint (REPSTORESIX) violated.
This error is caused by replication not recognizing the local database, which can be confirmed by the following query:
SELECT * FROM ttrep.ttstores WHERE is_local_store <> 0x0;
If this query returns no rows, or returns a row with the main host name of the database set to the result of the hostname command rather than the host you specified, you have encountered a configuration problem with the /etc/hosts file.
To correct the problem, make sure that the special host name you are using is defined in the /etc/hosts file and that there is an IP address in common between your special host name and the result of the hostname command.
For example, if the hostn!ame command returns softswitch and your system has two Ethernet cards with the addresses 10.10.15.136 and 192.168.15.136, the IP addresses defined for softswitch should include both IP addresses.
The following are two possible causes of problems when using ttRepAdmin -duplicate:
If you connected to your new subscriber DSN before running ttRepAdmin -duplicate, the database has already been created. In this situation, -duplicate returns:
Error : Restore not done : The datastore already exists. Unable to restore datastore locally
Confirm the existence of the database by running ttStatus and checking to see if the database is in the returned list. If the new subscriber database exists, destroy it and try ttRepAdmin -duplicate again.
> ttDestroy /tmp/newstore > ttRepAdmin -dsn newstoreDSN -duplicate -name newstore -from masterds -host "server1"
If you have made an error entering the subscriber database name or host name in the replication scheme, you may see something like the following:
Unable to swap datastore locally No receiver NEWSTORE on SERVER2 found to swap with
If you provide an incorrect host name for a subscriber, you may receive the following error:
Problem: ttRepAdmin -duplicate command returns TimesTen error 12080: No subscriber found to swap with.
You also receive information about the subscriber that TimesTen is trying to locate. One common cause is providing an incorrect host name, which must be the exact same name as the host name provided when issuing the CREATE ACTIVE STANDBY PAIR statement. For example, if you created the subscriber with myhost.oracle.com, but only provided myhost in the ttRepAdmin -duplicate, the subscriber will not be found.
|
Note: Ifmyhost is the local host, use the -localhost argument. You typically need to use the -localhost argument if the local host name does not exactly match the host name provided when creating the replication scheme. |
If you have more than one scheme specified in your TTREP.REPLICATIONS table, some ttRepAdmin commands may return the error:
Must specify -scheme to identify which replication scheme to use
To check the names of the replication schemes used by your database, use the ttIsql utility to connect, and enter:
Command> SELECT * from TTREP.REPLICATIONS;
Example 5-16 Two replication schemes assigned to the database
This example shows that two replication schemes, REPSCHEME1 and REPSCHEME2, are assigned to the database associated with subDSN. In this case, it is necessary to use the ttRepAdmin -scheme option.
> ttIsql -connStr "dsn=subDSN" Command> SELECT * from TTREP.REPLICATIONS; < REPSCHEME1 , REPL , C, 0, 0, -1 > < REPSCHEME2 , REPL , C, 0, 0, -1 > 2 rows found. Command> exit > ttRepAdmin -dsn subDSN -receiver -list -scheme REPSCHEME1 Peer name Host name Port State Proto ---------------- ------------------------ ------ ------- ----- SUBSCRIBER1 MYHOST Auto Start 10 Last Msg Sent Last Msg Recv Latency TPS RecordsPS Logs ------------- ------------- ------- ------- --------- ---- 0:01:12 - 19.41 5 52 2
This section includes the following topics:
When attempting to set CHECK CONFLICTS for an element in a CREATE REPLICATION statement, you may encounter an error similar to the following:
8004: Column REPL.TABS.TS cannot be used for replication timestamp checking if in an index or added by ALTER TABLE; and must be binary(8) with NULL values allowed.
In this situation, check:
That the timestamp column in the specified table is a nullable column of type BINARY(8). In the above example, the TS column in the REPL.TAB table should have a type of BINARY(8).
The timestamp column is defined in the original CREATE TABLE statement, rather than added later using ALTER TABLE.
You may receive an error similar to the following:
2208: Column TS does not exist in table.
In this situation, confirm that you have specified the correct name for the timestamp column in the CHECK CONFLICTS clause and that it exists in the specified table.
Also, make sure the timestamp column is not part of a primary key or index.
If you have configured replication to CHECK CONFLICTS, TimesTen sends reports to the local host. You can also configure a report file. See "Diagnostics through SNMP Traps" in the Oracle TimesTen In-Memory Database Error Messages and SNMP Traps.
If there is a large number of conflicts in a short period of time, subscriber performance can slow down because of the reporting requirements. You can use store attributes in the CREATE REPLICATION or ALTER REPLICATION statements to suspend and resume conflict reporting at specified rates of conflict:
CONFLICT REPORTING SUSPEND AT rate
CONFLICT REPORTING RESUME AT rate
Information about conflicts that occur while reporting is suspended cannot be retrieved.
See "Reporting conflicts" in the Oracle TimesTen In-Memory Database Replication Guide.