dbutility Console Informational Messages

The following messages appear in response to dbutility console commands.

Aux STMT Statistics:

Configured_max = nnn, Max_used = mmm, Recycled_stmt_cnt = rrr.rr

STMT reuse stats: min_sql_ops = nnn, max_sql_ops = mmm, avg_sql_ops = rrr.rr

STMTs never reused = nnn, min_sql_ops = mmm, max_sql_ops = ddd, avg_sql_ops = rrr.rr

This message appears in response to a dbutility ASTATS console command.

Client State = state_name

This message shows the Client status during a process command. It is displayed by dbutility in response to a STATUS command. This message typically includes the following additional lines. (The lines "Waiting for …” and "Thread[n]" are described elsewhere in this section.)

Processing updates from AFN=afn, ABSN=absn, SEG=seg, INX=inx, DMSII Time=timestamp

[(lag time = hh:mi:ss)]

These lines display the current StateInfo, and when processing audit files, is followed by the lag time.

Server = {DBServer | DBEnterprise}, Audit_access_rpc = {DBRead | DBWait} [, Audit file origin = AF_origin]

These lines provide the origin of the audit file updates. Possible values for AF_origin include DBServer-based operations HostAudit and DBTanker and DATABridge Enterprise Server-based operations IndirectDisk, DirectDisk and DBECache.

[Waiting for reason_for_wait, wait_time = mmmm ms]

Log File: "name"

These lines indicate that the main thread of the program is waiting for an event or a resource to become available. Values for reason_for_wait include: TCP/IP input; SQL execution to complete; bulk loader thread to complete; backlog to dissipate; index thread to complete; mutex name; and semaphore name. These messages are described individually within this section.

Trace: {on , mask = 0xhhhh, trace_file = "name" | off}

This line indicates whether tracing is enabled and provides the trace mask value and name of the trace file (if any).

Verbose: {on | off}, Scheduling: {on | off}

This line indicates whether the verbose option and scheduling are enabled (on).

[Stop processing updates on mm/dd/yyyy @hh:mm:ss]

[Stop processing updates at first QPT of AFN dddd]

[Update Worker Thread[n] {waiting for reason_for_wait, wait_time = dddd | running | terminated}

… ]

These lines indicate whether the Client stops processing updates at the first QPT of the specified audit file or at the specified date and time.

Commit ABSN increment will be set to nnn at next quiet point

This message is displayed in response to a dbutility COMMIT ABSN nnnn command.

Commit Parameters: ABSN_inc = aaa, UPDATE_inc = bbb, TIME = ccc, DMS_Txn = ddd

DBserver TXN Group Statistics (cumulative):

Commits = ddd, Avg UPDATE_inc = nnn.nn, Avg Trans time = sss sec, Avg ABSN_inc = ddd

Rollbacks = ddd, Avg UPDATE_inc = nnn.nn, Avg Trans time = sss sec

This message is displayed in response to a dbutility COMMIT STATS command.

Commit TIME increment will be set to nnn at next quiet point

This message is displayed in response to a dbutility COMMIT TIME ssss command.

Commit TXN increment will be set to nnn at next quiet point

This message is displayed in response to a dbutility COMMIT TRAN nnnn command.

Commit UPDATE increment will be set to nnn at next quiet point

This message is displayed in response to a dbutility COMMIT UPDATE nnnn command.

Connection to server not yet established

This message indicates that the console operator issued an SSTATS command before the Client established a connection with the Server Accessory.

Console Input: 'text'

The Client logs all console commands issued by the operator, ensuring a record of all such commands. This message, which only appears in the log file, contains the console command text as entered by the operator.

Console_Reader thread exiting

This message, which only appears when the -v option is enabled, indicates that the thread which is handling the console commands is about to terminate.

Console_Reader thread starting

This message, which only appears when the -v option is enabled, indicates that the thread handling the console commands was successfully created and that it has started executing.

dbutility will stop after AFN dddd

This message, in response to a QUIT AFTER afn command, indicates that the Client will stop after the given audit file is processed.

dbutility will stop at hh:mm:00

This message, in response to a QUIT AT hh:mm command, indicates that the Client will stops at the specified time.

dbutility will stop at the next quiet point

This message, in response to a QUIT command, indicates that the Client stops at the next quiet point.

I/O time = nn.nn seconds

This message is one of several lines of output produced by the SSTATS command. It shows the I/O time used by the Server Accessory worker.

Log file switched to "filename" (Operator Keyin)

This message is displayed in response to a successful LOGSWITCH command, which closes the current log file and starts a new one with the given name.

Operator commands: cmd_list

This message displays a list of the available console commands when a HELP command is issued.

Performance statistics not available

This message indicates that the operator issued a PSTATS command. However, performance statistics are not currently available because the Client has not yet started receiving extracts or updates from the DATABridge Engine or DATABridge Enterprise Server.

Performance statistics only available during process and clone commands

This message indicates that the operator issued a PSTATS command while executing a dbutility command other than process or clone.

Scheduling {disabled | re-enabled}

This message, in response to a SCHED command, indicates that the operator either disabled scheduling, or enabled scheduling that was previously disabled by a SCHED OFF command. This command takes effect only when it is time to schedule the next process command and does not affect the currently executing process command. If scheduling is disabled, the process command simply exits at this point.

Server statistics only available during a process or clone command

This message indicates that the operator issued a SSTAT command during a dbutility command other than the process or clone.

Server statistics will be displayed after next quiet point

This message indicates that the server statistics are not available by Client request until the next quiet point. This is the standard response to the SSTATS console command.

Server Statistics:

Usercode: usercode

Priority: nn

Processor time: nn.nnnn seconds

I/O time: nn.nnnn seconds

ReadyQ time: nn.nnnn seconds

Support version: vv.vvv.vvvv [timestamp]

Support: (usercode) filespec

Filter: name

These messages are the result of the dbutility SSTATS command, which requests the server statistics at the next quiet point when the Client is in control of the communications channel to the server. Some of these output lines may be omitted if they are not applicable. Usercode shows the USERCODE under which DBServer is run. Priority shows the priority of the Server Accessory worker task. Processor time displays the processor time used by the Server Accessory worker. I/O time displays the I/O time used by the Server Accessory worker. ReadyQ time displays the ready queue time used by the Server Accessory worker; this is time spent when the task is ready to run but cannot get a processor.

Note: If the -v option is enabled, this message will include additional lines of output. These lines are typically suppressed by the Client because the information is redundant.

Statistics function not supported by server

This message indicates that the statistics function is not supported by the Server Accessory because it predates the implementation of RPC currently in use.

Trace file switched to "filename"

This message is displayed in response to a successful TSWITCH command, which closes the current trace file and starts a new one with the specified name.

Trace_options set to 0xdddd

This message, in response to a TRACE command, indicates that tracing is now set to the specified value.

Update Worker thread[nn] {running | terminated}

These messages are part of the STATUS command output when multi-threaded updates are enabled. See the entry "Client State.." earlier in this section.

running indicates that the thread is actively executing the SQL for an update.

terminated indicates that the thread has exited. This only happens when the Client is shutting down.

Update Worker thread[nn] {waiting for wait_condition, wait_time = ssss ms | running | terminated}

These messages, which are part of the STATUS command output when multi-threaded updates are enabled, indicate the state of individual update worker threads. See the preceding "Client State.." entry. If the thread is waiting for an event, the event is shown in wait_condition and ssss is the amount of time (in milliseconds) the thread has been waiting.

Possible values for wait_condition include:

work which indicates that the thread is idle

SQL execution to complete which indicates that the thread is waiting for the database API code to return the control to it after the update is completed.

waiting for mutex name which indicates that the thread is waiting on a mutex whose name is provided. If this condition do not clear in a reasonable amount of time the program might be deadlocked.

waiting for semaphore name which indicates that the thread is waiting for the specified semaphore to be posted. If this condition does not clear in a reasonable amount of time, the program might be deadlocked.

unknown status dd which indicates that the thread is invalid because of an internal error in the program.

Verbose flag set to {true | false}

This message, which is a response to a VERBOSE command, indicates whether the verbose option is set.

Waiting for backlog to dissipate, wait_time = mmmm ms

(Windows only) This message is one of several lines of output produced by the STATUS command. It indicates that dbutility has been waiting for the backlog caused by excessive posting for the bulk_loader thread or index thread work queues to dissipate. If this number is very large, it may indicate an internal error in the Client.

Waiting for bulk loader thread to complete, wait_time = mmmm ms

(Windows only) This message is one of several lines of output produced by the STATUS command. It indicates that dbutility has been waiting for the specified amount of time for the bulk_loader thread to complete. If this number is very large, the bulk_loader thread may be blocked waiting for a database resource to become available.

Waiting for index thread to complete, wait_time = mmmm ms

(Windows only) This message is one of several lines of output produced by the STATUS command. It indicates that dbutility has been waiting for the specified amount of time for the index thread to complete. If this number is very large, the bulk_loader thread may be blocked waiting for a database resource to become available.

Waiting for mutex name, wait_time = mmmm ms

A thread that needs access to a critical section of code must first acquire the mutex. If the mutex is in use, the thread must wait until it becomes available. If a thread is stuck waiting for a mutex, this is usually an indication of a deadlock. In such cases, all you can do is abort the run.

Waiting for semaphore name, wait_time = mmmm ms

If a thread needs to execute code after another thread has finished a related task, it will typically do that with a semaphore, unless the associated thread has already posted the semaphore. When the associated thread is done it posts the semaphore. If a thread is stuck waiting for a mutex, it is usually an indication of a deadlock, which requires that you abort the run.

Waiting for SQL execution to complete, wait_time = mmmm ms

One of several lines of output produced by the STATUS command, this message indicates that dbutility has been waiting for the specified amount of time for an executed SQL statement to complete. If this number is very large, execution is blocked in the database server.

Waiting for TCP/IP input from DBServer, wait_time = mmmm ms

One of several lines of output produced by the STATUS command, this message indicates that dbutility has been waiting for the specified amount of time for input from the Server Accessory. If this number is very large, the Server Accessory is blocked waiting for some event (for example, for the operator to make an audit file available).