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

Return status of Datadeployment.. in Failure condition

Parag

Hi all,
Is there any way to catch the return status of datadeployment?

My datadeplyment file is viewers_dd.xml
In a simple perl script I am invoking this dd script by following command:
$iwodcmd=path of iwodcmd start fileneme;
my $result=`$iwodcmd 2>&1`;
print $result;

Here $result prints:

Locating OpenDeploy service.
Got OpenDeploy service
>>>>>-- Start deployment Viewers_dd.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
>>>>>-- Deployment Viewers_dd finished:
ID: m313 Start time: Fri Aug 03 02:42:28 PDT 2007
Status: Completed

If the content goes beyond the capacity of the column, then also the status returns same.

I want to catch the failure status, in cases where database does not updates, like the value entered is too large for the column or any mandatory filed missing voilating consrtraints.

Is there any way to catch the proper failure stattus?

Thanks
-Parag

Find more posts tagged with

Comments

moonkhanna

parse the micro deployment logs. Would require analysis at your end.

Parag

parse the micro deployment logs. Would require analysis at your end.

ohhh no... its very hectic...
any other(easy)way?

Parag

ok..
so no other way to get this done?
I'll have to read the micro deployment log only?

As currently this is routed thru a workflow. 20 deploment configurations are invoked thru this. Is it the right option to read the logs for the dd status?

As the log are incrementing continiously how can we check the latest entry in it?

Thanks,
-Parag

Adam Stoller

Hi all,
Is there any way to catch the return status of datadeployment?

My datadeplyment file is viewers_dd.xml
In a simple perl script I am invoking this dd script by following command:
$iwodcmd=path of iwodcmd start fileneme;
my $result=`$iwodcmd 2>&1`;
print $result;
...

Have you tried examining

as in:

...
my $result = qx($iwodcmd 2>&1);
my $status = $? >> 8;
if ($status) {
    # ERROR
}
...

Parag

Have you tried examining

as in:

...
my $result = qx($iwodcmd 2>&1);
my $status = $? >> 8;
if ($status) {
    # ERROR
}
...

Yes, I have tried this.

I want to catch the error when something is missing like constraints, or data is larger than the size.

The above code returns success in these conditions also

Adam Stoller

Yes, I have tried this.

I want to catch the error when something is missing like constraints, or data is larger than the size.

The above code returns success in these conditions also

You're saying the deployment failed, but the status returned 0 (zero)?
What version of DataDeploy are you using?
If you can provide a repeatable process for having this occur you should definitely open a support case with Interwoven.

If you want the details of what failed - you have to parse the log file associated with the deployment. When we had iwdd.ipl one would pass a log parameter to specify the log file and thus from a script you could easily know what file to parse after the deployment. With the restructuring of DD as a component of OD I don't recall if you still have that option, or whether you have to conjure up the name of the macro and micro log files in order to find and parse them.

ISCBorisB

You're saying the deployment failed, but the status returned 0 (zero)?

I've seen that happening many times. I'm sure you did too. The reason was always poor design where OD process has not been *informed* that it failed.

Some samples:
1. DNR scripts do not return <response code="-2"/> on failure (and often do not even check if they did fail)
2. Stored procedures ( DD case ) that return 0 regardless of operational status.
3. Combination of 1 and 2 where DNR does return -2 in some cases but not other are pathetically hard to debug.
4. Failed DB triggers. In this case, even if triggered SP does properly report failure to the DB Engine OD/DD has no way of knowing it.

Adam Stoller

I've seen that happening many times. I'm sure you did too. The reason was always poor design where OD process has not been *informed* that it failed.

Some samples:
1. DNR scripts do not return <response code="-2"/> on failure (and often do not even check if they did fail)
2. Stored procedures ( DD case ) that return 0 regardless of operational status.
3. Combination of 1 and 2 where DNR does return -2 in some cases but not other are pathetically hard to debug.
4. Failed DB triggers. In this case, even if triggered SP does properly report failure to the DB Engine OD/DD has no way of knowing it.

I agree - with the above - but in such cases - I don't think parsing the deployment log file is going to shed much light - will it? The above represent poor custom coding and not necessarily a bug in the application itself (which is what I thought was being stated)

ISCBorisB

The above represent poor custom coding and not necessarily a bug in the application itself (which is what I thought was being stated)

I seriously doubt that whatever Parag observes has been caused by OD bug. Chances are overwhelming that it's his problem

bonafide_certificate.rptdesign

nipper

I seriously doubt that whatever Parag observes has been caused by OD bug. Chances are overwhelming that it's his problem

I think we can safely say that about almost everyone on this board. Present comapnay excepted of course. Smiley Very Happy

Parag

I think we can safely say that about almost everyone on this board. Present comapnay excepted of course.

Please take a look of my dd script:
<data-deploy-configuration>

<data-deploy-elements filepath="$db_cfg_filepath" />

*** <client>

*******<deployment name="basearea">

*********** <source>

*************** <xml-source options="narrow"

*******area="$source_branch^/$source_area"

*******area-type="ts-filesystem"

*******xml-type="custom"

*******custom="yes">

*******<path name="templatedata/Viewers/ViewerCategory/data" visit-directory="deep"/>

****</xml-source>

*********** </source>

***

***<substitution>

***<field name="viewer/0/Category/0/Image/0"

*****match="/(.*)"

*****replace="/US/en/$1" />

***<field name="viewer/0/Category/0/BannerFile/0"

*****match="/(.*)"

*****replace="/US/en/$1" />

***</substitution>

***

*********** <destinations>

*************** 

****<database use ="$target_db"

****** update-type** = "standalone"

****** state-field** = "state"

****** enforce-ri*= "yes"

****** delete-tracker= "yes">

*****<search results-suppress-vpath ="f" results-program = "" />

*****<dbschema>

******* <group name="ECM_VIEWER_CATEGORY" table="ECM_VIEWER_CATEGORY_TEST" root-group="yes">

******* <attrmap>

******** <column name="Path" data-type="VARCHAR(255)" value-from-field="path"/>

******* <column name="CATEGORY_ID" data-type="VARCHAR(40)" value-from-field="viewer/0/ecmID/0" allows-null="no" is-url="no"/>

******* <column name="LOCALE" data-type="VARCHAR(42)" value-from-field="viewer/0/Category/0/Locale/0" allows-null="yes" is-url="no"/>

******* <column name="CONTENT_TYPE" data-type="NUMBER(1,0)" value-from-field="viewer/0/Category/0/Banner/0" allows-null="yes" is-url="no"/>

******* <column name="ACTIVE" data-type="NUMBER(1,0)" value-from-field="viewer/0/Category/0/Status/0" allows-null="yes" is-url="no"/>

******* <column name="TITLE" data-type="VARCHAR(80)" value-from-field="viewer/0/Category/0/Title/0" value="$locale_prefix^"* allows-null="yes" is-url="no"/>

******* <column name="IMAGE_FILE" data-type="VARCHAR(80)" value-from-field="viewer/0/Category/0/Image/0" allows-null="yes" is-url="no"/>

******* <column name="BODY" data-type="VARCHAR2(4000)" value-from-field="viewer/0/Category/0/Copy/0" allows-null="yes" is-url="no"/>

******* <column name="CONTENT_FILE" data-type="VARCHAR(80)" value-from-field="viewer/0/Category/0/BannerFile/0" allows-null="yes" is-url="no"/>

******* </attrmap>

******* <keys>

********<primary-key>

*********<key-column name="CATEGORY_ID"/>********************

********</primary-key>

******* </keys>

******* </group>

*****</dbschema>

*************** </database>

*********** </destinations>

******* </deployment>

*** </client>

</data-deploy-configuration>

---------------------------------------------------

The perl script in which this dd script is executed is:
#!/usr/iw-home/iw-perl/bin/iwperl

my $iwodcmd="D:\\Programs\\Interwoven\\OpendeployNG\\bin\\iwodcmd.exe start ";

my $count_param=@ARGV;
open(MYFILE,">>D:\\test-file.txt");
print MYFILE "\n $iwodcmd";

for($i=0;$i < $count_param ; $i++)
{
#print "argv[$i] = $ARGV[$i]\n";

$iwodcmd=$iwodcmd." ".$ARGV[$i];

}

print MYFILE "\n $iwodcmd";

my $result = qx($iwodcmd 2>&1);
my $status = $? >> 8;
if ($status) {
print MYFILE "\n Inside the loop";
}

print MYFILE "\n $result";
-------------------------------------------------

This perl script is executed from command line (with params)as:

\Programs\Interwoven\TeamSite\iw-perl\bin>iwperl d:\Programs\Interwoven\TeamSi
te\local\config\wft\Herbalife\Submit_and_deploy_testfile.ipl core/Viewers/ViewerCategory_dd_en_US
-k iwdd=basearea
-k source_branch=/default/main/US/Web/MyHerbalifecom/en
-k source_area=WORKAREA/Publisher
-k db_cfg_filepath=D:\Programs\Interwoven\OpenDeployNG\etc\database.xml
-k target_db=hl-atgecm-db

----------------------------------

on running this script I got the result as :

\Programs\Interwoven\OpendeployNG\bin\iwodcmd.exe start

\Programs\Interwoven\OpendeployNG\bin\iwodcmd.exe start core/Viewers/ViewerCategory_dd_en_US -k iwdd=basearea -k source_branch=/default/main/US/Web/MyHerbalifecom/en -k source_area=WORKAREA/Publisher -k replication_farm=MyHerbalife_en_US -k db_cfg_filepath=D:\Programs\Interwoven\OpenDeployNG\etc\database.xml -k target_db=hl-atgecm-db

Locating OpenDeploy service.
Got OpenDeploy service
>>>>>-- Start deployment core/Viewers/ViewerCategory_dd_en_US.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
>>>>>-- Deployment core/Viewers/ViewerCategory_dd_en_US finished:
ID: m342 Start time: Sun Aug 05 21:31:09 PDT 2007
Status: Completed

where the value for the filed ImageFile has more than 80 characters
And the dd log contains:
DBD: Column: CATEGORY_ID, field: viewer/0/ecmID/0, Index: 1,Converting '1185875499653' to VARCHAR
DBD: Column: Path, field: path, Index: 2,Converting 'templatedata\Viewers\ViewerCategory\data\1-test-category' to VARCHAR
DBD: Column: CONTENT_TYPE, field: viewer/0/Category/0/Banner/0, Index: 3,Converting '1' to DECIMAL
DBD: Column: ACTIVE, field: viewer/0/Category/0/Status/0, Index: 4,Converting '1' to DECIMAL
DBD: Column: TITLE, field: viewer/0/Category/0/Title/0, Index: 5,Converting '1-test-category' to VARCHAR
DBD: Column: IMAGE_FILE, field: viewer/0/Category/0/Image/0, Index: 6,Converting 'cvcvcxczxcccccccccccccccccccccccccccccccccccccccccccccccxzczxczxcsaaaaaaaaaffffffffffffffffffssssssssssssssssssssssffffffffffffffffffffffffffffsssssssssssssssssssssssffffffffffffffffffffffffffffffsssssssssssssssssssssssssffffff' to VARCHAR
DBD: Column: BODY, field: viewer/0/Category/0/Copy/0, Index: 7,Converting '1-test-category' to VARCHAR
DBD: UPDATE ECM_VIEWER_CATEGORY_TEST SET Path = ? , LOCALE = ? , CONTENT_TYPE = ? , ACTIVE = ? , TITLE = ? , IMAGE_FILE = ? , BODY = ? , CONTENT_FILE = ? WHERE CATEGORY_ID = ? AND Path = ? AND LOCALE is null AND CONTENT_TYPE = ? AND ACTIVE = ? AND TITLE = ? AND IMAGE_FILE = ? AND BODY = ? AND CONTENT_FILE is null
DBD: Column: Path, field: path, Index: 1,Converting 'templatedata\Viewers\ViewerCategory\data\1-test-category' to VARCHAR
DBD: Column: LOCALE, field: viewer/0/Category/0/Locale/0, Index: 2,Converting '' to VARCHAR
DBD: Column: CONTENT_TYPE, field: viewer/0/Category/0/Banner/0, Index: 3,Converting '1' to DECIMAL
DBD: Column: ACTIVE, field: viewer/0/Category/0/Status/0, Index: 4,Converting '1' to DECIMAL
DBD: Column: TITLE, field: viewer/0/Category/0/Title/0, Index: 5,Converting '1-test-category' to VARCHAR
DBD: Column: IMAGE_FILE, field: viewer/0/Category/0/Image/0, Index: 6,Converting 'cvcvcxczxcccccccccccccccccccccccccccccccccccccccccccccccxzczxczxcsaaaaaaaaaffffffffffffffffffssssssssssssssssssssssffffffffffffffffffffffffffffsssssssssssssssssssssssffffffffffffffffffffffffffffffsssssssssssssssssssssssssffffff' to VARCHAR
DBD: Column: BODY, field: viewer/0/Category/0/Copy/0, Index: 7,Converting '1-test-category' to VARCHAR
DBD: Column: CONTENT_FILE, field: viewer/0/Category/0/BannerFile/0, Index: 8,Converting '' to VARCHAR
DBD: Column: CATEGORY_ID, field: viewer/0/ecmID/0, Index: 9,Converting '1185875499653' to VARCHAR
DBD: Column: Path, field: path, Index: 10,Converting 'templatedata\Viewers\ViewerCategory\data\1-test-category' to VARCHAR
DBD: Column: CONTENT_TYPE, field: viewer/0/Category/0/Banner/0, Index: 11,Converting '1' to DECIMAL
DBD: Column: ACTIVE, field: viewer/0/Category/0/Status/0, Index: 12,Converting '1' to DECIMAL
DBD: Column: TITLE, field: viewer/0/Category/0/Title/0, Index: 13,Converting '1-test-category' to VARCHAR
DBD: Column: IMAGE_FILE, field: viewer/0/Category/0/Image/0, Index: 14,Converting 'cvcvc' to VARCHAR
DBD: Column: BODY, field: viewer/0/Category/0/Copy/0, Index: 15,Converting '1-test-category' to VARCHAR
DBD:
DBD: *******************************************************
DBD: SQLException occured in TDbSchemaGroupCfg
DBD: Exception Message: ORA-12899: value too large for column "HLATGECM"."ECM_VIEWER_CATEGORY_TEST"."IMAGE_FILE" (actual: 227, maximum: 80)

DBD: Vendor Error Code: 12899
DBD: SQL state: 72000
DBD: *******************************************************
DBD:
DBD: *******STACK TRACE*************
DBD: ERROR:
java.sql.SQLException: ORA-12899: value too large for column "HLATGECM"."ECM_VIEWER_CATEGORY_TEST"."IMAGE_FILE" (actual: 227, maximum: 80)

at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:573)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:1093)
at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2047)
at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1940)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2709)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589)
at com.interwoven.dd100.dd.TDbSchemaUpdateHelper.UpdateOneRow(TDbSchemaUpdateHelper.java:882)
at com.interwoven.dd100.dd.TDbSchemaUpdateHelper.DoUpdate(TDbSchemaUpdateHelper.java:728)
at com.interwoven.dd100.dd.TDbSchemaGroupCfg.DoRealUpdate(TDbSchemaGroupCfg.java:827)
at com.interwoven.dd100.dd.TDbSchemaCfg.RealUpdateWithGroupTree(TDbSchemaCfg.java:953)
at com.interwoven.dd100.dd.TDbSchemaCfg.RealUpdate(TDbSchemaCfg.java:933)
at com.interwoven.dd100.dd.TDbSchemaAgent.BasicWriteTuple(TDbSchemaAgent.java:439)
at com.interwoven.dd100.dd.TDbSchemaAgent.WriteTuple(TDbSchemaAgent.java:334)
at com.interwoven.dd100.dd.TTupleSubstitutor.WriteTuple(TTupleSubstitutor.java:113)
at com.interwoven.dd100.dd.TConsumerManager.WriteConsumerInternal(TConsumerManager.java:399)
at com.interwoven.dd100.dd.TConsumerManager.WriteConsumers(TConsumerManager.java:388)
at com.interwoven.dd100.dd.TAgentClient.DoOneTeamSiteSource(TAgentClient.java:1008)
at com.interwoven.dd100.dd.TAgentClient.DoTeamSiteSources(TAgentClient.java:508)
at com.interwoven.dd100.dd.TAgentClient.DoOneDeployment(TAgentClient.java:295)
at com.interwoven.dd100.dd.TAgentClient.Go(TAgentClient.java:183)
at com.interwoven.dd100.dd.IWDataDeploy.Go(IWDataDeploy.java:545)
at com.interwoven.dd100.dd.TDASThread.ProcessItem(TDASThread.java:203)
at com.interwoven.dd100.dd.TDASThread.run(TDASThread.java:128)

DBD: ERROR Smiley Very Happy

oRealUpdate() failed for group [ECM_VIEWER_CATEGORY].
DBD: -- Failed
DBD: ERROR:WriteTuple failure to consumer[0]
DBD: ERROR:Unable to process TeamSite source templatedata/Viewers/ViewerCategory/data
DBD: ERROR:deployment [basearea] FAILED
DBD: Error occured in area outside TDbAgent consumer (explicit rollback initiated)
DBD: Stat for group [ECM_VIEWER_CATEGORY]:
DBD: -----------------------------------
DBD: Rows inserted : 0
DBD: Rows updated : 0
DBD: Rows deleted : 0
DBD: Rows failed : 0
DBD: Rows rolled back : 0
DBD: Rows skipped : 0
DBD: -----------------------------------
DBD: Rollback database [uslaxatgdevdb.hrbl.net:1521:HLATG]...
DBD: Deployment[basearea]
DBD: -----------------------------------
DBD: DCRs inserted : 0
DBD: DCRs updated : 0
DBD: DCRs deleted : 0
DBD: DCRs failed : 0
DBD: DCRs rolled back : 0
DBD: DCRs skipped : 0
DBD: -----------------------------------
DBD: Started : Sun Aug 05 21:31:09 PDT 2007
DBD: Shutting down DDD PublisherThread
DBD: Finished: Sun Aug 05 21:31:09 PDT 2007
DBD:
### IWDataDeploy DONE ###

DBD:
### Sending result ###

ENG: 2007-08-05 21:31:09 PDT GMT-07:00 Database deployment execution returned 0

ENG: 2007-08-05 21:31:09 PDT GMT-07:00 <<< Completed database deployment Invocation>>>

ENG: 2007-08-05 21:31:09 PDT GMT-07:00 doTask returned 0

ENG: 2007-08-05 21:31:09 PDT GMT-07:00 Setting final state to TASKDONE

ENG: 2007-08-05 21:31:09 PDT GMT-07:00 Manifest path is

/Programs/Interwoven/OpenDeployNG/log/core/Viewers/src.ViewerCategory_dd_en_US.basearea.USLAXCMSDEV.to.database.log.mf

ENG: 2007-08-05 21:31:09 PDT GMT-07:00 Got Manifest object com.interwoven.od.adapter.delivery.base.IWODManifest@4194e0

ENG: 2007-08-05 21:31:09 PDT GMT-07:00 fHasFailedItems is set to false

ENG: 2007-08-05 21:31:09 PDT GMT-07:00 TEventReportingException: com.interwoven.report100.TPublisherNotFoundException
ENG: 2007-08-05 21:31:09 PDT GMT-07:00 Job ID=m342 Deployment leg=database Elapsed Time=94 ms <<<
ENG: 2007-08-05 21:31:09 PDT GMT-07:00 End logfile [D:\Programs\Interwoven\OpenDeployNG\log\core/Viewers\src.ViewerCategory_dd_en_US.basearea.USLAXCMSDEV.to.database.log]

---------------------

Thanks,
-Parag

TeamSite 6.7.1
OD 6.1
Win 2003 Server