Performance with SQR's using a Non-Unicode SQL Server Database Engine (Doc ID 2232630.1)

Last updated on JULY 18, 2017

Applies to:

PeopleSoft Enterprise SCM Purchasing - Version 9.2 and later
Information in this document applies to any platform.

Goal


Question 1:

PeopleTools upgrade, Dispatching PO returns error that PO hasn't been dispatched, but it actually has

When dispatching a PO from the Maintain Purchase Order page, the PODISP PSJob runs successfully in process monitor,  user gets message that the PO has not been dispatched, and to use Process Monitor to find out why.



Qustion 2:

Performance with SQR's using a non-Unicode SQL Server database engine, because apparently PeopleTools 8.55 SQR configuration is Unicode by default in pssqr.ini.; and when they reconfigured Environment:ODBC  ENCODING-DATABASE-API to a suitable non-unicode encoding, their performance issues with SQR's were resolved.

Current setting in PSSQR.ini for [Environment:ODBC] to ENCODING-DATABASE-API=UCS2. Please advice of the proper setting for a MS SQL Server 2014 non-Unicode database. T
 

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms