Connecting to Your Database
Troubleshooting Your Connection

The Database Trace tool records the internal commands that InfoMaker executes while accessing a database. You can trace a database connection in the development environment.

InfoMaker writes the output of Database Trace to a log file named PBTRACE.LOG (by default) or to a nondefault log file that you specify. When you enable database tracing for the first time, InfoMaker creates the log file on your computer. Tracing continues until you disconnect from the database.

COMMAND: (time)
   {additional_information}

FETCH NEXT: (77 MilliSeconds)
   dept_id=   dept_name=Business Services
FETCH NEXT: (4 MilliSeconds)
   dept_id=   dept_name=Corporate Management

By default, the Database Trace tool is turned off in InfoMaker. You can start it to trace your database connection.

Once you start tracing a particular database connection, InfoMaker continues sending trace output to the log until you do one of the following:

In the InfoMaker development environment, you can specify a nondefault name and location for the log file when you use Database Trace.

What you can do

By specifying a nondefault Database Trace log to use in the development environment, you can:

By default, InfoMaker writes Database Trace output to a log file named PBTRACE.LOG located in your Windows directory. You can override this default in the development environment by editing your InfoMaker initialization file.

How to do it

InfoMaker writes the output of the Database Trace tool to a file named PBTRACE.LOG (by default) or to a nondefault log file that you specify. To use the trace log, you can do the following anytime:

For information about where to find PBTRACE.LOG, see Location of the Database Trace log.

For instructions about specifying your own Database Trace log to use in the development environment, see Specifying a nondefault Database Trace log.

This section gives an example of Database Trace output that you might see in the log file and briefly explains each portion of the output.

The example traces a connection to an ODBC database named Sample. The output was generated while running an InfoMaker application that displays information about employees in each department. The SELECT statement shown retrieves information from the Employee table to display the names of employees in department 100.

The precision (for example, milliseconds) used when Database Trace records internal commands depends on your operating system's timing mechanism. Therefore, the timing precision in your Database Trace log might vary from this example.

Connect to database

DIALOG CONNECT TO TRACE SYCAdaptive Server Enterprise:
USERID=
SERVER=HOST12
DATA=QATEST
DPPARM=Release='12'

Prepare SELECT statement

PREPARE: 
SELECT employee.emp_id, employee.emp_lname,
employee.emp_fname, employee.dept_id FROM employee
WHERE ( employee.dept_id = 100 )
ORDER BY employee.emp_lname ASC (94 MilliSeconds)

Get column descriptions

DESCRIBE: (0 MilliSeconds)
name=emp_id,len=4,type=????,pbt5,dbt3,ct0,dec0
name=emp_lname,len=21,type=CHAR,pbt1,dbt1,ct0,dec0
name=emp_fname,len=21,type=CHAR,pbt1,dbt1,ct0,dec0
name=dept_id,len=4,type=????,pbt5,dbt3,ct0,dec0

Bind memory buffers to columns

BIND SELECT OUTPUT BUFFER (DataWindow):
(890 MilliSeconds)
name=emp_id,len=4,type=FLOAT,pbt3,dbt3,ct0,dec0
name=emp_lname,len=21,type=CHAR,pbt1,dbt1,ct0,dec0
name=emp_fname,len=21,type=CHAR,pbt1,dbt1,ct0,dec0
name=dept_id,len=4,type=FLOAT,pbt3,dbt3,ct0,dec0

Execute SELECT statement

EXECUTE: (0 MilliSeconds)

Fetch rows from result set

FETCH NEXT: (156 MilliSeconds)
      emp_id=   emp_lname=Jones   emp_fname=Alan
      dept_id=
FETCH NEXT: (0 MilliSeconds)
      emp_id=   emp_lname=Ciccone   emp_fname=Peter
      dept_id=
FETCH NEXT: (0 MilliSeconds)
      emp_id=   emp_lname=Houston   emp_fname=Mary
      dept_id=
FETCH NEXT: (0 MilliSeconds)
      emp_id=   emp_lname=Smith      emp_fname=Susan
      dept_id=
FETCH NEXT: (0 MilliSeconds)
      emp_id=   emp_lname=Stein      emp_fname=David
      dept_id=
FETCH NEXT: (0 MilliSeconds)
      emp_id=   emp_lname=Watson   emp_fname=Linda
      dept_id=
FETCH NEXT: (0 MilliSeconds)
Error 1 (rc 100)

Commit database changes

COMMIT: (55 MilliSeconds )

Disconnect from database

DISCONNECT: (0 MilliSeconds)

Shut down database interface

SHUTDOWN DATABASE INTERFACE: (203 MilliSeconds)