We have a scheduled job with 3 steps. The first two steps are the same customized session and create sequential files. The third step executes a shell command to concatenate the two sequential files.

Recently the job does not complete. The job history shows error 127 in running the shell script ./home/job100/make1dnb. This file contains the unix command to concatenate the two files creating a new file.

What is an error 127? :confused:

Error 127 = ENOPRIM = No primary key
Cheers,
Popeye!

Madhu,

I found this am confused...


oerr ora 127
00127, 00000, "dispatcher %s does not exist"
// *Cause: There is currently no dispatcher running with the specified
// name.
// *Action: Retry with a name of the form "D###" denoting an existing
// dispatcher process.


I guess you might have to check up with your Oracle DBA's.

Thanks, but this error is not an Oracle error.

It seems the error may be showing up because the job is stopped due to its failure to complete. The concatenated datafile is present and complete but the scheduled job never terminates.

I think this is a system (UX) error. What's exactly in the file? Could be that one of the files to be concatened is missing or the exec() system call is failing for some reason.

The file contains '*' delimited data from the sales order, accounts receivable and customer master tables. The last entries in the concatenated file are the last entries from the sequential file created from the second step, as they should be.

The records are:
608003*Everlight Chemical Industrial Corp.*6th Floor, Chung Ting Building*No. 77
, Sec. 2 **Taipei ** *600011*125*CIF*
*886-2-2706-6006* *600004*0*0*0*0*0*44*1*5303.03705*07112
002*7125*608003
999999*One Time Customer * *
** ** *0*004* *
* * *0*0*0*0*0*36.75*41*1*0*09082000*0*999999

I just found an overflow error in $BSE/log. Maybe that's my problem!