DSXchange

hi
this is the fatal error i got
"Parallel job reports failure (code 134)"

any help would be greatly appreciated

This is the error code given out from server. But you should be getting some other warning or error which is the actual reason.

Reset the job in Director. Additional diagnostic information may be logged "from previous run". Ask your support provider what "code 134" means.

Hi,

Code 132 means that the dataset is not available.

Code 1 means the File path is incorrect.

Code 134??

Are you using $APT_CONFILE_FILE. The Datatype should be FilePath and it should point to the right Configuration file.

But Iam not sure whether I got Code 138 or Code 134.

Kumar,

You dont get any warnings or other error messages in these case where there in only one error message which states Parallel Job reports failure along with this Code.

Ray,

Whatever you have mentioned is that applicable to Parallel jobs. I have seen them in Server jobs though.

HTH
--Rich

I have just run into this error as well. The job is a simple job that extracts from a SQL Server view and loads to Oracle.


main_program: Requesting delayed metadata.
APT_ParseError: Parsing parameters "max=0" for schema type "ustring": Max length must be positive, got: "0"
Could not find type: ustring[max=0]

Contents of phantom output file =>
RT_SC16/OshExecuter.sh: line 20: 25457 Aborted (core dumped) $APT_ORCHHOME/bin/osh "$@" -f $oshscript >$oshpipe 2>&1

Parallel job reports failure (code 134)

From another thread, I took Ray's suggestion to take a look at the script.

1 #!/bin/sh
2 # Shell script for Datastage to execute an Orchestrate osh script, generated at 2006-10-10 15:32:29
3 #
4 # Parameters:
5 # $1 - osh script to run (file path)
6 # $2 - fifo name to write osh diagnostic output
7 # $3 onwards - osh options (may be absent)
8 oshscript=$1
9 oshpipe=$2
10 shift
11 shift
12 if test ! -x "$APT_ORCHHOME/bin/osh"
13 then echo '##OSHRETVAL NOOSH' > $oshpipe
14 exit 1
15 fi
16 $APT_ORCHHOME/bin/osh "$@" -f $oshscript > $oshpipe 2>&1 &
17 oshpid=$!
18 # Write the pid of the conductor process to the fifo
19 echo '##OSHPID' $oshpid > $oshpipe
20 wait $oshpid
21 # Write the terminating string to the fifo
22 echo '##OSHRETVAL' $? > $oshpipe
23 # end of script

At line 20, it looks like it's just waiting for the PID to return its termination status, which I assume returned "25457 Aborted". Is there a way to find out what the error really was? Does it have anything to do with the "Max length must be positive" message?

I got this error when i explicity gave column length less than the actuall database column length.

so had to change that inside the job, if i have to avoid this error.

Thanks