Debugging nVision, Part 1

Set nVision Web/Process Scheduler Trace

To trace an online nVision process you must nVision tracing in the Process Scheduler configuration file.

$PS_CFG_HOME/appserv/prcs/DOMAIN/psprcs.cfg

Under the [nVision] section there will be a "TraceLevel" setting.  I typically useTraceLevel=4.  I like a lot of data.

Trace Level Options (from PeopleBooks)
0 = No Tracing
1 = High-level process flow and status information
2 = Level 1 plus high-level code information
3 = Level 2 plus includes SQL Statements
4 = Level 3 plus function calls, output values, and detailed process flows.  Maximum level.

A Process Scheduler bounce is not required.  At least, not if you have "Dynamic Changes" enabled.  I don't know for sure if the dynamic changes setting matters or not to this option.

The trace files will be posted online under Process Monitor.


Set nVision Windows Client Trace

Tracing for nVision running on the Windows client can be enabled through Configuration Manger.  Start Configuration Manager then on the "Profile" tab select "Edit".  On the "nVision" tab there will be a Trace Level setting.

I typically use Trace Level = 4.

On Windows the trace files go to your temporary directory and are named with non-sequential number values.  The easiest way to find them is to open Windows Explorer and type in %TEMP%.  This should take you to the temporary directory defined for your profile, and should be the same place nVision put the trace files.

In Configuration Manager you can also turn on SQL tracing from the Trace tab.  That tab has a place to enter the trace file name and location.  This will not give you much information about the nVision processes, but may help for reviewing the SQL that is run.


Set Other Process Scheduler Traces

If you need to see more about what's going on with the process scheduler then you can set the Process Scheduler traces in the psprscs.cfg configuration file.

$PS_CFG_HOME/appserv/prcs/DOMAIN/psprcs.cfg

This would give you the details on report distribution and scheduler status updates.  It will be tracing everything the process scheduler does so the log files could get quite large.  You should only leave it enabled for a short time.

[Trace]
;=========================================================================
; Trace settings
;=========================================================================
; SQL Tracing Bitfield
;
; Bit       Type of tracing
; ---       ---------------
; 1         - SQL statements
; 2         - SQL statement variables
; 4         - SQL connect, disconnect, commit and rollback
; 8         - Row Fetch (indicates that it occurred, not data)
; 16        - All other API calls except ssb
; 32        - Set Select Buffers (identifies the attributes of columns
;             to be selected).
; 64        - Database API specific calls
; 128       - COBOL statement timings
; 256       - not in use
; 512       - not in use
; 1024      - SQL Informational Trace
; Dynamic change allowed for TraceSql and TraceSqlMask
TraceSQL=0

;-------------------------------------------------------------------------
; PeopleCode Tracing Bitfield
;
; Bit       Type of tracing
; ---       ---------------
; 1         - Trace Evaluator instructions  (not recommended)
; 2         - List Evaluator program        (not recommended)
; 4         - Show assignments to variables
; 8         - Show fetched values
; 16        - Show stack
; 64        - Trace start of programs
; 128       - Trace external function calls
; 256       - Trace internal function calls
; 512       - Show parameter values
; 1024      - Show function return value
; 2048      - Trace each statement in program  (recommended)
; Dynamic change allowed for TracePC 
TracePC=0
...

[Process Scheduler]
;=========================================================================
; General settings for the Process Scheduler
;=========================================================================
PrcsServerName=PSUNX
...

;-------------------------------------------------------------------------
; Logging detail level
;
; Level     Type of information
; -----     -------------------
;  -100     - Suppress logging
;   0       - Status information
;   1       - Critical Information
;   2       - Errors
;   3       - Informational (default)
;   4       - Tracing Level 1
;   5       - Tracing Level 2
; Dynamic change allowed for LogFence
LogFence=3

Results will be in the process scheduler log files.

$PS_CFG_HOME/appserv/prcs/DOMAIN/LOGS...

AESRV_mmdd.LOG
DSTAGNT_mmdd.LOG
SCHDLR_mmdd.LOG
DSTAGNT_mmdd.LOG

Clear Tree Selector Tables
This is both a debugging option as well as a potential performance-improvement option.  The tree selector tables are dynamically populated when the reports are run and, in most cases, should be cleared when no longer needed.  Sometimes the tables can get quite large and start impacting performance.

Truncate all the selector tables as well as the control table.  Then when you run a test process you will be able to determine whether the data is being selected properly, or is what you expect.

-- Truncate Tree Selector Tables so they are rebuilt
TRUNCATE TABLE PSTREESELCTL;

TRUNCATE TABLE PSTREESELECT01;
TRUNCATE TABLE PSTREESELECT02;
TRUNCATE TABLE PSTREESELECT03;
TRUNCATE TABLE PSTREESELECT04;
TRUNCATE TABLE PSTREESELECT05;
TRUNCATE TABLE PSTREESELECT06;
TRUNCATE TABLE PSTREESELECT07;
TRUNCATE TABLE PSTREESELECT08;
TRUNCATE TABLE PSTREESELECT09;
TRUNCATE TABLE PSTREESELECT10;
TRUNCATE TABLE PSTREESELECT11;
TRUNCATE TABLE PSTREESELECT12;
TRUNCATE TABLE PSTREESELECT13;
TRUNCATE TABLE PSTREESELECT14;
TRUNCATE TABLE PSTREESELECT15;
TRUNCATE TABLE PSTREESELECT16;
TRUNCATE TABLE PSTREESELECT17;
TRUNCATE TABLE PSTREESELECT18;
TRUNCATE TABLE PSTREESELECT19;
TRUNCATE TABLE PSTREESELECT20;
TRUNCATE TABLE PSTREESELECT21;
TRUNCATE TABLE PSTREESELECT22;
TRUNCATE TABLE PSTREESELECT23;
TRUNCATE TABLE PSTREESELECT24;
TRUNCATE TABLE PSTREESELECT25;
TRUNCATE TABLE PSTREESELECT26;
TRUNCATE TABLE PSTREESELECT27;
TRUNCATE TABLE PSTREESELECT28;
TRUNCATE TABLE PSTREESELECT29;
TRUNCATE TABLE PSTREESELECT30;

References
http://docs.oracle.com/cd/E66686_01/pt855pbr1/eng/pt/tnvs/task_SettingTraceFiles-074f49.html#ContentsNavBar