ORA-01002 in a report

Hi,
Windows NT
Report 2.5
Oracle7
I have a simple repport with 2 querys:
Q1:
SELECT SUB_DIS.DISTRICT_CODE DISTRICT_CODE
,DISTRICT.NAME NAME
,SUB_DIS.NAME NAME1
,SUB_DIS.CODE CODE2
FROM SUB_DISTRICTS SUB_DIS
,DISTRICTS DISTRICT
WHERE DISTRICT.CODE = SUB_DIS.DISTRICT_CODE;
Q2:
SELECT LIC.SUB_DIS_CODE SUB_DIS_CODE
,LIC.SUB_DIS_DISTRICT_CODE SUB_DIS_DISTRICT_CODE
,MTRA.ID ID
,MTRA.MTRA_DATE MTRA_DATE
,MTRA.LIC_DIE LIC_DIE
,MTRA.DISCOUNT_AMOUNT DISCOUNT_AMOUNT
,MTRA.RESET_AMOUNT RESET_AMOUNT
,MTRA.RESET_AMOUNT-MTRA.DISCOUNT_AMOUNT NET_VALUE
FROM METER_LICENCES LIC
,METER_TRANSACTIONS MTRA
WHERE MTRA.LIC_DIE = LIC.DIE
AND MTRA.TRANSACTION_TYPE IN ('40', '41')
and MTRA.MTRA_DATE between NVL(to_date(:p_start_date, 'DD MON RRRR'), to_date( '01 JAN 1997', 'DD MON RRRR'))
and NVL(to_date(:cg$p_sysdate, 'DD MON RRRR'), sysdate)
The tow querys are linked by:
code2 = sub_dis_code
district_code= sub_dis_district_code
I get this error when I run the report for a specifique range date (from 01/11/06 to 01/12/06) If I ask for the sames report using a different period it seems to work.
Regards,
Message was edited by:
ASkika

What error? You did not indicate

Similar Messages

ORA-01002: fetch out of sequence error when using Oracle Thin Driver 9i with Weblogic 6.1

The simple program below is a client that executes a SELECT query -
there are 13 rows in the table, of which 10 are printed when I run the
program, then after that the ORA-01002 error is reported. I am not
doing anything with LOBs, or updates. I've tried putting
con.setAutoCommit(false) as well, but that does not do anything.
Why am I getting this error? Can anyone help.
Thanks
-H
Context ctx = null;
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL,
"t3://127.0.0.1:7001");
PreparedStatement stmt = null;
ResultSet rs = null;
UserTransaction ut = null;
try {
ctx = new InitialContext(ht);
javax.sql.DataSource ds
= (javax.sql.DataSource) ctx.lookup ("jtaXADS");
java.sql.Connection conn = ds.getConnection();
// You can now use the conn object to create
// Statements and retrieve result sets:
ut = (UserTransaction)
ctx.lookup("javax.transaction.UserTransaction");
ut.begin();
stmt = conn.prepareStatement("select firstname,surname from
EMPLOYEE ");
stmt.executeQuery();
rs = stmt.getResultSet();
// Close the statement and connection objects when you are finished:
while (rs.next())
System.out.println("Result is " + rs.getString("firstname") + " " +
rs.getString("surname"));
ut.commit();
stmt.close();
conn.close();
catch (Exception e) {
e.printStackTrace();
// a failure occurred
finally {
try {ctx.close();
rs.close();}
catch (Exception e) {
// a failure occurred
e.printStackTrace();

Thanks everybody.
I have tried this, calling ut.begin() first before getConnection,
however no difference. However the problem goes away if I call
stmt.setFetchSize(100);
But I would prefer not to have to code this in every time!!!
I see there is a setting within Weblogic Admin console to see the
row-prefetch, but that is already set to 45 rows, so why do have to
explicitly call stmt.setFetchSize(100)!!!
Thanks
-H
"Carl Lawstuen" <[email protected]> wrote in message news:<[email protected]>...
Agreed. The transaction must start before the connection. This is what
is most likely causing the error.
"Nils Winkler" <[email protected]> wrote in message
news:[email protected]...
Hi,
one more thing: The UserTransaction has to be started before you obtain
the connection, not after.
Nils
Humphrey wrote:
The simple program below is a client that executes a SELECT query -
there are 13 rows in the table, of which 10 are printed when I run the
program, then after that the ORA-01002 error is reported. I am not
doing anything with LOBs, or updates. I've tried putting
con.setAutoCommit(false) as well, but that does not do anything.
Why am I getting this error? Can anyone help.
Thanks
-H
Context ctx = null;
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL,
"t3://127.0.0.1:7001");
PreparedStatement stmt = null;
ResultSet rs = null;
UserTransaction ut = null;
try {
ctx = new InitialContext(ht);
javax.sql.DataSource ds
= (javax.sql.DataSource) ctx.lookup ("jtaXADS");
java.sql.Connection conn = ds.getConnection();
// You can now use the conn object to create
// Statements and retrieve result sets:
ut = (UserTransaction)
ctx.lookup("javax.transaction.UserTransaction");
ut.begin();
stmt = conn.prepareStatement("select firstname,surname from
EMPLOYEE ");
stmt.executeQuery();
rs = stmt.getResultSet();
// Close the statement and connection objects when you are finished:
while (rs.next())
System.out.println("Result is " + rs.getString("firstname") + " " +
rs.getString("surname"));
ut.commit();
stmt.close();
conn.close();
catch (Exception e) {
e.printStackTrace();
// a failure occurred
finally {
try {ctx.close();
rs.close();}
catch (Exception e) {
// a failure occurred
e.printStackTrace();
============================
[email protected]

Oracle Report raises ORA-01002 Fetch out of sequence

ORA-01002 Fetch out of sequence in runtime execution of
oracle report 3.0 and 2.5 in client/server environment.
The same sql query works in sqlplus without any problem.
If I change the criteria (where clause) the error sometime
disappear. I can't explain this weird behaviour.
Oracle server version is 7.1.5 on Digital VMS.
Any Help will be welcome.
null

ORA-01002 Fetch out of sequence in runtime execution of
oracle report 3.0 and 2.5 in client/server environment.
The same sql query works in sqlplus without any problem.
If I change the criteria (where clause) the error sometime
disappear. I can't explain this weird behaviour.
Oracle server version is 7.1.5 on Digital VMS.
Any Help will be welcome.
null

BUG: preview report template errors with ORA-01002

I've checked on my local install and on apex.oracle.com. I go into the Templates of Shared Components and filter on the Report Templates. Although the preview icon is displayed to allow me to preview the template, I always receive "ORA-01002: fetch out of sequence" on an error page. The only types of Report Templates I have are of type "Generic Columns" so not sure if the problem exists with "Named Columns."
Can anyone confirm this or correct me on this?
Shane.

I wouldn't mind piggy-backing this to ask if the Report Template "shortcut" links at the top of the page can be updated to account for all sections that are now a part of the Report Template. "Before Each Row" and "After Each Row" sections are not listed in the shortcuts. There are also two shortcuts listed as "Before" and "After" which should probably be relabeled.
Shane.

Bug and Fix: Report Template Preview displays ORA-01002

Hi, omniscient All!
Let me share some knowledge with you. There is an old APEX bug:
BUG: preview report template errors with ORA-01002
Report Template Preview/Copy Error
Template Preview Error:
You can definitely see it in 4.0, 4.1, 4.2, 4.2.1 versions: open any database application in AppBuilder, go to Shared Components→Templates, move cursor on Some Report Template row, click Preview Icon. Voilà:
report error:
ORA-01002: fetch out of sequenceI looked into Template Preview region's source and have found next WWV_RENDER_REPORT3.show call:
wwv_render_report3.show(
    p_query => '
select 1 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 2 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 3 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 4 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 5 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 6 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual
order by 1',
    p_row_template_id => :f4000_p245_id,
    p_region_id => 88449328191587806
);I have no wish to go deep into my further investigation, therefore I just call a cause: APEX Team, you forgot to set the value of P_PLUG_SOURCE_TYPE parameter.
Workaround: While APEX Team will making a patch, those who can't wait it should fix it manually by executing next code:
update &APEX_SCHEMA.wwv_flow_page_plugs
   set plug_source = q'{wwv_render_report3.show(
    p_query => '
select 1 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 2 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 3 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 4 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 5 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 6 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual
order by 1',
    p_row_template_id => :f4000_p245_id,
    p_region_id => 88449328191587806,
    p_plug_source_type => 'SQL_QUERY'
where id = 14562627207747006
/APEX_SCHEMA is schema where APEX was installed.
Good luck,
Alex
Edited by: tiPPLer on 14.02.2013 17:14

I wouldn't mind piggy-backing this to ask if the Report Template "shortcut" links at the top of the page can be updated to account for all sections that are now a part of the Report Template. "Before Each Row" and "After Each Row" sections are not listed in the shortcuts. There are also two shortcuts listed as "Before" and "After" which should probably be relabeled.
Shane.

ORA-01002 fetch out of sequence after suspend/resume transaction

Environment
- WebLogic 10.0.2.0
- Oracle thin driver 10.2.0.2.0
I iterate throw elements of ResultSet. During that global transaction is suspended and resumed. Then invoking of next on ResultSet caused following exception “java.sql.SQLException: ORA-01002: fetch out of sequence”.
I found that similar problem was reported in older WLS version ORA-01002 fetch out of sequence
Do you have any idea how I can fix it?
Best regards,
Adam

OK, to get to the complete explanation, I suggest you open
an official support case. And I'm not trying to avoid the issue,
but fetching millions of rows out of the database to process
them outside is the wrong way to go. I highly recommend
DBMS-side logic in stored procedures to do the raw data processing.

ORA-01002

Hi!.
I've got a problem with Reports 2.5. Sometimes when I call a Report from Forms an error success "ORA-01002 --> fetch out of sequence" and I don4t know what i have to do in order to resolve it.
Thanks.

Hi,
I've seen this problem resolved in 2.5 by upping the number of cursors in OPEN_CURSORS in the init.ora for the database. You can also try setting the commandline parameter NONBLOCKSQL to NO as that has worked in other cases. In 3.0 this is set to no by default, but in 2.5, the default is yes.
Hope that helps,
Toby

ORA-01002-Error in Select ... for update

I would like to insert CLOB in a table (VP_EVENTS) with a primary key (eventid) with the following code:
String content = "AAAAAAAAAAAAABBBBBBBBBBXXX";
PreparedStatement cs = this.con.prepareStatement("INSERT INTO vp_events (eventid,term,participant)
VALUES (?,?,empty_clob())");
//Register IN-Parameter
cs.setInt(1, 1);
cs.setInt(2, 1);
cs.setTimestamp(3, new java.sql.Timestamp( System.currentTimeMillis() ));
//Execute statement
cs.execute();
cs.close();
Statement stmt = con.createStatement();
ResultSet clobLocatorSet = stmt.executeQuery( "SELECT PARTICIPANT FROM VP_EVENTS WHERE EVENTID=1 FOR UPDATE");
// Get the CLOB-locator
if (clobLocatorSet.next())
oracle.sql.CLOB clob =
((oracle.jdbc.driver.OracleResultSet)
clobLocatorSet).getCLOB(1);
// Write CLOB-Data
// The first parameter to plsql_write, is // the offset from which to start
// writing, and the second parameter is the // data to be written.
// plsql_length(), returns the length of // the data in the CLOB column
countCLOB = clob.plsql_write(
0,content.toCharArray());
At the execution-point of the "Select for Update"-statement the oracle thin driver throws the Error "Fetch out of sequence ORA-01002".
What's wrong?

Connection conn = DriverManager.getConnection ("jdbc racle:thin:@myhost:1521:ORCL","scott", "tiger");
conn.setAutoCommit(false);
Statement stmt = conn.createStatement ();
null

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?

ERROR (ORA-01002) when Ioading a table by UPDATE/INSERT

I get the error message ORA-01002 ( Fetch out of sequence ) when I am loading a table by UPDATE/INSERT.
At de Runtime Audit Viewer the process of loading update a number of register, in that case 44.050 and to the left register I get the error message that I show above.

Can you please give us some details about your source and targets. I have used UPDATE/INSERT but I did not get this kind of error.
rgds
-AP

Why does this snippet produce ORA-01002 in 10g, but works fine in 9i.

While migrating from 9i to 10g, we found that one of our processes failed with ORA-01002: fetch out of sequence. Debugging produced the following example:
DECLARE
CURSOR A IS SELECT Dummy FROM Dual FOR UPDATE;
BEGIN
FOR B IN A LOOP COMMIT; END LOOP;
END;This code works in 9i, but produces an EXCEPTION in 10g:
SQL> SELECT Banner FROM V$Version;
BANNER
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
PL/SQL Release 9.2.0.8.0 - Production
CORE    9.2.0.8.0       Production
TNS for Linux: Version 9.2.0.8.0 - Production
NLSRTL Version 9.2.0.8.0 - Production
SQL> DECLARE
2   CURSOR A IS SELECT Dummy FROM Dual FOR UPDATE;
3 BEGIN
4   FOR B IN A LOOP COMMIT; END LOOP;
5 END;
6 /
PL/SQL procedure successfully completed.
SQL> SELECT Banner FROM V$Version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod
PL/SQL Release 10.2.0.4.0 - Production
CORE    10.2.0.4.0      Production
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
SQL> DECLARE
2   CURSOR A IS SELECT Dummy FROM Dual FOR UPDATE;
3 BEGIN
4   FOR B IN A LOOP COMMIT; END LOOP;
5 END;
6 /
DECLARE
ERROR at line 1:
ORA-01002: fetch out of sequence
ORA-06512: at line 4The documentation on the error explains this case in both 9i and more explicitly 10g. Should this have produced the EXCEPTION in 9i as well? Or, is there something else about 10g?

e.g. a FOR row IN cursor LOOP is now implicit using a bulk fetch operation (100 rows or so).This was also my first guess, but said optimization does not take place when the cursor is defined FOR UPDATE:
SQL> exec dbms_application_info.set_client_info(0)
PL/SQL procedure successfully completed.
SQL> declare
cursor a is select last_name, set_client_info(rownum) from employees;
begin
for b in a loop
    exit;
end loop;
end;
PL/SQL procedure successfully completed.
SQL> select sys_context('userenv','client_info') from dual
SYS_CONTEXT('USERENV','CLIENT_INFO')
100
1 row selected.
Now with FOR UPDATE:
SQL> exec dbms_application_info.set_client_info(0)
PL/SQL procedure successfully completed.
SQL> declare
cursor a is select last_name, set_client_info(rownum) from employees for update;
begin
for b in a loop
    exit;
end loop;
end;
PL/SQL procedure successfully completed.
SQL> select sys_context('userenv','client_info') from dual
SYS_CONTEXT('USERENV','CLIENT_INFO')
1
1 row selected.

Warning ORA-01002, ORA-06502 AND ORA-12899

Hi All,
When iam executing my mapping iam facing the following warninigs.
Name      Status      Log
MAP_     Warning     CursorFetchMapTerminationRTV20007
MAP_     Warning     ORA-01002: fetch out of sequence
ORA-02063: preceding line from link
MAP_Warning     ORA-06502: PL/SQL: numeric or value error: character string buffer too small
MAP_Warning     ORA-12899: value too large for column %s (actual: %s, maximum: %s)
ORA-02063: preceding line from link
Further to inform you that, in source and target the data type size is same.
How can i resolve it
Thanks in advance.

I mean to say select while executing it from Database you can pin-point the exact line which cause error.
cheers
Nawneet

Error ORA-01002: fetch out of sequence

Hi all,
I created 3 cursors. The scenario is like following :
Begin Cur A
Begin FOR xx IN Cur B LOOP
Begin FOR xx IN Cur C LOOP
End LOOP Cur C;
commit;
End LOOP Cur B;
End Cur A;
When i run the program its display error ORA-01002: fetch out of sequence.
The objective of my program is to insert into table and commit every transaction.
Kindly share info with me why this error happened.
TQ.
tim

Tim,
Refer to the following:
ORA-01002: fetch out of sequence
Cause: This error means that a fetch has been attempted from a cursor which is no longer valid.
Note that a PL/SQL cursor loop implicitly does fetches, and thus may also cause this error. There are a number of possible causes for this error, including:
1) Fetching from a cursor after the last row has been retrieved and the ORA-1403 error returned.
2) If the cursor has been opened with the FOR UPDATE clause, fetching after a COMMIT has been issued will return the error.
3) Rebinding any placeholders in the SQL statement, then issuing a fetch before reexecuting the statement.
Action:
1) Do not issue a fetch statement after the last row has been retrieved - there are no more rows to fetch.
2) Do not issue a COMMIT inside a fetch loop for a cursor that has been opened FOR UPDATE.
3) Reexecute the statement after rebinding, then attempt to fetch again.
HTH,
Thierry
Edited by: Thierry H. on May 4, 2011 12:30 PM Reformatting

Java.sql.SQLException: ORA-01002: fetch out of sequence

We are getting 'Fetch out of sequence' error whrn we try to execute a 'for update' query.
We are first inserting values into the DLX_ASSET table and if there is image to be inserted the particualr row is fetched using the query. The insert query inserts values into the database.
'SELECT HIGH_RES_IMAGE FROM DLX_ASSET WHERE ASSET_ID ="+assetId+ " FOR UPDATE'. While executing this query we are getting this exception. This is not happening when we are trying it from our local machine. But its happening everywhere else where its deployed.
We are using Websphere Application Server 6 and Oracle 9i. We have set autommit to false before the method is called and are commiting the transaction only after the whole set of queries are executed.
Please see below the code snippet,
                              /* UPDATE HIGH RESOLUTION IMAGE INTO DLX_ASSET TABLE */
                              logger.logInfo("inside IF condition ,,,,,,,,,,,"+assetId);
                              String query ="SELECT HIGH_RES_IMAGE FROM DLX_ASSET WHERE ASSET_ID ="+assetId+ " FOR UPDATE ";
                              logger.logInfo("QUERY is...."+query);
                              logger.logInfo("Connection closed:"+ con.isClosed());
                              psHighResObj =(OraclePreparedStatement) con.prepareStatement(query);
                              logger.logInfo("inside updating high res AFTER prepare statement"+psHighResObj);
                              rsHighRes = (OracleResultSet) psHighResObj.executeQuery();                              logger.logInfo("inside updating high res image 1");
                              while (rsHighRes.next()) {
                                   logger.logInfo("inside while high res image 2");
                                   highResImg =(OrdImage)rsHighRes.getCustomDatum(1,OrdImage.getFactory());
                                   highResImg.loadDataFromInputStream(assetCustomTo.getHighResolutionImageIn());
                                   assetCustomTo.getHighResolutionImageIn().close();
                                   logger.logInfo("before update high res");
                                   UPDATE_QRY = "UPDATE DLX_ASSET SET HIGH_RES_IMAGE = ? WHERE ASSET_ID=" + assetId;
                                   stmt1 =(OraclePreparedStatement) con.prepareCall(UPDATE_QRY);
                                   highResImg.setSource(assetCustomTo.getHighresFileType(),"",assetCustomTo.getSys_file_name1());
                                   highResImg.setContentLength(Integer.parseInt(assetCustomTo.getHighresFileSize()));
                                   highResImg.setProperties();
                                   logger.logInfo(" after update query asset id: " + assetId);
                                   logger.logInfo(" query high res:: " + UPDATE_QRY);
                                   stmt1.setCustomDatum(1, highResImg);
                                   stmt1.execute();
                                   logger.logInfo("after update high res");
                              //checking if thumbnail is present: if bulk upload thumb nail won't be present
the exception is occuring in the line 'rsHighRes = (OracleResultSet) psHighResObj.executeQuery();'
This is exception trace
java.sql.SQLException: ORA-01002: fetch out of sequence
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java(Inlined Compiled Code))
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java(Compiled Code))
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java(Compiled Code))
at oracle.jdbc.ttc7.TTC7Protocol.fetch(TTC7Protocol.java:1198)
at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2400)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2672)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:527)
at com.deluxe.imax.dataaccess.impl.extended.TelevisionAssetCustomDAOImpl.createWebElectronicTrailersAsset(Unknown Source)
at com.deluxe.imax.business.television.ejb.TelevisionFacadeJBean.createWebElectronicTrailersAsset(Unknown Source)
at com.deluxe.imax.business.television.handler.TelevisionHandler.createWebElectronicTrailersAsset(Unknown Source)
at com.deluxe.imax.business.television.action.WebNewAction.processExecute(Unknown Source)
at com.deluxe.imax.business.framework.BaseAction.execute(Unknown Source)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1284)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1241)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:136)
at com.deluxe.imax.business.framework.security.SecurityFilter.doFilter(Unknown Source)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:142)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:121)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:82)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:671)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3003)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:221)
at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:210)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1958)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:88)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:472)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.ja
Please share your feedback.
Thanks in advance!
Edited by: Sanu Sasidharan on May 11, 2011 4:26 AM

Hi Peter,
We tried pointing to the same database from local as well as QA. Works from local but not from QA.
assetId is the generated primary key in the same method.
Yes the exception is thrown from execute statement itself. the logger put just after the execute is not coming.
This is the method
public boolean createWebElectronicTrailersAsset(TelevisionResultDTO[] teleResultDTO, OracleConnection con) throws DAOException {
          methodName ="createWebElectronicTrailersAsset(TelevisionResultDTO[] teleResultDTO,OracleConnection con) :: ";
          //Value to be returned by method
          boolean createInd = false;
          OraclePreparedStatement psHighResObj = null;
          OraclePreparedStatement psThumbnailObj = null;
          OracleResultSet rsHighRes = null;
          OracleResultSet rsThumbnail = null;
          PreparedStatement psmt = null;
          OraclePreparedStatement stmt1 = null;
          OraclePreparedStatement stmt2 = null;
          OrdImage highResImg = null;
          OrdImage thumbnailImg = null;
          ImaxGroupsTO groupsTO = null;
          try {
               long tvAssetId = 0;
               long assetId = 0;
               long cst_dwnld_asset_id = 0;
               AssetCustomTO assetCustomTo = null;
               AssetCustomDownloadTO assetCustDwnldTO = null;
               CustomTVAssetTO tvAssetTo = null;
               String DLX_ASSET_QRY = "";
               String UPDATE_QRY = "";
               String DLX_ASSET_TV_QRY = "";
               String DLX_CUSTOM_DOWNLOAD_ASSET = "";
               int k = 1;
               for (int iCount = 0; iCount < teleResultDTO.length; iCount++) {
                    tvAssetId = (int) OraclePKGenerator.getInstance().getKey(InternalConstants.TV_ASSET_SEQUENCE);
                    assetId =(long) OraclePKGenerator.getInstance().getKey(InternalConstants.ASSET_SEQUENCE);
                    assetCustomTo = teleResultDTO[iCount].getAssetCustomTO();
                    tvAssetTo = teleResultDTO[iCount].getTv_Asset();
                    groupsTO= teleResultDTO[iCount].getGroupsTO();
                    if (assetCustomTo.getHighResolutionImageIn() != null) {
                         DLX_ASSET_QRY ="INSERT INTO DLX_ASSET("
                                                  + "ASSET_ID,"
                                                  + "CREATED_BY,"
                                                  + "CREATED_DATE,"
                                                  + "REVISED_BY,"
                                                  + "REVISED_DATE,"
                                                  + "FILE_NAME,"
                                                  + "FILE_SIZE,"
                                                  + "FILE_TYPE,"
                                                  + "SYS_FILE_NAME,"
                                                  + "HIGH_RES_IMAGE,"
                                                  + "THUMBNAIL_IMAGE,"
                                                  + "ASSET_STATUS_ID,"
                                                  + "DMX_PART1_REF,"
                                                  + "DMX_PRODUCT_ID_REF,"
                                                  + "DMX_PRODUCT_DESC_REF,"
                                                  + "ASSET_AVAIL_1_IND,"
                                                  + "DMX_PART_2,"
                                                  + "DMX_PRODUCT_2,"
                                                  + "DMX_PRODUCT_DESC_2,"
                                                  + "ASSET_AVAIL_2_IND,"
                                                  + "EFFECTIVE_DATE,"
                                                  + "EXPIRATION_DATE,"
                                                  + "FILE_NAME1,"
                                                  + "SYS_FILE_NAME1,"
                                                  + "ASSET_TYPE_ID,"
                                                  + "MATERIALS_CATEGORY,"
                                                  + "PART_1_NOTES,"
                                                  + "PART_2_NOTES,"
                                                  + "PHY_ORDER_STATUS)"
                                                  + "VALUES (?,?,SYSDATE,?,SYSDATE,?,?,?,?,ORDSYS.ORDImage.init(),"
                                                  +" ORDSYS.ORDImage.init(),?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)";
                    }else if(){
// condition if images are not uploaded
                         psmt = con.prepareStatement(DLX_ASSET_QRY);
                         k=1;
                         psmt.setLong(k++, assetId);
                         psmt.setString(k++, assetCustomTo.getCreated_by());
                         psmt.setString(k++, assetCustomTo.getRevised_by());
                         if(assetCustomTo.getAssetTextIn()!=null ){
                              psmt.setString(k++, assetCustomTo.getFile_name());
                              psmt.setString(k++, assetCustomTo.getFile_size());
                              psmt.setString(k++, assetCustomTo.getFile_type());
                              psmt.setString(k++, assetCustomTo.getSys_file_name());
                              /* UPLOAD PREVIEW VIDEO FILE INTO FILE SYSTEM .....*/
                              Util.upLoadFile(assetCustomTo.getAssetTextIn(),assetCustomTo.getSys_file_name());
                         }else if(assetCustomTo.getAssetTextIn()==null && assetCustomTo.getSys_file_name() != null
                                        && assetCustomTo.getSys_file_name().trim().length() != 0){
                                   psmt.setString(k++, assetCustomTo.getFile_name());
                                   psmt.setString(k++, assetCustomTo.getFile_size());
                                   psmt.setString(k++, assetCustomTo.getFile_type());
                                   psmt.setString(k++, assetCustomTo.getSys_file_name());
                         } else{
                              psmt.setNull(k++,Types.VARCHAR);
                              psmt.setNull(k++,Types.VARCHAR);
                              psmt.setNull(k++,Types.VARCHAR);
                              psmt.setNull(k++,Types.VARCHAR);
                         psmt.setLong(k++, assetCustomTo.getAsset_status_id());
                         if(assetCustomTo.getDmx_product_desc_1()!=null && assetCustomTo.getDmx_product_desc_1().trim().length()!=0){
                              psmt.setLong(k++, assetCustomTo.getDmx_part_1());
                              psmt.setLong(k++, assetCustomTo.getDmx_productId_1());
                              psmt.setString(k++, assetCustomTo.getDmx_product_desc_1());
                              psmt.setString(k++, assetCustomTo.getAsset_order_status_1());
                         }else{
                              psmt.setNull(k++,Types.INTEGER);
                              psmt.setNull(k++,Types.INTEGER);
                              psmt.setNull(k++,Types.VARCHAR);
                              psmt.setNull(k++,Types.VARCHAR);
                         if(assetCustomTo.getDmx_product_desc_2()!=null && assetCustomTo.getDmx_product_desc_2().trim().length()!=0){
                              psmt.setLong(k++, assetCustomTo.getDmx_part_2());
                              psmt.setLong(k++, assetCustomTo.getDmx_productId_2());
                              psmt.setString(k++, assetCustomTo.getDmx_product_desc_2());
                              psmt.setString(k++, assetCustomTo.getAsset_order_status_2());
                         }else{
                              psmt.setNull(k++,Types.INTEGER);
                              psmt.setNull(k++,Types.INTEGER);
                              psmt.setNull(k++,Types.VARCHAR);
                              psmt.setNull(k++,Types.VARCHAR);
                         if(assetCustomTo.getEffectiveDate()!=null){
                              psmt.setTimestamp(k++, assetCustomTo.getEffectiveDate());
                         }else{
                              psmt.setNull(k++,Types.TIMESTAMP);
                         if(assetCustomTo.getExpirationDate()!=null){
                              psmt.setTimestamp(k++, assetCustomTo.getExpirationDate());
                         }else{
                              psmt.setNull(k++,Types.TIMESTAMP);
                         psmt.setString(k++, assetCustomTo.getHighresFileName());
                         if(assetCustomTo.getSys_file_name1()!=null && assetCustomTo.getSys_file_name1().trim().length()!=0){
                              psmt.setString(k++, assetCustomTo.getSys_file_name1());
                         }else{
                              psmt.setNull(k++, Types.VARCHAR);
                         psmt.setLong(k++, assetCustomTo.getAsset_type_id());
                         psmt.setLong(k++, assetCustomTo.getMaterialCategory());
                         if(assetCustomTo.getPart_notes_1()!=null && assetCustomTo.getPart_notes_1().trim().length()!=0){
                              psmt.setString(k++, assetCustomTo.getPart_notes_1());
                         }else{
                              psmt.setNull(k++,Types.VARCHAR);
                         if(assetCustomTo.getPart_notes_2()!=null && assetCustomTo.getPart_notes_2().trim().length()!=0){
                              psmt.setString(k++, assetCustomTo.getPart_notes_2());
                         }else{
                              psmt.setNull(k++,Types.VARCHAR);
                         if(assetCustomTo.getDmx_product_desc_1()!=null){
                              psmt.setLong(k++,assetCustomTo.getPhy_asset_status());
                         }else{
                              psmt.setNull(k++,Types.INTEGER);
                         psmt.execute();
                         if (assetCustomTo.getHighResolutionImageIn() != null) {
                              /* UPDATE HIGH RESOLUTION IMAGE INTO DLX_ASSET TABLE */
                              logger.logInfo("inside IF condition ,,,,,,,,,,,"+assetId);
                              String query ="SELECT HIGH_RES_IMAGE FROM DLX_ASSET WHERE ASSET_ID ="+assetId+ " FOR UPDATE ";
                              psHighResObj =(OraclePreparedStatement) con.prepareStatement(query);
                              logger.logInfo("inside updating high res AFTER prepare statement"+psHighResObj);
                              rsHighRes = (OracleResultSet) psHighResObj.executeQuery();
                              while (rsHighRes.next()) {
                                   highResImg =(OrdImage)rsHighRes.getCustomDatum(1,OrdImage.getFactory());
                                   highResImg.loadDataFromInputStream(assetCustomTo.getHighResolutionImageIn());
                                   assetCustomTo.getHighResolutionImageIn().close();
                                   UPDATE_QRY = "UPDATE DLX_ASSET SET HIGH_RES_IMAGE = ? WHERE ASSET_ID=" + assetId;
                                   stmt1 =(OraclePreparedStatement) con.prepareCall(UPDATE_QRY);
                                   highResImg.setSource(assetCustomTo.getHighresFileType(),"",assetCustomTo.getSys_file_name1());
                                   highResImg.setContentLength(Integer.parseInt(assetCustomTo.getHighresFileSize()));
                                   highResImg.setProperties();
                                   stmt1.setCustomDatum(1, highResImg);
                                   stmt1.execute();
The connection in the method is passed from the service layer.
Thanks
Edited by: Sanu Sasidharan on May 12, 2011 2:30 AM

ORA-01002: fetch out of sequence! HELP NEEDED!

Hi, can someone help us (me)!
Application: Sun-ConcordeXAL 2.6
Clients: Sun-Oracle-7.2.3
Database: Linux-Oracle-8.0.5.1
(PS! if clients software change to XAL 2.7 and Oracle 8.0.4
then we get same error)
Maybe database configuration or client oracle configuration
problem we dont'no ...
HELP US(Me)
Andri
null

Andri Karniol (guest) wrote:
: Hi, can someone help us (me)!
: Application: Sun-ConcordeXAL 2.6
: Clients: Sun-Oracle-7.2.3
: Database: Linux-Oracle-8.0.5.1
: (PS! if clients software change to XAL 2.7 and Oracle 8.0.4
: then we get same error)
: Maybe database configuration or client oracle configuration
: problem we dont'no ...
: HELP US(Me)
: Andri
I met the same error message when I upgrade the database from
SCO-7.2.2.4 to Sun-7.3.4. It seems some Pro*C program can not
work anymore. It give me ORA-01002: fetch out of sequence.
Any idea in this case?
Rgds Johnny
null

ORA-01002 in a report

Similar Messages

Maybe you are looking for