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

transactional data deployment

Amit_LnT

Hi,
I have a requirement of making two data deployments transactional. First is a do-sql deployment and next is db schema deployment.
I have written third deployment following way
<deployment name="Article_Text_multi">
<exec-deployment use="pre_dd"/>
<exec-deployment use="Article_Text"/>
</deployment>
Both deployments individually works fine.
Pre_dd is a do-sql deployment. I want to make them transactional.
But when I run the command, it shows success, but not updating database.
Following is the log

ENG: 2007-08-29 18:55:30 EDT GMT-04:00 Begin logfile [D:\iw-home\OpenDeployNG\log\src.mhrs_geo_datadeploy.Article_Text_multi.gd1wpcmsap11.to.database.log] ---------
ENG: 2007-08-29 18:55:30 EDT GMT-04:00 Job ID=m480 Deployment=mhrs_geo_datadeploy
ENG: 2007-08-29 18:55:30 EDT GMT-04:00 DataDeploy Version is 6.1.0.0.0
ENG: 2007-08-29 18:55:30 EDT GMT-04:00 Owner started the deployment is amit-bhoyar2
ENG: 2007-08-29 18:55:30 EDT GMT-04:00 DD args iwdd-op="do-sql" area="/mhrs/main/MHRSGEO/CANADA/WORKAREA/wa/" psw="XXXXX" iwdd="Article_Text_multi" user="XXXX" user-op="pre_dd_geo" conn_str="10.203.61.62:1433?database=MHRSGEO" vpath="templatedata/English/Plan_Documentation/data/vijuQatest3" id_content="7F5786F9-9AD9-4122-92E0-F935D56E9037" cfg=d:\iw-home\OpenDeployNG\conf\mhrs_geo_datadeploy.xml need-result=yes depuuid=f1502190-5682-11dc-8195-9f2ccc7ddf09 leglabel=database

ENG: 2007-08-29 18:55:30 EDT GMT-04:00 Proceed to execute the database deployment

DBD: Deployment : Article_Text_multi
DBD: Database Vendor set to microsoft-inetuna
DBD: Database Vendor set to microsoft-inetuna
DBD: SQL datatype for column SummaryHeadline is char(100)
DBD: SQL datatype for column Summary is char(500)
DBD: SQL datatype for column Headline is char(200)
DBD: SQL datatype for column Body is char(5000)
DBD: SQL datatype for column ExpirationDate is DATETIME
DBD: SQL datatype for column EffectiveDate is DATETIME
DBD: SQL datatype for column CreationDate is DATETIME
DBD: # of columns: 10
DBD: # of primary key columns specified: 1
DBD: # of columns: 2
DBD: # of primary key columns specified: 2
DBD: # of foreign key columns specified: 1
DBD: # of columns: 2
DBD: # of primary key columns specified: 2
DBD: # of foreign key columns specified: 1
DBD: # of columns: 2
DBD: # of primary key columns specified: 2
DBD: # of foreign key columns specified: 1
DBD: # of columns: 2
DBD: # of primary key columns specified: 2
DBD: # of foreign key columns specified: 1
DBD: # of columns: 2
DBD: # of primary key columns specified: 2
DBD: # of foreign key columns specified: 1
DBD: # of columns: 2
DBD: # of primary key columns specified: 2
DBD: # of foreign key columns specified: 1
DBD: # of columns: 2
DBD: # of primary key columns specified: 2
DBD: # of foreign key columns specified: 1
DBD: # of groups defined in element: 8
DBD: [Wed Aug 29 18:55:30 EDT 2007] Begin executing Article_Text_multi
DBD: Setting up consumer TDbAgent
DBD: Validating cached connection...
DBD: Cached connection OK
DBD: Connected to [10.203.61.62:1433?database=MHRSGEO]
DBD: Consumer setup for deployment [pre_dd] ok
DBD: Setting up TDbSchemaAgent.
DBD: Validating cached connection...
DBD: Cached connection OK
DBD: Connected to [10.203.61.62:1433?database=MHRSGEO]
DBD: Consumer setup for deployment [Article_Text] ok
DBD: iwdd-op=do-sql
DBD: Committing database [10.203.61.62:1433?database=MHRSGEO]...
DBD: Deployment[Article_Text]
DBD: Deployment[pre_dd] Table[NO_TABLE_NEEDED]
DBD: -----------------------------------
DBD: Tuples inserted : 0
DBD: Tuples updated : 0
DBD: Tuples deleted : 0
DBD: Tuples failed : 0
DBD: Tuples rolled back : 0
DBD: Tuples skipped : 0
DBD: -----------------------------------
DBD: Started : Wed Aug 29 18:55:30 EDT 2007
DBD: Finished: Wed Aug 29 18:55:30 EDT 2007
DBD:
### IWDataDeploy DONE ###

DBD:
### Sending result ###

ENG: 2007-08-29 18:55:30 EDT GMT-04:00 Database deployment execution returned 0

ENG: 2007-08-29 18:55:30 EDT GMT-04:00 <<< Completed database deployment Invocation>>>

ENG: 2007-08-29 18:55:30 EDT GMT-04:00 doTask returned 0

ENG: 2007-08-29 18:55:30 EDT GMT-04:00 Setting final state to TASKDONE

ENG: 2007-08-29 18:55:30 EDT GMT-04:00 Job ID=m480 Deployment leg=database Elapsed Time=125 ms <<<
ENG: 2007-08-29 18:55:30 EDT GMT-04:00 End logfile [D:\iw-home\OpenDeployNG\log\src.mhrs_geo_datadeploy.Article_Text_multi.gd1wpcmsap11.to.database.log]

Pre-dd deletes entry from DB and next deployment inserts it. Ideally, third deployment should create two logs files for pre-dd and Article_Text. But I did not find any log file for them. I checked in DB, even pre-dd is not getting invoked, as data is still present in DB after Article_Text_multi deployment.
Is it possible to make them trasactional ? If yes, how does the command should be to invoke Article_Text_multi deployment?

help is much appreciated..

Env: Teamsite 6.5 SP2, windows server 2003

Thanks,
Amit Bhoyar

Find more posts tagged with

Comments

motlnt

not sure what the resolution is but it will be nice though to remove the username/pwd from the log you have posted....

RajatChopra

Hi,
I have a requirement of making two data deployments transactional. First is a do-sql deployment and next is db schema deployment.
I have written third deployment following way
<deployment name="Article_Text_multi">
<exec-deployment use="pre_dd"/>
<exec-deployment use="Article_Text"/>
</deployment>

.......
help is much appreciated..

Env: Teamsite 6.5 SP2, windows server 2003

Thanks,
Amit Bhoyar

Can you test out with


<deployment name="Article_Text_multi" transactional="yes" >
<exec-deployment use="pre_dd"/>
<exec-deployment use="Article_Text"/>
</deployment>

Amit_LnT

hey rajat,
thansk for suggestion.
i have tried that, the result is same.
and the transactional will come in picture when it will start invoking the deployments. Its not even invoking the pre-dd.
Going crazy with this.. fistly delete+insert did not work.
now there is no way for making these two deployments transactional..

motlnt: thnx for pointing that.. will def take care of such mistakes in future..
i m bit frusrated with this ****

thanks all

-Amit

Amit_LnT

well, I also tried calling the two dnr scripts in the opendeploy.
first deletes row in db and second inserts it.
looks like.
<deployment transactional="yes">
<execDeploymentTask useDefinition="MYDEFINITIONNAME" >
<deployNRun>
<dnrDeployment location="source" when="after" state="success">
<script cmd="d:\iw-home\iw-perl\bin\iwperl.exe d:\iw-home\local\bin\GEO\mhrs_geo_data_Deploy_dd.ipl $job_id^ $task_id^ $workarea^ $files^ $passtask^ $dd_type^" async="no"/>
</dnrDeployment>
<dnrDeployment location="source" when="after" state="success">
<script cmd="d:\iw-home\iw-perl\bin\iwperl.exe d:\iw-home\local\bin\GEO\mhrs_geo_data_Deploy_dd.ipl $job_id^ $task_id^ $workarea^ $files^ $passtask^" async="no"/>
</dnrDeployment>
</deployNRun>
</execDeploymentTask>
</deployment>
this doesnt work, if second fails. OD does not rollback it when second DNR fails.
I do not unserstand, if OD is incapable of doing this, then why does it accepts multiple DNR scripts with transactional=yes

any suggestion..

thanks,
amit

RajatChopra

Well Amit lets try this as small as it can be. I think the crux of your problem is real-updates. If they work, you don't have to worry about insert's and deletes. So can you try out a simple 1 value deployment into a dummy table on your database? Put RealUpdates as yes and check the logs.

I am not sure about why the DNR doesn't roll back, but it wouldn't be the first time that DD is behaving in a weird fashion.

GRD

I believe that OD will not do transactional deployment when DNR's are involved. Nor will it allow more than one combination file/database deployment per transaction.

It will do multiple database deployments as a transaction, but not along with files.

-Greg

ISCBorisB

I believe that OD will not do transactional deployment when DNR's are involved. Nor will it allow more than one combination file/database deployment per transaction.

It will do multiple database deployments as a transaction, but not along with files.

-Greg

DataDeploy aside, transactional multi-definition Deployments with or without DNRs are perfectly legal. We do it all the time

RajatChopra

I believe that OD will not do transactional deployment when DNR's are involved. Nor will it allow more than one combination file/database deployment per transaction.

It will do multiple database deployments as a transaction, but not along with files.

-Greg

We have done multiple DD(database) and OD(file) DNR deployments from a single descriptor.
And we have certainly done transactional deployment for files. Don't recall doing the transactional for DataDeploy.

Adam Stoller

We have done multiple DD(database) and OD(file) DNR deployments from a single descriptor.
And we have certainly done transactional deployment for files. Don't recall doing the transactional for DataDeploy.

The problem here is that the request is for two separate DD deployments to be transactional - and after the first one has committed - the second one, if it fails, does not have the ability to un-commit the first.

I believe in order to do what is being requested, one would have to put both DD deployments into a single DD config, call it once and have the DD transactionally perform both operations before returning control to OD.

If either of the DD steps (within a single DD config) fail, it will roll back, and (assuming you've coded it correctly) will cause the OD operation to roll back too.

Amit_LnT

I believe in order to do what is being requested, one would have to put both DD deployments into a single DD config, call it once and have the DD transactionally perform both operations before returning control to OD.

If either of the DD steps (within a single DD config) fail, it will roll back, and (assuming you've coded it correctly) will cause the OD operation to roll back too.

Ghoti,
I tried the same. But it even did not invoked a single deployment written inside the third deployment .
The problem here is that the first deployment is a pre_dd with some SQL statements and the second deployment is schema deployment from DCR. Now both deployments have different command parameters. So the question is can we make such deployments transactional and if yes what should be the command for the third one ?
appreciate all for your help

Adam Stoller

Ghoti,
I tried the same. But it even did not invoked a single deployment written inside the third deployment .
The problem here is that the first deployment is a pre_dd with some SQL statements and the second deployment is schema deployment from DCR. Now both deployments have different command parameters. So the question is can we make such deployments transactional and if yes what should be the command for the third one ?
appreciate all for your help

(a) I responded in the other thread - please don't duplicate posts
(b) if the two deployments have to occur separately - I don't believe there is any way for the second to rollback the first - and thus they cannot be transactional as a set.

motlnt

Amit, if the above suggestions doesn't help then it will be wise to ask IWOV support.