DSXchange

Push back against illogical decrees. Always. Otherwise you're asking for grief. Explain the downside(s), and get them to put their signature on a document you've prepared containing these explanations and the assertion that they want things done their way irrespective. At least then you can shift th...

Dev doesn't process the volumes. How long since you cleaned up in the production project? How long since its indexes were rebuilt? How many of its logs have thousands of entries? All these things (and more) can slow things down.

There is no repeating group (no OCCURS) in this data. By creating multiple outputs and running these into a Link Collector you are producing exactly the input file. Please create a written (that is, English) specification of the true structure of the input file, and the desired output file structure.

Only a year has gone by between posts. Maybe, wasimraja, you need to follow this up with your own support provider?

Write the data to a sequential file. If the spaces exist there, then the problem is an Oracle one. If they do not, then the problem is within your DataStage job design. We need to know which it is before suggesting any remedy.

An entry is placed in DS_LICENSE for each connected client. This provides a mechanism where the administrator tools can quickly check whether there are any clients connected to a project for which the tool requires exclusive access. Yes this hashed file is also used to monitor usage of client licenc...

Parallel jobs also must be precise about the format of date, times and timestamps. The default format is set up in the Administrator client (project properties). If you deviate from these (for example in functions or in job parameter values) then you must handle the deviation by specifying what the ...

Yes, I believe so.

You can't have naming consistency - that would remove the mystique!

And what did you find when you performed a Search for SIGSEGV ?

In short, don't resolve it - prevent it. Disable ODBC tracing. Or change the permissions to the trace file's parent directory and/or the trace file itself so that you can.

You NEVER kill DataStage processes. It may be that there are none, and the status was never updated. Search the forum for "Clear status file". You can also use the DS.TOOLS menu to determine whether there are, in fact, any processes associated with the job. This menu also includes options for loggin...

If it works in Dev there can be nothing wrong in the transformation logic. You must track down what's different between the two environments. This may be completely external to DataStage - your search must range far and wide, and include such things as command and shared library search lists (PATH a...

DataStage was never intended to be a reporting tool. Why are you trying to use the wrong tool?

A Hashed File is only available in server jobs. It uses a hashing algorithm (without building an index) to determine the location of keys within its structure. It is not amenable to parallelism. The contents of a hashed file may be cached in memory when using the Hashed File stage to service a refer...

Of course. There's always a way. Start by asking the client where they believe the code to be. DataStage, as they can see, is a graphical tool. You can certainly perform a walkthrough. Start at the top level job sequence. As you reach each activity, at least for the important ones, right click and c...