Skip to content

Time-out Properties#

BLOCK_ALL_TX_TIME_OUT (Unit: second)#

Data Type#

Unsigned Integer

Default Value#

3

Attributes#

Read-Write, Single Value

Range#

[0, 232-1]

Description#

This property restricts transactions' access to the hash table when the buffer manager resizes the hash table. The minimum value of 0 specifies that error handling is to be performed without any wait time.

This property can be changed using the ALTER SYSTEM statement while Altibase is running.

DDL_LOCK_TIMEOUT (Unit: second)#

Data Type#

Short integer

Default Value#

0

Attributes#

Read-Write, Single Value

Range#

[-1, 65535]

Description#

When DDL query statements are executed, this property sets how long to wait to establish a lock when the target table has already been locked by another transaction. In cases where a transaction cannot immediately gain write access to the table, If this parameter is set to -1, the transaction will wait indefinitely, whereas if this parameter is set to a positive value, the transaction will wait for that number of seconds before trying again.

The default value of this parameter is 0, which tells Altibase to return an error code if it cannot obtain a lock immediately at the time of executing a DDL statement.

This property can be changed using the ALTER SYSTEM statement while Altibase is running.

DDL_TIMEOUT (Unit: second)#

Data Type#

Unsigned Integer

Default Value#

0

Attributes#

Read-Write, Single Value

Range#

[0, 232-1]

Description#

If the execution time of a DDL statement exceeds the number of seconds specified here, execution of that statement is canceled. The default value of this property is 0, in which case Altibase waits indefinitely for DDL operations to finish.

This property can be changed using the ALTER SYSTEM or ALTER SESSION statement while Altibase is running.

Note: In Altibase versions up to 5.5.1, the execution time of DDL statements was governed by the UTRANS_TIMEOUT and QUERY_TIMEOUT properties, which still govern the execution time of DML and DCL statements.

FETCH_TIMEOUT (Unit: second)#

Data Type#

Unsigned Integer

Default Value#

60

Attributes#

Read-Write, Single Value

Range#

[0, 232-1]

Description#

This property prevents abnormal increases in database memory consumption when SELECT statements executed by client applications take an excessive amount of time. In cases where the query execution time exceeds the number of seconds specified using this property, the session will be disconnected and the transaction will be rolled back.

This property can be changed using the ALTER SYSTEM or ALTER SESSION statement while Altibase is running.

IDLE_TIMEOUT (Unit: second)#

Data Type#

Unsigned Integer

Default Value#

0

Attributes#

Read-Write, Single Value

Range#

[0, 232-1]

Description#

If a large number of clients are connected to a server for an excessive period of time due to some abnormality, the number of available connections will significantly decrease, ultimately leading to failure to provide service.

This property functions to preemptively prevent this situation. If the number of seconds that a session is idle exceeds this value, the session will be disconnected and any associated transactions will be rolled back.

The value of this property can be changed using the ALTER SYSTEM or ALTER SESSION statement while Altibase is running.

LOGIN_TIMEOUT (Unit: second)#

Data Type#

Unsigned Integer

Default Value#

0

Attributes#

Read-Write, Single Value

Range#

[0, 232-1]

Description#

This property specifies the permitted amount of time, in seconds, to wait for authorization to be completed after a connection has been made to an Altibase port. If authorization is not completed within this time, the server disconnects.

MULTIPLEXING_POLL_TIMEOUT (Unit: microsecond)#

Data Type#

Unsigned Integer

Default Value#

10000

Attributes#

Read-Write, Single Value

Range#

[1000, 1000000]

Description#

This property specifies the interval at which the multiplexed thread running service detects sessions.

QUERY_TIMEOUT (Unit: second)#

Data Type#

Unsigned Integer

Default Value#

600

Attributes#

Read-Write, Single Value

Range#

[0, 232-1]

Description#

This property is set to prevent abnormal increases in database memory consumption when particular kinds of queries (especially those involving sort operations or joins) are executed. If the query execution time exceeds the number of seconds specified here, the transaction is partially rolled back.

This property can be changed using the ALTER SYSTEM or ALTER SESSION statement while Altibase is running.

SHUTDOWN_IMMEDIATE_TIMEOUT#

Data Type#

Unsigned Integer

Default Value#

60

Attributes#

Read-Write, Single Value

Range#

[0, 232-1]

Description#

When shutting down Altibase with the IMMEDIATE option, Altibase is shut down after uncommitted transactions are rolled back. This property specifies the amount of time, in seconds, to wait for the transactions to be rolled back. If the elapsed time exceeds the specified value, Altibase is shut down forcibly and uncommitted transactions are not rolled back. If this property is set to 0, Altibase waits until all transactions are rolled back.

This property can be changed using the ALTER SYSTEM statement while Altibase is running.

UTRANS_TIMEOUT (Unit: second)#

Data Type#

Unsigned Integer

Default value#

3600

Attributes#

Read-Write, Single Value

Range#

[0, 232-1]

Description#

This property is set to prevent the number of log files from abnormally increasing when write operations (UPDATE, DELETE, INSERT) take a long time. If such a transaction takes longer than the number of seconds specified here, the session will be disconnected and the transaction in question will be rolled back.

This property can be changed using the ALTER SYSTEM or ALTER SESSION statement while Altibase is running.

XA_INDOUBT_TX_TIMEOUT (Unit: second)#

Data Type#

Unsigned Integer

Default Value#

60

Attributes#

Read-Only, Single Value

Range#

[0, 232-1]

Description#

When using the Two-Phase Commit Protocol, this property specifies the number of seconds to wait before terminating an entire transaction that has taken a long time and is thus in IN_DOUBT state.