ORA-03115 Error using CLOB with JDBC

When I try to access CLOB field data with JDBC driver, I gets following error:
ORA-03115: unsupported network datatype or representation.
I am using JDBC 8.1.6(Thin), Oracle 8.0.5
on Linux OS.
what's the problem ?
Thank you for any help.
Taesoo.
null

if it is a bug, then its better to upgrade the database to 10.2.0.4. it is the stable verion in 10g.

Similar Messages

A question about PreparedStatement and ORA-03115 error

Dear all,
I have an issue with JDBC and I would appreciate if you could kindly give me a hand.
I'm using:
- Oracle Database 11g Enterprise (Release 11.1.0.6.0)
- JDBC thin driver version: ( 11.1.0.7.0-Production)
- JDK 1.6
- Operating system: Linux (Ubuntu 8.10)
Here is my code
import java.sql.*;
public class Main
    public static void main(String[] args)
        String dbURL = "jdbc:oracle:thin:@localhost:1521:mydatabase";
        String username = "scott";
        String user_password = "tiger";
        try
            Connection connection = DriverManager.getConnection(dbURL, username, user_password);
            String query_text = "SELECT * FROM mytable";
            Statement statement = connection.createStatement();
            ResultSet query_result = statement.executeQuery(query_text);
            connection.close();
        catch (SQLException e)
            for (Throwable t: e)
                t.printStackTrace();
}This works pretty well without any problem. But when I want to use PreparedStatement instead of Statement I receive the ORA-03115 error message, that is, when I replace the Statement with PreparedStatement in the following way:
String query_text =
        "SELECT first_name, ?, id, ?, job_title, salary FROM mytable "+
        "WHERE id IN ('id14', ?, 'id17', 'id18')";
PreparedStatement prepared_statement = connection.preparedStatement(query_text);
prepared_statement.setString(1, "last_name");
prepared_statement.setString(2, "birthday");
prepared_statement.setString(3, "id02");
ResultSet query_result = prepared_statement.executeQuery(query_text);I get the following:
java.sql.SQLException: ORA-03115: unsupported network datatype or representation
     at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
     at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
     at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:791)
     at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:866)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1186)
     at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1377)
     at oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:387)
     at mysqlpackage.Main.main(Main.java:33)Therefore, right after
ResultSet query_result = prepared_statement.executeQuery(query_text);the exception is thrown,
why it works with Statement but not with PreparedStatement? I tested with several other queries, insert a new row, delete a row, everytime it works well, but when I want to use PreparedStatement instead of Statement, again I have this error message.
Any idea?
Thanks in advance,

OK, I found myself the answer.
First error, I had use ? also for column names, which is not accepted as the SQL query has to be precompiled.
Second error: Instead of writing
ResultSet query_result = prepared_statement.executeQuery(query_text);I had to write:
ResultSet query_result = prepared_statement.executeQuery();I tested with the following
String query_text =
              "SELECT first_name, last_name, id, birthday, job_title, salary "+
              "FROM myenterprise "+
              "WHERE id IN (?, ?, ?, ?) ";
            PreparedStatement prepared_statement =
                    connection.prepareStatement(query_text);
            prepared_statement.setString(1, "id02");
            prepared_statement.setString(2, "id04");
            prepared_statement.setString(3, "id08");
            prepared_statement.setString(4, "id09");
            ResultSet query_result = prepared_statement.executeQuery();And it works pretty well now! :)

ORA-03115 error when calling a Stored Procedure

Hi All,
I'm in the process of porting a Pro/C app from NT to Linux. I've installed 8.1.5 on our Linux box and patched it up to 8.1.5.02.
It all kind of works ok, except that I'm sometimes getting ORA-03115 errors when the app calls a stored procedure. The call in question looks like this:
EXEC SQL BEGIN DECLARE SECTION;
VARCHAR resprows[50][3998];
int numret = 0;
int numrows= 50;
int done= 0;
unsigned long resp_id = 0;
EXEC SQL END DECLARE SECTION;
EXEC SQL AT DB_NAME EXECUTE
BEGIN pkg_something.getdata(
:resp_id, /* IN */
:numrows, /* IN */
:done, /* OUT */
:resprows, /* OUT */
:numret /* OUT */
END;
END-EXEC;
The stored procedure basically uses the resp_id value to select rows from a table;
in each row there is a VARCHAR2(4000) column which it copies into the hostarray resprows.
There may be anything from 1 to numrows returned from the SP.
Initially, the resprows rows were defined to be size [4000]. Unfortunately, this caused ORA-02005 errors - I then changed the size to [3998], which seemed to fix the 02005's (although I'm unclear as to the reasons why).
Now I'm getting the 03115 errors when calling the SP. The oracle manual is not very helpful on what this error means.
This all works chipper on NT.
Any ideas?
Thanks in advance,
Nigel.
PS: The database the app is talking to is still hosted on NT.
null

Histon FTM wrote:
ORA-04063: package body "LAZARUS.LAZARUS" has errors Above, obviously conflicts with the statement that follows:
>
The procedure and package have both compiled without errors and the statement on its own works fine in SQL*Plus.I suggest you take a look in the USER_ERRORS view to see, what the errors are.
And just checking:
You have schema called LAZARUS, which holds a package named LAZARUS, which holds a procedure called POPULATEGRIDPOSITIONS?
Edited by: Toon Koppelaars on Oct 1, 2009 5:55 PM

Re: BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns

Hello Everyone.
I've run into something quite strange and am hoping you can help me.
I am using Apex 4.0.1 and Oracle version 10.2.0.5. I've created a "classical" report in which the underlying SQL is a very simple:
select * from pvtabThe Oracle table pvtab consists of 419 columns, all of which are varchar2(88) and number type. That's it.
When I run the report, al of the columns show up as expected.
However, when I go into the "Report Attributes" tab and click on one of the fields (any of them, it doesn't matter which one), I immediately get the following error:
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "598CAA7B68746A66F4B99E1512C36DED" application checksum = "0"If if replace the "*" with a few actual column names, then I am able to access any of these columns without problem.
If I put back the "*", I then encounter this error again.
I have never seen this error with other SQL SELECT statements in which I use the "*" qualifier to retrieve all columns from the table.
And so, I am wondering if the error is caused because of the large number of columns (419) in my table.
I've seen this same error mentioned in connection with forms but never with a report.
So, is there some limit to the number of columns one can have in a "classic" or interactive report?
Any idea why I would be getting this error?
Here is the DDL for my table pvtab:
CREATE TABLE "PVTAB"
   (     "MICRO" VARCHAR2(4),
     "PRIM" VARCHAR2(4),
     "UNIT" NUMBER,
     "SEC_REF_1" NUMBER,
     "SECN_1" VARCHAR2(88),
     "SEC_REF_2" NUMBER,
     "SECN_2" VARCHAR2(88),
     "SEC_REF_3" NUMBER,
     "SECN_3" VARCHAR2(88),
     "SEC_REF_4" NUMBER,
     "SECN_4" VARCHAR2(88),
     "SEC_REF_5" NUMBER,
     "SECN_5" VARCHAR2(88),
     "SEC_REF_6" NUMBER,
     "SECN_6" VARCHAR2(88),
     "SEC_REF_7" NUMBER,
     "SECN_7" VARCHAR2(88),
     "SEC_REF_8" NUMBER,
     "SECN_8" VARCHAR2(88),
     "SEC_REF_9" NUMBER,
     "SECN_9" VARCHAR2(88),
     "SEC_REF_10" NUMBER,
     "SECN_10" VARCHAR2(88),
     "SEC_REF_11" NUMBER,
     "SECN_11" VARCHAR2(88),
     "SEC_REF_12" NUMBER,
     "SECN_12" VARCHAR2(88),
     "SEC_REF_13" NUMBER,
     "SECN_13" VARCHAR2(88),
     "SEC_REF_14" NUMBER,
     "SECN_14" VARCHAR2(88),
     "SEC_REF_15" NUMBER,
     "SECN_15" VARCHAR2(88),
     "SEC_REF_16" NUMBER,
     "SECN_16" VARCHAR2(88),
     "SEC_REF_17" NUMBER,
     "SECN_17" VARCHAR2(88),
     "SEC_REF_18" NUMBER,
     "SECN_18" VARCHAR2(88),
     "SEC_REF_19" NUMBER,
     "SECN_19" VARCHAR2(88),
     "SEC_REF_20" NUMBER,
     "SECN_20" VARCHAR2(88),
     "SEC_REF_21" NUMBER,
     "SECN_21" VARCHAR2(88),
     "SEC_REF_22" NUMBER,
     "SECN_22" VARCHAR2(88),
     "SEC_REF_23" NUMBER,
     "SECN_23" VARCHAR2(88),
     "SEC_REF_24" NUMBER,
     "SECN_24" VARCHAR2(88),
     "SEC_REF_25" NUMBER,
     "SECN_25" VARCHAR2(88),
     "SEC_REF_26" NUMBER,
     "SECN_26" VARCHAR2(88),
     "SEC_REF_27" NUMBER,
     "SECN_27" VARCHAR2(88),
     "SEC_REF_28" NUMBER,
     "SECN_28" VARCHAR2(88),
     "SEC_REF_29" NUMBER,
     "SECN_29" VARCHAR2(88),
     "SEC_REF_30" NUMBER,
     "SECN_30" VARCHAR2(88),
     "SEC_REF_31" NUMBER,
     "SECN_31" VARCHAR2(88),
     "SEC_REF_32" NUMBER,
     "SECN_32" VARCHAR2(88),
     "SEC_REF_33" NUMBER,
     "SECN_33" VARCHAR2(88),
     "SEC_REF_34" NUMBER,
     "SECN_34" VARCHAR2(88),
     "SEC_REF_35" NUMBER,
     "SECN_35" VARCHAR2(88),
     "SEC_REF_36" NUMBER,
     "SECN_36" VARCHAR2(88),
     "SEC_REF_37" NUMBER,
     "SECN_37" VARCHAR2(88),
     "SEC_REF_38" NUMBER,
     "SECN_38" VARCHAR2(88),
     "SEC_REF_39" NUMBER,
     "SECN_39" VARCHAR2(88),
     "SEC_REF_40" NUMBER,
     "SECN_40" VARCHAR2(88),
     "SEC_REF_41" NUMBER,
     "SECN_41" VARCHAR2(88),
     "SEC_REF_42" NUMBER,
     "SECN_42" VARCHAR2(88),
     "SEC_REF_43" NUMBER,
     "SECN_43" VARCHAR2(88),
     "SEC_REF_44" NUMBER,
     "SECN_44" VARCHAR2(88),
     "SEC_REF_45" NUMBER,
     "SECN_45" VARCHAR2(88),
     "SEC_REF_46" NUMBER,
     "SECN_46" VARCHAR2(88),
     "SEC_REF_47" NUMBER,
     "SECN_47" VARCHAR2(88),
     "SEC_REF_48" NUMBER,
     "SECN_48" VARCHAR2(88),
     "SEC_REF_49" NUMBER,
     "SECN_49" VARCHAR2(88),
     "SEC_REF_50" NUMBER,
     "SECN_50" VARCHAR2(88),
     "SEC_REF_51" NUMBER,
     "SECN_51" VARCHAR2(88),
     "SEC_REF_52" NUMBER,
     "SECN_52" VARCHAR2(88),
     "SEC_REF_53" NUMBER,
     "SECN_53" VARCHAR2(88),
     "SEC_REF_54" NUMBER,
     "SECN_54" VARCHAR2(88),
     "SEC_REF_55" NUMBER,
     "SECN_55" VARCHAR2(88),
     "SEC_REF_56" NUMBER,
     "SECN_56" VARCHAR2(88),
     "SEC_REF_57" NUMBER,
     "SECN_57" VARCHAR2(88),
     "SEC_REF_58" NUMBER,
     "SECN_58" VARCHAR2(88),
     "SEC_REF_59" NUMBER,
     "SECN_59" VARCHAR2(88),
     "SEC_REF_60" NUMBER,
     "SECN_60" VARCHAR2(88),
     "SEC_REF_61" NUMBER,
     "SECN_61" VARCHAR2(88),
     "SEC_REF_62" NUMBER,
     "SECN_62" VARCHAR2(88),
     "SEC_REF_63" NUMBER,
     "SECN_63" VARCHAR2(88),
     "SEC_REF_64" NUMBER,
     "SECN_64" VARCHAR2(88),
     "SEC_REF_65" NUMBER,
     "SECN_65" VARCHAR2(88),
     "SEC_REF_66" NUMBER,
     "SECN_66" VARCHAR2(88),
     "SEC_REF_67" NUMBER,
     "SECN_67" VARCHAR2(88),
     "SEC_REF_68" NUMBER,
     "SECN_68" VARCHAR2(88),
     "SEC_REF_69" NUMBER,
     "SECN_69" VARCHAR2(88),
     "SEC_REF_70" NUMBER,
     "SECN_70" VARCHAR2(88),
     "SEC_REF_71" NUMBER,
     "SECN_71" VARCHAR2(88),
     "SEC_REF_72" NUMBER,
     "SECN_72" VARCHAR2(88),
     "SEC_REF_73" NUMBER,
     "SECN_73" VARCHAR2(88),
     "SEC_REF_74" NUMBER,
     "SECN_74" VARCHAR2(88),
     "SEC_REF_75" NUMBER,
     "SECN_75" VARCHAR2(88),
     "SEC_REF_76" NUMBER,
     "SECN_76" VARCHAR2(88),
     "SEC_REF_77" NUMBER,
     "SECN_77" VARCHAR2(88),
     "SEC_REF_78" NUMBER,
     "SECN_78" VARCHAR2(88),
     "SEC_REF_79" NUMBER,
     "SECN_79" VARCHAR2(88),
     "SEC_REF_80" NUMBER,
     "SECN_80" VARCHAR2(88),
     "SEC_REF_81" NUMBER,
     "SECN_81" VARCHAR2(88),
     "SEC_REF_82" NUMBER,
     "SECN_82" VARCHAR2(88),
     "SEC_REF_83" NUMBER,
     "SECN_83" VARCHAR2(88),
     "SEC_REF_84" NUMBER,
     "SECN_84" VARCHAR2(88),
     "SEC_REF_85" NUMBER,
     "SECN_85" VARCHAR2(88),
     "SEC_REF_86" NUMBER,
     "SECN_86" VARCHAR2(88),
     "SEC_REF_87" NUMBER,
     "SECN_87" VARCHAR2(88),
     "SEC_REF_88" NUMBER,
     "SECN_88" VARCHAR2(88),
     "SEC_REF_89" NUMBER,
     "SECN_89" VARCHAR2(88),
     "SEC_REF_90" NUMBER,
     "SECN_90" VARCHAR2(88),
     "SEC_REF_91" NUMBER,
     "SECN_91" VARCHAR2(88),
     "SEC_REF_92" NUMBER,
     "SECN_92" VARCHAR2(88),
     "SEC_REF_93" NUMBER,
     "SECN_93" VARCHAR2(88),
     "SEC_REF_94" NUMBER,
     "SECN_94" VARCHAR2(88),
     "SEC_REF_95" NUMBER,
     "SECN_95" VARCHAR2(88),
     "SEC_REF_96" NUMBER,
     "SECN_96" VARCHAR2(88),
     "SEC_REF_97" NUMBER,
     "SECN_97" VARCHAR2(88),
     "SEC_REF_98" NUMBER,
     "SECN_98" VARCHAR2(88),
     "SEC_REF_99" NUMBER,
     "SECN_99" VARCHAR2(88),
     "SEC_REF_100" NUMBER,
     "SECN_100" VARCHAR2(88),
     "SEC_REF_101" NUMBER,
     "SECN_101" VARCHAR2(88),
     "SEC_REF_102" NUMBER,
     "SECN_102" VARCHAR2(88),
     "SEC_REF_103" NUMBER,
     "SECN_103" VARCHAR2(88),
     "SEC_REF_104" NUMBER,
     "SECN_104" VARCHAR2(88),
     "SEC_REF_105" NUMBER,
     "SECN_105" VARCHAR2(88),
     "SEC_REF_106" NUMBER,
     "SECN_106" VARCHAR2(88),
     "SEC_REF_107" NUMBER,
     "SECN_107" VARCHAR2(88),
     "SEC_REF_108" NUMBER,
     "SECN_108" VARCHAR2(88),
     "SEC_REF_109" NUMBER,
     "SECN_109" VARCHAR2(88),
     "SEC_REF_110" NUMBER,
     "SECN_110" VARCHAR2(88),
     "SEC_REF_111" NUMBER,
     "SECN_111" VARCHAR2(88),
     "SEC_REF_112" NUMBER,
     "SECN_112" VARCHAR2(88),
     "SEC_REF_113" NUMBER,
     "SECN_113" VARCHAR2(88),
     "SEC_REF_114" NUMBER,
     "SECN_114" VARCHAR2(88),
     "SEC_REF_115" NUMBER,
     "SECN_115" VARCHAR2(88),
     "SEC_REF_116" NUMBER,
     "SECN_116" VARCHAR2(88),
     "SEC_REF_117" NUMBER,
     "SECN_117" VARCHAR2(88),
     "SEC_REF_118" NUMBER,
     "SECN_118" VARCHAR2(88),
     "SEC_REF_119" NUMBER,
     "SECN_119" VARCHAR2(88),
     "SEC_REF_120" NUMBER,
     "SECN_120" VARCHAR2(88),
     "SEC_REF_121" NUMBER,
     "SECN_121" VARCHAR2(88),
     "SEC_REF_122" NUMBER,
     "SECN_122" VARCHAR2(88),
     "SEC_REF_123" NUMBER,
     "SECN_123" VARCHAR2(88),
     "SEC_REF_124" NUMBER,
     "SECN_124" VARCHAR2(88),
     "SEC_REF_125" NUMBER,
     "SECN_125" VARCHAR2(88),
     "SEC_REF_126" NUMBER,
     "SECN_126" VARCHAR2(88),
     "SEC_REF_127" NUMBER,
     "SECN_127" VARCHAR2(88),
     "SEC_REF_128" NUMBER,
     "SECN_128" VARCHAR2(88),
     "SEC_REF_129" NUMBER,
     "SECN_129" VARCHAR2(88),
     "SEC_REF_130" NUMBER,
     "SECN_130" VARCHAR2(88),
     "SEC_REF_131" NUMBER,
     "SECN_131" VARCHAR2(88),
     "SEC_REF_132" NUMBER,
     "SECN_132" VARCHAR2(88),
     "SEC_REF_133" NUMBER,
     "SECN_133" VARCHAR2(88),
     "SEC_REF_134" NUMBER,
     "SECN_134" VARCHAR2(88),
     "SEC_REF_135" NUMBER,
     "SECN_135" VARCHAR2(88),
     "SEC_REF_136" NUMBER,
     "SECN_136" VARCHAR2(88),
     "SEC_REF_137" NUMBER,
     "SECN_137" VARCHAR2(88),
     "SEC_REF_138" NUMBER,
     "SECN_138" VARCHAR2(88),
     "SEC_REF_139" NUMBER,
     "SECN_139" VARCHAR2(88),
     "SEC_REF_140" NUMBER,
     "SECN_140" VARCHAR2(88),
     "SEC_REF_141" NUMBER,
     "SECN_141" VARCHAR2(88),
     "SEC_REF_142" NUMBER,
     "SECN_142" VARCHAR2(88),
     "SEC_REF_143" NUMBER,
     "SECN_143" VARCHAR2(88),
     "SEC_REF_144" NUMBER,
     "SECN_144" VARCHAR2(88),
     "SEC_REF_145" NUMBER,
     "SECN_145" VARCHAR2(88),
     "SEC_REF_146" NUMBER,
     "SECN_146" VARCHAR2(88),
     "SEC_REF_147" NUMBER,
     "SECN_147" VARCHAR2(88),
     "SEC_REF_148" NUMBER,
     "SECN_148" VARCHAR2(88),
     "SEC_REF_149" NUMBER,
     "SECN_149" VARCHAR2(88),
     "SEC_REF_150" NUMBER,
     "SECN_150" VARCHAR2(88),
     "SEC_REF_151" NUMBER,
     "SECN_151" VARCHAR2(88),
     "SEC_REF_152" NUMBER,
     "SECN_152" VARCHAR2(88),
     "SEC_REF_153" NUMBER,
     "SECN_153" VARCHAR2(88),
     "SEC_REF_154" NUMBER,
     "SECN_154" VARCHAR2(88),
     "SEC_REF_155" NUMBER,
     "SECN_155" VARCHAR2(88),
     "SEC_REF_156" NUMBER,
     "SECN_156" VARCHAR2(88),
     "SEC_REF_157" NUMBER,
     "SECN_157" VARCHAR2(88),
     "SEC_REF_158" NUMBER,
     "SECN_158" VARCHAR2(88),
     "SEC_REF_159" NUMBER,
     "SECN_159" VARCHAR2(88),
     "SEC_REF_160" NUMBER,
     "SECN_160" VARCHAR2(88),
     "SEC_REF_161" NUMBER,
     "SECN_161" VARCHAR2(88),
     "SEC_REF_162" NUMBER,
     "SECN_162" VARCHAR2(88),
     "SEC_REF_163" NUMBER,
     "SECN_163" VARCHAR2(88),
     "SEC_REF_164" NUMBER,
     "SECN_164" VARCHAR2(88),
     "SEC_REF_165" NUMBER,
     "SECN_165" VARCHAR2(88),
     "SEC_REF_166" NUMBER,
     "SECN_166" VARCHAR2(88),
     "SEC_REF_167" NUMBER,
     "SECN_167" VARCHAR2(88),
     "SEC_REF_168" NUMBER,
     "SECN_168" VARCHAR2(88),
     "SEC_REF_169" NUMBER,
     "SECN_169" VARCHAR2(88),
     "SEC_REF_170" NUMBER,
     "SECN_170" VARCHAR2(88),
     "SEC_REF_171" NUMBER,
     "SECN_171" VARCHAR2(88),
     "SEC_REF_172" NUMBER,
     "SECN_172" VARCHAR2(88),
     "SEC_REF_173" NUMBER,
     "SECN_173" VARCHAR2(88),
     "SEC_REF_174" NUMBER,
     "SECN_174" VARCHAR2(88),
     "SEC_REF_175" NUMBER,
     "SECN_175" VARCHAR2(88),
     "SEC_REF_176" NUMBER,
     "SECN_176" VARCHAR2(88),
     "SEC_REF_177" NUMBER,
     "SECN_177" VARCHAR2(88),
     "SEC_REF_178" NUMBER,
     "SECN_178" VARCHAR2(88),
     "SEC_REF_179" NUMBER,
     "SECN_179" VARCHAR2(88),
     "SEC_REF_180" NUMBER,
     "SECN_180" VARCHAR2(88),
     "SEC_REF_181" NUMBER,
     "SECN_181" VARCHAR2(88),
     "SEC_REF_182" NUMBER,
     "SECN_182" VARCHAR2(88),
     "SEC_REF_183" NUMBER,
     "SECN_183" VARCHAR2(88),
     "SEC_REF_184" NUMBER,
     "SECN_184" VARCHAR2(88),
     "SEC_REF_185" NUMBER,
     "SECN_185" VARCHAR2(88),
     "SEC_REF_186" NUMBER,
     "SECN_186" VARCHAR2(88),
     "SEC_REF_187" NUMBER,
     "SECN_187" VARCHAR2(88),
     "SEC_REF_188" NUMBER,
     "SECN_188" VARCHAR2(88),
     "SEC_REF_189" NUMBER,
     "SECN_189" VARCHAR2(88),
     "SEC_REF_190" NUMBER,
     "SECN_190" VARCHAR2(88),
     "SEC_REF_191" NUMBER,
     "SECN_191" VARCHAR2(88),
     "SEC_REF_192" NUMBER,
     "SECN_192" VARCHAR2(88),
     "SEC_REF_193" NUMBER,
     "SECN_193" VARCHAR2(88),
     "SEC_REF_194" NUMBER,
     "SECN_194" VARCHAR2(88),
     "SEC_REF_195" NUMBER,
     "SECN_195" VARCHAR2(88),
     "SEC_REF_196" NUMBER,
     "SECN_196" VARCHAR2(88),
     "SEC_REF_197" NUMBER,
     "SECN_197" VARCHAR2(88),
     "SEC_REF_198" NUMBER,
     "SECN_198" VARCHAR2(88),
     "SEC_REF_199" NUMBER,
     "SECN_199" VARCHAR2(88),
     "SEC_REF_200" NUMBER,
     "SECN_200" VARCHAR2(88),
     "SEC_REF_201" NUMBER,
     "SECN_201" VARCHAR2(88),
     "SEC_REF_202" NUMBER,
     "SECN_202" VARCHAR2(88),
     "SEC_REF_203" NUMBER,
     "SECN_203" VARCHAR2(88),
     "SEC_REF_204" NUMBER,
     "SECN_204" VARCHAR2(88),
     "SEC_REF_205" NUMBER,
     "SECN_205" VARCHAR2(88),
     "SEC_REF_206" NUMBER,
     "SECN_206" VARCHAR2(88),
     "SEC_REF_207" NUMBER,
     "SECN_207" VARCHAR2(88),
     "SEC_REF_208" NUMBER,
     "SECN_208" VARCHAR2(88)
   );Thank you for any help/advice.
Elie
Edited by: EEG on Jun 12, 2011 2:09 PM

So, is there some limit to the number of columns one can have in a "classic" or interactive report?Yes. See Oracle® Application Express Application Builder User's Guide Release 4.0, Appendix B: Oracle Application Express Limits.
Any idea why I would be getting this error?No, but I've replicated it in APEX 4.0.2.00.07 on 11.2.0.1.0 EE using a table of 420 <tt>varchar2(88)</tt> columns:
>
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "50C9BDC0AA1AEF0EB272E9158B2117B4" application checksum = "0"
>
Happens whether using <tt>select *</tt> or including all column names in the query. (I know you don't want to type all the column names, but I'd never use <tt>select *</tt> in a production application: always use a proper column list. You can get one without typing by drag-and-drop of a table in most IDEs, or a query from <tt>user_tab_columns</tt>.)
I hit the problem at 274 columns. Such an arbitrary number leads me to think that the problem is not one of the number of columns per se, but is due to some other limit (possibly a 32K VARCHAR2/RAW buffer somewhere).
Workaround:
Updates to the report column attributes are actually being saved, and you can navigate them using the Page Definition tree view as described in Appendix B.
Getting More Help:
This is probably a bug. If you have a support agreement with Oracle raise an SR with Oracle Support.
Also:
<li>Search the forum using the "ORA-20503" code and other possible terms to see if there's anything relevant. I had a quick look but the only thread in this context recommended an upgrade on an Oracle 9 DB version that's not compatible with APEX 4.0.
<li>To get the attention of the Oracle APEX team or anyone else who may know more about this problem than we do, edit your original post and change the Subject to be more specific about the actual nature of the problem: <em>BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns</em>, and include your database version/edition and the definition of the <tt>PVTAB</tt> table.
Finally:
Somebody's bound to ask, so we might as well get started:
<li>Why so many columns?
<li>What requirement is this trying to fulfil?

ORA-32034: unsupported use of WITH clause-issue

hello all,
i am facing some issue when i use with clause and union all operator.
i have created a dummy code to solve this problem..
my code is ----------
with dept_1 as
(select deptno d1 from detp9 where deptno = 20)
select empno from emp9 e,dept_d1 where e.empno = dept_1.d1
UNION ALL
with dept_1 as
(select deptno d2 from detp9 where deptno = 30)
select empno from emp9 e,dept_d2 where e.empno = dept_2.d2.
when i ran this i gort a message-
ORA-32034: unsupported use of WITH clause.
please help me to solve this iisue..
when i ran it separatly without using union/union all it ran sucessfully..
thanks in advance..

923315 wrote:
hello all,
i am facing some issue when i use with clause and union all operator.
i have created a dummy code to solve this problem..
my code is ----------
with dept_1 as
(select deptno d1 from detp9 where deptno = 20)
select empno from emp9 e,dept_d1 where e.empno = dept_1.d1
UNION ALL
with dept_1 as
(select deptno d2 from detp9 where deptno = 30)
select empno from emp9 e,dept_d2 where e.empno = dept_2.d2.
when i ran this i gort a message-
ORA-32034: unsupported use of WITH clause.
please help me to solve this iisue..
when i ran it separatly without using union/union all it ran sucessfully..
thanks in advance..Well, i don't see anything about these queries that makes sense.
You are essentially joining emp and dept on EMPNO to DEPTNO ... that doesn't usually make any sense.
How about you step back from the query which is almost certainly incorrect, and explain your tables, their data and what you need as output?
Cheers,

ORA-03115 error when accessing CLOB in servlet

hi, all
I stored some html files in Oracle as CLOB, I need to select one file out. I did this in normal java file, it worked pretty well, I can print this file out to terminal. Now I tried to use servlet to do this, post this file in browser, I got this error when I tried executeQuery("select *.. "):
java.sql.SQLException: ORA-03115: unsupported network datatype or representation
I guess this is JDBC driver problem, I used Tomcat3.2.4. Can anyone give me some hint? Thanks a lot!

you can try the lastest one to see if that helps
http://otn.oracle.com/software/tech/java/sqlj_jdbc/content.html

ORA-01461 error using jdbc 10.2.0.1.0

I am using the oracle jdbc 10.2.0.1.0 ( the latest version) and oracle 10g (10.1.0.4.0) database. Sometimes, the error "ORA-01461: can bind a LONG value only for insert into a LONG column' if I use a java program to insert record to a table containing a 'long raw' field. Previously, the same java program work well with oracle 9i.
Interestingly, the 'ORA-01461' only SOMETIMES happen. If the problem appears, I need to rename the table and create a new one and then the data can be inserted.

After 3 days of deep analysis on my project, now I have a clear idea of the problem.
As you can find on web, newer versions of Oracle drivers for Java have the possibility to set property :
oracle.jdbc.RetainV9LongBindBehavior=true
it's considered the fix for this bug, and effectively it seems to work.
But also with this setting, drivers have one more bug!+
The problem appears in these conditions:
- Application tries to save a string into a LONG column database
- String length is more than 4000 bytes
- String has less than 4000 characters (it's possible in case of international characters, which takes more than 1 byte)
With these conditions, we have again error ORA-01461: can bind a LONG value only for insert into a LONG column.
It seems that drivers evaluate string length before saving it, and consider it as LONG only for 4000+ characters. The bug is just on this check, that must consider length in bytes, according to database character encoding, and not simply for character length.
As workaround, on my application we added a logic that appends spaces (" ") until total characters are at least 4001. In this way, string is considered correctly as LONG and storage works correctly.
The check is something similar to this:
if(value.getBytes("UTF-8").length > 4000 && value.length() < 4000)
for(int x = value.length(); x<=4000; x++)
value += " "; // always use StringBuffer for appending
This workaround works, but it's clear that it can be not acceptable in many cases, for application funcionalities. In my specific bug, it has been very useful.
My customer opened a ticket to Oracle, asking for solution of this bug. I will wait for Oracle answer.
Finally, we have to say that Oracle warned to not use anymore LONG datatype: it's deprecated since v8.0.
Bye guys ;-)
Edited by: user12274810 on 25-nov-2009 12.04

ORA-03115 on call Procedure with VARARRAY of STRUCT as IN and separate OUT

Hello,
I am using Oracle 11.2 and odbc6.jar of Manifest: 11.2.0.2.0 an getting the following exception
java.sql.SQLException: ORA-03115:
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:837)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:445)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:523)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:204)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1007)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1315)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3576)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3677)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4714)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1374)
The Procedure is defined as following :
CREATE OR REPLACE PROCEDURE TEST_ORACLE_PROCEDUR (
I_CLOB IN CLOB,
O_CLOB OUT CLOB,
O_CURSOR1 OUT SYS_REFCURSOR,
O_CURSOR2 OUT SYS_REFCURSOR,
I_TESTPARAM IN NESTED_KEY_VAL_PAIR,
O_TESTPARAM OUT NESTED_KEY_VAL_CLOB,
I_BLOB IN BLOB ,
O_BLOB OUT BLOB ,
I_DATE IN DATE ,
O_DATE OUT DATE ,
I_ARRAY IN ARRAY_NESTED_KEY_VAL_PAIR,
O_ARRAY OUT ARRAY_NESTED_KEY_VAL_PAIR
Currently I am working for VarArray support in our enviroment. This error did not occour when removing the both Array parameters from SP.
The type ARRAY_NESTED_KEY_VAL_PAIR is defined as follows:
1.)
ARRAY_NESTED_KEY_VAL_PAIR AS VARRAY(6) OF NESTED_KEY_VAL_PAIR;
2.)
NESTED_KEY_VAL_PAIR AS OBJECT
MyStruct KEY_VAL_PAIR_REC,
MyVarchar VARCHAR2(100)
3.)
KEY_VAL_PAIR_REC AS OBJECT (
KEY VARCHAR2(400),
VAL VARCHAR2(4000)
I am passing an array of oracle.sql.STRUCT of type NESTED_KEY_VAL_PAIR as following:
ArrayDescriptor descriptor = ArrayDescriptor.createDescriptor( typeName , connection );
new oracle.sql.ARRAY(descriptor, connection, vector.toArray() );
, where vector is the vector of STRUCT. The STRUCT Objects are created right as same as there are evaluated for I_TESTPARAM .
-> So I think there must be some driver support issue of this ARRAY of STRUCT of STRUCT .. may at IN or OUT context..
very Thanks for Help.
rgs Andre, Berlin
Edited by: user10426085 on 25.08.2011 03:36

OK here the complete definition of the procedure :
CREATE OR REPLACE PROCEDURE TEST_ORACLE_PROCEDUR (
        I_CLOB      IN      CLOB,
        O_CLOB         OUT CLOB,
        O_CURSOR1      OUT SYS_REFCURSOR,
        O_CURSOR2      OUT SYS_REFCURSOR,
        I_TESTPARAM IN      NESTED_KEY_VAL_PAIR,
        O_TESTPARAM    OUT NESTED_KEY_VAL_CLOB,
        I_BLOB      IN      BLOB ,
        O_BLOB         OUT BLOB ,
        I_DATE      IN      DATE ,
        O_DATE         OUT DATE ,
        I_ARRAY     IN      ARRAY_NESTED_KEY_VAL_PAIR,
        O_ARRAY        OUT ARRAY_NESTED_KEY_VAL_PAIR
) IS
BEGIN
   BEGIN
         /* Test IN CLOB, IN UserDefindedType , IN BLOB */
              INSERT INTO TEST_ORACLE_PROCEDUR_TABLE (CLOBTEST,USERTYPETEST, BLOBTEST , DATETEST , ARRAYTEST ) VALUES( I_CLOB , I_TESTPARAM , I_BLOB , I_DATE , I_ARRAY );
              COMMIT;
         /* Test OUT CLOB by IN CLOB-Value */
              SELECT CLOBTEST     into O_CLOB       FROM TEST_ORACLE_PROCEDUR_TABLE;
         /* Test OUT BLOB by IN BLOB-Value */
              SELECT BLOBTEST     into O_BLOB       FROM TEST_ORACLE_PROCEDUR_TABLE;
         /* Test OUT DATE by IN DATE-Value */
              SELECT DATETEST     into O_DATE       FROM TEST_ORACLE_PROCEDUR_TABLE;
         /* Test OUT userdefined Type by self constructed object */
              O_TESTPARAM := NESTED_KEY_VAL_CLOB( KEY_VAL_PAIR_REC( 'myKey_1' , 'myValue_1' ) , 'myVarcharValue' , O_CLOB );
         /* Test OUT ARRAY Type */
              SELECT ARRAYTEST    into O_ARRAY      FROM TEST_ORACLE_PROCEDUR_TABLE;
         /* Test Out Cursor    */
              OPEN O_CURSOR1 FOR SELECT DUMMY FROM DUAL;
              OPEN O_CURSOR2 FOR SELECT CLOBTEST,USERTYPETEST, BLOBTEST, DATETEST , ARRAYTEST FROM TEST_ORACLE_PROCEDUR_TABLE;
    /* return */
         RETURN;
   EXCEPTION
     WHEN OTHERS THEN
         raise_application_error(-20001,'An error was encountered - '||SQLCODE||' -ERROR- '||SQLERRM);
   END;
END;

Using Clob with TopLink 9.0.4.5 and Oracle 10g RAC

I am trying to store an XML file in a Clob type field of a DB table using TopLink 9.0.4.5 and Oracle 10g RAC and need some guidance about how to do it. I got some directions to start it with the Tip "How-To: Map Large Objects (LOBs) to Oracle Databases with OracleAS TopLink" but still need some more helps.
When using the Oracle JDBC OCI driver, the tip gives the code block for a Clob field:
DirectToField scriptMapping = new DirectToField();
scriptMapping.setAttributeName("script");
scriptMapping.setFieldName("IMAGE.SCRIPT");
descriptor.addMapping(scriptMapping);
As I understand, TopLink creates instances of the Descriptor class at run time for each of the descriptor files and stores them in a database session, where is the proper place (in SessionEvent of TopLinkSessionEventHandler?) for me to get a reference to such an instance of my Descriptor class in Java code so that I can add the above mentioned additional Mapping? Are the above String values of "script" and "IMAGE.SCRIPT" predefined in TopLink API? Can I accomplish the same thing just using the TopLink Workbench tool instead? If yes, please advise the detailed steps to do so.
The tip also states to call the following code in case of using Clob:
DatabaseLogin login = session.getLogin();
login.useStringBinding();
Should the above 2 lines of code be called after the following lines of code?
SessionManager sessionManager = SessionManager.getManager();
Server serverSession = (Server)sessionManager.getSession("MY_SESSION_NAME");
Besides the above extra coding for the Session and Descriptor Mapping, is there any special handling in between Data model and DB table mapping? Can I map a Java String type to a DB Clob field using the Direct-to-field mapping?
Appreciate any help.

Never mind ....... I had already figured it out .....

TNS Ora-12532 error When connecting with Db11 running in the VM

I created a virtual machine from the PVM Entrerprise Linux 5 64 bits and db11g.
Inside the virtual Machine the sqlplus system/manager1@VDB11 is working well.
The tnsping 172.20.0.33 is working well too.
But from the other external machine using oracle 11g client these command are not working: Tns Ora-12532 error.
What to do?
Thanks

my virtual machine: vm1 have an static ip address 172.20.0.33
the oracle listener is was configured with the same ip
in the virtual machine : vm1 the /etc/hosts file content is:
127.0.0.1 localhost.localdomain
172.20.0.33 virtualdb11
in the tnsnames.ora file in the virtual machine i have a service:
VDB11 ...( host=172.20.0.33) (port=1521)
under console connection with my virtual machine vm1 the command : sqlplus system/manager1@VDB11 is working well
but when i working in an other external machine , where the tnsnames.ora have an entry:
VDB11 ...(host=172.20.0.33)......
the ping command : ping 172.20.0.33 is working well
but sqlplus system/manager1@VDB11 is not work and return the error:
ora-12532 tns

ORA-02068 errors using a DB Link between source and remote db servers

I get the following error when I query a table or view on a remote database using a db link:
13:58:13 SQL> /
COUNT(*)
92862
13:58:16 SQL> /
select count(*) from rp_adm.users
ERROR at line 1:
ORA-02068: following severe error from DURS.CONDEVD1.WORLD
ORA-03113: end-of-file on communication channel
14:03:53 SQL>
As you can see, the query works sometimes and then if I wait about 5 minutes, I get the error. If I run the query immediately after the error, it works fine.
rp_adm.users is a view which within the DDL it queries a remote database using a db link.
Any one have any idea how to get rid of this ORA-02068 and ORA-03113 error????

By the way, this is running on Solaris 10 OS running Oracle Database 10g Enterprise Edition Release 10.1.0.5.0 - 64bit databases.
Edited by: user10340463 on Nov 3, 2008 11:21 AM - Sorry for the dup. Browser screwing up.

Using OS_ROLES with JDBC Driver

I can't get my JDBC connections to pick-up the OS ROLES I have configured. Does the OCI driver support OS Roles?
I'm using 10gR2 with latest JDBC drivers, running on Windows XP.
If I connect locally with sqlplus then the roles are established correctly. However, establishing the 'equivalent' connection from Java yields a user with no ROLEs defined, i.e. they are not being picked-up from the OS.
Is there a trick or is it not supported?
I believe I have the database and the OS groups setup correctly and, as I say, it works fine with a sqlplus connection.
If anyone either knows how to do, or knows that its not supported then please let me know.
Thanks,
Richard.

to my knowledge this is not supported in jdbc specification2.0 and 3.0 and jdbc drivers are complied to this standards.
connecting with sql client is entirely different with the connection using java thin drivers.
thanks,
Ruchir

Can we use SQLScripts with jdbc?

can we use the SQLScripts with jdbc?
if possible please give some information on that.

no, Its not possible
prem

Error using JTextArea with JScrollPane

hi,
I am using JTextArea with JScrollpane. I am getting a problem in selecting the text in text area. I am searching for some text in the text area and selecting it if search successful. The problem is that the the scrollbar position didnt set to the correct location. So sometime the text selected is not visible in the scrolpane. Any help regarding this will be highly appreciated.
Regards
Danish

What about sth like this:Rectangle r = textarea.modelToView(textarea.getSelectionStart());
scrollpane.scrollRectToVisible(r);Just a guess, no idea whether it works.

ORA-00601 Error using JDBC, Oracle 8i on Linux

Hello,
Spatial is considering using Oracle as its database platform. I was assigned
the task of benchmarking the two platforms. So, I downloaded the latest copy
of Oracle for Linux, version 8.1.6.1.0 ( 8i Enterprise Edition Release 2 ).
I'm using RedHat 6.2, with a 2.2.14-5.0smp kernel. I ran the installer, set
up the databases, and everything seemed to be running quite nicely. I copied
a table and its data from mysql to Oracle, and wrote a java program to
benchmark the two. This java program takes command line arguments, the first
one being the connection URL, the second being the number of threads to
start, the third being the number of operations to complete for each thread.
So, if you pass it connection 35 35, it will open 35 threads, and each
thread will then execute 35 selects, inserts, and updates. These are
hard-coded queries, but they mimic the functionality currently in
production.
Oracle bombs on the update. I turned tracing on, and tried it again, with
the same result. Here's an excerpt from one of the trace files:
*** SESSION ID:(4.1) 2000-06-21 16:36:48.937
kvotenlg: epc_collect failed. EPC error: -1073751468.
CDF: /u01/app/oracle/product/8.1.6/otrace/admin/cdf/styorap0
FDF: /u01/app/oracle/product/8.1.6/otrace/admin/fdf/oracled.fdf
kvotenlg: epc_collect failed. ctx:368.
I was not able to find any information regarding this error. However, this
message ( or one very similar ) appeared in every trace file. I get the
following at the end of the pmon_xxxx.trc file:
Load Indicator not supported by OS !
*** 2000-06-21 17:42:19.122
error 601 detected in background process
And, the following in the alert_sid.log file:
Wed Jun 21 17:42:19 2000
PMON: terminating instance due to error 601
Instance terminated by PMON, pid = 3797
I made the assumption that this error was actually ORA-00601, and took a
peek on the internet for relavent information. The canned error message is
"PMON process runs into lock conflict trying to recovery processes". I found
someone who had a similar problem, who suggested setting mts_max_dispatchers
in the initsid.ora file to 1. However, this did not work.
Basically, when Oracle crashes, the java program is trying to update one
column in 1225 rows, 35 times, for 35 threads. The java exception is below.
java.sql.SQLException: No more data to read from socket
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java)
at oracle.jdbc.dbaccess.DBError.check_error(DBError.java)
at oracle.jdbc.ttc7.MAREngine.unmarshalUB1(MAREngine.java)
at oracle.jdbc.ttc7.MAREngine.unmarshalSB1(MAREngine.java)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java)
at
oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java)
at
oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java)
at
oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithBatch(OracleStatement.java)
at
oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java
at
oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java)
at ned.util.database.DBHammerThread.run(DBHammerThread.java:78)
Has anyone seen this kind of behavior before? Is this merely a
misconfiguration on my part? Help! :)
-ned

Sorry for the long delay in reply. I was using the thin client driver. However, when I switched to the oci8 driver, not only did I observe a 300% increase in speed, but this bizarre occurrence disappeared. I did find one issue with the oci8 driver, as follows.
In this thread program, if I created a connection in the main program before any of the threads were instantiated, and when the first thread attempted to create a connection, it would produce a segmentation fault. This behavior was very easy to replicate, and it did not matter whether or not I close the original connection. This problem was circumvented by moving the code in the "main" program to create its connection after the child threads had created theirs.

ORA-03115 Error using CLOB with JDBC

Similar Messages

Maybe you are looking for