nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DNRdeploymentJob not accepting the response code -2

Karthik_SP

Hi

We have a deployment to different locations (web server and app server) and also a datadeploy as dnr.

For datadeploy, we are using DNRDeploymentJob. During the failure of DD, we are print response code -2 and exiting the perl script.

Even if the response code is -2, transactional deployment is succeeds with status as completed.

We found in OD611.deploy PDF, it is mentioned that response code -2 is applicable only for task level dnr. Please let us know how to resolve this. We have tried executing a dummy deployment and then running the dnrdeployment for that dummy deployment. In this case, proper status is returned. But we want to avoid the additional deployment. Please suggest.

Teamsite 671SP1
Solaris 10
OD 611 with DD enabled

Thanks & Regards,
Karthik

Find more posts tagged with

Comments

Adam Stoller

Hi

We have a deployment to different locations (web server and app server) and also a datadeploy as dnr.

For datadeploy, we are using DNRDeploymentJob. During the failure of DD, we are print response code -2 and exiting the perl script.

Even if the response code is -2, transactional deployment is succeeds with status as completed.

We found in OD611.deploy PDF, it is mentioned that response code -2 is applicable only for task level dnr. Please let us know how to resolve this. We have tried executing a dummy deployment and then running the dnrdeployment for that dummy deployment. In this case, proper status is returned. But we want to avoid the additional deployment. Please suggest.

Teamsite 671SP1
Solaris 10
OD 611 with DD enabled

Thanks & Regards,
Karthik

As you've already found out - dnrDeploymentJob running after the deployment is too late to cause failure. You would need to use dnrDeployment with a specific triggerPoint value ( I don't remember off-hand, but something like when="after" triggerPoint="transfer") - however, as you're doing a multi-legged deployment you run into the problem of trying to make sure that all legs of the file (OD) deployment are completed before you do the data (DD) deployment. It's even worse if your OD deployment includes fan-outs to multiple target receivers.

Are your OD deployments 1:1 or fan-out deployments?

Karthik_SP

We are using fan-out deployment.

Adam Stoller

We are using fan-out deployment.

Then you need to break up the replicationFarm so that you have one farm with one node and another farm with all the remaining nodes - make two definitions that are identical with exception being the replicationFarm they reference, and then have two execDeploymentTask's - one for the first farm (one node) that calls the DNR, and one for the second farm that does not call the DNR.