Error When Activating Polling For on premise DB Connector

(Doc ID 2365273.1)

Last updated on MARCH 02, 2018

Applies to:

Integration Cloud Service - Version 16.4.1 and later
Information in this document applies to any platform.

Symptoms

On : ICS, Technology Adapters ( SOAP, REST, FTP, File, DB, AQ etc)

Error when activating polling for DB  in ICS. In this case, SQL Server was used as DB.

ERROR
-----------------------
[2018-01-29T09:53:35.032-06:00] [AdminServer] [WARNING] [] [oracle.tip.adapter.sa.impl.inbound.JCAInboundHandler] [tid: Thread-47] [userId: ] [ecid: 41454d20-48a0-4ff6-aa24-404bb7570416-00000004,0] [APP: agent-webapp] Generic error.[[
JCA binding runtime error.
Cause: {0}.
Please inspect the diagnostic log to determine the reason, and if possible take corrective action.
BINDING.JCA-12600
Generic error.
JCA binding runtime error.
Cause: {0}.
Please inspect the diagnostic log to determine the reason, and if possible take corrective action.

at oracle.tip.adapter.sa.impl.inbound.JCABindingActivationAgent.activateEndpoint(JCABindingActivationAgent.java:427)
at oracle.tip.adapter.sa.impl.JCABindingServiceImpl.activate(JCABindingServiceImpl.java:151)
at oracle.tip.adapter.sa.impl.inbound.JCAInboundHandler.activate(JCAInboundHandler.java:285)
at oracle.cloud.cpi.agent.PostActivationCpiCommand.postActivationOperation(PostActivationCpiCommand.java:63)
at oracle.cloud.cpi.agent.PostActivationCpiCommand.doRequest(PostActivationCpiCommand.java:51)
at oracle.cloud.cpi.agent.PostActivationCpiCommand.execute(PostActivationCpiCommand.java:35)
at oracle.cloud.cpi.agent.CpiAgentImpl.execute(CpiAgentImpl.java:40)
at oracle.cloud.cpi.agent.framework.CpiCommandBus.execute(CpiCommandBus.java:27)
at oracle.cloud.cpi.agent.framework.CpiCommandBus.receive(CpiCommandBus.java:22)
at oracle.cloud.cpi.agent.transport.DistributedCpiCommandExecutorOmcs.received(DistributedCpiCommandExecutorOmcs.java:109)
at oracle.cloud.cpi.agent.transport.AQConsumer.run(AQConsumer.java:78)
at java.lang.Thread.run(Thread.java:745)
Caused by: BINDING.JCA-12517
Endpoint Activation Error.
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter sqlserverdatabase was unable to activate the endpoint :{UseLocalWorkManager=true, MaxRaiseSize=1, MarkReadColumn=RecordUpdateStatus, PollingInterval=10, DescriptorName=Source.UC_Dummy_Table_4_Integration_SB, MarkReadValue=Processed, MaxTransactionSize=1, PollingStrategy=LogicalDeletePollingStrategy, ReturnSingleResultSet=false, MappingsMetaDataURL=/opt/ics_hcm/agenthome/user_projects/domains/agent-domain/agent/data/SQL2ICSNEW_01/inbound/Source_REQUEST/Source_REQUEST-or-mappings.xml, QueryName=SourceSelect, NumberOfThreads=5} due to the following reason: BINDING.JCA-12532
Cannot set JCA WSDL Property.
Error while setting JCA WSDL Property.
Property setUseLocalWorkManager is not defined for oracle.tip.adapter.db.DBActivationSpec
Please verify the spelling of the property.

Please correct the reported issue and redeploy the BPEL process.

at oracle.tip.adapter.sa.impl.fw.jca.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:585)
at oracle.tip.adapter.sa.impl.inbound.JCABindingActivationAgent.activateEndpoint(JCABindingActivationAgent.java:423)
... 11 more
Caused by: BINDING.JCA-12532
Cannot set JCA WSDL Property.
Error while setting JCA WSDL Property.
Property setUseLocalWorkManager is not defined for oracle.tip.adapter.db.DBActivationSpec
Please verify the spelling of the property.

at oracle.tip.adapter.sa.impl.fw.wsdl.WSDLUtils.invokeSetMethod(WSDLUtils.java:853)
at oracle.tip.adapter.sa.impl.fw.wsdl.WSDLUtils.setCciSpecParameters(WSDLUtils.java:738)
at oracle.tip.adapter.sa.impl.fw.jca.AdapterFrameworkImpl.createActivationSpec(AdapterFrameworkImpl.java:1274)
at oracle.tip.adapter.sa.impl.fw.jca.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:446)
... 12 more

]]






STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create integration with SQL Server Connection and set up polling, click activate, enable tracing, the activation goes in wait mode
2. Further when integration is created, it cannot be activated due to above error.


Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms