Hitachi

Hitachi Advanced Database Setup and Operation Guide

10.11.2 Information that is output as SQL trace information

The following information is output as SQL trace information:

Note

If SQL statement processing stops due to an error, any SQL trace information that could not be acquired at that point is not output.

The following subsections explain the SQL trace information items that are output.

Organization of this subsection

(1) HADB server version information

The following shows an example of HADB server version information that is output:

Hitachi Advanced Data Binder 03-01 Aug  5 2015 18:32:45
Explanation

  • The underlined portion is the HADB server's version.

  • Following the underlined portion, additional version information is output in the following format:

    MMM DD YYYY hh:mm:ss

    MMM: Month (three-letter abbreviation of the month name)

    DD: Date

    YYYY: Calendar year

    hh:mm:ss: Time

Note

The HADB server version information is output at the beginning of an SQL trace file.

To Page Top

(2) SQL statement execution information

This subsection explains an example of the SQL statement execution information that is output and the items that are included in the output.

(a) Example of output of SQL statement execution information

The following shows an example of SQL statement execution information that is output:

[Figure]

(b) Items that are output as SQL statement execution information

The following table lists and describes the items that are output as SQL statement execution information.

Table 10‒10: Items that are output as SQL statement execution information

No.

Item name

Description

1

con_id

Connection ID

2

con_num

Connection sequence number since the HADB server started.

3

stmt_hdl

Statement handle assigned to the SQL statement.

4

sql_serial_num

SQL statement sequence number since the connection was established.

5

call

Call type subject to SQL statement execution information. Table 10‒11: Correspondence between call types and processes that were performed describes the correspondence between call types that are output and processes that were performed.

A call is the unit of connection establishment or termination, transaction normal termination or cancellation, or database operation using an SQL statement.

When SQL trace information is set to be output for each SQL statement, the SQL statement execution information is output when execution of an SQL statement (execution of CLOS, EXEC, and EXDI for each call) is completed. In such a case, SQL is displayed in the call column.

6

sqlcode

SQLCODE.

For details about how SQLCODE corresponds to messages, see Interpreting SQLCODEs in the manual HADB Messages.

7

sqlstate

SQLSTATE.

For details about SQLSTATE, see List of SQLSTATE values in the manual HADB Messages.

8

start_time

Processing start time.

When SQL trace information is set to be output for each call, this item outputs the start time of each call.

When SQL trace information is set to be output for each SQL statement, this item outputs the start time of the first call described in Table 10‒12: Calls that are executed when the call type is SQL.

9

end_time

Processing termination time.

When SQL trace information is set to be output for each call, the termination time of each call is output.

When SQL trace information is set to be output for each SQL statement, the termination time of the first call executed is output.

10

exe_time(us)

Processing execution time in microseconds.

  • When SQL trace information is set to be output for each call

    The difference between the start time and the end time of each call is output.

    If an implicit commit or rollback occurs during the call processing, that processing time is included in this execution time. For the execution time of FETC for the second or any subsequent fetch operation, the sum of the execution times of all fetch operations is output, not the difference between the start time and the end time that is output as the same SQL statement execution information.

  • When SQL trace information is set to be output for each SQL statement

    The sum of the execution times of all calls is output.

11

rows

Number of rows subject to processing.

This information is output when the call type is FETC, EXEC, EXDI, or SQL.

  • When the call type is FETC

    For the first fetch operation, 0 or 1 is output. For a subsequent fetch operation, the number of rows fetched during the second through the last fetch operations is output.

  • When the call type is EXEC or EXDI

    If the SQL statement executed is DELETE, INSERT, or UPDATE, the number of rows that were updated is output. If the SQL statement executed is other than these, 0 is output.

  • When the call type is SQL

    If the SQL statement executed is SELECT, DELETE, INSERT, or UPDATE, the number of rows subject to processing is output. If the SQL statement executed is other than these, 0 is output.

12

tran_id

Transaction ID, which is a sequence number assigned since the database was initialized

13

trn_iso_lv

Transaction isolation level.

  • READ_COMMITTED: Output when the transaction isolation level is READ COMMITTED.

  • REPEATABLE_READ: Output when the transaction isolation level is REPEATABLE READ.

14

trn_access_mode

Transaction access mode.

  • READ_WRITE: Output when the transaction access mode is the read/write mode.

  • READ_ONLY: Output when the transaction access mode is the read-only mode.

15

sql_order_mode

Sort order for character string data.

  • BYTE: Output when character string data is sorted by bytecode.

  • ISO: Output when character string data is sorted by sort code.

16

cursor_holdability

Cursor operation.

  • CLOSE_CURSORS_AT_COMMIT: Output when the cursor is closed during the commit operation.

  • HOLD_CURSORS_OVER_COMMIT: Output when the cursor is not closed during the commit operation.

The cursor operation is output in the following cases:

  • The call type is OPEN, FETC, or CLOS.

  • The call type is SQL and the executed SQL statement is the SELECT statement.

17

message_log_info

Message log information.

This is the client process ID and connection sequence number for a message that is output to the message log file.

In the event of an SQL statement error, you can determine the cause of the error by checking the message log information against this client process ID and connection sequence number displayed in the message. For details, see 10.11.7 Using SQL trace information to determine the cause of errors in SQL statements.
Notes:

  • When the call type is CNCT, DISC, or DISP, no values are output for stmt_hdl, sql_serial_num, rows, tran_id, trn_iso_lv, trn_access_mode, and sql_order_mode.

  • When the call type is CMIT or RLBK, no values are output for stmt_hdl, sql_serial_num, and rows.

  • If a statement handle satisfies any of the following conditions, no values are output for call, sqlcode, sqlstate, start_time, end_time, exe_time, and rows (this does not apply to a statement handle resulting in an error when the transaction was settled due to an error in the SQL statement):

    • The call immediately preceding the subject statement handle resulted in an error.

    • The type of the call immediately preceding the subject statement handle was OPEN (the unit of SQL trace information output is a call).

    • The type of the call immediately preceding the subject statement handle was FETC and a fetch operation was performed only once (the unit of SQL trace information output is a call).

Table 10‒11: Correspondence between call types and processes that were performed

No.

Call type#1 (information output to call)

Processing that was performed

Unit of output#2

Additional information that is output#3

1

PREP

Preprocessing of SQL statements

Call

2, 4

2

OPEN

Cursor open processing

3, 4

3

CLOS

Cursor close processing

4, 6

4

FETC

First fetch operation or the second through the last fetch operations#4

4

5

EXEC

SQL statement execution#5

3, 4, 6

6

EXDI

Preprocessing and execution of SQL statements

2, 4, 6

7

CMIT

Commit processing

Call or SQL statement

4

8

RLBK

Rollback processing

4

9

CNCT

Connection establishment (for application programs and commands)

1, 4, 5, 7

10

DISC

Disconnection

4, 5, 7

11

DISP

Disconnection when using the connection pool function

4

12

SQL

Output by SQL statement#6, #7

2, 3, 4, 6
#1

For information about the correspondence between call types and executed JDBC methods, see (d) Correspondence between executed JDBC methods and the call types that are output.

For information about the correspondence between call types and executed ODBC functions, see (e) Correspondence between executed ODBC functions and the call types that are output.

For information about the correspondence between call types and executed CLI functions, see (f) Correspondence between executed CLI functions and the call types that are output.

#2

This is the output unit of the SQL trace information specified in the adb_sql_trc_level server definition operand or the adbchgsqltrc command.

#3

This is the information that is output in addition to the SQL statement execution information. The numbers in the table correspond to the following:

1: Client-definition information and connection status information

2: Executed SQL statement and access path information

3: Dynamic parameter information

4: Transaction information

5: Authorization identifier information

6: SQL statement statistical information and access path statistical information

7: Line delimiting the establishment or termination of a connection

#4

If the call type is FETC, this does not mean that as many sets of SQL trace information are output as there are fetches. If the fetch count is 2 or greater, only two sets of SQL statement execution information (one set for the first fetch operation and one set for all the subsequent fetch operations combined) are output regardless of how many times a fetch operation was performed. If the fetch count is 1, only one set of SQL statement execution information is output.

#5

If batch transfer of dynamic parameter values is performed, only one set of SQL statement execution information is output for the EXEC SQL statement. For details about batch transfer of dynamic parameter values, see Batch transfer of dynamic parameter values in the HADB Application Development Guide.

#6

If you execute the adbexport command by specifying an SQL statement file, information will be output as the execution information about a single SQL statement even if the output level is CALL. In this case, SQL is output as the call type.

#7

When SQL trace information is to be output for each SQL statement, one set of SQL statement execution information is output for each of the calls listed in the Calls that are executed column in Table 10‒12: Calls that are executed when the call type is SQL. In this case, SQL is output as the call type.

Table 10‒12: Calls that are executed when the call type is SQL

No.

Type of SQL statement

Calls that are executed#1

1

Update SQL statement

PREP → EXEC

2

EXEC (when EXEC is executed immediately after the call in No. 1 was executed)

3

EXDI

4

Definition SQL statement

PREP → EXEC

5

EXDI

6

Retrieval SQL statement

PREP → OPEN → FETC → [FETC] → CLOS (when the cursor is closed explicitly)

7

PREP → OPEN → FETC → [FETC] (when the cursor is not closed explicitly#2)
Note:

A call type enclosed in square brackets ([]) might not be executed.

#1

If an error occurs during execution of an SQL statement, SQL statement execution information is output as shown in (c) Output of SQL statement execution information in the event of an error during execution of an SQL statement (when the call type is SQL).

#2

This applies when a statement handle was released or a transaction was settled without closing the cursor. This does not apply when the cursor_holdability (cursor operation) explained in Table 10‒10: Items that are output as SQL statement execution information is HOLD_CURSORS_OVER_COMMIT, because the cursor is not closed even when commit processing is performed.

(c) Output of SQL statement execution information in the event of an error during execution of an SQL statement (when the call type is SQL)

If an error occurs during execution of an SQL statement, one set of SQL statement execution information is output for each of the following calls:

If the only type of call resulting in an error is FETC, the processing depends on whether implicit rollback occurred when the error occurred:

  • Implicit rollback occurred when the error occurred.

    Among the calls shown in Table 10‒12: Calls that are executed when the call type is SQL, a set of SQL statement execution information is output for the FETC that caused the error and for the calls that preceded it.

  • Implicit rollback did not occur.

    FETC resulting in the error is not treated as the completion of the retrieval SQL statement execution. Execution of the retrieval SQL statement is regarded as having been completed when the corresponding CLOS processing is completed. In this case, a set of SQL statement execution information is output for each call shown as a retrieval SQL statement in Table 10‒12: Calls that are executed when the call type is SQL.

The following are examples of when SQL statements result in an error:

  • When retrieval SQL statements were executed, OPEN resulted in an error.

    SQL statement execution information for PREP and OPEN is combined into one set, and one set of SQL statement execution information is output for each SQL statement.

  • When retrieval SQL statements were executed, FETC resulted in an error and implicit rollback occurred.

    SQL statement execution information for PREP, OPEN, [FETC], and FETC is combined into one set, and one set of SQL statement execution information is output for each SQL statement.

  • When update SQL statements were executed, PREP resulted in an error.

    SQL statement execution information for PREP is output as a set of SQL statement execution information for each SQL statement.

(d) Correspondence between executed JDBC methods and the call types that are output

The following table shows the correspondence between executed JDBC methods and the call types that are output.

Table 10‒13: Correspondence between executed JDBC methods and the call types that are output

No.

Executed JDBC method

Call type that is output

1

connect(String url, Properties info) of the Driver interface

CNCT

2

close() of the Connection interface

CMIT, DISC, DISP

3

commit() of the Connection interface

CMIT

4

prepareStatement(String sql) of the Connection interface

PREP

5

prepareStatement(String sql, int resultSetType, int resultSetConcurrency) of the Connection interface

6

prepareStatement(String sql, int resultSetType, int resultSetConcurrency, int resultSetHoldability) of the Connection interface

7

rollback() of the Connection interface

RLBK

8

close() of the Statement interface

CLOS, CMIT

9

execute(String sql) of the Statement interface

PREP, OPEN, EXEC, EXDI, CLOS, CMIT, RLBK

10

executeBatch() or executeLargeBatch() of the Statement interface

PREP, EXEC, EXDI, CMIT, RLBK

11

executeQuery(String sql) of the Statement interface

PREP, OPEN, CLOS, CMIT

12

executeUpdate(String sql) or executeLargeUpdate(String sql) of the Statement interface

PREP, EXEC, EXDI, CMIT, RLBK

13

getMoreResults() of the Statement interface

CLOS

14

execute() of the PreparedStatement interface

PREP, OPEN, EXEC, CLOS, CMIT, RLBK

15

executeQuery() of the PreparedStatement interface

PREP, OPEN, CLOS, CMIT, RLBK

16

executeUpdate() or executeLargeUpdate() of the PreparedStatement interface

PREP, EXEC, CMIT, RLBK

17

absolute(int row) of the ResultSet interface

FETC

18

afterLast() of the ResultSet interface

19

beforeFirst() of the ResultSet interface

20

first() of the ResultSet interface

21

isAfterLast() of the ResultSet interface

22

isBeforeFirst() of the ResultSet interface

23

ilast() of the ResultSet interface

24

irelative(int rows) of the ResultSet interface

25

isLast() of the ResultSet interface

26

next() of the ResultSet interface

27

close() of the ResultSet interface

CLOS, CMIT

28

getColumns(String catalog, String schemaPattern, String tableNamePattern, String columnNamePattern) of the DatabaseMetaData interface

PREP, OPEN

29

getCrossReference(String primaryCatalog, String primarySchema, String primaryTable, String foreignCatalog, String foreignSchema, String foreignTable) of the DatabaseMetaData interface

30

getExportedKeys(String catalog, String schema, String table) of the DatabaseMetaData interface

31

getImportedKeys(String catalog, String schema, String table) of the DatabaseMetaData interface

32

getIndexInfo(String catalog, String schema, String table, boolean unique, boolean approximate) of the DatabaseMetaData interface

33

getPrimaryKeys(String catalog, String schema, String table) of the DatabaseMetaData interface

34

getSchemas(String catalog, String schemaPattern) of the DatabaseMetaData interface

35

getTablePrivileges(String catalog, String schemaPattern, String tableNamePattern) of the DatabaseMetaData interface

36

getTables(String catalog, String schemaPattern, String tableNamePattern, String[] types) of the DatabaseMetaData interface

37

getSchemas() of the DatabaseMetaData interface

38

getConnection() of the DataSource interface

CNCT

39

getConnection(String username, String password) of the DataSource interface

40

close() of the PooledConnection interface

DISC

41

getConnection() of the PooledConnection interface

CNCT

(e) Correspondence between executed ODBC functions and the call types that are output

The following table shows the correspondence between executed ODBC functions and the call types that are output.

Table 10‒14: Correspondence between executed ODBC functions and the call types that are output

No.

Executed ODBC function

Call type that is output

1

SQLPrepare(W)

PREP

2

SQLExecute

PREP, EXEC, OPEN, CMIT

3

SQLExecDirect(W)

PREP, EXEC, CMIT

4

SQLParamData

EXEC, OPEN, CMIT

5

SQLFetch

FETC

6

SQLColumns(W)

PREP, OPEN

7

SQLForeignKeys(W)

8

SQLPrimaryKeys(W)

9

SQLStatistics(W)

10

SQLTablePrivileges(W)

11

SQLTables(W)

12

SQLFreeStmt

CLOS, CMIT

13

SQLCloseCursor

14

SQLEndTran

CMIT, RLBK

15

SQLDisconnect

CMIT, DISC

16

SQLFreeHandle

CMIT

17

SQLSetConnectAttr(W)

18

SQLConnect(W)

CNCT, DISC

19

SQLDriverConnect(W)

20

SQLBrowseConnect(W)

(f) Correspondence between executed CLI functions and the call types that are output

The following table shows the correspondence between executed CLI functions and the call types that are output.

Table 10‒15: Correspondence between executed CLI functions and the call types that are output

No.

Executed CLI function

Call type that is output

1

a_rdb_SQLPrepare()

PREP

2

a_rdb_SQLExecute()

OPEN, EXEC

3

a_rdb_SQLCloseCursor()

CLOS

4

a_rdb_SQLFetch()

FETC

5

a_rdb_SQLExecDirect()

EXDI

6

a_rdb_SQLEndTran()

CMIT, RLBK

7

a_rdb_SQLConnect()

CNCT

8

a_rdb_SQLDisconnect()

DISC

To Page Top

(3) Client-definition information

The following shows an example of client-definition information that is output.

■ Example of output of client-definition information

[client definitions]
adb_clt_ap_name="SAMPLE"
adb_clt_fetch_size=1024
adb_clt_group_name="test_group"
adb_clt_sql_order_mode="ISO"
adb_clt_sql_text_out="Y"
adb_clt_trn_access_mode="READ_WRITE"
adb_clt_trn_iso_lv="READ_COMMITTED"
adb_dbbuff_wrktbl_clt_blk_num=256
adb_sql_exe_hashflt_area_size=200
adb_sql_exe_hashgrp_area_size=4800
adb_sql_exe_hashtbl_area_size=2000
adb_sql_exe_max_rthd_num=0
adb_sql_prep_dec_div_rs_prior="FRACTIONAL_PART"
adb_sql_prep_delrsvd_use_srvdef="Y"

If the connection was established by an application program, the client-definition information that has been applied to that application program is output. If the connection was established by a command, no client-definition information is output.

Each operand value output to the client-definition information is the value applied to the application program, not the value specified in the client definition. For example, if the adb_sql_exe_max_rthd_num operand value specified in the client definition was changed to the default value by the HADB server because the specified value was invalid, the value assumed by the HADB server is output.

Note

Client-definition information is output in the following cases:

  • The call type is CNCT and CNCT terminated normally.

  • The first transaction was started after the adbchgsqltrc -s command was executed and SQL trace information was output (the client-definition information for the connection that started the transaction is output).

To Page Top

(4) Connection status information

The following shows an example of the connection status information that is output.

■ Example of output of the connection status information (when the connection was established by an application program)

[connection status]
client_type=AP(JDBC)
client_ip=127.0.0.1
connect_time=2015/07/31 21:54:41
client_process_id=0
connection_information=000010000000001-0000181584fb6700

■ Example of output of connection status information (when the connection was established by a command)

[connection status]
client_type=command(adbimport)
client_ip=127.0.0.1
connect_time=2015/07/31 16:10:37
client_process_id=30422
connection_information=000010000000003-000073b601e46700

The following table lists and describes the items that are output as connection status information.

Table 10‒16: Items that are output as connection status information

No.

Item name

Description

1

client_type

Type of HADB client.

  • For accesses from JDBC drivers: AP(JDBC)

  • For accesses from programs other than the JDBC drivers: AP(C library)

  • For commands: command(command-name)

    Example: command(adbimport)

2

client_ip

IP address of the HADB client

3

connect_time

Time when the connection was established

4

client_process_id

Process ID of the HADB client.

If a JDBC drive is used, 0 is output.

5

connection_information

Connection information (the information that is output for connection information in the KFAA81000-I message)
Note

Connection status information is output in the following cases:

  • The call type is CNCT and CNCT terminated normally.

  • The first transaction was started after the adbchgsqltrc -s command was executed and SQL trace information was output (the connection status information for the connection that started the transaction is output).

To Page Top

(5) Executed SQL statement and access path information

The following shows an example of executed SQL statement and access path information that is output.

■ Example of output of executed SQL statement and access path information

[SQL]
SELECT * FROM "T1" WHERE "C1"=? AND "C2"=? AND "C3"=?
 
[access path]
<<Tree View>>
 
     1 QUERY : 1
     2   SELECT STATEMENT
     3   +-TABLE SCAN(ADBUSER01.T1)
 
 
<<SQL Info >>
 
Version           : 03-01(Jul 31 2015 21:31:44)
Transaction ID    : 4342
Connection Number : 1
SQL Serial Number : 1
Explanation

  • [SQL]

    Outputs the executed SQL statement.

    Asterisks (*) are output for the password portion of the ALTER USER or CREATE USER statement.

    The executed SQL statement is output as is even if it contains unprintable special characters.

  • [access path]

    Outputs the access path information. For details about the items that are output as access path information, see How to use access paths (how to use SQL statement execution plans) in the HADB Application Development Guide.

Note

The executed SQL statement and the access path information are output in the following cases:

  • The call type is PREP.#

  • The call type is EXDI.

  • The call type is SQL.

#

The access path information is output when PREP terminates normally. If PREP did not terminate normally, only the executed SQL statement is output.

To Page Top

(6) Dynamic parameter information

The following shows an example of dynamic parameter information that is output.

■ Example of output of dynamic parameter information

[param]
param_no type      len1  len2  data
-------- --------- ----- ----- ----
       1 int           8       1
       2 char          2       'ab'
       3 dec           7     3 1234.567

The following table lists and describes the items that are output as dynamic parameter information.

Table 10‒17: Items that are output as dynamic parameter information

No.

Item name

Description

1

param_no

Sequence number of the dynamic parameter in the SQL statement

2

type

Data type of the dynamic parameter

3

len1

Parameter length

4

len2

Parameter length attribute. If there is no parameter length attribute, this item is not output.

For details about parameter lengths and parameter length attributes, see a_rdb_SQLDescribeParams() (acquire dynamic parameter information) in the HADB Application Development Guide.

5

data

Data bound to the dynamic parameter

The following table shows the output format for the dynamic parameter information.

Table 10‒18: Output format for the dynamic parameter information

No.

Data type

type

len1

len2

Output format

1

INTEGER

int

8

None

Decimal

2

DECIMAL(m,n)#1

dec

m

n

Decimal

3

SMALLINT

smallint

4

None

Decimal

4

DOUBLE PRECISION

double

8

None

MantissaEexponent

The mantissa and exponent are both output in decimal.

5

CHARACTER(n)

char

n

None

'character-string'

6

VARCHAR(n)

varchar

n

None

'character-string'

If the actual length is 0, '' is output.

7

DATE

date

4

None

Predefined output representation for date data#2

8

TIME(p)#3

time

3 + ↑p ÷ 2↑

p

Predefined output representation for time data#2

9

TIMESTAMP(p)#3

timestamp

7 + ↑p ÷ 2↑

p

Predefined output representation for time stamp data#2

10

BINARY(n)

binary

n

None

X'hexadecimal-value'

11

VARBINARY(n)

varbinary

n

None

X'hexadecimal-value'

If the actual length is 0, X'' is output.

12

ROW

row

Row length

None

X'hexadecimal-value'
Legend:

m, n, and p: Positive integer

#1

If the data type is DECIMAL, len1 acquires the precision. len2 acquires scaling.

#2

For details about the predefined output representations, see Predefined character-string representations in the manual HADB SQL Reference.

#3

If the data type is TIME or TIMESTAMP, len1 acquires the data length. len2 acquires the number of digits in the fractional seconds.

■ Output rules for dynamic parameter information

  • If bound data is the null value, NULL is output.

  • The dynamic parameter information is output as is even when it contains unprintable special characters.

  • If only a dynamic parameter is specified in the NULL predicate and data that is not the null value is bound, nothing is output in the data column. If the null value is bound, NULL is output in the data column.

  • If batch transfer of dynamic parameter values is performed, the headers (param_no, type, len1, len2, data, and separator line) and data are output for each dynamic parameter set. Note that [param] is output only once per batch transfer.

    For details about batch transfer of dynamic parameter values, see Batch transfer of dynamic parameter values in the HADB Application Development Guide.

Note

Dynamic parameter information is output when both the following conditions are satisfied:

  • A dynamic parameter is specified in the SQL statement.

  • The call type is OPEN, EXEC, or SQL.

To Page Top

(7) Transaction information

The following shows an example of transaction information that is output.

■ Example of output of transaction information

[Figure]

The following table lists and describes the items that are output as transaction information.

Table 10‒19: Items that are output as transaction information

No.

Item name

Description

1

tran_id

Transaction ID, which is a sequence number assigned since the database was initialized

2

start_time

Transaction start time

3

end_time

Transaction end time

4

exe_time(us)

Transaction execution time in microseconds. This is the difference between the transaction start time and the transaction end time.

5

trn_iso_lv

Transaction isolation level.

  • READ_COMMITTED: Output when the transaction isolation level is READ COMMITTED.

  • REPEATABLE_READ: Output when the transaction isolation level is REPEATABLE READ.

6

trn_access_mode

Transaction access mode.

  • READ_WRITE: Output when the transaction access mode is read/write mode.

  • READ_ONLY: Output when the transaction access mode is read-only mode.

7

sql_order_mode

Sort order for character string data.

  • BYTE: Output when character string data is sorted by bytecode.

  • ISO: Output when character string data is sorted by sort code.

8

~

The swung dash (~) is output as the separator line character for transaction information.
Note

Transaction information is output in the following cases:

  • The call type is CMIT or RLBK.

  • An implicit transaction settlement occurred.#

#

An implicit commit is executed when a definition SQL statement, TRUNCATE TABLE statement, or PURGE CHUNK statement terminates normally.

If the SQL statement results in an error, an implicit rollback might be executed. If this happens, the KFAA51001-E message will be output to the message log file.

An implicit commit is also executed when the connection is terminated during transaction processing.

To Page Top

(8) Authorization identifier information

The following shows an example of authorization identifier information that is output.

■ Example of output of authorization identifier information

When the call type is CNCT:
ADBUSER01 has been connected.
When the call type is DISC:
ADBUSER01 has been disconnected.
Explanation

The underlined portion is the authorization identifier that was specified when the connection was established by the application program.

If the connection was established by a command, the authorization identifier specified in the -u option of the command is output. If the -u option was omitted, no authorization identifier information is output even if the command connects to the HADB server.

Note

Authorization identifier information is output in the following cases:

  • The call type is CNCT and CNCT terminated normally.

  • The call type is DISC and DISC terminated normally.

To Page Top

(9) SQL statement statistical information

The following shows an example of SQL statement statistical information that is output. The example is in two parts because it consists of a large amount of data.

■ Example of output of SQL statement statistical information (part 1)

[Figure]

■ Example of output of SQL statement statistical information (part 2)

[Figure]

Explanation

The items that are output as SQL statement statistical information are the same as for the SQL statement statistical information for the adbstat command. For details about the items that are output, see Items that are output as SQL statement statistical information in the manual HADB Command Reference.

Note

SQL statement statistical information is output in the following cases:

  • The call type is CLOS (including when the statement handle was released or the transaction was concluded without closing the cursor).

  • The call type is EXEC, EXDI, or SQL.

To Page Top

(10) Access path statistical information

For an example of output of and output items for access path statistical information, see 10.11.3 Examples of output of and output items for access path statistical information.

To Page Top

(11) Line delimiting the establishment or termination of a connection

255 asterisks (*) are output as a line indicating where the connection was established or terminated.

■ Example of a line denoting connection establishment (when the call type is CNCT)

[Figure]

■ Example of a line denoting connection termination (when the call type is DISC)

[Figure]

Note

A line delimiting the establishment or termination of a connection is output in the following cases:

  • The call type is CNCT.

  • The call type is DISC and DISC terminated normally.

To Page Top

(12) SQL statement basic information

When SQL trace information is output for an SQL statement, basic information about the SQL statement is output. The following shows an example of SQL statement basic information that is output.

■ Example of output of SQL statement basic information

[Figure]

Explanation

  • con_id

    Outputs the connection ID.

  • con_num

    Outputs the connection sequence number since the HADB server started.

  • stmt_hdl

    Outputs the statement handle assigned to the SQL statement.

  • sql_serial_num

    Outputs the SQL statement sequence number since the connection was established.

To Page Top

All Rights Reserved. Copyright (C) 2012, 2020, Hitachi, Ltd.