PTPSQLRT – Error Encountered

After PeopleTools Upgrade, you need to compile Cobol programs and the entire process becomes trickier if you have custom Cobols, or if you use a custom compile script instead of the usual process laid out by Oracle and MicroFocus. Due to this it is pretty common to face Cobol issues post-PeopleTools upgrade. In this article, you’ll find common cause of the error “PTPSQLRT – Error Encountered
No longer have connection to DB due to an error from previous action.”

I’ve seen a few slight variants of this error (when referring to the previous action like SQL COMMIT or DISCONNECT or SQL FETCH ) but the cause was found to be the same. These common errors were:

PTPSQLRT – Error Encountered
No longer have connection to DB due to an error from previous
action: SQL COMMIT. Bypassing current action: .
Terminating Program.

PTPSQLRT – Error Encountered
No longer have connection to DB due to an error from previous
action: DISCONNECT. Bypassing current action: .
Terminating Program.

PTPSQLRT – Error Encountered
No longer have connection to DB due to an error from previous
action: SQL FETCH. Bypassing current action: .
Terminating Program.

How to Resolve the error “PTPSQLRT – Error Encountered”

The most likely cause of this error is either:

  • Messed up version of source code
  • Messed up version of compiled code

In PeopleTools Upgrade, you create new PS_HOME, PS_APP_HOME, PS_CUST_HOME and you’re moving existing files to new directories etc, so there could be situation wherein some of this source code or compiled code is messed up. Fortunately, it is easy to overcome the situation. Mentioned below are some of the steps and tasks that will walk you through the possible causes of this error:

  • Make sure that your PS_HOME and database have the same Unicode or Non-Unicode encoding.
  • Backup and delete the CBLBIN, CBLBINA, CBLBINE, CBLBINU directories.
  • Backup and delete the source code directories (src/cbl/base) for PS_HOME, PS_APP_HOME and PS_CUST_HOME.
  • Make sure you have the correct PeopleTools Cobol files and copy only the PeopleTools Cobol files to PS_HOME/src/cbl/base.
  • Compile the PeopleTools Cobols using cblbld or cblmak. Verify that all the Cobols got compiled properly.
  • If you’re on Linux/Unix, run psrun.mak
  • Run the data mover script storept.dms
  • Test the PTPDBTST Cobol

Hopefully PTPDBTST runs fine and you can move on to application specific and custom Cobols. If you see issues, check the compile log as it may contain compile errors. Most common compilation issues refer to missing source code (*.cbl or *.dms).

Now copy application specific Cobols to PS_APP_HOME/src/cbl/base directory and run cblbld or cblmak, psrun and storept. Test an application specific Cobol, preferably the one which gave you the error. If it was application specific Cobol, which gave the error – hopefully it resolves the issue. If you still see the same error, check the compile log as it would most likely contain errors related to programs, which could not be compiled.

If you had issue with a custom Cobol, copy custom Cobols to PS_CUST_HOME/src/cbl/base directory and run cblbld or cblmak, psrun and storept. Test the custom Cobol, preferably the one which gave you the error – hopefully it resolves the error.  If you still see the same error, check the compile log as it would most likely contain errors related to programs, which could not be compiled.

If you continue to face error, use the comment box below to reach out to us.

Apurva Tripathi
 

Apurva is a PeopleSoft consultant and a big advocate of everything PeopleSoft. He is also a technology enthusiast and loves learning and implementing newer and open source technologies. He spends his spare time updating this blog and likes to read books on self help and productivity.

Click Here to Leave a Comment Below 0 comments