Solution: Reinstalling 8.53, and applying the required-for-upgrade Minor Tools Patch ’01′ resolved this issue.
New Note: if you are on Microsoft SQL server 2012, the following fix from Microsoft, will help you continue.
FIX: “FOR UPDATE clause allowed only for DECLARE CURSOR” error when you execute stored procedures together with cursor-specific syntax in SQL Server 2012 –http://support.microsoft.com/kb/2740957
This FIX is included in Cumulative Update Package for MSS 2012, with is the minimum required for MSS 2012 to be supported on Windows 2008 (both R2 and not R2).
Another workaround developed at a customer site:
When looking at where the the script failed. I would see an empty value in OPERPSWD field. I updated the PSOPRDEFN and gave the OPRID a password. I re-ran the encrypt_password and advanced to next error. I repeated the step of updating OPERPSWD 2 more times to ensure a blank password was where the script stopped. I than updated all OPRIDs with a NULL password to have a password. I re-ran the script and was successful.
Note this is not a formally supported workaround, it is information passed to the GSC from a customer who implemented the workaround.
Another workaround developed at a customer site:
Another workaround if you’re using PS as your login ID is to copy the encryted password forOPRID PS from another instance and run this script.
update PSOPRDEFN
set OPERPSWD = ‘Encrypted PSWD for OPRID PS in another instance’, ENCRYPTED=1
where OPRID = ‘PS’”
Ref: GSC Doc ID 1532033.1
By: Prasanth Bhaskaran (PeopleSoft Application DBA)