Error in Report ORA-24801

Hi All,
I am trying to run a report containing the images stored in blob column in database 10g, while running the report I got following error ..
ORA-24801: illegal parameter value in OCI lob function
Cause: One of the parameter values in the OCI lob function is illegal.
Action: Check every parameter in the OCI Lob function call to make sure they are correct. Offsets should be greater than or equal to one.
I didn't understand with this the cause and the solution of error....Any body could please tell what exactly it means and what we should do.
Any help will be highly appriciated.
Best Regards

Hi Don,
The reason why i posted the item on 'data Connectivity issues' is because i suspect the problem is with the connection string.Though i had provided the correct connection string,re-writing the connection string with the same info might help to fix the issue with loading the report.
Does it mean that there is a problem in the connectivity?
I have a risk here that i cant re-write the connection string..i.e to open the RPT file in VS2005 and bind it.The production web server & database server sits in a third party environment and it is not in the company network.So i cant connect to this server to re-write from any other severs in the network.
Is there any fix which can applied to the server to get this issue resolved?
Cheers
Nithya.

Similar Messages

Error while exporting : ORA-24801: illegal parameter value in OCI lob funct

hello,
I am doing an export on a 10.2.0.4 , solaris machine.
The table i am doing an export has a blob & clob.
During the export I get the error :
EXP-00056: ORACLE error 24801 encountered
ORA-24801: illegal parameter value in OCI lob function
In metalink it was given : Check every parameter in the OCI Lob function call to make sure they
are correct. Offsets should be greater than or equal to one.
Where should I check for that OCI Lob function. Or is there any other alternative to do the export.
Thanks for any help.

I have increased the space on the mount I was doing the export and that solved the problem.
Thanks

"Error rendering report" in hosted application

I am suddenly getting the following error message in my hosted application (I work for Oracle):
Error rendering report: ORA-00600: internal error code, arguments: [17059], [0x9370852C], [0x93708260], [0x90EE7724], [], [], [], []
when running page 9 (Find Messages) of application 16924 (CRM MEssage Review tool).
I haven't made many changes to the page that would have caused this. I had a similar issue. last year, which was resolved by the APEX team.
Could you please look into this?
Thanks
Daniel

Daniel - If this is still happening please send me an internal email with details about how I can see this.
Scott

ORA-06502 : PL/SQL: numeric or value error in Report formattrigger

Hi guys,
I have a Format Trigger code to not display any amount less than 1.00 at a group frame level and outside of the group frame is the Grand Total in my report but I am getting
" REP-1401: ' r_headerformattrigger ' : Fatal PL/SQL error occurred.
"ORA-06502 : PL/SQL: numeric or value error"
every time I try to run it.
function R_headerFormatTrigger return boolean is
begin
if :c_header_amount_accrual1_disp > 0.99 then
return (TRUE);
else
return (FALSE);
end if;
end;
Does any one have any idea as why?

read this code
Cause: An arithmetic, numeric, string, conversion, or constraint error occurred. For example, this error occurs if an attempt is made to assign the value NULL to a variable declared NOT NULL, or if an attempt is made to assign an integer larger than 88 to a variable declared NUMBER(2).
Action: Change the data, how it is manipulated, or how it is declared so that values do not violate constraints
Rizwan

Report error while download the report.-ORA-06502

*"report error:ORA-06502: PL/SQL: numeric or value error: character string buffer too small."*
When I trying to download the classical report,It give the above error when report having the more than 26 column to print,
The download report format what ever may be except .csv.
Any solution for this?
Edited by: 945115 on Aug 29, 2012 12:35 AM
Edited by: 945115 on Aug 29, 2012 12:35 AM

Pratap.,
Error in classical report download by print server link.This is a PDF output that your are generating?
Which Report Server have you configured? This error is coming from Report Server.
The Standard Report Server has its limitations. If are using Std then maybe you have hit one of them.
Cheers,
PS: Change you handle to something better than 945115

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?

Getting ORA-24801: error when reading a CLOB data using BufferReader

I am getting the "ORA-24801: illegal parameter value in OCI lob function", when reading a CLOB using a BufferedReader, i am using "oracle.jdbc.OracleDriver" for creating a connection pool and using Oracle 9.2.0.7 with Weblogic 8.1 SP 5. My code looks like this,
oracle.sql.CLOB c_lob = null;
c_lob = ( oracle.sql.CLOB)stmt.getClob(7);
BufferedReader in1 = new BufferedReader(c_lob.getCharacterStream());
char buffer[] = new char[1];
int i;
while((i = in1.read(buffer)) != -1)
The error is coming at "in1.read(buffer)".

Hi,
Your buffer size should be the clob size.
char[] buffer = new char[c_lob.getBufferSize()];
Also, set the value for i as -1.
You could see the sample on OTN for help:
http://www.oracle.com/technology/sample_code/tech/java/sqlj_jdbc/files/advanced/LOBSample/Readme.html
Thanks,
Rashmi

Error in webi report - ORA-06502

Dear All,
I have create an object in Universe "description" , I am using this object in WEBI report.
When I run the WEBI report I am getting below error:
Database error occurred :the databasr error text is ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at line 1 . (Error: WIS 10901)
This object is working fine in Dev and Quality.
But it is getting above error in the Prod environment in WEBI report.
Actually i think its this "description" object which is the reason
dbms_lob.substr( xyz.DESCRIPTION, 4000, 1 )
Any help is highly appreciated

hello,
yes the DB across the landscapes is same version ...
the failure is due to....see the below test in the field
"cess Code |ZCCONSI| configured "
These 'bar' looking characters are what is causing the failure:
Any ideas on how to fix this.....will string function work at all for this?
Thanks

Error report: ORA-06531: Reference to uninitialized collection

I have Procedure like this
declare
CURSOR lcu_emp
IS
    (SELECT *
    FROM
emp);
ln_count PLS_INTEGER := 1;
TYPE emp_TBL_TYPE
IS
TABLE OF LCU_emp%ROWTYPE;
LT_emp emp_TBL_TYPE;
begin
FOR Lr_EMP IN LCU_EMP
LOOP
    ln_count             :=1;
Lr_EMP.EMP_NO:='1234'; -- updating the loop variable ... just for eg its 1234
--Transferring the loop variable to collection
lt_PREV_ASSIGN(ln_count):= Lr_PREV_ASSIGN;   -- THis line its errorring it as Error report: ORA-06531: Reference to uninitialized collection
END LOOP;
FOR lr_emp IN lt_emp.FIRST..lt_emp.LAST
LOOP
-- printing records when LT_emp (lr_emp ).emp_no = 1234;
END LOOP;
end;Please help how to assign cursor record to collection...
Thanks
Vinoth.

The realtime procedure is below... i thought it will be easy for u guys to understand
PROCEDURE MAIN(
    P_ERRBUFF OUT VARCHAR2,
    P_RETCODE OUT NUMBER,
    P_BUSINESS_GROUP_ID IN NUMBER,
    P_EFFECTIVE_DATE    IN VARCHAR2,
    p_debug_flag        IN VARCHAR2 )
AS
LN_ELEMENT_LINK_ID pay_element_links_f.element_link_id%TYPE;
LN_INPUT_VALUE_ID1 pay_input_values_f.input_value_id%TYPE;
LN_INPUT_VALUE_ID2 pay_input_values_f.input_value_id%TYPE;
ld_effective_start_date pay_element_entries_f.effective_start_date%TYPE;
LD_EFFECTIVE_END_DATE PAY_ELEMENT_ENTRIES_F.EFFECTIVE_END_DATE%TYPE;
LN_ELEMENT_ENTRY_ID PAY_ELEMENT_ENTRIES_F.ELEMENT_ENTRY_ID%TYPE;
ln_object_version_number pay_element_entries_f.object_version_number%TYPE;
lc_create_warning BOOLEAN;
CURSOR lcu_prev_assign
IS
    (SELECT *
    FROM
      (SELECT P_PAAF.ASSIGNMENT_ID PREV_ASSIGNMENT_ID,
        C_PAAF.ASSIGNMENT_ID CURR_ASSIGNMENT_ID,
        PAP.ACCRUAL_PLAN_NAME ACCRUAL_PLAN_NAME,
        APPS.PER_UTILITY_FUNCTIONS.GET_NET_ACCRUAL ( P_PAAF.ASSIGNMENT_ID, P_PAAF.PAYROLL_ID , P_PAAF.BUSINESS_GROUP_ID, -1 , TRUNC(XPPOS.PREV_ACTUAL_TERMINATION_DATE) , PAP.ACCRUAL_PLAN_ID) NET_ACCRUAL,
        XPPOS.PERIOD_OF_SERVICE_ID,
        XPPOS.PERSON_ID,
        XPPOS.CURRENT_DATE_START ,
        XPPOS.PREVIOUS_DATE_START,
        XPPOS.CURR_ACTUAL_TERMINATION_DATE,
        XPPOS.PREV_ACTUAL_TERMINATION_DATE ,
        XPPOS.PREV_LSP_DATE PREV_LSP_DATE,
        P_PAAF.BUSINESS_GROUP_ID PREV_BG_ID ,
        c_paaf.business_group_id curr_bg_id ,
        'N' NEW_ASSIGNMENT_ELEIGIBLE ,
        NULL PTO_ELIGBLE_DATE,
        NULL status,
        NULL ERROR_MESSAGE,
        NULL PREV_ASS_ELEMENT_ENTRY_ID,
        null curr_ass_element_entry_id
      FROM
        (SELECT PERIOD_OF_SERVICE_ID,
          PERSON_ID,
          DATE_START CURRENT_DATE_START,
          LEAD(DATE_START,1,NULL) OVER(PARTITION BY PERSON_ID ORDER BY DMY_ORDER) PREVIOUS_DATE_START,
          ACTUAL_TERMINATION_DATE CURR_ACTUAL_TERMINATION_DATE,
          LEAD(ACTUAL_TERMINATION_DATE,1,NULL) OVER(PARTITION BY PERSON_ID ORDER BY DMY_ORDER) PREV_ACTUAL_TERMINATION_DATE,
          lead(last_standard_process_date ,1,NULL) over(PARTITION BY person_id ORDER BY DMY_ORDER) prev_lsp_date,
          row_number() over (PARTITION BY person_id ORDER BY date_start DESC) DMY_SLCT
        FROM
          (SELECT period_of_service_id ,
            PERSON_ID ,
            DATE_START,
            ACTUAL_TERMINATION_DATE,
            last_standard_process_date,
            COUNT(PERSON_ID) OVER (PARTITION BY PERSON_ID) "CNT",
            row_number() over (PARTITION BY person_id ORDER BY date_start DESC) "DMY_ORDER"
          FROM PER_PERIODS_OF_SERVICE PPOS
      WHERE CNT     >=2
      AND DMY_ORDER IN (1,2)
        ) XPPOS,
        PER_ALL_ASSIGNMENTS_F C_PAAF ,
        PER_ALL_ASSIGNMENTS_F P_PAAF,
        PAY_ELEMENT_ENTRIES_F P_PEEF,
        PAY_ACCRUAL_PLANS PAP,
        PER_PERSON_TYPE_USAGES_F P_PPTUF,
        PER_PERSON_TYPES P_PPT
      WHERE XPPOS.DMY_SLCT =1
      AND C_PAAF.PERSON_ID = XPPOS.PERSON_ID
      AND TRUNC(CURRENT_DATE_START) BETWEEN C_PAAF.EFFECTIVE_START_DATE AND C_PAAF.EFFECTIVE_END_DATE
      AND C_PAAF.PRIMARY_FLAG = 'Y'
      AND P_PAAF.PERSON_ID    = XPPOS.PERSON_ID
      AND TRUNC(prev_actual_termination_date) BETWEEN P_PAAF.EFFECTIVE_START_DATE AND P_PAAF.EFFECTIVE_END_DATE
      AND P_PAAF.PRIMARY_FLAG = 'Y'
      AND P_PEEF.ASSIGNMENT_ID = P_PAAF.ASSIGNMENT_ID
      AND TRUNC(PREV_ACTUAL_TERMINATION_DATE) BETWEEN P_PEEF.EFFECTIVE_START_DATE AND P_PEEF.EFFECTIVE_END_DATE
      AND PAP.ACCRUAL_PLAN_ELEMENT_TYPE_ID = P_PEEF.ELEMENT_TYPE_ID
      AND C_PAAF.BUSINESS_GROUP_ID         = P_BUSINESS_GROUP_ID
      AND TRUNC(PREV_ACTUAL_TERMINATION_DATE) BETWEEN P_PPTUF.EFFECTIVE_START_DATE AND P_PPTUF.EFFECTIVE_END_DATE
      AND P_PPTUF.PERSON_ID                                                                                                                                                                       = P_PAAF.PERSON_ID
      AND P_PPTUF.PERSON_TYPE_ID                                                                                                                                                                  = P_PPT.PERSON_TYPE_ID
      AND P_PPT.SYSTEM_PERSON_TYPE                                                                                                                                                               IN ('EMP', 'EMP_APL')
      AND P_PAAF.EMPLOYMENT_CATEGORY                                                                                                                                                             IN ('LOCAL' , 'FR')
      AND C_PAAF.ASSIGNMENT_ID                                                                                                                                                                    = 83528
      AND APPS.PER_UTILITY_FUNCTIONS.GET_NET_ACCRUAL ( P_PAAF.ASSIGNMENT_ID, P_PAAF.PAYROLL_ID , P_PAAF.BUSINESS_GROUP_ID, -1 , TRUNC(XPPOS.PREV_ACTUAL_TERMINATION_DATE) , PAP.ACCRUAL_PLAN_ID) <> 0
      ORDER BY NEW_ASSIGNMENT_ELEIGIBLE
    CURSOR LCU_PTO_ELGIBLE(P_ASSIGNMENT_ID NUMBER , P_PLAN_NAME VARCHAR2 , P_EFF_DATE DATE)
    IS
      (SELECT MIN(peef.EFFECTIVE_START_DATE) pto_eligble_date
      FROM PAY_ELEMENT_ENTRIES_F PEEF,
        PAY_ELEMENT_TYPES_F PETF
      WHERE PEEF.ASSIGNMENT_ID = P_ASSIGNMENT_ID
      AND PETF.element_NAME    = P_PLAN_NAME
      AND TRUNC(p_eff_date) BETWEEN petf.effective_start_date AND petf.effective_end_date
    CURSOR LCU_ELEMENT_LINK(p_plan_name VARCHAR2,p_eff_date DATE)
    IS
      (SELECT PIVF1.INPUT_VALUE_ID INPUT_VALUE_ID1,
        PIVF2.INPUT_VALUE_ID INPUT_VALUE_ID2,
        PELF.ELEMENT_LINK_ID
      FROM PAY_ELEMENT_LINKS_F PELF ,
        PAY_ELEMENT_TYPES_F PETF,
        pay_input_values_f pivf1 ,
        pay_input_values_f pivf2
      WHERE PELF.ELEMENT_TYPE_ID = PETF.ELEMENT_TYPE_ID
      AND PIVF1.ELEMENT_TYPE_ID = PETF.ELEMENT_TYPE_ID
      AND PIVF2.ELEMENT_TYPE_ID = PETF.ELEMENT_TYPE_ID
      AND TRUNC(P_EFF_DATE) BETWEEN PELF.EFFECTIVE_START_DATE AND PELF.EFFECTIVE_END_DATE
      AND TRUNC(P_EFF_DATE) BETWEEN PETF.EFFECTIVE_START_DATE AND PETF.EFFECTIVE_END_DATE
      AND TRUNC(P_EFF_DATE) BETWEEN PIVF1.EFFECTIVE_START_DATE AND PIVF1.EFFECTIVE_END_DATE
      AND TRUNC(p_eff_date) BETWEEN pivf2.effective_start_date AND pivf2.effective_end_date
      AND ELEMENT_NAME = p_plan_name
        ||' RollOver Adj'
      AND PIVF2.NAME             = 'Hours'
      AND PIVF1.NAME             = 'Effective Date'
      AND petf.BUSINESS_GROUP_ID = P_BUSINESS_GROUP_ID
    ln_count PLS_INTEGER := 1;
TYPE PREV_ASSIGN_TBL_TYPE
IS
TABLE OF LCU_PREV_ASSIGN%ROWTYPE;
LT_PREV_ASSIGN PREV_ASSIGN_TBL_TYPE;
--LR_PREV_ASSIGN LCU_PREV_ASSIGN%ROWTYPE;
--Lb_PREV_ASSIGN LCU_PREV_ASSIGN%ROWTYPE;
BEGIN
FOR Lr_PREV_ASSIGN IN LCU_PREV_ASSIGN
LOOP
    ln_count             :=1;
    LN_ELEMENT_LINK_ID   := NULL;
    LN_INPUT_VALUE_ID1   := NULL;
    LN_INPUT_VALUE_ID2   := NULL;
    FOR LRU_ELEMENT_LINK IN LCU_ELEMENT_LINK (Lr_PREV_ASSIGN.ACCRUAL_PLAN_NAME,LR_PREV_ASSIGN.PREV_LSP_DATE )
    LOOP
      LN_ELEMENT_LINK_ID :=LRU_ELEMENT_LINK.ELEMENT_LINK_ID;
      LN_INPUT_VALUE_ID1 := LRU_ELEMENT_LINK.input_value_id1;
      LN_INPUT_VALUE_ID2 := LRU_ELEMENT_LINK.INPUT_VALUE_ID2;
      BEGIN
        apps.pay_element_entry_api.create_element_entry ( P_EFFECTIVE_DATE => LR_PREV_ASSIGN.PREV_LSP_DATE, P_BUSINESS_GROUP_ID => LR_PREV_ASSIGN.PREV_BG_ID ,p_assignment_id => Lr_PREV_ASSIGN.prev_assignment_id ,p_element_link_id => ln_element_link_id ,p_entry_type => 'E'
        --,p_creator_type => 'F'
        --,p_cost_allocation_keyflex_id => cost_keyflex_id
        --,p_date_earned => l_week_ending_date
        ,p_input_value_id1 => LN_INPUT_VALUE_ID1 ,p_input_value_id2 => LN_INPUT_VALUE_ID2
        --,p_input_value_id3 => l_inp_value3_id
        --,p_input_value_id4 => l_inp_value4_id
        ,P_ENTRY_VALUE1 => LR_PREV_ASSIGN.PREV_ACTUAL_TERMINATION_DATE ,p_entry_value2 => (-1)* LR_PREV_ASSIGN.net_accrual
        --,p_entry_value3 => l_constant_all_deductions
        --,p_entry_value4 => l_constant_no
        ,p_effective_start_date => ld_effective_start_date ,p_effective_end_date => ld_effective_end_date ,p_element_entry_id => ln_element_entry_id ,p_object_version_number => ln_object_version_number ,P_CREATE_WARNING => LC_CREATE_WARNING );
        LR_PREV_ASSIGN.STATUS                    :='P';
        Lr_PREV_ASSIGN.prev_ass_element_entry_id := ln_element_entry_id;
      EXCEPTION
      WHEN OTHERS THEN
        LR_PREV_ASSIGN.STATUS        :='E';
        Lr_PREV_ASSIGN.error_message := SQLERRM;
      END;
    END LOOP;
    FOR LR_PTO_ELGIBLE IN LCU_PTO_ELGIBLE(LR_PREV_ASSIGN.CURR_ASSIGNMENT_ID ,LR_PREV_ASSIGN.ACCRUAL_PLAN_NAME , LR_PREV_ASSIGN.CURRENT_DATE_START )
    LOOP
      LR_PREV_ASSIGN.NEW_ASSIGNMENT_ELEIGIBLE := 'Y';
      LR_PREV_ASSIGN.pto_eligble_date         := LR_PTO_ELGIBLE.pto_eligble_date ;
    END LOOP;
    IF(LR_PREV_ASSIGN.STATUS = 'P')
    then
    BEGIN
        apps.pay_element_entry_api.create_element_entry (
        P_EFFECTIVE_DATE => LR_PREV_ASSIGN.pto_eligble_date ,
        P_BUSINESS_GROUP_ID => LR_PREV_ASSIGN.CURR_BG_ID ,
        P_ASSIGNMENT_ID => LR_PREV_ASSIGN.CURR_ASSIGNMENT_ID ,
        P_ELEMENT_LINK_ID => LN_ELEMENT_LINK_ID ,
        p_entry_type => 'E'
        --,p_creator_type => 'F'
        --,p_cost_allocation_keyflex_id => cost_keyflex_id
        --,p_date_earned => l_week_ending_date
        ,P_INPUT_VALUE_ID1 => LN_INPUT_VALUE_ID1
        ,p_input_value_id2 => LN_INPUT_VALUE_ID2
        --,p_input_value_id3 => l_inp_value3_id
        --,p_input_value_id4 => l_inp_value4_id
        ,P_ENTRY_VALUE1 => LR_PREV_ASSIGN.PTO_ELIGBLE_DATE ,
        p_entry_value2 => LR_PREV_ASSIGN.net_accrual
        --,p_entry_value3 => l_constant_all_deductions
        --,p_entry_value4 => l_constant_no
        ,P_EFFECTIVE_START_DATE => LD_EFFECTIVE_START_DATE ,
        P_EFFECTIVE_END_DATE => LD_EFFECTIVE_END_DATE ,
        P_ELEMENT_ENTRY_ID => LN_ELEMENT_ENTRY_ID ,
        P_OBJECT_VERSION_NUMBER => LN_OBJECT_VERSION_NUMBER ,
        P_CREATE_WARNING => LC_CREATE_WARNING );
        LR_PREV_ASSIGN.STATUS                    :='S';
        LR_PREV_ASSIGN.CURR_ASS_ELEMENT_ENTRY_ID := LN_ELEMENT_ENTRY_ID;
        commit;
      EXCEPTION
      WHEN OTHERS THEN
      rollback;
        LR_PREV_ASSIGN.STATUS        :='E';
        LR_PREV_ASSIGN.ERROR_MESSAGE := SQLERRM;
      END;
      END IF;
    lt_PREV_ASSIGN(ln_count):= Lr_PREV_ASSIGN;
ln_count:=ln_count+1;
END LOOP;
FOR lr_prev_assign IN lt_prev_assign.FIRST..lt_prev_assign.LAST
LOOP
IF(lt_prev_assign(lr_prev_assign).status = 'E')
THEN
FND_FILE.PUT_LINE(FND_FILE.LOG,lt_prev_assign(lr_prev_assign).error_message);
end if;
    --print the error records here
END LOOP;
END MAIN;

KR TAX LOCALIZATION REPORT 실행시의 ORA-20000, ORA-06512 ERROR MESSAGE

제품 : FIN_AP
작성날짜 : 2002-12-02
KR TAX LOCALIZATION REPORT 실행시의 ORA-20000, ORA-06512 ERROR MESSAGE
===================================================================
PURPOSE
Multi-Org 환경속에서 Kr Tax Localization Report 실행시의 ORA-20000, ORA-06512 Error Message 를 해결한다.
Problem Description
Kr Tax Localization의 Reports가 Error를 발생하고, View Log를 통해 확인한 Message가 다음과 같을 경우
ORA-20000: APP-00001: Unable to find message:
AR_NO_ROW_IN_SYSTEM_PARAMETERS
ORA-06512: "APPS.ARP_STANDARD", 줄 999에서
ORA-06512: "APPS.ARP_STANDARD", 줄 2246에서
ORA-06512: "APPS.ARP_UTIL", 줄 29에서
ORA-06512: "APPS.ARP_UTIL_TAX", 줄 111에서
ORA-06512: "APPS.ARP_TAX_EXTRACT", 줄 6178에서
ORA-06512: 줄 1에서
Workaround
Solution Description
1) fnd_client_info.set_org_context(<org_id>);
or
2) v_org_id varchar2(10);
v_org_id := fnd_profile.value('ORG_ID');
fnd_client_info.set_org_context(v_org_id);
.rdf 의 경우 : Before Report Trigger 에 추가
.sql (Package Body, Procedure) 의 경우 : 각 Begin 절 이후
Reference Documents
-------------------

제품 : FIN_AP
작성날짜 : 2002-12-02
KR TAX LOCALIZATION REPORT 실행시의 ORA-20000, ORA-06512 ERROR MESSAGE
===================================================================
PURPOSE
Multi-Org 환경속에서 Kr Tax Localization Report 실행시의 ORA-20000, ORA-06512 Error Message 를 해결한다.
Problem Description
Kr Tax Localization의 Reports가 Error를 발생하고, View Log를 통해 확인한 Message가 다음과 같을 경우
ORA-20000: APP-00001: Unable to find message:
AR_NO_ROW_IN_SYSTEM_PARAMETERS
ORA-06512: "APPS.ARP_STANDARD", 줄 999에서
ORA-06512: "APPS.ARP_STANDARD", 줄 2246에서
ORA-06512: "APPS.ARP_UTIL", 줄 29에서
ORA-06512: "APPS.ARP_UTIL_TAX", 줄 111에서
ORA-06512: "APPS.ARP_TAX_EXTRACT", 줄 6178에서
ORA-06512: 줄 1에서
Workaround
Solution Description
1) fnd_client_info.set_org_context(<org_id>);
or
2) v_org_id varchar2(10);
v_org_id := fnd_profile.value('ORG_ID');
fnd_client_info.set_org_context(v_org_id);
.rdf 의 경우 : Before Report Trigger 에 추가
.sql (Package Body, Procedure) 의 경우 : 각 Begin 절 이후
Reference Documents
-------------------

When network is down, it took 15 minutes to report ORA-03113 error

Now I am using OCCI under redhat to develope application to access oracle database. It works well if the connection with datbase is ok.
But if the network gone down before executing executeQuery of Statement, it took 15 minutes to throw SQLexception and error code is ORA-03113. Is there any solution to decrease the time to wait?
I am using OCCI by the mode of: Environment::THREADED_MUTEXED | Environment::OBJECT)
I only installed 2 rpms in redhat:
oracle-instantclient-basic-10.1.0.3-1
oracle-instantclient-devel-10.1.0.3-1

Yes, it is using TCP/IP. It took a long time to change from TCP state ESTABLISHED to CLOSE_WAIT as to tcp/ip.
I don't know whether there is timeout mechanism in the procotol used between oracle client and oracle server.
If there is such timeout mechanism, is it possible to configure it in OCCI? For example, if the network layer
uses select with timeout option, then the timtout is possible to control. But now it seems that it is not clear to set such configuration. Or is there such nonblocking mode in OCCI?
Or we can assume that oracle client library just depend on the tcp/ip protocol implementataion to detect that the tcp is broken. And the fact is in windows platform, the OCCI client will throw exception after about 2 minutes.
Thanks in advance for any suggestion!

REP-1401 'beforereport' Fatal PL/SQL error occurred. ORA 00000 normal.

Hi,
I am running the report Journals - General (132 char)- file name GLRGNJ.rdf from
Oracle Report Builder 6.0.8.11.3.
I have commented all the (srw.user_exit) in the Before Report trigger but i still
get the message:
REP-1401 'beforereport' Fatal PL/SQL error occurred. ORA 00000 normal,
successful completion.
Can anyone suggest a solution please?
Thanks,
Faris

Dear sir, i am created one formula column in Reports6i and the following error has come. Could u please find out a solution. Thanks in advance.
my function is below
function CF_Branch_NameFormula return Char is
lc_branch_name varchar2(100);
begin
SELECT rtrim(substr(FVT.DESCRIPTION
,instr(FVT.DESCRIPTION,'-',1)+1
,100)) INTO lc_branch_name
FROM FND_FLEX_VALUES FFV, FND_FLEX_VALUES_TL FVT
WHERE FFV.flex_value_Set_id = 1007956
AND FFV.FLEX_VALUE_ID = FVT.FLEX_VALUE_ID
AND FFV.FLEX_VALUE = FVT.FLEX_VALUE_MEANING
AND FVT.DESCRIPTION <> 'xxx'
and rownum<=1
AND SUBSTR(FVT.FLEX_VALUE_MEANING,3,2) = :P_BRANCH;
return (lc_branch_name);
end;

REP-1401: Fatal PL/SQL error occurred. ORA-01403: no data found

Hi guys,
I am getting error 'REP-1401: Fatal PL/SQL error occurred. ORA-01403: no data found ' when run the report
and i m also use formula column in my report.
can any body help me why it's coming.
following code is used in formula column plz check and verify:
function CF_3Formula return Char is
T1 VARCHAR2(100);
begin
SELECT
     VAT_REG_NO INTO T1
FROM
     JA_IN_HR_ORGANIZATION_UNITS JIHOU,
     HR_LOCATIONS HL--,
     --MTL_TXN_REQUEST_HEADERS MTLH
WHERE
JIHOU.ORGANIZATION_ID=HL.INVENTORY_ORGANIZATION_ID AND
JIHOU.LOCATION_ID=HL.LOCATION_ID AND
--Jihou.ORGANIZATION_ID = Mtlh.Organization_Id AND
-- Hl.INVENTORY_ORGANIZATION_ID =Mtlh.Organization_Id AND
-- MTLH.ATTRIBUTE10=SUBSTR(HL.LOCATION_CODE,1,3) AND
SUBSTR(HL.LOCATION_CODE,1,3)= :TO_ORG1 ;
RETURN (T1);
end;
plz help me out.

Hi;
What is EBS version? Is it custom report or not?
See below which is mention similar errors
Autoinvoice Error: ORA-1403: no data found [ID 1209403.1]
APXIIMPT - Payable Open Interface Import Fails on "REP-1401: 'cf_source_nameformula': Fatal PL/SQL error occurred. ORA-01403: no data found" [ID 222058.1]
Regard
Helios

REP-1401: 'cf_10formula': Fatal PL/SQL error occurred. ORA-06502: PL/SQL: numeric or value error

Hi Team,
I am running one conc programme.
After running I am getting below error. I checked the issue on metalink and other, seems that it is an size related issue. I have increased the size of formula columns and placeholdder too.
But still getting issue.
My requirement is to get comma seperated values using SQL query itself. Neither i wanted to create layout of the report , since it is a XML publisher report and nor I am including it on RTF template.
I want the CF_10 formula column to be populated with comma seperated values.
MSG-00187: From Date 01-Sep-2014
REP-1401: 'cf_10formula': Fatal PL/SQL error occurred.
ORA-06502: PL/SQL: numeric or value error
And Here is my code for CF_10
function CF_10Formula return Number is
begin
   SELECT NVL(TO_CHAR(sum(Amount),'99,99,99,999'),0) into :CP_5 --NVL(ROUND(sum(Amount)),0) into :CP_5
-- xxhw_Coll_cat(category)     "Intercat Catg"
FROM hhxw_Region_col_v
WHERE Category IN ('Intercompany - CATV')
AND trunc(gl_date) BETWEEN TO_DATE(:P_FROM_DATE, 'DD/MM/RRRR') AND TO_DATE(:P_TO_DATE, 'DD/MM/RRRR');
RETURN ROUND(:CP_5);
end;
Anyone please suggest me.
Regards,
Sachin

Hi,
1)Why are you selecting the value into a report item? Select into a local variable and return that
RETURN :CP_5 --> This one!!
2)And you should avoid applying functions to DB columns in where clauses wherever possible, so oracle can use indexes on them if applicable:
AND gl_date >= To_date(:P_FROM_DATE, 'DD/MM/RRRR')
AND gl_date < To_date( :P_TO_DATE, 'DD/MM/RRRR') + 1;
I think you are taking 2 column in the Layout CF_10 and CP_5 right? if so, then use below Query.
FUNCTION cf_10formula
RETURN NUMBER
IS
v_amount NUMBER:null;
IS
BEGIN
BEGIN
    SELECT nvl(round(SUM(amount)), 0)
    INTO   v_amount --> Retruns the value for CF_10 column
    FROM   hhxw_region_col_v
    WHERE category IN ( 'Intercompany - CATV' )
    AND    gl_date >= to_date(:P_FROM_DATE, 'DD/MM/RRRR')
    AND    gl_date < to_date( :P_TO_DATE, 'DD/MM/RRRR') + 1;
    :CP_5 := nvl(trunc(v_amount),0); --> Retruns the value for CP_5 column
EXCEPTION
WHEN OTHERS THEN
    v_amount := 0;
    srw.message(1003,'Error in Getting :' ||p_from_date);
END;
END;
And
If you've got a number function returning into a number field then all you should need to do to make the comma appear is to change the number format mask in field.
From 40000 to 40,000

A database error occured. The database error text is: ORA-29275: partial multibyte character . (WIS 10901)

Hi,
My Webi report is geeting failed with the error
"A database error occured. The database error text is: ORA-29275: partial multibyte character . (WIS 10901)"
may i know the root cause of the above error and how to resolve it. I am using BO 3.1.
Its very important to provide the report. Please help urgently.
Thanks in advance.
Abid

Hi Abid,
Please see SAP Note 1556127.
Symptom
A database error occurs after refreshing a web intelligence report in java report panel or web intelligence in interactive mode
The database error text is: ORA 29275 with partial multibyte character (WIS 10901)
Environment
windows 2003 Server
Cause
Environment variables are not set with value UTF-8:LC_ALL,LANG, and NLS_LANG
Resolution
Set following system environment variables: LC_ALL,LANG, and NLS_LANG with value UTF-8. For example, LC_ALL=EN_US.UTF-8

Error in Report ORA-24801

Similar Messages

Maybe you are looking for