EJPSBCA job fails with EJPPF0181E during 'action-deploy-admin-oob'

During the installation and configuration for Portal 8 on a z/OS machine, the job EJPSBCA is created and run to install/configure Portal. If this task ended abruptly or was cancelled without a failure message, this problem may occur where a portlet was deployed to the database and not cleaned up as part of the failure. Running EJPSBCA again will pick up on the same task and try to deploy the app again, which fails because there is already a reference in the database.

In the ConfigTrace.log:

===============================================================
action-deploy-admin-oob:
[copy] Copying 1 file to /wasv80config/AppServer/profiles/default/ConfigEngine/config/work
[xmlaccess] EJPXB0006I: Connecting to URL http://myhostname:10025/wps/config/
[xmlaccess] EJPXB0002I: Reading input file /wasv80config/AppServer/profiles/default/ConfigEngine/config/work/SetupAdmin.xml
[xmlaccess] <?xml version="1.0" encoding="UTF-8"?>
[xmlaccess] <!-- IBM WebSphere Portal/8.0 build wp800CF03_001_22 exported on Thu Dec 13 12:52:34 GMT 2012 from myhostname/120.0.0.1 -->
[xmlaccess] <request build="wp800CF03_001_22" type="update" version="8.0.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PortalConfig_8.0.0.xsd">
[xmlaccess] <status element="[web-app wp.ap.impersonation.webapp uid=impersonation.war.webmod]" result="failed">
[xmlaccess] <message id="EJPXA0043E">EJPXA0043E: An error occurred while creating or updating the resource.</message>
[xmlaccess] <message id="EJPPF0181E">EJPPF0181E: Error occurred. The id=wp.ap.impersonation already exists for stored standard portlet application wp.ap.impersonation in the XML element portlet-app impersonation.war.</message>
[xmlaccess] <message id="EJPPF0181E">EJPPF0181E: Error occurred. The id=wp.ap.impersonation already exists for stored standard portlet application wp.ap.impersonation in the XML element portlet-app impersonation.war.</message>
[xmlaccess] <stacktrace><![CDATA[
[xmlaccess] com.ibm.wps.command.xml.XmlCommandException: EJPXA0043E: An error occurred while creating or updating the resource. [web-app wp.ap.impersonation.webapp uid=impersonation.war.webmod]
[xmlaccess] at com.ibm.wps.command.xml.ConfigItem.doUpdate(ConfigItem.java:610)
[xmlaccess] at com.ibm.wps.command.xml.UpdateEngine.processItem(UpdateEngine.java:216)
[xmlaccess] at com.ibm.wps.command.xml.UpdateEngine.updateTopLevelItem(UpdateEngine.java:171)
[xmlaccess] at com.ibm.wps.command.xml.XmlAccessHandler.fillObjectModel(XmlAccessHandler.java:330)
[...]
[xmlaccess] Caused by: com.ibm.wps.command.applications.AppAlreadyExistsException: EJPPF0181E: Error occurred. The id=wp.ap.impersonation already exists for stored standard portlet application wp.ap.impersonation in the XML element portlet-app impersonation.war.
[xmlaccess] WrappedException is: com.ibm.wps.pe.mgr.exceptions.DuplicateAppException: EJPPF0181E: Error occurred. The id=wp.ap.impersonation already exists for stored standard portlet application wp.ap.impersonation in the XML element portlet-app impersonation.war.
[...]
[xmlaccess] Caused by: com.ibm.wps.pe.mgr.exceptions.DuplicateAppException: EJPPF0181E: Error occurred. The id=wp.ap.impersonation already exists for stored standard portlet application wp.ap.impersonation in the XML element portlet-app impersonation.war.

===============================================================

EJPSBCA was previously run before and ended abruptly or was cancelled without a failure message. A portlet definition was added to the database and rerunning the EJPSBCA job will fail because of the reference in the database.

Remove and log files in the ConfigEngine/log folder and rerun EJPSBCA. This will cause the job to start from the beginning and rerun the basic-config portion which drops and recreates the Derby database.