Nonstop Database, HiRDB Version 9 UAP Development Guide
ADO.NET 2.0-compatible HiRDB.NET Data Provider can collect method traces as troubleshooting information.
You can collect method trace information by specifying appropriate values in the PDCLTPATH and PDDNDPTRACE client environment definitions. For details about the client environment definitions, see 6.6 Client environment definitions (setting environment variables).
The following rules apply to method trace output:
This subsection shows and explains an example of method trace output.
[1][1742][sds01][12345678][HiRDB_Data_Provider20][08.04.0.0] 1 2 3 4 5 6 |
[0000000001][E][HiRDBCommand@12345678 ExecuteNonQuery][SID(2)][2008/08/27 1:29:10.123] 1 2 3 4 5 6 7 [Return=0] 8 [nArraySize=10] -| | : |-9 | [CommandText=INSERT INTO T1 VALUES(100)] -| [MessageText=KFPA11117-E Number of insert values not equal to number of insert columns] 10 [SQLCODE=-117] 11 [SQLWARN=0000] 12 location Hitachi.HiRDB.native.HiRDBcore.ClearSectionItems() -| location Hitachi.HiRDB.HiRDBConnection.Close() | location Hitachi.HiRDB.HiRDBConnection.Dispose(Boolean disposing) |-13 location Hitachi.HiRDB.HiRDBConnection.Finalize() -| |
Access type | Call type | Argument or property value | Return value | Error information | |
---|---|---|---|---|---|
Method | E | Call | Y | -- | -- |
R | Return (normal) | -- | Y | -- | |
Return (error) | -- | -- | Y | ||
Property | S | Setting (normal) | Y | -- | -- |
Setting (error) | Y | -- | Y | ||
G | Acquisition (normal) | -- | Y | -- | |
Acquisition (error) | -- | -- | Y |
Access type | Caller | Format | Remarks | |
---|---|---|---|---|
Method | E | HiRDBCommand.Execute HiRDBCommand.ExecuteDbDataReader HiRDBCommand.ExecuteNonQuery HiRDBCommand.ExecuteReader HiRDBCommand.ExecuteScalar |
CommandText=VALUE#1 Parameters.Count=VALUE PARAMETER_VALUE#2 |
If there are arguments, the argument information is output. |
Other | ARGUMENT#3=VALUE | -- | ||
R | HiRDBConnection.Open | ConnectionString=VALUE ServerVersion=VALUE |
-- | |
Other | Return=VALUE | -- | ||
Property | S | -- | PROPERTY#4=VALUE | -- |
G | -- | Return=VALUE | -- |
When the capacity of the current method trace file reaches a specified size, the system starts using the other method trace file for output of method trace information. When this occurs, the oldest method trace information in the switched-in method trace file is overwritten by new method trace information. For this reason, you should back up the contents of the method trace file upon termination of a UAP.
To determine which method trace file is being used currently, check the two files' last update dates and times. The file with the most recent update date and time is the current method trace file. Use the dir command or Explorer to check the update dates and times.
All Rights Reserved. Copyright (C) 2011, Hitachi, Ltd.