Infor Applied Innovation

« | Main | »

Landmark Database Session Debugging

October 31, 2013

By Tom Passe and Daniel Julson

Beginning with the Landmark 9.2.3 release, Landmark Technology Runtime provides the ability to capture database tier debug and timestats for a single user session interaction. When requested, an end user can activate and deactivate the recording of OPF (Object Persistence Framework) and DBI (DataBase Interface) level debug and subsequently email the results to Infor Xtreme Support for analysis to allow faster diagnosis of database access related issues.  NOTE: this will capture a plethora of information for a session, thus the user’s session will appear slower than normal while this is enabled.  Turn on only when ready to capture the issue.

The captured information is a slightly less verbose version of database tier debug that is recorded when DEBUG=true is set in $LACFGDIR/dblog.cfg (no data is recorded other than the keys and filter values.) The output is stored to a Landmark environment framework business class, DBSessionDebug
under the la module. Debug can be captured via Infor Rich Client or a web browser (web ui) interface.

NOTE: any background actions triggered by the session while session debug capture is activated will also be captured to the same output if sufficient time is allowed for them to complete after debug capture is deactivated.

To capture session debug through canvas:

Select Show –> Settings.

LMRKDB_1

 

Switch to the Landmark tab, check the box labeled Log Database Tier Session Debug, and click the OK button.

LMRKDB_2

 

Return to the Landmark tab via Show –> Settings, clear the box labeled Log Database Tier Session Debug, and click the OK button. LMRKDB_3

 

To email session debug output:

Open the DBSessionDebug business class under the la module in the Data Menu widget to view the Database Tier Session Debug list.

Click the corresponding Email button on the Database Tier Session Debug list to open the email dialogue, enter the required details, and click OK.

LMRKDB_4

 LMRKDB_5

LMRKDB_6

 

To export the DebugLog.txt and/or DebugTimestats.txt of a session (e.g., to attach to a JIRA ticket):

Open the DBSessionDebug business class under the la module in the Data Menu widget to view the Database Tier Session Debug list.

LMRKDB_7

LMRKDB_8

 

Double-click the desired session in the list to view it in the Database Tier Session Debug form.

LMRKDB_9

LMRKDB_10

 

 

>Click the Save As menu option, adjust the file name and directory if necessary, and click the OK button.

LMRKDB_11

To capture session debug for an OleDB query:

Simply append &_CTXPROPERTIES=context.session.key.dbsessiondebug=”true” to your query. (Session debug will only be activated for the duration of the query; no action is required to deactivate it.)

e.g. query: _DATAAREA=DBTEST80&_CLASS=Sybtest1&_FIELD=Mc1&_CTXPROPERTIES=context.session.key.dbsessiondebug=”true”

Then use the steps above to identify the DBSessionDebug record where you can view, export, or email it.

To capture session debug via a Web UI URL:

Simply append &context.session.key.dbsessiondebug=”true” to your query.  (Session debug will only be activated for the duration of the query; no action is required to deactivate it.)

e.g. URL:

http://mymachine.lawson.com:6005/hcm/ManagerSelfService/controller.servlet?service=page&webappname=ManagerSelfService&name=ManageMySubordinates&panel=MySubordinates&dataarea=hcm&context.session.key.dbsessiondebug=”true”

Then use the steps above to identify the DBSessionDebug record where you can view, export, or email it.


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *



About this Blog

The latest innovations using Infor Technology