First Connection Attributes
TimesTen sets first connection attributes when a database created by the instance administrator is loaded into memory and persist for the first connection and all subsequent connections until the last connection to this database is closed.
You can modify first connection attributes only when the TimesTen database is unloaded. Then the instance administrator reconnects with new values for the first connection attributes.
If you try to connect to the database using attributes that are different from the first connection attribute settings, the new connection can be rejected or the attribute value can be ignored. However, for example, if existing connections have a LogFileSize of one size and a new connection specifies a LogFileSize of another size, TimesTen ignores the new value and returns a warning.
Only the instance administrator can change a first connection attribute to a value other than the one currently in effect. To change the value of a first connection attribute, you must first shut down the database and then connect with ADMIN privileges. No privileges are required to change AutoCreate and ForceConnect.
The first connection attributes are described in detail next.
AutoCreate
When you connect to an nonexistent database, the AutoCreateconnection attribute automatically creates that database.
With AutoCreate set, TimesTen creates the database, but not the path to the database. If you connect to a database that has the AutoCreate attribute set and the database does not exist yet, the database is created automatically if you supplied a valid existing path. If you attempt to connect to a database that does not exist and the AutoCreate attribute is not set, the connection fails.
Also see Overwrite.
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 AutoCreate as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
|
|
Windows ODBC Data Source Administrator |
Not applicable |
BackupFailThreshold
The BackupFailThreshold connection attribute enables you to ensure the safe completion of your backup.
This connection attribute controls the number of transaction log files that accumulate in the directory defined by the value of the LogDir attribute after a backup starts before TimesTen releases the hold on checkpoint operations. If a checkpoint is initiated before the completion of a backup, the backup is invalidated.
TimesTen temporarily ignores the CkptFrequency and CkptLogVolume attributes (controlling background checkpoints) while a backup is in progress if this attribute is not set or is set to 0.
Set the attribute to a value that is high enough to ensure the safe completion of your backup. For example, if a backup typically takes n seconds to complete and your database creates m transaction log files per second, set BackupFailThreshold to a value greater than n*m.
The number of log files generated by your database per any given unit of time is directly proportional to your write workload and inversely proportional to the value set for the LogFileSize attribute.
Required Privilege
Only the instance administrator can 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 BackupFailThreshold as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
Enter a non-zero integer value that indicates the number of transaction log files that are allowed to accumulate before the backup fails. The default is |
|
Windows ODBC Data Source Administrator |
Not applicable |
CkptFrequency
The CkptFrequency connection attribute controls the frequency in seconds that TimesTen performs a background checkpoint.
The counter used for the checkpoint condition is reset at the beginning of each checkpoint.
If both CkptFrequency and CkptLogVolume attributes have a value greater than 0, a checkpoint is performed when either of the two conditions becomes true. The values set by the ttCkptConfig built-in procedure replace the values set by these attributes.
In the case that your application attempts to perform a checkpoint operation while a background checkpoint is in process, TimesTen waits until the background checkpoint finishes and then executes the application's checkpoint.
When using TimesTen Scaleout, if Durability = 0, set EpochInterval to a value less than the value of the CkptFrequency when Durability=0 to guarantee at least 1 epoch per interval.
The value of this attribute is "sticky" as it persists across database loads and unloads unless it is explicitly changed. The default value is only used during database creation. Subsequent first connections default to using the existing value stored in the database.
When the value of this attribute is more than 0, if a checkpoint fails, TimesTen attempts a checkpoint once every 30 seconds. If a checkpoint failure occurs due to a lack of file system space, we recommend that you attempt a manual checkpoint as soon as space is available. Once any successful checkpoint occurs, background checkpointing reverts to the configured schedule.
Required Privilege
Only the instance administrator can 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 CkptFrequency as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
Enter a value in seconds for the frequency at which TimesTen should perform a background checkpoint. The default is If you do not specify this attribute with a value, TimesTen does not perform background checkpoints. For an existing database, TimesTen uses the stored value. |
|
Windows ODBC Data Source Administrator |
Not applicable |
CkptLogVolume
The CkptLogVolume connection attribute controls the amount of data in megabytes that collects in the log between background checkpoints.
The counter used for the checkpoint condition is reset at the beginning of each checkpoint.
If both CkptFrequency and CkptLogVolume attributes have a value greater than 0, a checkpoint is performed when either of the two conditions becomes true. The values set by the ttCkptConfig built-in procedure replace the values set by these attributes.
In the case that your application attempts to perform a checkpoint operation while a background checkpoint is in process, TimesTen waits until the background checkpoint finishes and then executes the application's checkpoint.
The value of this attribute is "sticky" as it persists across database loads and unloads unless it is explicitly changed. The default value is only used during database creation. Subsequent first connections default to using the existing value stored in the database.
When the value of this attribute is more than 0 and CkptFrequency=0, if a checkpoint fails, TimesTen attempts a checkpoint every 30 seconds. If a checkpoint failure occurs due to a lack of file system space, we recommend that you attempt a manual checkpoint as soon as space is available. Once any successful checkpoint occurs, background checkpointing reverts to the configured schedule.
Required Privilege
Only the instance administrator can 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 CkptLogVolume as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
Specify the amount of data in megabytes that can accumulate in the transaction log file between background checkpoints. The default is the value supplied for the LogFileSize attribute. For an existing database, TimesTen uses the stored value. If the attribute is specified, but you do not supply a value, TimesTen uses the value supplied for the LogFileSize attribute. |
|
Windows ODBC Data Source Administrator |
Not applicable |
CkptRate
The CkptRate connection attribute controls the maximum rate at which data should be written to disk during a checkpoint operation.
This can be useful when the writing of checkpoints to disk interferes with other applications.
All background checkpoints and by checkpoints initiated by the ttCkpt and ttCkptBlocking built-in procedures use the rate specified by this connection attribute. Foreground checkpoints (checkpoints taken during first connect and last disconnect) do not use this rate. The rate is specified in MB per second.
A value of 0 disables rate limitation. This is the default. The value can also be specified using the ttCkptConfig built-in procedure. The value set by the ttCkptConfig built-in procedure replaces the value set by this attribute.
The value of this attribute is "sticky" as it persists across database loads and unloads unless it is explicitly changed. The default value is only used during database creation. Subsequent first connections default to using the existing value stored in the database. If left unspecified (or empty in the Windows ODBC Data Source Administrator), TimesTen uses the stored setting. To turn the attribute off, you must explicitly specify a value of 0. For existing databases that are migrated to this release, the value is initialized to 0. To use the current or default value, the attribute value should be left unspecified.
For more details about the benefits of and issues when using CkptRate, see Setting the Checkpoint Rate in Oracle TimesTen In-Memory Database Operations
Guide.
Required Privilege
Only the instance administrator can 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 CkptRate as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
Specify the maximum rate in MB per second at which a checkpoint should be written to disk. A value of If you do not specify this attribute, TimesTen uses the default value ( If the attribute is specified, but you do not supply a value, the value of Specifying a value of |
|
Windows ODBC Data Source Administrator |
Not applicable |
CkptReadThreads
The CkptReadThreads connection attribute determines the number of threads used to read the checkpoint file when loading the database into memory, such as in first connection or recovery operations.
When the CkptReadThreads attribute is set to 1, TimesTen reads checkpoint files serially. When the CkptReadThreads attribute is set to a value greater than 1, TimesTen uses the specified number of threads to read checkpoint files concurrently (in parallel). When the CkptReadThreads attribute is set to 0 or unspecified, the previously specified value is used.
Required Privilege
Only the instance administrator can 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 CkptReadThreads as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
|
|
Windows ODBC Data Source Administrator |
Not applicable |
Note:
For a progress report on a recovery process, see the rebuild messages in the daemon log file. Set the number of threads low enough to leave sufficient resources on the TimesTen server for other services/processes.
Connections
This attribute indicates the upper bound on the number of user-specified concurrent connections to the database.
TimesTen allocates one semaphore for each expected connection. If the number of connections exceeds the value of this attribute, TimesTen returns an error.
The number of current connections to a database can be determined by viewing the output from the ttStatus utility.
As a guideline, set this value to the maximum number of expected application connections plus ten percent.
If you receive an error indicating that the number of connections exceeds the value of this attribute, increase the value until you no longer receive this error.
There is both a fixed and per connection overhead allocated from the PL/SQL segment, even if you do not use PL/SQL. For details, see PLSQL_MEMORY_SIZE.
Note:
The kernel must be configured with enough semaphores to handle all active databases. For details on setting semaphores for your system, see Operating System Prerequisites in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide or Operating System Prerequisites in Oracle TimesTen In-Memory Database Scaleout User's Guide.
Required Privilege
Only the instance administrator can 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 Connections as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
The default value is the lesser of Supported value is an integer from |
|
Windows ODBC Data Source Administrator |
Not applicable |
EpochInterval
For TimesTen TimesTen Scaleout, use this attribute to set the number of seconds between epochs.
If Durability = 1, the default for this attribute is 0. (System does not generate periodic epochs)
If Durability = 0, the default for this attribute is 1. You must set this attribute to a value less than the value of the CkptFrequency when Durability=0 to guarantee at least 1 epoch per interval.
If this attribute is set to 0, the system does not generate periodic epochs. An application can generate epochs at custom intervals by calling the ttEpochCreate built-in procedure each time the application wants to create an epoch.If an element is down, an epoch interval can be skipped.
As long as one element in each replica set is up, the system never skips more than K*EpochInterval seconds between epochs.
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 EpochInterval as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems database definition ( |
|
|
|
Windows ODBC Data Source Administrator |
N/A |
CreateEpochAtCommit.
ForceConnect
Specifies whether a connection is allowed to a failed database if it is not properly restored from the corresponding subscriber database.
When return receipt replication is used with the NONDURABLE TRANSMIT option, a failed master database is allowed to recover only by restoring its state from a subscriber database using the -duplicate option of the ttRepAdmin utility. In other words, the failed database cannot just come up and have replication bring it up to date because it may lose some transactions that were transmitted to the subscriber but not durably committed locally. The ForceConnect connection attribute overrides this restriction.
The ttConfiguration built-in procedure does not return the value of the ForceConnect attribute.
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 ForceConnect as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
|
|
Windows ODBC Data Source Administrator |
Not applicable |
ForceDisconnectEnabled
Allows you to force disconnection from the database using ttAdmin -disconnect.
The ttConfiguration built-in procedure does not return the value of the ForceDisconnectEnabled attribute.
Note:
-
By default, the forced disconnect feature is disabled. Existing direct-connect applications may find it undesirable for TimesTen to spawn the thread that is required to implement this functionality. See Force Disconnect.
-
Users should not specify different values of this attribute for different database connections. If the force disconnect feature is desired, add
ForceDisconnectEnabled=1to the DSN definition in thesys.odbc.inifile.
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 ForceDisconnectEnabled as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
|
|
Windows ODBC Data Source Administrator |
N/A |
LogAutoTruncate
Determines whether the first connection to the database should proceed if TimesTen recovery encounters a defective log record.
Required Privilege
Only the instance administrator can 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 LogAutoTruncate as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
|
|
Windows ODBC Data Source Administrator |
Not applicable |
LogBufMB
Specifies the size of the internal transaction log buffer in megabytes.
For TimesTen Classic, the LogBufMB attribute specifies the size of the internal transaction log buffer for the database.
For TimesTen Scaleout, the LogBufMB attribute specifies the size of the internal transaction log buffer for the element.
The recommendation is to set LogBufMB to a value between 256 MB and 4 GB. If memory space is a concern, start with 256 MB; otherwise, start with 1 GB.
If you change the value of LogBufMB, you also may need to change the value of LogBufParallelism to satisfy the constraint that LogBufMB/LogBufParallelism >= 8.
If you increase the value of LogBufMB, ensure the value of LogFileSize is greater than or equal to the value of LogBufMB (LogFileSize >= LogBufMB).
Required Privilege
Only the instance administrator can 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 LogBufMB as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
If not set and the database or element exists, TimesTen uses the value stored in the database. If not set and the database or element is being created, TimesTen uses the default value of The maximum value is 65,536 MB (64 GB). |
|
Windows ODBC Data Source Administrator |
Not applicable |
Examples
The following shows how to see the value of LogBufMB.
Command> CALL ttConfiguration('LogBufMB');
< LogBufMB, 64 >
1 row found.LogBufParallelism
The LogBufParallelism attribute specifies the number of transaction log buffer strands to which TimesTen writes log files before the log is written to disk, allowing for improved log performance.
Strands divide the transaction log buffer available memory into a number of different regions, which can be accessed concurrently by different connections. Each connection can execute data-independent DML statements in parallel using those strands as if each has its own transaction log buffer.
Each buffer has its own insertion latch. Records are inserted in any of the strands. The log flusher gathers records from all strands and writes them to the log files.
If you change the value of LogBufParallelism, you also may need to change the value of LogBufMB to satisfy the constraint that LogBufMB/LogBufParallelism >= 8.
Required Privilege
Only the instance administrator can 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 LogBufParallelism as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
An integer value between 1 and 64. The default is |
|
Windows ODBC Data Source Administrator |
Not applicable |
LogFileSize
The LogFileSize attribute specifies the maximum size of transaction log files in megabytes.
The minimum value is 8 MB. The default value is 64 MB. If you specify a size smaller than 8 MB, TimesTen returns an error message. Before TimesTen release 11.2.1.4, the minimum size was 1 MB. If you created your database in a previous release of TimesTen and specified a log file size of less than 8 MB, you must increase the value assigned to this attribute to avoid an error.
Actual transaction log file sizes can be slightly smaller or larger than LogFileSize because log records cannot span transaction log files.
If you specify a value of zero, TimesTen uses the default transaction log file size if the database does not exist. If the database exists, TimesTen uses the current specified transaction log file size.
Set the value of LogFileSize to be larger than or equal to the value of LogBufMB (LogFileSize >= LogBufMB).
Required Privilege
Only the instance administrator can 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 LogFileSize as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
The maximum value is 65,536 MB (64 GB). |
|
Windows ODBC Data Source Administrator |
Not applicable |
LogFlushMethod
Controls the method used by TimesTen to write and sync log data to transaction log files.
As a general rule, use the value 1 if most of your transactions commit durably and use the value 0 otherwise.
For best results, however, experiment with both values using a typical workload for your application and platform. Although application performance can be affected by this attribute, transaction durability is not affected. Changing the value of this attribute does not affect transaction durability in any way.
Required Privilege
Only the instance administrator can 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 LogFlushMethod as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
|
|
Windows ODBC Data Source Administrator |
Not applicable |
DurableCommits.
LogPurge
If the LogPurge attribute is set, TimesTen automatically removes transaction log files when they have been written to both checkpoint files and there are no transactions that still need the transaction log files' contents.
The first time checkpoint is called, TimesTen writes the contents of the transaction log files to one of the checkpoint files. When checkpoint is called the second time, TimesTen writes the contents of the transaction log files to the other checkpoint file.
TimesTen purges the transaction log files if all these conditions are met:
-
The contents of the transaction log files have been written to both checkpoint files.
-
The transaction log files are not pending incremental backup.
-
If replication is being used, the transaction log files have been replicated to all subscribers.
-
If XLA is being used, all XLA bookmarks have advanced beyond the transaction log files.
-
The transaction log files are not being used by any distributed transactions using the XA interface.
If this attribute is set to 0 or unchecked, unneeded transaction log files are appended with the.arch suffix. Applications can then delete the files.
Required Privilege
Only the instance administrator can 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 LogPurge as follows:
| Where to set the attributes | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
|
|
Windows ODBC Data Source Administrator |
Not applicable |
MemoryLock
Enables applications that connect to a shared database to specify whether the real memory should be locked during database loading.
On Linux, MemoryLock=4 will try to obtain a MemoryLock based on what the operating system allows. On Linux, locking all of the virtual memory size (physical + swap) can occur. TimesTen performs best if it does not use swap. Since the operating system allows locking more memory than is actually available, it is important to carefully configure the operating system memory management parameters to limit the amount of lockable memory. You can configure these parameters in the /etc/security/limits.conf file.
On AIX the MemoryLock attribute is not implemented.
The PL/SQL shared memory segment is not subject to MemoryLock.
Required Privilege
Only the instance administrator can change the value of this attribute.
On Linux systems, set the groupname in the MemLock setting to be the same as the instance administrator in the /etc/security/limits.conf file. Set the value of MemLock to be at least as large as the TimesTen database shared memory segment.
To restart the TimesTen daemons, in the new login shell, use:
% ttDaemonadmin -restart
Usage in TimesTen Scaleout and TimesTen Classic
This attribute is supported in both TimesTen Classic and TimesTen Scaleout.Setting
Set MemoryLock as follows.
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
|
|
Windows ODBC Data Source Administrator |
Not applicable |
Overwrite
Specifies that the existing database should be overwritten with a new one when a connection is attempted.
If the Overwrite attribute is set and there is an existing database with the same database path name as the new database, TimesTen destroys the existing database and creates a new empty database if the existing database is not in use. If the Overwrite attribute is set and there is not a database with the specified database path name, TimesTen only creates a new database if the AutoCreate attribute is also set (see AutoCreate). TimesTen ignores the Overwrite attribute if AutoCreate is set to 0. Applications should use caution when specifying the Overwrite =1 attribute.
Required Privilege
Only the instance administrator can change the value of this attribute. If a user other than an instance administrator attempts to connect to a database with Overwrite=1, TimesTen returns an error.
Usage in TimesTen Scaleout and TimesTen Classic
This attribute is supported in TimesTen Classic but not supported in TimesTen Scaleout.Setting
Set Overwrite as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
|
|
Windows ODBC Data Source Administrator |
N/A |
PermSize
Indicates the size in MB for the permanent partition of the database.
For TimesTen Classic, indicates the size in MB of the permanent memory region for the database.
For TimesTen Scaleout, indicates the size in MB of the permanent memory region for the element.
You may increase PermSize at first connect but not decrease it.
TimesTen returns a warning if you attempt to decrease the permanent memory region
size. If the database does not exist, a PermSize value of
0 or no value indicates to use the default size. For an
existing database, a value of 0 or no value indicates that the existing size should
not be changed.
Once you have created a database, you can make the permanent partition larger, but not smaller. See Specifying the Memory Region Sizes of a Database in Oracle TimesTen In-Memory Database Operations Guide.
Also see information about the TempSize connection attribute.
The ttMigrate and ttDestroy utilities can also be used to change the Permanent Data Size, when appropriate.
Required Privilege
Only the instance administrator can 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 PermSize as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
|
|
Windows ODBC Data Source Administrator |
Not applicable |
RecoveryThreads
The RecoveryThreads attribute determines the number of threads used to rebuild indexes during recovery.
If RecoveryThreads=1, during recovery, indexes that must be rebuilt are done serially. If you have enough processors available to work on index rebuilds on your computer, setting this attribute to a number greater than 1 can improve recovery performance. The performance improvement occurs only if different processors can work on different indexes. There is no parallelism in index rebuild within the same index.
The value of RecoveryThreads can be any value up to the number of CPUs available on your system.
The default is 1 when the database is created. Upon subsequent connections, if the database must be recovered and RecoveryThreads is unspecified or has a value of 0, then TimesTen uses the previous setting for this attribute.
Required Privilege
Only the instance administrator can 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 RecoveryThreads as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
|
|
Windows ODBC Data Source Administrator |
Not applicable |
Note:
For a progress report on the recovery process, see the rebuild messages in the daemon log.
Set the number of threads low enough to leave sufficient resources on the TimesTen server for other services/processes.
TempSize
Indicates the size in MB for the temporary partition of the database.
For TimesTen Classic, TempSize indicates the total
amount of memory in MB allocated to the temporary region for the database.
For TimesTen Scaleout, indicates the total amount of memory in MB allocated to the temporary region for an element.
TempSize has no predefined value.
If left unspecified, the TempSize value is determined
from PermSize as follows:
-
If
PermSizeis less than 64 MB,TempSize = 32 MB + ceiling(PermSize / 4 MB). -
Otherwise,
TempSize = 40 MB + ceiling(PermSize / 8 MB).
TimesTen rounds the value up to the nearest MB.
In TimesTen Classic, the minimum TempSize is 32 MB. In
TimesTen Scaleout, the minimum TempSize is 64 MB.
If specified, TimesTen always honors the TempSize
value. Since the temporary data partition is recreated each time a database is
loaded, the TempSize attribute can be increased or decreased each
time a database is loaded. For an existing database, a value of 0 or no value
indicates that the existing size should not be changed.
Required Privilege
Only the instance administrator can 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 TempSize as follows:
| Where to set the attribute | How the attribute is represented | Setting |
|---|---|---|
|
C or Java programs or UNIX and Linux systems |
|
|
|
Windows ODBC Data Source Administrator |
Not applicable |