Where the **** is ddconv.ipl?

This is a sort of long question? I don't want to be vague, though.

I am using TS 5.5.2, Templating 5.5.2, and DD 5.5.2. Currently, I am fooling around with the example templates to get a feel for things. I have successfully set up DD to interact with an Oracle8i database using a wide tuple arrangement--pretty much out of the box with a couple of tweaks as prescribed in the documentation. Good so far.

I thought I might fiddle with the press release capture / deploy by setting up my dbschema.cfg to take the Introductory Paragraph. My thinking would be to run the iwsyncdb.ipl with the appropriate sequence of options (-dbschemagen [vpath] -force and -ddgen [vpath] -force) and hopefully the resulting [type]_dd.cfg file would reflect the change.

Well, this was not the case. The ..._dd.cfg file had all of this commentary to the effect that this section of junk had been automatically created using ddconv.ipl. I did a search of my entire filesystem to find this file to no avail.

So, where the **** is ddconv.ipl?

What I am really after though: Can I reconstitute the structure of a database table and preserve the data etc. if I need to add a field from a dcr. Or, are the tables immutable once created? Bear in mind that I am asking this question from a DD perspective. I know that I can use PL/SQL calls to perform all of the magic that I desire, but can I do it through DD configuration TS event triggering?

Thanks for bearing with this question?

Find more posts tagged with

Comments

Migrateduser

I didn't quite understand exactly what problem you have.

There is nothing called ddconv.ipl in DataDeploy. Not sure where you found any kind of reference to it.

DataDeploy isn't capable of dynamically altering the structure of a table, if you modify the dbschema.cfg or the resulting/derived type_dd.cfg file. DD simply checks if the table specified in the <group> element exists. If the table doesn't exist, it creates one with the <column> definitions you provide in the config file. If it already exists, it proceeds to deploy the data.

So, if you have to modify the dbschema.cfg or the type_dd.cfg file in between deployments, in the sense that you are adding or dropping columns in the schema definition, it's better to drop the existing tables or alter them outside of DD, using one of the Oracle client tools, before running the deployments.

The PressRelease example is a custom dcr type. Out of the box example ships a DTD (pr.dtd) for it. iwsyncdb.ipl -dbschemagen command looks up the iwhome/local/conf/templating.cfg file to see the type of the dcr (if it is custom or iwov style) and generates the dbschema.cfg either from datacapture.cfg (if iwov style) or from the DTD (if custom dcr style). In the later case, it looks for <template_type_name>.dtd file under the workarea/templatedata/category/type directory. Therefore, before you run iwsyncdb.ipl -dbschemagen command for this type, rename the pr.dtd to PressRelease.dtd. Make any changes to the existing DTD that you desire before running the -dbschemagen command. Setup ddhome/conf/ddcfg_uds_custom.template file which is used by iwsyncdb.ipl -initial (or an explicit iwsyncdb.ipl -ddgen) command to produce the PressRelease_dd.cfg file.

Hope this helps.