OD updating changed replicants but deleting others

Open Deploy Ver: 6.0.2.0.0 Build 46963

have Document template with 11 replicants. First time(table doesn't have records for this particular project), after deploying I am seeing 11 records in the table relating to each replicant. But if I repeat the same deployment, it is showing only 2 records, the other records are deleted. If I delete all the existing records and do the deployment again, it is inserting 11 records.

After few deployements, I found, whatever the modified replicant data is updating in the database, the other non-replicated records are being deleted.

I have this statement in config file:
<database use="oracle9_db" update-type="standalone" delete-tracker="yes" real-update="yes">

Is there any xml tag(or command or property), which informs OD(DD), to update the changed records and delete the remaining unchanged records?
I appreciate any help to resolve this. Thanks

Find more posts tagged with

Comments

Srinivasa Talla

Correction :
New : After few deployements, I found, whatever the modified replicant data is updating in the database, the other non-modified(replicants) records are being deleted.

Migrateduser

We're having the same problem with DataDeploy. We have 2 containers in the same DCT and we want the values of those replicants to go to the same fields in the same table. We have them as seperate containers for simplicity for the end users.
[html]

[/html]

[font=Verdana]As you can see, we're trying to deploy to the same columns from 2 different replicants in the same DCR.

[/font]

The results we're getting are as follows:

Initial Insert - Works as expected. The rows are inserted for both sets of replicants.

Update FAQ - deletes FAQ rows. (see attached log)

Questions: Is what we're trying to do possible? If so, what are we doing wrong? If not, what would the best workaround be?

Thanks,

Jason

Bill Klish

I don't see the attached log.

We ran into this issue with OD 6.0.2 on solaris 2.9. It is a bug that is fixed in SP1. Basically, we had to turn real-updates off to get it to work, but our database performance suffers and the deployments take longer.

If upgrading isn't an option, try to turn real-updates off.

Migrateduser

We tried turning off real-updates and it didn't seem to make a difference. Also, looking at the release notes for SP1, this issue is not mentioned. Once you installed SP1, it worked? If that's our only solution, then we'll have to figure out a way.

Thanks for the reply,

- Jason

Bill Klish

Let me see if I can find the bug # so you can verify that it matches your issue.

Migrateduser

Found a workaround. Had to turn Real Updates on and Enforce RI off. We were then able to deploy correctly. Have not had a chance to install SP1 yet. That may also resolve the problem.

Thanks for your help,

Jason

RajatChopra

This workaround is not working for us and we have OD 6.1 with Teamsite 6.7.1 on Windows.

It seems, that the problem is being caused by setting foreign key mapping in the data deploy descriptors. After removing the mapping, it started functioning as expected. Can some one throw some light on this?

Thanks,
-R