JDBC Connector - Datasource issue

Hi,
We have a datasource created in JDBC Connector in Visual Admin Services. The issue is whenever there is a connection failure due to network or the database system is restarted the JDBC datasource doesn't work and we get invalid connection in our application.We have to stop and restart the datasource through Visual Admin to make it work.
Is there any resolution that we dont have to restart the datasource manually in case of connection failure.
Appreciate your support

Hi,
I had same problems!
I only know of a workaround for JMS adapter which showed same issues after a MQ restart. There an option got introduced to "ping" the source / target to recreate the connection by a parameter to be set in the channel itself. I'm not sure this option is also available for JDBC channels...
Does anybody got news here?
Thanks,
Kai

Similar Messages

Starting JDBC Connector datasource service Automatically

Hi Members,
We have a custom development in webdynpro using ejb to access data from a oracle database (on a different server). we have created a JDBC Connecter datasource on the j2ee egine and defined a alias for the same.
when ever the oracle database is restarted for whatever reason, the datasource service stops and is not up when the database is up.
In order to restart the service Administrator has to go J2ee Admin and start explicitly. we would like to know of any mechanisim by which the service starts automatically when the database is up.
Thanking in Advance,
Regards
Vinay Rane

Gehakkafakka: Finally: usr\sap\J2E\JC00\j2ee\admin
Tata Robin, points added
When I installed it on my windows server it indeed asked for a J2EE user and password, cant remember it exactly but i kept it default.
It made a windows user j2eadm which i use to log into windows. But now, where do i enter this password? In my http://localhost:50000/irj/portal or what? I really cant figure out where to find the tool itself.
In desperate need of your less-stressfull moments,
HW
Message was edited by:
Hans Wassink

JDBC Connector in NetWeaver Dev Studio WebAS

Hello,
I am attempting to deploy a web module that utilizes a WebAS datasource for an external Oracle database. I expect to add a JDBC Connector leveraging the Oracle JDBC driver. I have been unable to deploy the Oracle datasource.
I receive the stack trace below whenever I attempt to Start the datasource. I find many posts asking about this error but never have I found an answer as to the cause or resolution. OSS Note 751175 describes this as a classloader problem with connectors but it does not offer any repair method that works with this problem (in my case).
I've had this problem with NetWeaver SP7 and it remains with SP10.
Does anyone have explanation? Can I expect to test such applications in NetWeaver's standalone WebAS?
Best regards,
Gary
ava.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4114150:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "CMR".
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1836)

Hello Benny,
One of my co-workers resolved the problem which boiled down to driver configuration confusion. Here's what we learned:
No SDA component was required though this was a good exercise for us to go through.
The driver (JAR or ZIP) file can be added simply using the Visual Administrator JDBC Connector Runtime tab.
We were not able to activate more than one type of datasource at a time (feature, bug or something else?)
The following configurations start okay:
**Starts***
Driver: Oracle's classes12.zip
JDBC Version: 1.x
Driver class: oracle.jdbc.driver.OracleDriver
Database URL: jdbc:oracle:thin:@host:port:instance
User&Password specified.
**Starts***
Driver: Oracle's 1.4 ojdbc14.jar
JDBC Version: 2.0
Driver class: oracle.jdbc.pool.OracleDataSourceFactory
Datasource type: ConnectionPoolDataSource
CPDS Classname: oracle.jdbc.pool.OracleConnectionPoolDataSource
Additional properties:
URL = jdbc:oracle:thin:@host:port:instance
User = xxxx
Password = yyyyy
**Will not start but the failure is expected***
Driver: Oracle's classes12.zip
JDBC Version: 1.x
Driver class: oracle.jdbc.pool.OracleConnectionPoolDataSource
Database URL: jdbc:oracle:thin:@host:port:instance
User&Password specified.
We do need to run multiple datasources using Oracle and Sybase so I'm hoping the issue we encountered is simply configuration issues again.
I appreciate your time and feedback Benny!
Best regards,
Gary

Can't connect to external Oracle DB with JDBC connector

Hello guys,
I had failed to connect to connect external Oracle via JDBC connector .
Could you please help me to resolve the problem ?
Backgroud:
We need to connect the external Oracle DB with JDBC connector, because BI need to connect to the target Oracle. If the JDBC connector suceed, BI will create a UD which use the datasource
we create in Visual admin to connect to the external Oracle DB.
Environment:
Our EP version is NW04S SP17 , OS is AIX .
The target Oracle DB version is 10g(10.1.0.2.0, 64bi).
Configuration procedure :
1. Import Oracle driver "ojdbc14.jar" and create new driver which named "Oracle " under
JDBC Connector ->Run time ->Driver in Visual Admin.
2. Create datasource "Mydatasource" under JDBC Connector ->Run time ->Data Source,
Name : Mydatasource
Driver Name : Oracle
JDBC version: 2.0(with XA support)
JDBC compliant:
Object Factory :oracle.jdbc.pool.OracleDataSourceFactory
DataSource Type: ConnectionPoolDataSource
*CPDS class name :oracle.jdbc.pool.OracleConnectionPoolDataSource
Additional:
Additional Properties:
DatabaseName:LPAR8TEST
DriverName:oracle.jdbc.OracleDriver
Password: *****
PortNumber:1521
ServerName: 10.1.16.208
URL :jdbc:oracel:[email protected]:1521:LPAR8TEST
User:IMPL
Connectoin Pool:
Initial Connectons: 1                                         Expiration: (check)
Maximum Connections: 25                                  Connection Lifetime :600
Maximum time wait of connection : 60                  Cleanup Thread : 200
Default Connectoin Isolaton :Default
SQL Engine:
Open SQL
3.Create Connector :
   Copy the standard connector :SDK_JDBC to SDK_JDBC_Oracle,
Resource Adopter:
Loader References:
Add "libray:Oracle" .
Managed Connection Factory:
Configuration Property:
DriverName:oracle.jdbc.OracleDriver
Password: ****
User:IMPL
URL: jdbc:oracle:[email protected]:1521:LPAR8TEST
All fo my configuration had been listed.
And I had created JCO RFC : JT-BIDEV_PORTAL_BD1 , and created RFC connection with SM59 in BI.
Please give me some suggesiton.
Thanks.
Louis

When I try to start datasoure "Mydatasource" , it display error, error detail:
java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "sap.com/Mydatasource". [id = StartupError]
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:608)
Caused by: java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 3128050:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot start DataSource "CGNPC".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1549)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: java.sql.SQLException: Invalid Oracle URL specified: OracleDataSource.makeURL
     at com.sap.engine.services.dbpool.spi.CPManagedConnectionFactoryImpl.createManagedConnection(CPManagedConnectionFactoryImpl.java:198)
Caused by: java.sql.SQLException: Invalid Oracle URL specified: OracleDataSource.makeURL
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 3128050:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot start DataSource "Mydatasource".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1549)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: java.sql.SQLException: Invalid Oracle URL specified: OracleDataSource.makeURL
     at com.sap.engine.services.dbpool.spi.CPManagedConnectionFactoryImpl.createManagedConnection(CPManagedConnectionFactoryImpl.java:198)
Caused by: java.sql.SQLException: Invalid Oracle URL specified: OracleDataSource.makeURL
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
          u2026.
When I try to test JDBC with URL : http://jt-pldev:50000/TestJDBC_Web/TestJDBCPage.jsp,
First I choose connection name "SDK_JDBC_Oracle" .
If I click "Check Connectons", it display :
500   Internal Server Error
SAP J2EE Engine/7.00
Application error occurred during request processing.
Details:
java.lang.NoClassDefFoundError: com.sap.ip.bi.sdk.dac.connector.odbo.impl.Connection (initialization failure)
Exception id: [001A64A86F2C006B000004C40010302A000469C74E86A096]
If I click "Slecton Connection", it display:
500   Internal Server Error
SAP J2EE Engine/7.00
Application error occurred during request processing.
Details:
com.sap.engine.frame.core.load.SAPNoClassDefFoundError: javax.resource.Referenceable
Exception id: [001A64A86F2C0063000004C00010302A000469C74FA2BB59]

JDBC-ORACLE CONNECTIVITY ISSUE WITYH OCI8 DRIVER using oracle 11g client..

JDBC-ORACLE CONNECTIVITY ISSUE WITYH OCI8 DRIVER using oracle 11g client..
I am getting below error when i m trying to access oracle db using oracle 11g client. It works with earlier oracle client versions. how do i resolve this. is there any issue with version of ojdbc6.jar that i am using??? I cant use thin driver since its an old application for which i dont have source files.
Apr 6, 2013 1:00:59 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet jsp threw exception
java.lang.UnsatisfiedLinkError: no ocijdbc9 in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1682)
at java.lang.Runtime.loadLibrary0(Runtime.java:822)
at java.lang.System.loadLibrary(System.java:992)
at oracle.jdbc.oci8.OCIDBAccess.logon(OCIDBAccess.java:262)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:346)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at PettyCash.SysDate.getSysSubSys(SysDate.java:232)
at org.apache.jsp.PettyCash.index_jsp._jspService(org.apache.jsp.PettyCash.index_jsp:186)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
Code is as follow for reference
import oracle.jdbc.driver.*;
DriverManager.registerDriver(new oracle.jdbc.OracleDriver());
conn = DriverManager.getConnection ("jdbc:oracle:oci8:@" + database,db_user, db_pass);
eNVIRONMENT VARIABLES set are as follows:
classpath
C:\Program Files\apache-tomcat-5.5.12\common\lib\servlet-api.jar;C:\Program Files\apache-tomcat-5.5.12\webapps\ROOT\WEB-INF\lib\classes12.jar;C:\Program Files\apache-tomcat-5.5.12\webapps\ROOT\WEB-INF\lib\ojdbc6.jar;
JAVA_HOME
C:\Program Files\Java\jdk1.5.0_04
PATH
C:\Program Files\Java\jdk1.5.0_04\bin
ORACLE_HOME
D:\Oracle11\product\11.2.0\client_1\BIN

Apr 8, 2013 5:24:06 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet jsp threw exception
java.lang.NullPointerException
     at org.apache.jsp.abc.index_jsp._jspService(org.apache.jsp.abc.index_jsp:280)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:868)
     at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:663)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Thread.java:595)

Portal Test Connection Failed for JDBC Connector

Hi,
We are trying to create a JDBC system in EP to connect SQL Server 2005 database. Our aim is to build a model in VC using data services from SQL Server 2005.
We deployed the Driver file sqljdbc.jar and connection was successful when tested by creating a data source in Visual Administrator-> JDBC Connector
We have created a system in EP with user mapping type (admin,user) and user mapping also done for system alias with the SQL Server administrator user id and password. UME is maintained in ABAP Stack. When we try for test connection with the system created in EP for JDBC connection, the system throws an error message like Connection failed. Make sure user mapping is set correctly and all connection properties are correct
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the back end application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure user mapping is set correctly and all connection properties are correct.
The following are the URL and driver class name:
URL: jdbc:sqlserver://<host_name>:1433;DatabaseName=db_ name
Driver class name: com.microsoft.sqlserver.jdbc.SQLServerDriver
Is there any other setting to be maintained in the Visual Administrator or in the Portal?
Kindly let us know any clue to overcome this issue.
Quick response highly appreciated.
Regards
Saravanan.r

Hi Saravanan and Sathish,
not sure how far you got with this. I had the same problem or at least a very similar one with access to MS SQL Server 2005 and solved it. I followed essentially very similar steps with a couple of minor twists:
1) copied the sqljdbc.jar file to the storyboard server and set the classpath environment variable to point to it.
2) I did not create a data source, just created a new driver "SQLServer".
3) Under Connector Container I cloned SDK_JDBC as "SDK_SSQL".
4) The Visual Composer property vc.bi.sqlEditor Enabled should be set to true for you to be able the SQL Editor in the Data Service in VC.
In the portal I created a system of type BI_JDBC from a template.
The connection url and driver class were as in the thread:
URL: jdbc:sqlserver:ipaddress:1433;DatabaseName=name
Driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
ConnectionFActoryClass as above under 3.
User rights: admin,user
The user mapping to the system alias should be as described.
This should allow you to use the data service in VC to access SQL Server tables. If access to stored procedures (sometimes quite useful) is required, this would need to utilise the p9sqlserver.jar file already on the server.
Best Regards
Felix Logemann

JDBC Connector : pool gets depleted

Hi,
we are currently working with SAP EP 6.0 SP2 and trying out some development work with the connector framework.
We are writing a component which uses the CF to retrieve information from a Microsoft SQL Server 2000.
The portal component works, we are able to retrieve the information from the DB, but after some time the request times out.
We monitored the connections for a while both on the J2EE platform and on the backend database and came to this conclusion : apparently each request - even by the very same user looking at the very same component, just but pressing the refresh button in the browser window - creates a new connection in the pool managed by the connector framework.
- result : the number of successful views of the components is equal to the number of Maximum Connections defined for the JDBC connector on the J2EE platform.
In our code we are using the close() method on the IConnection interface as indicated in the documentation that comes with the PDK.
Is this a known problem OR are we doing something wrong here ?
We suspect that there is something wrong in the implementation of the JDBC connector, which isn't handling the close method correctly.

In more general terms this issue raises the following questions :
- how does the Connector framework manage the pool of JDBC connections ?
- the fact that our component at each request (even after a refresh in the browser) causes the CF to create a new connection, does that mean we are writing our code incorrectly so that each request is indeed considered to be a unique and in need of its own database connection ?
We have tried to avoid as much reason as possible for the CF to generate a new connection : e.g. we have set up user mapping so that all users access the database with the same account. This should already eliminate the requirement to have a separate for each user. => in general : what are the different ways by which to control the generation of connections by the Connector Framework, for the JDBC Connector in particular ?
- So far we are writing the code accessing the SQL server straight into a JSPDynpage. Am I wrong in thinking that this is allowed. Although we intend to write a portal service as a wrapper for all database interaction in a later stage, for the simple exercises now we are directly using the CF service API in the portal components.
- by what algorithms does CF determine whether to take a connection from the pool or to create a new connection to the back-end system.
- Am I wrong in thinking that connection pool management is no longer the task of the developer when using CF ?

OIM 11g AD Connector Provisioning Issue

Hi Guys
i have this problem which just came from nowhere as everything used to work before. Please see below the stacktrace. I have to increase the timeout values on my datasources etc but it keeps failing. My database and everything is in good condition but this problem keeps occurring.
Running ISADAM
Target Class = java.lang.String
Running Get Attribute Map
Running AD Create User
Running ISADAM
Target Class = java.lang.String
Running GETUSESSL
Target Class = java.lang.String
Running CheckUserStatus
Running GETATTRIBUTEHASH
Target Class = com.thortech.xl.util.adapters.tcUtilHashTableOperations
Running Set User Attribute
Running Set User Expiration Date
Running ISADAM
Target Class = java.lang.String
Running CheckUserStatus
Running GETPWDEXPIRESATTRIBUTEHASH
Target Class = com.thortech.xl.util.adapters.tcUtilHashTableOperations
Running Set Pwd Expires Attribute False
Running GETATTRIBUTEHASH
Target Class = com.thortech.xl.util.adapters.tcUtilHashTableOperations
Running Set User Attributes
<May 16, 2011 9:23:53 AM WAT> <Warning> <XELLERATE.DATABASE> <BEA-000000> <Exception while trying to get the connection count : 0>
<May 16, 2011 9:24:14 AM WAT> <Warning> <XELLERATE.DATABASE> <BEA-000000> <Exception while trying to get the connection count : 1>
<May 16, 2011 9:24:35 AM WAT> <Warning> <XELLERATE.DATABASE> <BEA-000000> <Exception while trying to get the connection count : 2>
<May 16, 2011 9:25:17 AM WAT> <Error> <XELLERATE.DATABASE> <BEA-000000> <Class/Method: DirectDB/getConnection encounter some problems: Error while retrieving database connection.Please check for the follwoing
Database srever is running.
Datasource configuration settings are correct.
java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 29 seconds
BEA1-6F7499AA29E6D0A2F599
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1609)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1496)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:439)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355)
at oracle.iam.platform.utils.vo.OIMDataSource.getConnection(OIMDataSource.java:57)
at com.thortech.xl.util.DirectDB.getConnection(DirectDB.java:200)
at com.thortech.xl.util.DirectDB.getConnection(DirectDB.java:148)
at com.thortech.xl.dataaccess.tcDataBase.getConnection(tcDataBase.java:3198)
at com.thortech.xl.dataaccess.tcDataBase.readPartialStatement(tcDataBase.java:705)
at com.thortech.xl.dataobj.tcDataBase.readPartialStatement(tcDataBase.java:271)
at com.thortech.xl.dataaccess.tcDataSet.executeQuery(tcDataSet.java:935)
at com.thortech.xl.dataobj.tcDataSet.executeQuery(tcDataSet.java:1523)
at com.thortech.xl.dataaccess.tcDataSet.executeQuery(tcDataSet.java:903)
at com.thortech.xl.dataobj.tcDataSet.executeQuery(tcDataSet.java:1490)
at com.thortech.xl.cache.CacheUtil.getSetCachedQuery(CacheUtil.java:250)
at com.thortech.xl.dataobj.tcDataObj.eventPostUpdate(tcDataObj.java:2262)
at com.thortech.xl.dataobj.tcScheduleItem.eventPostUpdate(tcScheduleItem.java:742)
at com.thortech.xl.dataobj.tcDataObj.update(tcDataObj.java:662)
at com.thortech.xl.dataobj.tcDataObj.save(tcDataObj.java:508)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.updateSchItem(tcAdpEvent.java:188)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.finalizeProcessAdapter(tcAdpEvent.java:3529)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.finalizeAdapter(tcAdpEvent.java:3711)
at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpADCSCREATEUSER.implementation(adpADCSCREATEUSER.java:105)
at com.thortech.xl.client.events.tcBaseEvent.run(tcBaseEvent.java:196)
at com.thortech.xl.dataobj.tcDataObj.runEvent(tcDataObj.java:2492)
at com.thortech.xl.dataobj.tcScheduleItem.runMilestoneEvent(tcScheduleItem.java:2936)
at com.thortech.xl.dataobj.tcScheduleItem.eventPostInsert(tcScheduleItem.java:554)
at com.thortech.xl.dataobj.tcDataObj.insert(tcDataObj.java:602)
at com.thortech.xl.dataobj.tcDataObj.save(tcDataObj.java:474)
at com.thortech.xl.ejb.beansimpl.tcProvisioningOperationsBean.retryTasks(tcProvisioningOperationsBean.java:3704)
at Thor.API.Operations.tcProvisioningOperationsIntfEJB.retryTasksx(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy482.retryTasksx(Unknown Source)
at Thor.API.Operations.tcProvisioningOperationsIntfEJB_4xftoh_tcProvisioningOperationsIntfRemoteImpl.retryTasksx(tcProvisioningOperationsIntfEJB_4xftoh_tcProvisioningOperationsIntfRemoteImpl.java:2683)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:84)
at $Proxy160.retryTasksx(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)
at $Proxy481.retryTasksx(Unknown Source)
at Thor.API.Operations.tcProvisioningOperationsIntfDelegate.retryTasks(Unknown Source)
at com.thortech.xl.webclient.actions.ResourceProfileProvisioningTasksAction.retryTasks(ResourceProfileProvisioningTasksAction.java:698)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:269)
at com.thortech.xl.webclient.actions.tcLookupDispatchAction.execute(tcLookupDispatchAction.java:133)
at com.thortech.xl.webclient.actions.tcActionBase.execute(tcActionBase.java:894)
at com.thortech.xl.webclient.actions.tcAction.execute(tcAction.java:213)
at org.apache.struts.chain.commands.servlet.ExecuteAction.execute(ExecuteAction.java:58)
at org.apache.struts.chain.commands.AbstractExecuteAction.execute(AbstractExecuteAction.java:67)
at org.apache.struts.chain.commands.ActionCommandBase.execute(ActionCommandBase.java:51)
at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:191)
at org.apache.commons.chain.generic.LookupCommand.execute(LookupCommand.java:305)
at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:191)
at org.apache.struts.chain.ComposableRequestProcessor.process(ComposableRequestProcessor.java:283)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:462)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.thortech.xl.webclient.security.CSRFFilter.doFilter(CSRFFilter.java:61)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.iam.platform.auth.web.PwdMgmtNavigationFilter.doFilter(PwdMgmtNavigationFilter.java:115)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.iam.platform.auth.web.OIMAuthContextFilter.doFilter(OIMAuthContextFilter.java:100)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.transaction.TimedOutException: Transaction timed out after 29 seconds
BEA1-6F7499AA29E6D0A2F599
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1607)
... 111 more
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1515)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:439)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355)
at oracle.iam.platform.utils.vo.OIMDataSource.getConnection(OIMDataSource.java:57)
at com.thortech.xl.util.DirectDB.getConnection(DirectDB.java:200)
at com.thortech.xl.util.DirectDB.getConnection(DirectDB.java:148)
at com.thortech.xl.dataaccess.tcDataBase.getConnection(tcDataBase.java:3198)
at com.thortech.xl.dataaccess.tcDataBase.readPartialStatement(tcDataBase.java:705)
at com.thortech.xl.dataobj.tcDataBase.readPartialStatement(tcDataBase.java:271)
at com.thortech.xl.dataaccess.tcDataSet.executeQuery(tcDataSet.java:935)
at com.thortech.xl.dataobj.tcDataSet.executeQuery(tcDataSet.java:1523)
at com.thortech.xl.dataaccess.tcDataSet.executeQuery(tcDataSet.java:903)
at com.thortech.xl.dataobj.tcDataSet.executeQuery(tcDataSet.java:1490)
at com.thortech.xl.cache.CacheUtil.getSetCachedQuery(CacheUtil.java:250)
at com.thortech.xl.dataobj.tcDataObj.eventPostUpdate(tcDataObj.java:2262)
at com.thortech.xl.dataobj.tcScheduleItem.eventPostUpdate(tcScheduleItem.java:742)
at com.thortech.xl.dataobj.tcDataObj.update(tcDataObj.java:662)
at com.thortech.xl.dataobj.tcDataObj.save(tcDataObj.java:508)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.updateSchItem(tcAdpEvent.java:188)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.finalizeProcessAdapter(tcAdpEvent.java:3529)
at com.thortech.xl.adapterfactory.events.tcAdpEvent.finalizeAdapter(tcAdpEvent.java:3711)
at com.thortech.xl.adapterGlue.ScheduleItemEvents.adpADCSCREATEUSER.implementation(adpADCSCREATEUSER.java:105)
at com.thortech.xl.client.events.tcBaseEvent.run(tcBaseEvent.java:196)
at com.thortech.xl.dataobj.tcDataObj.runEvent(tcDataObj.java:2492)
at com.thortech.xl.dataobj.tcScheduleItem.runMilestoneEvent(tcScheduleItem.java:2936)
at com.thortech.xl.dataobj.tcScheduleItem.eventPostInsert(tcScheduleItem.java:554)
at com.thortech.xl.dataobj.tcDataObj.insert(tcDataObj.java:602)
at com.thortech.xl.dataobj.tcDataObj.save(tcDataObj.java:474)
at com.thortech.xl.ejb.beansimpl.tcProvisioningOperationsBean.retryTasks(tcProvisioningOperationsBean.java:3704)
at Thor.API.Operations.tcProvisioningOperationsIntfEJB.retryTasksx(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy482.retryTasksx(Unknown Source)

Hi Rajiv
I tried that..but eventually the error comes occurs.
The problem occurs when the connector executes Set User Attributes task. Im not sure what exactly it is setting that causes and where i can look to investigate this.
Any ideas?

EP7 JDBC connector integration to Oracle 8i database

Hello,
We are planning to use the EP7 JDBC connector to integrate with an Oracle database version 8.1.7.0. Are there any issues with integrating with this version of Oracle?
Thanks
Rebecca

Hi,
I would rather suggest you to go with Oracle 10g because of incompatibility issues.I am not sure whether 8i will work smoothly or not but for safer side go with 10g
Regards,
Ameya

From Steve Zeng: collector/jdbc connector won't start

Hi,
when i develop a database collector to collect bussiness database
logs about oracle for our customer , i use JDBC to connect to remote
oracle database, after i add database collector / jdbc connector /
database event source in SCC, i found i can not startup any of these
plugins, why? can database collector debug? the following codes is my
collector codes, additions, can anyone provide me a detail step by step
guide for database collector?
sqlquery.base
SELECT TOP %d * FROM ts_querybillsigned_log WHERE REQUEST_TM > %s
release.js
Collector.prototype.initialize = function() {
this.PARSER.getOffsetData = function(input) {
if (typeof input.RXMap != "undefined") {
return input.RXMap.REQUEST_TM;
conn.addParser(this.PARSER.getOffsetData);
return true;
Collector.prototype.cleanup = function() {
return true;
Connector.prototype.sendQuery = function() {
return true;
Record.prototype.preParse = function(e) {
if (this.CONNECTION_ERROR != null || typeof this.RXMap == "undefined")
{ return false; }
if (this.CONNECTION_METHOD == "DATABASE") {
for (var field in this.RXMap) {
this[field] = this.RXMap[field];
return true;
Record.prototype.parse = function(e) {
this.iuid = this.LOG_ID;
this.cv30 = this.METHODNAME;
this.cv31 = this.CLIENTNAME;
this.cv32 = this.CLIENTMAC;
this.cv33 = this.CLIENTIP;
this.cv34 = this.QUERYTYPE;
this.cv35 = this.SIGNEDTYPE;
var detstring =
this.RXMap.REQUEST_TM.replace(/(\d+)\/(\d+)\/(\d{4})\s(\S+)/, "$1/$2/$3
$4 GMT");
var dt = new Date(detstring);
e.setDeviceEventTime(dt);
return true;
Record.prototype.normalize = function(e) {
instance.SEND_EVENT =true;
return true;
Record.prototype.postParse = function(e) {
return true;
Record.prototype.reply = function(e) {
return true;
DCorlette
DCorlette's Profile: https://forums.netiq.com/member.php?userid=323
View this thread: https://forums.netiq.com/showthread.php?t=50302

Hi Steve,
I believe you've gotten closer to tracking down your issue, but there
are a couple style issues here I thought I'd comment on for general
consumption.
1) Your Collector will issue a query against the database, then it will
return a Record object. Each column in the database is mapped to the
RXMap object within that Record, in the form 'rec.RXMap.METHODNAME',
'rec.RXMap.CLIENTIP', etc. Since 'parse()' is a member function of
Record, 'rec' in this case is simply 'this'.
2) You then proceed to copy all of those fields from
this.RXMap.something to this.something, and then you proceed to copy
several fields from this.something to
this.somethingelsethatlookslikeasentinelfield. All of this is completely
unnecessary.
3) As long as you don't have to do any further processing on the values
in the source data (as with REQUEST_TM), you can skip everything in
preParse() and all of the this.* = this.* stuff in parse(), and simply
put entries like this in Rec2Evt.map:
iuid,RXMap.LOG_ID
cv30,RXMap.METHODNAME
cv31,RXMAP.CLIENTNAME
The Collector will automatically copy the information from the fields on
the RHS of Rec2Evt.map into the Sentinel Event fields on the LHS of
Rec2Evt.map.
Thus your entire Collector can be boiled down to this:
Collector.prototype.initialize = function() {
this.PARSER.getOffsetData = function(input) {
if (typeof input.RXMap != "undefined") {
return input.RXMap.REQUEST_TM;
conn.addParser(this.PARSER.getOffsetData);
return true;
Record.prototype.parse = function(e) {
var dt = new Date(this.RXMap.REQUEST_TM.substr(0,
this.RXMap.REQUEST_TM.length-2));
e.setDeviceEventTime(dt);
return true;
DCorlette
DCorlette's Profile: https://forums.netiq.com/member.php?userid=323
View this thread: https://forums.netiq.com/showthread.php?t=50302

JDBC Connector service in visual administrator

Hi All,
JDBC Connector service in visual administrator is not getting start or stopped.
I checked in Visual admiistrator ,then in JDBC Connector. On right click to JDBC Connector, Start or stop options are disabled.
It may be because of wrong configuration,please provide me the solution for this or provide me the configuration settings for JDBC Connector, so that i could recheck.Please tell how to start JDBC Connector from visual administrator services.
Points will be awarded.
Thanks & Regards,
Aman.

Hi Aman,
> i am also not able to start/stop data sources that i have created manually
On such datasources, for each one there is one .xml entry (the DS definition file)and below that, the datasource settings can be reached. If you mark the first one - the xml definition file - you get a blank screen right-hand, but at the same time, the "Stop" button (tooltip: "Stop Selected Standalone Application"; or the corresponding "Start" button, depending on the DS state) gets clickable.
This does not hold for the preconfigured default DS (which also has no xml entry).
Hope it helps
Detlev

Visual Admin - JDBC connector

Hi
Can anyone help me in configuring JDBC Connector -> Data source for Oracle.
Regards,
Murali.

Hi,
Here are the steps,
1. Create a driver (say, refer to it as "ORACLE"), and include the classes12.zip file in it.
2. Create a DataSource ("ORACLEDS") and configure it like this:
a. Add an alias ("ALIAS")
b. Driver Name = ORACLE
c. JDBC Version = 2.0 (with XA support)
d. Object Factory =
e. DataSource Type = XADataSource
f. XADS Classname = oracle.jdbc.xa.client.OracleXADataSource
g. In the additional properties pane, add 3 properties:
i. Password = ~PWD to your Oracle server~
ii. User = ~Username to your Oracle server~
iii. URL = jdbc:oracle:thin:@~IP:PORT:ALIAS~
h. SQL Engine = Vendor SQL
Regards
Srinivasan T

About jdbc connector service

Hi experts,
I create a new datasource to connect to the database mysql,when I click the button"Execute" on the DB Initialization tab,everything is OK.But several hours later, an exception occurs"Error occured when ececuting init statement".So I click the button"Execute" again,the above exception disappears.Please tell me why.It's urgent.Thanks

Hai,
Check the user password are changed or not in the mysql side which mentioned in the jdbc connector configuration.
Thanks and Regards,

JDBC Connector and pooling problems. Should be ConnectionPoolDataSource ?

Ciao all,
I am testing the JDBC Connector by Sun.
As you know, such JDBC connector is a JCA connector which can be used to
wrap a JDBC Driver or a JDBC Data Source or a JDBC
ConnectionPoolDataSource into a JCA connector.
Such JDBC Connector exposes to the client component the usual DataSource
interface, so that an application that was developed using a DataSource
can be easily migrated to a JCA enabled application: the application in fact will use the JDBC connector as if it was a DataSource, without
knowing that actually it is a JCA connector.
Here is my problem: the JCA architecture provides a pool. Therefore, I'd like the JDBC Connector to appear to the client as a
ConnectionPoolDataSource rather than a simple DataSource.
In fact, I have an application that performs a JNDI lookup to retrieve a JDBC data source. Then, if the obtained data source is instance of ConnectionPoolDataSource then the applications will use the SQL Connection and will closes it to release it back to the pool.
But if the data source is instance of DataSource, then the application
will retrieve a SQL connection, will use it, and will keep it in its own pool in order to reuse the SQL connection for better performance.
Now, if such application works with either a DataSource or a ConnectionPoolDataSource everything works properly, but when it works
with the JDBC Connector it fails: the JDBC Connector in fact appears as
a simple DataSource without pooling, so the application keeps the
obtained SQL connections in its own pool. But actually, the JDBC
Connector is a JCA connector which has a pool too, so the SQL connection
is kept in two pools and as a consequence, the JDBC Connector pool invalidates or destroy the connection in its pool, and the application, which is unaware, keeps in its pool a reference to an invalid connection, which leads to a SQLException at runtime.
So my question is: don't you think that the JDBC Connector should implement ConnectionPoolDataSource rather then DataSource, since it is a
JCA connector that offers pool services ?
And if so, is there a way to submit this question to someone working for Sun ?
Thank you for your time.
Gian Maria Romanato.

You can send your comments and feedbacks to [email protected]

BI - JDBC connector for remote database.

Hi,
I am trying to use my portal oracle database in VC applications. I have successfully connected to the database using JDBC connector as well as BI-JDBC connector. However when I try to use this BI-JDBC system in SQL editor I cannot see any tables. I have created JDBC and BI-JDBC system objects in the portal and the connection test is successful for both the systems.
I am using BI-JDBC connector so that I can see the tables and write select queries which I can use in VC applications. Using JDBC connector I can see only the stored procedures. So tried using BI-JDBC connector.
Is there anyway I can see the tables and views in the oracle database in the VC applications.
Thanks in advance.
Aamod.

Hi,
The DB user which I am using, can query the database from SQL PLUS. So he can see the tables and everything. But when the same user is used for mapping with portal user the tables cannot be seen.
When I select the system in VC and click on "Browse Table Catalog" I get the following structure.
BI-JDBC
|- 0
|- 1.
And below 1 theres nothing. When I select "Tables" and search *, it says "Search returned no result".
Please advice.
Regards,
Aamod.

JDBC Connector - Datasource issue

Similar Messages

Maybe you are looking for