1 2 Previous Next 17 Replies Latest reply on Jun 17, 2020 8:00 AM by dan.smith@informatica.com Go to original post Branched from an earlier discussion. Branched to a new discussion.
      • 15. Re: PWXCCL for PWX SQL Server CDC
        dan.smith@informatica.com Guru

        That is windows saying that it can't find dtlscli.dll.

        dtlscli.dll is the executable that PC calls to talk with PWX.

         

        Make sure that the login running PC has read and execute permissions on dtlscli

        • 16. Re: PWXCCL for PWX SQL Server CDC
          YuanJie Li New Member

          I have the same problem here, but I don't think it is caused by this reason.

          How have you created two Extraction Definitions from different DB tables with the same Instance?

           

          The following 2 source databases that all publish to the same DistDB

          ・ProdMgtBasicInfo

          ・ProgressMgt

          I found there are two instances as below

          ・PROD000

          ・PROG000

          And I've created two capture registrations as below by the PWX Navigator, both of them are Condense Type of Partial and Active.

          d10prod000.table01.dmx

          ・ d10prog000.table02.dmx

           

          the content of my configuration file is as follows:

          ◆dbmover.cfg

          CAPI_CONNECTION=(NAME=CAPIMSQ,

          TYPE=(MSQL,DISTSRV=10.0.0.4,

                DISTDB=distribution,

                EOF=N,RSTRADV=0,MULTIPUB=Y))

           

          LOGPATH=C:\Informatica\PowerExchange10.4.0\mms\Logs

          CAPT_PATH=C:\Informatica\PowerExchange10.4.0\mms\capture@

          CAPT_XTRA=C:\Informatica\PowerExchange10.4.0\mms\capture\camaps

          TRACING=(PFX=PWXLOG,APPEND=Y,FLUSH=1,FILENUM=3,RECLEN=255,SIZE=1)

           

          /* Define a CAPX CAPI_CONNECTION statement if you use the PowerExchange Logger

          /* and continuous extraction mode.

          CAPI_CONN_NAME=CAPIMSQ

          CAPI_CONNECTION=(NAME=CAPXMMS,TYPE=(CAPX,DFLTINST=PRODnnn))

          ◆pwxccl.cfg

          DBID=PRODnnn

          DB_TYPE=MSS

          CAPTURE_NODE_UID=XXX

          /*CAPTURE_NODE_EPWD=encrypted_password

          CAPTURE_NODE_PWD=XXXXXXXXX

          PROMPT=Y

          /* The directory that you created for the Logger log files.

          EXT_CAPT_MASK=C:\Informatica\PowerExchange10.4.0\mms\logger_files\scondense

           

          I guess there should be a problem with the DFLTINST in Dbmover.cfg and the DBID setting in PWXCCL.cfg.

          When there is only one Instance, DFLTINST in Dbmover.cfg and DBID in PWXCCL.cfg should be set to the name of the Instance. But now there are two Instances, how should DFLTINST and DBID be set?

          • 17. Re: PWXCCL for PWX SQL Server CDC
            dan.smith@informatica.com Guru

            When you are using Multipub=Y, the rules about DFLTINST and DBID change slightly.

             

            However, DFLTINST always determines the CDCT that PWX Listener will read when it attempts to find captured data in CND files.

             

            Likewise, DBID in PWXCCL.CFG is what will be used by PWXCCL when creating the CDCT.

             

            So those two values always have to match.

            1 2 Previous Next