Prevent database rollback

Running a standalone datadeployment to an oracle 10g db, and the deployment often fails on account of a single record, while 300 other records don't get inserted. Is there a way to prevent the entire database transaction from rolling back?

Find more posts tagged with

Comments

Adam Stoller

Running a standalone datadeployment to an oracle 10g db, and the deployment often fails on account of a single record, while 300 other records don't get inserted. Is there a way to prevent the entire database transaction from rolling back?

Do you understand what a transactional deployment means?
All-or-none.
Therefore your question, as worded, makes no sense.

Instead you should be focusing on why that one record fails and either fix that situation (either truly fix, or remove that record from consideration) so that you get correctly successful transactional deployments to your database.

Assia

Ok, thanks, I'll try to re-phrase. Can datadeploy be configured not to use transactional deployments? I would like the failure of the particular record(s) to be resolved at a later time by the admin, after he examines the logs.

Adam Stoller

Ok, thanks, I'll try to re-phrase. Can datadeploy be configured not to use transactional deployments? I would like the failure of the particular record(s) to be resolved at a later time by the admin, after he examines the logs.

I do not believe that DataDeploy provides for non-transactional deployments. You could (and perhaps should) check with Support - and if (as I believe) DD does not support a non-transactional mode, you can file an official feature request for it