My Oracle Support Banner

Step 1 of BDA Mammoth Expansion Fails with "ERROR: <FQDN ASR Server> has 162 : CLOSED" (Doc ID 2476494.1)

Last updated on JANUARY 29, 2020

Applies to:

Big Data Appliance Integrated Software - Version 4.5.0 and later
Linux x86-64

Symptoms

NOTE: In the examples that follow, user details, table name, company name, email, hostnames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.

 

Step 1 of BDA Mammoth expansion fails with an error like:

...
ERROR: Error code 1 when executing checkSW.sh on host bdanode0x #Step 1#
ERROR: Error is : Software checks failed #Step 1#
ERROR: Errors executing checkSW.sh. Continuing anyway. #Step 1#
ERROR: Some server software failed
INFO: Successfully pinged ASR: <FQDN ASR Server>
ERROR: <FQDN ASR Server> has 162 : CLOSED
ERROR: Errors found verifying ASR setup requirements.
ERROR: Please disable ASR using the Configuration Generation Utility and regenerate the mammoth input configuration file.
ERROR: Use mammoth-config add asr later to configure ASR or
ERROR: Please fix the issues and re-run this step.
...


Using telnet to access the ASR server on port 162 fails as below: 

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.