1 2 Previous Next 17 Replies Latest reply on Oct 6, 2017 11:20 AM by Chetan Pradhan

    DTM Error

    Ashley Massa New Member

      We are connecting to an access database to pull data into a custom object.  The integration field mapping is correct but we keep getting this error "Internal error. The DTM process terminated unexpectedly. Contact Informatica Global Customer Support."  We have followed online help to run counter logs, restarting the server and refreshed windows.  We have also taken down firewalls. We are still getting the error and are looking for help.

        • 1. Re: DTM Error
          Ashley Massa New Member

          Update  - error log

          08/18/2017 13:59:08 **** Importing Connection: SrcConn_0009CA0B000000000008 ...

          08/18/2017 13:59:08 **** Importing Connection: TargConn_0009CA0B000000000001 ...

          08/18/2017 13:59:09 **** Importing Source Definition: tblHecoRepAllQuestionsSync ...

          08/18/2017 13:59:09 **** Importing Target Definition: VPD_Questions__c ...

          08/18/2017 13:59:09 **** Importing SessionConfig: cfg_s_dss_0009CA0I00000000000J ...

              <Warning> :  The Error Log DB Connection value should have Relational: as the prefix.

              <Warning> :  Invalid value  for attribute Error Log DB Connection. Will use the default value

              Validating Source Definition  tblHecoRepAllQuestionsSync...

              Validating Target Definition  VPD_Questions__c...

          08/18/2017 13:59:09 **** Importing Mapping: m_dss_0009CA0I00000000000J ...

          Validating transformations of mapping m_dss_0009CA0I00000000000J...

          Validating mapping variable(s).

          08/18/2017 13:59:09 **** Importing Workflow: wf_dss_0009CA0I00000000000J ...

              <Warning> :  The value entered is not a valid integer.

              <Warning> :  Invalid value NO for attribute Fail task after wait time. Will use the default value

          Successfully extracted session instance [s_dss_0009CA0I00000000000J].  Starting repository sequence id is [2066994015]

          • 2. Re: DTM Error
            EC140656 Seasoned Veteran

            Hi Ashley,

            Few suggestions here :

             

            1) Try to make appropriate changes to the code so that the Warnings are not present.

            2) In your specific scenario below:

            --------------------------------------------------------------------------------------------------------------

            08/18/2017 13:59:09 **** Importing Workflow: wf_dss_0009CA0I00000000000J ...

                <Warning> :  The value entered is not a valid integer.

            --------------------------------------------------------------------------------------------------------------

             

            There seems to be a datatype mismatch. Please correct that.

            3) Please check the target connection type & source connection type. Is it a ODBC driver connection or MS-Access driver connection? Since MS-Access is a legacy DB, there "may be" driver limitations/compatibility issues also. Please check on those lines.

            4) In your particular scenario, since you say you are using MS-Access DB, if the Workflow fails & tries to write the error log to MS-Access it will fail since the error log DB connection is not set up properly. This could be why the DTM process is failing. This I say because of the following line in your Error log given in your message :

             

            ----------------------------------------------------------------------------------------------------------------

            08/18/2017 13:59:09 **** Importing SessionConfig: cfg_s_dss_0009CA0I00000000000J ...

                <Warning> :  The Error Log DB Connection value should have Relational: as the prefix.

                <Warning> :  Invalid value  for attribute Error Log DB Connection. Will use the default value

            --------------------------------------------------------------------------------------------------------------------

             

            5) Please share the Worfklow log/Session Log details in full if possible. That will make it easier to suggest a solution in this forum.

            6) If the DTM process(Data Transformation Manager) terminated unexpectedly, that will be caused by either bad parameter values/bad connections/bad data most of the time. The issue mostly will  not be with your mapping/workflow code.

             

            Hope this helps.

            Please keep us updated.

            • 3. Re: DTM Error
              Ashley Massa New Member

              Here is the full log.  The only field I can think that would be a datatype mismatch is the one in the attached photo.  It is a lookup field in Salesforce to the UserID and is a text field in the Access DB.

               

              • 4. Re: DTM Error
                Ashley Massa New Member

                08/18/2017 13:59:08 **** Importing Connection: SrcConn_0009CA0B000000000008 ...

                08/18/2017 13:59:08 **** Importing Connection: TargConn_0009CA0B000000000001 ...

                08/18/2017 13:59:09 **** Importing Source Definition: tblHecoRepAllQuestionsSync ...

                08/18/2017 13:59:09 **** Importing Target Definition: VPD_Questions__c ...

                08/18/2017 13:59:09 **** Importing SessionConfig: cfg_s_dss_0009CA0I00000000000J ...

                    <Warning> :  The Error Log DB Connection value should have Relational: as the prefix.

                    <Warning> :  Invalid value  for attribute Error Log DB Connection. Will use the default value

                    Validating Source Definition  tblHecoRepAllQuestionsSync...

                    Validating Target Definition  VPD_Questions__c...

                08/18/2017 13:59:09 **** Importing Mapping: m_dss_0009CA0I00000000000J ...

                Validating transformations of mapping m_dss_0009CA0I00000000000J...

                Validating mapping variable(s).

                08/18/2017 13:59:09 **** Importing Workflow: wf_dss_0009CA0I00000000000J ...

                    <Warning> :  The value entered is not a valid integer.

                    <Warning> :  Invalid value NO for attribute Fail task after wait time. Will use the default value

                Successfully extracted session instance [s_dss_0009CA0I00000000000J].  Starting repository sequence id is [2066994015]

                ======================================================================

                DIRECTOR> VAR_27085 [2017-08-18 13:59:09.228] Parameter file [C:\Program Files\Informatica Cloud Secure Agent\apps\Data_Integration_Server\data\parameters\s_dss_0009CA0I00000000000J.param] is opened for [session [wf_dss_0009CA0I00000000000J.s_dss_0009CA0I00000000000J]].

                DIRECTOR> VAR_27062 [2017-08-18 13:59:09.228] Warning! Cannot find section for worklet [wf_dss_0009CA0I00000000000J] and folder [] in parameter file [C:\Program Files\Informatica Cloud Secure Agent\apps\Data_Integration_Server\data\parameters\s_dss_0009CA0I00000000000J.param].

                DIRECTOR> VAR_27028 [2017-08-18 13:59:09.228] Use override value [s_dss_0009CA0I00000000000J_0_error.csv] for user-defined workflow/worklet variable:[$ErrorFileName].

                DIRECTOR> VAR_27028 [2017-08-18 13:59:09.228] Use override value ['1970-01-01'] for user-defined workflow/worklet variable:[$LastRunDate].

                DIRECTOR> VAR_27028 [2017-08-18 13:59:09.228] Use override value [#1970-01-01 00:00:00#] for user-defined workflow/worklet variable:[$LastRunTime].

                DIRECTOR> VAR_27028 [2017-08-18 13:59:09.228] Use override value [s_dss_0009CA0I00000000000J_8_18_2017_18_59_success.csv] for user-defined workflow/worklet variable:[$SuccessFileName].

                DIRECTOR> TM_6014 [2017-08-18 13:59:09.228] Initializing session [s_dss_0009CA0I00000000000J] at [Fri Aug 18 13:59:09 2017].

                DIRECTOR> TM_6683 [2017-08-18 13:59:09.228] Repository Name: [XMLRepository]

                DIRECTOR> TM_6684 [2017-08-18 13:59:09.228] Server Name: [rDTM]

                DIRECTOR> TM_6686 [2017-08-18 13:59:09.228] Folder: []

                DIRECTOR> TM_6685 [2017-08-18 13:59:09.228] Workflow: [wf_dss_0009CA0I00000000000J] Run Instance Name: [] Run Id: [0]

                DIRECTOR> TM_6101 [2017-08-18 13:59:09.228] Mapping name: m_dss_0009CA0I00000000000J.

                DIRECTOR> TM_6964 [2017-08-18 13:59:09.228] Date format for the Session is [MM/DD/YYYY HH24:MI:SS]

                DIRECTOR> TM_6703 [2017-08-18 13:59:09.228] Session [s_dss_0009CA0I00000000000J] is run by 64-bit Integration Service  [], version [9.1.0 HotFix1], build [0627].

                MANAGER> PETL_24058 [2017-08-18 13:59:09.243] Running Partition Group [1].

                MANAGER> PETL_24000 [2017-08-18 13:59:09.243] Parallel Pipeline Engine initializing.

                MANAGER> PETL_24001 [2017-08-18 13:59:09.243] Parallel Pipeline Engine running.

                MANAGER> PETL_24003 [2017-08-18 13:59:09.243] Initializing session run.

                MAPPING> CMN_1569 [2017-08-18 13:59:09.243] Server Mode: [UNICODE]

                MAPPING> CMN_1570 [2017-08-18 13:59:09.243] Server Code page: [MS Windows Latin 1 (ANSI), superset of Latin1]

                MAPPING> TM_6151 [2017-08-18 13:59:09.243] The session sort order is [Binary].

                MAPPING> TM_6185 [2017-08-18 13:59:09.243] Warning. Code page validation is disabled in this session.

                MAPPING> TM_6155 [2017-08-18 13:59:09.243] Using HIGH precision processing.

                MAPPING> TM_6180 [2017-08-18 13:59:09.243] Deadlock retry logic will not be implemented.

                MAPPING> TM_6181 [2017-08-18 13:59:09.243] Session source-based commit interval is [5000].

                MAPPING> SDKS_38029 [2017-08-18 13:59:09.243] Loaded plug-in 310600: [PowerExchange for Salesforce.com Writer Plugin 9.1.0].

                MAPPING> SDKS_38024 [2017-08-18 13:59:09.243] Plug-in 310600 initialization complete.

                MAPPING> SDKS_38017 [2017-08-18 13:59:09.243] Writer SDK plug-in intialization complete.

                MAPPING> SDKS_38509 [2017-08-18 13:59:09.243] SDK target and group initialization complete.

                MAPPING> TM_6308 [2017-08-18 13:59:09.243] DTM error log using code page UTF-8.

                MAPPING> TM_6310 [2017-08-18 13:59:09.243] DTM error log enabled at file [C:\Program Files\Informatica Cloud Secure Agent\apps\Data_Integration_Server\data\error\s_dss_0009CA0I00000000000J_0_error.csv].

                MAPPING> TM_6682 [2017-08-18 13:59:09.243] Warning: Since DTM Error Logging is enabled, row level errors will not be written to the session log. Please check the DTM Error Log for any row level errors.

                MAPPING> TM_6701 [2017-08-18 13:59:09.243] Warning: The data column delimiter for DTM Error logging and the flat file delimiter are the same [','].

                MAPPING> TE_7022 [2017-08-18 13:59:09.243] TShmWriter: Initialized

                MAPPING> DBG_21491 [2017-08-18 13:59:09.243] Source-based commit interval based on rows from Source Qualifier [SQ_tblHecoRepAllQuestionsSync]

                MAPPING> DBG_21244 [2017-08-18 13:59:09.243] Initializing Load Order Group [1]. Source Qualifier is [SQ_tblHecoRepAllQuestionsSync]

                MAPPING> TM_6007 [2017-08-18 13:59:09.243] DTM initialized successfully for session [s_dss_0009CA0I00000000000J]

                DIRECTOR> PETL_24033 [2017-08-18 13:59:09.275] All DTM Connection Info: [<NONE>].

                MANAGER> PETL_24004 [2017-08-18 13:59:09.275] Starting pre-session tasks. : (Fri Aug 18 13:59:09 2017)

                MANAGER> PETL_24027 [2017-08-18 13:59:09.353] Pre-session task completed successfully. : (Fri Aug 18 13:59:09 2017)

                DIRECTOR> PETL_24006 [2017-08-18 13:59:09.353] Starting data movement.

                MAPPING> TM_6660 [2017-08-18 13:59:09.353] Total Buffer Pool size is 11611984 bytes and Block size is 642888 bytes.

                READER_1_1_1> DBG_21438 [2017-08-18 13:59:09.353] Reader: Source is [VPDDataSync], user [bogususername]

                READER_1_1_1> BLKR_16051 [2017-08-18 13:59:09.353] Source database connection [SrcConn_0009CA0B000000000008] code page: [MS Windows Latin 1 (ANSI), superset of Latin1]

                READER_1_1_1> CMN_1021 [2017-08-18 13:59:09.384] Database driver event...

                CMN_1021 [ODBC Event Using array fetches.

                 

                 

                ODBC Event Using Single Row Inserts. connect string = [VPDDataSync]. userid = [bogususername]]

                 

                 

                READER_1_1_1> BLKR_16003 [2017-08-18 13:59:09.384] Initialization completed successfully.

                WRITER_1_*_1> SFDC_31211 [2017-08-18 13:59:09.384] [INFO] Target [VPD_Questions__c] enables treat insert as upsert. external Id: [VPD_Sync__c].

                WRITER_1_*_1> SFDC_31210 [2017-08-18 13:59:09.384] [INFO] Target [VPD_Questions__c] will process Salesforce.com object type [VPD_Questions__c].

                WRITER_1_*_1> SFDC_31217 [2017-08-18 13:59:09.384] [INFO] The Salesforce connection timeout is set to: [300].

                WRITER_1_*_1> SFDC_31218 [2017-08-18 13:59:09.384] [INFO] The Salesforce connection is using [TLSv1.2] for encryption.

                WRITER_1_*_1> SFDC_31216 [2017-08-18 13:59:10.462] [INFO] Account [itdept@highwayequipment.com] logged on salesforce.com at [https://login.salesforce.com/services/Soap/u/31.0].

                WRITER_1_*_1> WRT_8270 [2017-08-18 13:59:10.462] Target connection group #1 consists of target(s) [VPD_Questions__c: Partition 1]

                WRITER_1_*_1> WRT_8324 [2017-08-18 13:59:10.462] Warning: Target Connection Group's connection doesn't support transactions. Targets [VPD_Questions__c: Partition 1] may not be loaded according to specified transaction boundary rules!

                WRITER_1_*_1> WRT_8003 [2017-08-18 13:59:10.462] Writer initialization complete.

                READER_1_1_1> BLKR_16007 [2017-08-18 13:59:10.462] Reader run started.

                WRITER_1_*_1> WRT_8005 [2017-08-18 13:59:10.462] Writer run started.

                WRITER_1_*_1> WRT_8158 [2017-08-18 13:59:10.462]

                 

                 

                *****START LOAD SESSION*****

                 

                 

                Load Start Time: Fri Aug 18 13:59:10 2017

                 

                 

                Target tables:

                 

                 

                     VPD_Questions__c: Partition 1

                 

                 

                 

                 

                READER_1_1_1> RR_4010 [2017-08-18 13:59:10.462] SQ instance [SQ_tblHecoRepAllQuestionsSync] SQL Query [SELECT tblHecoRepAllQuestionsSync.QuestionNum3, tblHecoRepAllQuestionsSync.HecoRepCode, tblHecoRepAllQuestionsSync.Question1, tblHecoRepAllQuestionsSync.SalesforceID, tblHecoRepAllQuestionsSync.Question4, tblHecoRepAllQuestionsSync.QuestionNum1, tblHecoRepAllQuestionsSync.Question2, tblHecoRepAllQuestionsSync.Question3, tblHecoRepAllQuestionsSync.QuestionNum2, tblHecoRepAllQuestionsSync.QuestionNum4 FROM tblHecoRepAllQuestionsSync]

                READER_1_1_1> RR_4049 [2017-08-18 13:59:10.462] SQL Query issued to database : (Fri Aug 18 13:59:10 2017)

                • 5. Re: DTM Error
                  EC140656 Seasoned Veteran

                  Few observations from my side based on the full error log & the screenshot:

                   

                  1. Since the Error log stops at the Reader end, the mapping is not reading the source data for sure.

                  2. I am not sure where your MS Access DB is placed. Is it in the same box as the Informatica Server or is it placed across the network(inside your company network/across the internet etc.) in a different desktop/laptop?  The best practice for pulling data from MS-Access is to collect the different Access DBs using FTP into a common shared folder in the Informatica server & then pulling data into Informatica from there.

                  3. Since it is MS-Access DB, I would suggest debugging as follows: Copy a sample MS Access DB with sample data into the Informatica Server box,change the source connection values to this path & try pulling data from it. If it works, then the issue is with the network path to the MS Access source DB only.

                   

                  Hope this helps.

                  Krishna

                  • 6. Re: DTM Error
                    Ashley Massa New Member

                    Krishna

                     

                    Here's our current setup on the server.

                    As you can see, we have a functional cloud secure agent on the same server as Access DB which is on the root directory of the server.  We also have a ODBC Source connection.  Are we missing something?

                     

                    As for #3 - I'm struggling to understand this as the connection tests fine when we are in Informatica so doesn't that show it's a good connection?

                    • 7. Re: DTM Error
                      EC140656 Seasoned Veteran

                      Few observations based on your screenshot & based on my understanding so far :

                       

                      1. What version of Windows are you using? Is it Windows 10 or lesser versions? This is relevant because the 64-bit verion of Informatica Cloud Secure Agent is not fully stable when installed on Windows 10 OS. We tried to install 64-bit version of Informatica Cloud Secure Agent on Windows 10 box but it did not install/run properly.

                      2. The 32-bit version of Informatica Cloud Secure Agent is stable & more robust. The 64-bit version was not so stable until 4 or 5 months back. This means it might be prone to errors. You may check this out in other forums to confirm my experience on 64-bit version of ISA.

                      3. I have the following suggestions for you :

                           a) Use the 32-bit version of Informatica Cloud Secure Agent rather than the 64-bit version.

                           b) Test out the Informatica Cloud Secure Agent connection on a Windows 7 or 8 32-bit version OS. That will make it easier for you to debug.

                      4. Since you have placed the MS Access Source DB in the same box as the Informatica server(as per your previous message), the network path issue is ruled out for now.

                      • 8. Re: DTM Error
                        EC140656 Seasoned Veteran

                        I suggest you go through below KB article on how to debug DTM error further :

                         

                        https://kb.informatica.com/solution/23/Pages/58/497790.aspx

                        • 9. Re: DTM Error
                          Ashley Massa New Member

                          where we download the 32-bit client?

                          • 10. Re: DTM Error
                            EC140656 Seasoned Veteran

                            I suggest you go through below KB article in full. You may be able to infer the next steps from this :

                             

                            https://network.informatica.com/docs/DOC-14954

                             

                            Please follow me in Informatica Network so that we can discuss/share further details over email message.

                            • 11. Re: DTM Error
                              Ashley Massa New Member

                              Krishna

                               

                              We followed the article but all that is available when downloading a new agent is the 64 bit.

                               

                              • 12. Re: DTM Error
                                Scott Nelson Guru

                                The 32-bit client went EOL last year.

                                • 13. Re: DTM Error
                                  Ashley Massa New Member

                                  Scott - with that in mind, I'm not sure what to do next.  We've tried moving the database and connection to a windows 2010 and 2007 machine with the same failure. 

                                  • 14. Re: DTM Error
                                    EC140656 Seasoned Veteran

                                    Yes.

                                     

                                    You have to request the 32-bit client either directly from Informatica Support or check it with your support team who might have downloaded it//archived it when they first installed the Informatica Cloud Integration.

                                     

                                    The other option is to get it from some other sources/people who are currently using it.

                                     

                                    Have you installed the 64-bit version on Windows 10 or earlier versions? Installing the 64-bit Secure Agent on earlier versions(for ex. Windows 8.1 64-bit version OS etc.) may work. I don't know for sure though. I used the 32-bit version of the Secure Agent the last time.

                                     

                                    You may also search in the Internet for this.

                                    1 2 Previous Next