User Guide. Informatica Log Express

Transcription

1 User Guide Informatica Log Express (Version 1.1)

2 Table of Contents Chapter 1: Getting Started Introduction Benefits Architecture Chapter 2: Installation Installing Server Windows Linux Installing Agent Pre-requisites for Agent Installation Windows UNIX Platforms Chapter 3: User Interface Login Home Page Agents Navigator Agent Overview Actions Scenario Output Chapter 4: Configuration Configure Agent Configure Product Configure User Administrator user Non-Administrator user Configure SMTP Chapter 5: Scenario Based Collections Scenario Run Overview PowerCenter Scenarios Session Crash Session Hang Session Performance Integration Service Crash Integration Service Hang Repository Service Crash Repository Service Hang Table of Contents ii

3 Data Quality Scenarios Mapping Crash Mapping Hang Data Quality Profile Crash Data Quality Profile Hang Generic Scenarios PowerCenter Repository Inconsistencies Create Domain Backup Generic Scenario Table of Contents iii

4 C HAPTER 1 Getting Started Introduction Informatica Log Express is a scenario based intelligent aggregator of troubleshooting information. It is a web based self-help application, which collects diagnostic data such as logs, configuration reports, system information, stack traces, metadata exports, workflow exports etc. For a given scenario, it can collect the diagnostic data from any of the servers in your (customer) environment where Informatica products are deployed. Informatica Log Express has a light-weight agent running on your environment, which collects the data less intrusively and uploads it seamlessly to a common secure FTP location at Informatica. Informatica Log Express s scenario based wizard UI helps you understand the problem type and upload the appropriate logs to Informatica FTP. Informatica Log Express - the automated diagnostic data gathering utility - expedites the data gathering and issue resolution process. Benefits Informatica Log Express enables you to: Improve user experience in overall problem discovery process during the life cycle of a service request Reduce up to 25 percent of overall resolution time Gather all troubleshooting data in a single customer and Global Customer Support interaction Collect all relevant logs from different products using a single interface (product neutral solution) Improve product quality by monitoring error trends identified through the standardized uploaded logs Introduction 4

5 Architecture Informatica Log Express consists of a centralized server and multiple agents. The server is deployed on Tomcat. The Informatica Log Express agents are light-weight Java processes running for every installation of the product. On startup, the agents register themselves with the server. Each agent is configured to a product installation instance. The Informatica Log Express server delegates the collection of troubleshooting data for a given node (product instance) to the appropriate agent on that node. Log Express Server Scenario output Log Express Agent Node Node Log Express Agent Informatica Domain Node Node Log Express Agent Log Express Agent TSFTP Informatica Log Express enables you to collect all the relevant troubleshooting data for a given scenario in few easy steps. The data is zipped into a file and uploaded to the user folder in the Informatica FTP site - TSFTP. Informatica Global Customer Support can access all data at one go and thus the number of data collection iterations are minimized. Architecture 5

6 C HAPTER 2 Installation Informatica Log Express consists of a centralized server and multiple agents. The server is deployed on Tomcat. Install the Informatica Log Express Server before installing any agent. This is because Informatica Log Express agents register themselves with server after installation. Thus, it is advisable to have the server up and running before installing the agents. The Informatica Log Express installation involves Installing Server and Installing Agent. The server can be installed on the following operating systems: Windows Linux The agent can be installed on any Informatica 9 supported operating system. Installing Server Windows To install Informatica Log Express server on Windows, do the following: 1. Close all other applications before starting the installation. 2. Copy the LogExpressInstaller.zip file on your local machine, unzip it, and run the LogExpressInstaller.exe file. 3. The Welcome screen introduces the Informatica Log Express installation. Click Next. 4. Select the location where you want to install Informatica Log Express server. Click Next. Installing Server 6

7 5. Provide the Tomcat Connector Port, Tomcat Shutdown Port, FTP Port, and FTP Directory. Click Next. Installing Server 7

8 6. Review the pre-installation summary. Click Install to proceed. Installing Server 8

9 Informatica Log Express server would be installed. Installing Server 9

10 Linux To install Informatica Log Express sever on Linux, do the following: 1. Unzip LogExpressInstaller_Linux.zip. 2. Set Execute permission to unzip the folder. Example, chmod -R 755 LogExpressInstaller_Linux. 3. Go to the unzipped folder, such as, cd LogExpressInstaller_Linux. 4. Run sh install.sh. 5. The Welcome screen introduces the Informatica Log Express installation. Click Next. Installing Server 10

11 6. Provide the location where you want to install Informatica Log Express server. The default location is InformaticaLogExpress directory in the user's home directory, such as /home/idptest1/informaticalogexpress. Press Enter to continue. 7. Provide the Tomcat Connector port number. Press Enter to continue. 8. Provide the Tomcat Shutdown port number. Press Enter to continue. Installing Server 11

12 9. Provide the Embedded FTP Server port number. Press Enter to continue. 10. Provide the FTP directory. The default is tomcat/ftproot in the LogExpress installation directory, such as /home/idptest1/informaticalogexpress/logexpress/tomcat/ftproot. Press Enter to continue. 11. Review the pre-installation summary displayed. Press Enter to continue. Installing Server 12

13 12. Informatica Log Express server would be installed. Installing Server 13

14 Installing Agent The agent can be installed on the following: Windows UNIX Platforms Pre-requisites for Agent Installation Before installing an agent, do the following: 1. Ensure that the following environment variables are set: INFA_HOME INFA_DEFAULT_DOMAIN_PASSWORD Note: In case of agents running on Windows, ensure that the above mentioned variables are set as system variables and not as user-defined variables in the environment configuration. 2. On UNIX installations, install/start the agent with the same user credentials and environment settings as the user running the Informatica processes. 3. In case of Informatica 9.5.x running on HP-UX and AIX, ensure that INFA_JDK_HOME environment variable is set. 4. Ensure that the Informatica Log Express server is installed and is already running. Note: Agents have to be installed on all nodes for which you intend to collect the troubleshooting data. Installing Agent 14

15 Windows The agent installation has a few pre-requisites. Refer to Pre-requisites for Agent Installation section before proceeding. After the above pre-requisites are met, do the following to install the agent: 1. Copy LogExpressAgentInstaller.zip on the machine where PowerCenter server is hosted, unzip it, and run the LogExpressAgentInstaller.bat file. 2. The Welcome screen is displayed. Ensure that the Informatica Log Express Server is already installed and all the port numbers you input are free and available. Click Next to continue. 3. Provide the server configuration information - server host name and port number. Click Next to continue. Installing Agent 15

16 4. The Informatica Log Express server will be pinged. In case the ping fails, verify the following: The Informatica Log Express server is already installed and is running. The Informatica Log Express server host and port provided are correct. 5. Provide the location where you would like to install the Log Express agent. Click Next to continue. Installing Agent 16

17 6. Provide a port number on this host for the agent. Click Next to continue. 7. If the port number is already in use by another process/service, the following would be displayed. Provide another port value to resolve the issue. Installing Agent 17

18 8. Select bit-mode of Informatica install on this host. Click Next to continue. Note: The Log Express application will not start if the choice is incorrect. 9. The pre-installation summary is displayed. Click Install to continue. Installing Agent 18

19 The Informatica Log Express Agent would be installed. Installing Agent 19

20 UNIX Platforms The following section discusses the steps for installing a Log Express agent on all Informatica 9 supported UNIX platforms, such as Linux, AIX, Solaris, and HP-UX. The agent installation has a few pre-requisites. Refer to Pre-requisites for Agent Installation section before proceeding. After the above pre-requisites are met, do the following to install the agent: 1. Unzip LogExpressAgentInstaller.zip on the machine where PowerCenter is running. 2. Set Execute permission on unzipped folder. Example, chmod -R 755 LogExpressAgentInstaller. 3. Go to the unzipped folder, such as, cd LogExpressAgentInstaller. 4. Run sh install.sh. 5. The Welcome screen is displayed. Ensure that the Informatica Log Express Server is already installed and all the port numbers you input are free and available. Press Enter to continue. Installing Agent 20

21 6. Provide Informatica Log Express Server configuration information - server host name and port number. Press Enter to continue. 7. The Informatica Log Express server will be pinged. In case the ping fails, verify the following: The Informatica Log Express server is already installed and is running. The Informatica Log Express server host and port provided are correct. Installing Agent 21

22 8. Provide the location where you would like to install the Log Express agent. Press Enter to continue. 9. Provide a port number on this host for the agent. Press Enter to continue. 10. If the port number is already in use by another process/service, the following would be displayed. Provide another port value to resolve the issue. Installing Agent 22

23 11. The pre-installation summary is displayed. Press Enter to continue. Installing Agent 23

24 The Informatica Log Express Agent would be installed. Installing Agent 24

25 C HAPTER 3 User Interface Login When you launch Informatica Log Express, the login screen is displayed. Enter the user name and password to access the application. Note: For first time login, use the username/ password as Administrator/Administrator. For non-administrator login, refer to the Configure User section in the Configuration chapter. Login 25

26 Home Page The home page consists of the following sections: Agents Navigator Agent Overview Actions Scenario Output Agents Navigator The left section of the home page lists all the agents. The agents are maintained under different domains. Log Express discovers new agents and associates them to the domain they belong to. If you configure one agent under a domain, Log Express applies the same configuration settings to all the other agents/nodes under that domain. Select an agent to view its properties or perform any action on it. Home Page 26

27 Agent Overview The right section of the home page displays all the details of the selected agent. It consists of the following: Agent Properties: User, port, operating system type, host, and URL. Product Properties: Product name, home directory, and output directory. Domain Properties: Domain name, domain host, and domain port. Note: The agent status is checked every 30 seconds and a message is displayed accordingly. For example, The agent is available message is displayed when the agent is up and running. Actions The Agent Navigator includes an Actions menu that allows you to perform various tasks for each of the agents. These tasks could be configuring the product on that agent, collecting agent log, or running a scenario to gather logs, such as logs for session crash, hang, etc. Home Page 27

28 Scenario Output When you perform an action on the agent, such as running a session crash scenario, the output of that scenario is uploaded on the Informatica FTP. The same output files can be viewed by clicking the Scenario Output button. The Scenario Output section displays the output for the various scenarios run and their corresponding information: Scenario Type Agent Name Product Type Time of scenario run TSFTP location where the output has been uploaded for Informatica Global Customer Support Time when output was uploaded on Informatica TSFTP File name, clicking on which allows you to download a local copy of the output Click the Actions menu to use the different options. Send to Support: Send the diagnostic data to Informatica Global Customer Support by selecting the corresponding check boxes and clicking the Send to Support option under Actions. Refer to the Send to Support section for more information. Send As Mail: Informatica Log Express Server allows you to share the collected diagnostic data with other users through . Select the corresponding check boxes and click Send as Mail option under Actions. Refer to the Send As Mail section for more information. Delete Output: Delete the diagnostic data by selecting the corresponding check boxes and clicking the delete option. Note: You can download the diagnostic data such as logs and exports (zipped together) by clicking the file name. Home Page 28

29 Send to Support To upload the files on Informatica FTP, do the following: 1. Select the appropriate check boxes and click Actions > Send to Support. 2. You would be prompted to provide the directory name where you wish to upload the files. Based on your input, a new directory would be created if it does not already exist. Provide the directory name and click OK. The selected files would be uploaded in the directory specified by you on Informatica FTP. A detailed confirmation message is displayed with the file name(s) and directory name. You may copy this message for your reference, it to Informatica Global Customer Support, or update it in the SR raised by you. Note: After the upload, the TSFTP location and time would be updated in the Scenario Output section. Filter Scenario Output You can narrow down the list of scenario outputs using the filter option available on this screen. Select the required scenario and click the filter icon on right. The relevant results would be displayed in the list. Home Page 29

30 You also have the option to enter the value based on which you wish to filter the data. For example, to view results for a specific agent, provide the agent name in the space available above the Agent column. You can follow the same approach for Product Type, Time, and File name. Click the Filter icon on the right to display the filtered results. You can also sort the scenario outputs in ascending/descending order using any of the columns listed on this screen, such as Scenario Type, Agent name, Product Type, Time, or File name. Note: By default, the outputs are sorted in the descending order of the date/time. Send As Mail Informatica Log Express Server allows you to share the collected diagnostic data with other users through . Note: Before sending an , ensure that you have configured the SMTP. Refer to Configure SMTP section under the Configuration chapter for more information. When you click Send as Mail option under the Actions menu, the following screen is displayed. Home Page 30

31 The SMTP Host name and Port are populated based on the information provided for the SMTP Configuration. Provide the sender s address and password along with the other details, such as recipient ID, subject, and message. Click Send to send the files. Home Page 31

32 C HAPTER 4 Configuration After installing Informatica Log Express, configure the following: Agent Product User Configure Agent On startup, the agent sends its details to the server to register. The details include the host and port where agent is listening, and environment variables like INFA_HOME. Informatica Log Express Server discovers new agents and associates them to the domain they belong to. If you configure one agent under a domain, Informatica Log Express Server applies the same configuration settings to all the other agents/nodes under that domain. No more configuration is required for the agent. Note: If required, you can delete an agent. To delete an agent, select the specific agent to be removed and click Actions > Remove Agent. The selected agent will be deleted. Configure Product Every product configuration requires a registered agent to be running on the same node as the product. To configure a product, do the following: 1. Select the agent in the left navigation to configure product for that agent. Click Actions > Configure Product... Configure Agent 32

33 The Product Configuration wizard is displayed. 2. Select the product, and provide the Agent Working Directory and Core File Directory. Note: The Core File Directory is the directory where Informatica processes dump core files. By default, the core file gets generated in the home directory of the executable. For example, in case of a session crash, the core file would be dumped in the INFA_HOME/server/bin directory. Log Express has the provision to configure multiple core file directories (comma-separated). This provides the ability to gather information from various locations. The Core File Directory can be changed using coreadm, which is a UNIX tool. Follow a core naming convention like core.<pid> so that the files are not overwritten. When running a scenario, you have the option to override the default core file directory provided at the product configuration step. 3. Click Next. Configure Product 33

34 4. The next screen displays the domain details. Informatica Log Express Server discovers and populates, by default, all domain details except the Domain Database Password and Domain Security Type. For Domain Security Type, you can select Native or LDAP. The following image shows the fields displayed when Native is selected: Configure Product 34

35 The LDAP based security configured in the Informatica Domain can be used here. If LDAP is selected as the Domain Security Type, then provide LDAP Security Name and the LDAP Domain User name. The domain Security Name is the LDAP configuration name and the Domain User is configured LDAP user name. Note: You would be prompted to test the connection before you can proceed. Click Test Connection to ensure that the connection is successful. Configure Product 35

36 5. Select the Repository and Model Repository Services to configure their database details. 6. Click Save. It is recommended that you test the connection before saving the details. Note: If required, you can delete a product. To delete the product configured on a particular agent, click Actions > Remove Product. The product will be deleted from that agent. This step will only delete the product configured on that agent and will not delete the agent. Configure Product 36

37 Configure User For uploading the troubleshooting data on Informatica FTP, you need to configure the My Support credentials. The default user is Administrator. To access Log Express as a non-administrator user, ensure that your user credentials have been added by the Administrator. Click the user name displayed on the top left of the Log Express application. Click Manage User. Administrator user As the Administrator, you have the option to add/delete users or manage their details, such as update username and passwords. The password for Administrator login can also be updated. To add a new user, do the following: 1. Click the Add button. 2. The User Configuration window appears. 3. Provide the following information: Log Express User Configuration: The user name and password to be used for accessing the Log Express application. My Support Credentials: The ID and password fields are the Informatica customer portal My Support (communities.informatica.com) user credentials. These credentials are used to upload files to the Informatica FTP site - TSFTP. Configure User 37

38 4. Click Save. The user would be added successfully. As the Administrator, you can also delete or edit the user details. Select the appropriate user and click the corresponding Delete or Edit icons as required. Note: You cannot delete the Administrator user. All other users can be deleted by the Administrator. Non-Administrator user To access Log Express as a non-administrator user, ensure that your user credentials have been added by the Administrator To configure a non-administrator user, click Manage User. You would be prompted to edit the configuration details. Edit the information as required: Log Express User Configuration: The user name and password to be used for accessing the Log Express application. You can only update your password. My Support Credentials: The ID and password fields are the Informatica customer portal My Support (communities.informatica.com) user credentials. These credentials are used to upload files to the Informatica FTP site - TSFTP. Configure User 38

39 Configure SMTP Informatica Log Express Server allows you to share the collected log files with other users through . To do the same, configure the SMTP the first time you log into Log Express. Provide the Host name and Port details and click Save. The SMTP information is prefetched for sending s. Configure SMTP 39

40 C HAPTER 5 Scenario Based Collections The errors and anomalies experienced during the Informatica product usage are categorized into different scenarios in Informatica Log Express. Every scenario requires collecting specific troubleshooting data. Based on the scenario, Informatica Log Express server delegates this collection to the appropriate agent. They are broadly classified into the following: PowerCenter Scenarios Data Quality Scenarios Generic Scenarios Note: Before running a scenario, ensure that conditions mentioned in Pre-requisites for Agent Installation section in Installation chapter are met. Scenario Run Overview In Informatica Log Express, you can run a scenario based on the issue you are facing. A scenario run broadly includes the following steps: 1. Select the appropriate product/agent where you see an issue, such as session crash, session hang, mapping crash, etc. 2. Click Actions. The drop-down menu displays the three types of scenarios: PowerCenter Scenario, Data Quality Scenario, or Generic Scenario. Scenario Run Overview 40

41 3. Mouse-over the appropriate scenario type. The various scenarios would be displayed. 4. Select the appropriate scenario, such as PowerCenter Session Crash. The corresponding scenario wizard would be displayed. 5. Provide the details related to that issue, such as Repository Service name, Integration Service name, Core File Directory, the date range during which the issue occurred, etc. Note: In certain scenarios, such as session or mapping crash, you will be prompted to select the session/mapping where the issue was observed. 6. The next screen displays a list of collectors, such as Domain logs, Node logs, Stack Trace, needed for troubleshooting this scenario. By default, all logs are selected. You may uncheck them if required. Note: For crash scenarios, selection of stack trace option opens a drop-down menu with the list of available core files. Select the appropriate file based on the scenario. Similarly, for hang scenarios, selection of stack trace option opens a drop-down menu with the list of PIDs. Select/add the appropriate PID based on the scenario. 7. After selecting the collectors, you would be prompted to send the output to Informatica Global Customer Support. You may also download the scenario output for your reference. 8. You would be prompted to provide the directory name where you wish to upload the files. Based on your input, a new directory would be created if it does not already exist. Provide the directory name and click OK. Scenario Run Overview 41

42 The selected files would be uploaded in the directory specified by you on Informatica TSFTP. A detailed confirmation message is displayed with the file name(s) and directory name. You may copy this message for your reference, it to Informatica Global Customer Support, or update it in the SR raised by you. PowerCenter Scenarios The various PowerCenter scenarios are as follows: Session Crash: PowerCenter session (pmdtm process) fails and a core might be generated Session Hang: PowerCenter session (pmdtm process) stops responding or there is no throughput Session Performance: PowerCenter session (pmdtm process) run is extremely slow and there is less throughput Integration Service Crash: PowerCenter Integration Service (pmserver process) crashes and a core might be generated Integration Service Hang: PowerCenter Integration Service (pmrepagent process) hangs or stops responding to client connections and job requests Repository Service Crash: PowerCenter Repository Service (pmrepagent process) crashes and a core might be generated Repository Service Hang: PowerCenter Repository Service (pmrepagent process) hangs or stops responding to client connections Session Crash This is a typical scenario where a session (pmdtm process) fails abruptly. Many a times, the failure is due to a crash accompanied by a core dump. To troubleshoot such issues, Informatica Global Customer Support requires a variety of logs and at times, additional information such as system information and metadata export. In case you are facing a session crash, do the following: 1. In Informatica Log Express, select the appropriate product/agent where you see session crash. 2. Click Actions > Run PowerCenter Scenarios > Session Crash. The Session Crash Scenario wizard is displayed. PowerCenter Scenarios 42

43 3. Select the appropriate Repository Service and Integration Service for the session. 4. The Core File Directory would be recognized from the Product Configuration. You may update it if required. Note: The Core File Directory is the directory where Informatica processes dump core files. By default, the core file gets generated in the home directory of the executable. For example, in case of a session crash, the core file would be dumped in the INFA_HOME/server/bin directory. Log Express has the provision to configure multiple core file directories (comma-separated). This provides the ability to gather information from various locations. The Core File Directory can be changed using coreadm, which is a UNIX tool. Follow a core naming convention like core.<pid> so that the files are not overwritten. 5. Provide the date range during which the crash occurred. 6. Informatica Log Express Server fetches all failed sessions based on the information provided. Select the appropriate session and click Next. PowerCenter Scenarios 43

44 PowerCenter Scenarios 44

45 7. The next screen displays a list of collectors needed for troubleshooting this scenario. By default, all logs are selected. You may uncheck them if required. However, it is recommended to select all check boxes unless suggested otherwise by Informatica Global Customer Support. This list includes node logs, domain logs, Repository Service logs, Integration Service logs, session logs, stack trace (in case of core dump), CSM, workflow export. Note: Selection of stack trace option opens a drop-down menu with the list of available core files. Select the appropriate file based on the scenario. 8. Click Run. You would be prompted to upload the scenario output to Informatica FTP. Note: Refer to Scenario Run Overview at the beginning of this chapter for more information on uploading the output on Informatica TSFTP. PowerCenter Scenarios 45

46 Filter List In case the list of sessions (or mappings) crashed (or hung) is huge, use the filter option to narrow down to the required entry. You can filter using the following approaches: Enter the value based on which you wish to filter the data. For example, to view results for a session, provide the session name in the space available above the Failed/Crashed Session column. You can follow the same approach for Start Time, and End Time. Click the Filter icon on the right to display the filtered results. PowerCenter Scenarios 46

47 You can also sort the scenario outputs in ascending/descending order using any of the columns listed on this screen. Click the column header to sort it in ascending/descending order. Note: By default, the list is sorted in the descending order of the End Time. Session Hang This is a scenario where a session (pmdtm process) stops responding or there is no throughput. To troubleshoot such issues, Informatica Global Customer Support requires a variety of logs and at times, additional information such as system information and metadata export. In case you are facing a session hang, do the following: 1. In Informatica Log Express, select the appropriate product/agent where you see session hang. 2. Click Actions > Run PowerCenter Scenario > Session Hang. The Session Hang Scenario wizard is displayed. 3. Select the appropriate Repository Service and Integration Service for the session. 4. Provide the date range during which the hang occurred. Click Next. PowerCenter Scenarios 47

48 5. Informatica Log Express Server fetches all sessions that stopped responding during the selected time period. Select the appropriate session and click Next. Note: In case the list of sessions is huge, use the filter option to narrow down to the required entry. For more information, refer to the Filter List section in PowerCenter Session Crash scenario. PowerCenter Scenarios 48

49 6. The next screen displays a list of collectors needed for troubleshooting this scenario. By default, all logs are selected. You may uncheck them if required. However, it is recommended to select all check boxes unless suggested otherwise by Informatica Global Customer Support. This list includes Node logs, Domain logs, Repository Service logs, Integration Service logs, Session logs, Stack Trace (in case of core dump), CSM, workflow export. Note: Selection of stack trace option opens a drop-down menu with the list of PIDs. Select/add the appropriate PID based on the scenario. 7. Click Run. You would be prompted to upload the scenario output to Informatica FTP. Note: Refer to Scenario Run Overview at the beginning of this chapter for more information on uploading the output on Informatica TSFTP. PowerCenter Scenarios 49

50 Session Performance This is a scenario where the session (pmdtm process) run is extremely slow and there is less throughput. To troubleshoot such issues, Informatica Global Customer Support requires a variety of logs and at times, additional information such as system information and metadata export. In case you are facing a slow session run, do the following: 1. In Informatica Log Express, select the appropriate product/agent where you see the slow performing session. 2. Click Actions > Run PowerCenter Scenarios > Session Performance. The Session Performance Scenario wizard is displayed. 3. Select the appropriate Repository Service and Integration Service for the session. 4. The Core File Directory would be recognized from the Product Configuration. You may update it if required. Note: The Core File Directory is the directory where Informatica processes dump core files. By default, the core file gets generated in the home directory of the executable. For example, in case of a session crash, the core file would be dumped in the INFA_HOME/server/bin directory. Log Express has the provision to configure multiple core file directories (comma-separated). This provides the ability to gather information from various locations. The Core File Directory can be changed using coreadm, which is a UNIX tool. Follow a core naming convention like core.<pid> so that the files are not overwritten. PowerCenter Scenarios 50

51 5. Provide the date range during which the crash occurred. 6. Informatica Log Express Server fetches all impacted sessions based on the information provided. Select the appropriate session and click Next. Note: In case the list of sessions is huge, use the filter option to narrow down to the required entry. For more information, refer to the Filter List section in PowerCenter Session Crash scenario. 7. The next screen displays a list of collectors needed for troubleshooting this scenario. By default, all logs are selected. You may uncheck them if required. However, it is recommended to select all check boxes unless suggested otherwise by Informatica Global Customer Support. This list includes session logs, CSM report, workflow export, and stack trace. PowerCenter Scenarios 51

52 Note: Selection of stack trace option opens a drop-down menu with the list of available core files. Select the appropriate file based on the scenario. 8. Click Run. You would be prompted to upload the scenario output to Informatica FTP. Note: Refer to Scenario Run Overview at the beginning of this chapter for more information on uploading the output on Informatica TSFTP. Integration Service Crash This is a scenario where the Integration Service (pmserver process) fails and a core might be generated. To troubleshoot such issues, Informatica Global Customer Support requires a variety of logs and at times, additional information such as system information and metadata export. In case you are facing an Integration Service crash, do the following: 1. In Informatica Log Express, select the appropriate product/agent where you see the Integration Service crash. 2. Click Actions > Run PowerCenter Scenarios > Integration Service Crash. The Integration Service Crash Scenario wizard is displayed. 3. Select the appropriate Repository Service and Integration Service. 4. The Core File Directory would be recognized from the Product Configuration. You may update it if required. PowerCenter Scenarios 52

53 Note: The Core File Directory is the directory where Informatica processes dump core files. By default, the core file gets generated in the home directory of the executable. For example, in case of a session crash, the core file would be dumped in the INFA_HOME/server/bin directory. Log Express has the provision to configure multiple core file directories (comma-separated). This provides the ability to gather information from various locations. The Core File Directory can be changed using coreadm, which is a UNIX tool. Follow a core naming convention like core.<pid> so that the files are not overwritten. 5. Provide the date range during which the crash occurred. 6. The next screen displays a list of collectors needed for troubleshooting this scenario. By default, all logs are selected. You may uncheck them if required. However, it is recommended to select all check boxes unless suggested otherwise by Informatica Global Customer Support. This list includes Node logs, Domain logs, Repository Service logs, Integration Service logs, Stack Trace, CSM Report. Note: Selection of stack trace option opens a drop-down menu with the list of available core files. Select the appropriate file based on the scenario. PowerCenter Scenarios 53

54 7. Click Run. You would be prompted to upload the scenario output to Informatica FTP. Note: Refer to Scenario Run Overview at the beginning of this chapter for more information on uploading the output on Informatica TSFTP. Integration Service Hang This is a scenario where the PowerCenter Integration Service (pmrepagent process) hangs or stops responding to client connections and job requests. To troubleshoot such issues, Informatica Global Customer Support requires a variety of logs and at times, additional information such as system information and metadata export. In case you are facing an Integration Service hang, do the following: 1. In Informatica Log Express, select the appropriate product/agent where you see the Integration Service hang. 2. Click Actions > Run PowerCenter Scenario > Integration Service Hang. The Integration Service Hang Scenario wizard is displayed. 3. Select the appropriate Repository Service and Integration Service. 4. Provide the date range during which the hang occurred. 5. The next screen displays a list of collectors needed for troubleshooting this scenario. By default, all logs are selected. You may uncheck them if required. However, it is recommended to select all check boxes unless suggested otherwise by Informatica Global Customer Support. This list includes Node logs, Domain logs, Repository Service logs, Integration Service logs, Stack Trace, and CSM Report. PowerCenter Scenarios 54

55 Note: Selection of stack trace option opens a drop-down menu with the list of PIDs. Select/add the appropriate PID based on the scenario. 6. Click Run. You would be prompted to upload the scenario output to Informatica FTP. Note: Refer to Scenario Run Overview at the beginning of this chapter for more information on uploading the output on Informatica TSFTP. Repository Service Crash This is a scenario where the PowerCenter Repository Service (pmrepagent process) crashes and a core might be generated. To troubleshoot such issues, Informatica Global Customer Support requires a variety of logs and at times, additional information such as system information and metadata export. In case you are facing a Repository Service crash, do the following: 1. In Informatica Log Express, select the appropriate product/agent where you see Repository Service crash. 2. Click Actions > Run PowerCenter Scenarios > Repository Crash. The Repository Service Crash Scenario wizard is displayed. 3. Select the appropriate Repository Service. 4. Provide the date range during which the crash occurred. PowerCenter Scenarios 55

56 5. The Core File Directory would be recognized from the Product Configuration. You may update it if required. Note: The Core File Directory is the directory where Informatica processes dump core files. By default, the core file gets generated in the home directory of the executable. For example, in case of a session crash, the core file would be dumped in the INFA_HOME/server/bin directory. Log Express has the provision to configure multiple core file directories (comma-separated). This provides the ability to gather information from various locations. The Core File Directory can be changed using coreadm, which is a UNIX tool. Follow a core naming convention like core.<pid> so that the files are not overwritten. 6. The next screen displays a list of collectors needed for troubleshooting this scenario. By default, all logs are selected. You may uncheck them if required. However, it is recommended to select all check boxes unless suggested otherwise by Informatica Global Customer Support. This list includes Node logs, Domain log, Repository Service logs, Integration Service logs, stack trace, and CSM Report. Note: Selection of stack trace option opens a drop-down menu with the list of available core files. Select the appropriate file based on the scenario. 7. Click Run. You would be prompted to upload the scenario output to Informatica FTP. Note: Refer to Scenario Run Overview at the beginning of this chapter for more information on uploading the output on Informatica TSFTP. PowerCenter Scenarios 56

57 Repository Service Hang This is a scenario where PowerCenter Repository Service (pmrepagent process) hangs or stops responding to client connections. To troubleshoot such issues, Informatica Global Customer Support requires a variety of logs and at times, additional information such as system information and metadata export. In case you are facing a Repository Service hang, do the following: 1. In Informatica Log Express, select the appropriate product/agent where you see the Repository Service hang. 2. Click Actions > Run PowerCenter Scenarios > Repository Service Hang. The Repository Service Hang Scenario wizard is displayed. 3. Select the appropriate Repository Service. 4. Provide the date range during which the hang occurred. 5. The next screen displays a list of collectors needed for troubleshooting this scenario. By default, all logs are selected. You may uncheck them if required. However, it is recommended to select all check boxes unless suggested otherwise by Informatica Global Customer Support. This list includes Node logs, Domain logs, Repository Service logs, Integration Service logs, Stack Trace (in case of core dump) and CSM Report. Note: Selection of stack trace option opens a drop-down menu with the list of PIDs. Select/add the appropriate PID based on the scenario. PowerCenter Scenarios 57

58 6. Click Run. You would be prompted to upload the scenario output to Informatica FTP. Note: Refer to Scenario Run Overview at the beginning of this chapter for more information on uploading the output on Informatica TSFTP. Data Quality Scenarios The various Data Quality scenarios are as follows: Mapping Crash: A mapping fails and a core might be generated Mapping Hang: A mapping stops responding to client connections and job requests Data Quality Profile Crash: Data Quality Profile Job or Data Integration Service (DIS) fails and a core might be generated Data Quality Profile Hang: Data Quality Profile or DIS stops responding to client connections and job requests Mapping Crash This is the scenario where a mapping fails and a core might be generated. To troubleshoot such issues, Informatica Global Customer Support requires a variety of logs and at times, additional information such as system information and metadata export. In case you are facing a mapping crash, do the following: 1. In Informatica Log Express, select the appropriate product/agent where you see the mapping crash. 2. Click Actions > Run Data Quality Scenarios > Mapping Crash. 3. In the drop-down menu, select the Mapping Crash scenario. The Mapping Crash Scenario wizard is displayed. Data Quality Scenarios 58

59 4. Select the Model Repository Service, Data Integration Service, and Analyst Service. 5. The Core File Directory would be recognized from the Product Configuration. You may update it if required. Note: The Core File Directory is the directory where Informatica processes dump core files. By default, the core file gets generated in the home directory of the executable. For example, in case of a session crash, the core file would be dumped in the INFA_HOME/server/bin directory. Log Express has the provision to configure multiple core file directories (comma-separated). This provides the ability to gather information from various locations. The Core File Directory can be changed using coreadm, which is a UNIX tool. Follow a core naming convention like core.<pid> so that the files are not overwritten. 6. Provide the date range during which the crash occurred. Data Quality Scenarios 59

60 7. Informatica Log Express Server fetches all impacted mappings based on the information provided. Select the appropriate mapping and click Next. Note: In case the list of sessions is huge, use the filter option to narrow down to the required entry. For more information, refer to the Filter List section in PowerCenter Session Crash scenario. 8. The next screen displays a list of collectors needed for troubleshooting this scenario. By default, all logs are selected. You may uncheck them if required. However, it is recommended to select all check boxes unless suggested otherwise by Informatica Global Customer Support. This list includes Node logs, Domain logs, MRS logs, DIS logs, Mapping Export, Stack Trace (in case of core dump), and CSM. Note: Selection of stack trace option opens a drop-down menu with the list of available core files. Select the appropriate file based on the scenario. 9. Click Run. You would be prompted to upload the scenario output to Informatica FTP. Data Quality Scenarios 60

61 Note: Refer to Scenario Run Overview at the beginning of this chapter for more information on uploading the output on Informatica TSFTP. Mapping Hang This is the scenario where a mapping stops responding to client connections and job requests. To troubleshoot such issues, Informatica Global Customer Support requires a variety of logs and at times, additional information such as system information and metadata export. In case you are facing a mapping hang, do the following: 1. In Informatica Log Express, select the appropriate product/agent where you see the mapping hang. 2. Click Actions > Run Data Quality Scenarios > Mapping Hang. The Mapping Hang Scenario wizard is displayed. 3. Select the Model Repository Service, Data Integration Service, and Analyst Service. 4. Provide the date range during which the crash occurred. 5. Informatica Log Express Server fetches all impacted mappings based on the information provided. Select the appropriate mapping and click Next. Data Quality Scenarios 61

62 Note: In case the list of sessions is huge, use the filter option to narrow down to the required entry. For more information, refer to the Filter List section in PowerCenter Session Crash scenario. 6. The next screen displays a list of collectors needed for troubleshooting this scenario. By default, all logs are selected. You may uncheck them if required. However, it is recommended to select all check boxes unless suggested otherwise by Informatica Global Customer Support. This list includes Node logs, Domain logs, MRS logs, DIS logs, Mapping Export, Stack Trace (in case of core dump), and CSM. Note: Selection of stack trace option opens a drop-down menu with the list of PIDs. Select/add the appropriate PID based on the scenario. 7. Click Run. You would be prompted to upload the scenario output to Informatica FTP. Data Quality Scenarios 62

63 Note: Refer to Scenario Run Overview at the beginning of this chapter for more information on uploading the output on Informatica TSFTP. Data Quality Profile Crash This is the scenario where Data Quality Profile Job or Data Integration Service (DIS) fails and a core might be generated. To troubleshoot such issues, Informatica Global Customer Support requires a variety of logs and at times, additional information such as system information and metadata export. In case you are facing a profile crash, do the following: 1. In Informatica Log Express, select the appropriate product/agent where you see the crash. 2. Click Actions > Run Data Quality Scenarios > Data Quality Profile Crash. The Data Quality Profile Crash Scenario wizard is displayed. 3. Select the Model Repository Service, Data Integration Service, and Analyst Service. 4. The Core File Directory would be recognized from the Product Configuration. You may update it if required. Note: The Core File Directory is the directory where Informatica processes dump core files. By default, the core file gets generated in the home directory of the executable. For example, in case of a session crash, the core file would be dumped in the INFA_HOME/server/bin directory. Log Express has the provision to configure multiple core file directories (comma-separated). This provides the ability to gather information from various locations. The Core File Directory can be changed using coreadm, which is a UNIX tool. Follow a core naming convention like core.<pid> so that the files are not overwritten. 5. Provide the date range during which the crash occurred. 6. If you select the Profile Export option, you will be prompted to provide the profile configuration information - project name, profile name, and folder path. Data Quality Scenarios 63

64 7. The next screen displays a list of collectors needed for troubleshooting this scenario. By default, all logs are selected. You may uncheck them if required. However, it is recommended to select all check boxes unless suggested otherwise by Informatica Global Customer Support. This list includes Node logs, Domain logs, MRS logs, DIS logs, Analyst logs, Profiling logs, Profile Export, Stack Trace (in case of core dump), and CSM. Data Quality Scenarios 64

65 Note: Selection of stack trace option opens a drop-down menu with the list of available core files. Select the appropriate file based on the scenario. 8. Click Run. You would be prompted to upload the scenario output to Informatica FTP. Note: Refer to Scenario Run Overview at the beginning of this chapter for more information on uploading the output on Informatica TSFTP. Data Quality Profile Hang This is the scenario where Data Quality Profile or DIS stops responding to client connections and job requests. To troubleshoot such issues, Informatica Global Customer Support requires a variety of logs and at times, additional information such as system information and metadata export. In case you are facing a profile hang, do the following: 1. In Informatica Log Express, select the appropriate product/agent where you see session crash. 2. Click Actions > Run Data Quality Scenarios > Data Quality Profile Hang. The Profile Hang Scenario wizard is displayed. Data Quality Scenarios 65

66 3. Select the Model Repository Service, Data Integration Service, and Analyst Service. 4. Provide the date range during which the hang occurred. 5. If you select the Profile Export option, you will be prompted to provide the profile configuration information - project name, profile name, and folder path. 6. The next screen displays a list of collectors needed for troubleshooting this scenario. By default, all logs are selected. You may uncheck them if required. However, it is recommended to select all check boxes unless suggested otherwise by Informatica Global Customer Support. This list includes Node logs, Domain logs, MRS logs, DIS logs, Analyst logs, Profiling logs, Profile Export, Stack Trace (in case of core dump), and CSM. Data Quality Scenarios 66

67 Note: Selection of stack trace option opens a drop-down menu with the list of PIDs. Select/add the appropriate PID based on the scenario. 7. Click Run. You would be prompted to upload the scenario output to Informatica FTP. Note: Refer to Scenario Run Overview at the beginning of this chapter for more information on uploading the output on Informatica TSFTP. Data Quality Scenarios 67

68 Generic Scenarios The various generic scenarios are as follows: PowerCenter Repository Inconsistencies Create Domain Backup Generic Scenario PowerCenter Repository Inconsistencies This is a scenario where PowerCenter repository database has corrupted data, which could result in repository crash. To troubleshoot such issues, Informatica Global Customer Support requires a variety of logs and at times, additional information such as system information and metadata export. In case you are facing a repository corruption, do the following: 1. In Informatica Log Express, select the appropriate product/agent where you see the repository corruption. 2. Click Actions > Run Generic Scenarios > PowerCenter Repository Inconsistencies. The Repository Inconsistencies Scenario wizard is displayed. 3. Select the appropriate Repository Service. 4. Provide the date range during which the corruption occurred. Generic Scenarios 68

69 5. The next screen displays a list of collectors needed for troubleshooting this scenario. By default, all logs are selected. You may uncheck them if required. However, it is recommended to select all check boxes unless suggested otherwise by Informatica Global Customer Support. 6. Click Run. You would be prompted to upload the scenario output to Informatica FTP. Note: Refer to Scenario Run Overview at the beginning of this chapter for more information on uploading the output on Informatica TSFTP. Create Domain Backup This scenario is used for backing up the contents of the domain into a mrep file, which can be restored later. To back up the domain, do the following: 1. In Informatica Log Express, select the appropriate product/agent. 2. Click Actions > Run Generic Scenarios > Create Domain Backup. 3. The domain backup would be created. You would be prompted to upload the scenario output to Informatica FTP. Generic Scenarios 69

70 Note: Refer to Scenario Run Overview at the beginning of this chapter for more details. Generic Scenario There may be cases where you need to collect some troubleshooting data that may not fit into the above scenarios. Also in some cases, you may need to collect generic troubleshooting data that may be a super set. In such cases use the Generic scenario and select the collectors appropriately. Do the following: 1. In Informatica Log Express, select the appropriate product/agent. 2. Click Actions > Run Generic Scenarios > Generic. The Generic Scenario wizard is displayed. 3. The Core File Directory would be recognized from the Product Configuration. You may update it if required. Generic Scenarios 70

71 Note: The Core File Directory is the directory where Informatica processes dump core files. By default, the core file gets generated in the home directory of the executable. For example, in case of a session crash, the core file would be dumped in the INFA_HOME/server/bin directory. Log Express has the provision to configure multiple core file directories (comma-separated). This provides the ability to gather information from various locations. The Core File Directory can be changed using coreadm, which is a UNIX tool. Follow a core naming convention like core.<pid> so that the files are not overwritten. 4. Provide the date range and click Next. You would be prompted to select the logs to be uploaded. By default, logs for all the services configured on the domain would be selected. Also, you have the option to collect stack trace of a specific Process by providing its ID. 5. Click Run. You would be prompted to upload the scenario output to Informatica FTP. Note: Refer to Scenario Run Overview at the beginning of this chapter for more information on uploading the output on Informatica TSFTP. Generic Scenarios 71