OWB 9.2: expression length limit (4000) too small

I am writing a very long FILTER expression, exceeding 4000 bytes, which OWB does not allow. Has anybody experienced this before and found a workaround?
Jaap.

Hello Jaap,
Try breaking the expression into several FILTER operators.
Hope this helps
Mate

Similar Messages

Execute a DML query its length exceeds 4000 characters with execute immediate statement.

I want to execute a DML query with execute immediate statement. That DML query length exceeds 4000 characters. This query has Xquery related conditions, i can not split the query. when i tried execute it is giving "string literal too long". I tried with DBMS_SQL.Parse() and DBMS_SQL.Execute also, but it is giving same error. I have to execute this DML query inside a Procedure. Please help me to resolve this. We are using oracle 10g version
Thanks & Regards,
K.Kedarnadh

Actually Query is a dynamic query. Query length will exceeds if the no of domains\domain values \products exceeds. Any way Below one is current dynamic query, which is generated within procedure
SELECT
IVT.ID_IVT
    ,IVT.ID_INS_IVT
,EXTRACTVALUE(IVT.DOCUMENT_IVT,'//productName/text()') AS PRODUCTNAME
,EXTRACTVALUE(IVT.DOCUMENT_IVT,'//elementName/text()') AS INSTANCENAME
,EXTRACTVALUE(IVT.DOCUMENT_IVT,'//elementInternalName/text()') AS INTERNALNAME
    ,CTG.NAME_CTG
    ,CTR.NAME_CTR
    ,MDL.NAME_MDL
,IVT.REEDIT_FLAG_IVT
    FROM VARIATION_IVT IVT INNER JOIN CATEGORY_CTG CTG ON CTG.ID_CTG=IVT.ID_CTG_IVT
AND IVT.STATUS_IVT='Active' AND IVT.DELETE_FLAG_IVT=0 AND IVT.ID_PRJ_IVT=1
AND IVT.DOCUMENT_IVT.existsnode('.//domain[domainName="Jurisdictions" and (domainValue="Delhi" or domainValue="Bangladesh" or domainValue="Mumbai" or domainValue="India" or domainValue="Pakistan" or domainValue="Nepal" or domainValue="Maldives" or domainValue="Kolkata" or domainValue="Bhutan" or domainValue="Chennai" or domainValue="ALL")]')=1 AND IVT.DOCUMENT_IVT.existsnode('.//domain[domainName="Channels" and (domainValue="Agents" or domainValue="SBI" or domainValue="Maruti" or domainValue="Direct" or domainValue="CitiFinancial" or domainValue="SCB" or domainValue="BankAssurance" or domainValue="CitiBank" or domainValue="Employees" or domainValue="GE" or domainValue="Brokers" or domainValue="Telemarketing" or domainValue="Agency" or domainValue="ALL")]')=1 AND IVT.DOCUMENT_IVT.existsnode('.//domain[domainName="ModeofDelivery" and (domainValue="Walkin" or domainValue="Internet" or domainValue="ALL")]')=1 AND IVT.DOCUMENT_IVT.existsnode('.//context[(productName="ALL" or productName="A009" or productName="A010" or productName="A046" or productName="AccidentShieldClassic" or productName="AccidentShieldOnline" or productName="AM01" or productName="AM02" or productName="AME_Cancellation" or productName="ARHG" or productName="ARPA" or productName="B003" or productName="B004" or productName="B007" or productName="B008" or productName="B009" or productName="B010" or productName="B012" or productName="B013" or productName="B015" or productName="B016" or productName="B017" or productName="BC04_PA" or productName="BC06_FDP" or productName="BC06_PA" or productName="BC09" or productName="BC10" or productName="BC12" or productName="BC13" or productName="BF03" or productName="BS01" or productName="BS02" or productName="C017" or productName="C035" or productName="C036" or productName="C037" or productName="C038" or productName="C040" or productName="C041" or productName="C041Gold" or productName="C041New" or productName="C045HomeContents" or productName="C048" or productName="C049" or productName="C054" or productName="C057" or productName="C060Building" or productName="C060Contents" or productName="C060FDP" or productName="C061Building" or productName="C061Contents" or productName="C062" or productName="C063" or productName="C067" or productName="C070" or productName="C072" or productName="C074" or productName="C077" or productName="C081" or productName="C082" or productName="C087" or productName="C088" or productName="CITIFOREVER" or productName="CITISECURE" or productName="CITICHILDPLAN" or productName="D001" or productName="DB01" or productName="DD01" or productName="DD02" or productName="DD03" or productName="DD04" or productName="DD09" or productName="DD10" or productName="E005" or productName="E011" or productName="E016" or productName="E020" or productName="E030" or productName="E034" or productName="E040" or productName="E041" or productName="E045HCP" or productName="E045HSP" or productName="E049" or productName="E049New" or productName="E052" or productName="E053" or productName="E054FDP" or productName="E055" or productName="E056" or productName="E057" or productName="E058" or productName="E061" or productName="E061BATCH" or productName="E062" or productName="E063" or productName="E064HCP" or productName="E064HSP" or productName="E066" or productName="E069" or productName="E073" or productName="E075" or productName="E076" or productName="E088" or productName="E090" or productName="E093A" or productName="E093B" or productName="E095" or productName="E099A" or productName="E099B" or productName="E106" or productName="E107" or productName="E110" or productName="E112" or productName="E114" or productName="E115" or productName="E116" or productName="F001" or productName="FamilyHealthInsurance" or productName="FamilyHospitalBenefits" or productName="FamilyHospitalisationCoverBenefit" or productName="G001" or productName="G002" or productName="HealthShieldOnline" or productName="Health_B005" or productName="Health_S057" or productName="HealthSheild" or productName="HealthWalkin" or productName="HomeContentOnline" or productName="HomeShieldOnline" or productName="HomeShieldWalkin" or productName="HospitalCashOnline" or productName="J001" or productName="J008" or productName="K001" or productName="KV02" or productName="LC03" or productName="ML01" or productName="MP02" or productName="MP03" or productName="MR01" or productName="O005" or productName="PO01" or productName="PO02" or productName="PO03" or productName="PO04" or productName="PO05" or productName="PO06" or productName="RR02" or productName="RR03" or productName="RR04" or productName="S006" or productName="S033" or productName="S049" or productName="S051" or productName="S054" or productName="S057" or productName="S060" or productName="S061" or productName="S065" or productName="S065TM" or productName="S068" or productName="S076" or productName="S077" or productName="S079" or productName="S080" or productName="S081" or productName="S084" or productName="S085" or productName="S086" or productName="S087" or productName="S088" or productName="S091" or productName="S092" or productName="S093" or productName="S094" or productName="S095" or productName="S097" or productName="S098" or productName="S099" or productName="S100" or productName="S101" or productName="S102" or productName="S103" or productName="S104" or productName="S106" or productName="S107" or productName="S108" or productName="S109" or productName="S110" or productName="S111" or productName="S113" or productName="SCBNAC" or productName="SF02" or productName="SS01" or productName="SS02" or productName="SUNFHM" or productName="SurgicalShield" or productName="TD01" or productName="TD02" or productName="TP01" or productName="U002Building" or productName="U002Contents" or productName="U004Building" or productName="U007" or productName="U009" or productName="U013" or productName="U014" or productName="U015" or productName="U016" or productName="V001" or productName="V002" or productName="V005" or productName="V006" or productName="V008" or productName="W008" or productName="W020" or productName="W021" or productName="W022" or productName="W023" or productName="W024" or productName="W026" or productName="W027" or productName="W028" or productName="W029" or productName="W105" or productName="W106" or productName="WI01" or productName="WI02" or productName="WI03" or productName="WI07" or productName="WI08" or productName="WI09" or productName="WI10" or productName="WI11" or productName="WI12" or productName="WI13" or productName="WI14" or productName="WI17" or productName="WI20" or productName="WI21" or productName="WI21_Health" or productName="WI23" or productName="WI24" or productName="WI26" or productName="WI30" or productName="WI31" or productName="WI33" or productName="WI34" or productName="X001" or productName="X002" or productName="X003" or productName="X004" or productName="X005" or productName="X008" or productName="Y001" or productName="Y007" or productName="Y009" or productName="Y010" or productName="Y011" or productName="Y011H" or productName="Y020" or productName="Y020N" or productName="Z008" or productName="ZI001")]')=1
INNER JOIN CENTER_CTR CTR ON CTR.ID_CTR=CTG.ID_CTR_CTG
    INNER JOIN MODEL_MDL MDL ON MDL.ID_MDL=CTR.ID_MDL_CTR

10g - report object - filename property length limit

I am posting this in the hopes that I can stop someone from beating their head against their desk for a couple of days like I did.
In 10g forms (9.0.4.2.0), for a report object, there seems to be a limit to the length of the filename property - 79 characters. When it hits 80 characters, at runtime I get a "FRM-92101: There was a failure in the Forms Server during startup. This could happen due to invalid configuration"... error. Clicking the details button will show expanded info indicating a java exception "oracle.forms.net.ConnectionException: Forms session <x> aborted: unable to communicate with runtime process".
It would be nice if help for the filename property could include the length limit.
Gary

Thanks for your attention.
Gary
P.S. Thanks also for your write-up and javabean code on your blog regarding how to open a report in a new window with titlebar, etc disabled. Works like a charm.

Memlock limit too small

Hi,
We have Oracle 11gR2 (11.2.0.3) on the server with RHEL 5. Whenever we restart the database, we get below statements in the alert log:
Memlock limit too small: 32768 to accommodate segment size: 16777216
Memlock limit too small: 32768 to accommodate segment size: 16777216
Memlock limit too small: 32768 to accommodate segment size: 16777216
Memlock limit too small: 32768 to accommodate segment size: 16777216
Memlock limit too small: 32768 to accommodate segment size: 16777216
Memlock limit too small: 32768 to accommodate segment size: 2097152
****************** Large Pages Information *****************
Total Shared Global Region in Large Pages = 0 KB (0%)
Large Pages used by this instance: 0 (0 KB)
Large Pages unused system wide = 1536 (3072 MB) (alloc incr 16 MB)
Large Pages configured system wide = 1536 (3072 MB)
Large Page size = 2048 KB
RECOMMENDATION:
Total Shared Global Region size is 3014 MB. For optimal performance,
prior to the next instance restart increase the number
of unused Large Pages by atleast 0 2048 KB Large Pages (0 KB)
system wide to get 100% of the Shared
Global Region allocated with Large pages
Please advise.
-Onkar

PaulR,
below are the entries in my /etc/security/limits.conf file:
#Each line describes a limit for a user in the form:
#<domain>        <type> <item> <value>
#Where:
#<domain> can be:
#        - an user name
#        - a group name, with @group syntax
#        - the wildcard *, for default entry
#        - the wildcard %, can be also used with %group syntax,
#                 for maxlogin limit
#<type> can have the two values:
#        - "soft" for enforcing the soft limits
#        - "hard" for enforcing hard limits
#<item> can be one of the following:
#        - core - limits the core file size (KB)
#        - data - max data size (KB)
#        - fsize - maximum filesize (KB)
#        - memlock - max locked-in-memory address space (KB)
#        - nofile - max number of open files
#        - rss - max resident set size (KB)
#        - stack - max stack size (KB)
#        - cpu - max CPU time (MIN)
#        - nproc - max number of processes
#        - as - address space limit
#        - maxlogins - max number of logins for this user
#        - maxsyslogins - max number of logins on the system
#        - priority - the priority to run user process with
#        - locks - max number of file locks the user can hold
#        - sigpending - max number of pending signals
#        - msgqueue - max memory used by POSIX message queues (bytes)
#        - nice - max nice priority allowed to raise to
#        - rtprio - max realtime priority
#<domain>      <type> <item>         <value>
#*               soft    core            0
#*               hard    rss             10000
#@student        hard    nproc           20
#@faculty        soft    nproc           20
#@faculty        hard    nproc           50
#ftp             hard    nproc           0
#@student        -       maxlogins       4
# End of file
oracle          soft    nproc   16384
oracle          hard    nproc   32768
oracle          soft    nofile 65536
oracle          hard    nofile 98304
oracle          soft    stack   32768
oracle          hard    stack   49152
Any suggestions??
-Onkar

ExternalInterface.call String parameter length limit???

Is there a String length limit to the amount of chars a
String can contain when passed as a parameter to
ExternalInterface.call()?
Also, are there any chars that ExternalInterface.call()
cannot serialize in a string?? Like \n, \t ...etc.
The livedocs don't answer these questions.

thanks for your reply but i just figured it out.
ExternalInterface.call("jsFunc", longString);
There is seems to be no char limit that i came across cause i
was able to shove 2K in there.
The problem is the newlines in the string, they must get
messed up during serialization. Just make sure you clean the string
of newlines like so:
longString = longString.split("\r").join("
").split("\n").join(" ");
ExternalInterface.call("jsFunc", longString);
works fine......

Cable length limit on the so-called "Internet" port?

Is there a limit on the cable-length when connecting an Ethernet cable to the so-called "Internet" port on a WRT54G router?
I assume this is a standard 10/100 Ethernet port, since I am connecting this to the Ethernet port of my DSL modem. Since the Ethernet standard defines a maximum cable-length of 100 meters when connecting any 2 Ethernet devices, I should be able to use a cable up to this length when connecting 2 Linksys routers together.
Here is what I want to do:
DSL Modem-->Linksys Router-->Linksys Router
My first Linksys WRT54G router is connected to a DSL modem. I want to put a second WRT54G Linksys router in a different building, and connect them with a 100 meter Ethernet cable, connecting the remote end to the second router´s "Internet" port, and the other end into one of the first router´s available 10/100 ports. This will allow me to create 2 wireless signals, with 2 different DHCP scopes and 2 different SSID´s, basically allowing me to extend the range, with the 2 routers connected with a physical wire.
This works when connecting them with a short, 2 meter cable. Using a short cable I am able to associate with the second router´s SSID, get a DHCP address from that router, and then turn on RIP on both routers and have traffic route from the second router to the first one and out to the Internet successfully.
However, when I replace the short cable with a longer one, either 80 meters or 100 meters, I don´t get a link light between the routers. I do get a link light if I connect to a 10/100 port on both routers, but RIP doesn´t seem to want to exchange routes on the second router out anything other than the "Internet" port. Moving the cable back to the "Internet" port fails to produce a link light (unless I use a really short cable, which does produce a link light).
So my question is this: from a Layer-1 perspective, is the "Internet" port an Ethernet port that enforces a cable-length limit that doesn`t follow the standard 100 meter rule?
--- Christer

well..the internet port is definitely an ethernet port...however, it is not supposed to limit the cable length .. try a 50 m cable and check whether it works...because my friend had a similar kind of an issue and it worked fine with a 50 m ethernet cable ..

The mail address of mobileme has length limit!

In system preferences/mobileme/member name, length limit is 32 characters!
The mail address I have sign up with 34 characters,I can use it itunes(length limit 50+,tested),I can use it in appstore on my iphone.

... however, you have to go through the process of migrating from MobileMe to iCloud, it won't happen automatically. Just log into your account at me.com.

Cisco/Linksys WRVS4400N email address length limit

I have noticed that when I try and enter in an e-mail address for alert logs that I am unable to using the web form provided as there is a length limit.
The only way I have managed to get around this is to use the firefox plugin tamper data - https://addons.mozilla.org/en-us/firefox/addon/tamper-data/
I am using the latest firmware:
V2.0.0.8-ETSI
Are there any other solutions/updates/fixes available?

Hi Mark, thank you for using our forum, my name is Johnnatan I am part of the Small business Support community. I apologize for this but I don´t understand your problem. If you could give us more details that going to be really helpful in order to help you.
Greetings,
Johnnatan Rodriguez Miranda.
Cisco Network Support Engineer.

ORA-06502 (character string buffer too small) on import application via script

Running apex 4.2.2.00.11
oracle 10.2.0.5
I'm using a script to import my development application to a few production applications.
It worked great on apex 4.1.1, but now I get an 'ORA-06502 PL/SQL numeric of value error: character string buffer too small'
In the command window, I see that the script fails after it starts on the plugins.
My question: is this a bug in 4.2.2?
I could be a incompatible plugin, but how can I found out which plugin?
My script is quite simple:
In a command window I run
sqlplus SCHEMA/PASSWORD@SPIEU10 @_IMPORT_F102.sql
The script is
declare
l_workspace_id number;
begin
    -- determine the workspace id for the workspace FM in the target system
    select workspace_id into l_workspace_id from apex_workspaces where workspace = 'BY_APEX_SHARED';
    -- set the context for the target workspace
    apex_application_install.set_workspace_id( l_workspace_id );
    -- override the original application id 102
    apex_application_install.set_application_id ( 102 );
    -- set a different application name and alias, it should be unique within an APEX instance
    apex_application_install.set_application_alias( 'MY_ALIAS' );
    apex_application_install.set_application_name( 'MY_APP_NAME' );
    -- Use fixed offset
    apex_application_install.set_offset( p_offset => 0);
    -- override the original parsing schema FM with a different value
    apex_application_install.set_schema( 'BY_SCHEMA' );
end;
-- install the original application export, now the values for the workspace
@f102.sql
exit;
Error message from command window:
...ui types
...plugins
begin
ERROR at line 1:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at line 3
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64
bit Production
With the Partitioning, Data Mining and Real Application Testing options

ListAGG throws an ORA-01489 for varchar2 > 4000 bytes
OP has an ORA-06502 --> the IR is running into a 4k/32k limit.
quick solution: wrap USER_COMMENTS ListAGG in a substr( ...., 1, 4000)
Longer solution, use a subquery to modify the comments based on ROW_NUMBER() (ie after nth row, change it to NULL)
with
-- simulating data
t as (select task_id, sysdate - lv as date_entered
,round(dbms_random.value(1,24)) hours
, '-*' || lv || '.' || task_id || '*-' as user_comments
from ( select level as task_id from dual connect by level <=10 ), (select level lv from dual connect by level < 1000)
-- modify data
modified_data as (
select task_id, hours, date_entered
    ,case
      when row_number() over (partition by task_id order by date_entered desc) < 5
        then user_comments
      else null
     end USER_COMMENTS
    from t)
select task_id, sum(hours) total_hours,
listagg( user_comments ) within group (order by date_entered desc)
|| case when count(*) >= 5 then '! MORE COMMENTS !' else null end
    as user_comments
from modified_data
group by task_id;

Checkbox Item: character string buffer too small (APEX 4.0. - 4.2.)

Hi all,
I'm currently running the Oracle Application Express 4.0.2 on the Oracle DB 11g and thinking about the APEX upgrading to current 4.2. version. We have there quite big application used by the inernal employees so prior I need to test, if the migration will work.
I installed the new server with database and the APEX 4.2. and import the current application. Everything seems to working good except few checkboxes, which returns me the error: "ORA-06502: PL/SQL: numeric or value error: character string buffer too small."
LOV (Source) Code of Checkbox Item:
SELECT email as display_value, id as return_value
FROM users
WHERE <some conditions>;
In the current version 4.0.2. I get the checkbox item (total count of the rows approx. 650), but in the 4.2. I get this "string buffer too small" error and the page could not be rendered (if I add to the same query limitation: "rownum<242" it will display the item).
Could you please help me with this issue? Any idea, what I should set up in the new APEX to get the same results or you see there any limitation, why it does not work in the new version, but in the old version the same SQL works fine?
Thank you all in advance.
Regards,
Tomas.

1007462 wrote:
Hi all,Welcome to the forum: please read the FAQ and forum sticky threads (if you haven't done so already), and update your forum profile with a real handle instead of "1007462".
I'm currently running the Oracle Application Express 4.0.2 on the Oracle DB 11g and thinking about the APEX upgrading to current 4.2. version. We have there quite big application used by the inernal employees so prior I need to test, if the migration will work.
I installed the new server with database and the APEX 4.2. and import the current application. Everything seems to working good except few checkboxes, which returns me the error: "ORA-06502: PL/SQL: numeric or value error: character string buffer too small."
LOV (Source) Code of Checkbox Item:
SELECT email as display_value, id as return_value
FROM users
WHERE <some conditions>;
In the current version 4.0.2. I get the checkbox item (total count of the rows approx. 650), but in the 4.2. I get this "string buffer too small" error and the page could not be rendered (if I add to the same query limitation: "rownum<242" it will display the item).
Could you please help me with this issue? Any idea, what I should set up in the new APEX to get the same results or you see there any limitation, why it does not work in the new version, but in the old version the same SQL works fine?The total size of the HTML generated for an LOV-based item in APEX is restricted to 32K (this limit applies to every version). Why you are hitting this limit in the new instance may be due to differences in data or the database configuration (e.g. character set) rather than changes introduced in APEX.
Is the data exactly the same? Is the database configuration the same? When you limit the number of rows so the checkboxes are displayed and view the page source, is there any difference in the HTML used to render the checkbox form elements between the two versions?
That said, from a usability perspective 650 LOV options is rather a lot, and your application may very well outgrow this limit naturally in any version of APEX as more users as added. It is probably worthwhile thinking about other ways to display these options.

ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion

Hi all,
the following query select to_char(nvl(round(pc.target_cost*xx_primavera.geteurtolvrate,2),amount),'FM999G999G999G999G990D00') detail_amount,
nvl(ct.cost_type, description) detail_description,
tm_desc.memo_id,
primavera_prj_name detail_prj_name,
hp.party_number detail_party_number,
xpid.interface_line_attribute1,
utl_i18n.unescape_reference(replace(regexp_replace(utl_raw.cast_to_varchar2(tm_desc.task_memo), '<[^>]*>'), chr(13)||chr(10))) document_description,
REPLACE(regexp_replace(utl_raw.cast_to_varchar2(tm_id.task_memo), '<[^>]*>'), chr(13)||chr(10)) prim_memo_client_id
from XX_PRIMAVERA_INVOICES_DETAIL xpid
join admuser.xx_ar_hz_parties xahp on xahp.orig_system_bill_customer_id = xpid.orig_system_bill_customer_id
join hz_parties hp on hp.party_id = xahp.party_id
left join admuser.projcost pc on pc.proj_id = xpid.primavera_prj_id and pc.cost_type_id != 29 and xpid.service_code = 8 and pc.task_id = xx_primavera.getTaskId(xpid.primavera_prj_id,'A1020', 'Изготвяне на оферта') and delete_session_id is null
left join admuser.costtype ct on ct.cost_type_id = pc.cost_type_id
left join admuser.taskmemo tm_id on tm_id.proj_id = xpid.primavera_prj_id and tm_id.memo_type_id = 53 and tm_id.task_id = xx_primavera.getTaskId(xpid.primavera_prj_id,'A1020', 'Изготвяне на оферта')
left join admuser.taskmemo tm_desc on tm_desc.proj_id = xpid.primavera_prj_id and tm_desc.memo_type_id = 55 and tm_desc.task_id = xx_primavera.getTaskId(xpid.primavera_prj_id,'A1020', 'Изготвяне на оферта')
where amount != 0
and xpid.interface_line_attribute1 = :ra_ctp_attribute1
ORDER BY xpid.primavera_prj_name, xpid.description;returns error:
ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: 2371, maximum: 2000) I found that the error occurs in the row : utl_i18n.unescape_reference(replace(regexp_replace(utl_raw.cast_to_varchar2(tm_desc.task_memo), '<[^>]*>'), chr(13)||chr(10))) document_description,and tried to change it to: utl_i18n.unescape_reference(replace(regexp_replace(utl_raw.cast_to_varchar2(dbms_lob.substr(tm_desc.task_memo,1,2000)), '<[^>]*>'), chr(13)||chr(10))) document_description,....but it returns not value for that field... am i using dbms_lob.substr at the wrong place? The column 'tm_desc.task_memo' is BLOB type.
Any ideas how to cheat it ?
Version: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
PL/SQL Release 11.1.0.7.0 - Production
"CORE     11.1.0.7.0     Production"
TNS for Linux: Version 11.1.0.7.0 - Production
NLSRTL Version 11.1.0.7.0 - ProductionThanks in advance,
Bahchevanov.

Your second example has the parameters reversed. The amount (length) comes first and then the offset:
DBMS_LOB.SUBSTR (
   lob_loc     IN    BLOB,
   amount      IN    INTEGER := 32767,
   offset      IN    INTEGER := 1)
RETURN RAW;
DBMS_LOB.SUBSTR (
   lob_loc     IN    CLOB   CHARACTER SET ANY_CS,
   amount      IN    INTEGER := 32767,
   offset      IN    INTEGER := 1)
RETURN VARCHAR2 CHARACTER SET lob_loc%CHARSET;
DBMS_LOB.SUBSTR (
   file_loc     IN    BFILE,
   amount      IN    INTEGER := 32767,
   offset      IN    INTEGER := 1)
RETURN RAW;Also, remember that # of bytes is not necessarily the same as the # of characters depending on your character set. So 2000 bytes might become 4000 characters. And you have to make sure the BLOB is actually character data and not arbitrary binary data.
Post the results of reversing the parameters and using a smaller chunk size.

Error in notification - "character string buffer too small"

Hi All,
Hope everyone is doing great...
I have issue with one of the procedure which sends out status email for the reports. Below is the code.
It worked fine from last six months but today it failed because of the length of characters (more reports are added).
The variable "l_an_report" is VARCHAR and it has crossed it limit so gave the below error. Not sure how to handle the report so that it includes all the data.
Also please let me if this is good solution :- Have the report status in excel sheet and attach to the email.
If its fine please let me know how i can achieve this and any prerequisite from network team we need to get?
ERROR :-
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "REPORT_STAT.PACKG_EMAIL", line 441
ORA-06512: at line 2
Procedure PRC_SUMMARY IS
      l_an_report varchar2(32767);
      l_header VARCHAR2(1000);
      cnxn UTL_SMTP.connection;
      P_job           NUMBER (10)    DEFAULT TO_NUMBER (TO_CHAR (SYSDATE,'YYYYMMDD'));
BEGIN
                      l_an_report := '<style type="text/css">



</style>
<center><b><font face="Arial">Summary Report '
            || '<br><br></font></b></center>'
            || ' <div align="center"><table width="90%" border="1" cellspacing="0" cellpadding="1"'
            || 'style="font-size: 10pt; font-family: Arial" > '
            || '<tr bgcolor=b4b4b4><td align="center"> <font size="3"> <b>'
            || 'Report</b></td><td align="center"><font size="3"> <b>'
            || 'Run Duration </b></td><td align="center"><font size="3"> <b>'
            || 'Status</b></font></td></tr> ' || UTL_TCP.CRLF;
                FOR curr_refresh IN (SELECT
                                     AN.NAME report_NAME,
                                     ROUND(((ARH.RUN_END_TIME-ARH.RUN_START_TIME)*24*60),2) RUN_TIME,
                                     ARH.JOB_STATUS STATUS
                                     FROM
                                     REPORT_HISTORY ARH,REPORT AN
                                     WHERE
                                     ARH.RUN_START_TIME>TO_DATE(SYSDATE-93)
                                     AND AN.report_ID=ARH.report_ID
                                     and arh.JOB_NAME like 'QA%'
                                     and arh.JOB_STATUS='Completed')
                              LOOP
          l_an_report := l_an_report ||
          '<tr><td align="center">'|| curr_refresh.report_name|| '</td><td align="center">'|| curr_refresh.RUN_TIME ||
          '</td><td align="center">'|| curr_refresh.STATUS ||
           '</td><td align="center">' || UTL_TCP.CRLF;
            exit when length (l_an_report) > 32767;
      END LOOP;
       l_an_report := l_an_report || '</table><br><br>';
            FOR curr_email IN (SELECT global_name instance_name,
            REU.EMAIL_USER_LAST_NAME last_name,
            REU.EMAIL_USER_FIRST_NAME first_name,
            REU.EMAIL_USER_EMAIL_ID,
            '[email protected]' mail_from
                             FROM EMAIL_USER REU, EMAIL_GROUP REG,GLOBAL_NAME
                                         WHERE REU.EMAIL_GROUP_ID = REG.EMAIL_GROUP_ID
                                               AND REG.EMAIL_GROUP_NAME ='IT') LOOP
            cnxn := UTL_SMTP.open_connection('smtprelay.ats.com', 25);
            UTL_SMTP.helo(cnxn, 'smtprelay.ats.com');
            UTL_SMTP.mail(cnxn, '[email protected]');
            UTL_SMTP.rcpt(cnxn, curr_email.EMAIL_USER_EMAIL_ID);
               l_header := 'MIME-Version: 1.0'||'
               To: ' || curr_email.last_name || ' <' || curr_email.EMAIL_USER_EMAIL_ID || '>
               From: ' || curr_email.mail_from || '
               Subject: Summary Report for ' || curr_email.instance_name || ' on ' || to_char(sysdate, 'DD-MON-YYYY') || '
               Reply-To: [email protected]
               Content-Type: text/html;' || UTL_TCP.CRLF || UTL_TCP.CRLF;
            UTL_SMTP.data(cnxn, l_header || l_an_report);
            UTL_SMTP.quit(cnxn);
      END LOOP;
END PRC_SUMMARY;Please share your thoughts.
Regards,
Sunny

>
It worked fine from last six months but today it failed because of the length of characters (more reports are added).
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
>
The error is because you don't check the length of 'l_an_report' until it is already too long.
This code checks the length AFTER adding to it.
>
l_an_report := l_an_report ||
'<tr><td align="center">'|| curr_refresh.report_name|| '</td><td align="center">'|| curr_refresh.RUN_TIME ||
'</td><td align="center">'|| curr_refresh.STATUS ||
'</td><td align="center">' || UTL_TCP.CRLF;
exit when length (l_an_report) > 32767;
>
You need to test the length of the new string to be added to make sure it won't cause 'l_an_report' to be too long
-- add a new variable in the declare section
v_new_string VARCHAR2(2000);
-- in loop do calc
v_new_string := '<tr><td align="center">'|| curr_refresh.report_name|| '</td><td align="center">'|| curr_refresh.RUN_TIME ||
          '</td><td align="center">'|| curr_refresh.STATUS ||
           '</td><td align="center">' || UTL_TCP.CRLF;
-- test length
IF (length(v_new_string) + length (l_an_report) > 32767 THEN EXIT;But as others have said if you need to handle lengths > 32767 then use an attachment as shown in the links provided.

Listener Error - character string buffer too small (ORA-06502)

I am running into a very strange problem with the APEX listener on seemingly random pages. I can hit every page in my application just fine, but as soon as I hit this specific one, Glassfish throws an HTTP 500 error. If I click Debug, the page seems to load fine with no indications of trouble, but as soon as I turn debug back off, it goes back to the HTTP 500 error. I don't see anything special about the page that makes this happen. It is pretty simple and has 4 regions. I have noticed that if I set any 1 of the 4 regions to "Never display", the page loads fine. It's like having all 4 of them enabled at once are causing some overload, even though it's actually a smaller amount of data than most of my other pages.
**Update: I just discovered this only happens if I'm logged into the workspace first and then try to run the page! If I log out of APEX and then hit the application as a normal user, page loads error-free. This is still an annoying problem, but at least it seems I have a decent workaround since regular users never see it.
After a couple days, I noticed the exact same problem on a second APEX application I'm using. Again, it is on some random page whereas all the other pages work fine.
Both applications and pages in question worked without issue in APEX 3.x. I am trying to get an APEX application up and running on the latest version.
I have tried both Glassfish server and simply downloading the latest listener (version 1.1.1) and running it in standalone mode. I get the problem both ways, which is why it seems it's a listener issue.
I have seen a few other threads of people having this problem, but I never did find anyone with a solution, and most of the posts stopped back in December.
Some details on my environment:
Database version: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bi
APEX version: 4.0.2
Webserver: Glassfish 3.1
Here is the log entry from Glassfish when the HTTP 500 error displays as I try to load one of the bugged pages.
[#|2011-05-10T21:14:22.967-0500|INFO|oracle-glassfish3.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=111;_ThreadName=Thread-1;|MaxConnectionReuseCount=50000|#]
[#|2011-05-10T21:14:46.431-0500|SEVERE|oracle-glassfish3.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=112;_ThreadName=Thread-1;|
***********ERROR***********
init: # headers=46
declare nm owa.vc_arr := ?;
vl owa.vc_arr := ?;
begin
owa.init_cgi_env( ?, nm, vl );
htp.init; htp.HTBUF_LEN := 63;
? := sys_context('USERENV','SID');
end;
SID:1242
CALL:
begin
f(p=>?);
commit;
end;
BINDS
p:100:2:220529248574492::NOPAGE CALL:
declare
nlns number := 999999;
l_clob CLOB;
lines htp.htbuf_arr;
l_buff varchar2(32767);
l_clob_init boolean:= false;
l_file varchar2(5);
l_doc_info varchar2(1000);
begin
OWA.GET_PAGE(lines, nlns);
if (nlns > 1) then
for i in 1..nlns loop
if ( length(lines(i)) > 0 ) then
if ( ( lengthb(l_buff) + lengthb(lines(i))) > 32767) then
if (NOT l_clob_init) then
dbms_lob.createtemporary(l_clob, TRUE);
dbms_lob.open(l_clob, dbms_lob.lob_readwrite);
l_clob_init:=true;
end if;
dbms_lob.writeappend(l_clob,length(l_buff),l_buff);
l_buff := lines(i);
else
l_buff := l_buff || lines(i);
end if;
end if;
end loop;
end if;
if (l_clob_init) then
dbms_lob.writeappend(l_clob,length(l_buff),l_buff);
l_buff := '';
end if;
? := l_clob;
? := l_buff;
if (wpg_docload.is_file_download) then l_file:='TRUE'; wpg_docload.get_download_file(l_doc_info); else l_file := 'FALSE'; end if; ? := l_file;
? := l_doc_info;
end;
get_page FAILED:ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at line 33
Edited by: BrianB on May 11, 2011 7:50 AM
Edited by: BrianB on May 11, 2011 8:01 AM

Brian,
this post is going to get a bit longer, so the summary comes first.
h6. Summary
1. I could reproduce the problem on my system using the APEX Listener in standalone mode.
2. I don't think the problem is content-related in the sense that you have any issue in your page or database contents.
3. I have a workaround for your problem.
h6. Error message
Having that error in my environment made me start to think. I not only disabled some item and got it work, but I could also add something to achieve this effect.
So I came to think, this really is somewhere deep down. The error message doesn't seem very helpful on first sight, but when starting to follow on what's happening there, things get clearer:
APEX generates pages dynamically, replacing substitution strings and other tokens to get the actual page definition. This has to be read by a requesting client. The use of VARCHAR2 as buffer introduces a limit of 32767 bytes, after which the contents is handled as CLOB instead.
h6. Analysis
Obviously, there are cases where the "estimation" fails. Of course, this is may only be relevant in rare cases, because:
1. If a page would exceed the maximum without some charset interpretation problem, the buffer would be switched to clob.
2. If a page stays small enough to stay below 32767 even with some characters that are acutally larger then expected, the buffer isn't busted.
To find out, if your could be one of these rare cases, I investigated the HTTP headers, focussing on X-DB-Content-length and made an odd observation.
Test case 1: "Go" button disabled, so the page runs fine with APEX Listener
1. It has *31968 bytes* when coming from APEX Listener with a Go button disabled.
2. It has *31938 bytes* according to the header set by EPG - for exactly the same page.
That makes a difference of 30 bytes for what is expected to be the same contents.
Test case 2: The button is enabled again
1. This causes the page load to crash in APEX Listener.
2. EPG transports *32341 bytes* according to that header.
So we are pretty close to the hard limit for the VARCHAR2 buffer.
For some reason, APEX Listener seems to cause a false calculation of the actual page size. Whether this is due to some charset problem or due to some other problem with response handling, I don't know. The 30 bytes difference may result from the odd header "X-ORACLE-IGNORE" with value "IGNORE, IGNORE, IGNORE, IGNORE" sent by the APEX Listener. This value has exactly 30 bytes in length, but this could be coincidence, as there are more differences in headers. If I add the size of all headers, we are even closer to the buffer limit and probably exceed it when some items need more bytes than expected.
This could even be as simple as a line break, as your page has about 424 lines when I disabled the button... Adding 1 byte per line to the 32341 bytes of the EPG, I get 32765 bytes. Now add that button (403 bytes difference on EPG) and you exceeed the limit. Reduce that value by the line count again and you are still below.
Could be coincidence as well, but makes me wonder.
h6. Workaround
To make sure that we were actually hitting that limit, I now introduce my suggestion for a workaround.
Test case 3: Add a hidden item
1. APEX Listener loads the page, stating the size to be *32876 bytes*
2. EPG sees 30 bytes less and transmits the header with *32846 bytes*
h6. Conclusion
I can't give you a real solution for that problem, nor do I have a definitive answer on what is the root cause for it. It seems, only one of the developers may find it. But I can offer you a workaround, which is to just add some hidden item to your page so it exceeds the limit for the VARCHAR2 buffer and gets handled as clob.
Note that this may occur outside the app builder as well. The app builder just renders some additional items when starting that page, so it has a different size from its productive representation. On the other hand, I may start counting the size of that additional page section - I wouldn't wonder if that results in a value around 400 bytes, and this is the forgotten part...
Unfortunately, if it actually is happening outside of the app builder, this workaround isn't very handy: Dynamic contents can't be calculated that easy all the time, so you may have cases where you just don't know in advance if you are close to the limit and have to add some item to exceed it or if you've already exceeded it or if you are far below, or close enough to actually hit it when adding just one byte...
-Udo

APEX BUG ? Buffer too small for CLOB to CHAR or BLOB to RAW

Hi
I tried use search field (right top corner) in Application Builder for my APP. After while a had:
report error:
ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: 8000, maximum: 4000)
I changed my main table and now I would like search every appearance in app, I thought it's the best solution to use search.
Do you know how resolve my problem.
APEX ver 4.0.1.00.03

You can't...there's a limit of 4k for any page item in apex....attempting to convert or bring in more into a page item or even from an app process into a javascript variable, kicks that error.
It's a limitation with mod_plsql, there's a fix in 4.0 but it requires using the java listener instead of mod_plsql.

ORA-22835: Buffer too small for CLOB to CHAR on Solaris but not Windows

Hi,
I get the following error on Solaris but not Windows equivalent 10.2 installations
ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: 4575, maximum: 4000)
ORA-06512: at line 65
the code causing the problem is:
SELECT A.TABLE_NAME, A.DEFAULT_DIRECTORY_NAME, B.LOCATION,
CASE
WHEN INSTR(A.ACCESS_PARAMETERS,'RECORDS FIXED')<>0 THEN
SUBSTR(A.ACCESS_PARAMETERS,INSTR(A.ACCESS_PARAMETERS,'RECORDS FIXED')+14,3)
ELSE NULL
END RSZ FROM USER_EXTERNAL_TABLES A, USER_EXTERNAL_LOCATIONS B
WHERE A.TABLE_NAME = B.TABLE_NAME(+);
the entire code being executed is:
DECLARE
EX BOOLEAN;
CNT NUMBER;
SQL1 VARCHAR2(4000);
FLEN NUMBER;
BSIZE NUMBER;
TABNAME VARCHAR2(4000);
DEFDIR VARCHAR2(4000);
RSZ VARCHAR2(4000);
ECODE NUMBER(38);
ERRMSG VARCHAR2(4000);
CURSOR C1 IS
SELECT A.TABLE_NAME, A.DEFAULT_DIRECTORY_NAME, B.LOCATION,
CASE
WHEN INSTR(A.ACCESS_PARAMETERS,'RECORDS FIXED')<>0 THEN
SUBSTR(A.ACCESS_PARAMETERS,INSTR(A.ACCESS_PARAMETERS,'RECORDS FIXED')+14,3)
ELSE NULL
END RSZ FROM USER_EXTERNAL_TABLES A, USER_EXTERNAL_LOCATIONS B
WHERE A.TABLE_NAME = B.TABLE_NAME(+);
TYPE C1_TYPE IS TABLE OF C1%ROWTYPE;
REC1 C1_TYPE;
BEGIN
OPEN C1;
FETCH C1 BULK COLLECT INTO REC1;
FOR I IN REC1.FIRST .. REC1.LAST
LOOP
UTL_FILE.FGETATTR(NVL(REC1(I).DEFAULT_DIRECTORY_NAME,'CARDSLOAD'),
REC1(I).LOCATION, EX, FLEN, BSIZE);
IF EX THEN
IF INSTR(TO_CHAR(REC1(I).RSZ),'\.')<>0 THEN
     DBMS_OUTPUT.PUT_LINE('INVALID RECORDSIZE OR CORRUPTED FILE');
     END IF;
     DBMS_OUTPUT.PUT_LINE('Table Name: ' || TO_CHAR(REC1(I).TABLE_NAME));
DBMS_OUTPUT.PUT_LINE('File Exists '||REC1(I).LOCATION);
     DBMS_OUTPUT.PUT_LINE('File Length: ' || TO_CHAR(FLEN));
     DBMS_OUTPUT.PUT_LINE('Record Size: ' || TO_CHAR(REC1(I).RSZ));
DBMS_OUTPUT.PUT_LINE('Block Size: ' || TO_CHAR(BSIZE));
     DBMS_OUTPUT.PUT_LINE('# RECORDS: ' || FLEN/TO_NUMBER(REC1(I).RSZ));
     BEGIN
     CNT:='';
     SQL1:='SELECT COUNT(*) FROM '|| REC1(I).TABLE_NAME;
     EXECUTE IMMEDIATE SQL1 INTO CNT;
DBMS_OUTPUT.PUT_LINE('SELECT COUNT FOR: ' || REC1(I).TABLE_NAME||' = '||CNT);
     EXCEPTION
     WHEN OTHERS THEN
     DBMS_OUTPUT.PUT_LINE('SELECT COUNT FAILED FOR: ' || REC1(I).TABLE_NAME);
     ECODE := SQLCODE;
ERRMSG := SQLERRM;
DBMS_OUTPUT.PUT_LINE(ECODE||' '||ERRMSG);
     END;
ELSE
DBMS_OUTPUT.PUT_LINE(REC1(I).TABLE_NAME||' '||REC1(I).LOCATION||' File Does Not Exist');
END IF;
     DBMS_OUTPUT.PUT_LINE('-----------------------------------------------------');
END LOOP;
CLOSE C1;
EXCEPTION
WHEN OTHERS THEN RAISE;
END;
Any ideas why Solaris but not Windows would have this problem?
Thanks,
Victor

Check out Bug 4715104 - ORA-22835 / truncated data from USER/ALL/DBA_EXTERNAL_TABLES

OWB 9.2: expression length limit (4000) too small

Similar Messages

Maybe you are looking for