DSXchange

Good. So the system tables (UV_SCHEMA and UV.ACCOUNT) are intact with respect to this project. Have you been executing these commands from the Administrator client command window? If so, at least the Administrator client can connect to the project, which means that we have some progress on that scor...

I am not a premium user. Can you please share the solution with everyone including non premium user. No. 100% of revenue from premium memberships is devoted to meeting the hosting and bandwidth costs of DSXchange. The company behind it is no Microsoft. DSXchange does not make money. It is an all-vo...

How the hell are we expected to know that??? You have give no row counts, no row sizes, no indication of physical memory, no indication of the configuration, or - indeed - anything that could allow some kind of guesstimate to be made. Therefore my answer to you is: measure it We have no means to ass...

ray.wurlod wrote:Are there any other warnings near this one in the job log?

Was there anything unclear about that question?

You mention a hashed file. That means that this thread belongs in the server forum. Or are you using a server shared container in a parallel job?

Suggestion: use the file format in Case 1.

Suggestion: use the file format in Case 1.

Get into the Administrator client. Execute the following command, as shown. SELECT NAME FMT '35L', CATEGORY FMT '35L' FROM DS_JOBS WHERE JOBNO IN (SELECT OBJIDNO FROM DS_JOBOBJECTS WHERE EVAL "@RECORD" LIKE '%<<Routine Name>>%'); You can substitute your routine name for <<Routine N...

It may not be, as you say. For example if you are processing (sorting, maybe) 10GB of data, then 1GB of scratch space will possibly not be enough: definitely won't be enough if you only have 4GB of memory in the machine.

Aggregator is functionally equivalent to SQL - you do not need any grouping column. In this case you will get one row of output. HOWEVER -- in a parallel execution environment you will get one output row on each processing node, so you may need (depending on your exact requirements) to force the Agg...

Do you have a time dimension table you can use in a lookup?

When you run a job you can set a maximum number of warnings. The job will abort when this number of warnings is exceeded. A value of 0 means that the job can generate an unlimited number of warnings and still run to completion.

You may need to recompile the job sequence.

You may further need to check that the logic of the job sequence is intact, for example that every path through the job sequence can enter an activity and leave that activity.

No, that will be a run time error. "Link initialization" happens at run time.

Are there any other warnings near this one in the job log?