ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Interchange Server + Adapters » IBM WBI JDBC adapter fault

Post new topic  Reply to topic
 IBM WBI JDBC adapter fault « View previous topic :: View next topic » 
Author Message
4integration
PostPosted: Tue Jan 30, 2007 8:30 am    Post subject: IBM WBI JDBC adapter fault Reply with quote

Disciple

Joined: 04 Sep 2006
Posts: 197
Location: Gothenburg, Sweden
I am trying to generate BO's for the JDBC adapter using ODA and BO Designer but have problems. We have two different Oracle databases (not the same schema at all)

For the database 1 there is no problem to generate BO's.
For the database 2 I can not generate anything and getting a fault in the trace telling:
Quote:

[Time: 2007/01/30 17:11:10.836] [System: Object Discovery Agent] [SS: JDBCODA] [Type: Trace] [Mesg: Getting Attributes.]
[Time: 2007/01/30 17:11:10.836] [System: Object Discovery Agent] [SS: JDBCODA] [Type: Trace] [Mesg: Entering method getObjectAttributes.]
[Time: 2007/01/30 17:11:10.836] [System: Object Discovery Agent] [SS: JDBCODA] [Type: Trace] [Mesg: Entering method getColumns.]
[Time: 2007/01/30 17:11:13.850] [System: Object Discovery Agent] [SS: JDBCODA] [Type: Trace] [Mesg: Exiting method getColumns.]
[Time: 2007/01/30 17:11:13.850] [System: Object Discovery Agent] [SS: JDBCODA] [Type: Trace] [Mesg: No Columns found in the table/View/Procedure/Synonym INTERFACE_MAPPING_HEADER in Schema DCSDBA]
[Time: 2007/01/30 17:11:13.850] [System: Object Discovery Agent] [SS: JDBCODA] [Type: Unknown] [Mesg: null]
[Time: 2007/01/30 17:12:18.705] [System: Object Discovery Agent] [SS: JDBCODA] [Type: Trace] [Mesg: Exiting method createSpecs.]
[Time: 2007/01/30 17:12:18.705] [System: Object Discovery Agent] [SS: JDBCODA] [Type: Trace] [Mesg: Exiting method generate Defs.]


What can do this and how can this be solved?
I have used a std Java app and reads the metadata just fine.

Other
Trying to increase the trace level but the parameters "TraceFileName" and "TraceLevel" are not available in BO Designer. Is the metadata/template available for those settings so I can manually add them or is it any other way?

EDIT SOLUTION:
Quote:
This information can be entered in ..\IBM\WebSphereAdapters\ODA\odk.dd.xml e.g.
Quote:
<?xml version="1.0" encoding="utf-8" ?>
<odk>
<startup>
<messagefile usestandard="true"></messagefile>
</startup>
<diagnostics>
<tracefile usestandard="false">MyTrace.log</tracefile>
<tracelevel usestandard="false">5</tracelevel>
</diagnostics>
</odk>
But it seems that the default trace level is set to maximum



The stored connections, where are they stored?

Thanks!
_________________
Best regards
4 Integration
Back to top
View user's profile Send private message
4integration
PostPosted: Thu Feb 01, 2007 3:18 pm    Post subject: Reply with quote

Disciple

Joined: 04 Sep 2006
Posts: 197
Location: Gothenburg, Sweden
I have got a bit forward in the fault tracing. The Oracle JDBC connection seems to "crashes" when the setIncludeSynonyms is true and getting metadata. When setIncludeSynonyms is false it works fine in my test app.

Using ojdbc14_g.jar (10.2.0.2.0) and my test application is:
Code:
package test;

import java.sql.Connection;
import java.sql.DatabaseMetaData;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.util.Enumeration;

import oracle.jdbc.OracleConnection;

public class OracleTest {
   public static void main(String[] args) {
      try {
         DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
         oracle.jdbc.driver.OracleLog.setTrace(true);
                  
         Enumeration enums = DriverManager.getDrivers();
         while (enums.hasMoreElements()) {
            System.out.println("Driver \"" + enums.nextElement().getClass().getName() + "\" is loaded");
         }
         
         Connection conn = DriverManager.getConnection("jdbc:oracle:thin:@ora.domain.net:1521:dbname", "user", "password");
         System.out.println("Connection Class: " + conn.getClass().getName());

         ((OracleConnection)conn).setIncludeSynonyms(true);
         DatabaseMetaData dbmd = conn.getMetaData();
         ResultSet r = dbmd.getColumns(null, "SCHEMA", "MY_TABLE", "%");
         while (r.next()) {
            System.out.println("[Column name: "+ r.getString(4)+ "] [Data type: " + r.getString(5)+ "] [Data type name: " + r.getString(5)+"]");
         }
         conn.close();
      } catch (Exception e) {
         e.printStackTrace();
      }
   }
}


The trace from Oracle JDBC looks like:
Quote:
Driver "oracle.jdbc.driver.OracleDriver" is loaded
Driver "oracle.jdbc.driver.OracleDriver" is loaded
2007-feb-01 23:53:35 oracle.jdbc.driver.PhysicalConnection setAutoCommit
INFO: PhysicalConnection.setAutoCommit(autoCommit=true)
2007-feb-01 23:53:35 oracle.jdbc.driver.PhysicalConnection setAutoCommit
INFO: PhysicalConnection.setAutoCommit(autoCommit): return
2007-feb-01 23:53:35 oracle.jdbc.driver.PhysicalConnection setIncludeSynonyms
INFO: PhysicalConnection.setIncludeSynonyms(synonyms=true)
2007-feb-01 23:53:35 oracle.jdbc.driver.PhysicalConnection getMetaData
INFO: PhysicalConnection.getMetaData()
2007-feb-01 23:53:35 oracle.jdbc.driver.PhysicalConnection getIncludeSynonyms
INFO: PhysicalConnection.getIncludeSynonyms() returned true
Connection Class: oracle.jdbc.driver.T4CConnection
2007-feb-01 23:53:35 oracle.jdbc.driver.PhysicalConnection getRemarksReporting
INFO: PhysicalConnection.getRemarksReporting()
2007-feb-01 23:53:35 oracle.jdbc.driver.PhysicalConnection getRemarksReporting
INFO: PhysicalConnection.getRemarksReporting()
2007-feb-01 23:53:35 oracle.jdbc.driver.PhysicalConnection getIncludeSynonyms
INFO: PhysicalConnection.getIncludeSynonyms() returned true
2007-feb-01 23:53:35 oracle.jdbc.driver.PhysicalConnection getIncludeSynonyms
INFO: PhysicalConnection.getIncludeSynonyms() returned true
2007-feb-01 23:53:35 oracle.jdbc.driver.PhysicalConnection getRemarksReporting
INFO: PhysicalConnection.getRemarksReporting()
2007-feb-01 23:53:35 oracle.jdbc.driver.PhysicalConnection getIncludeSynonyms
INFO: PhysicalConnection.getIncludeSynonyms() returned true
2007-feb-01 23:53:35 oracle.jdbc.driver.PhysicalConnection getDefaultFixedString
INFO: PhysicalConnection.getDefaultFixedString() returning false
2007-feb-01 23:53:35 oracle.jdbc.driver.PhysicalConnection getIncludeSynonyms
INFO: PhysicalConnection.getIncludeSynonyms() returned true
2007-feb-01 23:53:35 oracle.jdbc.driver.OraclePreparedStatement setString
INFO: OraclePreparedStatement.setString(paramIndex=1, x=SCHEMA)
2007-feb-01 23:53:35 oracle.jdbc.driver.OraclePreparedStatement setString
INFO: OraclePreparedStatement.setString(paramIndex=2, x=SCHEMA)
2007-feb-01 23:53:35 oracle.jdbc.driver.OraclePreparedStatement setString
INFO: OraclePreparedStatement.setString(paramIndex=3, x=MY_TABLE)
2007-feb-01 23:53:35 oracle.jdbc.driver.OraclePreparedStatement setString
INFO: OraclePreparedStatement.setString(paramIndex=4, x=MY_TABLE)
2007-feb-01 23:53:35 oracle.jdbc.driver.OraclePreparedStatement setString
INFO: OraclePreparedStatement.setString(paramIndex=5, x=%)
2007-feb-01 23:53:35 oracle.jdbc.driver.OraclePreparedStatement setString
INFO: OraclePreparedStatement.setString(paramIndex=6, x=SCHEMA)
2007-feb-01 23:53:36 oracle.jdbc.driver.T4CPreparedStatement allocateTmpByteArray
ALLVARLIG: oracle.jdbc.driver.T4CPreparedStatement.allocateTmpByteArray : Re-allocate byte array of size : 16000
2007-feb-01 23:53:39 oracle.jdbc.driver.PhysicalConnection close
INFO: PhysicalConnection.close()


Why does this happen?
How can I solve this?

I would be very happy if someone could help me solve this.
_________________
Best regards
4 Integration
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Interchange Server + Adapters » IBM WBI JDBC adapter fault
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.