Script (.pdf file, 4 MB) - SAP MaxDB

SAP® MaxDB Expert Sessions 

SAP MaxDB Tracing 

Martin Koerner, SAP AG 

Bettina Laidler, SAP AG 

June 19, 2012

Objective of this session 

© SAP AG 2010. All rights reserved. / Page 2 

Getting the answer to the following questions: 

What means tracing ? 

What is the purpose of tracing ? 

What kinds of traces are available ? 

When should I use which trace ? 

How can I create these traces ?

Agenda 

1. Introduction 

1.1. What is tracing all about ? 

1.2. Kinds of traces used in MaxDB context 

2. SAP MaxDB Database Trace 

2.1. At a glance 

2.2. Functional chain 

2.3. Additional functionality 

2.4. Using SAP MaxDB Tools for database tracing 

2.4.1. Database Manager CLI (DBMCLI) 

2.4.2. Database Manager GUI (DBMGUI) 

2.4.3. SQL Studio / SQLCLI 

2.4.4. Database Studio 

2.4.5. xkernprot 

2.5. Using SAP Transactions for database tracing 

2.5.1. DB50 / LC10 

2.5.2. DBACOCKPIT 

© SAP AG 2010. All rights reserved. / Page 3

Agenda 

3. SAP MaxDB Interface Traces 

3.1. SQLDBC Trace 

3.1.1. Using SAP MaxDB Tools for SQLDBC tracing 

3.1.2. Using SAP Transactions for SQLDBC tracing 

3.2. JDBC Trace 

3.3. ODBC Trace 

4. Additional Traces 

4.1. SQL Trace 

4.2. Developer Trace 

4.3. DBMRFC Trace 

5. Useful Information Resources 


Agenda 


Please read the notes of the slides !

Agenda 





5. Useful Information Resources


1.1. What is tracing all about ? [1] 

Software Engineering 

Design, Implementation, Modification 

Executable Software 

to fulfill specific requirements



Executable Software 

to fulfill specific requirements 

No errors 

Correct results 

Requirements fulfilled 

OK 

Verifying 

data input 

E r r o r 

errors or incorrect results 

E r r o r a n a l y s i s 

Analyzing 

log files 

. . . 

Reproducing Tracing 

the error 

the error



T r a c i n g 

Advanced method used for error analysis 

Shouldn‘t be mixed up with event logging 

Creates trace output in a logfile referring 

to the program flow 

Trace output details can be configured via 

certain trace levels 

In most cases trace output can only be 

analyzed by technical support staff


1.2. Kinds of traces used in SAP MaxDB context ? [1] 

Application 

SAP MaxDB client 

Application 


Application 


SQLDBC JDBC ODBC 

SAP MaxDB Database


1.2. Kinds of traces used in SAP MaxDB context ? [2] 

Database Trace (database kernel trace) 

SQLDBC Trace (interface trace) 

JDBC Trace (interface trace) 

ODBC Trace (interface trace)

Agenda 







2.1. At a glance [1] 

Application 


Application 


Application 





2.1. At a glance [2] 

Application 

SAP or Third-Party 



SAP MaxDB X Server 

SAP MaxDB 

Database 

When it is indicated to use this trace? 

An error occurs which most likely happens in 

database kernel 

Examples: SQL error, Table / Index error 

Catalog error 

Which tools can be used to activate? 

SAP MaxDB Tools SAP Transactions 

Database Studio DB50 / LC10 

Database Manager GUI DBACOCKPIT 

SQL Studio 

DBMCLI 

SQLCLI 

Where is the trace log file located? 

binary as well as readable trace log file are 

located in the work directory of the database 

instance (parameter RUNDIRECTORY) 

Example: /sapdb/data/wrk/


2.2. Functional chain 


Database 

Database Trace 

Enable 

Switches on trace 

writing with at least 

one trace activity. 

Trace output is 

generated an kept 

in trace buffer. 

5 

1 

2 

3 

4 

Database is in mode ADMIN or ONLINE 

Trace file exists in its full size and is initialized 

Trace file name is ‘knltrace‘ by default 

Trace file is located in work directory of the 

database 


Disable 

Switches off trace 

writing. The whole 

trace output is still 

located in trace 

buffer. 


Flush 

The whole trace 

output is written 

from trace buffer to 

file ‘knltrace‘. 


Generate log 

file (readable) 

6 7 8 

Converts the 

original binary 

trace output of file 

‘knltrace‘ into 

readable text 

format.


2.3. Additional functionality 


Database 

1 

2 

3 

Database trace can be activated only for a specific 

session 

This is helpful to analyze a very special case (e.g. a 

special SQL error) as only trace output is generated 

which is context relevant 

Database trace can stop automatically in the 

event of a specific error 

This is helpful if an error always ends with a 

specific kernel error message. Trace writing is 

stopped automatically once this error occurred. It 

avoids that relevant trace output is overwritten 

again by newer trace output. 

In case of a database emergency shutdown the 

database trace is flushed automatically 

Even if the database trace wasn‘t switched on in 

case of an emergency shutdown context 

information can be kept and written to the trace file 

‘knltrace‘.


2.4. Using SAP MaxDB Tools for database tracing 


Database 


is supported by MaxDB‘s own tools: 

Database Manager CLI (DBMCLI) 

Database Manager GUI (DBMGUI) 

SQL Studio / SQLCLI 

Database Studio


2.4.1. Database Manager CLI (DBMCLI) [1] 


Database 


Enable 

1 


DBMCLI session has been opened 

(this is not a mandatory requirement, 

commands can be executed individually 

without an opened session, too) 


Disable 


Flush 

trace_on default trace_flush 

trace_off default 

2 

3 


Generate log 


trace_prot abkms 

4



1 

2



3 

2 

1



2 

2 

3 

1


2.4.2. Database Manager GUI (DBMGUI) [1] 


Database 


Enable 

Check 


check ‘TraceDefault‘ 

choose button 

‘Selected Items ON‘ 

1 


DBMGUI has been started and the MaxDB 

instance in question has been added for 

administration 


Disable 

Check 


choose button 

‘Selected Items OFF‘ 

2 


Flush 

Check 


choose button 

‘Flush‘ 

3 


Generate log 


Check 


Tab ‘Trace File‘ 

choose button 

‘Make Protocol‘ 

4


1 

2 

2.4.2. Database Manager GUI (DBMGUI) [2]



2 

1



2 

1



1



1



2 

1



2 

1



1 

1


2.4.3. SQL Studio / SQLCLI [1] 


Database 


Enable 


SQL Studio or SQLCLI has been started and a 

session to the MaxDB instance in question has 

been opened 


Disable 


Flush 

1 3 

diagnose vtrace default on diagnose vtrace flush 

2 

diagnose vtrace default off 


Generate log 


not possible here 

4



1



2 

1



2 

1



1


2.4.4. Database Studio


2.4.5. xkernprot [1] 

2 

1 

3


2.4.5. xkernprot [2] 

2 

1


2.5. Using SAP Transactions for database tracing 


Database 


is supported by SAP Transactions: 

DB50 

LC10 

DBACOCKPIT


2.5.1. DB50 / LC10 [1] 

2 

1


2.5.1. DB50 / LC10 [2] 

2 

1 

3


2.5.1. DB50 / LC10 [3] 

2 

1


2.5.1. DB50 / LC10 [4] 

1 

3 

4 

2


2.5.1. DB50 / LC10 [5] 

1 2


2.5.1. DB50 / LC10 [6]


2.5.2. DBACOCKPIT [1]





Agenda 







3.1. SQLDBC Trace [1] 

Application 


Application 


Application 






Application 



SQLDBC 

JDBC ODBC 



Database 


An error occurs in the interface between application 

and database 

Examples: SQL error, Connect error, Short dump 



SQLDBC_CONS DB50 / LC10 

DBACOCKPIT 


in the directory \wrk (Microsoft 

Windows) respectively 

/.sdb/ (UNIX/LINUX) 

as sqldbctrace-.prt file 

Example: C:\sdb\globaldata\wrk\sqldbctrace-125.prt 

Name, location and size of the trace log file can be 

changed



Application 



SQLDBC 

JDBC ODBC 



Database 

For which user the trace is written? 

The SQLDBC trace is written for the OS user 

who switches the trace on. 

On Windows the R/3 processes usually run as 

SAPService. Therefore you must specify 

the -u option of sqldbc_cons when you activate 

the trace at operating system level: 

sqldbc_cons -u SAPService 

This is not required in DB50/LC10/DBACOCKPIT 

since the environment of the SAPService 

already exists there.


3.1.1. Using SAP MaxDB Tools for SQLDBC tracing 

Application 






Database 

SQLDBC Trace 

is supported by MaxDB‘s own tools: 

SQLDBC_CONS


3.1.1. SQLDBC_CONS [1] 

sqldbc_cons [] [] 

Description 

-h help; shows all options and commands 

-v detailed information (verbose) 

-p the following command is executed only for the specified 

process ID 

-f force tool execution, even if a lock file of another instance 

is found 

-u the following command is executed for the specified user



sqldbc_cons [] [] 

Description 

SHOW ALL Displays configuration and dynamic trace options 

CONFIG TRACE 

FILENAME 

TRACE SIZE 

Sets the name of the trace file name. A '%p' in the 

name is replaced by the process id of the application 

for which the trace is written. 

Limits the size of the trace file to bytes, at 

least 8192 bytes are required 

TRACE SQL ON|OFF Activates or deactivates the SQL trace 

TRACE LONG ON|OFF Activates or deactivates method argument and detail 

debug trace 

TRACE TIMESTAMP 

ON|OFF 

TRACE STOP ON ERROR 

|OFF [COUNT 

] 

Activates or deactivates the time stamp for each 

logged action 

Stops tracing after the error has happened 

times (default is 1), or switches the trace 

stop feature off



1 

2



1 

3 

2



1 

2


3.1.1. SQLDBC_CONS [6]


3.1.2. Using SAP Transactions for SQLDBC tracing 

Application 






Database 

SQLDBC Trace 

is supported by SAP Transactions: 

DB50 

LC10 

DBACOCKPIT


3.1.2. DB50 / LC10 [1]

5 

6 


3.1.2. DB50 / LC10 [2] 

1 3 

4 

2


3.1.2. DB50 / LC10 [3]


3.1.2. DB50 / LC10 [4]


3.1.2. DB50 / LC10 [5]


3.1.2. DB50 / LC10 [6]


3.1.2. DB50 / LC10 [7]




3.2. JDBC Trace [1] 

Application 


Application 


Application 






Application 



SQLDBC JDBC 

ODBC 



Database 


An error occurs in the Java interface between 

application and database 

Examples: Connect error, SQL error, 



SAP MaxDB JDBC driver 


No fix location, can be configured 

Name of the trace log files can also be changed 

Example: C:\ jdbctrace3945742732322446323.prt



Application 



SQLDBC JDBC 

ODBC 



Database 


The JDBC trace is written for the OS user who 

activates the trace. 

On Windows systems the SAP R/3 processes 

usually run as OS user SAPService. 

On UNIX systems the SAP R/3 processes 

usually run as OS user adm.



java –jar \runtime\jar\sapdbc.jar [] [] 

Description 


-V shows version of SAP MaxDB JDBC driver (attention: capital ‘v‘) 

-d SAP MaxDB database name 

-u SAP MaxDB database user 

-n host where the database is running on 

-c SQL command to be executed 

-a DBM command to be executed



java –jar \runtime\jar\sapdbc.jar [] [] 

Description 

TRACE ON|OFF Enables|disables trace 

TRACE SIZE Limits the size of the trace file to bytes, at least 

8192 bytes are required 

TRACE FILENAME 

 


|OFF 

SHOW 

[ALL|TRACESETTINGS] 

Sets the name of the trace file. An unique suffix to the 

trace file name is added. 

Stops trace writing after error occurred or 

switches the trace stop feature off 

Displays the current trace settings



2 

1 

3 

3 

1



1 

1 

2 

3



2 

1



1 

3 

2



1


3.3. ODBC Trace [1] 

Application 


Application 


Application 






Application 






Database 


An error occurs in the interface between application 

and database 

Examples: SQL error, Connect error, HTTP error 



ODBC_CONS 


in the directory \wrk (Microsoft 

Windows) respectively 

/.sdb/ (UNIX/LINUX) 

as odbctrace-.prt file 

Example: C:\sdb\globaldata\wrk\odbctrace-125.prt 

Name, location and size of the trace log file can be 

changed



Application 






Database 


The ODBC trace is written for the OS user 

who switches the trace on.


3.3. ODBC_CONS [1] 

odbc_cons [] [] 

Description 


-v detailed information (verbose) 

-p the following command is executed only for the specified 

process ID 

-f force tool execution, even if a lock file of another instance 

is found 

-u the following command is executed for the specified user



odbc_cons [] [] 

Description 

SHOW ALL Displays configuration and dynamic trace options 

CONFIG TRACE 

FILENAME 

TRACE SIZE 

Sets the name of the trace file name. A '%p' in the 

name is replaced by the process id of the application 

for which the trace is written. 

Limits the size of the trace file to bytes, at 

least 8192 bytes are required 

TRACE SQL ON|OFF Activates or deactivates the SQL trace 

TRACE LONG ON|OFF Activates or deactivates method argument and detail 

debug trace 

TRACE TIMESTAMP 

ON|OFF 


|OFF [COUNT 

] 

Activates or deactivates the time stamp for each 

logged action 

Stops tracing after the error has happened 

times (default is 1), or switches the trace 

stop feature off



1 

2



1 

3 

2



1 

2


3.3. ODBC_CONS [6]


3.3. ODBC_CONS [7]

Agenda 







4.1. SQL Trace


4.2. Developer Trace


4.3. DBMRFC Trace [1]







Agenda 






5. Useful Information Resources 


SAP MaxDB documentation: 

http://maxdb.sap.com 

following “Documentation” “Version 7.8” 

SAP notes: 

“Glossary” “Trace” 

837385 “FAQ: SAP MaxDB database trace (VTRACE)” 

822239 “FAQ: SAP MaxDB Interfaces” 

1428709 “Creating ODBC trace as of SAP MaxDB Version 7.7“ 

903018 “SAP MaxDB: JDBC trace“ 

SAP Community Network (SCN): 

http://wiki.sdn.sap.com/wiki/display/MaxDB/SAP+MaxDB+traces 

(SAP MaxDB traces)

Questions and Answers 


Thank You! 

Bye, Bye – And Remember Next Session 

August 14, 2012 SAP MaxDB No-Reorganization Principle 

All Expert Sessions: http://maxdb.sap.com/training

Disclaimer 

This presentation reflects current planning. 

Contents may be changed 

without prior notice, and are in no way 

binding upon SAP.

© 2010 SAP AG. All Rights Reserved 

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein 

may be changed without prior notice. 

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. 

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. 

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, 

eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, 

POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, 

MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. 

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. 

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other 

countries. 

Oracle is a registered trademark of Oracle Corporation. 

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. 

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. 

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. 

Java is a registered trademark of Sun Microsystems, Inc. 

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. 

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer and other SAP products and services mentioned herein as well 

as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. 

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and 

services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries. 

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. 

National product specifications may vary. 

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the 

express prior written permission of SAP AG. 

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, 

developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or 

development. Please note that this document is subject to change and may be changed by SAP at any time without notice. 

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other 

items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of 

merchantability, fitness for a particular purpose, or non-infringement. 

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these 

materials. This limitation shall not apply in cases of intent or gross negligence. 

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links 

contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Script (.pdf file, 4 MB) - SAP MaxDB

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?