REP-2103 error in report summary column
Hi ,
I am getting the below error while running the report
REP-2103 Column 'CS_Achived_tot' : PL/SQL formula returned invalid value or no value
Could you please help me ...
Thanks in Advance
Regards,
Sandeep
Hi,
I have used the below code in the formula column
function CF_Achived_totFormula return Number is
v_achived_tot number;
begin
begin
select nvl(:attribute4,0)
into v_achived_tot
from dual;
exception when others
then
--v_achived_tot :=0;
srw.message(130,'CF_Achived_tot');
return null;
end;
return (v_achived_tot);
end;
no data was there in the attribute4 feild and it was varchar2 data type
Regards,
sandeep
Similar Messages
-
I have written a formula column in a matrix report. I want to display a zero instead of a blank field where there are not recordd. When I run the report I get the error REP-2103: Column 'Zero_disp' PL/SQL formula returned invalid or no value. How do I trap this error. I have tried the no_data_found and SRW.DO_SQL_FAILURE and others. All these failed. Any Ideas.
nullcan u plz send me the script for ur formula column ?
-
Rep=2103 error message in oracle 10g
Hi After migrating from 6i to 10g I am getting the following msg when I try to generate a report:
rep-2103: column 'cf_street_address' : pl/sql formula returned invalid value or no value
I have the following code in my function:
function CF_street_addressFormula return VARCHAR2 is
begin
return(:address_line_1||' '||:address_line_2||' '||:address_line_3||' '||:address_line_4);
end;
Please help.I'm using Reports 9.0.4.0.19 and I recreated the scenario without any issues. I'm just wondering what would happen if you wrapped the :address_lines in nvl's in case 10g cares.
return(nvl(:address_line_1,' ')||' '||nvl(:address_line_2,' ')||' '||nvl(:address_line_3,' ')||' '||nvl(:address_line_4,' '));
Sorry, I could reproduce the problem.
-mike -
REP-1419 -- Error in report 6i
I am getting this error while running the report6i in the apps
REP-1419
Can any one help me out of these....
KrishnaHi ,
try using with these
Cause: One or more fields in a report is accessing data that is not available to that report, i.e. invalid PL/SQL references.
Action: Make sure that all tables/columns queried in the report are a) available and b) populated with data which matches parameters set in the report.
if it wont work then specify the steps what u r doing....
--Basava.S -
Hi All
When I am running a report in 10g, I am facing following error.
Terminated with error: <br>REP-163: Invalid value for keyword DESTYPE. Valid options are FILE, PRINTER, MAIL, INTEROFFICE, or CACHE.
Kindly give any suggestions
Best Regards,Hi,
questions regarding reports should be posted in the reports forum.
I suppose you tried to change the value of DESTYPE inside of a trigger or a program unit, but you chose a wrong argument for it. Searching inside your report for the keyword DESTYPE might help.
Regards
Frank -
Dear All..........
i have a report with n of pages now i want to get the sum total on each page but it should be a running page total...which mean on the first page it should display the total amount of the first page only and on the second page it should sum the total of second page and the total of the first page..and so on and ofcourse the last page should display the total of last page and the total of all the previes pages
Thanks people in advanceI would love to tell you all the things which we need to do to achieve this.
But on Second thoughts, Why should we ever discuss some things which are readily available. Help is a very undermined utility as fas as Oracle Developer is concerned.
There is an example over there for this. So just loo up .
And to every one. Please make use of Help. It will solve lot many of your problems.
Good Luck
Vij -
Problem in Report Formula Column
I recently Transfer my databse 9i to 10g and iam using developer 2.1 release 5 as a front hand.
so problem is that my reports run successfully with oracle 9i but when i change my database to oracle 10g iam facing error in reports formula column. when i use select statement in formula column. i gave u an example about that.
function CF_1Formula return Number is
lc_count NUMBER;
begin
SELECT count(*)
INTO lc_count
FROM tab;
RETURN (NVL(lc_count,0));
end;
when i compile formula column i got this error.
ORA-00600 internal error , argument:[17069], [19156148],[],[],[],[],[],[]
please help me in this matter.
Thanks.
M.Sohail Taihi fs,
Thanks for reply me my friend.
i also use the column name but same error is appeared when i compile formula column . this is only the example i gave to u. now i give u actual code.
function CF_Close_Rate1Formula return Number is
lc_rate number;
begin
select CL_RATES_CLOSE
into lc_rate
from sys_cl_rates
where cp_id = :v_cp_id
and loc_id = :v_loc_id
and trade_type_id = :trade_type_id
and cp_list_id = :cp_list_id
and CL_RATES_DATE = (select max(cl_rates_date)
from sys_cl_rates
where cp_id = :V_CP_ID
and loc_id = :V_LOC_ID
and trade_type_id = :trade_type_id
and cp_list_id = :cp_list_id);
--= :lc_closing_date;
return (nvl(lc_rate,0));
EXCEPTION WHEN NO_DATA_FOUND THEN
RETURN(0);
end;
This work properly with 9i database but not with 10g database.
Reply me soon .
Thanks,
M.Sohail Tai -
REP-1425 report formula DO_SQL error putting value into column
Hi all
I have opened a report 2.5 in Oracle9i Reports Developer and, it converted ok. However, when I run the report (paper layout), the message
rep-1425 report formula DO_SQL error putting value
into column. Column may not be referenced by parameter
triggers
appears. There are several report level formula columns and corresponding placeholder columns that are the cause of this error. The formula has the following :
SRW.DO_SQL('SELECT RPAD(''DAILY TABLE AUDIT REPORT'',60,''.'')||TO_CHAR(SYSDATE,''DD-MON-YYYY'') INTO :REPORT_TIT FROM DUAL');
COMMIT;
RETURN('');
I can't work out what this error message really means as the column, report_tit is a placeholder column and, the formula column is not a parameter trigger!! The report_tit placeholder is used as a source for a layout field. I noticed that the layout field is defined as a placeholder column in the converted report but in the reports 2.5 version, it is defined as a layout field.
I can do a work around by replacing the SRW.DO_SQL statement with a normal PL/SQL SELECT statement. However, I wonder if anyone else has had the same problem and, if anyone can help provide an answer as to what this error really means and, also, how I can retain the SRW.DO_SQL statement and/or an alternative work around to the one that I have described.
Thanks.
Therese Hughes
Forest Products CommisionHi again
The firewall proved to be the problem after all! The firewall set in Reports config-files is not used for WebServices, it has to be set within the stub:
Properties prop = System.getProperties();
prop.put("http.proxyHost","yourProxyServer");
prop.put("http.proxyPort","youProxyServerPort");
I inserted this in my java-code and after some problems (see below), restarting Report Builder turned the trick, the report works now.
Cheers
Tino
Here there mail I set up before I found that restarting Report Builder helped:
Thanks for your answer, putting in the proxy-settings actually helped some - the same error message is
popping up, but instantly and not after 10 seconds like before:
My proxy lines look like this, I also tried "http://proxy.ch.oracle.com", but "proxy.ch.oracle.com" proved to
be the correct syntax:
public Float getRate(String country1, String country2) throws Exception
Float returnVal = null;
Properties prop = System.getProperties();
prop.put("http.proxyHost","proxy.ch.oracle.com");
prop.put("http.proxyPort","8080");
URL endpointURL = new URL(endpoint);
Call call = new Call();
I tested the new proxy-entries by disabling the proxy preference in JDeveloper, so I could verify the added
proxy-lines in the code work - they do. If I change the proxy to some incorrect value like
"proxyy.ch.oracle.com", they fail.
After unsuccessfully trying recompile and re-import of Java classes, I rebuild the report from scratch and
stumbled over the same problem. Now the question is, whether I'm still doing something wrong with the
proxy or whether there is another problem after passing the firewall....
------------------------------------------------------------------------------------------------------------- -
Using Page Level Summary Column in Report 6i
Hi Folks,
I'm trying to create a report in which I want a Page level Summary column i.e., the Summary column should reset at each page and should display the sum of a particular field on each page depending upon how many records are displayed on each page. But whenever I choose the Reset Property to Page the following error is displayed" Page level summaries are not supported in the defaulting" and in certain case the summary column displays the sum only on the last page of the report and the rest of the pages do not display the summary column. The database has three tables i.e., master-detail-detail.
Do I need to make some changes in the Data Model or what?
TIA
HassanHi Hassan,
it only works onceWell, this is definitely not expected. Maybe you can try to see after running the report once whether all the values you set in your report (from my last post) remain the the same, or somehow they revert back to their default values.
if I do some formatting of the report... summary also disapperasYou could try placing the page level summary in another frame, below your group repeating frame, with enough gap between them. Also, try setting the value for "max no of records" to some lower value, which makes sure there is space for the summary column on every page.
Another idea for making a page level summary is - you can place the summary BEFORE your group repeating frame, which means the summary will print on top of every page. In this case, you won't even have to worry about setting "max no of records per page" to some particular value. See if this suits your needs.
Navneet. -
Report 6i/Webdb -Not able to display the report in the browser - rep- 3002 error.
Would someone tell what I missed, I have set up the following:
1) a report using report builder on NT
2) my database is in Unix
3) my report server is started in NT
4) I run webdb listener for the following code: http://myweb.com/cgi/rwcgi60.exe?server=repserver+report=myreport+userid=usid/pw/connect_string+destype=cache+desformat=html. Then, I receive this message:
Error: The requested URL was not found, or cannot be served at this time.
Oracle Reports Server CGI - Report Job has terminated with error.
Reports Server Replies:
REP-3002: Error initializing printer. Please make sure a printer is installed.
Why is it thinking I want to use the printer whereas I want to display the report in the browser?. Any help would be appreciated.
nullIt sounds like that your Web CGI did not configure right. To test if your CGI configuration is correct, type:
http://hostname:port/cgi-bin/rwcgi60exe?
If you get a help screen, then you should be able to bring up your report.
Regards,
Xiaoling -
Error Running Reports (REP-0081 & REP-0124)
Please help.
I am having the following error when running a report on the web:
(from the Reports Queue Manager)
Terminated with Error :
REP-0081: Error during file I/O operation. REP-0124: Unable to
write to the temporary file. scafa 3
thanks for a reply
regards
YogeerajHello pals,
i have set the following parameters: TMPDIR and REPORTS60_TMP...
and it seems to be working!!!
i hope that the problem is not somewhere else.
NB. I was having problems with 2 reports only. the others were
working fine.
any comments will be most welcomed.
regards
Yogeeraj -
: HIDING SUMMARY COLUMNS IN MATRIX REPORT , URGENT
Hi,
Can any one please tell me how to hide a column in oralce matrix report. Its a summary column for the matrix report which appears next to the cell values. For example
Manufacturer
Brand
SubBrand1 SubBrand2 Brand Total Manufacturer Total
Week $ Sales $ Sales Total $ Sales Total $ Sales
This is a case where,the cell value is the $ sales for the SubBrand for the week. And it gets total at each brand level and each Manufacturer level. The requrement is if there is only one SubBrand for a Brand then the Brand total should not appear on the report. Similarly if there is one Brand for a Manufacturer, then the total at Manufacturer level should not appear . The point is not only it should dissapear but the frame should srink to make it fell that there is no totaling going on at those two levels. If the fileds just remains blank then the report looks odd. So the gap should be srinked as well. How to do it . This is very urgent . Please help me out.
Thanks
Ferozuse a formst trigeer on the field that returns false when you don't want to display the field.
-
REP-770 Error while executing the report.
Hi,
I am trying to run a report in Application Server 10g. I am executing this report from a form.
When I try to run the report using the 'rdf', I get the error
"Terminated with error: <br>REP-770: There exist uncompiled program unit(s). REP-1247: Report contains uncompiled PL/SQL."
But if I run the report as 'rep' then the report works fine. Now after this if I run the report as 'rdf', it works fine again.
Just to summarise - The problem occurs if I first try to run the report as rdf. But the problem disappears if I run the report as rep first before running it as rdf.
Could someone help me solve this issue.
Thanks
ArunaHi Aruna,
I can see 2 bugs logged on Reports 9.0.4.1 (that means 10g patch 1) that report a similar problem:
BUG 4050488 - JSP REPORTS CONTAINING REF CURSOR ASKS FOR COMPILATION EVERYTIME WITH WEB LAOUT
and
BUG 4040844 - REF CURSOR QUERY REP-737 ORA-1247 RUNNING ON LINUX
Another bug reported on 10g has been fixed in upcoming Reports version 10.1.2:
BUG 3324576 - SRW.APPLY_DEFINITION IN PGM UNIT FAILS USING .REP FILE WITH REP-1457 ERROR
They are published bugs. See if you are hitting the same issue. Though I don't think that these bugs reported REP-1247 only the FIRST time you run the report.
Secondly, when I said "compile on the same platform on which you are going to run", I meant this - if you are going to run the report on OracleAS installed on Win 2000, you must compile the report in Reports Builder on Win 2000. Similarly, if you are going to run the report on OracleAS installed on Linux, you must compile the report in Reports Builder on Linux, before running it.
Navneet. -
Reports Builder Error - REP 1070 Error while opening or saving document
Hi,
I tried opening an rdf file in Reports Builder 10g and 6i. I get the REP 1070 error.
Kindly suggest a solution for this.
Thanks,
AnandHi,
Edit the system registry and assign REPORTS_PATH then your problem will be cleared. -
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 PMSo, 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?
Maybe you are looking for
-
Thunderbolt / firewire adapter issues.
I was excited to get the new IMAC this past December. In doing so I expected my 4tb caldigit external drive to work with the adapter I purchased. When I first hooked it up and turned on the drive it seemed to be having a hard time locating the comp
-
hi all, my scenario is that a middleware .net generates xml files which i have to pick up into sap r/3 and then also generate xml files to that middleware. Now my question is 1) Does the xml file need to follow any specifications to be read? 2)What i
-
Check in Similar not populating custom metadata value set by global rule
I have created a global rule to set the default value for custom metadata field creation date as current system date.This rule is working fine for normal check in but when i am using check in similar functionality of ucm the creation date value is ge
-
Ovi map for other country downloaded and installed...
I've used the Ovi Suite 2.2.0.245 and connected with N900 but selected PC suite mode instead of Mass storage. I read alot that you have to select Mass storage for N900, but Ovi Suite won't then be connected with my phone, but works with PC suite. I w
-
IS there a way to put Microsoft office on an iPad 2? In particular word and PowerPoint