Equivalent of java.sql.ResultSetMetaData

Hi,
I'm looking for something which is equivalent to java.sql.ResultSetMetaData in Toplink. Does anyone know how this can be done ?
Thanks,
-Prashant

Hi,
I have a similar problem. I want to find out the column names when i fire raw-sql. I use SQLCall to do this.
Then I get a Vector<DatabaseRow>.
Vector vDR = session.executeQuery( new SQLCall( "select * from table_name" ) )
Now Is there a way to find out the column names dynamically. In the javadocs i see that objDatabaseRow.keys() returns an Enum<DatabaseField>... but i cant see javadocs on how to use DatabaseField.
So is there any other way ?
Thanks,
Krishna

Similar Messages

GetScale(int) method of java.sql.ResultSetMetaData

On weblogic 8.1 instance I am using oracle JDBC TYPE 4 Thin driver.
The jar file for the driver is ojdbc14.jar.
Our database is 9.2.0.
code excerpt:
//rs is the resultset
if (rs != null)
ResultSetMetaData RSMD = rs.getMetaData();
int i = RSMD.getColumnCount();
int test=0;
String cName="";
for(int j = 1; j <= i; j++)
test = RSMD.getScale(j);
cName = RSMD.getColumnName(j);
System.out.println("The scale of column name : "+cName+ " is " +test);
The output is:
The scale of column name : PERSON_ID is -127
The scale of column name : FIRST_NAME is 0
The scale of column name : LAST_NAME is 0
The data type of column PERSON_ID is NUMBER. Why is it so? getScale(int) should return zero for a column whose data type is NUMBER.
Help me. Is it driver specific probelm?

Hi,
I have a similar problem. I want to find out the column names when i fire raw-sql. I use SQLCall to do this.
Then I get a Vector<DatabaseRow>.
Vector vDR = session.executeQuery( new SQLCall( "select * from table_name" ) )
Now Is there a way to find out the column names dynamically. In the javadocs i see that objDatabaseRow.keys() returns an Enum<DatabaseField>... but i cant see javadocs on how to use DatabaseField.
So is there any other way ?
Thanks,
Krishna

JDBC Sender Adapter : java.sql.SQLException: Cursor state not valid.

Hello all,
We have configured JDBC Sender Adapter which fetches around 10K records with poll interval 1hr from DB2 System .
It was working fine,suddenly it started throwing an exception in Adapter Monitoring :
Error during conversion of query result to XML: java.sql.SQLException: Cursor state not valid.
It is not fetching any records.
Without changing any configurations when we tried to fetch to around 1000 records it's working fine.
For 10K records same exception persists
What could be the reason ?How to resolve this issue?
regards
GangaPrasad

Hello Christophe ,
Trace in VA :::
Date : 05/09/2008
Time : 11:45:57:750
Message : Unexpected error converting database resultset to XML, reason: java.sql.SQLException: Cursor state not valid.
     at java.lang.Throwable.<init>(Throwable.java:194)
     at java.lang.Exception.<init>(Exception.java:41)
     at java.sql.SQLException.<init>(SQLException.java:40)
     at com.ibm.as400.access.JDError.throwSQLException(JDError.java:389)
     at com.ibm.as400.access.JDError.throwSQLException(JDError.java:366)
     at com.ibm.as400.access.AS400JDBCResultSet.getValue(AS400JDBCResultSet.java:3580)
     at com.ibm.as400.access.AS400JDBCResultSet.getString(AS400JDBCResultSet.java:3223)
     at sun.reflect.GeneratedMethodAccessor459222074.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:309)
     at com.sap.aii.adapter.jdbc.sql.jdbctrace.TraceInvocationHandler.invoke(TraceInvocationHandler.java:45)
     at com.sap.aii.adapter.jdbc.sql.jdbctrace.$Proxy254.getString(Unknown Source)
     at com.sap.aii.adapter.jdbc.JDBC2XI.convert2XML(JDBC2XI.java:954)
     at com.sap.aii.adapter.jdbc.JDBC2XI.invoke(JDBC2XI.java:492)
     at com.sap.aii.af.service.scheduler.JobBroker$Worker.run(JobBroker.java:475)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:99)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:119)
Severity : Error
Category : /Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC
Location : com.sap.aii.adapter.jdbc.JDBC2XI.convert2XML(ResultSet, ResultSetMetaData)
Application :
Thread : XI JDBC2XI[JDBC_SND_DB2_VehicleReceiving/DB2PRD00/]_170
Datasource : 12428950:/usr/sap/PXI/DVEBMGS01/j2ee/cluster/server0/log/applications/com.sap.xi/xi.log
Message ID : 00145E742794005E0014980B000000BE00044CC763766C4F
Source Name : /Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC
Argument Objs : java.sql.SQLException: Cursor state not valid.
     at java.lang.Throwable.<init>(Throwable.java:194)
     at java.lang.Exception.<init>(Exception.java:41)
     at java.sql.SQLException.<init>(SQLException.java:40)
     at com.ibm.as400.access.JDError.throwSQLException(JDError.java:389)
     at com.ibm.as400.access.JDError.throwSQLException(JDError.java:366)
     at com.ibm.as400.access.AS400JDBCResultSet.getValue(AS400JDBCResultSet.java:3580)
     at com.ibm.as400.access.AS400JDBCResultSet.getString(AS400JDBCResultSet.java:3223)
     at sun.reflect.GeneratedMethodAccessor459222074.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:309)
     at com.sap.aii.adapter.jdbc.sql.jdbctrace.TraceInvocationHandler.invoke(TraceInvocationHandler.java:45)
     at com.sap.aii.adapter.jdbc.sql.jdbctrace.$Proxy254.getString(Unknown Source)
     at com.sap.aii.adapter.jdbc.JDBC2XI.convert2XML(JDBC2XI.java:954)
     at com.sap.aii.adapter.jdbc.JDBC2XI.invoke(JDBC2XI.java:492)
     at com.sap.aii.af.service.scheduler.JobBroker$Worker.run(JobBroker.java:475)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:99)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:119)
Arguments : java.sql.SQLException: Cursor state not valid.
     at java.lang.Throwable.<init>(Throwable.java:194)
     at java.lang.Exception.<init>(Exception.java:41)
     at java.sql.SQLException.<init>(SQLException.java:40)
     at com.ibm.as400.access.JDError.throwSQLException(JDError.java:389)
     at com.ibm.as400.access.JDError.throwSQLException(JDError.java:366)
     at com.ibm.as400.access.AS400JDBCResultSet.getValue(AS400JDBCResultSet.java:3580)
     at com.ibm.as400.access.AS400JDBCResultSet.getString(AS400JDBCResultSet.java:3223)
     at sun.reflect.GeneratedMethodAccessor459222074.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:309)
     at com.sap.aii.adapter.jdbc.sql.jdbctrace.TraceInvocationHandler.invoke(TraceInvocationHandler.java:45)
     at com.sap.aii.adapter.jdbc.sql.jdbctrace.$Proxy254.getString(Unknown Source)
     at com.sap.aii.adapter.jdbc.JDBC2XI.convert2XML(JDBC2XI.java:954)
     at com.sap.aii.adapter.jdbc.JDBC2XI.invoke(JDBC2XI.java:492)
     at com.sap.aii.af.service.scheduler.JobBroker$Worker.run(JobBroker.java:475)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:99)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:119)
Dsr Component :
Dsr Transaction : d1f629d01d9b11dd984200145e742794
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives : com.sap.aii.adapter.jdbc.JDBC2XI
Resource Bundlename :
Session : 0
Source : /Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC
ThreadObject : XI JDBC2XI[JDBC_SND_DB2_VehicleReceiving/DB2PRD00/]_170
Transaction : SAP J2EE Engine JTA Transaction : [0ffffffbdffffffa6ffffff960086]
User : J2EE_GUEST
Regards
Ganga Prasad

Put java.sql.Date in correct format

I need to put java.sql.Date in correct format to query an Oracle database.
Here is my code:
        SimpleDateFormat formatter = new SimpleDateFormat("dd-MMM-yy");
        java.util.Date dateChosen = jXDatePicker1.getDate();
        String strDate = formatter.format(dateChosen);
        System.out.println("Date Chosen: " + strDate); // output is: 11-Feb-00
        java.util.Date parserDate = null;
        try {
            parserDate = formatter.parse(strDate);
        } catch (ParseException re) {
            System.err.println("Exception caught: " + re.getMessage());
        // create java.sql.Date object
            java.sql.Date oraDate = new java.sql.Date(parserDate.getTime());
        System.out.println(oraDate); // date is in this format: 2000-02-11
        System.out.println("formatted oraDate: " + formatter.format( oraDate ) ); // no good, stringIf I use formatter.format( oraDate ) I get the correct format (11-Feb-00) BUT it is no longer a sql Date, it is a String which can't be use.
I have looked at the API and many other forum threads on this, any help would be greatly appreciated!

In the class with the PreparedStatement, I pass the date like this:
public class report extends javax.swing.JDialog {
     java.sql.Date newDate;
    public report(java.sql.Date passedOraDate, String passedtxtDate) {
        super();
        initComponents();
        setTitle("Report");
        setModal(true);
        newDate = passedOraDate;
        statusLabel.setText(passedtxtDate);
        System.out.println("passedtxtDate: " +passedtxtDate);
        System.out.println("newDate: " +newDate);
    }Here is the code that uses the actual PreparedStatement:
        try {
            // In my actual code I have all columns listed in query
            String query = "SELECT * FROM report WHERE repdate = ?";
            ps = conn.prepareStatement(query); // create a statement
                       ps.setDate(1, newDate); // set input parameter
            rs = ps.executeQuery();
            // extract data from the ResultSet
            ResultSetMetaData md = rs.getMetaData();
            int columns = md.getColumnCount();This is greatly edited to show relevant code!

Java.sql.Time not working correctly

Hi guys,
I have the following code which is used to put clients session data in my database.
long logged_in_time = p.getCreatedTime();
            long logged_out_time = System.currentTimeMillis();
            long duration = logged_out_time - logged_in_time;
            System.out.println("LOGGED IN: " + logged_in_time);
            System.out.println("LOGGED OUT: " + logged_out_time);
            System.out.println("DURATION: " + duration);
            System.out.println("DURATION TIME: " + new Time(duration));and this is the result:
LOGGED IN: 1141394617474
LOGGED OUT: 1141394638634
DURATION: 21160
DURATION TIME: 01:00:21
Does anyone know why java.sql.Time adds an hour? The duration in milliseconds equals 21 seconds but when I constuct the Time obj I get 1 hour 21 seconds.
Any help would be great.
Alex

Probably because your default timezone is not GMT, but GMT+1 (e.g. CET.)
The java.util.Date (and subclasses) wraps a long value representing the number of miliseconds elapsed since January 1, 1970, 00:00:00 GMT.
As a consequence a new Date(0) will represent the date above, which is equivalent to January 1, 1970, 01:00:00 CET.
You might use a DateFormat and specify the TimeZone.
Example:        Time time = new Time(21160);
        DateFormat format = DateFormat.getTimeInstance();
        format.setTimeZone(TimeZone.getTimeZone("CET"));
        System.out.println(format.format(time));
        format.setTimeZone(TimeZone.getTimeZone("GMT"));
        System.out.println(format.format(time));Will output:
01:00:21
00:00:21

Unreported exception; java.sql.SQLException; must be caught or declared to

Hi everyone,
For my Java course assignment we need to make a small application that uses a MS Access database. But de code below gives me a "Unreported exception; java.sql.SQLException; must be caught or declared to be thrown at line xx" error.
public class ConnectieBeheer
private static Connection con;
private static Statement stmt;
private static ResultSet res;
private static ResultSetMetaData md;
private ConnectieBeheer(){}
public static void openDB() {
    Driver driver = new JdbcOdbcDriver();
    Properties info = new Properties();
    String url = "jdbc:odbc:theater";
    con = driver.connect(url, info);       <--- Error here
    if (con != null)
      stmt = con.createStatement();      <--- Error here
      DatabaseMetaData dma = con.getMetaData();      <--- Error here
}So I tried this :
public static void openDB() throws SQLException {Now I do not get an error.
The OpenDB method is called from a different class like this :
public static void test1(){
    ConnectieBeheer.openDB();
    System.out.println("DB opened");
}But now it gives the same "Unreported exception; java.sql.SQLException; must be caught or declared to be thrown at line xx" error but now at the line ConnectieBeheer.openDB();
Why is this? And what can I do to correct this?
Thanks!
Steven.

you should read the sun tutoriel about exceptions handling ;
there are two ways to handle an exception : either you redirects it (using "throws" statement, what you did for the openDB method), or you catch it using a try { ... } catch (Exception exc) {}
if you want to get rid of the error what you can do is :
public static void test1(){
    try {
        ConnectieBeheer.openDB();
    } catch (java.sql.SQLException sqle) {
        sqle.printStackTrace();
    System.out.println("DB opened");
}

Create table dinamically using java sql types?

Hi! I've an application that reads an XML file. This file contains de definitions of some tables, using java sql types. For example:
<dbtable>
<dbtablename>Name of table</dbtablename>
<dbtablefield>
    <name>Name of table field</name>
    <type>java.sql.Types.VARCHAR</type>
    <length>10</lenght>
    <canNull>0</canNull>
    <isPK>1</isPK>
</dbtablefield>
</dbtable>That's a little example of one table, with one field. Is a java.sql.Types.VARCHAR (or is equivalent in int), which has a size of 10, it cannot be null and is a primary key for the table.
Now, the lenght, null, and primary keys are not problem at all. What I want to know, is how do I create de table using the java.sql.Types. I mean, I don't want to hard code:
String s = "CREATE TABLE name (COLUMN VARCHAR(10)...";Instead, I want to use some "wild cards", as are used in PreparedStatement. The idea of this is that no matter what DB I'm using, I must always be capable of creating the tables not worrying for the DB. I mean, I must be able to create the table in Oracle, SQL Server, DB2, etc., using the same XML and the same java class.
Something like:
String s = "CREATE TABLE name (COLUMN ? (10)...";
someobject.setObject(1,java.sql.Types.VARCHAR);
someobject.execute(); //create tableIs this possible? Or do I have to make a map for each DB?
Thanks a lot for your help! Dukes available!

you can provide some fields at runtime..
for example
"CREATE TABLE name (COLUMN" + arg[1] +"(10)..."
here arg is the string array passed into the main.

$ENV perl equivalent in Java

We are in our first steps in trying to convert some of our systems from Perl to Java.
In a module we had (Database module) which was responsible for all DB activity, we had an area where, upon errors, we printed out $ENV{SCRIPT_NAME} environment variable, which is set by Apache and can be read by Perl. This helps us debug things by knowing which script was ran when a DB error occurred.
As we are porting the Database module into a Database class, we are trying to think how we can achieve the same capability with Java.
I don't know of the existence of $ENV equivalent in Java. Not one that contains the web-server executed script, in case its a script that is ran by a web server.
Is there?
Note that the Database module may be ran as part of a Servelet but may also be part of just a simple server script. In perl, is such case, the $ENV{SCRIPT_NAME} would come out empty.
Any suggestions of how to do that?

Pidgin wrote:
As you indicated: Note that both are relatively slow and should only be used for exceptional or error conditions.
The access to the SCRIPT_NAME is actually a web re,ated variable that we need for showing which HTTP resquest generated the specific SQL error.It's only a variable in perl (or in CGI scripts, to be more precise).
It happens often enough, and doing a very low-level trace of the executed code migt not be the right option.SQLExceptions that need logging happen often? That shouldn't be the fact. How often?
Stacktraces are not awfully slow. They are ok for handling errors & exceptions. But they should not be used for classical flow control.
For example, it might be that the executing code is Script.class using Database.class, but Script.class can be initiated from www.whatever.com/script/ or www.whatever.com/premium/script/.. in each case, we want to know the full URL of the called "script'.With the stack trace you'd see the Servlet and/or Action that handles the request.
So we do need access to the web "environment".
What we do now, is store a static Servlet_Request variable (set on the first Database constructor, by passing the servlet request and response objects to the Database constructor). From that point on, we can access Servlet_Request.getRequestURI()That won't work as soon as more than one request is handled at the same time (which is very, very soon!).
You might want to look into something like log4js MDC, where you can at one point in your application set a key in a map and have that appear in every log statement from that thread until it's removed again.
This is quite different than the Perl logic, where we could access a "web enabled" System.getenv() and read from it SCRIPT_NAME or other web related parameters, if they existed (or returning null if they didn't)You should not try to apply the best practices learned by perl web programming 1:1 on Java. In the Java world pretty different concepts apply, especially when doing Web-Programming, as Perl web-applications are usually based on the rather antiquated CGI interface, while Java uses a central application server that handles each request as it wishes.

Decompilation errors java source "java/sql/Date"

Hi,
I've decompiled a Contoller file and inside the new created java source file
there is a line like
<b>
Class aclass2[] = {
java/sql/Date, java/lang/Integer, java/lang/String, java/lang/String
</b>
But this line can't be compiled in a new file version. What is the equivalent to this or how can I change it, so that
the java file can compiled properly.
Thanks a a lot and regards
Robert
Edited by: user2979718 on 17.05.2010 02:05

Hi Robert,
Try with Class aclass2[] = {
java.sql.Date, java.lang.Integer, java.lang.String, java.lang.String
Hope this will resolve your issue.
Regards,
Reetesh Sharma

Implementation of java.sql.* abstract methods

Hi to u all,
Can someone tell me where the abstract methods in some interfaces in the java.sql package are implemented?
For example:
-- START CODE --
ResultSet rs = null;
try
ps = db().prepareStatement("select * from aTable where x=?");
ps.setInt(1, aValue);
rs = ps.executeQuery();
ResultSetMetaData md = rs.getMetaData();
-- END CODE --
It's about the getMetaData()-call.
It returns information about the column names in the resultset.
If I open the declaration (eclipse) the abstract method getResultSet() in the interface ResultSet in the java.sql-package is shown.
So where is the actual implementation of the method??
As a collegue told me he suspected the implementation is probably somewhere in the driver-software. If this is the case, how does the JVM know to find it there?
Thx in advance for your time and answer(s)

The JDBC driver implements the JDBC API.
The JVM how to know that?
1. The Class.forName("jdbc driver name") will load the driver into memory.
2. The DriverManager.registerDriver(Driver driver) will register the driver for later use.
Check the DriverManager.java for more detail.

Poblem with java.sql.Date while inserting to a table

Hi All,
I have a PostgreSQL database table which contains fields(columns ) of type date. I want to insert values to the table in the[b] �dd-MMM-YYYY� format using the prepared statement.
My code is as follows
java.text.DateFormat dateFormatter =new java.text.SimpleDateFormat("dd-MMM-yyyy");
String formatedDate=dateFormatter.format(theDate);
currentDate = new java.sql.Date(dateFormatter.parse(formatedDate).getTime())
��
��
��
pst.setDate(12,currentDate);The problem is the currentDate variable gives date only in the �YYYY-MMM-dd� format but requirement is the currentDate variable should give date in the �dd-MMM-YYYY� format and this should be save to table as java.sql.Date type
There is any solution???? please help me...
Thanks and Regards,
Hyson_05

Hi,
What are you talking about? A Date does always wrap a millisecond value, and doesn't have any formatting. It's the database, or your program which formats the date that you see.
In short. You should format the value when you print it, and not when you store it.
Kaj

OpenSQLException - object of type java.sql.Date is not normalized

Hi,
I am attempting to code an SQL query in an EJB and get the following exception:
com.sap.sql.log.OpenSQLException: The object of type java.sql.Date with the value '2010-06-04 13:21:09.424' assigned to host variable 1 is not normalized. It must not contain time components in the time zone running the virtual machine. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124) at com.sap.sql.jdbc.common.CommonPreparedStatement.setDate(CommonPreparedStatement.java:650) at......
Below is the code snippet I am using:
                    private static String selWQ = "Select * from ZZZZ_TABLE " +
                                                                   "where DATEFROM >= ? " +
                                                              "and DATETO <= ? ";
     public UsageRecord[] getRecords(Date fromDate,Date toDate)
          UsageRecord[] ura = null;
          String q          = null;
          ArrayList al      = new ArrayList();
          try
               q = selWQ;
               conn.open();
               PreparedStatement p = conn.prepareStatement(q);
               p.setDate(1, fromDate);
               p.setDate(2,toDate);
               ResultSet rs = p.executeQuery();
I have a PreparedStatement and am using setDate to set the values. The fromDate and toDate parameters are of type java.sql.Date
Can someone please tell me what I am doing wrong and how to fix it?
thanks
Brian

As requested, here is an example of what I used to resolve this:
               PreparedStatement p = conn.prepareStatement(q);
               SimpleDateFormat ddf = new SimpleDateFormat("yyyy-MM-dd");
                                           String sFrom = ddf.format(new java.util.Date(fromDate));
               String sTo   = ddf.format(new java.util.Date(toDate));
               p.setDate(1, java.sql.Date.valueOf(sFrom));
               p.setDate(2, java.sql.Date.valueOf(sTo));
               ResultSet rs = p.executeQuery();
fromDate and toDate are parameters of type long...
regards
Brian

What is the diffrence between package javax.sql and java.sql

Is javax designed for J2EE?
And when to use package javax?

Hi,
What is the diffrence between package javax.sql and java.sql?The JDBC 2.0 & above API is comprised of two packages:
1.The java.sql package and
2.The javax.sql package.
java.sql provides features mostly related to client
side database functionalities where as the javax.sql
package, which adds server-side capabilities.
You automatically get both packages when you download the JavaTM 2 Platform, Standard Edition, Version 1.4 (J2SETM) or the JavaTM 2, Platform Enterprise Edition, Version 1.3 (J2EETM).
For further information on this please visit our website at http://java.sun.com/j2se/1.3/docs/guide/jdbc/index.html
Hope this helps.
Good Luck.
Gayam.Srinivasa Reddy
Developer Technical Support
Sun Micro Systems
http://www.sun.com/developers/support/

Java.sql.SQLException: ORA-06502: PL/SQL in EBS R12

Hi everyone,
May you please help me diagnose the problem.
Oracle EBS 12.0.0.6, DB(10.2.0.3) on one machine and App(forms, concurrent manager, etc) on other machine, both AIX 5.3.
I have following failed concurrent request:
*====================================================*
Payables: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
APPPBR module: AP Prepayment Balance Report
Current system time is 12-MAY-2010 15:33:36
XDO Data Engine Version No: 5.6.3
Resp: 50661
Org ID : 81
Request ID: 449826
All Parameters: ORG_ID_PARAM=81:COA_ID_PARAM=50328:FROM_DATE_PARAM="2010/05/12 00:00:00":TO_DATE_PARAM=:PERIOD_FROM_PARAM=JUL-09:PERIOD_TO_PARAM=MAY-
10:CURR_CODE_PARAM=:ACCOUNT_FROM_PARAM=:ACCOUNT_TO_PARAM=:SUPPLIER_FROM_PARAM=Adel Bin Abdullah Bin Taha Al
Hadad:SUPPLIER_TO_PARAM=:PAID_ONLY_PARAM=:POSTED_ONLY_PARAM=:DUMMY_PARAM=2
Data Template Code: APPPBR
Data Template Application Short Name: SQLAP
Debug Flag: N
{ORG_ID_PARAM=81, PERIOD_FROM_PARAM=JUL-09, CURR_CODE_PARAM=, DUMMY_PARAM=2, PAID_ONLY_PARAM=, PERIOD_TO_PARAM=MAY-10, POSTED_ONLY_PARAM=,
ACCOUNT_FROM_PARAM=, SUPPLIER_FROM_PARAM=Adel Bin Abdullah Bin Taha Al Hadad, SUPPLIER_TO_PARAM=, TO_DATE_PARAM=, ACCOUNT_TO_PARAM=,
FROM_DATE_PARAM=2010/05/12 00:00:00, COA_ID_PARAM=50328}
Calling XDO Data Engine...
[051210_033341921][][STATEMENT] Start process Data
[051210_033341922][][STATEMENT] Process Data ...
[051210_033341924][][STATEMENT] Executing data triggers...
[051210_033341924][][STATEMENT] BEGIN
AP_BAL_PKG.ORG_ID_PARAM := :ORG_ID_PARAM ;
AP_BAL_PKG.COA_ID_PARAM := :COA_ID_PARAM ;
AP_BAL_PKG.FROM_DATE_PARAM := :FROM_DATE_PARAM ;
AP_BAL_PKG.TO_DATE_PARAM := :TO_DATE_PARAM ;
AP_BAL_PKG.PERIOD_FROM_PARAM := :PERIOD_FROM_PARAM ;
AP_BAL_PKG.PERIOD_TO_PARAM := :PERIOD_TO_PARAM ;
AP_BAL_PKG.CURR_CODE_PARAM := :CURR_CODE_PARAM ;
AP_BAL_PKG.ACCOUNT_FROM_PARAM := :ACCOUNT_FROM_PARAM ;
AP_BAL_PKG.ACCOUNT_TO_PARAM := :ACCOUNT_TO_PARAM ;
AP_BAL_PKG.SUPPLIER_FROM_PARAM := :SUPPLIER_FROM_PARAM ;
AP_BAL_PKG.SUPPLIER_TO_PARAM := :SUPPLIER_TO_PARAM ;
AP_BAL_PKG.PAID_ONLY_PARAM := :PAID_ONLY_PARAM ;
AP_BAL_PKG.POSTED_ONLY_PARAM := :POSTED_ONLY_PARAM ;
AP_BAL_PKG.DUMMY_PARAM := :DUMMY_PARAM ;
:XDO_OUT_PARAMETER := 1;
END;
[051210_033341927][][STATEMENT] 1:81 :
[051210_033341928][][STATEMENT] 2:50328 :
[051210_033341928][][STATEMENT] 3:2010/05/12 00:00:00 :
[051210_033341928][][STATEMENT] 4: :
[051210_033341928][][STATEMENT] 5:JUL-09 :
[051210_033341928][][STATEMENT] 6:MAY-10 :
[051210_033341928][][STATEMENT] 7: :
[051210_033341928][][STATEMENT] 8: :
[051210_033341928][][STATEMENT] 9: :
[051210_033341928][][STATEMENT] 10:Adel Bin Abdullah Bin Taha Al Hadad :
[051210_033341928][][STATEMENT] 11: :
[051210_033341928][][STATEMENT] 12: :
[051210_033341929][][STATEMENT] 13: :
[051210_033341929][][STATEMENT] 14:2 :
[051210_033341940][][EXCEPTION] SQLException encounter while executing data trigger....
java.sql.SQLException: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at line 11
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
     at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:215)
     at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:965)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1170)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3339)
     at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3445)
     at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4395)
     at oracle.apps.xdo.dataengine.XMLPGEN.executeTriggers(XMLPGEN.java:650)
     at oracle.apps.xdo.dataengine.XMLPGEN.processData(XMLPGEN.java:262)
     at oracle.apps.xdo.dataengine.XMLPGEN.processXML(XMLPGEN.java:215)
     at oracle.apps.xdo.dataengine.XMLPGEN.writeXML(XMLPGEN.java:254)
     at oracle.apps.xdo.dataengine.DataProcessor.processDataStructre(DataProcessor.java:390)
     at oracle.apps.xdo.dataengine.DataProcessor.processData(DataProcessor.java:355)
     at oracle.apps.xdo.oa.util.DataTemplate.processData(DataTemplate.java:348)
     at oracle.apps.xdo.oa.cp.JCP4XDODataEngine.runProgram(JCP4XDODataEngine.java:293)
     at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Start of log messages from FND_FILE
End of log messages from FND_FILE
Executing request completion options...
------------- 1) PUBLISH -------------
Beginning post-processing of request 449826 on node EBSCL1 at 12-MAY-2010 15:33:42.
Post-processing of request 449826 failed at 12-MAY-2010 15:33:42 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.
Finished executing request completion options.
Concurrent request completed
Current system time is 12-MAY-2010 15:33:42
*====================================================*
When I look at OPP Log, following is the info:
*====================================================*
[5/12/10 3:33:42 PM] [OPPServiceThread0] Post-processing request 449826.
[5/12/10 3:33:42 PM] [28164:RT449826] Executing post-processing actions for request 449826.
[5/12/10 3:33:42 PM] [28164:RT449826] Starting XML Publisher post-processing action.
[5/12/10 3:33:42 PM] [28164:RT449826]
Template code: APPPBR
Template app: SQLAP
Language: en
Territory: US
Output type: RTF
[5/12/10 3:33:42 PM] [UNEXPECTED] [28164:RT449826] java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
     at java.lang.reflect.Method.invoke(Method.java:615)
     at oracle.apps.xdo.common.xml.XSLT10gR1.invokeParse(XSLT10gR1.java:517)
     at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:224)
     at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:177)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1044)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:997)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:212)
     at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1665)
     at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:975)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5926)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3458)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3547)
     at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:259)
     at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:172)
Caused by: oracle.xdo.parser.v2.XMLParseException: Start of root element expected.
     at oracle.xdo.parser.v2.XMLError.flushErrors1(XMLError.java:337)
     at oracle.xdo.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:343)
     at oracle.xdo.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:285)
     at oracle.xdo.parser.v2.XMLParser.parse(XMLParser.java:289)
     ... 17 more
[5/12/10 3:33:42 PM] [28164:RT449826] Completed post-processing actions for request 449826.
*====================================================*
Br,
Anjum

Hi,
It seems like a bug as per metalink note:
APPPBR : AP Prepayment Balance Report Error Out java.sql.SQLException: ORA-06502: PL/SQL: numeric or value error: character string buffer too small ORA-06512: at line 11 [ID 827325.1]
Anyway, if you have any relevant information, please share.
Br,
Anjum

*URGENT HELP REQUIRED* java.sql.SQLException: Invalid Oracle URL specifed

Hi all,
In the middle of the last week for my final year project and having to convert to an Oracle database due to compatibility problems with university Tomcat Server and MS Access. I'm having trouble connecting to the Oracle database and would appreciate some help please.
Running on Windows 98 in the lab here, and the Oracle 9i, release 9.2.0.2.0, J2SDK1.4.0, Classes12.zip installed OK.
Code for connection looks like this inside the constructor of my class:
Class.forName("oracle.jdbc.driver.OracleDriver");
cardSaleConnexion = DriverManager.getConnection("jdbc:oracle:[email protected]:1521:sid","user_name","pwdt");
System.out.println("Connection Successful ");
And I'm getting the following error when calling the constructor in a driver program:
java.sql.SQLException: Invalid Oracle URL specified
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:188)
     at java.sql.DriverManager.getConnection(DriverManager.java:512)
     at java.sql.DriverManager.getConnection(DriverManager.java:171)
     at CardSale.<init>(CardSale.java:30)
     at Driver.main(Driver.java:11)
Exception in thread "main"
Please reply on a very urgent basis.
Kind regards,
Peter

Try ojdbc14.jar as the JDBC driver instead of classes12.zip.
Refer:
http://otn.oracle.com/software/tech/java/sqlj_jdbc/htdocs/jdbc9201.html
http://docs.sun.com/source/817-5603-10/index.html
Database Driver
This section describes the known database driver issues and associated solutions.
ID      Summary
4700531      On Solaris, an ORACLE JDBC driver error occurs.
     This new Java Database Connectivity (JDBC) driver is for Oracle (R) working with JDK1.4. The problem is caused by a combination of the Oracle 9.1 database and ojdbc14.jar. Applying the patch will fix the problem on Solaris 32-bit machine, running an Oracle 9.0.1.3 database.
     Solution
     Obtain and apply the patch to your server from the Oracle Web site for Bug 2199718. Perform the following steps:
     1.��Go to the Oracle web site.
     2.��Click the 'patches' button.
     3.��Type 2199718 in the patch number field.
     4.��Click the 32-bit Solaris OS patch.Go to Metalink.oracle.com.
     5.��Click patches.
     6.��Under patch number, enter 2199718.
     7.��Click the 32 bit Solaris OS patch.
4707531      On Solaris, accessing an Oracle 9.1 database with an Oracle 9.2 Client may cause data corruption.
     If you use an Oracle (R) 9.2 client to access an Oracle 9.1 database, data corruption might occur when a number column follows a timestamp column.
     The problem might be caused by using the ojdbc14.jar file with an Oracle 9.1 database. Applying the patch might assist in addressing the situation on Solaris 32-bit machines, running an Oracle 9.1 database. This JDBC driver is for Oracle working with JDK1.4.
     Solution
     Obtain the patch that Oracle might make available from the Oracle web site for Bug 2199718 and apply it to your server.
Regards,
Pankaj D.

Equivalent of java.sql.ResultSetMetaData

Similar Messages

Maybe you are looking for