IC5Notice: We have upgraded developerWorks Community to the latest version of IBM Connections. For more information, read our upgrade FAQ.
Topic
  • 14 replies
  • Latest Post - ‏2010-03-12T19:02:34Z by OldJack
SystemAdmin
SystemAdmin
533 Posts

Pinned topic Match Designer Match Pass run failed

‏2007-10-08T13:26:50Z |
DataStage Release : 8
Operating System : Windows 2003 Server

I try to redo the Quality Stage 8.0 Essentials course. No problems until I want to test the passes within the Match Designer.

The error 'Match Designer Match Pass run failed' pops up. The Show Error(s) (OSHErrors.txt) and Show Full Log (OSHErrorLog.txt) are both empty.

Setting up the Test Environment using the QS-database reports no errors.

Does anyone have an idea ?
Updated on 2010-03-12T19:02:34Z at 2010-03-12T19:02:34Z by OldJack
  • SystemAdmin
    SystemAdmin
    533 Posts

    Re: Match Designer Match Pass run failed

    ‏2007-11-08T03:07:52Z  
    Install Fixpack 1 and the empty error will be resolved.

    Have you setup an ODBC connection on your server that matches the one used on the client for the Match Designer DB?

    Stewart
  • SystemAdmin
    SystemAdmin
    533 Posts

    Re: Match Designer Match Pass run failed

    ‏2008-01-07T11:42:37Z  
    Install Fixpack 1 and the empty error will be resolved.

    Have you setup an ODBC connection on your server that matches the one used on the client for the Match Designer DB?

    Stewart
    Hi stewart,

    i got same OSHerrorlog with empty .i install the fixpack one. but still i have osherrorlog . now i got error messages. i pasted that below .could you please help me to solve this one.

    am using - db2 wire protocol

    ##I IIS-DSEE-TFCN-00001 22:25:34(000) <main_program>

    IBM WebSphere DataStage Enterprise Edition 8.0.1.4665

    Copyright (c) 2001, 2005-2007 IBM Corporation. All rights reserved

    ##I IIS-DSEE-TOSH-00002 22:25:34(001) <main_program> orchgeneral: loaded

    ##I IIS-DSEE-TOSH-00002 22:25:34(002) <main_program> orchsort: loaded

    ##I IIS-DSEE-TOSH-00002 22:25:34(003) <main_program> orchstats: loaded

    ##I IIS-QSEE-POP*-00001 22:25:35(001) <matchspec> Creating sub-operator: <QSmatStats -workDir C:/IBM/InformationServer/Server/Projects/sample/QSScratch/matchspec -f matchspec.MAT -trace all -lvl 1>

    ##I IIS-QSEE-POP*-00001 22:25:35(002) <matchspec> Creating sub-operator: <copy>

    ##I IIS-QSEE-POP*-00001 22:25:35(003) <matchspec> Creating sub-operator: <copy>

    ##I IIS-QSEE-POP*-00001 22:25:35(004) <matchspec> Creating sub-operator: <QSmat -n 1 -workDir C:/IBM/InformationServer/Server/Projects/sample/QSScratch/matchspec -f matchspec.MAT -trace all -lvl 1>

    ##I IIS-QSEE-POP*-00001 22:25:35(005) <matchspec> Creating sub-operator: <tsort -flagKey -stable -key MatchPrimaryWord1NYSIIS_USNAME -ci -collation_sequence en -strength secondary>

    ##I IIS-QSEE-POP*-00001 22:25:35(006) <matchspec> Creating sub-operator: <tsort -key qsMatchDataIDA -key qsMatchPassNumber -collation_sequence en -strength secondary>

    ##I IIS-QSEE-POP*-00001 22:25:35(007) <matchspec> Creating sub-operator: <copy>

    ##I IIS-QSEE-POP*-00001 22:25:35(008) <matchspec> Creating sub-operator: <innerjoin -key qsMatchDataID>

    ##I IIS-QSEE-POP*-00001 22:25:35(009) <matchspec> Creating sub-operator: <tsort -key qsMatchDataID -collation_sequence en -strength secondary>

    ##I IIS-QSEE-POP*-00001 22:25:35(010) <matchspec> Creating sub-operator: <QSmat_join -U -workDir C:/IBM/InformationServer/Server/Projects/sample/QSScratch/matchspec -f matchspec.MAT -trace all -lvl 1>

    ##I IIS-QSEE-POP*-00001 22:25:35(011) <matchspec> Creating sub-operator: <copy>

    ##I IIS-DSEE-TDOD-00080 22:25:35(013) <ODBC_Enterprise_0> Process meta data not available in database

    ##W IIS-DSEE-TDOD-00007 22:25:35(014) <main_program> DataDirectODBC DB2 Wire Protocol driverUDB DB2 for Windows, UNIX, and LinuxDB2ADMIN.PASS_1_RESULTS_DATA IS AN UNDEFINED NAME.

    ##I IIS-DSEE-TDOD-00081 22:25:35(015) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(016) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(017) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(018) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(019) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(020) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(021) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(022) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(023) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(024) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(025) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(026) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(027) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(028) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(029) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(030) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(031) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(032) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(033) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(034) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(035) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(036) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(037) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(038) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(039) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(040) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(041) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(042) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(043) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(044) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##E IIS-DSEE-TDOD-00083 22:25:35(045) <main_program> ?? (PASS_1_RESULTS_DATA)

    ##E IIS-DSEE-TDOD-00062 22:25:35(047) <ODBC_Enterprise_0> Table create failed: {0}

    ##I IIS-DSEE-TDOD-00080 22:25:35(048) <ODBC_Enterprise_1> Process meta data not available in database

    ##E IIS-DSEE-TFSR-00019 22:25:36(000) <main_program> Could not check all operators because of previous error(s)

    ##W IIS-DSEE-TFOR-00073 22:25:36(001) <APT_CopyOperator(1) in matchspec> When checking operator: A sequential operator cannot preserve the partitioning

    of the parallel data set on input port 0.

    ##W IIS-DSEE-TFIP-00095 22:25:36(002) <APT_CopyOperator(3) in matchspec> When checking operator: The modify operator drops field "qsMatchMasterFlag" which is not present in output interface.

    ##W IIS-DSEE-TFIP-00072 22:25:36(003) <APT_CopyOperator(3) in matchspec> When checking operator: When binding output schema variable "outRec": When binding output interface field "qsMatchSetID" to field "qsMatchSetID": Implicit conversion from source type "uint64" to result type "int64": Possible range limitation.

    ##W IIS-DSEE-TFIP-00072 22:25:36(004) <APT_CopyOperator(3) in matchspec> When checking operator: When binding output schema variable "outRec": When binding output interface field "qsMatchDataID" to field "qsMatchDataID": Implicit conversion from source type "uint64" to result type "int64": Possible range limitation.

    ##W IIS-DSEE-TFIP-00072 22:25:36(005) <QSM_MatStatsOp in matchspec> When checking operator: When binding output interface field "qsMatchStatValue" to field "qsMatchStatValue": Implicit conversion from source type "uint64" to result type "int64": Possible range limitation.

    ##E IIS-DSEE-TCOS-00029 22:25:36(006) <main_program> Creation of a step finished with status = FAILED.

    Many thanks in advance

    Message was edited by: qualitystage
    Updated on 2008-01-07T11:42:37Z at 2008-01-07T11:42:37Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    533 Posts

    Re: Match Designer Match Pass run failed

    ‏2008-01-09T02:09:26Z  
    Hi stewart,

    i got same OSHerrorlog with empty .i install the fixpack one. but still i have osherrorlog . now i got error messages. i pasted that below .could you please help me to solve this one.

    am using - db2 wire protocol

    ##I IIS-DSEE-TFCN-00001 22:25:34(000) <main_program>

    IBM WebSphere DataStage Enterprise Edition 8.0.1.4665

    Copyright (c) 2001, 2005-2007 IBM Corporation. All rights reserved

    ##I IIS-DSEE-TOSH-00002 22:25:34(001) <main_program> orchgeneral: loaded

    ##I IIS-DSEE-TOSH-00002 22:25:34(002) <main_program> orchsort: loaded

    ##I IIS-DSEE-TOSH-00002 22:25:34(003) <main_program> orchstats: loaded

    ##I IIS-QSEE-POP*-00001 22:25:35(001) <matchspec> Creating sub-operator: <QSmatStats -workDir C:/IBM/InformationServer/Server/Projects/sample/QSScratch/matchspec -f matchspec.MAT -trace all -lvl 1>

    ##I IIS-QSEE-POP*-00001 22:25:35(002) <matchspec> Creating sub-operator: <copy>

    ##I IIS-QSEE-POP*-00001 22:25:35(003) <matchspec> Creating sub-operator: <copy>

    ##I IIS-QSEE-POP*-00001 22:25:35(004) <matchspec> Creating sub-operator: <QSmat -n 1 -workDir C:/IBM/InformationServer/Server/Projects/sample/QSScratch/matchspec -f matchspec.MAT -trace all -lvl 1>

    ##I IIS-QSEE-POP*-00001 22:25:35(005) <matchspec> Creating sub-operator: <tsort -flagKey -stable -key MatchPrimaryWord1NYSIIS_USNAME -ci -collation_sequence en -strength secondary>

    ##I IIS-QSEE-POP*-00001 22:25:35(006) <matchspec> Creating sub-operator: <tsort -key qsMatchDataIDA -key qsMatchPassNumber -collation_sequence en -strength secondary>

    ##I IIS-QSEE-POP*-00001 22:25:35(007) <matchspec> Creating sub-operator: <copy>

    ##I IIS-QSEE-POP*-00001 22:25:35(008) <matchspec> Creating sub-operator: <innerjoin -key qsMatchDataID>

    ##I IIS-QSEE-POP*-00001 22:25:35(009) <matchspec> Creating sub-operator: <tsort -key qsMatchDataID -collation_sequence en -strength secondary>

    ##I IIS-QSEE-POP*-00001 22:25:35(010) <matchspec> Creating sub-operator: <QSmat_join -U -workDir C:/IBM/InformationServer/Server/Projects/sample/QSScratch/matchspec -f matchspec.MAT -trace all -lvl 1>

    ##I IIS-QSEE-POP*-00001 22:25:35(011) <matchspec> Creating sub-operator: <copy>

    ##I IIS-DSEE-TDOD-00080 22:25:35(013) <ODBC_Enterprise_0> Process meta data not available in database

    ##W IIS-DSEE-TDOD-00007 22:25:35(014) <main_program> DataDirectODBC DB2 Wire Protocol driverUDB DB2 for Windows, UNIX, and LinuxDB2ADMIN.PASS_1_RESULTS_DATA IS AN UNDEFINED NAME.

    ##I IIS-DSEE-TDOD-00081 22:25:35(015) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(016) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(017) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(018) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(019) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(020) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(021) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(022) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(023) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(024) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(025) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(026) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(027) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(028) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(029) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(030) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(031) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(032) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(033) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(034) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(035) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(036) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(037) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(038) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(039) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(040) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(041) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(042) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(043) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##I IIS-DSEE-TDOD-00081 22:25:35(044) <main_program> Driver doesn't support the datatype. DataType Code = -9

    ##E IIS-DSEE-TDOD-00083 22:25:35(045) <main_program> ?? (PASS_1_RESULTS_DATA)

    ##E IIS-DSEE-TDOD-00062 22:25:35(047) <ODBC_Enterprise_0> Table create failed: {0}

    ##I IIS-DSEE-TDOD-00080 22:25:35(048) <ODBC_Enterprise_1> Process meta data not available in database

    ##E IIS-DSEE-TFSR-00019 22:25:36(000) <main_program> Could not check all operators because of previous error(s)

    ##W IIS-DSEE-TFOR-00073 22:25:36(001) <APT_CopyOperator(1) in matchspec> When checking operator: A sequential operator cannot preserve the partitioning

    of the parallel data set on input port 0.

    ##W IIS-DSEE-TFIP-00095 22:25:36(002) <APT_CopyOperator(3) in matchspec> When checking operator: The modify operator drops field "qsMatchMasterFlag" which is not present in output interface.

    ##W IIS-DSEE-TFIP-00072 22:25:36(003) <APT_CopyOperator(3) in matchspec> When checking operator: When binding output schema variable "outRec": When binding output interface field "qsMatchSetID" to field "qsMatchSetID": Implicit conversion from source type "uint64" to result type "int64": Possible range limitation.

    ##W IIS-DSEE-TFIP-00072 22:25:36(004) <APT_CopyOperator(3) in matchspec> When checking operator: When binding output schema variable "outRec": When binding output interface field "qsMatchDataID" to field "qsMatchDataID": Implicit conversion from source type "uint64" to result type "int64": Possible range limitation.

    ##W IIS-DSEE-TFIP-00072 22:25:36(005) <QSM_MatStatsOp in matchspec> When checking operator: When binding output interface field "qsMatchStatValue" to field "qsMatchStatValue": Implicit conversion from source type "uint64" to result type "int64": Possible range limitation.

    ##E IIS-DSEE-TCOS-00029 22:25:36(006) <main_program> Creation of a step finished with status = FAILED.

    Many thanks in advance

    Message was edited by: qualitystage
    Its a little tough to determine the issue from the error. But it would seem the issue is that the 'odbcwrite' operator is unable to create a Match Designer results table because it can't reconcile that table's intended schema with the datatypes supported by the target database. There are a couple of possibilities that I'd investigate in this order.


    Most Likely - This is an NLS installation (so the odbcwrite operator creates a 'vargraphic' datatype), but the 'Codeset' of the target DB2 database is '1208' (which doesn't recognize 'vargraphic' input). In that case, the Codeset should be 'UTF-8' - You can confirm this as follows: DB2 Control Center -> All Databases -> <your database name> (right-click) -> Configure Parameters -> CODESET = UTF-8 ? If it isn't 'UTF-8', then the target DB will have to be recreated as the Codeset for an existing DB can't be changed. And while you're at it, you should probably create the new DB with a 'Default Page Size' parameter of '32K'. This is only a requirement if you're processing data records "wider" than 8,000 bytes, but it's a good practice.


    Less Likely - QualityStage will always present the same collection of 'generic' datatypes, some of which may not align with the 'odbcwrite' target database. And since the operator doesn't always perform DB-specfic substitutions, it's the burden of the user to make sure the column definitions used in their Match Designer input dataset are valid for the target DBMS.

    If you are unable to resolve this issue, please contact IBM Support.

    Stewart

    Message was edited by: StewartH

    Message was edited by: StewartH



    Updated on 2008-01-09T02:09:26Z at 2008-01-09T02:09:26Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    533 Posts

    Re: Match Designer Match Pass run failed

    ‏2008-01-10T07:19:19Z  
    Its a little tough to determine the issue from the error. But it would seem the issue is that the 'odbcwrite' operator is unable to create a Match Designer results table because it can't reconcile that table's intended schema with the datatypes supported by the target database. There are a couple of possibilities that I'd investigate in this order.


    Most Likely - This is an NLS installation (so the odbcwrite operator creates a 'vargraphic' datatype), but the 'Codeset' of the target DB2 database is '1208' (which doesn't recognize 'vargraphic' input). In that case, the Codeset should be 'UTF-8' - You can confirm this as follows: DB2 Control Center -> All Databases -> <your database name> (right-click) -> Configure Parameters -> CODESET = UTF-8 ? If it isn't 'UTF-8', then the target DB will have to be recreated as the Codeset for an existing DB can't be changed. And while you're at it, you should probably create the new DB with a 'Default Page Size' parameter of '32K'. This is only a requirement if you're processing data records "wider" than 8,000 bytes, but it's a good practice.


    Less Likely - QualityStage will always present the same collection of 'generic' datatypes, some of which may not align with the 'odbcwrite' target database. And since the operator doesn't always perform DB-specfic substitutions, it's the burden of the user to make sure the column definitions used in their Match Designer input dataset are valid for the target DBMS.

    If you are unable to resolve this issue, please contact IBM Support.

    Stewart

    Message was edited by: StewartH

    Message was edited by: StewartH



    Many thanks Stewart . i solved that problem by installing again without NLS. now i can run matching successfully.

    Stewart can i have ur mail Id? i have more doubts in quality stage tool

    Regards
  • Ray.Wurlod
    Ray.Wurlod
    18 Posts

    Re: Match Designer Match Pass run failed

    ‏2008-01-10T17:15:26Z  
    Many thanks Stewart . i solved that problem by installing again without NLS. now i can run matching successfully.

    Stewart can i have ur mail Id? i have more doubts in quality stage tool

    Regards
    Keep posting them here so we can all be aware of them (and their resolutions when found).
  • SystemAdmin
    SystemAdmin
    533 Posts

    Re: Match Designer Match Pass run failed

    ‏2008-01-11T11:57:21Z  
    Keep posting them here so we can all be aware of them (and their resolutions when found).
    in matching , i have pass to match 3 fields. name and reg number and another reg number. but out of 100% records more than 34% of records are null in 3rd field. can we do any overrides to make a match if the 3rd field have null.
  • SystemAdmin
    SystemAdmin
    533 Posts

    Re: Match Designer Match Pass run failed

    ‏2008-01-11T17:07:32Z  
    Its a little tough to determine the issue from the error. But it would seem the issue is that the 'odbcwrite' operator is unable to create a Match Designer results table because it can't reconcile that table's intended schema with the datatypes supported by the target database. There are a couple of possibilities that I'd investigate in this order.


    Most Likely - This is an NLS installation (so the odbcwrite operator creates a 'vargraphic' datatype), but the 'Codeset' of the target DB2 database is '1208' (which doesn't recognize 'vargraphic' input). In that case, the Codeset should be 'UTF-8' - You can confirm this as follows: DB2 Control Center -> All Databases -> <your database name> (right-click) -> Configure Parameters -> CODESET = UTF-8 ? If it isn't 'UTF-8', then the target DB will have to be recreated as the Codeset for an existing DB can't be changed. And while you're at it, you should probably create the new DB with a 'Default Page Size' parameter of '32K'. This is only a requirement if you're processing data records "wider" than 8,000 bytes, but it's a good practice.


    Less Likely - QualityStage will always present the same collection of 'generic' datatypes, some of which may not align with the 'odbcwrite' target database. And since the operator doesn't always perform DB-specfic substitutions, it's the burden of the user to make sure the column definitions used in their Match Designer input dataset are valid for the target DBMS.

    If you are unable to resolve this issue, please contact IBM Support.

    Stewart

    Message was edited by: StewartH

    Message was edited by: StewartH



    Hi Stewart,

    I've got exactly the same problem as qualitystage reported on the 7th of January on our IIS 8.0.1 installation. I'm using an Oracle 10g database as ODBC-datasource. The database uses UTF8 as its NLS_NCHAR_CHARACTERSET, but not as its NLS_CHARACTERSET:

    NLS_CHARACTERSET WE8MSWIN1252
    NLS_NCHAR_CHARACTERSET UTF8

    I really did hope this might work, since we haven't currently got a database with different settings.

    I am afraid I haven't got the option to just reinstall IIS on our AIX machine, so I'll have to find a solution to this on the database side.

    Have you got any suggestions?

    regards
    Roland

    Message was edited by: rmelzer
    Updated on 2008-01-11T17:07:32Z at 2008-01-11T17:07:32Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    533 Posts

    Re: Match Designer Match Pass run failed

    ‏2008-01-11T22:58:49Z  
    Many thanks Stewart . i solved that problem by installing again without NLS. now i can run matching successfully.

    Stewart can i have ur mail Id? i have more doubts in quality stage tool

    Regards
    This is not a solution to the problem. What you are doing by installing without NLS is simply avoiding it. QualityStage support NLS installations and fully supports Unicode data.

    My preference is to learn more about why you had this problem and determine if either it was a product issue or the documentation lack the detail required to set this up.

    Stewart
  • SystemAdmin
    SystemAdmin
    533 Posts

    Re: Match Designer Match Pass run failed

    ‏2008-01-11T23:10:52Z  
    in matching , i have pass to match 3 fields. name and reg number and another reg number. but out of 100% records more than 34% of records are null in 3rd field. can we do any overrides to make a match if the 3rd field have null.
    I am not sure I understand what you are trying do, but I suspect your objective is that when Col3 is MISSING (special QS term, look up the docs) then you don't what it to impact your match.

    Or are you using these Columns in your blocking?

    Regards

    Stewart
  • SystemAdmin
    SystemAdmin
    533 Posts

    Re: Match Designer Match Pass run failed

    ‏2008-01-11T23:16:51Z  
    Hi Stewart,

    I've got exactly the same problem as qualitystage reported on the 7th of January on our IIS 8.0.1 installation. I'm using an Oracle 10g database as ODBC-datasource. The database uses UTF8 as its NLS_NCHAR_CHARACTERSET, but not as its NLS_CHARACTERSET:

    NLS_CHARACTERSET WE8MSWIN1252
    NLS_NCHAR_CHARACTERSET UTF8

    I really did hope this might work, since we haven't currently got a database with different settings.

    I am afraid I haven't got the option to just reinstall IIS on our AIX machine, so I'll have to find a solution to this on the database side.

    Have you got any suggestions?

    regards
    Roland

    Message was edited by: rmelzer
    Roland,

    I am investigating this, will post a reply when I finish.

    Regards,

    Stewart
  • SystemAdmin
    SystemAdmin
    533 Posts

    Re: Match Designer Match Pass run failed

    ‏2008-02-13T03:35:56Z  
    Hi Stewart,

    I've got exactly the same problem as qualitystage reported on the 7th of January on our IIS 8.0.1 installation. I'm using an Oracle 10g database as ODBC-datasource. The database uses UTF8 as its NLS_NCHAR_CHARACTERSET, but not as its NLS_CHARACTERSET:

    NLS_CHARACTERSET WE8MSWIN1252
    NLS_NCHAR_CHARACTERSET UTF8

    I really did hope this might work, since we haven't currently got a database with different settings.

    I am afraid I haven't got the option to just reinstall IIS on our AIX machine, so I'll have to find a solution to this on the database side.

    Have you got any suggestions?

    regards
    Roland

    Message was edited by: rmelzer
    Sorry for the delay...

    These are the setting's I found for the Metadata Server database from the Oracle instructions. I am not Oracle expert but I hope they help

    Database Character Set AL32UTF8
    National Character Set AL16UTF16

    If you still have troubles please open a Support case so it can be tracked and resolved.

    Stewatr
  • SystemAdmin
    SystemAdmin
    533 Posts

    Re: Match Designer Match Pass run failed

    ‏2008-04-05T15:39:21Z  
    Sorry for the delay...

    These are the setting's I found for the Metadata Server database from the Oracle instructions. I am not Oracle expert but I hope they help

    Database Character Set AL32UTF8
    National Character Set AL16UTF16

    If you still have troubles please open a Support case so it can be tracked and resolved.

    Stewatr
    Hi Stewart,

    Thanks for the info. These settings are probably advisable, but we solved the problem using the settings I mentioned earlier on.

    The problem is that Character-Set settings can't be changed on an operational database.

    It looks like using Non-unicode strings on all input-columns of the match-designer input-file (not counting Match-frequency files) may solve the problem.
  • SystemAdmin
    SystemAdmin
    533 Posts

    Re: Match Designer Match Pass run failed

    ‏2009-05-01T18:37:54Z  
    Hi Stewart,

    Thanks for the info. These settings are probably advisable, but we solved the problem using the settings I mentioned earlier on.

    The problem is that Character-Set settings can't be changed on an operational database.

    It looks like using Non-unicode strings on all input-columns of the match-designer input-file (not counting Match-frequency files) may solve the problem.
    Hi, I am also getting the same below error: please let me know how to resolve this..

    ##I IIS-DSEE-TUTL-00031 13:52:31(001) <main_program> The open files limit is 15000; raising to 2147483647.
    ##I IIS-DSEE-TOSH-00002 13:52:31(002) <main_program> orchgeneral: loaded
    ##I IIS-DSEE-TOSH-00002 13:52:31(003) <main_program> orchsort: loaded
    ##I IIS-DSEE-TOSH-00002 13:52:31(004) <main_program> orchstats: loaded
    ##I IIS-DSEE-TDOD-00080 13:52:32(000) <MWI_Odbc_Write> Process meta data not available in database
    ##I IIS-DSEE-TFSC-00001 13:52:32(002) <main_program> APT configuration file: /opt/IBM/InformationServer/Server/Configurations/default.apt
    ##E IIS-QSEE-MATM-00004 13:52:33(000) <QS_Test_MWI_0,0> Variable _qsC_CityName_USAREA not found in [A] frequency file

    ##E IIS-QSEE-POTO-00002 13:52:33(001) <QS_Test_MWI_0,0> Fatal error from object qsmExit, code 4

    ##E IIS-DSEE-TFOR-00089 13:52:33(003) <QS_Test_MWI_0,0> The runLocally() of the operator failed.
    ##I IIS-DSEE-TFOR-00094 13:52:33(004) <QS_Test_MWI_0,0> Output 0 produced 100 records.
    ##E IIS-DSEE-TFPM-00040 13:52:33(005) <QS_Test_MWI_0,0> Operator terminated abnormally: runLocally did not return APT_StatusOk
    ##E IIS-DSEE-TFSC-00011 13:52:39(000) <main_program> Step execution finished with status = FAILED.
    ##I IIS-DSEE-TCOS-00026 13:52:39(001) <main_program> Startup time, 0:06; production run time, 0:01.

    Thanks in advance..

    Jan Reddy
  • OldJack
    OldJack
    1 Post

    Re: Match Designer Match Pass run failed

    ‏2010-03-12T19:02:34Z  
    Hi, I am also getting the same below error: please let me know how to resolve this..

    ##I IIS-DSEE-TUTL-00031 13:52:31(001) <main_program> The open files limit is 15000; raising to 2147483647.
    ##I IIS-DSEE-TOSH-00002 13:52:31(002) <main_program> orchgeneral: loaded
    ##I IIS-DSEE-TOSH-00002 13:52:31(003) <main_program> orchsort: loaded
    ##I IIS-DSEE-TOSH-00002 13:52:31(004) <main_program> orchstats: loaded
    ##I IIS-DSEE-TDOD-00080 13:52:32(000) <MWI_Odbc_Write> Process meta data not available in database
    ##I IIS-DSEE-TFSC-00001 13:52:32(002) <main_program> APT configuration file: /opt/IBM/InformationServer/Server/Configurations/default.apt
    ##E IIS-QSEE-MATM-00004 13:52:33(000) <QS_Test_MWI_0,0> Variable _qsC_CityName_USAREA not found in [A] frequency file

    ##E IIS-QSEE-POTO-00002 13:52:33(001) <QS_Test_MWI_0,0> Fatal error from object qsmExit, code 4

    ##E IIS-DSEE-TFOR-00089 13:52:33(003) <QS_Test_MWI_0,0> The runLocally() of the operator failed.
    ##I IIS-DSEE-TFOR-00094 13:52:33(004) <QS_Test_MWI_0,0> Output 0 produced 100 records.
    ##E IIS-DSEE-TFPM-00040 13:52:33(005) <QS_Test_MWI_0,0> Operator terminated abnormally: runLocally did not return APT_StatusOk
    ##E IIS-DSEE-TFSC-00011 13:52:39(000) <main_program> Step execution finished with status = FAILED.
    ##I IIS-DSEE-TCOS-00026 13:52:39(001) <main_program> Startup time, 0:06; production run time, 0:01.

    Thanks in advance..

    Jan Reddy
    I have the similar issue here. I've tried to eliminate all the unicode data from source, force the source data converted from nvarchar to varchar, and changed the table definition in QualityStage to varchar with no unicode supported. However, the Test Pass still failed. Below is the full log.

    ##I IIS-DSEE-TFCN-00001 18:54:30(000) <main_program>
    IBM WebSphere DataStage Enterprise Edition 8.1.0.4987
    Copyright (c) 2001, 2005-2008 IBM Corporation. All rights reserved

    ##I IIS-DSEE-TFCN-00006 18:54:30(001) <main_program> conductor uname: -s=Windows_NT; -r=2; -v=5; -n=UKATREMA4500; -m=Pentium
    ##I IIS-DSEE-TOSH-00002 18:54:30(002) <main_program> orchgeneral: loaded
    ##I IIS-DSEE-TOSH-00002 18:54:30(003) <main_program> orchsort: loaded
    ##I IIS-DSEE-TOSH-00002 18:54:30(004) <main_program> orchstats: loaded
    ##I IIS-DSEE-TDOD-00080 18:54:31(001) <ODBC_Enterprise_0> Process meta data not available in database
    ##I IIS-DSEE-TDOD-00080 18:54:31(003) <ODBC_Enterprise_0> Process meta data not available in database
    ##I IIS-DSEE-TDOD-00080 18:54:31(006) <ODBC_Enterprise_0> Process meta data not available in database
    ##I IIS-DSEE-TDOD-00080 18:54:31(008) <MWI_Odbc_Write> Process meta data not available in database
    ##I IIS-DSEE-TFSC-00001 18:54:31(010) <main_program> APT configuration file: E:/IBM/InformationServer/Server/Configurations/default.apt
    ##W IIS-DSEE-TFIP-00072 18:54:31(011) <APT_CopyOperator(2) in QSmtc_geomatch> When checking operator: When binding output schema variable "outRec": When binding output interface field "qsMatchSetID" to field "qsMatchSetID": Implicit conversion from source type "uint64" to result type "int64": Possible range limitation.
    ##W IIS-DSEE-TFIP-00072 18:54:31(012) <APT_CopyOperator(2) in QSmtc_geomatch> When checking operator: When binding output schema variable "outRec": When binding output interface field "qsMatchRefID" to field "qsMatchRefID": Implicit conversion from source type "uint64" to result type "int64": Possible range limitation.
    ##W IIS-DSEE-TFIP-00072 18:54:31(013) <APT_CopyOperator(2) in QSmtc_geomatch> When checking operator: When binding output schema variable "outRec": When binding output interface field "qsMatchDataID" to field "qsMatchDataID": Implicit conversion from source type "uint64" to result type "int64": Possible range limitation.
    ##W IIS-DSEE-TFIP-00072 18:54:31(014) <QSM_MatStatsOp in QSmtc_geomatch> When checking operator: When binding output interface field "qsMatchStatValue" to field "qsMatchStatValue": Implicit conversion from source type "uint64" to result type "int64": Possible range limitation.
    ##E IIS-QSEE-GLBL-00007 18:55:31(000) <QSM_MatOp in QSmtc_geomatch,1> A call to the ICU function utrans_transUChars failed, reason code 15
    U_BUFFER_OVERFLOW_ERROR

    ##E IIS-QSEE-POTO-00002 18:55:31(001) <QSM_MatOp in QSmtc_geomatch,1> Fatal error from object or function rtExpandBuffer, code 1

    ##E IIS-DSEE-TFOR-00089 18:55:31(002) <QSM_MatOp in QSmtc_geomatch,1> The runLocally() of the operator failed.
    ##I IIS-DSEE-TFOR-00163 18:55:31(003) <QSM_MatOp in QSmtc_geomatch,1> Input 0 consumed 2999 records.
    ##I IIS-DSEE-TFOR-00163 18:55:31(004) <QSM_MatOp in QSmtc_geomatch,1> Input 1 consumed 2 records.
    ##I IIS-DSEE-TFOR-00163 18:55:31(005) <QSM_MatOp in QSmtc_geomatch,1> Input 2 consumed 89093 records.
    ##I IIS-DSEE-TFOR-00163 18:55:31(006) <QSM_MatOp in QSmtc_geomatch,1> Input 3 consumed 2 records.
    ##I IIS-DSEE-TFOR-00094 18:55:31(007) <QSM_MatOp in QSmtc_geomatch,1> Output 0 produced 5335 records.
    ##I IIS-DSEE-TFOR-00094 18:55:31(008) <QSM_MatOp in QSmtc_geomatch,1> Output 1 produced 3 records.
    ##E IIS-DSEE-TFPM-00040 18:55:31(009) <QSM_MatOp in QSmtc_geomatch,1> Operator terminated abnormally: runLocally() did not return APT_StatusOk
    ##E IIS-DSEE-TFSC-00011 18:55:38(000) <main_program> Step execution finished with status = FAILED.
    ##I IIS-DSEE-TCOS-00026 18:55:38(001) <main_program> Startup time, 0:13; production run time, 0:54.

    Anyone can help?

    Thanks