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; } } }

DNR script called twice

Amit_LnT

Hi,
I have a DNR script in the OD config, which inserts data in the database.
I got data insertion failure. I checked the script log file and found that the scripts got called twice. In the first call, everything went fine. Immediately, it called the same script and it throwed insertion error with some primary key violation.
I am trying to find out, how could the DNR script got called twice?
I checked the OD base log, and it showed me the DNR script failed and return status as fail (DNR is transactional).

It just happened once and now its working fine.

Does anyone had the same experience with DNR before?
Also, if anyone could share some thought where should I investigate for this, will be really appreciated..

Env: TS 6.5 sp3 on windows server 2003. OD 6.1.0

Find more posts tagged with

Comments

sniv

Hey,

DNR script trigger multiple times depending on the DNR trigger and the number of deployment legs.

If the deployment entails multiple nodes, the DNR script will execute once for each micro leg. For example, if there is a fan-out deployment with 4 nodes, OpenDeploy will execute a micro leg to 4 different targets and each micro leg will try to execute the DNR. Thus, OpenDeploy will execute the DNR four times.

If the intention is to run the DNR once, use the "dnrDeploymentJob", which is run once per job.

Hope this help you!

Regards!
Vinayak

LocationAssetHierarchy.rptdesign

Adam Stoller

Hey,

DNR script trigger multiple times depending on the DNR trigger and the number of deployment legs.

If the deployment entails multiple nodes, the DNR script will execute once for each micro leg. For example, if there is a fan-out deployment with 4 nodes, OpenDeploy will execute a micro leg to 4 different targets and each micro leg will try to execute the DNR. Thus, OpenDeploy will execute the DNR four times.

If the intention is to run the DNR once, use the "dnrDeploymentJob", which is run once per job.

Hope this help you!

Regards!
Vinayak

The problem with dnrDeploymentJob is that you either need to run it before or after all the file deployments and as the database model performs a commit on success you can either end up with data deployed to your database without the associated files being deployed to your web/app server (if DNR runs before) if the file deployment fails for some reason -or- you can end up with files deployed to your web/app server without the data having been deployed to the database (if DNR is run after).

If run before - there is no [built-in] way to rollback the database in the event of file deployment failure.
If run after - there is no [built-in] way to rollback the file deployments if there is a data deployment failure.

The alternative, which I've documented before, is that you duplicate your definitions and break up your farms so that (in the example you provided) you would have FarmA with one node and FarmB with three nodes. The definitions would be identical except with regard to the farm being referenced. You would then have two execDeploymentTasks - one which uses the definition that references FarmA and performs the DNR for DD, and the other which references FarmB and does not invoke a DNR. The allows you to get the built-in transactional rollback functionality.

If you want to use the dnrDeploymentJob concept the config files are simpler, but you have to build your own rollback functionality that finds the files or data that used to be out there and attempts to redeploy them to overwrite the partial deployment that preceded it (and then you have to figure out what to do if your custom rollback deployment fails ...)

Amit_LnT

If the deployment entails multiple nodes, the DNR script will execute once for each micro leg.

Thank you Vinayak and Adam for you valuable inputs.
As Vinayak mentioned, that the DNR script will be executed number of times the nodes mentioned in the OD config file. I have one farm, containing two nodes specifed in my config file. So one execdepoymenttask with DNR script.
But, when I checked the log file for past 3 weeks and the script got called only once for each deployment.
I am finding difficulty to confirm the above quote from Vinayak.
It just happened only once that script got called twice.
For reference, I have attached the OD config file.

Did I misunderstood something here?

Thanks,
Amit

Steps.docx

DataSection.docx

Adam Stoller

Thank you Vinayak and Adam for you valuable inputs.
As Vinayak mentioned, that the DNR script will be executed number of times the nodes mentioned in the OD config file. I have one farm, containing two nodes specifed in my config file. So one execdepoymenttask with DNR script.
But, when I checked the log file for past 3 weeks and the script got called only once for each deployment.
I am finding difficulty to confirm the above quote from Vinayak.
It just happened only once that script got called twice.
For reference, I have attached the OD config file.

Did I misunderstood something here?

Thanks,
Amit

If you have two nodes in your farm, I don't believe there is any way that the config file you posted would only exec the DNR script once. The scenarios I can think of where what you posted would work are:

data - then DD will issue an INSERT directive - but if the script is called twice (or more, once per deployment leg) then the first running will work (INSERT OK), but all subsequent runs will fail (unable to INSERT an already existing record - must use UPDATE).

Amit_LnT

[QUOTE=ghoti]

Adam,This config file has been released to production three months back and not modified after that. (We do not get direct access to the server and modified date is also not changed). This config file is used daily and runs the DNR only once (according to log file). So, I think the first option you mention might be working here.But, still there is question. If it works in above way, why script got called twice?Also, the script always do a delete + insert in the database.Do you think, it might be a glitch in OD or will it be good if I put this to IW support?Thanks,Amit

Adam Stoller

Adam,
This config file has been released to production three months back and not modified after that. (We do not get direct access to the server and modified date is also not changed). This config file is used daily and runs the DNR only once (according to log file).
So, I think the first option you mention might be working here.
But, still there is question. If it works in above way, why script got called twice?
Also, the script always do a delete + insert in the database.

Do you think, it might be a glitch in OD or will it be good if I put this to IW support?

Thanks,
Amit

This is a custom implementation, so unless you can prove that there is a bug in the product - the onus is on you to find/fix the problem in the implementation (you can try to open a case with Support on this, but chances are you're not going to get far unless you can prove that there is a bug in the product).

We've already given you lots of information about how this works and why you might be running into problems - but we don't have access to your servers, and we are not getting paid to fix your problems - so again, the onus is on you to dig deeper and figure out what's happening.

Amit_LnT

Adam,
I do not wish anyone to solve my problem (that will not help me for future as well). I was just wondering if people can help me in looking at right direction if I am missing anything. Smiley Happy

And the help with this thread has certainly helped me moving ahead.
Thank you all. I will take it further.