This chapter describes the TimesTen home page. The home page conveys high level configuration and performance information about your TimesTen database.
To view the home page, make sure you are on the TimesTen target page. For information on navigating to the TimesTen target page, see "Navigating to the TimesTen target page".
From the TimesTen IMDB menu, select Home.
The TimesTen home page displays.
The TimesTen home page consists of five regions each of which has been customized specifically for TimesTen targets.
The five home page regions described in detail include:
This region shows information about your TimesTen target:
This value is taken from the last part of the path to the datastore. For example, if the path to the datastore is
/var/tt/sampledb_1122, the datastore name is
The name of your current TimesTen instance.
The version of your current TimesTen instance.
The name of the host where TimesTen is running.
Oracle Net Service Name
The service name of the Oracle database used for cache. If you have not configured cache, then this value is N/A.
This region shows status information including:
This value can be either Up or Down. The TimesTen Server is the listener process that enables client/server connections to the database.
This value can be either Up, Down, or N/A. If you have not configured a cache environment, then this value is N/A. The Cache Agent is used for read or write caching of data in an Oracle 10g or 11g database.
This value can be either Up, Down, or N/A. If you have not configured a replication scheme, then this value is N/A. The Replication Agent is used to either replicate data between TimesTen databases or to asynchronously write data to an Oracle 10g or 11g database.
The date when the database was loaded into memory.
This region shows configuration information specific to your database. These attributes are first connection attributes and the values are set at first connect. For more information on first connection attributes, see "Connection Attributes" in the Oracle TimesTen In-Memory Database Reference.
Allocated PERM Space
Allocated TEMP Space
Internal log buffer size
PL/SQL memory segment size
The Performance Overview region consists of four subregions. The first three subregions include information represented in graphical format. All graphs are represented against time.
This region uses a line graph to show the number of direct linked connections and client/server connections. These line graphs change according to time in order to show not only the current value but also the values collected in recent metric collections.
The X-Axis represents time. The Y-Axis represents the number of current direct linked connections and the number of client/server connections. These connections do not include subdaemon connections or connections created by the TimesTen plug-in to collect configuration and performance data.
This region uses a line graphs to show permanent and temporary space currently in use. The values are expressed as a percentage of what was configured at database first connect. For information on the configured values, see the Summary, Status, and Configuration regions.
The X-Axis represents time. The Y-Axis represents the percent of permanent space in use and the percent of temporary space in use.
This region uses a graph to show the free space in the file systems where the checkpoint and transaction log files are currently located.
The X-Axis represents time. The Y-Axis represents the free space in the checkpoint file system and the free space in the transaction log file system. If you configured the checkpoint and transaction log files in the same file system and path, the two lines will be on top of each other and you will see one line.
A very low percentage of free disk available may indicate a need to install a larger disk.
This regions shows the Top SQL statements in the SQL command cache expressed in table format. This information is useful in analyzing your queries. It may be useful to sort by the number of executions to see the SQL statements that are most executed. It may also be useful to exclude system SQL commands by clicking in the box to the left of Exclude System.
As you review the top executions, look at the values in the Prepares column. If the SQL query is not prepared, then you should prepare the query. For optimal performance, a SQL statement should be prepared once and executed many times. If the number of prepares for a SQL statement is large then check to see if your application can be enhanced to minimize the number of prepares per SQL statement.In addition, you can click on the text in the Query Text column. When you do this, a Full SQL text dialog opens showing the SQL query. You can copy and paste this SQL query into the worksheet in SQL Developer and review the results from Explain Plan. You can also paste the SQL query into
ttIsql and look at the
showplan for the query. This may give you a better understanding of how and why your queries are performing as they are.
You can also click on the column header to sort the table based on the column. A description of each column follows:
A unique identifier for the SQL command. This number is generated by the TimesTen database.
A counter for the number of executions that took place on this command since it was brought into the command cache.
A counter for the number of prepares for a SQL statement.
A counter of the number of reprepares.
The identifier of the user who created the command.
The SQL text.
This region displays alerts that have exceeded either warning or error thresholds.