JDBC to JDBC Scenerio

Dear All,
i want to do one JDBC to JDBC scenario in which I want to update one table in MSAccess by taking data from the other table stored in MSAccess. Plz tell me the parameters which I have to maintain for this scenerio in Integration Directory & Repository. Also plz tell shuld I have to write any SQL Query for that & if yes then where I have to give that query. Also, plz tell me the good weblog for this scenario.
Waiting for ur valuable replies,
reg,
nishu

Hi,
In your sender JDBC adapter , you can give a JOIN select query.
Like,
select table1.col1,table1.col2,table2.col3 from table1,table2 where table1.col1=table2.col1 and table2.col4 = '1'
<i> Also there is something called Document Namespace, so what we have to specify there.</i>
You will create your Sender JDBC Datattype under a Namespace. GIve the DocumentNamespace value as this Namespace and Document Name as the Datatype Name.
<i>Also, what will be the structure for the Sender JDBC Data Type.</i>
For query above,
<i><DT_SORUCEDATATYPE>
<row>  <b>0 to UB</b>
<col1>  </col1>
<col2> </col2>
<col3> </col3>
</row>
</DT_SOURCEDATATYPE></i>
All this info is available on http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/content.htm
Please read the same for all info you need.
Regards,
Bhavesh

Similar Messages

  • JDBC Scenerio.

    hi guruz,
    when we do Configuration steps in Integration Depository for communication channel.(whether file 2 jdbc or jdbc to file).
    how can i will know the database connection parameter like
    driver name
    connection name
    user name
    password
    i am making txt file to jdbc(MS Access db).
    i want to update one table in to MS access from txt file data.
    how can i know the db connection parameter.
    pls help me
    warm regards.

    HI Pawan,
    Initially you should get installed the required drivers in your XI server by the basis people.Then get the connection details, user Id and password from them.
    Please refer the blog of Jdbc to Jdbc scenario in which MS access db is used.
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/jdbcTOJDBC
    In the same way you can do your scenario(File to Jdbc or Jdbc to file)
    I hope this helps you
    Regards,
    Pradeep

  • Error in http-jdbc

    with reference to blog
    /people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
    i completed http to jdbc scenerio
    but in moni i got this error
    com.sap.aii.af.ra.ms.api.DeliveryException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'pra' (structure 'recordset'): java.sql.SQLException: FATAL ERROR document format: structure 'recordset', no key element found</SAP:AdditionalText>
    can any body post suggestions,
    thanks & regards
    sandeep

    hai bhavesh, with reference to u r mesage , i uncheck the key mandatory in jdbc receiver adapter.
    now i got some different error i.e
    com.sap.aii.af.ra.ms.api.DeliveryException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'pra' (structure 'recordset'): java.sql.SQLException: [Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 1
    my jdbc request data type is as follows.
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn://http2db" targetNamespace="urn://http2db">
         <xsd:element name="jdbc_req_mt" type="jdbc_req_dt" />
         <xsd:complexType name="jdbc_req_dt">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   40e3cd4020b611dcb6da0014221c4454
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="recordset" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             726c80600b4311dcc762fe4aac121c42
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:complexType>
                             <xsd:sequence>
                                  <xsd:element name="pra">
                                       <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            726c80610b4311dca1c0fe4aac121c42
                                            </xsd:appinfo>
                                       </xsd:annotation>
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element name="access">
                                                      <xsd:annotation>
                                                           <xsd:appinfo source="http://sap.com/xi/TextID">
                                                           726c80630b4311dc8cccfe4aac121c42
                                                           </xsd:appinfo>
                                                      </xsd:annotation>
                                                      <xsd:complexType>
                                                           <xsd:sequence>
                                                                <xsd:element name="lifnr" type="xsd:string" minOccurs="0">
                                                                     <xsd:annotation>
                                                                          <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                          726c80640b4311dc9f7bfe4aac121c42
                                                                          </xsd:appinfo>
                                                                     </xsd:annotation>
                                                                </xsd:element>
                                                                <xsd:element name="name1" type="xsd:string" minOccurs="0">
                                                                     <xsd:annotation>
                                                                          <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                          726c80650b4311dcb353fe4aac121c42
                                                                          </xsd:appinfo>
                                                                     </xsd:annotation>
                                                                </xsd:element>
                                                                <xsd:element name="ort01" type="xsd:string" minOccurs="0">
                                                                     <xsd:annotation>
                                                                          <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                          726c80660b4311dcb603fe4aac121c42
                                                                          </xsd:appinfo>
                                                                     </xsd:annotation>
                                                                </xsd:element>
                                                                <xsd:element name="key">
                                                                     <xsd:annotation>
                                                                          <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                          09a635201e4011dcb3cafa21ac121c48
                                                                          </xsd:appinfo>
                                                                     </xsd:annotation>
                                                                     <xsd:complexType>
                                                                          <xsd:sequence>
                                                                               <xsd:element name="lifnr" type="xsd:string" minOccurs="0">
                                                                                    <xsd:annotation>
                                                                                         <xsd:appinfo source="http://sap.com/xi/TextID">
                                                                                         09a635211e4011dccfa0fa21ac121c48
                                                                                         </xsd:appinfo>
                                                                                    </xsd:annotation>
                                                                               </xsd:element>
                                                                          </xsd:sequence>
                                                                     </xsd:complexType>
                                                                </xsd:element>
                                                           </xsd:sequence>
                                                      </xsd:complexType>
                                                 </xsd:element>
                                            </xsd:sequence>
                                            <xsd:attribute name="action" type="xsd:string">
                                                 <xsd:annotation>
                                                      <xsd:appinfo source="http://sap.com/xi/TextID">
                                                      83dac9b01f2f11dcc0f7ee74ac121b94
                                                      </xsd:appinfo>
                                                 </xsd:annotation>
                                            </xsd:attribute>
                                       </xsd:complexType>
                                  </xsd:element>
                             </xsd:sequence>
                        </xsd:complexType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>
    plz help me regarding this.

  • Can I get information on JDBC to JDBC Using BPM

    Hi @SAPXI
    Can I get information on JDBC to JDBC Using BPM
    Thanks
    Rao

    hi
    look into this u ll get the answer
    JDBC to JDBC Scenerio
    regards
    kish
    reward if found useful

  • Problem when trying the Stored Procedures in JDBC receiver side

    Hi,
    I am facing some problem when i am trying to configure a scenario in the receiver side of JDBC adpater.
    We have never got stored procedures to work as messages go in 'Delivering'   status always. It's as if control never gets back to the adapter engine after the stored procedure call is made by the JDBC adapter. Then I went to checkt in the IE where the message has successfuly sent. Then I went to check
    in AE where the message is in "Delivering" state for long time.
    So checked the Default trace File and Thread dumps.
    In Thread dumps, i found a strange thing like one thread is hanging on condition wait at the below location :
      at java/lang/StringCoding.getEncoder(StringCoding.java:331(Compiled Code))
      at java/lang/StringCoding.encode(StringCoding.java:472(Compiled Code))
      at java/lang/String.getBytes(String.java:651(Compiled Code))
      at com/sap/aii/adapter/jdbc/SAXHandler.constructResponseStream(xml2sql.java:841(Compiled Code))
      at com/sap/aii/adapter/jdbc/SAXHandler.SQLcallStmt(xml2sql.java:988)
    Can you please help me in solving this issue as it is very critical to me ?
    Thanks,
    Prakash.

    Dear Prakash,
       There are number of reasons for SAX error. May be structure is not well defined, statement is not written correctly. These following links help you to solve your issue.
         SQL Queries(JDBC sendor CC)
         Oracle DB - XI - SQL DB
         JDBC Scenerio.
    Regards,
    JP.

  • RFC TO JDBC adapter

    Hi ,
            i am working on RFC to JDBC scenerio.
    SENDER: RFC
    RECEIVER:JDBC
    when i am sending message from RFC my receiver CC is in eror.it shows this erro.
    Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection to URL 'jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//172.25.086\home\iqxadm\xifiles\mohittest\sender\Student_Database.mdb,Uid=iqxadm;Pwd=india123;': java.lang.NullPointerException
    please help.

    Hi Mohit,
    The CC parameters are  as follow:
    JDBC Driver: jdbc.odbc.JdbcOdbcDriver
    Connection: jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=
    xxxxxx\xxxxx\TestCon.mdb
    your access database url is too long (this don't harm but first check it in shorter path).
    Check this  :
    /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
    Regards
    Laxmi Bhushan
    Edited by: laxmi bhushan on Jun 24, 2010 3:06 PM

  • Scenerio without business system

    Hi guruz,
    how many  type of scenerio we can create without business system and business service.
    like example file to jdbc scenerio ,at reciver side jdbc adapter is there . we can give all the parameters in adapters configuration(like db name ,connection string,driver name ,server address etc) .  please correct me if  iam wrong .so what is the need of business system .
    OR is it possible to do like this or not?
    help me.
    warm regards.

    hi,
    in case you want to connect to any database system, the JDBC adapter is used.When you want to read or insert/update data into database you should use the jdbc adapter . Also when you want to do the lookup into data base table from UDF( user defined function) you should use jdbc adapter .
    For mode details on jdbc adapter refer the following link .
    /people/saravanakumar.kuppusamy2/blog/2005/01/19/rdbms-system-integration-using-xi-30-jdbc-senderreceiver-adapter
    for more ref: http://help.sap.com/saphelp_nw04/helpdata/en/22/b4d13b633f7748b4d34f3191529946/content.htm
    When you want to read or insert/update data into database you should use the jdbc adapter . Also when you want to do the lookup into data base table from UDF( user defined function) you should use jdbc adapter .
    For mode details on jdbc adapter refer the following link .
    /people/saravanakumar.kuppusamy2/blog/2005/01/19/rdbms-system-integration-using-xi-30-jdbc-senderreceiver-adapter
    We use this adapter to connect database systems using the JDBC driver. We need to deploy JDBC driver Deploy JDBC Driver using the link
    http://help.sap.com/saphelp_nw04/helpdata/en/80/4f34c587f05048adee640f4c346417/frameset.htm
    U will find all the details including how to configure sender JDBC adapter + receiver JDBC adapter:
    http://help.sap.com/saphelp_nw04/helpdata/en/e2/cb610b230c9c4cb4b800989196b63a/frameset.htm
    U can Start your hands on with:
    FILE to JDBC Adapter using SAP XI 3.0-
    /people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
    Thanks,
    Vijaya.

  • Sender JDBC adapter: duplicate data sent

    Hi experts,
    The scenerio is XI is polling the Data from source system using JDBC  sender adapter. But the duplicate data is being sent to target system. I have check the chaneel configuaration and it is as follows:
    Polling Intervals(secs) = 3600
    and schedulling for the channel in RWB is set as: Daily at ......AM for 2 hours
    as per my understanding the here the adpater is polling the data for one hour and again it starts polling for another one hour which is set in secheduling.
    If I set the Availability planing as Daily at ......AM for 1 hour then problem can be resolved.
    Please advise.
    thanks,
    Regards,
    Mohan

    This could be resolved if you can add a field in the DB table like 'ReadFlag'.And your sql statement should have a check on this field.
    You can ask someone(who can actually make changes in the Database) to add the field in the Table.
    Please refer this blog for more understanding
    /people/yining.mao/blog/2006/09/13/tips-and-tutorial-for-sender-jdbc-adapter

  • ABAP client proxy With Receiver JDBC Adapter

    Hello Experts,
    I am working on a scenerio ABAP client proxy With Receiver JDBC Adapter.
    The client proxy program will fetch the master data related to equipment in plant maintenance module and  will update the sql database through Receiver JDBC Adapter .
    my requirement is if the equipement is created in sap then the  scheduled job has to trigger the client proxy program and send the message with status 'created'  to sql data base.
    if the equipment is modified in sap then the scheduled job has to trigger the client proxy program and send the message with status 'modify' to sql data base.
    please let me know how can i write the logic/code for this scenerio in client proxy program.
    Tables for equipment master i am using  is EQUI and fields are   ERDAT and AEDAT which is created date and modified date.
    fields for scheduling start date is tbtcp-sdldate.
    Thanks in advance.
    Ram.

    Hello Ram,
       Here you can check if updated date field is not empty then send status as created and if this field is not blank then send status as modified record.
    Monica

  • JDBC Receiver Sync

    Hi,
    I configured RFC -> JDBC(MS-SQL) sync scenario according to documentation and blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3928. [original link is broken] [original link is broken] [original link is broken] [original link is broken]
    Since I did not get any response I looked at the trace and found
    <SAP:ProcessingMode><b><u>asynchronous</u></b></SAP:ProcessingMode>
    Does anyone know what could be the problem?
    How can a sync scenario in the IR/ID appear as an A-Sync during runtime?
    Cheers,

    Hi,
    >> How can a sync scenario in the IR/ID appear as an A-Sync during runtime?
    To my knowledge it is not Possible.
    Can you check whether you have selected the right Message Interface with the Option synchronous and also check which Message Interface you have selected in the Interface mapping of the particular scenerio where you are facing the issue.
    Mean time try the SLD cache refresh
    To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
    Regards
    Agasthuri Doss

  • Upgrade 10G to use 10G thin jdbc drivers- OCI

    This is wierd...
    If I upgrade 10G app server to use the 10G thin JDBC drivers, and set up a data source to use the thin drivers, is there any way that I could score a[b] ORA-01010 invalid OCI operation error when I'm not using an OCI driver?
    Anyone else seen this...again, it makes no sense...

    You can not and should not use JDK 1.2 with 8i drivers.
    If you want to use JDK 1.2 drivers, download the 8.1.6 SDK
    from external site.
    Please, please, please READ the FAQ at www.oracle.com/java/jdbc
    before posting
    Premal Mehta (guest) wrote:
    : Hi,
    : Sorry for multiple posting. Previous posting has incomplete
    : information. Here's the whole scenerio...
    : I have Oracle 8i installed on my server. I have downloaded
    : JDBC drivers for Oracle 8i from Oracle site. When I try to run
    a
    : sample example from the demo files given, I get a Windows
    : internal Error "Exception: Access Violation (0xc0000005),
    : Address: 0x6ee0fb83". I am using Oracle 8i on Win NT 4.0 with
    : SP4, IIS4.0 with 128 MB RAM.
    : Also, I am trying to use OCI8 JDBC drivers with JDK 1.2. The
    : classpath is set for classes111.zip files.
    : I am unable to run applets with JDBC also. On using thin
    : drivers, it gives "SO Exception" error.
    : I have tried many options but it dosent seem to work.
    Please
    : help as this is very urgent.
    Oracle Technology Network
    http://technet.oracle.com
    null

  • Cannot assign an empty string to a parameter with JDBC type VARCHAR

    Hi,
    I am seeing the aforementioned error in the logs. I am guessing its happening whenever I am starting an agent instance in PCo. Can somebody explain whats going on?
    Regards,
    Chanti.
    Heres the complete detail from logs -
    Log Record Details   
    Message: Unable to retreive path for , com.sap.sql.log.OpenSQLException: Failed to set the parameter 1 of the statement >>SELECT ID, PARENTID, FULLPATH, CREATED, CREATEDBY, MODIFIED, MODIFIEDBY, REMOTEPATH, CHECKEDOUTBY FROM XMII_PATHS WHERE FULLPATH =  ?  <<: Cannot assign an empty string to a parameter with JDBC type >>VARCHAR<<.
    Date: 2010-03-12
    Time: 11:32:37:435
    Category: com.sap.xmii.system.FileManager
    Location: com.sap.xmii.system.FileManager
    Application: sap.com/xappsxmiiear

    Sounds like a UI browsing bug (when no path is selected from a catalog tree folder browser) - I would suggest logging a support ticket so that it can be addressed.

  • JDBC Lookup - Import table data from a different schema in same DB

    Hi XI Experts,
    We are facing an issue while importing a Database table into the external definition in PI 7.1.
    The details are as below:
    I have configured user 'A' in PI communication channel to access the database. But the table that I want to access is present in schema "B". Due to this, I am unable to view the table that I have to import in the list available.
    In other words, I am trying to access a table present in a different schema in the same database. Please note that my user has been given all the required permissions to access different schema. Even then, I am unable to access the table in different schema.
    Kindly provide your valuable suggestions as to how I can import table which is present in another schema but in the same Database.
    Regards,
    Subbu

    If you are using PI 7.1, then you can do JDBC Lookup to import JDBC meta data (table structures from DB). Configure a jdbc receiver communication channel where you specify username and password which has permission to access schema A and Schema B of database. Specify database name in the connection string. Then you might have access to import both schema.
    Please refer these links
    SAP PI 7.1 Mapping Enhancements Series: Graphical Support for JDBC and RFC Lookups
    How to use JDBC Lookup in PI 7.1 ?

  • Error while creating a JDBC connection to Oracle 11g using WLS 6.1

    Hi
    I am trying to connect to Oracle 11g database on Weblogic 6.1 server.
    First of all i would like to know if this is compatible?
    The environement that i have is this
    1. JDK 1.3
    2. Database 11g is on remote system
    3. Oracle client on my local system ( Connecting to the 11g DB through the client works fine)
    4. Weblogic server 6.1
    5. Currently the application is connected to Oracle 10g DB and working fine(We are attempting to move it to 11g)
    Below are the steps that i followed to create the connection:
    1. Made an entry for the datasource in config.xml under <WLS_DOMAIN>/config folder as below
    <JDBCConnectionPool DriverName="oracle.jdbc.driver.OracleDriver"
    MaxCapacity="4" Name="CADConnectionPool"
    Properties="user=abc_proxy;password=proxy_abc;dll=ocijdbc8;protocol=thin"
    RefreshMinutes="5" ShrinkPeriodMinutes="10" Targets="CAsvr"
    TestConnectionsOnRelease="true" TestConnectionsOnReserve="true"
    TestTableName="dual" URL="jdbc:oracle:thin:@gen11t-ora.db.lab.xyz.com:1530:GEN11T"/>
    2. Restarted the server.
    3. Ran the application and get the following error on the server console:
    <Aug 22, 2011 12:39:42 AM CDT> <Error> <JDBC> <Cannot startup connection pool "C
    ADConnectionPool" weblogic.common.ResourceException:
    Could not create pool connection. The DBMS driver exception was:
    java.lang.ArrayIndexOutOfBoundsException
    at oracle.security.o3logon.C0.r(C0)
    at oracle.security.o3logon.C0.l(C0)
    at oracle.security.o3logon.C1.c(C1)
    at oracle.security.o3logon.O3LoginClientHelper.getEPasswd(O3LoginClientH
    elper)
    at oracle.jdbc.ttc7.O3log.<init>(O3log.java:289)
    at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:251)
    at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:246)
    at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.ja
    va:365)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
    nectionEnvFactory.java:193)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
    nectionEnvFactory.java:134)
    at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
    cator.java:705)
    at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
    ava:282)
    at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
    ava:650)
    at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:360)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:285)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:239)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:199)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:360)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    57)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    25)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy31.updateDeployments(Unknown Source)
    at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
    yments(ServerMBean_CachingStub.java:2977)
    at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
    er(ApplicationManager.java:372)
    at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
    nManager.java:160)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:360)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    57)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    25)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy42.start(Unknown Source)
    at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
    .start(ApplicationManagerMBean_CachingStub.java:480)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
    at weblogic.management.Admin.finish(Admin.java:644)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
    at weblogic.Server.main(Server.java:35)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
    nectionEnvFactory.java:209)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
    nectionEnvFactory.java:134)
    at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
    cator.java:705)
    at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
    ava:282)
    at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
    ava:650)
    at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:360)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:285)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:239)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:199)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:360)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    57)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    25)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy31.updateDeployments(Unknown Source)
    at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
    yments(ServerMBean_CachingStub.java:2977)
    at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
    er(ApplicationManager.java:372)
    at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
    nManager.java:160)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:360)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    57)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    25)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy42.start(Unknown Source)
    at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
    .start(ApplicationManagerMBean_CachingStub.java:480)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
    at weblogic.management.Admin.finish(Admin.java:644)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
    at weblogic.Server.main(Server.java:35)
    Can't load scjd12.dll, file not found java.library.path=C:\jdk1.3.1_11\bin;.;C:\WINDOWS\system32;C:\WINDOWS;.\bin;C:\P
    rogram Files\Lotus\Notes\Data;C:\Program Files\Lotus\Notes;C:\Program Files\Java
    \jre1.5.0_17\bin;C:\Program Files\Java\j2re1.4.2_06\bin;C:\Oracle\bin;C:\Program
    Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\sys
    tem32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\nls;C:\WINDOWS\sys
    tem32\nls\ENGLISH;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\Rational
    \common;C:\Program Files\Rational\ClearCase\bin;C:\apache-ant-1.6.5\bin;C:\jdk1.
    3.1_11\bin;C:\Program Files\Citrix\ICAService\;C:\Program Files\Citrix\System32\
    ;Z:.
    <Aug 22, 2011 12:38:06 AM CDT> <Info> <JDBC> <Sleeping in createResource()>
    <Aug 22, 2011 12:38:07 AM CDT> <Error> <JDBC> <Cannot startup connection pool "c
    ispool" weblogic.common.ResourceException:
    Could not load 'com.neon.jdbc.Driver
    If this is a type-4 JDBC driver, it could occur if the JDBC
    driver is not in the system CLASSPATH.
    If this is a type-2 JDBC driver, it may also indicate that
    the Driver native layers(DBMS client lib or driver DLL)
    have not been installed properly on your system
    or in your PATH environment variable.
    This is most likely caused by one of the following:
    1. The native layer SO, SL, or DLL could not be found.
    2. The file permissions on the native layer SO, SL, or DLL
    have not been set properly.
    3. The native layer SO, SL, or DLL exists, but is either
    invalid or corrupted.
    For more information, read the installation documentation
    for your JDBC Driver, available from:
    http://e-docs.bea.com
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
    nectionEnvFactory.java:212)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
    nectionEnvFactory.java:134)
    at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
    cator.java:705)
    at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
    ava:282)
    at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
    ava:650)
    at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:360)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:285)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:239)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:199)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:360)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    57)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    25)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy31.updateDeployments(Unknown Source)
    at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
    yments(ServerMBean_CachingStub.java:2977)
    at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
    er(ApplicationManager.java:372)
    at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
    nManager.java:160)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:360)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    57)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    25)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy42.start(Unknown Source)
    at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
    .start(ApplicationManagerMBean_CachingStub.java:480)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
    at weblogic.management.Admin.finish(Admin.java:644)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
    at weblogic.Server.main(Server.java:35)
    Would like some help on this asap as the project is in critical stage.
    Thanks

    The driver being used by your weblogic is too old and incompatible with the DBMS. Upgrade the driver.

  • Error while running a test case in Jcaps 6 JDBC project

    I encountered an error while running the testcase for a JDBC BC project in Jcaps 6.
    BPCOR-6135:A fault was not handled in the process scope; Fault Name is {http://docs.oasis-open.org/wsbpel/2.0/process/executable}selectionFailure; Fault Data is null. Sending errors for the pending requests in the process scope before terminating the process instance
    Caused by: I18N: BPCOR-3023: Selection Failure occurred in BPEL({http://enterprise.netbeans.org/bpel/DBSample/Db}Db
    Kindly suggest a solution

    It seems to be a very common error. Try checking your map assignments when the source (from) is empty (null). These mappings with null values may produce the error you are facing...
    Good luck!

Maybe you are looking for