Oracle® In-Memory Database Cache User's Guide 11g Release 2 (11.2.2) E21634-08 |
|
|
PDF · Mobi · ePub |
The following sections describe the tasks for setting up the TimesTen and Oracle Database systems before you can start caching Oracle Database data in a TimesTen database:
Configuring your system to cache Oracle Database data in TimesTen
Configuring a TimesTen database to cache Oracle Database data
Testing the connectivity between the TimesTen and Oracle databases
Oracle In-Memory Database Cache supports the following Oracle Database Server releases:
Oracle 11g Release 2 (11.2.0.2.0 or above)
Oracle 11g Release 1 (11.1.0.7.0 or above)
Oracle 10g Release 2 (10.2.0.5.0 or above)
Configure the environment variables for your particular operating system, as described in "Oracle In-Memory Database Cache environment variables for UNIX" or "Oracle In-Memory Database Cache environment variables for Microsoft Windows".
Then, install TimesTen as described in Oracle TimesTen In-Memory Database Installation Guide.
Note:
From a product perspective, "Oracle In-Memory Database Cache" is used interchangeably with "TimesTen" because the Oracle In-Memory Database Cache product option includes the Oracle TimesTen In-Memory Database.TimesTen does not support Oracle Name Server for Windows clients.
The shared library search path environment variable such as LD_LIBRARY_PATH
or SHLIB_PATH
must include the TimesTen_install_dir
/lib
directory.
For more information, see "Shared library path environment variable" in Oracle TimesTen In-Memory Database Installation Guide.
The PATH
environment variable must include the TimesTen_install_dir
/bin
directory.
In the following example, TimesTen is installed in the /timesten/myinstance
directory:
LD_LIBRARY_PATH=/timesten/myinstance/lib PATH=/timesten/myinstance/bin
The PATH
system environment variable must include the following directories:
Oracle_install_dir
\bin
TimesTen_install_dir
\lib
TimesTen_install_dir
\bin
In the following example, Oracle Database is installed in the C:\oracle\ora112
directory and TimesTen is installed in the C:\timesten\myinstance
directory:
PATH=C:\oracle\ora112\bin;C:\timesten\myinstance\lib;C:\timesten\myinstance\bin
The following sections describe the tasks that must be performed on the Oracle database by the sys
user:
Automatically create Oracle Database objects used to manage data caching
Manually create Oracle Database objects used to manage data caching
First, you must create a user timesten
that is to own the Oracle Database tables that store information about cache grids. The SQL*Plus script TimesTen_install_dir
/oraclescripts/initCacheGlobalSchema.sql
creates:
The timesten
user
The Oracle Database tables owned by the timesten
user to store information about cache grids
The TT_CACHE_ADMIN_ROLE
role that defines privileges on these Oracle Database tables
Create or designate a default tablespace for the timesten
user and pass this tablespace as an argument to the initCacheGlobalSchema.sql
script. See "Managing a caching environment with Oracle Database objects" for a list of Oracle Database tables owned by the timesten
user.
Example 3-1 Creating the timesten user and its tables
In the following SQL*Plus example, the default tablespace that is created for the timesten
user is cachetblsp
:
% cd TimesTen_install_dir/oraclescripts % sqlplus sys as sysdba Enter password: password SQL> CREATE TABLESPACE cachetblsp DATAFILE 'datfttuser.dbf' SIZE 100M; SQL> @initCacheGlobalSchema "cachetblsp"
Then, you must create or designate one or more users that is to own Oracle Database tables that are to be cached in a TimesTen database. We refer to these users as the schema users. These may be existing users or new users. The tables to be cached may or may not already exist.
Example 3-2 Creating a schema user
As the sys
user, create a schema user oratt
.
Use SQL*Plus to create the schema user:
SQL> CREATE USER oratt IDENTIFIED BY oracle;
Next, you must create a user that creates, owns, and maintains Oracle Database objects that store information used to manage a specific cache grid and enforce predefined behaviors of particular cache group types. We refer to this user as the cache administration user.
Designate the tablespace that was created for the timesten
user as the default tablespace for the cache administration user. This user creates tables in this tablespace that are used to store information about the cache grid and its cache groups. Other Oracle Database objects (such change log tables, replication metadata tables, and triggers) are used to enforce the predefined behaviors of autorefresh cache groups and AWT cache groups are created in the same tablespace.
See "Managing a caching environment with Oracle Database objects" for a list of Oracle Database tables and triggers owned by the cache administration user.
Note:
An autorefresh cache group refers to a read-only cache group or a user managed cache group that uses theAUTOREFRESH MODE INCREMENTAL
cache group attribute.Example 3-3 Creating the cache administration user
As the sys
user, create a cache administration user cacheuser
. In the following example, the default tablespace for the cacheuser
user is cachetblsp
.
Use SQL*Plus to create the cache administration user:
SQL> CREATE USER cacheuser IDENTIFIED BY oracle 2 DEFAULT TABLESPACE cachetblsp QUOTA UNLIMITED ON cachetblsp;
The privileges that the Oracle Database users require depends on the types of cache groups you create and the operations that you perform on the cache groups. The privileges required for the Oracle Database cache administration user and the TimesTen cache manager user for each cache operation are listed in Table 3-1.
Table 3-1 Oracle Database and TimesTen user privileges required for cache operations
Cache operation | Privileges required for Oracle Database cache administration userFoot 1 | Privileges required for TimesTen cache manager userFoot 2 |
---|---|---|
Initialize the cache administration user. The |
Permissions for the default tablespace |
|
Set the cache administration user name and password
|
|
|
Get the cache administration user name
|
None |
|
Create a cache grid
|
|
|
Associate a TimesTen database with a cache grid
|
|
|
Attach a TimesTen database to a cache grid
|
|
|
Detach a TimesTen database from a cache grid
|
|
|
Detach a list of nodes from a cache grid
|
|
|
Destroy a cache grid
|
|
|
Start the cache agent
|
|
|
Stop the cache agent
|
None |
|
Set a cache agent start policy
|
|
|
Return the cache agent start policy setting
|
|
None |
Start the replication agent
|
None |
|
Stop the replication agent
|
None |
|
Set a replication agent start policy
|
None |
|
when the cache group created is an AWT cache group |
|
|
Duplicate the database with |
|
|
|
||
|
|
|
|
||
|
|
|
(see variants in following rows) |
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
None |
|
|
|
|
Synchronous writethrough or propagate |
|
|
Asynchronous writethrough |
|
|
Asynchronous writethrough when the |
Note: This privilege is an addition to the privileges needed for any asynchronous writethrough cache group. |
No additional privileges |
Asynchronous writethrough cache for Oracle Database |
Note: This privilege is an addition to the privileges needed for any asynchronous writethrough cache group. |
No additional privileges |
Incremental autorefresh |
|
None |
Full autorefresh |
|
None |
Dynamic load |
|
|
Aging |
None |
|
Set the LRU aging attributes
|
None |
|
Generate Oracle Database SQL statements to manually install or uninstall Oracle Database objects
|
|
|
Disable or enable propagation of committed cache table updates to the Oracle database
|
None |
|
Configure cache agent timeout and recovery method for autorefresh cache groups
|
|
|
Set the AWT transaction log file threshold
|
None |
|
Enable or disable monitoring of AWT cache groups
|
None |
|
Enable or disable tracking of DDL statements issued on cached Oracle Database tables
|
|
|
Return information about cache grids
|
|
|
Return information about cache grid nodes
|
|
|
Footnote 1 At minimum, the cache administration user must have the CREATE TYPE
privilege.
Footnote 2 At minimum, the cache manager user must have the CREATE SESSION
privilege.
Footnote 3 If the cache administration user will not create autorefresh cache groups, then you can grant the CREATE TRIGGER
privilege instead of the CREATE ANY TRIGGER
privilege.
Footnote 4 Not required if the Oracle Database objects used to manage the caching of Oracle Database data are manually created with the initCacheAdminSchema.sql
script.
Footnote 5 Required if the cache agent start policy is being set to always
or norestart
.
Footnote 6 Required on all Oracle Database tables cached in the TimesTen cache group except for tables owned by the cache administration user.
Footnote 7 The CACHE_MANAGER
privilege includes the CREATE [ANY] CACHE GROUP
privilege. ANY
is required if the cache manager user creates cache groups owned by a user other than itself.
Footnote 8 ANY
is required if any of the cache tables are owned by a user other than the cache manager user.
Footnote 9 Required if the cache group's autorefresh mode is incremental and initial autorefresh state is OFF
, and the Oracle Database objects used to manage the caching of Oracle Database data are automatically created.
Footnote 10 Required if the TimesTen user accessing the cache group does not own the cache group.
Footnote 11 Required if the cache group's autorefresh mode is incremental.
Footnote 12 Required if the TimesTen user accessing the cache group does not own all its cache tables.
Footnote 13 The privilege must be granted to the Oracle Database user with the same name as the TimesTen cache manager user if the Oracle Database user is not the cache administration user.
Footnote 14 Required if the TimesTen user accessing the cache table does not own the table.
TimesTen can automatically create Oracle Database objects owned by the cache administration user, such as cache and replication metadata tables, change log tables, and triggers when particular cache grid and cache group operations are performed. Some of these objects are used to store information about TimesTen databases that are associated with a particular cache grid. Other objects are used to enforce the predefined behaviors of autorefresh cache groups and AWT cache groups.
These Oracle Database objects are automatically created if the cache administration user has been granted the required privileges by running the SQL*Plus script TimesTen_install_dir
/oraclescripts/grantCacheAdminPrivileges.sql
as the sys
user. The set of required privileges include CREATE SESSION
, RESOURCE
, CREATE ANY TRIGGER
, and the TT_CACHE_ADMIN_ROLE
role. The cache administration user name is passed as an argument to the grantCacheAdminPrivileges.sql
script.
Note:
Alternatively, you can manually create these objects as described in "Manually create Oracle Database objects used to manage data caching" before performing any cache grid or cache group operations if, for security purposes, you do not want to grant theRESOURCE
or CREATE ANY TRIGGER
privileges to the cache administration user required to automatically create these tables and triggers.In addition to the privileges granted to the cache administration user by running the grantCacheAdminPrivileges.sql
script, this user may also need to be granted privileges such as SELECT
or INSERT
on the cached Oracle Database tables depending on the types of cache groups you create, and the operations that you perform on the cache groups and their cache tables. See Table 3-1 for a complete list of privileges that need to be granted to the cache administration user in order to perform particular cache grid, cache group, and cache table operations.
Example 3-4 Granting privileges to automatically create Oracle Database objects
As the sys
user, run the grantCacheAdminPrivileges.sql
script to grant privileges to the cache administration user to automatically create Oracle Database objects used to manage caching Oracle Database data in a TimesTen database. In the following example, the cache administration user name is cacheuser
.
Use SQL*Plus to run the grantCacheAdminPrivileges.sql
script:
SQL> @grantCacheAdminPrivileges "cacheuser" SQL> exit
For example, with autorefresh cache groups, the Oracle Database objects used to enforce the predefined behaviors of these cache group types are automatically created if the objects do not already exist and one of the following occurs:
The cache group is created with its autorefresh state set to PAUSED
or ON
The cache group is created with its autorefresh state set to OFF
and then altered to either PAUSED
or ON
The cache administration user requires the RESOURCE
privilege to automatically create the Oracle Database objects used to:
Store information about TimesTen databases that are associated with a particular cache grid.
Enforce the predefined behaviors of autorefresh cache groups. In this case, the cache administration user also requires the CREATE ANY TRIGGER
privilege to automatically create these Oracle Database objects.
Enforce the predefined behaviors of AWT cache groups.
For security purposes, if you do not want to grant the RESOURCE
and CREATE ANY TRIGGER
privileges to the cache administration user required to automatically create the Oracle Database objects, you can manually create these objects.
To manually create the Oracle Database tables and triggers used to enforce the predefined behaviors of particular cache group types, run the SQL*Plus script TimesTen_install_dir
/oraclescripts/initCacheAdminSchema.sql
as the sys
user. These objects must be created before you can create autorefresh cache groups and AWT cache groups. The cache administration user name is passed as an argument to the initCacheAdminSchema.sql
script.
The initCacheAdminSchema.sql
script also grants a minimal set of required privileges including CREATE SESSION
and the TT_CACHE_ADMIN_ROLE
role to the cache administration user. In addition to the privileges granted to the cache administration user by running the initCacheAdminSchema.sql
script, this user may also need to be granted privileges such as SELECT
or INSERT
on the cached Oracle Database tables depending on the types of cache groups you create and the operations that you perform on the cache groups and their cache tables. See Table 3-1 for a complete list of privileges that need to be granted to the cache administration user in order to perform particular cache grid, cache group, and cache table operations.
To manually create the Oracle Database tables used to store information about TimesTen databases that are associated with a particular cache grid, run the SQL*Plus script TimesTen_install_dir
/oraclescripts/initCacheGridSchema.sql
as the sys
user. These tables must be created before you can create a cache grid. The cache administration user name and the name of the cache grid that you create are passed as arguments to the initCacheGridSchema.sql
script.
Example 3-5 Manually creating Oracle Database objects used to manage caching data
As the sys
user, run the initCacheAdminSchema.sql
script to manually create Oracle Database objects used to enforce the predefined behaviors of autorefresh cache groups and AWT cache groups, and grant a limited set of privileges to the cache administration user. Then run the initCacheGridSchema.sql
script to manually create Oracle Database objects used to store information about TimesTen databases associated with a particular cache grid. In the following example, the cache administration user name is cacheuser
and the cache grid name is ttGrid
.
Use SQL*Plus to run the initCacheAdminSchema.sql
and initCacheGridSchema.sql
scripts:
SQL> @initCacheAdminSchema "cacheuser" SQL> @initCacheGridSchema "cacheuser" "ttGrid" SQL> exit
Other Oracle Database objects associated with Oracle Database tables that are cached in an autorefresh cache group are needed to enforce the predefined behaviors of these cache group types. See "Manually creating Oracle Database objects for autorefresh cache groups" for details about how to create these additional objects after you create the cache group.
To view a list of the Oracle Database objects created and used by TimesTen to manage the caching of Oracle Database data, execute the following query in SQL*Plus as the sys
user:
SQL> SELECT owner, object_name, object_type FROM all_objects WHERE object_name 2 LIKE 'TT\___%' ESCAPE '\';
The query returns a list of tables, indexes and triggers owned by either the timesten
user or the cache administration user.
The following sections describe the operations that must be performed on the TimesTen database by the instance administrator or the cache manager user:
A TimesTen database that caches data from an Oracle database can be referenced by either a system DSN or a user DSN. See "Managing TimesTen Databases" in Oracle TimesTen In-Memory Database Operations Guide for more information about creating TimesTen DSNs.
When creating a DSN for a TimesTen database that caches data from an Oracle database, pay special attention to the settings of the following connection attributes. All of these connection attributes can be set in a Data Manager DSN or a connection string, unless otherwise stated.
PermSize
specifies the allocated size of the database's permanent partition in MB. Set this value to at least 32 MB.
OracleNetServiceName
must be set to the net service name of the Oracle database instance.
On Microsoft Windows systems, the net service name of the Oracle database instance is specified in the Oracle Net Service Name field of the IMDB Cache tab within the TimesTen ODBC Setup dialog box.
DatabaseCharacterSet
must be set to the Oracle database character set.
You can determine the Oracle database character set by executing the following query in SQL*Plus as any user:
SQL> SELECT value FROM nls_database_parameters 2 WHERE parameter='NLS_CHARACTERSET';
UID
specifies the name of a cache user, such as the cache manager user, that has the same name as an Oracle Database user who can access the cached Oracle Database tables. The UID
connection attribute can be specified in a Data Manager DSN, a Client DSN, or a connection string.
PWD
specifies the password of the TimesTen user specified in the UID
connection attribute. The PWD
connection attribute can be specified in a Data Manager DSN, a Client DSN, or a connection string.
OraclePWD
specifies the password of the Oracle Database user that has the same name as the TimesTen user specified in the UID
connection attribute and can access the cached Oracle Database tables.
PassThrough
can be set to control whether statements are to be executed in the TimesTen database or passed through to be executed in the Oracle database. See "Setting a passthrough level".
LockLevel
must be set to its default of 0 (row-level locking) because Oracle In-Memory Database Cache does not support database-level locking.
TypeMode
must be set to its default of 0 (Oracle Database type mode).
ReplicationApplyOrdering
and CacheAWTParallelism
control parallel propagation of changes to TimesTen cache tables in an AWT cache group to the corresponding Oracle Database tables. See "Configuring parallel propagation to Oracle Database tables".
Example 3-6 DSN for a TimesTen database that caches data from an Oracle database
The following example is the definition of the cachealone1
DSN that references the first standalone TimesTen database that becomes a member of the ttGrid
cache grid:
[cachealone1] DataStore=/users/OracleCache/alone1 PermSize=64 OracleNetServiceName=orcl DatabaseCharacterSet=WE8ISO8859P1
First you must create a user who performs cache grid and cache group operations. We refer to this user as the cache manager user. This user must have the same name as an Oracle Database user that can select from and update the cached Oracle Database tables. The Oracle Database user can be the cache administration user, a schema user, or some other existing user. The password of the cache manager user can be different than the password of the Oracle Database user with the same name.
The cache manager user is responsible for creating and configuring the cache grid and creating the cache groups. This user can also monitor the grid itself and various operations that are performed on the cache groups.
Then, you must create a user with the same name as an Oracle Database schema user for each schema user who owns or will own Oracle Database tables to be cached in the TimesTen database. We refer to these users as cache table users, because the TimesTen cache tables are to be owned by these users. Therefore, the owner and name of a TimesTen cache table is the same as the owner and name of the corresponding cached Oracle Database table. The password of a cache table user can be different than the password of the Oracle Database schema user with the same name.
Operations on a cache group or a cache table, such as loading a cache group or updating a cache table, can be performed by any TimesTen user that has sufficient privileges. In the examples throughout this guide, the cache manager user performs these types of operations although these operations can be performed by another user, such as a cache table user, that has the required privileges. If these operations are to be performed by a TimesTen user other than the cache manager user, the other user must have the same name as an Oracle Database user that can select from and update the cached Oracle Database tables. Connect to the TimesTen database specifying that user's name in the UID
connection attribute, and supply the corresponding TimesTen and Oracle Database passwords in the PWD
and OraclePWD
connection attributes, respectively, to perform operations on a cache group or cache table.
Example 3-7 Creating the TimesTen users
In the following ttIsql
utility example, create the TimesTen database by connecting to the cachealone1
DSN as the instance administrator. Then create the cache manager user cacheuser
whose name, in this example, is the same as the Oracle Database cache administration user. Then, create a cache table user oratt
whose name is the same as the Oracle Database schema user who is to own the Oracle Database tables to be cached in the TimesTen database.
% ttIsql cachealone1 Command> CREATE USER cacheuser IDENTIFIED BY timesten; Command> CREATE USER oratt IDENTIFIED BY timesten;
The privileges that the TimesTen users require depend on the types of cache groups you create and the operations that you perform on the cache groups. The privileges required for the TimesTen cache manager user and the Oracle Database cache administration user for each cache operation are listed in Table 3-1.
Example 3-8 Granting privileges to the cache manager user
The cacheuser
cache manager user requires privileges to perform the following operations:
Set the cache administration user and password (CACHE_MANAGER
).
Create and associate the TimesTen database with a cache grid (CACHE_MANAGER
).
Start the cache agent and replication agent processes on the TimesTen database (CACHE_MANAGER
).
Attach the TimesTen database to the cache grid (CACHE_MANAGER
).
Create cache groups to be owned by the cache administration user (CREATE CACHE GROUP
, inherited by the CACHE_MANAGER
privilege; CREATE ANY TABLE
to create the underlying cache tables which are to be owned by the oratt
cache table user).
As the instance administrator, use the ttIsql
utility to grant the cache manager user cacheuser
the required privileges:
Command> GRANT CREATE SESSION, CACHE_MANAGER, CREATE ANY TABLE TO cacheuser; Command> exit
You must set the cache administration user name and password in the TimesTen database before any cache grid or cache group operation can be issued. The cache agent connects to the Oracle database as this user to create and maintain Oracle Database objects that store information used to manage a cache grid and enforce predefined behaviors of particular cache group types.
The cache administration user name and password need to be set only once in each TimesTen database that caches Oracle Database data unless it needs to be changed. For example, if the TimesTen database is destroyed and re-created, or the cache administration user name is dropped and re-created in the Oracle database, the cache administration user name and password must be set again.
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.
Example 3-9 Setting the cache administration user name and password
The cache administration user name and password can be set programmatically by calling the ttCacheUidPwdSet
built-in procedure as the cache manager user:
% ttIsql "DSN=cachealone1;UID=cacheuser;PWD=timesten;OraclePWD=oracle" Command> call ttCacheUidPwdSet('cacheuser','oracle');
It can also be set from a command line by running a 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.
An Oracle Database table cannot be cached in separate cache groups within the same TimesTen database. However, the table can be cached in separate cache groups within different TimesTen databases.
A TimesTen cache grid provides users with Oracle databases a means to horizontally scale out cache groups across multiple systems with read and write data consistency across the TimesTen databases and predictable latency for database transactions. A cache grid contains one or more grid members that collectively manage application data using the relational data model. A grid member is either a standalone TimesTen database or an active standby pair that consists of at least two replicated TimesTen databases.
Each database of a grid member is called a grid node. A node is a single TimesTen database that is either a standalone database, or the active database or standby database of an active standby pair. Therefore, a grid member is composed of one or two nodes.
Note:
See "Administering an Active Standby Pair with Cache Groups" in Oracle TimesTen In-Memory Database Replication Guide for more information about replicating cache tables.Grid members can reside on the same system or on different systems. If the grid members reside across different systems, the systems must be connected to each other in a TCP/IP private network. Each system must have the same machine architecture, operating system version, platform, and bit version. The TimesTen major release number of all grid members must be the same.
A TimesTen database that is or is part of a grid member can contain local and global cache groups as well as explicitly loaded and dynamic cache groups.
Note:
See "Dynamic cache groups" for more information about dynamic cache groups.See "Global cache groups" for more information about global cache groups.
A cache grid can be associated with only one Oracle database. A TimesTen database can be a member of only one cache grid. An Oracle database can be associated with more than one cache grid and each grid can be administered by a different cache administration user. A cache grid has no association with other cache grids.
The following sections describe the operations that must be performed on the TimesTen database by the cache manager user:
If you are planning a grid with ten or more nodes, modify the PROCESSES
Oracle Database system parameter. Use this guideline:
PROCESSES >= 10*GridMembers + DLConnections + OraBackgroundProcesses
where:
GridMembers = number of grid members
DLConnections = number of dynamic load connections
OraBackgroundProcesses = number of Oracle Database background processes
The number of dynamic load connections is determined by how many sessions are to have dynamic cache group operations.
For more information about modifying an Oracle Database system parameter, see "Changing Parameter Values in a Parameter File" in Oracle Database Reference. For more information about Oracle Database background processes, see "Background Processes" in Oracle Database Reference.
The examples in the rest of this guide create a cache grid ttGrid
that contains three grid members: two standalone TimesTen databases and an active standby pair consisting of three TimesTen databases. This chapter shows how to associate one of the standalone databases with the cache grid. Subsequent chapters show how to create the other standalone database and the active standby pair, and how to associate those members with the grid.
See Example 3-6 for the DSN definition of the first standalone TimesTen database.
You can create a cache grid from any of the standalone databases, or from either the active or standby database of the active standby pair. A cache grid is created only once from any one of the grid members.
Example 3-10 Creating a cache grid
Create the ttGrid
cache grid from the first standalone database by calling the ttGridCreate
built-in procedure as the cache manager user:
Command> call ttGridCreate('ttGrid');
All the databases in these examples, except for the read-only subscriber database of the active standby pair, are associated with the ttGrid
cache grid.
If you manually created the Oracle Database objects used to store information about TimesTen databases that are associated with a particular cache grid as described in "Manually create Oracle Database objects used to manage data caching", you do not need to call ttGridCreate
because the grid, in effect, was created by running the initCacheGridSchema.sql
script.
By default, you must associate a TimesTen database with a cache grid before you can create cache groups in that database. For backward compatibility, you can set the CacheGridEnable
connection attribute to 0 so that you do not have to create a cache grid and associate the TimesTen database with the grid before cache groups can be created within that database. However, regardless of the setting of CacheGridEnable
, you must create a cache grid and associate the TimesTen database with the grid before you can create global cache groups within that database. See "Global cache groups" for more information about global cache groups.
CacheGridEnable
is set to 1 by default.
To test the connectivity between the TimesTen and Oracle databases, set the passthrough level to 3 and execute the following query, to be processed on the Oracle database, as the cache manager user:
Command> passthrough 3; Command> SELECT * FROM V$VERSION; Command> passthrough 0;
If connectivity has been successfully established, the query returns the version of the Oracle database. If it does not, check the following for correctness:
The Oracle Net service name set in the OracleNetServiceName
connection attribute and the state of the Oracle database server
The settings of the shared library search path environment variable such as LD_LIBRARY_PATH
or SHLIB_PATH
The setting of the cache administration user name in the TimesTen database
Example 3-12 Determining the cache administration user name setting
The cache administration user name setting can be returned programmatically by calling the ttCacheUidGet
built-in procedure as the cache manager user:
Command> call ttCacheUidGet;
It can also be returned from a command line by running a ttAdmin -cacheUidGet
utility command as a TimesTen external user with the CACHE_MANAGER
privilege:
% ttAdmin -cacheUidGet cachealone1
The cache agent is a TimesTen process that performs cache operations such as loading a cache group and autorefresh, as well as manages Oracle Database objects used to enforce the predefined behaviors of particular cache group types.
Example 3-13 Starting the cache agent
The cache agent can be manually started programmatically by calling the ttCacheStart
built-in procedure as the cache manager user:
Command> call ttCacheStart;
It can also be started from a command line by running a ttAdmin -cacheStart
utility command as a TimesTen external user with the CACHE_MANAGER
privilege:
% ttAdmin -cacheStart cachealone1
Example 3-14 Stopping the cache agent
The cache agent can be manually stopped programmatically by calling the ttCacheStop
built-in procedure as the cache manager user:
Command> call ttCacheStop;
It can also be stopped from a command line by running a ttAdmin -cacheStop
utility command as a TimesTen external user with the CACHE_MANAGER
privilege:
% ttAdmin -cacheStop cachealone1
The ttCacheStop
built-in procedure has an optional parameter and the ttAdmin -cacheStop
utility command has an option -stopTimeout
that specifies how long the TimesTen main daemon process waits for the cache agent to stop. If the cache agent does not stop within the specified timeout period, the TimesTen daemon stops the cache agent. The default cache agent stop timeout is 100 seconds. A value of 0 specifies to wait indefinitely.
Do not stop the cache agent immediately after you have dropped or altered an autorefresh cache group. Instead, wait for at least two minutes to allow the cache agent to clean up Oracle Database objects such as change log tables and triggers that were created and used to manage the cache group.
Note:
The TimesTen X/Open XA and Java Transaction API (JTA) implementations do not work with Oracle In-Memory Database Cache. The start of any XA or JTA transaction fails if the cache agent is running.A cache agent start policy determines how and when the cache agent process starts on a TimesTen database. The cache agent start policy can be set to:
manual
always
norestart
The default start policy is manual
, which means the cache agent must be started manually by calling the ttCacheStart
built-in procedure or running a ttAdmin -cacheStart
utility command. To manually stop a running cache agent process, call the ttCacheStop
built-in procedure or run a ttAdmin -cacheStop
utility command.
When the start policy is set to always
, the cache agent starts automatically when the TimesTen main daemon process starts. With the always
start policy, the cache agent cannot be stopped when the main daemon is running unless the start policy is first changed to either manual
or norestart
. Then issue a manual stop by calling the ttCacheStop
built-in procedure or running a ttAdmin -cacheStop
utility command.
With the manual
and always
start policies, the cache agent automatically restarts when the database recovers after a failure such as a database invalidation. If the database was attached to a cache grid when the failure occurred, it is automatically reattached to the grid when the database recovers.
Setting the cache agent start policy to norestart
means the cache agent must be started manually by calling the ttCacheStart
built-in procedure or running a ttAdmin -cacheStart
utility command, and stopped manually by calling the ttCacheStop
built-in procedure or running a ttAdmin -cacheStop
utility command.
With the norestart
start policy, the cache agent does not automatically restart when the database recovers after a failure such as a database invalidation. You must restart the cache agent manually by calling the ttCacheStart
built-in procedure or running a ttAdmin -cacheStart
utility command. If the database was attached to a cache grid when the failure occurred, it is not automatically reattached to the grid when the database recovers. You must call the ttGridAttach
built-in procedure to reattach the database to the grid.
Note:
For more details, see "ttAdmin," "ttCachePolicySet," "ttCacheStart," "ttCacheStop," and "ttGridAttach" in the Oracle TimesTen In-Memory Database Reference.Example 3-15 Setting a cache agent start policy
The cache agent start policy can be set programmatically by calling the ttCachePolicySet
built-in procedure as the cache manager user:
Command> call ttCachePolicySet('always');
It can also be set from a command line by running a ttAdmin -cachePolicy
utility command as a TimesTen external user with the CACHE_MANAGER
privilege:
% ttAdmin -cachePolicy norestart cachealone1