My Oracle Support Banner

E-PRCS: Master Note for Process Failure Issues (Doc ID 1266549.1)

Last updated on MARCH 07, 2018

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.44 and later
Information in this document applies to any platform.

Details

 

 

Process Failure Issues When Running Through Process Scheduler Master Note

 

We can run below processes through Process scheduler:

1. AE
2. Cobol
3. SQR
4. Crystal
5. XMLP
6. NVision
7. Winword

Chekpoints

1. Check if the issue is happening with some specific processes or all the processes.

2. If the issue is happening with some specific process type only (for ex: Crystal), then check the below points:

2.1. Check if the issue is happening with one specific Crystal report or all the crystal reports?
2.2. Were the users ever able to run this specific Crystal report successfully in past, in the same environment?
2.3. Is this issue intermittent in nature?
2.4. Is the same report is running in 2-tier environment or the issue is happening only when running in Web environment?
2.5. Check the Process Scheduler logs and Traces.

3. If the issue is happening with all the processes running through the scheduler, check the below points:

3.1. Check the Process Scheduler logs and the Traces from the "View Log/Trace" link.
That will help in determining the error messages for the reports.
3.2. Also, check the errors in the Message Log page.
3.3. Check if the Scheduler is "Up" and running.
3.4. Rebooting the scheduler domain.
In some situations, issue happens due to the corruption of configuration file itself.
In that case, it is suggested to recreate the Process Scheduler domain from scratch.
3.5. Check if the Master Scheduler service is running in the problem environment.

Settings for Trace Generation for different Process Types

In PSPRCS.cfg file:

Logging Levels (LogFence)

; 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

Trace Values (TraceSQL)

; 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 - Sybase Bind information
; 512 - Sybase Fetch information
; 1024 - SQL Informational Trace
; Dynamic change allowed for TraceSql and TraceSqlMask
TraceSQL=0

Location of Main Logs and configuration file:

1. PSPRCS.cfg file:
%PS_HOME%appserv/prcs/domain name/psprcs.cfg

2. Message Log:
Navigate to PeopleTools > Process scheduler > Process Monitor > Details > Message Log


3. Process Scheduler Log:
%PS_HOME%appserv/prcs/domain name/Logs

There are some specific guidelines also for generating traces for some specific Process Types.

Application Engine

1. Application Engine traces
2. Tracing from PIA
3. Process Scheduler trace options in psprcs.cfg file

Two ways / places for setting AE trace:

1. Tracing from PIA

Typical AE tracing options:

TOOLSTRACESQL 31
TOOLSTRACEPC 3596
TRACE 7

2. Process Scheduler trace options in psprcs.cfg file

It will trace all Application Engine Processes run via the scheduler.

TraceSQL= 31 (First 4 SQL options)

TracePC = 3596 (Variable assignment, Fetched values, Parameter values, Function return values, Each Statement)

TraceAE = 7 (First 3 AE Bit Tracing)

* see PeopleBooks > Enterprise PeopleTools 8.4x PeopleBook: PeopleSoft Application Engine > Tracing Application Engine Programs

There are three Types of AE Traces:

1. Application Engine Trace = Application Engine Trace File (AET)
File name is AE_[process_name]_[process_instance].AET

2. SQL Trace = PeopleSoft Trace File
File name is AE_[process_name]_[process_instance].trc

3. PeopleCode Trace = PeopleSoft Trace File
File name is AE_[process_name]_[process_instance].trc

1. Steps:

 

1.1. PeopleTools > Process Scheduler > Processes

1.2. Go to the 'Override Options' tab.
Set the 'Parameter List' option to 'Append' and add the required tracing flags.

1.3. Run the AE.

1.4. Get the generated trace file.

 

2. Trace location:
Files are moved to Report Repository and viewed from Process Monitor > Details > View Log/Trace link.

1. Equivalent Override Option Flags

psprcs.cfg v's PIA override page

TraceSQL=31 <=> -TOOLSTRACESQL 31
TracePC=3596 <=> -TOOLSTRACEPC 3596
TraceAE=7 <=> -TRACE 7

2. Trace location:


PSReports\[DB Name]\[Transfer date in YYYMMDD format]\[Report Instance]

3. File name:

AET Trace File: AE_[process_name]_[process_instance].AET
PeopleCode Trace File: AE_[process_name]_[process_instance].trc
SQL Trace File: AE_[process_name]_[process_instance].trc

Tracing via psprcs.cfg file traces ALL processes.

Cobol

1. Cobol traces
2. Tracing from PIA
3. Process Scheduler trace options in psprcs.cfg file

There are two ways for setting Cobol trace

1. Tracing from PIA

Setting 'Parameter List' option to 'Append' in Process definition.

2. Process Scheduler trace options in psprcs.cfg file

Traces all Cobol processes run via the scheduler.
E.g. TraceSQL=255

1. Steps:

1.1. Navigate to:
PeopleTools > Process Scheduler > Process Types

1.2. Copy data from the 'Parameter List' field.

Here is an example:
%ÛTYPE%%/%ÛNAME%%/%%OPRID%%/%%OPRPSWD%%/%%RUNCNTLID%%/%%INSTANCE%%//%ÛFLAG%%

1.3. PeopleTools > Process Scheduler > Processes

Set the 'Parameter List' option to 'Override' and insert the tracing bip map number needed between INSTANCE and DBFLAG.

Here is an example:
/%%INSTANCE%%/255/%ÛFLAG%%

1.4. Run the COBOL process.

1.5. Get the generated trace file.

2. Trace location:

Files are moved to Report Repository and viewed from Process Monitor > Details > View Log/Trace link.

3. File name:
cobsql_[process_instance].trc

1. Trace Options & associated numbers for each option:


; 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 - Sybase Bind information
TraceSQL=0

2. Trace location:
PSReports\[DB Name]\[Transfer date in YYYMMDD format]\[Report Instance]

3. File name:
cobsql_[process_instance].trc

Note:
Tracing via psprcs.cfg file traces ALL processes

SQR

1. SQR traces
2. Tracing in 2-tier
3. Tracing from PIA

There are two ways for setting SQR trace:

1. In 2-tier environment


This would help in tracing for a specific SQR report in 2-tier environment.

Typical SQR tracing options:
-debugxyz -S

2. Tracing from PIA

1. Steps:

1.1. Find the SQR you want to trace in your $PS_HOME\sqr directory.

1.2. Make a copy of the main SQR process that you will be tracing in one of your local directory ('C:\temp' for example).

1.3. Open the copy of the SQR program with an editor such as Notepad.

1.4. Search for a keyword 'debug' from top to bottom in this SQR program.

#ifdef debugx
SHOW 'Report Title: ' $ReportTitle
#endif

1.5. Write down the letters after word 'debug'.

1. Steps:

1.1. Navigate to:
PeopleTools > Process Scheduler > Processes

1.2. Go to the 'Override Options' tab.

1.3. Set the 'Parameter List' option to 'Append' and add the required SQR flags.

1.4. Run the SQR report.

1.5. Get the trace file.

2. Trace location:


Files are moved to report repository and viewed from Process Monitor > Details > View Log/Trace link.

3. SQR Flags:


" XYZ should be replaced by the letters you found in SQR program.
" Each SQR flag is separated by a blank space.
" -debugF shows program flow.
" -debugD shows data.
" -debugT shows timing.
" -S shows SQL cursors.

Crystal

1. Crystal traces
2. TraceSQL option is psprcs.cfg file
3. Crystal Trace for Crystal process

There are two types of Crystal trace:

1. TraceSQL option is psprcs.cfg file

It generates traces for all the underlying Query generated SQL requests.

This can be perform Via PSPRCS.cfg file.

2. Crystal Trace for Crystal process

Trace=Yes under [Crystal] section in psprcs.cfg file.

It generates traces for the pscrrun.exe program execution.

Note:
Both trace ALL Crystal Processes run via the scheduler.

1. Trace Options & associated numbers for each option:

; 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 - Sybase Bind information
TraceSQL=0

2. Trace location:
PSReports\[DB Name]\[Transfer date in YYYMMDD format]\[Report Instance]

3. File name:
pssqltrace.trc

1. In PSPRCS.CFG file

[Crystal]
;===============================
; Trace settings for Crystal
;===============================

Trace=YES

TraceFile=%TEMP%\CRYSTAL.TRC

2. Trace location:

C:\Temp

3. File name:

CRYSTAL.TRC

XML Publisher

1. XDO Debugging/Logging information
2. How to run XMLP reports in debug mode?

In order to get more detailed log file we need to debug Oracle xdo engine processing.

Running XMLP reports in a Debug mode will help to narrow down the problems whether it is in the XML data file, Template file, Application PeopleCode or in App Engine program.

XDO logging creates "XDO.log" file with detailed logging information.

The files that are created during the XDO logging are XML, XLS, Translation (XLIFF) and Template files (PDF, RTF) in the location
Location = Temporary directory specified in the LogDir.

Steps:

1. Create a file named xdodebug.cfg and place it under ($PS_HOME\JRE\lib directory)
[java_home]/lib/xdodebug.cfg, where [java_home] is your JRE directory delivered with PeopleTools installation.

2. Add the following entries to this file:
LogLevel=STATEMENT
LogDir=/tmp/xdolog (just an example)
(You need to specify a location of log files to be created in a directory that has full access)

Windows

The file should include following below information:
LogLevel=STATEMENT
LogDir=c:\temp (point to an appropiate temporary directory on the machine running the reports)

Unix

The file should include following below information:
LogLevel=STATEMENT
LogDir=/ds3/ps/dssgrp/tmp (point to an appropiate temporary directory on the machine running the reports)

3. Restart your App Server and Process Scheduler servers.

4. A set of files including detailed xdo log and all temporary files will be generated in a log directory you specified in the xdodebug.cfg ( /tmp/xdolog ).

5. After Replication remove xdodebug.cfg from $PS_HOME\JRE\lib directory.

PS/nVision

Users may turn on trace for PS/nVision reports in the PS/nVision section of the Process Scheduler configuration file (PSPRCS.cfg).

The Output of that trace would be available at:

Client: c:\temp\psnvs_[process_id].nvt
Web:
View Log/Trace link under Process Details

TraceLevel=0 (0-4)

0: No tracing (default setting)
1: Basic high level process flow and status
2: Entries from Level 1 plus additional info
3: Tracing up to level 2 and SQL statements
4: Tracing up to level 3 plus additional function calls, output values, and other detail information.

Reference

Application Engine:
PeopleBooks > Enterprise PeopleTools 8.4x PeopleBook: PeopleSoft Application Engine > Tracing Application Engine Programs

KEYWORDS:

QUEUED, FAILURE, PROCESS, PROCESS INSTANCE, APPLICATION ENGINE, COBOL, SQR, CRYSTAL, XMLP, XML PUBLISHER, NVISION, FAILURE, PROCESS FAILURE, TRACE, PROCESS TYPE

Actions

 

Contacts

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Details
Actions
Contacts
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.