Problem with APEX 4.0 - "ORA-20001: Error with: GRANT CREATE CLUSTER "

I have a workspace which I've succesfully created with schema A.
However when i try to assign an additional schema to it, schema B, I get the following error message :-
"ORA-20001: Error with: GRANT CREATE CLUSTER TO "BI_SOURCES" ORA-01031: insufficient privileges"
i've tried granting "create cluster with admin option' to users A,B,anonymous AND APEX_040000. FLOWS_030000 already has these privileges.
Anybody any ideas ?
regs
johnnie
Edited by: johnnie d on 31-Aug-2011 10:58

I have experience the similiar problem. The error message: Invalid exist/not exist condition: ORA 2001 Query must begin with Select or With.
I have home page and concept review report page below home page. And Concept review form under the report page. The error is display in all of the three pages. I checked carefully and still not able to find where the error come from. Can you please help? All the report region and form region have the select statement, is it from the LOVs? Home
Concept review report
Concept reveiw Form(for detail info)
Thank you!

Similar Messages

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-20001:Error fetching column value:Query must begin with SELECT or WITH

Hi all,
I have implemented an application with a master-detail form using Apex 3.1.2 and I imported that to Apex 3.2 on different server. Everything else seems to be fine except when I add detail record (clicking on Add Rows), I am getting following error.
=================
report error:
ORA-20001: Error fetching column value: ORA-20001: Query must begin with SELECT or WITH
====================
Both the databases have same version 10gR2. I didn't make any change after importing it as well. Can someone let me know what could be the issue? Thanks in advance.
SHY

May we know your first name?
Can you put the application in your workspace on apex.oracle.com so we can take a look?
Scott

ORA-20001: error 29th ORA-24344 When creating a workspace

Hi,
I just installed APEX 4.0 on 10g (10.2.0.4).
When I tried to create a new workspace, at the last step (after clicking "Create Workspace" button), it fails with the following error.
ORA-20001: error 29th ORA-24344: success with compilation error
Error provisioning test.
I could not find any errors in PLSQL debug error, and in DBA_ERRORS table.
Could you help me to fix this problem? I ran utlrp.sql to make sure we don't have invalid objects. And I read the installation log and found no errors. XDB, OWA installed.
I have another APEX 4.0 instance on 11g R2, and it works fine.
Thanks
Jung
Edited by: jwryoo on Jul 15, 2010 8:37 AM

thanks.
Yes, that's I already checked and confirmed that the privilege is granted.
DBA_ERRORS did not show any errors owned by APEX% users.
But I did see some errors owned by XDB.
PL/SQL: Item ignored
PLS-00201: identifier 'UTL_FILE' must be declared
PL/SQL: Statement ignored
PLS-00201: identifier 'DBMS_LOB' must be declared
It seems the DB has revoked some public access for security reasons.
So, I am trying to ask DBA to grant the privileges to XDB.

Master Detail report report error: ORA-20001: Error fetching column

Hi All,
I am a newbie in apex and try to create a master detail form, where the detail is displayed as a report.
After inserting a new row in the master form i like to create the detail. It displays then ORA-01403: no data found
I also insert in the database table the details. If i want to edit then it shows the following report error:
ORA-20001: Error fetching column value: ORA-01403: no data found
Can anyone help me, because i am struggling for a week with this problem.

Your problem seems to be related to the usage of primary keys. You have to look into that and get more details.
Denes Kubicek
http://deneskubicek.blogspot.com/
http://www.opal-consulting.de/training
http://apex.oracle.com/pls/otn/f?p=31517:1
http://www.amazon.de/Oracle-APEX-XE-Praxis/dp/3826655494
-------------------------------------------------------------------

ORA-20001 Error when creating a new application

Hi,
I am trying to create a new application of an existing table in the database and I get the following error. The application is created using the wizard (app type Database, from scratch, Report and Form page)
ORA-20001: Unable to create modules. ORA-20001: Create pages error. ORA-20001: Unable to create form page. ORA-20001: Error page=2 item="P2_NON_ORACLE_EMPLOYEE_SPEAKER" id="1975288532127294112" ORA-20001: Error page=2 item="P2_NON_ORACLE_EMPLOYEE_SPEAKER" id="1975288532127294112" has same name as existing application-level item. ORA-0000: normal, successful completion
The table I am creating the app on is defined like this:
CREATE TABLE "TABLE_1"
   (    "ID" NUMBER,
        "SESSION_EXTERNAL_PAPER" VARCHAR2(30),
        "OWNER_CFP_SUBMITTER1_FULL_NA" VARCHAR2(255),
        "OWNER_CFP_SUBMITTER1_COMPANY" VARCHAR2(255),
        "STATUS" VARCHAR2(30),
        "SESSION_ID" NUMBER,
        "TITLE" VARCHAR2(255),
        "ABSTRACT" VARCHAR2(4000),
        "SESSION_TYPE" VARCHAR2(30),
        "SESSION_CATEGORY" VARCHAR2(30),
        "STREAM" VARCHAR2(30),
        "PRIMARY_TRACK" VARCHAR2(255),
        "OPTIONAL_TRACK" VARCHAR2(255),
        "CROSS_STREAM_TRACK" VARCHAR2(30),
        "SUPPORTING_VIDEO" VARCHAR2(4000),
        "ATTENDEE_ROLE" VARCHAR2(255),
        "TO_RATING" VARCHAR2(30),
        "TO_COMMENTS" VARCHAR2(4000),
        "COMMENTS" VARCHAR2(4000),
        "ORACLE_PARTNERNETWORK" VARCHAR2(30),
        "IS_YOUR_OPN_MEMBERSHIP_UNDER_A" VARCHAR2(255),
        "ORACLE_PARTNER_TYPE" VARCHAR2(255),
        "OPN_MEMBERSHIP_LEVEL" VARCHAR2(30),
        "ORACLE_REGION_BASED" VARCHAR2(30),
        "ORACLE_VALIDATED_INTEGRATION" VARCHAR2(30),
        "HAS_YOUR_COMPANY_ACHIEVED_SPEC" VARCHAR2(4000),
        "PLEASE_DESCRIBE_THE_VALUE_OF_O" VARCHAR2(4000),
        "INCLUDE_CASE_STUDY" VARCHAR2(30),
        "PROVIDE_NAME_OF_THE_CUSTOMER_F" VARCHAR2(255),
        "PLEASE_PROVIDE_A_BRIEF_DESCRIP" VARCHAR2(4000),
        "NON_ORACLE_EMPLOYEE_SPEAKER1_F" VARCHAR2(255),
        "NON_ORACLE_EMPLOYEE_SPEAKER1_C" VARCHAR2(255),
        "ORACLE_EMPLOYEE_SPEAKER1_FULL" VARCHAR2(255),
        "ORACLE_EMPLOYEE_SPEAKER1_COMPA" VARCHAR2(255),
        "NON_ORACLE_EMPLOYEE_SPEAKER2_F" VARCHAR2(255),
        "NON_ORACLE_EMPLOYEE_SPEAKER2_C" VARCHAR2(255),
        "ORACLE_EMPLOYEE_SPEAKER2_FULL" VARCHAR2(255),
        "ORACLE_EMPLOYEE_SPEAKER2_COMPA" VARCHAR2(255),
        "NON_ORACLE_EMPLOYEE_SPEAKER3_F" VARCHAR2(255),
        "NON_ORACLE_EMPLOYEE_SPEAKER3_C" VARCHAR2(255),
        "ORACLE_EMPLOYEE_SPEAKER3_FULL" VARCHAR2(255),
        "ORACLE_EMPLOYEE_SPEAKER3_COMPA" VARCHAR2(255),
        "NON_ORACLE_EMPLOYEE_SPEAKER4_F" VARCHAR2(255),
        "NON_ORACLE_EMPLOYEE_SPEAKER4_C" VARCHAR2(255),
        "ORACLE_EMPLOYEE_SPEAKER4_FULL" VARCHAR2(255),
        "ORACLE_EMPLOYEE_SPEAKER4_COMPA" VARCHAR2(255),
        "CREATED" DATE,
        "CREATED_BY" VARCHAR2(50),
        "LAST_UPDATE" DATE,
        "LAST_UPDATED_BY" VARCHAR2(50),
         CONSTRAINT "OOW_PAPER_PK" PRIMARY KEY ("ID") ENABLE
   ) ;I am using APEX version 4.0.2.00.07
Any idea what could be wrong and what can be done to resolve the problem?
Cheers,
Andy

Thanks! Never thought of that.
--Andy

ORA-20001 error when creating Tabular Form or Form and Report

Whenever I try and add a Tabular Form or Form and Report to my application i am getting the following error at the end of the Wizard.
ORA-20001: Unable to create updateable report. ORA-20001: Error creating shortcut id="" ORA-00001: unique constraint (APEX_030200.WWV_FLOW_SHORTCUT_IDX1) violatedIt's not a problem I have seen when building other apps and clearly I have managed to corrupt this application somehow.
I have loaded the problem onto apex.oracle.com for those that have access. The application number is 20325.
Any help would be very much appreciated.
Cheers Shunt

Thanks! Never thought of that.
--Andy

Error in mru internal routine: ORA-20001: Error in MRU: row= 1, ORA-01400:

my application on apex.oracle.com.
http://apex.oracle.com/pls/otn/f?p=19391:1:931174149200985:::::
login : guest pwd : 123
To get the error
1. click on edit button on daily entry.
2. click on add button on daily_entry_detail
3. enter party name
4 enter qty
and click on add row to add 2nd row
following error
Error in mru internal routine: ORA-20001: Error in MRU: row= 1, ORA-01400: cannot insert NULL into ("PTEST"."DAILY_ENTRY_DETAILS"."ENTRY_DATE"), insert into "PTEST"."DAILY_ENTRY_DETAILS" ( "ENTRY_DATE", "PARTY_NAME", "QTY") values ( :b1, :b2, :b3)     Error     Unable to process update

Hi
I am going to assume that ENTRY_DATE should be the date that the user created the record - otherwise, you will have to add this field to your form to get the user to fill it in.
You need to check how your DAILY_ENTRY_DETAILS table is set up.
Go to SQL Workshop, Object Browser and in the list of tables, select DAILY_ENTRY_DETAILS, then click on the SQL option above the table definition and you should see something like:
CREATE TABLE "A_LOV1"
   (     "LOV1" NUMBER,
     "LOV1_NAME" VARCHAR2(100),
      CONSTRAINT "A_LOV1_PK" PRIMARY KEY ("LOV1") ENABLE
CREATE OR REPLACE TRIGGER "BI_A_LOV1"
before insert on "A_LOV1"
for each row
begin
if :NEW."LOV1" is null then
    select "A_LOV1_SEQ".nextval into :NEW."LOV1" from dual;
end if;
end;
ALTER TRIGGER "BI_A_LOV1" ENABLE
/(This is based on one of my tables, so the names etc will be different for you).
In the first block, the CONSTRAINT line tells you whether or not you have a primary key on the table - in the example above, the primary key field is LOV1. If this is not set up, you must do this - click on the Constraints option at the top of the page and click Create then follow the prompts.
The next block is a TRIGGER. This is set to run whenever a record is inserted into the table. A record being inserted is referred to as :NEW. You can see from the example that, in this case, when the record is being inserted, the value in the Primary Key is checked. If it is null, then a new sequence number is generated (see below) and the record is updated with this number before the record is saved.
The final block just switches the trigger on
You will see that this trigger says "select A_LOV1_SEQ.nextval...". This refers to a "sequence" object. Go back to the Object Browser and select Sequences. In my example, there is a sequence called A_LOV_SEQ which, if I select it and look at the sql, it is defined as:
CREATE SEQUENCE "A_LOV1_SEQ" MINVALUE 1 MAXVALUE 99999999999999999999999 INCREMENT BY 1 START WITH 1 NOCACHE NOORDER NOCYCLEThis is a counter that is used by the trigger to get the next Primary Key value for the record.
If you don't have the sequence, you will need to set it up. This can be done by clicking the Create button at the top right and following the prompts. Or you can copy the above, change the sequence name as required and then run this in the SQL Commands window
If you don't have the trigger, you can copy the code above and edit it to suit your table needs.
Now for the ENTRY_DATE issue. If this is to be automatically set to the current date, you can handle this in the trigger. For example - assume I had that field on my table, then my trigger would be:
CREATE OR REPLACE TRIGGER "BI_A_LOV1"
before insert on "A_LOV1"
for each row
begin
if :NEW."LOV1" is null then
    select "A_LOV1_SEQ".nextval into :NEW."LOV1" from dual;
end if;
if :NEW."ENTRY_DATE" is null then
    :NEW."ENTRY_DATE" := SYDATE;
end if;
end;
ALTER TRIGGER "BI_A_LOV1" ENABLE
/SYSDATE just means the current date/time
The CREATE and ALTER statements must be run separately in the SQL Commands window
Once you have that set up correctly, your form should work
Andy

Error in mru internal routine: ORA-20001: Error in MRU: row= 1, ORA-01779:

I have a tabular form based on a view like:
select
t1.id,
t2.network_id,
t2.month_id,
t2.icp_ic,
t1.status,
t1.disc_comment
from
table1 t1,
table2 t2
where
t1.month_id (+) = t2.month_id and
t1.network_id (+) = t2.network_id and
t1.icp_id (+) = t2.icp_id
id is a surrogate key of table1 and there is a trigger to populate this on insert. There is also a unique index on table2 (month_id, network_id, icp_id). When I change the disc_comment column through the form and try to save I get an error:
Error in mru internal routine: ORA-20001: Error in MRU: row= 1, ORA-01779: cannot modify a column which maps to a non key-preserved table
If I take out the outer join, it works fine. The problem is table1 will not have a row for every row in table 2, hence I need the outer join. Any ideas how I can get around this problem?
Regards
Sadanand

Hi Andy,
Yes I am paginating the form and I am not getting a set of blank rows. What I mean by next set of records is - if the page is showing rows 11 to 20 and I enter a comment against row 15 and save, the form inserts the comment into the table via the INSTEAD OF trigger and the page automatically refreshes with rows 21 to 30 from the query. On the other hand, if I click Prev link and redisplay rows 11 to 20, change the comment and click on Save, the form updates the comment and refreshes the page with rows 11 to 20. If I update the comment again, it redisplays page with rows 11 to 20 and this is the behaviour I desire when I insert data. Remember that I am using outer join, so there will be a mix of inserts and updates of data. I hope my explanation is clear. I have tried removing the tabular form region and starting from scratch but that hasn't helped - maybe I will drop the page and recreate it.
As for checksum error, you are right - it disappears after I logout and login again.
Regards
Sadanand

Error in mru internal routine: ORA-20001: Error in MRU: row= 0, ORA-20001:

Hi, I'm using HTMLDB version 1.6.0.00.87 on a DB 10.1.0.3.0.
I'm creating a Tabular Form to perform update operations on multiple rows in a database table.
The table is in a schema outside of the HTMLDB schema and my application works.
If I substitute my table with a synonym (outside of the HTMLDB schema) pointing to another table (outside of the HTMLDB schema), the select works fine but when I try to update records an error occurs:
0.05: Branch point: BEFORE_PROCESSING
0.05: Processing point: AFTER_SUBMIT
0.05: ...MULTI_ROW_UPDATE (AFTER_SUBMIT) #OWNER#:CSTCMP:T$NCMP:T$CPCP
0.08: Show ERROR page...
0.09: Processing point: AFTER_ERROR_HEADER
0.10: Processing point: BEFORE_ERROR_FOOTER
Error in mru internal routine: ORA-20001: Error in MRU: row= 0, ORA-20001: ORA-20001: Current version of data in database has changed since user initiated update process. current checksum = "1F2F93F97DFD18A9D69960FCD28AF6EF", item checksum = "A884FA378C851786DDFE3A33709CB23C"., update "WS_T1"."CSTCMP" set
If I perform with SQL the update on the synonym, it works.
I only have a browser connected to the application and I'm not locking the table.
I don't think this is correlated with
Re: Error in mru internal routine (HTML DB BUG?)
What do you think about?
Thanks in advance.

To look into what? You probably modified your tabular form by adding a column and you didn't take care of the column source.
Denes Kubicek
http://deneskubicek.blogspot.com/
http://www.opal-consulting.de/training
http://apex.oracle.com/pls/otn/f?p=31517:1
http://www.amazon.de/Oracle-APEX-XE-Praxis/dp/3826655494
-------------------------------------------------------------------

Error in mru : ORA-20001: Error in MRU: row= 1 Current version of data ...

hi i am getting tihs error msg
Error in mru internal routine: ORA-20001: Error in MRU: row= 1, ORA-20001: ORA-20001: Current version of data in database has changed since user initiated update process. current checksum
i'll try to show a form table in which i can edit and add data
when i use the wizzard it is all fine with editing but i cant creat a new item because i have to insert my primary key and that shoud be done automatically.
ok again
my PK is at first col1 and second col2
i got a dropdown list in which i choose an item from col1 to just show items in my form with that value, here are more than one results possible
no i want to edit col2 up to col4
or add a line with the same col1 but different col2 and some col3-col4 values
but if i add a line i want to insert col2 to up to col4 (and the PK from col1 shoud be automatically insert from my dropwdown list i choosed before)
i want in col2 an drop down list
so all this works fine i got all the changes i want but when i try do save or update my changes i got the error frome above
i think the problem is at the primary key thing cause i want to choose a part manually but i have to
to get the new line actually u use the add row link but i use instead after my select statement an
Union select :P62_PNR_VOll, null, null, null from dual
to get my first pk automatically from my dropdown element (in my case :P62_PNR_VOLL)
how can i solve that error?
thx for ur help
regadrs
Falk

Hi Falk,
It is usually best to have a sequence number for the primary key on a table. If you need to restrict other fields to be unique, then you can create a constraint to do this.
To create a sequence number and apply this to a new record, you need to do two things:
Let us say that you have a table called TABLEX and this has a numeric primary key field of ID. Do the following in the SQL Commands window
1 - Create a sequence SQL object:
CREATE SEQUENCE "TABLEX_ID_SEQ" MINVALUE 1 MAXVALUE 99999999999999999999999 INCREMENT BY 1 START WITH 1 NOCACHE NOORDER NOCYCLE2 - Create a trigger:
CREATE OR REPLACE TRIGGER "TABLEX_BI"
BEFORE
INSERT ON "TABLEX"
FOR EACH ROW
BEGIN
IF :NEW.ID IS NULL THEN
SELECT TABLEX_ID_SEQ.NEXTVAL INTO :NEW.ID FROM DUAL;
END IF;
END;This needs to be enabled, so run:
ALTER TRIGGER "TABLEX_BI" ENABLEWhen this is done, you then have "An existing trigger" that you can use for your tabular form. When a new record is created, the trigger is run and this checks for a value in the ID field. If this is NULL, then the next value in the sequence is assigned to it.
Primary Keys can be based on other values. You can use any value from the current record - for example, if you need to get the value from the XXX field, you just reference :NEW.XXX You can use this to pass into a function that returns your new primary key value. But I would recommend keeping to one field for your primary key as this makes things a lot simpler later on.
Andy

ORA-20001: Error

hi all,
I have a problem when I try to delete or a save in my my form I am getting this error.
ORA-20001: Error in DML: p_rowid=52, p_alt_rowid=MSB_ID, p_rowid2=, p_alt_rowid2=. ORA-20001: Current version of data in database has changed since user initiated update process. current checksum = "310B7C5EFC6B9299BC7CB7DB500A2E84" application checksum = "0"
what can be the problem?
Thanks.

1. Please tell us your first name and put it in your handle and/or profile to help us.
2. Explain all the details of your page (all components and all of their attributes, etc.) or show us the application on apex.oracle.com so we can see it (preferred).
3. What version of Application Express and database?
Scott

Classic Report - report error:ORA-20001: Error fetching column value

Hi,
In Apex 4 I have created an SQL report which errors with ORA-20001: Error fetching column value: ORA-01403: no data found.
It works fine if I hard code the start and end dates but fails when I use page items as parameters.
I call a stored function as below:
DECLARE
l_sql VARCHAR2(4000);
BEGIN
SELECT ICDB_PCT_MRSA_POS_REP(v('P40_NEWSTARTDATE'),
v('P40_NEWENDDATE'))
INTO l_sql
FROM dual;
RETURN(l_sql);
END;
although I have used the :P40_NEWSTARTDATE form too, with the same result.
Any suggestions will be welcome.
Thanks,
Chris

Hi Chris,
have you debugged if ICDB_PCT_MRSA_POS_REP is raising the no-data-found error or if it's the actual SQL statement which got returned?
Comment out the call to ICDB_PCT_MRSA_POS_REP and return a hard coded SQL statement with
return 'select [... here comes a sample sql statement returned by ICDB_PCT_MRSA_POS_REP]';to rule out that ICDB_PCT_MRSA_POS_REP is raising the error.
BTW what is the purpose of the select from dual? Just call the ICDB_PCT_MRSA_POS_REP directly like
return ICDB_PCT_MRSA_POS_REP(:P40_NEWSTARTDATE, :P40_NEWENDDATE);Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX 4.0 Plug-Ins: http://apex.oracle.com/plugins

Report error: ORA-20001: Error fetching column value

Hi,
I try to build a tabular form with 1 column as "Select List (Query based on LOV)". This select list should display round about 1.100 rows in the LOV ordered by name. So I got the error: report error:
ORA-20001: Error fetching column value: ORA-06502: PL/SQL: numerischer oder Wertefehler: character string buffer too small
When I try tho define this column as Popup LOV (Query based LOV) only the the ID of the attribute and not the display value appeares in the row. The LOV it self displays the display number and not the the ID. I want to see the display value in the column of the particular row and the LOV and return the ID to the record by insert or update as it is normal in LOVs of form regions.
This lot of rows in the LOV is necessary because it is a part to develop formulas like (number_of_acquisitions - number_of_old_parts)/100 or so. The most formulas will be more complex. In the database there should only be the ID as reference to the attributes.
Please help me to display the attribute bases on LOV in every particular row.
Thank you
Siegwin

In Apex 4 there is now a column type "Popup Key LOV (named LOV)" which is exactly what you are looking for.
Edited by: 964978 on Oct 12, 2012 4:53 AM

Report suddenly showing ORA-20001: Error fetching column value: ORA-06502:

Hi,
Some reports in my applications are suddenly showing:
ORA-20001: Error fetching column value: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
instead iof the data they used to show.
In my development system I can fix this by:
1. changing the column alias in my sql
select 'a' alias1 from dual becomes
select 'a' alias2 from dual
2. SAVE CHANGES
3. change column alias back to original
select 'a' alias2 from dual becomes
select 'a' alias1 from dual
4. reorder columns back to original in the 'report attributes' tab
alias1 is now at the bottom of my colum list - i just bounce it up to column 4 using the up arrows
5. SAVE CHANGES
then everything starts working OK again.
There seems to be nothing wrong with my sql as I can make it works on a new page or after I run the above steps, so I guess something is breaking somewhere but I cannot work out what.
Has anyone else seen this? Does anyone know the cause? Does anyone have a fix for this that does not involve the above steps (plus redeployment to prodcution and all the work that involves)?
I am seeing this on version 2.3 and 3.0.
Thanks,
Martin

Hi Scott,
I think this is want you want (sorry it's not easy to read):
wp.suite_id - Database Column NUMBER - Report Column Based on LOV
wp.project_id - Database Column NUMBER - Report Column Based on LOV
wp.application_order wp_order - Database Column NUMBER - Report Column Standard
lpad(wp.work_package_id,5,'0')||' - '||wp.name wp_name - Database Column NUMBER/VARCHAR2 - Report Column Standard
pt.application_order pt_order - Database Column NUMBER - Report Column Standard
pt.name pt_name - Database Column VARCHAR2 - Report Column Standard
substr(pt.description,1,30) description - Database Column VARCHAR2 - Report Column Standard
pt.application_tier - Database Column VARCHAR2 - Report Column Based on LOV
pt.application_method - Database Column VARCHAR2 - Report Column Based on LOV
pt.TECH_LEAD_ID - Database Column NUMBER - Report Column Based on LOV
This report has no link columns and no derived columns.
Regards,
Martin

Problem with APEX 4.0 - "ORA-20001: Error with: GRANT CREATE CLUSTER "

Similar Messages

Maybe you are looking for