Message

Description

Abort_Transaction:

This message indicates that the DATABridge Client is making an API call to rollback the current transaction group.

Begin_Transaction:

This message indicates that DATABridge Client is starting a transaction group.

BindColumnPtr, stmt=nnnn:

This message only appears when the configuration parameter aux_stmts has a nonzero value. It indicates that the columns involving a host variable in the SQL statement that was just parsed are being bound to a memory address. This message follows every Parse_SQL message.

Bind_Record: col=number, name=colname, ofs=number, size=number, type=number

This message appears when the various data columns referenced explicitly or implicitly in a select statement are bound to fields in a program structure. This messages lists the column number (col=number), item name (name=colname), offset of the field in the structure expressed as a hexadecimal number (entry ofs=number), size of the field (in bytes) expressed as a decimal number (size=number), and code for the sql_type of the column (type=number).

Close_Database:

This message indicates that a database session has been closed. The DATABridge Client typically uses two database sessions at a time.

Commit_Transaction:

This message indicates that the DATABridge Client is making an API call to commit the current transaction group.

Execute_PreParsed_
SQL for stmt number, table 'name'

This message is immediately followed by the SQL_DATA message, which displays the actual values of the host variables for the pre-parsed SQL statement that is being executed.

Execute_SQL:

This message indicates that the DATABridge Client called the Execute_SQL procedure, which executes most SQL statements not involving host variables. This call is preceded by one or more calls on Process SQL, which constructs the SQL statements in a temporary buffer.

Execute_SQL_Direct:

This message indicates that the DATABridge Client called the Execute_SQL_Direct procedure, which executes SQL statements directly (versus from the buffer that Process_SQL creates).

Fetch_Results: No more rows

This message appears when the DATABridge Client loads the client control tables and indicates the no more rows are available in the select statement result.

Fetch_Results: Row retrieved

This message appears when the DATABridge Client loads the client control tables and indicates that the DATABridge Client successfully read the row when it retrieved the results of a select statement.

OCIBindByName: col_name = 'name', addr = 0xhhhhhhhh, len = 0xhhhh

This message, which is limited to the DATABridge Client for Oracle, indicates that the given column in the parsed SQL statement was bound to a host variable at the given address and the given length.

Open_Database: user=userid, pwd=******,
{db=database | data source = src}, rslt=dbhandle

This message indicates that the DATABridge Client established a database session with the given parameters. The value dbhandle is the address of the internal structure used to hold the connection parameters and is expressed as a hexadecimal number. The DATABridge Client typically uses two database sessions. The database designation (db=database) refers to the Oracle client, while all other clients use data_source.

Open_Stmt: Opened stmt nnnn

This message indicates that the Client allocates a new stmt structure associated with a SQL statement that uses host variables. The Client allocates a maximum of auxiliary statements (configuration file parameter aux_stmts) before reusing these structures with the least-recently used algorithm.

Open_Stmt: Opened stmt number

This message is limited to the DATABridge Client for Oracle when the configuration parameter aux_stmts has a nonzero value. It indicates that Oracle is creating a new cursor. The DATABridge Client uses an algorithm that looks for the least used cursor to ensure that the most frequently used cursors are not deallocated.

Parse_SQL: SQL[number]=stmt

This message indicates that the SQL statement involving a host variable is being parsed using the stmt in question.

Using host variables improves performance by only parsing statements, binding the host variables to specific columns, and executing the statement multiple time after setting the host variables to the desired values.

Process_SQL:
SQL = SQLText

This message, which should not be confused with a similar SQL tracing message, overrides the SQL trace when both SQL and API tracing are enabled.

SQLBindParameter: col_no = nn, addr = 0xhhhhhhhh, len = 0xhhhh, ind_addr = 0xhhhhhhhh, ind = nn

This message, which applies to all ODBC and CLI clients, indicates that the given column in the prepared SQL statement was bound to a host variable at the given address and the given length. The ind column is an indicator that is used to mark columns as being null.

SQL_DATA[number]=
...|...|...

This message, which should not be confused with a similar SQL tracing message, overrides the SQL trace when both SQL and API tracing are enabled.