CA PPM upgrade fails if ppm_invalid_user's details vary from its seed data

book

Article ID: 103234

calendar_today

Updated On:

Products

CLARITY PPM FOR ITG CLARITY PPM FEDERAL Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

PPM_INVALID_USER is an account whose information is seeded under SRM_RESOURCES and CMN_SEC_USERS tables. Upgrades rely on this seed data to not change. Where there is a change, the upgrade fails.

Failure due to this issue, will have Errors such as the below logged in install.log:
An error such as the below is obtained during CA PPM upgrade.
Updating xogseeddata for component = infrastructure 
Applying PPM_INVALID_USER.xml 
/fs0/clarity1/clarity/.setup/scripts/db.xml:2352: The following error occurred while executing this line: 
/fs0/clarity1/clarity/.setup/scripts/db.xml:2568: The following error occurred while executing this line: 
/fs0/clarity1/clarity/.setup/scripts/db.macros.xml:105: Java returned: 2 
at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:568) 
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:443) 
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105) 
at com.niku.tools.taskdefs.xpath.Iter.executeTarget(Iter.java:294) 
at com.niku.tools.taskdefs.xpath.Iter.execute(Iter.java:189) 

Applying XOG: Failure occurred while applying PPM_INVALID_USER.xml 
Check /fs0/clarity1/clarity/logs/xog-seeddata/out/infrastructure/PPM_INVALID_USER_out.xml for errors 
ERROR: Upgrade failed for tenant

Cause

Failure is caused due to changes in seed data of user 'ppm_invalid_user'.

Environment

CA PPM 14.3.x, 15.x 

Resolution

Run the following update queries, that will update this account with the original seed data prior to upgrade. For both the queries below, only one row each should be updated. If there is more than one row being updated, do not commit.

UPDATE SRM_RESOURCES 
SET LAST_NAME = 'Invalid_User', 
FIRST_NAME ='PPM',
MIDDLE_NAME = NULL,
EMAIL = '[email protected]', 
SMS_EMAIL = NULL,
PERSON_TYPE =300,
USER_ID = '-99',
DATE_OF_HIRE = NULL,
DATE_OF_TERMINATION = NULL,
MANAGER_ID = NULL, 
IS_ACTIVE = 0, 
FULL_NAME ='Invalid_User, PPM', 
IS_EXTERNAL = 0,
EXTERNAL_SOURCE_ID =1,
EXTERNAL_ID = NULL,
--RESOURCE_TYPE = NULL,
USE_IN_FRC_BUDGET =0,
SLICE_STATUS = NULL,
INCLUDE_FLAG =1,
BOOK_MANAGER_ID = NULL,
ENTITY_CODE = NULL,
FORECAST_RATE = NULL
WHERE USER_NAME = 'ppm_invalid_user';

UPDATE CMN_SEC_USERS 
SET ID ='-99',
USER_NAME ='ppm_invalid_user',
PWD ='977637977634d34664e6a4833494a7a6b6943073e5ad7c4022926c5c2c9aa4b124249', 
PWD_REQUIRED = NULL,
USER_STATUS_ID =202, 
OBS_ID = NULL,
DESCRIPTION = NULL,
FIRST_NAME ='PPM',
MIDDLE_NAME = NULL,
LAST_NAME = 'Invalid_User', 
EMAIL_ADDRESS ='[email protected]', 
SMS_EMAIL_ADDRESS = NULL,
PHOTO_FILE = NULL,
LOCALE = 'en_US',
TIMEZONE ='Europe/London', 
LANGUAGE_ID =1,
COUNTRY_ID =1, 
CURRENCY_CODE = NULL,
LOGIN_COUNT = NULL,
BAD_LOGIN_COUNT = NULL,
FORCE_PWD_CHANGE =1,
FULL_NAME = NULL,
COMPANY_ID =0,
EXTERNAL_SOURCE_ID = 1, 
EXTERNAL_ID = NULL,
IS_LDAP =1,
USE_PROXY =0,
PROXY_USER_ID = NULL,
HOME_URL = NULL,
NAV_STATE =0,
BO_USER = NULL,
SCREEN_READER_OPT =0,
HIGH_CONTRAST_UI =0,
NO_CSRF_MSG = NULL,
SALT ='ywcM4fNjH3IJzkiC', 
USER_UID = 'ppm_invalid_user'
WHERE USER_NAME = 'ppm_invalid_user';
 

Additional Information

Note: It is recommended to not change data of seed users that are placed out of the box in the PPM Database.