2

We did upgrade from Tridion 5.3 SP1 to Tridion 2011 SP1.

Most of the things are working fine. Publishing of few pages is getting failed at "Committing Deployment" state with below mentioned error. Database is SQL Server.

Phase: Deployment Prepare Commit Phase failed, Unable to prepare transaction: tcm:0-249333-66560, Unable to store
item inside current transaction, Unable to persist data entity, org.hibernate.exception.ConstraintViolationException:
could not insert: [com.tridion.storage.ComponentMeta], org.hibernate.exception.ConstraintViolationException: could
not insert: [com.tridion.storage.ComponentMeta], Unable to persist data entity,
org.hibernate.exception.ConstraintViolationException: could not insert: [com.tridion.storage.ComponentMeta],
org.hibernate.exception.ConstraintViolationException: could not insert: [com.tridion.storage.ComponentMeta], Unable
to store item inside current transaction, Unable to persist data entity,
org.hibernate.exception.ConstraintViolationException: could not insert: [com.tridion.storage.ComponentMeta],
org.hibernate.exception.ConstraintViolationException: could not insert: [com.tridion.storage.ComponentMeta], Unable
to persist data entity, org.hibernate.exception.ConstraintViolationException: could not insert:
[com.tridion.storage.ComponentMeta], org.hibernate.exception.ConstraintViolationException: could not insert:
[com.tridion.storage.ComponentMeta], Unable to prepare transaction: tcm:0-249333-66560, Unable to store item inside
current transaction, Unable to persist data entity, org.hibernate.exception.ConstraintViolationException: could not
insert: [com.tridion.storage.ComponentMeta], org.hibernate.exception.ConstraintViolationException: could not insert:
[com.tridion.storage.ComponentMeta], Unable to persist data entity,
org.hibernate.exception.ConstraintViolationException: could not insert: [com.tridion.storage.ComponentMeta],
org.hibernate.exception.ConstraintViolationException: could not insert: [com.tridion.storage.ComponentMeta], Unable
to store item inside current transaction, Unable to persist data entity,
org.hibernate.exception.ConstraintViolationException: could not insert: [com.tridion.storage.ComponentMeta],
org.hibernate.exception.ConstraintViolationException: could not insert: [com.tridion.storage.ComponentMeta], Unable
to persist data entity, org.hibernate.exception.ConstraintViolationException: could not insert:
[com.tridion.storage.ComponentMeta], org.hibernate.exception.ConstraintViolationException: could not insert:
[com.tridion.storage.ComponentMeta]
user1453602
  • 1,165
  • 5
  • 14
  • Did you use the sample cd_storage config file from the install or your old one? Maybe try to use the sample and move your db settings and bindings into it? – robrtc Nov 23 '12 at 08:53
  • Yes we used sample cd_storage config and moved our setting to it. Most of the pages are getting published successfully. Few pages are getting failed. – user1453602 Nov 23 '12 at 09:30
  • We also found that when we have particular component on page, then only it is gettting failed. If we remove that component(presentation) then page is getting published successfully. – user1453602 Nov 23 '12 at 09:55
  • Is it possible you restored the Broker DB with an older version than the CM DB? Then your CMS will have an item with URI 12345 for a news item but the Broker might have 12345 with a product item? Then, when publishing, it tries to update the item but it is actually 2 different ones? I would suggest to do another restore of your BRoker DB and CMS DB from Production (or your source system) and try again. – robrtc Nov 23 '12 at 13:50
  • To restore the databases again will be costly activity. But yes, Backup of CMS, Log and Broker was taken at same time. Also we keep PR freeze while taking backup. I do agree with you that there must be some mismatch, as we know which component is causing issue, is there any way (query) to check in broker what is going wrong for that particular component ? – user1453602 Nov 23 '12 at 14:27
  • How many deployer instances do you have running? Could it be there's more than one pointing to the same broker db? – Quirijn Nov 23 '12 at 14:53
  • We have only one deployer instance. – user1453602 Nov 27 '12 at 17:14

2 Answers2

1

I seem to remember a similar problem that was addressed by hotfix CD_2011.1.1.82946 which is available on sdltridionworld.com. Note that this hotfix was built specially for version 2011 SP1 HR1.

Hope this helps.

Cheers, Daniel.

Daniel Neagu
  • 1,711
  • 11
  • 13
1

I just upgraded to Tridion 2011 SP1 HR1 and got the exact same error even after applying CD_2011.1.1.82946

Apparently, there's another hotfix (unreleased on SDL Tridion World) called CD_2011.1.1.83467 which fixed the issue

Robert Jin
  • 241
  • 2
  • 4