E-COB: Cobol runtime errors. Return Code: 08080 An invalid bind variable number was specified or Return Code: 08095 A SELECT item number is outside valid range for query
(Doc ID 763181.1)
Last updated on FEBRUARY 20, 2025
Applies to:
PeopleSoft Enterprise PT PeopleTools - Version 8.4 and laterInformation in this document applies to any platform.
*** ***
***Checked for relevance on 22-Oct-2015***
Symptoms
Applies to :Tools 8.4x and greater on Windows, Linux, UNIX platforms
For this particular example, the environment is a campus solutions 9 demo database on 8.49.15 tools running oracle 10.2.0.3 database on hp-ux itanium, with the process scheduler and application server on windows 2003 and compiler is Net Express 4
The site has had a tools and application upgrade. All cobols compiled without any errors.
When running cobol process, they ALL fail with an error :
Scenario 1)
PTPSQLRT - ERROR IN BIND SETUP/DATA
STATEMENT=PTPUSTAT_U_PRCRQSB
VARIABLE#=001
DATA TYPE=001
DATA LEN =0001
SCALE =000
Application Program Failed
Action Type : SQL UPDATE
In Pgm Section : SQLRT: PROCESS-SETUP(BIND)
With Return Code: 08080
Error Message : An invalid bind variable number was specified
Stored Stmt : PTPUSTAT_U_PRCRQSB
SQL Statement : UPDATE PSPRCSRQST SET RUNSTATUS = :1 ,PRCSRTNCD = :2 ,BEGIND
TTM = GETDATE() ,LASTUPDDTTM = GETDATE() ,CONTINUEJOB = :3 W
HERE PRCSINSTANCE = :4
PTPSQLRT - Error Encountered
The same issue can also manifest into the below error:
Scenario 2)
Application Program Failed
Action Type : SQL SELECT
In Pgm Section : SQLRT: PROCESS-SETUP(SELECT)
With Return Code: 08095
Error Message : A SELECT item number is outside valid range for query
STEPS
-----------------------
The error can be reproduced by running any cobol process e.g PTPDBTST process.
Scenario 3)
"Remote program PTPNTEST failed with return code: 8006 : Reason : Invalid datatype specified . In section SQLRT: EXECUTE-STMTSQL-UPDID. Check log file ......"
Scenario 4)
"Remote program PTPNTEST failed C_PSN_GET_DATA: Parameter length mismatch............"
Scenario 5)
"Remote program PTPNTEST failed with return code : 404 . Reason: SQLRT: Unable to connect to database:....."
Scenario 6)
PTPSQLRT - SQLRT NOT FOUND
Load error : file 'C_SQLRBK'
error code: 173, pc=0, call=1, seg=0
173 Called program file not found in drive/directory
Scenario 7)
2020-05-14-11.30.39.810000 INFO(5830,1) PI(1439947) Program(GLPPPOST)
Begin Posting at 2020-05-14-11.30.39.790000.
RUNID^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@END
STATEMENT=INSERT INTO PS_JRNL_EDIT_LOG (PROCESS_INSTANCE,JRNL_EDT_PRCS_ORIG,OPRID,RUN_CNTL_ID,DTTM_STAMP_SEC) VALUES (0001439947, 'A','5^@Y^@a^@w^@u^@D^@b^@P^@k^@c^@x^@V^@n^@W^@r^@2^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@',' ',SYSTIMESTAMP)
Application Program Failed
Action Type : SQL UPDATE
In Pgm Section : SQLRT: COMPILE-DYNAMIC
With Return Code: 08012
Error Message : Invalid syntax in SQL statement
Dynamic Stmt : GLPPPOST_U_CA000
SQL Statement : INSERT INTO PS_JRNL_EDIT_LOG (PROCESS_INSTANCE,JRNL_EDT_PRCS
_ORIG,OPRID,RUN_CNTL_ID,DTTM_STAMP_SEC) VALUES (0001439947,
'A','5^@Y^@a^@w^@u^@D^@b^@P^@k^@c^@x^@V^@n^@W^@r^@2^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@',' ',SYSTIMESTAMP)^@
at pos 00021
at pos 00021
> 2020-05-14-11.30.39.930000 SEVERE ERROR IN PGM:(5830,7) PI(1439947) Program(GLPPPOST)
PSPSQLRT error in Posting: GLPPPOST - CA000 INSERT.
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 |
Cause |
Solution |