DataStage server migration

kumar_s · Post by **kumar_s** » Tue Mar 28, 2006 9:18 pm

The Configuration you mentioned is compatable for 7.5x.

benny.lbs · Post by **benny.lbs** » Tue Mar 28, 2006 10:17 pm

I know the APT_CONFIG_FILE format is compatible.

However, if the server name changed, we simply transfer the disks to new server, the Dataset can be read correctly ?

ArndW · Post by **ArndW** » Wed Mar 29, 2006 2:58 am

Yes, you can move without worries in this part of the transition. The dataset descriptors don't contain a a server name reference, just the schema information and the paths to the actual data files.

trobinson · Post by **trobinson** » Wed Mar 29, 2006 7:15 am

I'm confused by ArndW's reply. I see the config file in a dataset when I do a orchadmin ll. The fastname will be the old server. If the job that generates the dataset does NOT use "Use Existing (Discard schema and records)" when the job is run, then won't the existing dataset attempt to use the old environment's config file and not the new?

kumar_s · Post by **kumar_s** » Thu Mar 30, 2006 2:45 am

HI,

The config file information is from 'Orchadmin' command and not from dataset descriptor file.

trobinson · Post by **trobinson** » Thu Mar 30, 2006 9:11 am

Hey, I'm still confused. Maybe you can help me out. I see this doing a orchadmin ll:
"Embedded ORCHESTRATE system configuration:"

and then the config information.

so my questions would be these;

1. How does orchadmin know which configuration file applies to the dataset? We have several and I would consider that quite mis-leading if orchadmin showed me one when in fact the dataset was created with another.
2. Why does orchadmin say "embedded"?

Thanks for the help!

Is this a hijack of the thread? Maybe, but the answer will apply.

ray.wurlod · Post by **ray.wurlod** » Thu Mar 30, 2006 1:45 pm

The configuration file used/reported is whatever is currently pointed to by the APT_CONFIG_FILE environment variable.

trobinson · Post by **trobinson** » Fri Mar 31, 2006 7:13 am

Still confused. I was content with Ray's answer as that made sense and he is Ray after all. However, perusing the documentation for another problem I took a quick peek at Managing DataSets from the PX Developer's Guide pdf page 1046. It very clearly states that the configuration file in (sic) use when the DataSet was created is in the Descriptor file.

Having it there makes sense to me since the Config file in the current APT_CONFIG_FILE env variable could be radically different then the config file used when the dataset was created.

ArndW · Post by **ArndW** » Fri Mar 31, 2006 8:05 am

I took a look at the files and trobinson is correct, the config file that was used is embedded in the dataset along with the schema and file locations.
But looking at the orchadmin options it seems that the locations listed as the paths to the data files override any config file inherited attributes, so you will be able to utilize the dataset on the new node.

You could test this by changing the config settings in the dataset to some other path and see if the datasets is still displayable.

trobinson · Post by **trobinson** » Fri Mar 31, 2006 9:20 am

I will surmise that you go on to discuss the -x option of orchadmin. Doing orchadmin -help discusses which config file to use when using orchadmin; the one contained within the dataset descriptor file or the APT_CONFIG_FILE one.

Reading further it looks like whatever one does in DataStage; NEVER, ever ...

ray.wurlod · Post by **ray.wurlod** » Fri Mar 31, 2006 3:55 pm

Clearly an embedded configuration is necessary in a Data Set or a File Set. For example, if it was written under control of a four-node configuration file, then it can only be read from those four nodes, irrespective of the "current" configuration file. This can imply a need to re-partition in a running job.

My statement was about configuration file - I should have been more explicit.

trobinson · Post by **trobinson** » Fri Mar 31, 2006 4:51 pm

Yes, clearly... now. Remember the single most important success factor in any DataStage implementation is ...

... the use of the ellipse.