Could not contact Service Manager FNDSM_EBSERPAPP2_R12ZAT


Unsuccessful in TNS ping of node EBSERPAPP2, error reported: Ping Timed Out.

Could not contact Service Manager FNDSM_EBSERPAPP2_R12ZAT. The TNS alias could not be located, the listener process on EBSERPAPP2 could not be contacted, or the listener failed to spawn the Service Manager process.


Cause: unable to telnet node2 from node1

[root@ebserpapp1 ~]# telnet ebserpapp2.nprdmt.nprd.oraclevcn.com 1646
Trying 10.203.2.144...
^C

[root@ebserpapp1 ~]# telnet ebserpapp1.nprdmt.nprd.oraclevcn.com 1646
Trying 10.203.2.78...
Connected to ebserpapp1.nprdmt.nprd.oraclevcn.com.
Escape character is '^]'.
^]
telnet> quit
Connection closed.

Solution:

enable ingress rule in Cloud console to enable access node2 from node1.



Comments

Post a Comment

Popular posts from this blog

adop UNEXPECTED Unable to find appltop_id for host ebsapp2 in database

error: Validating system setup.     Node registry is valid.     [UNEXPECTED]Unable to find appltop_id for host ebsapp2 in database     [UNEXPECTED]Unable to find appltop_id for host ebsapp2 in database cause: on node2  s_atName parameter value having wrong entryu on node1 grep -i s_atname $CONTEXT_FILE          <APPL_TOP_NAME oa_var="s_atName">AT_ebsapp1</APPL_TOP_NAME> [appr12prd@esbapp1:R12PRD:scripts] [appr12prd@ebsapp2:R12PRD:~] > grep -i s_atname $CONTEXT_FILE          <APPL_TOP_NAME oa_var="s_atName">ebsapp1</APPL_TOP_NAME>  === wrong entry on node2 , it should be AT_ebsapp1 reference: ADOP Phase=prepare Fails With the Error "[UNEXPECTED]Unable To Find Appltop_id For Host In Database" (Doc ID 2794402.1) Fix:  s_atName parameter value in node1 and node2 should be same as  AT_ebsapp1 as node2 is having wrong entry ,  updated it with correct value and...
Read more

adop failing ORA-06512: at line 2 (DBD ERROR: OCIStmtExecute)

Error: While running   Checking for existing adop sessions.     No pending session exists.     Starting new adop session.     [UNEXPECTED]Unable to find appltop_id for host ebsappprd2 in database  Statement Handler Error Code: 20010  Statement Handler Error Message: ORA-20010: No admin node found. Review and correct your configuration,                                contacting Oracle Support as needed. ORA-06512: at "APPS.AD_ZD_ADOP", line 3028 ORA-06512: at line 2 (DBD ERROR: OCIStmtExecute)  Reference of statement-handler is valid, not attempting database reconnect.  Failed to execute SQL statement:       begin          ad_zd_adop.INSERT_ADD_NODE_RECORDS;         end;  Error Message: ORA-20010: No admin node found. Review and correct your configuration,         ...
Read more