DSXchange

Perhaps a new first forum is required, in which posts are automatically deleted and the poster barred. Flamed would be nice, but this never gets back to the perpetrator.

Also not reported is the method you are using to convert the decimal numbers to strings. Are you using a Modify stage or a Transformer stage? Which function are you using? Are you qualifying that function (for example with "fix_zero" for DecimalToString() function)?

laxmi_etl wrote:Thanks for your concern.

I selected Index mode as maintanence and disable constraints true for the write mode append.

It solved my problem.

Thanks

What happened to "no luck"?

He means not to use this "innocuous job" as a prelude to every job - only do it once, at the beginning of a job sequence. Otherwise the volume of queries against the DUAL table will prove counter-productive.

We email Walter, but he is entitled to his weekends. The first to encounter the problem should email Walter and post that he/she has done so, so that Walter does not get deluged with emails. It might be worth seeking legal advice. I don't know what US law is; such activity is illegal here in Austral...

OK, do-able but not best practice.

Speed Data type conversion and "casting" functions Speed More null-handling functions Speed Mantissa functions Retrieval of environment variable value Did I mention speed? Performance of the Transformer stage in version 7.5.1A (?) was significantly enhanced. Switch and Filter stages are effectively ...

laxmi_etl wrote:No luck, Any other thoughts.

"No luck" may mean that you didn't even try it - even with my RMM stage operational I have no way of knowing that. Explain what you tried, what results obtained and whether these results were different from those obtained previously.

I'm not certain that's right, Arnd. The segment file names include the name of the descriptor file. The naming convention for segment files is descriptor.user.fastname.0000.0000.0000.c4.c4e17a7d.0000.2fdc262f where descriptor is the name of the descriptor file user is the name of the user who execut...

Or you can run an innocuous little job (such as SELECT * FROM DUAL;) that aborts if you can't connect to the database. You can detect this job's status in your job sequence in order to make the decision whether to proceed with the other jobs.

That looks like a corrupted DSX file. For whatever reason the import process is trying to read the line "=+=+=+=" as the name of a routine's executable code. You could search for this text in the DSX file, ascertain whether it immediately follows a BEGIN tag. Try doing a selective import, without im...

DSguruji ?

Search is your friend; others have encountered this in the past.

Please delete the duplicate of your post in the server forum - it does not belong there.

orchadmin is in the bin subdirectory of PXEngine, which is a sibling directory of DSEngine. Therefore, assuming DSHOME is set: APT_ORCHHOME=$DSHOME/../PXEngine ; export APT_ORCHHOME For the orchadmin command to work, you also need APT_CONFIG_FILE to be set, and set to the same configuration file as...

The descriptor files (which I called control files - the ones with names ending in ".ds") are wherever you located them. If you did not provide a pathname, but just a "xyz.ds" file name, in the Data Set stage that wrote the Data Set, then the descriptor file is in your project directory. Neither orc...