Table of Contents

Search

  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. Enterprise Data Preparation Service
  12. Interactive Data Preparation Service
  13. Informatica Cluster Service
  14. Mass Ingestion Service
  15. Metadata Access Service
  16. Metadata Manager Service
  17. Model Repository Service
  18. PowerCenter Integration Service
  19. PowerCenter Integration Service Architecture
  20. High Availability for the PowerCenter Integration Service
  21. PowerCenter Repository Service
  22. PowerCenter Repository Management
  23. PowerExchange Listener Service
  24. PowerExchange Logger Service
  25. SAP BW Service
  26. Search Service
  27. System Services
  28. Test Data Manager Service
  29. Test Data Warehouse Service
  30. Web Services Hub
  31. Application Service Upgrade
  32. Application Service Databases
  33. Connecting to Databases from Windows
  34. Connecting to Databases from UNIX or Linux
  35. Updating the DynamicSections Parameter of a DB2 Database

Monitoring Interactive Data Preparation Service Node Status

Monitoring
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 u.id = m.user_id;