AbortTimeOut

Time (in minutes) after which an idle transaction is aborted.

A negative or zero value means no timeout.

120

RW/
Startup

AdaptiveRowsPerMessage

If set to yes, the average number of rows returned to the client is used as the rows per message value. The value increases as more rows are fetched.

If set to no, the RowsPerMessage parameter value is used.

yes

RW/
Startup

AllowConnect

If set to no, only connections from solidDB Remote Control (solcon) or solidDB SQL Editor (solsql) are allowed

yes

RW/
Startup

AllowCore

If set to yes, exceptions can be triggered when there is an assertion failure.

yes

RW/
Startup

AllowMiniDump

(Windows only) If set to yes, (and Srv.AllowCore is also set to yes), the server creates a process minidump when an unhandled exception occurs.

The dump file (solid-timestamp.dmp) is created in the working directory, and can be used with a debugging program to find out information about the process that crashed.

yes

RW/
Startup

At

Commands for automating administrative tasks, such as executing operating system commands, creating backups, checkpoints, and database status reports.

The parameter value has the following syntax:

For example:

If you specify a backup, the default backup directory is the one set with the General.BackupDirectory parameter.

If the day is not given, the command is executed daily.

None

RW

 

The timed_command has the following options (with arguments and default values):

For information about entering timed commands, see Entering timed commands.

 

 

AuditInfoExcludeUsers

Comma-separated list of users whose activity is excluded from the audit.

None

RW/
Startup

AuditInfoIncludeUsers

Comma-separated list of users who are included in AuditInfo output.

None

RW/
Startup

AuditInfoLogDir

Directory path for storing the audit files.

The path can be an absolute path or relative to the solidDB working directory and must use the conventions of your operating system. For example, in Windows environments, if the path contains white space characters, the path must be enclosed in double quotation marks. If the server runs on a UNIX operating system, path separators must be slashes instead of backslashes.

The directory must exist prior to starting the server. If the directory becomes unreachable or full while the audit is in progress, the audit fails with an appropriate error code.

None

RW/
Startup

AuditInfoLogEnabled

If set to yes, audit logging is enabled.

Audit records are saved in a solaudit.out file in the directory specified by AuditInfoLogDir.

no

RW/
Startup

AuditInfoLogFileNum

Internal parameter to keep the latest audit log file number.

If Audit Info logging is running, this parameter is added to the solid.ini file, however, you should not change the value..

None

 

AuditInfoFilter

None
(all database operations are collected)

RW/
Startup

AuditInfoLogFileSize

Maximum file size (in bytes) for audit logging,

Follow the value with K (to specify a value in KB), M (to specify a value in MB), or G (to specify a value in GB).

Audit logging uses multiple files each with a maximum size specified by AuditInfoLogFileSize. The latest file is solaudit.out and older files are renamed using a pattern solaudit.n.out.

100000000 (about 100 MB)

RW/
Startup

AuditInfoLogMaxSize

Maximum total size (in bytes) for audit log files.

Follow the value with K (to specify a value in KB), M (to specify a value in MB), or G (to specify a value in GB).

When the maximum size is reached, the oldest audit file is deleted.

1000000000 (about 1 GB)

RW/
Startup

AuditInfoMemQueueLength

Maximum memory queue length (in records) used to buffer audit records.

If audit records are not processed when the queue gets full then applications must wait for new space in the queue.

10000

RW/
Startup

AuditInfoReadMaxWait

Maximum time (in seconds) to wait for an audit read operation before records are discarded.

5

RW/
Startup

AutoReportInterval

Time interval (in seconds) after which the server generates a server report file.

Report files are named solautorep.nnn.txt (where nnn is an incrementing number).

0

RW

AutoReportLimit

Number of report files that are kept on disk.

Report files are named solautorep.nnn.txt (where nnn is an incrementing number).

A value of 0 means that no report files are generated.

0

RW

ConnectionCheckInterval

Time (in seconds) between connection status checks in thread/client mode.

To use this parameter, you must set the Srv.ReadThreadMode parameter to 0 and the Srv.Threads parameter to a value that is large enough to accommodate the threads in your environment.

When the Srv.ReadThreadMode parameter is set to 2 (default), a broken connection is not detected until the server tries to write something to the client.

10

RW/
Startup

ConnectTimeOut

Continuous idle time (in minutes) after a connection is dropped.

A negative or zero value means no timeout.

480

RW/
Startup

DatabaseSizeReportInterval

Database size increase (in megabytes) that causes the system to generate a report file.

This parameter is useful to trace unexpected database size growth.

The minimum non-zero value for this parameter is 1 (1 MB). The report file name is repdbmbMB.dbg.

0
(no reports generated)

RW/
Startup

DisableOutput

If set to yes, generation of the solmsg.out and the solerror.out files is disabled.

For details on these files, see Viewing error messages and log files.

no

RO

Echo

If set to yes, contents of solmsg.out file are also displayed in the server command window.

no

RW/
Startup

ExecRowsPerMessage

Number of result rows that are sent (prefetched) to the client driver in response to the SQLExecute call with a SELECT statement.

The result rows are subsequently returned to the application with the first SQLFetch calls generated by the application. The default value of 2 allows for prefetching of single-row results. If your SELECT statements usually return larger number of rows, setting this to an appropriate value can improve performance significantly.

See also, RowsPerMessage.

2

RW/
Startup

ForceThreadsToSystemScope

Applies only to symmetric multiprocess (SMP) Solaris operating systems, in which the default scope that is provided by the threads of the runtime library can be set to process scope, system scope, or light weight process (lwp) scope. In Solaris environments, threads are lightweight processes.

If set to yes, server performance can be significantly improved in a multi-CPU machine. The actual performance improvement depends on how evenly the workload is already spread across your CPUs.

If set to no, you should get slightly better performance in single-CPU systems.

When this parameter is set to yes, it forces lwp threads to be run in system scope, instead of process scope. It also allows Solaris to schedule solidDB threads on any available CPU. This reduces bottlenecks and enhances the parallelization of operations, including I/O.

For more information about lwp, see Solaris operating system documentation.

Solaris: yes

Other environments: no

RW/
Startup

HealthCheckEnabled

If set to yes, a periodical check is performed to detect a stalled server due to, for example, unexpected operating system stalls or software errors.

The check uses a timeout-based server deadlock detection algorithm that checks certain critical low-level concurrent programming synchronization objects (mutexes).

If a deadlock is detected, the server process terminates with an error and a message is printed to solerror.out.

For example in High Availability (HotStandby) configurations, a failover can be enforced upon the detection of a server deadlock.

no

RW/
Startup

HealthCheckInterval

Time interval (in seconds) between internal health checks

30

RW

HealthCheckTimeout

The time (in seconds) that the system waits before deciding there is a deadlock.

The factory value is high enough to escape false errors. If faster detection is needed, set the parameter to a lower value.

60

RW

InifileLineSplitting

If set to yes, solid.ini configuration file lines that are longer than 79 characters are split into multiple lines when server saves the file.

For example, if you create comments longer than 79 characters, the server splits the comments on separate lines using a backslash (\) at the end of the line but without adding a comment marker (;) on the new line. The server handles the lines that have been split in this way; however, applications such as watchdogs might see the file as corrupted and thus fail.

If set to no, lines are never split.

yes

RW/
Startup

KeepAllOutFiles

If set to yes, the solidDB message log (solmsg.out) and trace files are not overwritten with new contents.

Instead, when a file limit is reached, a new file is created with an incremented file name number postfix. The starting value of the postfix is set by using parameters Srv.TraceBackupFileNum and Srv.SolmsgBackupFileNum.

no

RO

LocalStartTasks

Number of server internal tasks that execute the local background statements that were started with the statement START AFTER COMMIT (without FOR EACH REPLICA).

Valid values range from 1 to 100.

In this case, you can have 1 to N tasks that execute the background operations. More tasks mean that background tasks reserve more resources and are handled faster, and that other operations (for example, interactive operations) get fewer resources and are handled more slowly.

2

RW/
Startup

MaxBigTaskInterval

Maximum length of time (in seconds) to wait before checking whether internal administrative tasks that are "sleeping" should be "woken".

For example, if a connection has been broken or disconnected, this parameter specifies the maximum length of time that the server will wait before noticing that the connection is not available. This time is in addition to whatever time is required for the underlying communication layer to detect that the connection is broken. For example, if you have a Connect Timeout of 100 seconds and the value of MaxBigTaskInterval is 50 seconds, then you might have to wait up to 150 seconds before a broken connection is detected and no longer counted as one of the connections.

You might want to set or adjust this parameter if you get the following types of errors:

This parameter applies only to the internal administrative tasks of the server. It does not affect the scheduling of user tasks.

Setting MaxBgTaskInterval to a small enough value might reduce performance and might reallocate some time from high-priority tasks to low-priority tasks. This can happen in systems where low-priority connections are not checked often enough to notice that they have been disconnected. However, because the parameter only affects server administrative tasks, not user tasks, the effect is generally small.

2

RW/
Startup

MaxConstraintLength

Maximum number of bytes that the server searches through in a string, for example in WHERE clauses such as:

For example, if the value is 1024, ASCII character strings are searchable up to 1024 characters and Unicode character strings are searchable up to 512 characters (1024 bytes).

This parameter applies to strings that have the following data types:

It does not apply to strings that have the data type(s):

The minimum valid value is 254. If you specify a smaller number, the server will still search the first 254 bytes.

Although you can use any value from 254 to 2G-1, practical values are generally in the range of a few kilobytes, like 1024, or 8192.

254
(254 ASCII characters or 127 Unicode characters)

RW

MaxOpenCursors

Maximum number of cursors that a database client can have simultaneously open.

1000

RW/
Startup

MaxRPCDataLength

Maximum string length (in bytes) of a single SQL statement that is sent to the server.

Follow the value with K (to specify a value in KB), M (to specify a value in MB), or G (to specify a value in GB).

This is particularly useful if you are sending CREATE PROCEDURE commands that are longer than 64KB. The value should be between 65536 (64KB) and 1048576 (1024KB). If the value is set to less than 65536, the server will use a minimum of 64KB.

524288
(512 KB)

RW/
Startup

MaxStartStatements

Maximum number of simultaneous "uncommitted" START AFTER COMMIT statements.

Possible values range from 0 to 1000000.

10000

RW/
Startup

MaxUsers

Maximum number of connections to solidDB.

When the number of maximum users has been exceeded, error 14507 is generated and you can connect to solidDB only by using solidDB Remote Control (solcon).

A value of 0 means that the maximum number of connections is not restricted.

0

RW/
Startup

MemoryReportDelta

Increase or decrease (in bytes) in memory allocation between messages that causes a new message to be printed to solmsg.out.

Follow the value with K (to specify a value in KB), M (to specify a value in MB), or G (to specify a value in GB).

20M

RW/
Startup

MemoryReportLimit

Minimum size (in bytes) for memory allocations after which reporting to solmsg.out is initiated.

0
(no reporting)

RW/
Startup

MemorySizeReportInterval

Memory size increase (in megabytes) that causes the system to generate a report file.

This is parameter is useful, for example when tracing unexpected memory growth in the server.

The minimum non-zero value for this parameter is 1 (1 MB). The report file name is repmemmbMB.dbg.

0
(no reports generated)

RW/
Startup

MessageLogSize

Maximum size (in bytes) of the solmsg.out file.

Follow the value with K (to specify a value in KB), M (to specify a value in MB), or G (to specify a value in GB).

10000000

RW/
Startup

Name

Informal name of the server, equivalent to the -n command line option.

None

RW/
Startup

NetBackupRootDir

Root directory for network backups to the NetBackup server.

The path can be absolute or relative to the working directory.

For example with the following setting:

backups are created in subdirectories of the abc\backups directory under the NetBackup server working directory.

The path must use the conventions of your operating system. For example, in Windows environments, if the path contains white space characters, the path must be enclosed in double quotation marks. If the server runs on a UNIX operating system, path separators must be slashes instead of backslashes.

working directory

RW

NUMANodeBind

Applies to Windows 64-bit only.

Specific NUMA node(s) to which solidDB is bound.

Set NUMANodeBind to either a list of values (comma-separated individual values, ranges of values, or both) or the keyword all.

For example: NUMANodeBind=1, 3-4

The keyword all spreads the threads to all available nodes.

The default value of 0 is used to indicate that thread affinities are not changed. If the operating system starts numbering nodes from 0, you must add '1' to the O/S number for each node when you add node numbers as parameter values.

If both NUMANodeBind and ProcessorGroupBind are set, ProcessorGroupBind has priority.

0

RW/
Startup

ODBCDefaultCharBinding

Binding method for character data types.

Any value that is specified for this parameter is overridden by the client-side parameter, Client.ODBCCharBinding parameter (if set), see Client section.

The following options are valid:

Depends on the value of the parameter General.InternalCharEncoding (see description)

RW/
Startup

PessimisticTableUseNFetch

(Applies if pessimistic locking is used and the query locks any rows)

If set to yes, the value set in the Srv.RowsPerMessage parameter is used to determine the number of rows that are returned in each message.

If set to no, any value that is set by the Srv.RowsPerMessage parameter is ignored, and only one row is returned in each message.

no

RW/
Startup

PmonHistoryInterval

PMON history interval (in seconds).

60

RW/
Startup

PmonHistoryLimit

Maximum number of PMONs kept in memory.

1440

RW/
Startup

PrintMsgCode

Causes a unique 8-character message code to be inserted before each status and error message in the message log files (solmsg.out and solerr.out).

no

RW/
Startup

ProcessMemoryCheckInterval

Interval (in milliseconds) after which process size limits are checked.

The minimum non-zero value is 1000 (1 second). An error message is generated if any non-zero value below 1000 is specified.

If the ProcessMemoryCheckInterval parameter is set to 0, the ProcessMemoryLimit parameter is not effective, that is, there is no process memory limit.

See also, ProcessMemoryLowPercentage and ProcessMemoryWarningPercentage.

0
(process checking is disabled)

RW

ProcessMemoryHysteresisPercentage

Difference (as a percentage of a memory limit parameter) that determines the value at which a system event is generated when the memory usage decreases below the limit.

As the amount of memory used crosses different boundaries (as specified with, for example, the MME.ImdbMemoryLowPercentage or the Srv.ProcessMemoryLimit parameters), system events are generated. To prevent too many system events being generated when the memory usage alternates rapidly above and below the specified limit, the value that triggers a message when the memory decreases below the specified limit is somewhat lower than the value that triggers a message when the memory increases above the specified limit. The difference is specified as a percentage of the memory limit parameter.

For example, if the ProcessMemoryLimit parameter is set to 1000M (1GB), and ProcessMemoryHysteresisPercentage is set to 5 (5%), system event messages that report memory usage are only generated in the following situations:

5

RW

ProcessMemoryLimit

Maximum amount of virtual memory (in MB) that can be allocated to the in-memory database process.

Follow the value with G to specify a value in GB.

A value of 0 means there is no limit.

If you use this parameter, set it to a value that ensures that the in-memory database process fits entirely within physical memory. Consider the following factors:

When the limit is reached, the server accepts only ADMIN COMMANDs.

if the ProcessMemoryCheckInterval parameter is set to 0, the ProcessMemoryLimit parameter is not effective, that is, there is no process memory limit.

0
(no limit)

RW

ProcessMemoryLowPercentage

Second warning limit (as percentage of the ProcessMemoryLimit parameter value) for the total process size.

Exceeding this limit generates a system event.

The ProcessMemoryLowPercentage parameter value must be greater than the ProcessMemoryWarningPercentage parameter value. This ensures that a warning message about the total process size has already been written in the solmsg.out log file before a system event is generated.

See also, ProcessMemoryLimit, ProcessMemoryCheckInterval, and ProcessMemoryWarningPercentage.

90

RW

ProcessMemoryWarningPercentage

First warning limit (as percentage of the ProcessMemoryLimit parameter value) for the total process size.

Exceeding this limit generates a warning message in the solmsg.out log file.

The ProcessMemoryWarningPercentage parameter value is must be lower than the ProcessMemoryLowPercentage parameter value.This ensures that a warning message about the total process size has already been written in the solmsg.out log file before a system event is generated.

See also, ProcessMemoryLimit, ProcessMemoryCheckInterval, and ProcessMemoryLowPercentage.

80

RW

ProcessorGroupBind

Applies to Windows 64-bit only.

Specific NUMA node(s) to which solidDB is bound.

Set ProcessorGroupBind to either a list of values (comma-separated individual values, ranges of values, or both) or the keyword all.

For example: ProcessorGroupBind=1, 3-4

The keyword all spreads the threads to all available nodes.

The default value of 0 is used to indicate that thread affinities are not changed. If the operating system starts numbering nodes from 0, you must add '1' to the O/S number for each node when you add node numbers as parameter values.

If both NUMANodeBind and ProcessorGroupBind are set, ProcessorGroupBind has priority.

0

RW/
Startup

ReadThreadMode

Number of threads that the server uses to service client requests.

If set to 0, the server uses the number of threads specified with the Threads parameter.

If set to 2, the server creates a separate thread for each client.

Using more threads will generally improve performance, but also requires more memory.

This parameter controls only the number of threads that serve client requests. It does not affect the number of threads that do other work within the server.

Some operating systems might limit the maximum number of threads allowed, and setting this parameter value to 2 might cause the server to request more threads than the operating system allows. If you try to exceed the number of threads allowed, the following type of error is generated:

2

RW/
Startup

RemoteStartTasks

Number of internal tasks inside a replica server that execute the remote background statements (that are started on the master server with the statement START AFTER COMMIT... FOR EACH REPLICA).

Valid values range from 1 to 100.

2

RW/
Startup

ReportInterval

Interval (in seconds) at which reports are automatically generated.

Automated reports are named reptimestamp.dbg and output to the solidDB working directory.

A value of 0 means that reports are not generated automatically.

0
(no reports not generated)

RW

RowsPerMessage

Number of rows returned from the server in one network message when an SQLFetch call is executed (and there are no prefetched rows).

(solidDB version 200.0.3 and later) Maximum value is 10000.

(solidDB version 200.0.2 and earlier) Maximum value is 100.

See also, Srv.ExecRowsPerMessage, Srv.PessimisticTableUseNFetch.

100

RW/
Startup

Silent

If set to yes, no output is generated to the server command window. Only license information is displayed.

no

RW/
Startup

SolmsgBackupFileNum

Starting digit of the message log file (solmsg.out) name postfix.

Only used if the KeepAllOutFiles parameter is set to yes.

For example, if the value is set to 5, the solmsg.out files are named as follows:

Valid values range from 0 to 999999.

0

RW/
Startup

StackTraceEnabled

If set to yes, stack trace functionality is enabled upon an assertion failure or a signal caused by server malfunction.

The stack trace information is output to ssstacktrace‑process_id-thread_id.out file.

The following signals invoke the stack traces output automatically:

The stack traces information is produced for only the thread that received the signal.

Additionally, you can generate the stack traces information for all currently running threads by sending the server the SIGUSR1 signal.

yes

RW/
Startup

StandardDateTimeFormat

If set to yes, solidDB uses the ISO/IEC/ANSI standard date representation, which is also the standard date literal format in SQL. The date is represented as 2008-10-15 09:29:40

If set to no, the message log files (solmsg.out) use a date format such as 15.10 09:29:40. The solerror.out file uses a date format such as Mon Oct 22 15:16:35 2007.

yes

RO

StatementMemoryTraceLimit

Allocated memory limit (in bytes) for statements that, if exceeded, triggers tracing activity.

Follow the value with K (to specify a value in KB), M (to specify a value in MB), or G (to specify a value in GB).

A value of 0 means there is no tracing activity.

Statements that have allocated memory that is greater than the specified value are put into the peak memory usage list, which is printed to report file. These statements are also printed to the solmsg.out file.

0

RW/
Startup

Threads

Number of concurrent threads that the server uses to process user requests.

The helper threads, such as I/O threads, are not included in the count.

5

RW/
Startup

TraceBackupFileNum

Starting value of the trace file name postfix that is appended to the file name.

Only used if the KeepAllOutFiles parameter is set to yes.

Valid values range from 0 to 999999.

0

RW/
Startup

TraceLogSize

Maximum size (in bytes) of the trace log file, soltrace.out.

Follow the value with K (to specify a value in KB), M (to specify a value in MB), or G (to specify a value in GB).

For information about enabling monitoring, see the description of ADMIN COMMAND 'monitor...' in ADMIN COMMAND syntax and the -m command-line option in Command line options.

When the maximum size is reached, a backup copy of the trace file is made, and a new trace file is started from scratch.

10000000

RW/
Startup

TraceSecDecimals

Number of decimal places in trace outputs.

Possible values range from 0 to 3.

This parameter is deprecated. All times are expressed in milliseconds.

3

RW/
Startup