ERROR : expecting 0 segments, read 1 segments

clarcombe · Post by **clarcombe** » Wed Jan 10, 2007 7:40 am

I am getting the following error running a job from a job sequence.

ERROR

main_program: Dataset: /apps/ascential/data/DEV_QTE/ds/Ds_ORA_PS_PRDSVC2_HistoricProductStatus_Upsert.ds, expecting 0 segments, read 1 segments.

main_program: When deleting data set /apps/ascential/data/DEV_QTE/ds/Ds_ORA_PS_PRDSVC2_HistoricProductStatus_Upsert.ds, previous delete attempt not complete; removing /apps/ascential/data/DEV_QTE/ds/Ds_ORA_PS_PRDSVC2_HistoricProductStatus_Upsert.ds.being_deleted in order to proceed.

However, when I run the job by hand, the job runs without problem. I therefore assume that it is the Job Sequence that is causing the problem

PARAMETERS

I have compared both sets of parameters and they are the same

By Hand
$APT_DUMP_SCORE = Faux
GpPathDs = /apps/ascential/data/DEV_QTE/ds/
GpPathReject = /apps/ascential/data/DEV_QTE/reject/
GsSchemaCib = PRDSVC2
LsBase = ORA
LsApplication = PS
LsTable = HistoricProductStatus
LsReference1 = Product
LsReference2 = ProductStatus
LiFlowNumber = 10

By Job Sequence
Starting Job JsQTE_E20_Nv3_HistoricProductStatus_ORA.
$APT_CONFIG_FILE = /apps/ascential/Ascential/DataStage/Configurations/Qte_TwoNode.apt
$APT_DISABLE_COMBINATION = Faux
$APT_DUMP_SCORE = Faux
GpPathDs = /apps/ascential/data/DEV_QTE/ds/
GpPathReject = /apps/ascential/data/DEV_QTE/reject/
GsSchemaCib = PRDSVC2
LsBase = ORA
LsApplication = PS
LsTable = HistoricProductStatus
LsReference1 = Product
LsReference2 = ProductStatus
LiFlowNumber = 10
DSJobController = JsQTE_E20_Nv3__PreLoad

JOB
The job is consists of three dataset transformations. It is a replica of one of 20 jobs which run without problem in the same job sequence.

NODE
The job is configured to run on two nodes in both instances

CHECKS
I have checked to ensure that the dataset in question is not used twice within the Job Sequence

Any Suggestions ?

ray.wurlod · Post by **ray.wurlod** » Wed Jan 10, 2007 2:20 pm

Looks like there's a problem with partial deletion of the Data Set.

Try deleting it using the GUI or orchadmin command before running the job sequence that populates it.

Are you using the same configuration file when populating the Data Set as when reading from it?

clarcombe · Post by **clarcombe** » Thu Jan 11, 2007 1:48 am

Thanks for the reply.

I deleted it using Orchadmin and I even recreated the job sequence call to the routine. But this has had no positive effect

It is the same node configuration used for both

Regards

clarcombe · Post by **clarcombe** » Thu Jan 11, 2007 5:27 am

I discovered that the output that I thought was going to two separate files was in fact going to only one file, thus the segment error.

Changed the parameter in one of the DS outputs and it now works

ulab · Post by **ulab** » Tue Jan 24, 2017 6:13 am

which parameter you changed?

chulett · Post by **chulett** » Tue Jan 24, 2017 6:24 am

I would assume the parameterized name of the file.

ray.wurlod · Post by **ray.wurlod** » Thu Jan 26, 2017 2:53 am

ulab wrote:which parameter you changed?

Versions after 8.0 (the IBM versions) work somewhat differently - actually a lot differently - to the version 7 environment of the ten year old post to which you responded.

DSXchange