Deploy of UPROC on target node fails
search cancel

Deploy of UPROC on target node fails

book

Article ID: 240243

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

We are trying to deploy objects like Task, Session, UPROC and BV from node OVM5 to target node NT-TEST-0443 and it fails for deployment of UPROC's, whereas other objects are getting deployed.

Screen shot of failure while deploying UPROC's

Environment

Release : 6.x

Component : DOLLAR UNIVERSE

Cause

In logs review of UVC and target node, we find that the UPROC's at source node are associated with Applications which are missing in the target node, resulting in failure.

UVC - univiewer.log (default location: c:\users\<user-name>\univiewer_console\logs)

|2022-04-20 15:24:23,347|ERROR||BackgroundWorker-31|com.orsyp.kmeleon.universe.UniverseBusiness|Problem during deployment of object [ADHOC_FCY][000] on [BSPTST/TARGET-NODE/X] 
|2022-04-20 15:24:23,363|ERROR||BackgroundWorker-31|com.orsyp.kmeleon.universe.deployment.UnifiedDeploymentBusiness$DeploymentAction|Problem occured during deployment of UPROC [ADHOC_FCY][000] on TARGET-NODE/X
com.orsyp.api.ObjectDependencyNotFoundException: Dependency not found - Application not found error

Target node - universe.log

| 2022-04-10 00:56:06 |ERROR|X|IO |pid=p.t| xn_get_id                 | O_TYPE_APPLICATION ID not found for <STANDARD>
| 2022-04-10 00:56:06 |INFO |X|IO |pid=p.t| o_io_cache_data_provider_ | ID for <STANDARD> Not Found
| 2022-04-10 00:56:06 |ERROR|X|IO |pid=p.t| get_appli_id              | cannot get internal ID for Application [STANDARD]
| 2022-04-10 00:56:06 |ERROR|X|IO |pid=p.t| get_appli_id              | cannot get internal ID for Application [CRITICAL]
| 2022-04-10 00:56:06 |ERROR|X|IO |pid=p.t| xn_get_id                 | O_TYPE_APPLICATION ID not found for <CRITICAL>
| 2022-04-10 00:56:06 |INFO |X|IO |pid=p.t| o_io_cache_data_provider_ | ID for <CRITICAL> Not Found

Resolution

The recommendation is to always use Expand (under Objects and Dependencies) while sending objects to a new node, so the user can select dependencies of objects getting deployed and can avoid dependencies failure due to missing application, domains, submission account etc. Please refer screen shot below