Table of Contents


  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service REST API
  10. Data Integration Service Applications
  11. Data Privacy Management Service
  12. Enterprise Data Preparation Service
  13. Interactive Data Preparation Service
  14. Informatica Cluster Service
  15. Mass Ingestion Service
  16. Metadata Access Service
  17. Metadata Manager Service
  18. Model Repository Service
  19. PowerCenter Integration Service
  20. PowerCenter Integration Service Architecture
  21. High Availability for the PowerCenter Integration Service
  22. PowerCenter Repository Service
  23. PowerCenter Repository Management
  24. PowerExchange Listener Service
  25. PowerExchange Logger Service
  26. SAP BW Service
  27. Search Service
  28. System Services
  29. Test Data Manager Service
  30. Test Data Warehouse Service
  31. Web Services Hub
  32. Application Service Upgrade
  33. Appendix A: Application Service Databases
  34. Appendix B: Connecting to Databases from Windows
  35. Appendix C: Connecting to Databases from UNIX or Linux
  36. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Monitoring Interactive Data Preparation Service Node Status

Interactive Data Preparation Service
Node Status

You can troubleshoot by finding the state of the
Interactive Data Preparation Service
nodes in a grid at any given point in time.
To find the nodes of the service along with the state, connect to the Data Preparation repository and execute the following SQL query:
select node_id, node_ip, state, created_ts, node_port, isp_node_name from dp_physical node;
The state column shows the current state of the node service. It can be in any of the following states:
  • ACTIVE: The node is ready to take new user sessions.
  • SUSPECTED_UNREACHABLE: The node cannot accept new sessions as peer-check operation is failing on that node. The node might not be completely down as the server may recover after a brief period of high load.
To find the user to node assignment, connect to the Data Preparation repository and execute the following SQL query:
select login_id, node_ip, a.node_id, isp_node_name from dp_physical_node a, dp_user u, dp_user_to_node_map m where a.node_id = m.node_id and = m.user_id;