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

Deployment to non root group causing future deployments to fail.

TroyP

I think this is an easy question.

Linux
OD 6.1.1

I have a deployment that updates two tables called CR_Content and CR_Blob. The first table has metadata and the second table simple has two columns which are the path and CLOB (contents of files of the files I am deploying).

Most of the time the deployment works fine. However if the Metadata is not set correctly on a file then sometimes the CR_Blob is updated when the update/insert to the CR_Content table fails. Event after the metadata is fixed then the next and future deployments fail because of a PK violation on the CR_Blob table.

How can I fix this? I have asked myself these questions.

1. Are my PK and FK correct on the tables and my DD config file?
2. Should I separate this deployment into two different deployments?
3. Should I make the CR_Blob group the root group rather than the CR_Content?
4. Is there a setting that says "don't continue if the root-group update fails.
[HTML]

global="yes"/>

[/HTML]

Find more posts tagged with

Comments

TroyP

This problem is almost resolved. I did #3 which helped 95% of the time.

Now I am only faced with the problem when a file is renamed in TeamSite. The PK of the CR_Content table is an EA on the file and when it's renamed then there is a PK violation error because DD tries to do an INSERT on both tables rather than an INSERT on the CR_Blob table and an update on the CR_Content table.

I think there are two solutions to my problem.

A. Separate the deployment groups into two deployments.
B. Set the PK for the CR_Blob table as an EA on the file rather than us the path. This would mean that when a file is renamed the PK value for the CR_Blob table would be in the EAs with the PK values for the CR_Content table.

A. is "cleaner" IMHO.
B. is is more complex but does keep the deployment as one and thus can be transactional (at least at the file level).

Thoughts?

Ugan

The way it is working now seems to be the good approach and it should be implement it in same way (the other problems which you are seeing are very rare). 2 separete deployments of same file or dcr is a tedious process and not a good approach, The other option B i did not understand it properly.

Thanks,
UD

Ugan

One more approach is XML, DB approach, Send the metadata to DB (using DD) and the content to a flat xml file (using OD) to the application and DB server. and from application side using a query we can use metadata and from XML properties we can use the content.