Fatal Error: Field not found: keyChange
Posted: Wed Jul 16, 2008 12:37 pm
Hi
While using the Reference Match stage in my job , The job aborts throwing the error
"main_program: Fatal Error: Field not found: keyChange"
The prev message of this fatal one is
Reference_Match_12: Creating sub-operator: <QSmatStats -workDir ./RT_QS37/V0S12 -f Reference_Match_12.txt>
Creating sub-operator: <copy>
Creating sub-operator: <generator -par -schema "record(qsMatchDataID:uint64{cycle={init='part+1',incr=partcount}})">
Creating sub-operator: <copy>
Creating sub-operator: <copy>
Creating sub-operator: <generator -par -schema "record(qsMatchDataID:uint64{cycle={init='part+1',incr=partcount}})">
Creating sub-operator: <copy>
Creating sub-operator: <QSmat -n 1 -workDir ./RT_QS37/V0S12 -f Reference_Match_12.txt>
Creating sub-operator: <tsort -key qsMatchDataIDA -collation_sequence en -strength secondary>
Creating sub-operator: <QSmat_join -workDir ./RT_QS37/V0S12 -f Reference_Match_12.txt>
Creating sub-operator: <tsort -key qsMatchDataIDB -collation_sequence en -strength secondary>
Creating sub-operator: <QSmat_join -B -workDir ./RT_QS37/V0S12 -f Reference_Match_12.txt>
Creating sub-operator: <switch -ignoreRejects -key qsMatchType -case MP=0 -case CP=1 -case DA=2 -case DB=3>
I have already see a post on this :
viewtopic.php?t=114578&highlight=Fatal+ ... +keyChange
I have also given one blocking coloumn still the error is not solved.
can you please share the solutioin if any one has comeacross same problem?
Thanks,
Rajan
While using the Reference Match stage in my job , The job aborts throwing the error
"main_program: Fatal Error: Field not found: keyChange"
The prev message of this fatal one is
Reference_Match_12: Creating sub-operator: <QSmatStats -workDir ./RT_QS37/V0S12 -f Reference_Match_12.txt>
Creating sub-operator: <copy>
Creating sub-operator: <generator -par -schema "record(qsMatchDataID:uint64{cycle={init='part+1',incr=partcount}})">
Creating sub-operator: <copy>
Creating sub-operator: <copy>
Creating sub-operator: <generator -par -schema "record(qsMatchDataID:uint64{cycle={init='part+1',incr=partcount}})">
Creating sub-operator: <copy>
Creating sub-operator: <QSmat -n 1 -workDir ./RT_QS37/V0S12 -f Reference_Match_12.txt>
Creating sub-operator: <tsort -key qsMatchDataIDA -collation_sequence en -strength secondary>
Creating sub-operator: <QSmat_join -workDir ./RT_QS37/V0S12 -f Reference_Match_12.txt>
Creating sub-operator: <tsort -key qsMatchDataIDB -collation_sequence en -strength secondary>
Creating sub-operator: <QSmat_join -B -workDir ./RT_QS37/V0S12 -f Reference_Match_12.txt>
Creating sub-operator: <switch -ignoreRejects -key qsMatchType -case MP=0 -case CP=1 -case DA=2 -case DB=3>
I have already see a post on this :
viewtopic.php?t=114578&highlight=Fatal+ ... +keyChange
I have also given one blocking coloumn still the error is not solved.
can you please share the solutioin if any one has comeacross same problem?
Thanks,
Rajan