DD 6.0.2 rowmapgen can't handle variables

Bill Klish

TeamSite 6.5 SP1
Solaris 2.9
OpenDeploy/DataDeploy 6.0.2

I have a huge database deployment that needs to run, so we attempted to pregenerate the row map cache file using iwsyncdb -rowmapgen, but it failed using my data deploy configuration file since the area is specified as a variable. Here is the snippet from the source section:





and this is the error that was returned:

[12:52:02]$ ../../bin/iwsyncdb -rowmapgen /tmp/EnhancedBrand-JobVacancies-ddconfig.xml EnhancedBrand-JobVacancies /tmp/rowmap.out
DD Home : /opt/iw-home/OpenDeployNG
args[ 0 ] -rowmapgen
Config file /tmp/EnhancedBrand-JobVacancies-ddconfig.xml
Deployment Name EnhancedBrand-JobVacancies
RowmapCache file /tmp/rowmap.out
DataDeploy Version 6.0.2.0.0 Build 46963 Interwoven 20050402
DD Home : /opt/iw-home/OpenDeployNG
args[0]:cfg=/tmp/EnhancedBrand-JobVacancies-ddconfig.xml
args[1]:iwdd=EnhancedBrand-JobVacancies
args[2]:rowmapgen=yes
args[3]:rowmapcachefile=/tmp/rowmap.out
numArgs=4
**WARN**ubstituteParameters 104 Replacing undefined parameter $sourceArea with empty string
**ERROR**:com.interwoven.dd100.dd.TGenericXmlDataCfg 103 TeamSite element does not specify a TeamSite area
Database Vendor set to rdbms
# of groups defined in element: 2
[Mon Nov 21 12:52:09 CST 2005] Begin executing EnhancedBrand-JobVacancies
ERROReployment "EnhancedBrand-JobVacancies" has an invalid data source
Started : Mon Nov 21 12:52:09 CST 2005
Finished: Mon Nov 21 12:52:09 CST 2005
Done executing iwsyncdb-rowmapgen

Is the value of this parameter required to generate a cache file?

If I put a TeamSite /default/main path in there, everything works fine

Where is this feature documented? There are no occurrences of it in the DataDeploy 6.0.2 Admin manual.

Migrateduser

The feature is partially documented in the OpenDeploy Reference guide, under the DataDeploy DTD. (I have a filed documentation bug on this to doc in the main guide.)

The value of the area is not needed for the generation of the row map. Since DD is using the deployment config to read the dbschema, it's probably checks the deployment config as a whole to see if it's valid. Ideally it should have skipped the params outside the dbchema, since dbschema is actually the part the row map gen needs. Easy to workaround, but kind of a pain. I'll file a bug.

Mariam