DSXchange

As mentioned, it is an Environmental variable used to define those values. And it might be used in IPC stage properties to define the Buffersize and Timeouts. If you want the details of Buffer Size and Timeouts, I can help you in pasting the help text. Buffer Size Defaults to 128 Kb. The IPC stage u...

If you target field is of decimal its not possible to get the preceeding 0s. Atleast in server edition. Char/Varchar type can be used for this.

Humm... if its the data of 2000s, shouldnt it be one time load (Initial load)?
Shouldnt you be loadining it all in a stretch or in a batch, where as the current daily data may be scheduled to be extracted based on the condition SYSDATE-1...
May be I got your requirement wrong.

No Transformation. He/She might be using it to assign the values of Buffersize and Timeouts in IPC stage.

So that was an ultimate answer to the amateur question.

Check if the same appears in other projects?

Hi Ramesh, Welcome to DsXchange :D !!! The function of the Switch stage is to split the rows based on the given condition. You can also achieve this using Transformer stage. But ultimately to create the the different table that you have mentioned, you may use the Database stage with the respective o...

Try declaring the Env variable as a Job Parameter and use that parameter in your. Similarly, try assinging a stage variable and initialize the Env variable in it and use the stage variable.

Rather than aborting the job (Which may not look tidy), Select the table name from TAB or ALL_TABLES and based on the result, set UserStatus. Based on the user status, trigger the rest of the jobs. Or as narasimha mentioned, split into two streams for each function.

42% With any specific formula you arrived this number

Ray's job is PX. How about yours?
If your also on PX, you have a work around. Promote that warning to Info using Message handler. If server, better approach Support.

Hi Parvathi, Why cant you use the OCI stage and output to a sequential stage for this. Which is for the same reason. If you the SQL that you use is not compatable in OCI stage, you can alternatively use Shell script directly to call the .sql through ExecuteCommand Activity or in any Before/After sub...

Version control is again a part of Import/Export but done by the tool itself.

Dont you get any error or warning message? What happens if you have design to extract body and pass the file with header and body?

If you use the metadata for the body and if you try to extract the header and body, dont you get the header getting rejected?
Sorry I dont have access to Datastage at the moment. Is your header and body are of same fixed length?