My Oracle Support Banner

E-COB: RC=9979 Attempting to use Unicode COBOL to access Ansi DB (Doc ID 2125463.1)

Last updated on DECEMBER 28, 2021

Applies to:

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

Symptoms

This issue applies to Tools 8.55 releases, upto and including tools 8.55.05.   Fix delivered in 8.55.06, scheduled for release at end of May.

Applies to ANSI environments only, on both windows and UNIX/Linux platforms.   Not an issue for Unicode environments.

Sample Environment:
-----------------
PT 8.55.01   ( upgraded from PT 8.54.13 )
Production and test/dev environments affected
HCM 9.2  ( upgrade from HCM 9.1 )
DB is Microsoft SQLServer 2012
OS is Microsoft Windows x64 (64-bit)  2012 R2
Net express NE 5.1 WP11


Issue :
-------
The site upgraded HCM 9.1 to 9.2 and tools from 8.54.13 to PT 8.55.01
Customer tested cobol (via scheduler and remote call ) using PS and all tests were successful.

Subsequently, when user with oprid TUXEDO attempted to run a cobol process,  the process ran to error.  The sample cobol test process PTPDBTST ran to error, and remote call test failed as well.

Error message " RC=9979 Attempting to use Unicode COBOL to access Ansi DB"

SqlTrace shows:

PeopleSoft Batch Timings Report: cobsql.trc

Encoding Scheme Used: Ansi

Time Line Elapsed SQL Cursor Return DB API Statement
------------ --------- ------- ------- ------ ------- ----------------
08:34:10.742 1 0.203 0.203 #1 RC=0 Connect=HRTEST/people/?
08:34:10.768 2 0.016 0.000 #1 RC=0 COM Stmt=SELECT OWNERID FROM PSDBOWNER WHERE DBNAME = :1
08:34:10.768 3 0.000 0.000 #1 RC=0 Bind position=1, type=SQLPSTR, length=0, value=HRTEST
08:34:10.799 4 0.031 0.000 #0 RC=0 PSODBC - [Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid object name 'PSDBOWNER'.
08:34:10.799 5 0.000 0.000 #1 RC=601 EXE
08:34:10.843 6 0.047 0.000 #1 RC=0 CEX Stmt=SELECT OWNERID, UNICODE_ENABLED FROM PSSTATUS
08:34:10.843 7 0.000 0.000 #1 RC=0 SSB column=1, type=SQLPSTR, length=31
08:34:10.843 8 0.000 0.000 #1 RC=0 SSB column=2, type=SQLPSIN, length=4
08:34:10.879 9 0.031 0.000 #1 RC=0 Fetch
08:34:10.895 10 0.016 0.000 #1 RC=0 COM Stmt=SELECT A.STM_ACCESS_ID, A.STM_ACCESS_PSWD, A.STM_ACCESS_PART1, A.STM_ACCESS_PART2, A.ENCRYPTED FROM PSOPRDEFN O, PSACCESSPROFILE A WHERE O.OPRID=:1 AND A.SYMBOLICID = O.SYMBOLICID
08:34:10.895 11 0.000 0.000 #1 RC=0 Bind position=1, type=SQLPSTR, length=0, value=TUXEDO
08:34:10.895 12 0.000 0.000 #1 RC=0 SSB column=1, type=SQLPSTR, length=41
08:34:10.895 13 0.000 0.000 #1 RC=0 SSB column=2, type=SQLPSTR, length=41
08:34:10.895 14 0.000 0.000 #1 RC=0 SSB column=3, type=SQLPSTR, length=13
08:34:10.895 15 0.000 0.000 #1 RC=0 SSB column=4, type=SQLPSTR, length=13
08:34:10.896 16 0.016 0.000 #1 RC=0 SSB column=5, type=SQLPSIN, length=4
08:34:10.973 17 0.062 0.000 #1 RC=0 EXE
08:34:10.973 18 0.000 0.000 #1 RC=0 Fetch
08:34:11.010 19 0.047 0.000 #1 RC=0 Disconnect
08:34:11.174 20 0.156 0.000 #1 RC=0 Connect=HRTEST/accessid/?
08:34:11.298 21 0.125 0.000 #1 RC=0 SET OprId=TUXEDO
08:34:11.309 22 0.016 0.000 #1 RC=0 SET type= cursor=persistent
08:34:11.376 23 0.062 0.000 #1 RC=0 COM Stmt=SELECT PTOPERPSWDV2, OPERPSWDSALT FROM PSOPRDEFN WHERE OPRID = :1
08:34:11.376 24 0.000 0.000 #1 RC=0 Bind position=1, type=SQLPSTR, length=0, value=TUXEDO
08:34:11.376 25 0.000 0.000 #1 RC=0 SSB column=1, type=SQLPSTR, length=93
08:34:11.376 26 0.000 0.000 #1 RC=0 SSB column=2, type=SQLPSTR, length=89
08:34:11.429 27 0.063 0.000 #1 RC=0 EXE
08:34:11.430 28 0.000 0.000 #1 RC=0 Fetch
08:34:11.430 29 0.000 0.000 #1 RC=9979 Attempting to use Unicode COBOL to access Ansi DB

 

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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