Mapping Rule Fails with 'Failure During Child Login Attempt: Host is Bad' & ORA-3136 'Inbound Connection Timed Out'

Last updated on MAY 24, 2018

Applies to:

Symptoms

In Oracle Profitability Manager (PFT), when running a Rule Set containing many Mapping Rules, after several mapping rules run successfully but slower than normal, subsequent Mapping Rules fail and messages like the following are output to the View Log:

Current system time is 06-NOV-2013 17:26:31

*** FCFilterCondition: SqlStr returned: ((a.USER_DIM7_ID > 3070957 OR a.USER_DIM7_ID < 3070957) AND ((a.USER_DIM10_ID > 40501957 OR a.USER_DIM10_ID < 40501957) .........AND (((a.DATASET_CODE =15017)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =15006)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =15011)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =15012)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =17019)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =17020)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =17021)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =17022)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =17023)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =17024)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) ) AND (a.CREATED_BY_OBJECT_ID NOT IN(119430)) AND (a.LEDGER_ID = 3001)
Failure during child login attempt: Host is bad

[[[16101] User requested termination16074] User requested termination

16099] User requested termination
Within FCIoLedger::classicOutputMethodHandler::~classicOutputMethodHandler()
*** FCFilterCondition: SqlStr returned: ((a.USER_DIM7_ID > 3070957 OR a.USER_DIM7_ID < 3070957) AND ((a.USER_DIM10_ID > 40501957 OR a.USER_DIM10_ID < 40501957) ........... (((a.DATASET_CODE =15017)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =15006)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =15011)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =15012)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =17019)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =17020)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =17021)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =17022)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =17023)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) OR((a.DATASET_CODE =17024)and(a.CAL_PERIOD_ID =24565970000000000000101200100140)) ) AND (a.CREATED_BY_OBJECT_ID NOT IN(119095)) AND (a.LEDGER_ID = 3001)
Max Num Threads = 24
[[[[21609[[[[2160721618[[[[[2162821611] ] [[[[[21612] 21634] ] [] User requested termination216202161921616] ] User requested termination[[User requested termination216322162121624] 2163021633User requested termination]
User requested termination[[21613] ] 21623] User requested termination21629User requested termination21627] User requested termination] 21610] ] 21614User requested termination
User requested termination

21625User requested termination]
] User requested termination

The Oracle Database's alert log contains the following error at approximately the same time the Mapping Rules are run:

***********************************************************************

Fatal NI connect error 12170.

  VERSION INFORMATION:
TNS for Solaris: Version 11.2.0.2.0 - Production
Oracle Bequeath NT Protocol Adapter for Solaris: Version 11.2.0.2.0 - Production
TCP/IP NT Protocol Adapter for Solaris: Version 11.2.0.2.0 - Production
  Time: 06-NOV-2013 17:29:43
  Tracing not turned on.
  Tns error struct:
  ns main err code: 12535
  
TNS-12535: TNS:operation timed out
  ns secondary err code: 12606
  nt main err code: 0
  nt secondary err code: 0
  nt OS err code: 0
  Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=<server>)(PORT=<port>))
WARNING: inbound connection timed out (ORA-3136)

The remaining rules in the Rule Set fail.

However, the rules run normally when they are re-submitted a second time.

Cause