Hi, I am getting the similar error while testing the match passes:
Please help me on this issue.
Thanks
Jana
##I IIS-DSEE-TUTL-00031 09:38:41(001) <main_program> The open files limit is 2000; raising to 2147483647.
##I IIS-DSEE-TOSH-00002 09:38:41(002) <main_program> orchgeneral: loaded
##I IIS-DSEE-TOSH-00002 09:38:41(003) <main_program> orchsort: loaded
##I IIS-DSEE-TOSH-00002 09:38:42(000) <main_program> orchstats: loaded
##I IIS-DSEE-TDOD-00080 09:38:42(006) <MWI_Odbc_Write> Process meta data not available in database
##I IIS-DSEE-TFSC-00001 09:38:42(008) <main_program> APT configuration file: /opt/IBM/InformationServer/Server/Configurations/default.apt
##E IIS-QSEE-MATM-00004 09:38:43(000) <QS_Test_MWI_0,0> Variable [_qsC_StateAbbreviation_USAREA] not found in [A] frequency file
##E IIS-QSEE-POTO-00002 09:38:43(001) <QS_Test_MWI_0,0> Fatal error from object qsmExit, code 4
##E IIS-DSEE-TFOR-00089 09:38:43(003) <QS_Test_MWI_0,0> The runLocally() of the operator failed.
##I IIS-DSEE-TFOR-00094 09:38:43(004) <QS_Test_MWI_0,0> Output 0 produced 201 records.
##E IIS-DSEE-TFPM-00040 09:38:43(005) <QS_Test_MWI_0,0> Operator terminated abnormally: runLocally did not return APT_StatusOk
##E IIS-DSEE-TFSC-00011 09:38:49(000) <main_program> Step execution finished with status = FAILED.
##I IIS-DSEE-TCOS-00026 09:38:49(001) <main_program> Startup time, 0:06; production run time, 0:01.
QualityStage Match Process Error
Re: QulityStage Match Process Error
Hi do you guys have any Idea why I am getting the above error.
Basically I have one source standardised dataset, one source frequency dataset, one Verispan standardised Dataset and Verispan Freq ds for referencr match process.
I am getting the below two errors while testing match passes:
1. ##I IIS-DSEE-TDOD-00080 09:38:42(006) <MWI_Odbc_Write> Process meta data not available in database
2. ##E IIS-QSEE-MATM-00004 09:38:43(000) <QS_Test_MWI_0,0> Variable [_qsC_StateAbbreviation_USAREA] not found in [A] frequency file
I really appriciate if you have any thoughts on how to resolve these issues.
Thanks
Jan
Basically I have one source standardised dataset, one source frequency dataset, one Verispan standardised Dataset and Verispan Freq ds for referencr match process.
I am getting the below two errors while testing match passes:
1. ##I IIS-DSEE-TDOD-00080 09:38:42(006) <MWI_Odbc_Write> Process meta data not available in database
2. ##E IIS-QSEE-MATM-00004 09:38:43(000) <QS_Test_MWI_0,0> Variable [_qsC_StateAbbreviation_USAREA] not found in [A] frequency file
I really appriciate if you have any thoughts on how to resolve these issues.
Thanks
Jan
janreddy wrote:Hi, I am getting the similar error while testing the match passes:
Please help me on this issue.
Thanks
Jana
##I IIS-DSEE-TUTL-00031 09:38:41(001) <main_program> The open files limit is 2000; raising to 2147483647.
##I IIS-DSEE-TOSH-00002 09:38:41(002) <main_program> orchgeneral: loaded
##I IIS-DSEE-TOSH-00002 09:38:41(003) <main_program> orchsort: loaded
##I IIS-DSEE-TOSH-00002 09:38:42(000) <main_program> orchstats: loaded
##I IIS-DSEE-TDOD-00080 09:38:42(006) <MWI_Odbc_Write> Process meta data not available in database
##I IIS-DSEE-TFSC-00001 09:38:42(008) <main_program> APT configuration file: /opt/IBM/InformationServer/Server/Configurations/default.apt
##E IIS-QSEE-MATM-00004 09:38:43(000) <QS_Test_MWI_0,0> Variable [_qsC_StateAbbreviation_USAREA] not found in [A] frequency file
##E IIS-QSEE-POTO-00002 09:38:43(001) <QS_Test_MWI_0,0> Fatal error from object qsmExit, code 4
##E IIS-DSEE-TFOR-00089 09:38:43(003) <QS_Test_MWI_0,0> The runLocally() of the operator failed.
##I IIS-DSEE-TFOR-00094 09:38:43(004) <QS_Test_MWI_0,0> Output 0 produced 201 records.
##E IIS-DSEE-TFPM-00040 09:38:43(005) <QS_Test_MWI_0,0> Operator terminated abnormally: runLocally did not return APT_StatusOk
##E IIS-DSEE-TFSC-00011 09:38:49(000) <main_program> Step execution finished with status = FAILED.
##I IIS-DSEE-TCOS-00026 09:38:49(001) <main_program> Startup time, 0:06; production run time, 0:01.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
As noted in your other thread, _qsC_StateAbbreviation_USAREA should have been included in the output of the standardization job. I trust that you did perform standardization using the same rule set that you are trying to use for Match?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Premium Member
- Posts: 425
- Joined: Sat Nov 19, 2005 9:26 am
- Location: New York City
- Contact:
janreddy,
Check cases in StateAbbreviation_USAREA field. Compare the metadata in the standardization job that populate the sample frequency data set and the one used in your match command. The Match Reference is case sensitive
Also check that the path to the Frequency Data Set in your Test Environment is pointing to same data set created with your standardization job
..... Did you updated your Test Environment database?
Check cases in StateAbbreviation_USAREA field. Compare the metadata in the standardization job that populate the sample frequency data set and the one used in your match command. The Match Reference is case sensitive
Also check that the path to the Frequency Data Set in your Test Environment is pointing to same data set created with your standardization job
..... Did you updated your Test Environment database?
Julio Rodriguez
ETL Developer by choice
"Sure we have lots of reasons for being rude - But no excuses
ETL Developer by choice
"Sure we have lots of reasons for being rude - But no excuses
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Hi Ray,
I performed below two steps to resolve this issue:
a. Standardize Job for Source DataSet and Reference Dataset: In match frequency stage included all fields.
b. In he Match Designer: Specify that there are not frequency data available for the field using Variable Special Handling with NOFREQ while designing your match specifications.
Thanks
Jan
I performed below two steps to resolve this issue:
a. Standardize Job for Source DataSet and Reference Dataset: In match frequency stage included all fields.
b. In he Match Designer: Specify that there are not frequency data available for the field using Variable Special Handling with NOFREQ while designing your match specifications.
Thanks
Jan
ray.wurlod wrote:Please advise HOW this issue was resolved.