Support Article

Upgrade.sh script fails for data upgrade

SA-30819

Summary



Upgrade.sh script fails for data upgrade with :

[java] WARNING: Encountered database error attempting to load jar into Oracle: ORA-00604: error occurred at recursive SQL level 1
[java] ORA-28003: password verification for the specified password failed
[java] ORA-20002: Password length less than 15
[java]
[java] Throwable occurred: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
[java] ORA-28003: password verification for the specified password failed
[java] ORA-20002: Password length less than 15

TSE Notes - This occurs during UDF generation. The rest of the install appears fine, UDF installation starts normally before this error occurs.


Error Messages



[java] WARNING: Encountered database error attempting to load jar into Oracle: ORA-00604: error occurred at recursive SQL level 1
[java] ORA-28003: password verification for the specified password failed
[java] ORA-20002: Password length less than 15
[java]
[java] Throwable occurred: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
[java] ORA-28003: password verification for the specified password failed
[java] ORA-20002: Password length less than 15


Steps to Reproduce



1) Create a Deployment User with the required privileges.
2) Add these details in the setupDatabase.properties file.
3) Run the upgrade.sh with dataOnly set to true.
4) Script fails with below error:


[java] WARNING: Encountered database error attempting to load jar into Oracle: ORA-00604: error occurred at recursive SQL level 1
[java] ORA-28003: password verification for the specified password failed
[java] ORA-20002: Password length less than 15
[java]
[java] Throwable occurred: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
[java] ORA-28003: password verification for the specified password failed
[java] ORA-20002: Password length less than 15


Root Cause



A third-party product issue, the user attempted to be modified is an Oracle maintained user.

Resolution



Here’s the explanation for the reported behavior: 

The issue is caused by something in the environment attempting to modify the user OJVMSYS this is not related to Pega but is an internal Oracle maintained user new to Oracle 12c. Recommended user contact Oracle support.

 

Published November 25, 2016 - Updated November 28, 2016

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.