General Connection Attributes

ChannelCreateTimeout

Use this attribute to determine the time limit in milliseconds to wait for a response to a channel create request.

The value used for the channel create timeout is determined by comparing the values set for the ChannelCreateTimeout, SQLQueryTimeoutMSec and SQLQueryTimeout connection attributes.

If ChannelCreateTimeout, SQLQueryTimeout and SQLQueryTimeoutMSec are non-zero, then the timeout used is the minimum value of these connection attributes.
If ChannelCreateTimeout is set to 0, then irrespective of the value of SQLQueryTimeout, channel timeout feature will be disabled and channel creation will be synchronous.
If ChannelCreateTimeout is set to a non-zero value and SQLQueryTimeout or SQLQueryTimeoutMSec are all set to 0, then the value of ChannelCreateTimeout is the timeout for channel creation.

Note:

If the timeout used is different than what is configured in the ChannelCreateTimeout connection attribute, TimesTen does not overwrite the value set for the ChannelCreateTimeout connection attribute.

See Choose SQL and PL/SQL Timeout Values in the Oracle TimesTen In-Memory Database Operations Guide for more information.

The timeout for channel create should not exceed the value specified for TTC_Timeout, which is a timeout for when the TimesTen client application waits for a result from the corresponding TimesTen Server process. See TTC_Timeout for details on this connection attribute.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is not supported in TimesTen Classic.

This attribute is supported in TimesTen Scaleout.

Setting

Set ChannelCreateTimeout as follows:

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems database definition (`.dbdef`) file in TimesTen Scaleout	`ChannelCreateTimeout`	`n` - Time limit in milliseconds for how long to wait on a create channel request. The value of `n` can be any integer equal to or greater than 0. The default value is 30,000 milliseconds (30 seconds). If you set the value to `0`, then the query does not time out.
Windows ODBC Data Source Administrator	Not applicable

CommitBufferSizeMax

CommitBufferSizeMax indicates the total amount of memory in MB allocated to the transaction commit buffer.

Set this attribute to handle the size of reclaim records.

You can use the ALTER SESSION SQL statement, described in Oracle TimesTen In-Memory Database SQL Reference, to assign or change the maximum size of the commit buffer within a session. The new value takes effect when a new transaction starts.

ALTER SESSION SET COMMIT_BUFFER_SIZE_MAX = n;

You can see the configured maximum for the commit buffer by calling the ttConfiguration built-in procedure.

For more information on reclaim operations, including details about setting the commit buffer size, see Transaction Reclaim Operations in the Oracle TimesTen In-Memory Database Operations Guide. Also see information about the ttCommitBufferStats and the ttCommitBufferStatsReset built-in procedures.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in both TimesTen Classic and TimesTen Scaleout.

Setting

Set CommitBufferSizeMax as follows:

Where to set the attribute How the attribute is represented Setting

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`CommitBufferSizeMax`	`0` - Commit buffer is configured to the default size. (10MB). `n` - Integer value. Minimum user configured size is 1 (MB), Configure this value to a value much smaller than `TempSize`.
Windows ODBC Data Source Administrator	Not applicable

C or Java programs or UNIX and Linux systems odbc.ini file in TimesTen Classic or in the database definition (.dbdef) file in TimesTen Scaleout

CommitBufferSizeMax

0 - Commit buffer is configured to the default size. (10MB).

n - Integer value. Minimum user configured size is 1 (MB), Configure this value to a value much smaller than TempSize.

Windows ODBC Data Source Administrator

Not applicable

Note:

When you call the built-in procedure ttCommitBufferStats, the commit buffer statistics are expressed in bytes. However, the ttConfiguration built-in procedure output and the value set by the connection attribute CommitBufferSizeMax are expressed in MB.

ConnectionName

This attribute enables you to attach a symbolic name to any database connection. Connection names are unique within a process.

This attribute is also available as a client connection attribute.

TimesTen uses the symbolic name to help identify the connection in various administrative utilities, such as ttIsql, ttXactAdmin and ttStatus. This can be particularly useful with processes that make multiple connections to the database, as is typical with multithreaded applications or in the identification of remote clients.

The value of this attribute is intended to be dynamically defined at connection time using the connection string. The default value is the connecting executable file name. It can also be defined statically in the DSN definition. Values used for ConnectionName should follow SQL identifier syntax rules.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in both TimesTen Classic and TimesTen Scaleout.

Setting

Set ConnectionName as follows:

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`ConnectionName`	Enter a string up to 30 characters that represents the name of the connection. If the specified or default connection name is in use, TimesTen assigns the name `conn`, where `n` is an integer greater than 0 to make the name unique. If not specified, the connecting process name.
Windows ODBC Data Source Administrator	Connection field on the Oracle TimesTen client DSN Setup dialog	Enter a string up to 30 characters that represents the name of the connection. If the specified or default connection name is in use, TimesTen assigns the name `conn`, where `n` is an integer greater than 0 to make the name unique. If not specified, the connecting process name.

CreateEpochAtCommit

For TimesTen Scaleout, specifies if each commit generates an epoch.

Set this general connection attribute to 1 to make every commit from this connection an epoch. The default value is 0, which will make it so commits are not epochs unless the transaction included a call to the ttEpochCreate built-in procedure.

TimesTen Classic ignores this attribute.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is not supported in TimesTen Classic.

This attribute is supported in TimesTen Scaleout.

Setting

Set CreateEpochatCommit as follows:

Where to set the attribute How the attribute is represented Setting

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems database definition (`.dbdef`) file in TimesTen Scaleout	`CreateEpochatCommit`	`0` (default) - TimesTen does not write the transaction log to disk on transaction commit. `1` - TimesTen writes log to disk on transaction commit.
Windows ODBC Data Source Administrator	Not applicable

C or Java programs or UNIX and Linux systems database definition (.dbdef) file in TimesTen Scaleout

CreateEpochatCommit

0 (default) - TimesTen does not write the transaction log to disk on transaction commit.

1 - TimesTen writes log to disk on transaction commit.

Windows ODBC Data Source Administrator

Not applicable

Also see LogFlushMethod.

DDLReplicationAction

Determines whether a table or a sequence is included in an active standby pair replication scheme when created.

The table can be included if the DDLReplicationLevel connection attribute is set to 2 or 3. The sequence can be included if the DDLReplicationLevel connection attribute is set to 3.

Replication of DDL operations is enabled (with restrictions) by the set value of the DDLReplicationLevel connection attribute. For more details, see DDLReplicationLevel.

The value can be modified by an ALTER SESSION SQL statement, described in Oracle TimesTen In-Memory Database SQL Reference. For example:

ALTER SESSION SET DDL_REPLICATION_ACTION='EXCLUDE';

Values set by ALTER SESSION override the value set by this attribute.

For examples of altering an active standby pair, see Altering an Active Standby Pair in the Oracle TimesTen In-Memory Database Replication Guide.

DDL operations are automatically committed. When RETURN TWOSAFE has been specified, errors and timeouts may occur as described in RETURN TWOSAFE in the Oracle TimesTen In-Memory Database Replication Guide. If a RETURN TWOSAFE timeout occurs, the DDL transaction is committed locally regardless of the LOCAL COMMIT ACTION that has been specified.

To learn more about replicating DDL, see Making DDL Changes in an Active Standby Pair in the Oracle TimesTen In-Memory Database Replication Guide.

Required Privilege

ADMIN privilege is required if the value of this attribute is INCLUDE.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in TimesTen Classic but not supported in TimesTen Scaleout.

Setting

Set DDLReplicationAction as follows:

Where to set the attribute How the attribute is represented Setting

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic	`DDLReplicationAction`	`INCLUDE` (default) - When a table or sequence is created, it is automatically added to the active standby pair scheme when the appropriate `DDLReplicationLevel` value is configured. `EXCLUDE` - When a table or sequence is created, it is not automatically included in the active standby pair.
Windows ODBC Data Source Administrator	Not applicable

C or Java programs or UNIX and Linux systems odbc.ini file in TimesTen Classic

DDLReplicationAction

INCLUDE (default) - When a table or sequence is created, it is automatically added to the active standby pair scheme when the appropriate DDLReplicationLevel value is configured.

EXCLUDE - When a table or sequence is created, it is not automatically included in the active standby pair.

Windows ODBC Data Source Administrator

Not applicable

DDLReplicationLevel

Enables replication of a subset of data definition language (DDL) statements (with restrictions) in an active standby replication scheme.

When the value of the DDLReplicationLevel connection attribute is set to 1, CREATE or DROP statements for tables, indexes, or synonyms are not replicated to the standby database. However, you can add or drop columns with the ALTER TABLE ADD or DROP COLUMN to or from a replicated table, and those actions are replicated to the standby database.

When the value of the DDLReplicationLevel connection attribute is set to 2 (the default), the following DDL statements (described in Oracle TimesTen In-Memory Database SQL Reference) are replicated to the standby and any subscribers:

CREATE INDEX or DROP INDEX
CREATE SYNONYM or DROP SYNONYM
CREATE TABLE or DROP TABLE (including global temporary tables but not CREATE TABLE AS SELECT)

When the value of the DDLReplicationLevel connection attribute is set to 3, the following DDL statements (described in Oracle TimesTen In-Memory Database SQL Reference) and those replicated when the value is set to 2 are replicated to the standby and any subscribers:

CREATE VIEW or DROP VIEW
CREATE SEQUENCE or DROP SEQUENCE
Replication of the results to the standby master when setting the cache administration user name and password with the ttCacheUidPwdSet built-in procedure. You do not need to stop and restart the cache agent or replication agent to execute the ttCacheUidPwdSet built-in procedure. For more information, see Changing Cache User Names and Passwords in Oracle TimesTen In-Memory Database Cache Guide or ttCacheUidPwdSet.

Some things to be aware of when setting this attribute to are:

If set to 0, open cursors are automatically closed with the implicit commit that occurs in a transaction that contains a DDL statement. You should not use cursors in this way in DDL transactions.

The value of this attribute can be modified by an ALTER SESSION statement, described in Oracle TimesTen In-Memory Database SQL Reference. For example:

ALTER SESSION SET DDL_REPLICATION_LEVEL=3;

Values set by ALTER SESSION override the value set by this attribute.

For examples of altering an active standby pair, see Altering an Active Standby Pair in Oracle TimesTen In-Memory Database Replication Guide.

To learn more about replicating DDL, see Making DDL Changes in an Active Standby Pair in Oracle TimesTen In-Memory Database Replication Guide.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in TimesTen Classic but not supported in TimesTen Scaleout.

Setting

Set DDLReplicationLevel as follows:

Where to set the attribute How the attribute is represented Setting

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic	`DDLReplicationLevel`	`1` - Replicates `ALTER TABLE ADD or DROP COLUMN` to the standby database. Does not replicate `CREATE` and `DROP` operations for tables, indexes, or synonyms to the standby database. `2` (default) - Replicates creating and dropping of tables, indexes and synonyms. `3` - Replicates creating and dropping of views and sequences and replicates the results of the `ttCacheUidPwdSet` built-in procedure.
Windows ODBC Data Source Administrator	Not applicable

C or Java programs or UNIX and Linux systems odbc.ini file in TimesTen Classic

DDLReplicationLevel

1 - Replicates ALTER TABLE ADD or DROP COLUMN to the standby database. Does not replicate CREATE and DROP operations for tables, indexes, or synonyms to the standby database.

2 (default) - Replicates creating and dropping of tables, indexes and synonyms.

3 - Replicates creating and dropping of views and sequences and replicates the results of the ttCacheUidPwdSet built-in procedure.

Windows ODBC Data Source Administrator

Not applicable

Restrictions

Replication of DDL operations has these restrictions:

CREATE TABLE AS SELECT statements are not replicated.
The CREATE INDEX statement is replicated only when the index is created on an empty table.
To control whether a table or sequence is included in an active standby pair replication scheme at the time of creation, use the DDLReplicationAction connection attribute.
Sequences with the CYCLE attribute cannot be replicated.
Objects are replicated only when the receiving database is of a TimesTen release that supports that level of replication, and is configured for an active standby pair replication scheme. For example, replication of sequences (requiring DDL_REPLICATION_LEVEL=3) to a database release prior to 11.2.2.7.0 is not supported. When DDLReplicationLevel value is set to 3, both the active and standby master databases need to be TimesTen Release 11.2.2.7 or later. When DDL_REPLICATION_LEVEL=2, the receiving database must be at least release 11.2.1.8.0 for replication of objects to be supported.
All restrictions for the ttCacheUidPwdSet built-in procedure apply.
When DDLReplicationLevel=1 or 2, you cannot alter a table to add a NOT NULL column to a table that is part of a replication scheme with the ALTER TABLE ... ADD COLUMN NOT NULL DEFAULT statement. You must remove the table from the replication scheme first before you can add a NOT NULL column to it. However, if DDLReplicationLevel=3, then you can alter a table to add a NOT NULL column to a table that is part of a replication scheme.

Diagnostics

Enables an application to configure the level of diagnostics information generated by TimesTen for the connection.

TimesTen diagnostics messages are warnings whose numbers lie within the range 20000 through 29999. Diagnostics connection attribute values are integers.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in both TimesTen Classic and TimesTen Scaleout.

Setting

Set Diagnostics as follows:

Where to set the attribute How the attribute is represented Setting

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	Diagnostics	`0` - TimesTen does not generate diagnostic messages. `1` (default) - TimesTen generates base-level diagnostics messages.
Windows ODBC Data Source Administrator	Not applicable

C or Java programs or UNIX and Linux systems odbc.ini file in TimesTen Classic or in the database definition (.dbdef) file in TimesTen Scaleout

Diagnostics

0 - TimesTen does not generate diagnostic messages.

1 (default) - TimesTen generates base-level diagnostics messages.

Windows ODBC Data Source Administrator

Not applicable

DurableCommits

By default, DurableCommits is set to 0. With this setting, TimesTen writes a log record to the file system when a transaction is committed, but the log record is not immediately written to disk. This reduces transaction execution time at the risk of losing some committed transactions if a failure occurs. When DurableCommits is set to 1, TimesTen writes a log record to disk when the transaction is committed.

A connection can also call the ttDurableCommit built-in procedure to do durable commits explicitly on selected transactions. A call to ttDurableCommit flushes the log buffer to disk. The log buffer is shared among all connections and contains log records from transactions of all connections.

Log records are continually copied from the file system to disk. You can use LogFlushMethod to control when the file system is synchronized with the disk.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in TimesTen Classic but not supported in TimesTen Scaleout.

Setting

Set DurableCommits as follows:

Where to set the attribute How the attribute is represented Setting

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic	`DurableCommits`	`0` (default) - TimesTen does not write the transaction log to disk on transaction commit. `1` - TimesTen writes log to disk on transaction commit.
Windows ODBC Data Source Administrator	Not applicable

C or Java programs or UNIX and Linux systems odbc.ini file in TimesTen Classic

DurableCommits

0 (default) - TimesTen does not write the transaction log to disk on transaction commit.

1 - TimesTen writes log to disk on transaction commit.

Windows ODBC Data Source Administrator

Not applicable

Also see LogFlushMethod.

IncludeInCore

The IncludeInCore attribute allows the application to control whether TimesTen shared memory should be included in application core dumps, and which portions of that memory should be included.

If multiple connections exist from a single application process to a single TimesTen database, the IncludeInCore value of the most recent connection of the process determines the parts of the core file to dump.

For client/server connections, the setting is passed to TimesTen server, which passes it on to the direct driver.

TimesTen daemons always dump everything.

The settings noted below are additive. For example, set IncludeInCore to 3 (1+2) for DB header and other fixed allocations plus perm space. Set it to 15 (1+2+4+8) for DB header and other fixed allocations plus perm space, temp space, and log buffer.

Required Privilege

ADMIN privilege is required to include the DB header and other fixed allocations.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in both TimesTen Classic and TimesTen Scaleout.

Setting

Set IncludeInCore as follows:

Where to set the attribute How the attribute is represented Setting

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`IncludeInCore`	`0` - Exclude the shared memory associated with this database connection from any core files. `1` - Include the DB header and other fixed allocations from this database in core files. This is necessary to make sense of other information you request. 2 - Include perm space from this database in core files. `4` - Include temp space from this database in core files. `8` - Include the log buffer from this database in core files. `16` - Include the PL/SQL shared memory from this database in core files. The default value is 255.
Windows ODBC Data Source Administrator	N/A

C or Java programs or UNIX and Linux systems odbc.ini file in TimesTen Classic or in the database definition (.dbdef) file in TimesTen Scaleout

IncludeInCore

0 - Exclude the shared memory associated with this database connection from any core files.

1 - Include the DB header and other fixed allocations from this database in core files. This is necessary to make sense of other information you request.

2 - Include perm space from this database in core files.

4 - Include temp space from this database in core files.

8 - Include the log buffer from this database in core files.

16 - Include the PL/SQL shared memory from this database in core files.

The default value is 255.

Windows ODBC Data Source Administrator

N/A

Isolation

By default, TimesTen uses read committed isolation. The Isolation attribute specifies the initial transaction isolation level for the connection. For a description of the isolation levels, see Concurrency Control Through Isolation and Locking in Oracle TimesTen In-Memory Database Operations Guide.

The value can be modified by an ALTER SESSION statement, described in Oracle TimesTen In-Memory Database SQL Reference . For example:

ALTER SESSION SET ISOLATION_LEVEL=serializable;

CREATE CACHE GROUP, ALTER CACHE GROUP and DROP CACHE GROUP statements are not supported in serializable isolation mode.

If the passthrough or the propagate cache feature is used, the TimesTen isolation level setting is inherited by the Oracle session. TimesTen serializable mode is mapped to Oracle's serializable mode. TimesTen read committed mode is mapped to Oracle's read committed mode. For more details on the passthrough attribute, see PassThrough.

With PassThrough set to 3, you must use an ALTER SESSION statement to permanently modify the isolation level on the Oracle database connection. For example on a connection to the DSN repdb1_221:

Call ttIsql and connect to the DSN with PassThrough level 3:

% ttIsql;
Command> connect "dsn=repdb1_221;passthrough=3";
Connection successful:. . .PassThrough=3;
<default setting Autocommit=1>

Turn off AutoCommit:
```
Command> autocommit=0;
```
Temporarily change the PassThrough level to 0:
```
Command> passthrough=0;
```

Alter the isolation level to serializable:

Command> prepare 1 ALTER SESSION SET ISOLATION_LEVEL=serializable;
         commit;
         exec=1;

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in TimesTen Classic.

In TimesTen Scaleout, only Isolation=1 is supported.

Setting

Set Isolation as follows:

Where to set the attribute How the attribute is represented Setting

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`Isolation`	`0` - Connects to database in serializable isolation mode. `1` (default) - Connects to database in read committed mode.
Windows ODBC Data Source Administrator	Not applicable

C or Java programs or UNIX and Linux systems odbc.ini file in TimesTen Classic or in the database definition (.dbdef) file in TimesTen Scaleout

Isolation

0 - Connects to database in serializable isolation mode.

1 (default) - Connects to database in read committed mode.

Windows ODBC Data Source Administrator

Not applicable

LockLevel

Specifies whether the connection should use row-level locking (value = 0) or database-level locking (value = 1).

By default, TimesTen enables row-level locking for maximum concurrency. With row-level locking, transactions usually obtain locks on the individual rows that they access, although a transaction may obtain a lock on an entire table if TimesTen determines that doing so would result in better performance. Row-level locking is the best choice for most applications, as it provides the finest granularity of concurrency control. To use row-level locking, applications must set the LockLevel connection attribute to 0 (the default value). To cache Oracle database tables, you must set row-level locking. To CREATE, DROP, or ALTER a user, you can only use row-level locking and thus, the lock level must be set to 0 before you can perform any of these operations.

To give every transaction in this connection exclusive access to the database, you can enable database-level locking by setting the LockLevel attribute to 1. Doing so may improve performance for some applications.

A connection can change the desired lock level at any time by calling the ttLockLevel built-in procedure. Connections can also wait for unavailable locks by calling the ttLockWait built-in procedure. Different connections can coexist with different levels of locking, but the presence of even one connection doing database-level locking leads to loss of concurrency. To display a list of all locks on a particular database you can use the ttXactAdmin utility.

When using PL/SQL in your applications, set LockLevel=0 and selectively change to database level locking for specific transactions that require that level of locking by using the ttLockLevel built-in procedure.

Required Privilege

ADMIN privilege is required if the value of this attribute is 1.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in both TimesTen Classic and TimesTen Scaleout.

Setting

Set LockLevel as follows:

Where to set the attribute How the attribute is represented Setting

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`LockLevel`	`0` (default) - Transactions access the database using row-level locking. `1` - Transactions access the database by acquiring an exclusive lock on the entire database.
Windows ODBC Data Source Administrator	Not applicable

C or Java programs or UNIX and Linux systems odbc.ini file in TimesTen Classic or in the database definition (.dbdef) file in TimesTen Scaleout

LockLevel

0 (default) - Transactions access the database using row-level locking.

1 - Transactions access the database by acquiring an exclusive lock on the entire database.

Windows ODBC Data Source Administrator

Not applicable

LockWait

The LockWait attribute enables an application to configure the lock wait interval for the connection.

The lock wait interval is the number of seconds to wait for a lock when there is contention on it. Sub-second LockWait values significant to tenths of a second can be specified using decimal format for the number of seconds. For example:

LockWait = 0.1

results in a lock wait of one tenth of a second.

LockWait can be set to any value between 0 and 1,000,000 inclusive to a precision of tenths of a second. The default is 10 seconds:

LockWait = 10.0

Actual lock wait response time is imprecise and can be exceeded by up to one tenth of a second, due to the scheduling of the agent that detects timeouts. This imprecision does not apply to zero second timeouts, which are always reported immediately.

The number of connections to a database can impact the time needed to resolve lock contentions. If you anticipate having many connections to the database, increase the lock wait interval.

A connection can change the lock wait interval at any time by calling the built-in procedure.

To display a list of all locks on a particular database you can use the TimesTen utility ttXactAdmin.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in both TimesTen Classic and TimesTen Scaleout.

Setting

Set LockWait as follows:

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`LockWait`	`s` - Indicates the number of seconds to wait for locking conflict resolution before timing out. The default is `10` seconds.
Windows ODBC Data Source Administrator	Not applicable

OptimizerHint

The OptimizerHint connection attribute establishes the connection's optimizer hint defaults.

They can be different than the system defaults. The optimizer hints set with this connection attribute are set for every SQL statement in the user application.

The value of this attribute is a string of the same format as the statement level optimizer hints, but without the delimiters *+, */ and -+. The string can only contain the optimizer hint names. It cannot be mixed with other hint strings or comments.

The order of precedence for optimizer hints is statement level hints, transaction level hints and lastly hints set by this connection attribute.

For client/server applications, the attribute set by the client connection takes precedence over server DSN settings of this attribute.

Some symbols, such as semi-colons (;) are not accepted in attribute values. For hints where the parameter might contain a semi-colon, multiple hints of the same name are combined into one hint. For example, to express:

TT_INDEX (t1,i1, 0; t2, i2,0)

use

TT_INDEX (t1,i1,0) TT_INDEX (t2, i2,0 )

To combine multiple hints at the connection level, you must enter them in the same line.

For a list of optimizer hints supported as values to this attribute, see Statement Level Optimizer Hints in the Oracle TimesTen In-Memory Database SQL Reference.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in both TimesTen Classic and TimesTen Scaleout.

Setting

Set OptimizerHint as follows:

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`OptimizerHint`	A string specifying optimizer hints and their values. The maximum length of the string is 512.
Windows ODBC Data Source Administrator	Not applicable

PermWarnThreshold

The PermWarnThreshold attribute indicates the threshold percentage at which TimesTen issues out-of-memory warnings for the permanent partition of the database's memory.

The database is considered no longer out of permanent memory if it falls 10% below this threshold. An application must call the built-in procedure ttWarnOnLowMemory to receive out-of-memory warnings.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in both TimesTen Classic and TimesTen Scaleout.

Setting

Set PermWarnThreshold as follows:

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`PermWarnThreshold`	`p` - Percentage at which TimesTen should issue out-of-memory warnings. Default is `90`.
Windows ODBC Data Source Administrator	Not applicable

PrivateCommands

Determines if commands are shared between connections.

When multiple connections execute the same command, they access common command structures controlled by a single command lock. To avoid sharing their commands and possibly placing contention on the lock, you can use PrivateCommands. This gives you better scaling at the cost of increased temporary space usage.

By default, the PrivateCommands is turned off and commands are shared.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in both TimesTen Classic and TimesTen Scaleout.

Setting

Set PrivateCommands as follows:

Where to set the attribute How the attribute is represented Setting

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`PrivateCommands`	`0` (default) - Commands are shared with other connections. `1` - Commands are not shared with any other connection.
Windows ODBC Data Source Administrator	Not applicable

C or Java programs or UNIX and Linux systems odbc.ini file in TimesTen Classic or in the database definition (.dbdef) file in TimesTen Scaleout

PrivateCommands

0 (default) - Commands are shared with other connections.

1 - Commands are not shared with any other connection.

Windows ODBC Data Source Administrator

Not applicable

Note:

If there are many copies of the same command, all of them are invalidated by a DDL or statistics change. Reprepare of these multiple copies takes longer when PrivateCommands = 1. With more commands DDL execution can take slightly longer.
When using the PrivateCommands attribute, memory consumption can increase considerably if the attribute is not used cautiously. For example, if PrivateCommands=1 for an application that has 100 connections with 100 commands, there are 10,000 commands in the system: one private command for each connection.

PWDCrypt

The PWDCrypt contains an encrypted version of the corresponding PWD value.

The value for PWD is stored in clear text, which does not allow special characters, in the .odbc.ini file on UNIX and Linux systems and in the Windows Registry on Windows. Any users who have access to the .odbc.ini file or Windows Registry can view the value for this attribute. The PWDCrypt attribute enables special characters, is case sensitive and contains the value of the encrypted password.

For security reasons, the PWDCrypt attribute should only be placed in User DSNs or user private ODBCINI files. The presence of the PWDCrypt in System DSNs enables any user to use the PWDCrypt value to connect to TimesTen, even though they have no knowledge of the cleartext password.

To generate the value for this attribute, run the ttUser utility.

Required Privilege

No privilege is required to change the value of this attribute.

Notes

If PWD and PWDCrypt are both supplied, TimesTen uses the value of the PWD attribute. See UID and PWD.
TimesTen does not store the value of the PWD attribute anywhere in the TimesTen system.
If you are not using PwdWallet to specify a wallet and if you want to provide an encrypted password, use PWDCrypt instead of PWD to specify an encrypted password that corresponds with the specified UID.

See Required User Authentication for Utilities in the description of UID and PWD for details about the treatment of passwords when using utilities that require specific privileges.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in both TimesTen Classic and TimesTen Scaleout.

Setting

Set PWDCrypt as follows:

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`PWDCrypt`	Enter the value generated by the `ttUser` utility.
Windows ODBC Data Source Administrator	PWDCrypt field on the Oracle TimesTen client DSN Setup dialog	Enter the value generated by the `ttUser` utility.

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic	`PwdWallet`	Absolute path and name of the wallet that stores the cache administration user name and password.
Windows ODBC Data Source Administrator	PwdWallet field on the Oracle TimesTen client DSN Setup dialog.

QueryThreshold

Use this attribute to write a warning to the daemon log when the execution time of a SQL statement exceeds the specified value.

You cannot set a query threshold for a SQL statement that is executed by the cache agent. The value of QueryThreshold applies to all connections. It applies to all SQL statements except those executed by the replication agent or the cache agent.

The value of this attribute can be any integer equal to or greater than 0. The default value is 0. A value of 0 indicates that no warning is issued. The unit is seconds.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in both TimesTen Classic and TimesTen Scaleout.

Setting

Set QueryThreshold as follows:

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`QueryThreshold`	A non-negative integer. Default is `0` and indicates that TimesTen does not return a warning.
Windows ODBC Data Source Administrator	Not applicable

ReplicationTrack

When managing track-based parallel replication, this attribute assigns a connection to a replication track.

All transactions issued by the connection are assigned to this track, unless the track is altered.

To start track-based parallel replication you must set a value for the ReplicationParallelism attribute, specifying the number of replication tracks to be applied in parallel. You must also set ReplicationApplyOrdering to 2.

The Track_ID column of the TTREP.REPPEERS system table (described in Oracle TimesTen In-Memory Database System Tables and Views Reference) shows the track associated with the connection.

You can use the ALTER SESSION SQL statement, described in Oracle TimesTen In-Memory Database SQL Reference, to assign or change the value of this attribute within a session. For example:

ALTER SESSION SET REPLICATION_TRACK=4;

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in TimesTen Classic but not supported in TimesTen Scaleout.

Setting

Set ReplicationTrack as follows:

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic	`ReplicationTrack`	`n` - An integer between 1 and 64 that specifies the replication track to be used by transactions issued by the connection.
Windows ODBC Data Source Administrator	Not applicable

SQLQueryTimeout

Use this attribute to specify the time limit in seconds within which the database should execute SQL statements.

This attribute does not stop cache operations that are being processed on an Oracle database. This includes passthrough statements, flushing, manual loading, manual refreshing, synchronous writethrough, and propagating.

Both SQLQueryTimeout and SQLQueryTimeoutMSec attributes are internally mapped to one timeout value in milliseconds. If different values are specified for these attributes, only one value is retained.

The SQLQueryTimeout/SQLQueryTimeoutMsec value should be less than the TransactionTimeout value; the TransactionTimeout value should be less than the TTC_Timeout value.

For more details, see Choose SQL and PL/SQL Timeout Values in the Oracle TimesTen In-Memory Database Operations Guide.

Note:

When SQL query timeouts are used (SQLQueryTimeout or SQLQueryTimeoutMsec), TimesTen behavior is on a best-effort basis. It is not possible to guarantee that the timeout will actually occur within the specified time.
SQL query timeouts are honored during dynamic load unless the dynamic load requires a new connection to the Oracle database, in which case the connection is allowed to complete. If the connection completes successfully but the dynamic load times out, the connection will be retained.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in both TimesTen Classic and TimesTen Scaleout.

Setting

Set SQLQueryTimeout as follows:

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`SQLQueryTimeout`	`n` - Time limit in seconds for which the database should execute SQL queries. The value of `n` can be any integer equal to or greater than 0. The default value is `0`. A value of `0` indicates that the query does not time out.
Windows ODBC Data Source Administrator	Not applicable

SQLQueryTimeoutMSec

Use this attribute to specify the time limit in milliseconds within which the database should execute SQL statements.

This attribute does not stop cache operations that are being processed on an Oracle database. This includes passthrough statements, flushing, manual loading, manual refreshing, synchronous writethrough, and propagating.

Both SQLQueryTimeout and SQLQueryTimeoutMsec attributes are internally mapped to one timeout value in milliseconds. If different values are specified for these attributes, only one value is retained.

The SQLQueryTimeout/SQLQueryTimeoutMsec value should be less than the TransactionTimeout value; the TransactionTimeout value should be less than the TTC_Timeout value.

For more details, see Choose SQL and PL/SQL Timeout Values in the Oracle TimesTen In-Memory Database Operations Guide.

Note:

When SQL query timeouts are used (SQLQueryTimeout or SQLQueryTimeoutMsec), TimesTen behavior is on a best-effort basis. It is not possible to guarantee that the timeout will actually occur within the specified time.
SQL query timeouts are honored during dynamic load unless the dynamic load requires a new connection to the Oracle database, in which case the connection is allowed to complete. If the connection completes successfully but the dynamic load times out, the connection will be retained.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in TimesTen Classic.

This attribute is supported in TimesTen Scaleout.

Setting

Set SQLQueryTimeoutMsec as follows:

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`SQLQueryTimeoutMSec`	`n` - Time limit in milliseconds for which the database should execute SQL queries. The value of `n` can be any integer equal to or greater than 0. The default value is `0`. A value of `0` indicates that the query does not time out.
Windows ODBC Data Source Administrator	Not applicable

TempWarnThreshold

Indicates the threshold percentage at which TimesTen issues out-of-memory warnings for the temporary partition of the database's memory.

The database is considered no longer out of temporary memory if it falls 10% below this threshold. An application must call the built-in procedure ttWarnOnLowMemory to receive out-of-memory warnings. See ttWarnOnLowMemory.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in both TimesTen Classic and TimesTen Scaleout.

Setting

Set TempWarnThreshold as follows:

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`TempWarnThreshold`	`p` - Percentage at which warning should be issued. Default is `90`.
Windows ODBC Data Source Administrator	Not applicable

TransactionTimeout

Use this attribute to specify the time limit in seconds for a user transaction to complete.

If a transaction times out, TimesTen returns an error indicating that either:

TimesTen rolled back the transaction on behalf of the user, or
The user must roll back the transaction.

The SQLQueryTimeout/SQLQueryTimeoutMsec value should be less than the TransactionTimeout value; the TransactionTimeout value should be less than the TTC_Timeout value.

Note:

When a transaction timeout is provided, TimesTen behavior is on a best-effort basis. It is not possible to guarantee that the timeout will actually occur within the specified time.
Transaction timeouts are honored during the active phases of the transaction. However, transactions do not timeout during non-active phases, such as commit, reclaim or in-doubt transaction recovery.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in both TimesTen Classic and TimesTen Scaleout.

Setting

Set TransactionTimeout as follows:

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`TransactionTimeout`	`n` - Time limit in seconds for a user transaction to complete. The value of `n` can be any integer equal to or greater than 0. The default value is `0,` indicating that the transaction does not time out.
Windows ODBC Data Source Administrator	Not applicable

UID and PWD

UID specifies a user name defined on the TimesTen server, while PWD specifies the password corresponding to that UID.

A user ID and password must be provided by a user who is identified internally to TimesTen. Alternatively, an encrypted password can be supplied using the PWDCrypt attribute. Some TimesTen operations prompt for the UID and PWD of the user performing the operation.

For client/server applications, specify UID and PWD either in the Client DSN configuration or in the connection string. The UID and PWD values specified in a connection string take precedence over the values specified in the Client DSN configuration.

Generally, when no UID connection attribute is given, the UID is assumed to be the user name identified by the operating system, and TimesTen does not prompt for a password.

When caching Oracle database tables, PWD specifies the TimesTen password while OraclePWD specifies the Oracle password.

Note:

You can set user names and passwords in connection strings or DSN definitions with the UID and PWD connection attributes, and encrypt passwords with the PWDCrypt connection attribute. However, we recommend you store your passwords in wallets. See ttUser for more information.

Required User Authentication for Utilities

All utilities that require a password prompt for one.

If a UID connection attribute is given but no PWD attribute is given, either through a connection string or in the ODBCINI file for the specified DSN, TimesTen prompts for a password. When explicitly prompted, input is not displayed on the command line.

A password given on the command line, before TimesTen prompts for the password, is visible to the ps command, so use of the PWD connection attribute is not recommended in the first call to the utility. For example, the following usage is not recommended:

% ttIsql -connStr "DSN=mydsn;UID=terry;PWD=secret";

Generally, when no UID connection attribute is given, the UID is assumed to be the user name identified by the operating system, and TimesTen does not prompt for a password.

When a utility accepts a DSN, connection string or database path as a parameter, specify the value at the end of the command line.

Required Privilege

No privilege is required to change the values of these attributes.

Usage in TimesTen Scaleout and TimesTen Classic

These attributes are supported in both TimesTen Classic and TimesTen Scaleout.

Setting

Set UID and PWD as follows:

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`UID`	Character string specifying the user ID.
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic or in the database definition (`.dbdef`) file in TimesTen Scaleout	`PWD`	Character string specifying the password that corresponds to the user ID.
Windows ODBC Data Source Administrator	User ID and Password fields on the Oracle TimesTen Client DSN Setup dialog	Character string specifying the user ID.

WaitForConnect

The WaitForConnect connection attribute specifies that the connection attempt should wait if an immediate connection is not possible.

When an application requests a connection to a TimesTen database and the connection is not possible (perhaps during concurrent loading/recovery of a database), TimesTen usually waits for completion of the conflicting connection. In some cases, it can take some time for an application to connect to a database. If the WaitForConnect attribute is off and the database is not immediately accessible, TimesTen returns immediately an error. For a description of the error, look for the error message number in Warnings and Errors in Oracle TimesTen In-Memory Database Error Messages and SNMP Traps.

Required Privilege

No privilege is required to change the value of this attribute.

Usage in TimesTen Scaleout and TimesTen Classic

This attribute is supported in TimesTen Classic but not supported in TimesTen Scaleout.

Setting

Set WaitForConnect as follows:

Where to set the attribute How the attribute is represented Setting

Where to set the attribute	How the attribute is represented	Setting
C or Java programs or UNIX and Linux systems `odbc.ini` file in TimesTen Classic	`WaitForConnect`	`0` - Does not wait if connection to database fails. `1` (default) - Waits until connection to database is possible.
Windows ODBC Data Source Administrator	Not applicable

C or Java programs or UNIX and Linux systems odbc.ini file in TimesTen Classic

WaitForConnect

0 - Does not wait if connection to database fails.

1 (default) - Waits until connection to database is possible.

Windows ODBC Data Source Administrator

Not applicable

ChannelCreateTimeout

CommitBufferSizeMax

ConnectionName

CreateEpochAtCommit

DDLReplicationAction

DDLReplicationLevel

Diagnostics

DurableCommits

IncludeInCore

Isolation

LockLevel

LockWait

OptimizerHint

PermWarnThreshold

PrivateCommands

PWDCrypt

PwdWallet

QueryThreshold

ReplicationTrack

SQLQueryTimeout

SQLQueryTimeoutMSec

TempWarnThreshold

TransactionTimeout

UID and PWD

WaitForConnect