Error deploying the ear file message when upgrading RSA Identity Governance & Lifecycle 7.x
Originally Published: 2019-04-23
Article Number
Applies To
RSA Version/Condition: 7.x
Issue
-------------------------------------------------- Restarting database. Database is not running. Database is running. ----------------------------------------------- --- Backing up parts of filesystem...at Thu Mar 14 14:44:57 CST 2019 -- /home/oracle/database -- /home/oracle/deploy -- Backup the plug-in config files -- Applying changes to database support files ... -------------------------------------------------- Applying changes to ear file...at Thu Mar 14 14:45:19 CST 2019 -- Adding patch update into ear file -- Cleaning out obsolete jar files. --Applying change to deploy area support files... Change deploy area ownership to root:oinistall Copy the utilities --Setting proper ownership properties on ear file/directory structure -------------------------------------------------- Starting application server to import patched ear ...at Th Mar 14 14:45:58 CST 2019 Java Home is: /etc/alternative/java_sdk_1.6.0 Updating System Values ... Verifying database Timezone value ... No change to the Timezone was detected. Total Memory: 48252 MB Reserved for OS: 2048 MB Reserved by AFX: 3072 MB Reserved by DB: 28035 MB Available for WildFly:15097 MB Starting RSA Identity Governance and Lifecycle: Verifying Oracle and System time match ... Database : 03-14-2019 14:46:05 +0800 ~ Web : 03-14-2019 14:46:04 +0800 Waiting for RSA Identity Governance and Lifecycle to start. ..... RSA Identity Governance and Lifecycle is running Deploying patched ear file... Error deploying the ear file [ |#
If patching, the patch log (/home/oracle/Aveksa_7.1.0_P05/logs/7.1.0_P05_2019-03-14-1436.log ) shows the following error:
Wildfly is running
Repackaging the aveksa.war and aveksa.ear
Archive name is: aveksa_7.1.0_143825_P05-2019-Mar-14-14.41.ear
Creating aveksa.ear file for deployment
Exception while building deployment ear file.
Could not find created archive file aveksa_7.1.0_143825_P05-2019-Mar-14-14.41.ear. Please check /home/oracle/archive/ if using a relative path
An error occured in the customizeACM command : error code 3
Error deploying the ear file
Step failed! See /home/oracle/Aveksa_7.1.0_P05/logs/7.1.0_P05_2019-03-14-1436.log for more information.Cause
Resolution
Steps
- Fix the contents of /home/oracle/archive/<latest>.ear and re-create the EAR. To do this, login as the oracle user and complete the following tasks:
mkdir test cd /home/oracle/test mkdir unpack cd unpack mkdir ear cd ear jar xvf /home/oracle/archive/<latest>.ear rm -fr aveksa_tmp cd .. jar cvf <latest>.ear -C ear .
- Make a backup copy of /home/oracle/archive/aveksa_7.1.0_143825_P02-2018-Sep-12-0.34.ear.
- Replace /home/oracle/archive/aveksa_7.1.0_143825_P02-2018-Sep-12-0.34.ear with /home/oracle/test/unpack/aveksa_7.1.0_143825_P02-2018-Sep-12-0.34.ear. For example,
cp /home/oracle/test/unpack/aveksa_7.1.0_143825_P02-2018-Sep-12-0.34.ear /home/oracle/archive
Notes
Related Articles
RSA Via Lifecycle and Governance (L&G) 7.0 does not start when the database time is earlier than server time 27Number of Views RSA Identity Governance & Lifecycle aveksa.ear deployment takes a long time to complete 117Number of Views How to manually deploy an aveksa ear file in RSA Identity Governance & Lifecycle 986Number of Views Patch/upgrade fails with 'Error deploying the ear file' error in RSA Identity Governance & Lifecycle 579Number of Views Error when running RSA Via Lifecycle & Governance 7.0 customizeACM.sh: Could not find Aveksa ear 238Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?