DB2Everyplace (DB2E) Data Collection document

Technote (FAQ)


Question

What information should be gathered before opening a PMR with DB2 Everyplace support?

Cause

What information should be gathered for DB2E support?

Answer

Please read all the information below and fill out the configuration form as best as you can where it applies to your environment and prepare all the log files available before opening a PMR with DB2 Everyplace support.

Server Environment:
- Server OS: (i.e AIX, Windows/2000, etc) = ????
- WEA bundle (if part of a bundle) Version = ????
- DB2 UDB Version & Fixpak = ????
- WebSphere Version & Fixpak = ????
- DB2 Everyplace EE Version (9.1)/fixpack = ????
- Subscription Type: (DataPropagator or JDBC) = ????
- Client Connection method: (i.e. RAS, Mocha W32, HTTP, etc) = ????
- Number of Active Clients Supported by the server = ????
- Source Database details if other than local DB2 (AS/400, Oracle, etc...) = ????

Client Environment:
- Device Type: (i.e. Palm, Win/CE, Win/32, etc) = ????
- Device Model: (for hardware devices) = ????
- Device OS: (i.e. PalmOS 3.5 / WIndows Mobile 5.0) ????
- DB2 Everyplace EE Version (9.1)/fixpack = ????

In addition to the above information, please also prepare to provide a detail problem description including any error codes issued on the server or client systems.

Generally, a detail level trace will also be required for problem diagnosis. It is advisable to delete any trace files before turning on the detail level trace, to keep things clean. Problem determination often will require reviewing the following logs from the \DB2Everyplace\Server\log directory.

dsyxxxx.trace xxxx=0000,0001,...
syncadapterinit.log
dsyadminxxxx.trace xxxx=0000,0001,...
dsyctldb.log

To enable/disable a detail level server trace do the following:

Defining the tracing level
By default, the DB2® Everyplace® Sync Server only logs error messages in the trace files. However, for diagnostic purposes, you might want to turn on tracing to include more detailed information. Use DSYTrace to turn on or off tracing.

The DSYTrace command changes the Trace.Level in file DSYGdflt.properties in the \<DSYPATH>\Server\properties\com\ibm\mobileservices\ directory, where <DSYPATH> is the directory where DB2 Everyplace is installed. For additional tracing options, type DSYTrace with no options at the command line or open the DSYGdflt.properties file in a text editor and modify the Trace.var parameters where var is a specific parameter variable.

1. To save all trace messages in a .trace file, turn tracing on.

    a. Open a command prompt.
    b. Change to the <DSYPATH>/Server/bin directory, where <DSYPATH> is the directory where DB2
    Everyplace is installed.
    c. At the command prompt, type: DSYTrace 1 -console
2. To save only error messages in a.trace file, turn tracing off.
    a. Open a command prompt.
    b. Change to the <DSYPATH>/Server/bin directory, where <DSYPATH> is the directory where DB2
    Everyplace is installed.
    c. At the command prompt, type: DSYTrace 0 -console

Please send all of the files from the list bellow that were created.

dsyxxxx.trace xxxx=0000,0001,...
syncadapterinit.log
dsyadminxxxx.trace xxxx=0000,0001,...
dsyctldb.log

Enabling tracing for the DB2 Everyplace Sync Client
Each time that you synchronize a mobile device, the DB2 Everyplace ® Sync Client generates a trace file called trace-isyn that stores information about the synchronization process. Follow these steps to enable tracing in your CLI-based application.
  1. Call the iscServiceOpenEx() function to create a new service handle. When you call the function, set the value of the isync.trace argument to "detailed".
  2. Call the iscConfingOpen() function to connect to the configuration store. When you call the function, set the value of the path argument to the path to which you want to store the trace-isyn file.

Important: For debugging purposes, view the file by using a text editor on a workstation. If you are using Windows, open the trace file in Wordpad. Windows Notepad might not display international characters properly.

On the device, set detail trace on to obtain these files:
    logdb-isyn
    trace-isyn
If any of these logs are available when the problem is re-created, you can go ahead and pack the available log files into a zip archive

To Send data to IBM

The Service Request (SR) tool allows you to submit and manage Problem Management Records on demand. For more information, see Using the SR tool for managing PMRs.

Customers that are registered and on an authorized caller list:
1. Sign onto the SR tool.

2. On the Welcome page, enter the PMR number in the Enter a report number field and click Go.

3. Scroll down to the Attach Relevant File field.

4. Click Browse to locate the log or trace file that you want to submit to IBM Support.

5. Click Submit to transfer your file to IBM Technical Support through FTP (ECuRep) and associated with
this PMR.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 Everyplace
General Issues

Software version:

9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5

Operating system(s):

AIX, EPOC, Linux, Neutrino, Palm OS, Solaris, Symbian OS, Windows, Windows Handhelds

Software edition:

Database Edition, Enterprise Edition, Express Edition, Software Development Kit

Reference #:

1389373

Modified date:

2014-02-14

Translate my page

Machine Translation

Content navigation