DSXchange

poorna_76 wrote:Please let me know any solid solution, yet.

There isn't one. It would need to be reproducible first.

Nicely said.

The only thing I'd add is on the subject of using shared containers to add Server functionality to PX jobs. Do this at the expense of speed in your job.

Is there any other way to use the find command, apart from the FTP process ? Of course. I'm curious why you feel the need to do this in an ftp session. Is this the only access you have to a remote system? Is it at least a UNIX system? Perhaps if you explained your need in greater detail people coul...

I wouldn't classify this as a 'problem', per se. If you open a Shared Container as if to work on it, it becomes locked just like a job would be. While it is open and locked, jobs that reference it cannot be compiled. The solution is to only 'access' the shared containers like it sounds you are doing...

While not having a clue about this particular message, I was curious about something. In this 'migration' from one storage disk to another, did anything about the end result change? Meaning, does your current configuration match your old configuration - mount points, pathnames where everything lives...

When i said 'technically', i meant that if the same file is used both as the source and the target, a job compilation wouldn't result in an error. In fact, I meant to say exactly what u said. 'In isolation'. No worries... and very true. Doing something like that won't cause a compilation error. Thi...

Sounds like a kernel parameter needs to be increased, that or do something to bring the number of simultaneous client connections down. Do a 'man sshd' - you should see something like this that I pulled off the net: sshd (SSH Daemon) is the daemon program for ssh(1). Together these programs replace ...

Agreed - what if both had been their 666th?

While agreeing with you that you can't LOAD them preserving order, you can of course always reorder them subsequently by dragging the column name up or down in the grid. As I noted earlier. I really don't see it as a big deal, either, but obviously Phil is of a different opinion. Different strokes...

Of course it can be done - a constraint expression can be any valid expression, and therefore can invoke routines. Ok... [sigh] I should have been more specific in my question. It's not the simple fact of calling a routine that I was questioning, it was the use of the routine to write to multiple s...

I don't want you to feel ignored Arnd, but I have no direct experience with either 10g or NLS. All I can tell you is that the plugin metadata definitions can just plain ol' be wrong at times via the OCI plugin and must be corrected by hand. Don't know if this is one of those times, however, or if yo...

Sainath.Srinivasan wrote:Write in 2 separate seq files and concat them at end.

Exactly. Or do that and then concatenate in the 'after job' area via ExecSH.

In other words, there is absolutely no problem with processing an 'empty' sequential file. The job will simply process zero records and then declare everything good, green and A-Ok.

You problem will come in if the file does not exist. That will cause the job to abort.

This seems to be a popular topic lately. For one example, please see this thread in the EE/PX forum. You cannot have two processes writing to the same sequential file at the same time. Period. If your create link is writing rows to the file, it must complete and close the file before it is safe for ...

The same file can in fact be the source and target, technically no matter at the reject link or output link. The file update mode should rather be append. But the whole affair depends on ur OS. Please be careful when giving advice like this. A sequential file is a sequential file and it can only be...