DataStage "Connector Import Wizard" and "View data" in Oracle Connector fails with error "Failed to send the request to the handler: The agent at : 31531 is not available"

-

Problem(Abstract)

DataStage "Connector Import Wizard" and "View data" in Oracle Connector fails with error "Failed to send the request to the handler: The agent at <Engine Server>: 31531 is not available"

Cause

- Import metadata using "Connector Import Wizard" in DataStage designer client and/or "View data" from Connector stages in the DataStage job fails when the ASB port 31531 on Engine tier is blocked in a Multi-tier environment (Repository and Services tier resides on one server and Engine tier resides on another server)

- Because the "Connector Import Wizard" and "View data" request flow goes from DataStage Designer Client through ASB Agent to Connector Access Service to Connector Framework to Oracle Connector to Oracle database and then result flows back in-reverse order through all these items to GUI and/or repository (depending on the operation), so If ASB agent port on Engine tier is blocked then the "Connector Import Wizard" and "View data" request fails.


Diagnosing the problem

DataStage job runs successfully but "Connector Import Wizard" fails and "View data" using Connector stages fails. Then follow below steps to check whether ASB node port 31531 is blocked on Engine tier.

1). Open a DOS command window on your workstation.
2). Run " telnet <Engine tier hostname> 31531" and see if this returns successful telnet session or fails.
3). If telnet session fails with "Could not open connection to the host, on port 31531" message, this means then ASB port on Engine tier is blocked.

Resolving the problem

To open blocked port contact your UNIX Administrator or Network Administrator and request to open ASB port 31531 on the Engine tier and follow below steps to confirm whether port is opened or not and to test "Connector Import Wizard" and "View data" from DataStage designer client.

- After opening port 31531 on Engine tier repeat steps 1 and 2 to make sure the telnet session is successful.
- After successful telnet session connectivity, launch DataStage Designer client and test importing metadata using "Connector Import Wizard" and check "View data" from Connector stage.







Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more