Scheduler agent can't submit state ORA-06502:

hi all
scheduler agent can't submit state
getting below error on agent side in $ORACLE_HOME/data/agent.log
2012.08.31 03:32:56 MSD Job terminated successfully. Duration: 14.89 seconds
2012.08.31 03:32:56 MSD Database Error on Submit: Job Run Completion Failed!
2012.08.31 03:32:56 MSD Database Error on Submit: Error: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
wtf ?
Edited by: djeday84 on Aug 31, 2012 10:34 AM
ps: db oel 5.8 psu 11.2.0.3.2
client win 2003 ( scheduler agent 11.2.0.3 )

Hi Sridher,
is there any question attached to your posting?
How long is the answer of your web service? (in bytes)
brgds,
Peter
Blog: http://www.oracle-and-apex.com
ApexLib: http://apexlib.oracleapex.info
BuilderPlugin: http://builderplugin.oracleapex.info
Work: http://www.click-click.at

Similar Messages

Disco for Oracle Apps with Scheduling not in Apps ~ Throws Error ORA-06502

Hi All,
I have had an SR with Oracle for almost 1/2 year now to set-up scheduling with the scheduling schema not being Apps. They have not been able to fix this yet.
I have used note 757831.1. When I try to set-up a schedule that is recurring, the following error is thrown: ORA-06502.
Does any one have a success story associated with setting-up scheduling in a Disco Oracle Apps end user layer where the scheduling schema is not apps?
Thanks,
Patrick
Edited by: Patrick Bacon on Dec 10, 2010 7:18 AM
Edited by: Patrick Bacon on Dec 10, 2010 8:21 AM

Pl do not post contents of MOS Docs publicly - this violates terms of your support contract.
We were successful in doing this with Disco 4i a long time ago. I am assuming the process is the same for 10g. Pl see if these MOS Docs can help. Pl post the complete error message.
Error When Trying To Schedule Workbooks: The Batch Repository Schema Must Have Been Granted Direct Access To All Of The Tables Referenced In This Sheet (Doc ID 1125208.1)
How To Store Scheduled Workbooks Results In A Different Schema Other than APPS? (Doc ID 370855.1)
Error When Trying To Schedule Workbooks: The Batch Repository Schema Must Have Been Granted Direct Access To All Of The Tables Referenced In This Sheet (Doc ID 464968.1)
Discoverer Quick Start: Setting Up Workbook Scheduling (Doc ID 74116.1)
Scheduling Workbooks In A Applications Mode EUL Configured With A Batch User Fails With Errors ORA-06502, ORA-06512 (Doc ID 331165.1)
HTH
Srini

Can Only Compile a Package in Object Browser ORA-06502

I am running Apex 3.0.1 against a 10.2 Database..
I have at least 2 packages, that I can only change in APEX using the Object Browser, If I try using SQL Developer/TOAD or any other tools it returns the error message below. The package bodies are around 400 Lines and 1500 Lines. This even happens if I try to compile with no changes .. But I can make all my changes in Object Browser I want without the error messages..
Any ideas of where to start...
Error at line 1
ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at line 14
Kathy

Open your package in TOAD and have a look at the line 14. There is probably a variable
which is too small to take a value specified.
Denes Kubicek
http://deneskubicek.blogspot.com/
http://www.opal-consulting.de/training
http://apex.oracle.com/pls/otn/f?p=31517:1
-------------------------------------------------------------------

Sql Query (updateable Report) returning ORA-06502: PL/SQL: numeric or value

Hi I have a Sql Query Report Region as defined below. On the report attributes I am not using any "Row Selector". In a After submit process I try to print out the results of the value I have entered in as a value in updatable report and i get the error: I am doing this as a test before i use the data to insert into another table...
I receive this error if I enter in a characters (not numeric) into the "Field Value" field.:
ORA-06502: PL/SQL: numeric or value error: character to number conversion error.
If I enter in a numeric into the "Field Value" text box, then I get the value displayed back without error. I need to be able to enter a varchar value without error.
My SQL QUERY is:
select i.INDEXED_FIELD_ID, i.field_name,
HTMLDB_ITEM.TEXT(3,d.indexed_field_value) field_value,
decode(f.required, 0, 'O', 1, 'R', 'NOT USED') REQUIRED
from XXVG_EFILE_DOCUMENT_FIELDS D,
xxvg_efile_type_fields f, xxvg_efile_indexed_fields i
WHERE f.indexed_field_id = i.indexed_field_id
and f.required in (0,1)
and i.indexed_field_id = d.indexed_field_id(+)
and d.document_id(+) = -1
and f.document_type_id = :p21_doc_type
My after submit process is the following...**Note** I am using P21_test as a field just to display my test. I receive the value back just fine without error if numeric. If varchar, that is when the problems occur. I have used just a length variable like the lettter 't' for testing and still receive the error.
DECLARE
vRow BINARY_INTEGER;
BEGIN
-- update field values
FOR i IN 1 .. HTMLDB_APPLICATION.g_f03.COUNT -- your field value
LOOP
vRow := HTMLDB_APPLICATION.g_f03(i);
IF vRow is Not NULL --means the field has data in it.
THEN
:p21_test := HTMLDB_APPLICATION.G_F03(i); --set a variable to the field with data.
END IF;
END LOOP;
END;
Is there a conversion I need to do? I do not want to do this via checkboxes as I dont want the user have to check a checkbox and then enter a value in. I just want a blank text box the user can enter a value in and then i can do an insert.
Thanks So much.

Thanks Scott, That did do the trick as the varchar is now displayed of the entered item.
How do i also display the value of indexed_field_id as well.
I have an insert where i need the indexed field id and the entered field value.
Thanks in advance.

PL/SQL function body returning SQL query - ORA-06502: PL/SQL: numeric or value error

I'm attempting to dynamically generate a rather large SQL query via the "PL/SQL function body returning SQL query" report region option. The SQL query generated will possibly be over 32K. When I execute my page, I sometimes receive the "ORA-06502: PL/SQL: numeric or value error" which points to a larger than 32K query that was generated. I've seen other posts in the forum related to this dynamic SQL size limitation issue, but they are older (pre-2010) and point to the 32K limit of the DNS (EXECUTE IMMEDIATE) and DBMS_SQL. I found this post (dynamic sql enhancements in 11g) which discusses 11g no longer having the 32K size limitation for generating dynamic SQL. Our environment is on 11gR2 and using ApEx 4.2.1. I do not know which dynamic SQL method -- DNS or DBMS_SQL -- ApEx 4.2.1 is using. Can someone clarify for me which dynamic SQL method ApEx uses to implement the "PL/SQL function body returning SQL query" option?
As a test, I created a page on apex.oracle.com with a report region with the following source:
declare
l_stub varchar2(25) := 'select * from sys.dual ';
l_sql clob := l_stub || 'union all ';
br number(3) := 33;
begin
while length ( l_sql ) < 34000 loop
 l_sql := l_sql || l_stub || 'union all ';
end loop;
l_sql := l_sql || l_stub;
for i in 1 .. ceil ( length ( l_sql ) / br ) loop
 dbms_output.put_line ( dbms_lob.substr ( l_sql, br, ( ( i - 1 ) * br ) + 1 ) );
end loop;
return l_sql;
end;
The dbms_output section is there to be able to run this code in SQL*Plus and confirm the size of the SQL is indeed larger than 32K. When running this in SQL*Plus, the procedure is successful and produces a proper SQL statement which can be executed. When I put this into the report region on apex.oracle.com, I get the ORA-06502 error.
I can certainly implement a work-around for my issue by creating a 'Before Header' process on the page which populates an ApEx collection with the data I am returning and then the report can simply select from the collection, but according to documentation, the above 32K limitation should be resolved in 11g. Thoughts?
Shane.

What setting do you use in your report properties - especially in Type and in Region Source?
If you have Type="SQL Query", then you should have a SELECT statement in the Region Source. Something like: SELECT .... FROM ... WHERE
According to the ERR-1101 error message, you have probably set Type to "SQL Query (PL/SQL function body returning SQL query)". In this situation APEX expects you to write a body of a PL/SQL function, that will generate the text of a SQL query that APEX should run. So it can be something like:
declare
mycond varchar2(4000);
begin
if :P1_REPORT_SEARCH is not null THEN
mycond:='WHERE LAST_NAME like :P1_REPORT_SEARCH ||''%''';
end if;
return 'select EMPLOYEE_ID, FIRST_NAME, LAST_NAME from EMPLOYEES ' ||mycond;
end;
And for escaping - are you interested in escaping the LIKE wildcards, or the quotes?
For escaping the wildcards in LIKE function so that when the user enters % you will find a record with % and not all functions, look into the SQL Reference:
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14200/conditions007.htm
(You would than need to change the code of your function accordingly).
If you are interested in escaping the quotes, try to avoid concatenating the values entered by the user into the SQL. If you can, use bind variables instead - as I have in my example above. If you start concatenating the values into the text of SQL, you are open to SQLInjection - user can enter anything, even things that will break your SQL. If you really need to allow users to choose the operator, I would probably give them a separate combo for operators and a textfield for values, than you could check if the operator is one of the allowed ones and create the condition accordingly - and than still use bind variable for inserting the filtering value into the query.

ORA-06502 - Error when running "Ask The Expert 0.9"

Hi ,
I successfully installed "Ask the Expert" package with Apex 3.0 on Oracle 10g Database 10.2.0.1.0. No error ocurred during the import in my Apex environment.
Besides that, i'm having problems when i tried to run the "Aks the Expert". It always shows the following message errors:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
Error Unable to write activity log.
I think it was a problem with APEX instalation, but i could run the Sample Application of Apex without any problem.
I opened an SR in Metalink, but to my surprise, the analist of support don't know what's wrong with the demo "Ask de Expert".
The debug function of the application show the following commands before the error ocurrs:
0.01:
0.01: S H O W: application="103" page="1" workspace="" request="" session="6648566035252817"
0.01: Language derived from: FLOW_PRIMARY_LANGUAGE, current browser language: en-us
0.01: alter session set nls_language="AMERICAN"
0.01: alter session set nls_territory="AMERICA"
0.01: NLS: CSV charset=WE8MSWIN1252
0.01: ...NLS: Set Decimal separator="."
0.01: ...NLS: Set NLS Group separator=","
0.02: ...NLS: Set date format="DD-MON-RR"
0.02: ...Setting session time_zone to -03:00
0.02: NLS: Language=en-us
0.02: Application 103, Authentication: CUSTOM2, Page Template: 667896385843019243
0.02: ...Determine if user "N3COUTINHO" workspace "951808960237899" can develop application "103" in workspace "951808960237899"
0.02: ...ok to reuse builder session for user:nobody
0.03: ...Application session: 6648566035252817, user=nobody
0.03: ...Determine if user "N3COUTINHO" workspace "951808960237899" can develop application "103" in workspace "951808960237899"
0.03: Session: Fetch session header information
0.03: ...Metadata: Fetch page attributes for application 103, page 1
0.03: Fetch session state from database
0.03: Branch point: BEFORE_HEADER
0.03: Fetch application meta data
0.04: Computation point: BEFORE_HEADER
0.04: ...Perform computation of item: P1_CLEAN_CRITERIA, type=FUNCTION_BODY
0.04: ...Performing function body computation
0.06: ...Session State: Save "P1_CLEAN_CRITERIA" - saving same value: ""
0.06: Processing point: BEFORE_HEADER
0.06: ...Process "Read and Write Activity Cookie": PLSQL (BEFORE_HEADER) declare l_cookie_id number; begin owa_util.mime_header('text/html', FALSE); -- ate_api.read_activity_cookie; l_cookie_id := ate_api.fetch_activity_cookie_val( 'COOKIE_ID' ); -- if l_cookie_id is null then l_cookie_id :=
Content-type: text/html; charset=ISO-8859-1 Set-Cookie: activity_ask_expert=1|2400346189796; expires=Wed, 01-Jan-2020 08:00:00 GMT; path=/;
0.06: Encountered unhandled exception in process type PLSQL
0.06: Show ERROR page...
0.06: Performing rollback...
Please, could any one help me to solve this problem ? Metalink couldn't help me diagnosing what's wrong.
Thanks,
Sergio Coutinho

Hi,
I don´t know if it help the analisis, but i collect some informations about my environment:
1) HTML DB version
3.0.1
2) Database version
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
3) Database server operating system (as well, if 32-bit or 64-bit)
Solaris 5.9 - 64 bits
4) Database Parameters:
PARAMETER VALUE
NLS_CALENDAR GREGORIAN
NLS_CHARACTERSET WE8ISO8859P1
NLS_COMP BINARY
NLS_CURRENCY $
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_DUAL_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_LANGUAGE AMERICAN
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_NCHAR_CONV_EXCP FALSE
NLS_NUMERIC_CHARACTERS .,
NLS_RDBMS_VERSION 10.2.0.1.0
NLS_SORT BINARY
NLS_TERRITORY AMERICA
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
Could it explain why ASK THE EXPERT is running on hosted apex site and it´s
generating error when running in my environment?
Thanks for the help !
Sergio

ORA-06502: PL/SQL: numeric or value error: Bulk Bind: Truncated Bind

Hi
I am getting this run time error ORA-06502: PL/SQL: numeric or value error: Bulk Bind: Truncated Bind in my pl/sql . I tried evrything , changing datatypes ,etc but still this error is coming .What can be the cause , please help.
declare
svid xxpor_utility.p_svid@sppmig1%type;
p_sv_id xxpor_utility.p_svid@sppmig1%type;
tab xxpor_utility.xxpor_indextab@sppmig1;
svid1 xxpor_utility.p_svid@sppmig1%type;
p_sv_id1 xxpor_utility.p_svid@sppmig1%type;
tab1 xxpor_utility.xxpor_indextab@sppmig1;
svid2 xxpor_utility.p_svid@sppmig1%type;
p_sv_id2 xxpor_utility.p_svid@sppmig1%type;
tab2 xxpor_utility.xxpor_indextab@sppmig1;
svid3 xxpor_utility.p_svid@sppmig1%type;
p_sv_id3 xxpor_utility.p_svid@sppmig1%type;
tab3 xxpor_utility.xxpor_indextab@sppmig1;
v_index t2_error_table.id_value%type;
v_code t2_error_table.error_code%type;
p_error varchar2(600);
k number(20):=0;
v_msg varchar2(2000);
v_commit_count number(10);
v_at_gpid varchar2(512);
v_at_oper varchar2(512);
v_sch varchar2(512);
v_vat varchar2(512);
exp exception;
exp1 exception;
exp2 exception;
exp3 exception;
exp4 exception;
v_pay varchar2(512);
v_res varchar2(512);
v_digit varchar2(512);
v_agree varchar2(512);
v_driver_licence PERSON_HISTORY.drivers_licence%TYPE;
v_cus_gen1 number(10);
v_cus_gen2 number(10);
v_cus_gen3 number(10);
svid_sr number(10);
v_social PERSON_HISTORY.social_security_number%TYPE;
CURSOR person_cur (p_person_id person_history.person_id%TYPE)
IS
SELECT drivers_licence ,social_security_number
FROM PERSON_HISTORY@SPPMIG1
WHERE PERSON_ID=p_person_id --p2(p).person_id
     AND EFFECTIVE_START_DATE = (SELECT MAX(EFFECTIVE_START_DATE)
     FROM PERSON_HISTORY@sppmig1
                                        WHERE PERSON_ID=p_person_id);--p2(p).person_id) ;
--p number(20):=1;
--j number(20);
cursor c1 is
select * from cus_node_his ;
type temp_c1 is table of customer_node_history%rowtype
index by binary_integer;
t2 temp_c1;
type temp_c2 is table of customer_node_history@slpmig1%rowtype
index by binary_integer;
p2 temp_c2;
/*cursor c2(p_id customer_query.customer_node_id%type) is
select general_1,general_2,general_3
from customer_query@sppmig1 c where c.customer_query_type_id=10003 and
c.customer_node_id(+) =p_id
and c.open_date = (select
max(open_date) from customer_query@sppmig1 where customer_node_id=p_id
and customer_query_type_id=10003 and c.customer_query_id =(select max(customer_query_id) from customer_query@sppmig1
where customer_node_id=p_id and customer_query_type_id=10003));*/
procedure do_bulk_insert is
bulk_errors EXCEPTION;
PRAGMA EXCEPTION_INIT(bulk_errors, -24381);
begin
forall j in 1..t2.count SAVE EXCEPTIONS
insert into aaa values t2(j);
commit;
--t2.delete;
k:=0;
v_msg:=sqlerrm;
EXCEPTION WHEN bulk_errors THEN
FOR L IN 1..SQL%bulk_exceptions.count
LOOP
v_index := SQL%bulk_exceptions(L).ERROR_INDEX;
v_code := sqlerrm(-1 * SQL%bulk_exceptions(L).ERROR_CODE);
--v_index := SQL%bulk_exceptions(j).ERROR_INDEX;
--v_code := sqlerrm(-1 * SQL%bulk_exceptions(j).ERROR_CODE);
INSERT INTO t2_error_table
VALUES('CUSTOMER_NODE_HISTORY',
'CUSTOMER_NODE_ID',
v_msg,
t2(v_index).customer_node_id,
null,
'DO_BULK_INSERT',
v_code
commit;
END LOOP;
end do_bulk_insert;
begin
select value into v_at_gpid from t2_system_parameter@sppmig1 where name='atlanta_group_id';
select value into v_commit_count from t2_system_parameter@sppmig1 where name='batch_size';
select value into v_sch from t2_system_parameter@sppmig1 where name='schedule_id';
select value into v_pay from t2_system_parameter@sppmig1 where name='payment_location_code';
select value into v_at_oper from t2_system_parameter@sppmig1 where name='atlanta_operator_id';
select value into v_digit from t2_system_parameter@sppmig1 where name='digits_to_be_screened';
select value into v_res from t2_system_parameter@sppmig1 where name='responsible_agent';
select value into v_vat from t2_system_parameter@sppmig1 where name='vat_rate';
select value into v_agree from t2_system_parameter@sppmig1 where name='bank_agreement_status';
xxpor_utility.xxpor_loadmemory@sppmig1('CUSTOMER_NODE_HISTORY','CUSTOMER_NODE_TYPE_ID',tab);
xxpor_utility.xxpor_loadmemory@sppmig1('CUSTOMER_NODE_HISTORY','CREDIT_RATING_CODE',tab2);
xxpor_utility.xxpor_loadmemory@sppmig1('CUSTOMER_NODE_HISTORY','PAYMENT_METHOD_CODE',tab3);
xxpor_utility.xxpor_loadmemory@sppmig1('CUSTOMER_NODE_HISTORY','CUSTOMER_NODE_STATUS_CODE',tab1);
open c1;
loop
fetch c1 bulk collect into p2 limit v_commit_count;
for p in 1..p2.count loop
k:=K+1;
begin
xxpor_utility.xxpor_getsvid@sppmig1(p2(p).CUSTOMER_NODE_TYPE_ID,tab,svid);
p_sv_id:=svid;
xxpor_utility.xxpor_getsvid@sppmig1(p2(p).CUSTOMER_NODE_STATUS_CODE,tab1,svid1);
p_sv_id1 :=svid1;
xxpor_utility.xxpor_getsvid@sppmig1(p2(p).CREDIT_RATING_CODE,tab2,svid2);
p_sv_id2:=svid2;
xxpor_utility.xxpor_getsvid@sppmig1(p2(p).PAYMENT_METHOD_CODE,tab3,svid3);
p_sv_id3:=svid3;
OPEN person_cur (p2(p).person_id);
FETCH person_cur INTO v_driver_licence, v_social;
CLOSE person_cur;
--select social_security_number into v_social from person_history@sppmig1 where
--PERSON_ID=p2(p).person_id AND EFFECTIVE_START_DATE = (SELECT MAX(EFFECTIVE_START_DATE) FROM
--PERSON_HISTORY@sppmig1 WHERE PERSON_ID=p2(p).person_id) ;
/*open c2(p2(p).customer_node_id);
fetch c2 into v_cus_gen1, v_cus_gen2, v_cus_gen3;
close c2;
xxpor_utility.get_status_code@sppmig1(v_cus_gen1,v_cus_gen2,v_cus_gen3,svid_sr);*/
svid_sr:=2600000;
t2(k).CUSTOMER_NODE_ID     :=     p2(p).CUSTOMER_NODE_ID;
t2(k).LAST_MODIFIED          :=     p2(p).LAST_MODIFIED;
t2(k).EFFECTIVE_START_DATE     :=     p2(p).EFFECTIVE_START_DATE;
t2(k).EFFECTIVE_END_DATE     :=     p2(p).EFFECTIVE_END_DATE;
t2(k).CUSTOMER_NODE_TYPE_ID     := p_sv_id;
if p_sv_id is null then
raise exp1;
end if;
t2(k).PRIMARY_IDENTIFIER      :=     p2(p).PRIMARY_IDENTIFIER;
t2(k).PRIMARY_IDENTIFIER2     :=     p2(p).PRIMARY_IDENTIFIER2;
t2(k).NODE_NAME           :=     p2(p).NODE_NAME ;
t2(k).NODE_NAME_UPPERCASE     :=     p2(p).NODE_NAME_UPPERCASE ;
t2(k).NODE_NAME_SOUNDEX     :=     p2(p).NODE_NAME_SOUNDEX;
t2(k).ATLANTA_GROUP_ID          := v_at_gpid ;
t2(k).ATLANTA_OPERATOR_ID     :=     p2(p).ATLANTA_OPERATOR_ID;
t2(k).GL_CODE_ID          :=     p2(p).GL_CODE_ID;
t2(k).PARENT_CUSTOMER_NODE_ID     := p2(p).PARENT_CUSTOMER_NODE_ID ;
t2(k).HIERARCHY_LEVEL          := p2(p).HIERARCHY_LEVEL ;
t2(k).ROOT_CUSTOMER_NODE_ID      := p2(p).ROOT_CUSTOMER_NODE_ID ;
t2(k).CUSTOMER_NODE_STATUS_CODE := p_sv_id1 ;
if p_sv_id1 is null then
raise exp2;
end if;
t2(k).CREATED_DATE     :=          p2(p).CREATED_DATE;
t2(k).ACTIVE_DATE      :=          p2(p).ACTIVE_DATE ;
t2(k).PERSON_ID     :=          p2(p).PERSON_ID ;
t2(k).PRIME_ACCOUNT_ID :=          p2(p).PRIME_ACCOUNT_ID;
t2(k).REPORT_LEVEL_CODE :=          p2(p).REPORT_LEVEL_CODE;
t2(k).POSTAL_ADDRESS_ID     :=     p2(p).POSTAL_ADDRESS_ID;
t2(k).SITE_ADDRESS_ID     :=     p2(p).SITE_ADDRESS_ID ;
t2(k).CURRENCY_ID      :=          p2(p).CURRENCY_ID;
t2(k).SCHEDULE_ID     :=          v_sch;
t2(k).BILLING_PRIORITY     :=     p2(p).BILLING_PRIORITY ;
t2(k).BILLING_COMPLEXITY:=          p2(p).BILLING_COMPLEXITY ;
t2(k).BILLING_CONFIGURATION_CODE     := p2(p).BILLING_CONFIGURATION_CODE;
t2(k).SUPPRESS_IND_CODE           := p2(p).SUPPRESS_IND_CODE ;
t2(k).SUPPRESS_BILL_CYCLE_COUNT := p2(p).SUPPRESS_BILL_CYCLE_COUNT;
t2(k).SUPPRESS_UNTIL_ISSUE_DATE := p2(p).SUPPRESS_UNTIL_ISSUE_DATE;
t2(k).TURNOVER               := p2(p).TURNOVER;
t2(k).TURNOVER_CURRENCY_ID      :=     p2(p).TURNOVER_CURRENCY_ID ;
t2(k).CREDIT_LIMIT           :=     p2(p).CREDIT_LIMIT ;
t2(k).CREDIT_LIMIT_CURRENCY_ID :=     p2(p).CREDIT_LIMIT_CURRENCY_ID;
t2(k).EXPECTED_REVENUE      :=     p2(p).EXPECTED_REVENUE ;
t2(k).EXPECTED_REVENUE_CURRENCY_ID     := p2(p).EXPECTED_REVENUE_CURRENCY_ID ;
t2(k).CREDIT_RATING_CODE      :=     p_sv_id2 ;
-- if p_sv_id2 is null then
--raise exp3;
-- end if;
t2(k).CREDIT_COMMENTS           := p2(p).CREDIT_COMMENTS ;
t2(k).TAX_CLASS_CODE          := 1     ;
t2(k).PAYMENT_METHOD_CODE     :=     p_sv_id3;
--if p_sv_id3 is null then
--raise exp4;
--end if;
t2(k).PAYMENT_LOCATION_CODE      := v_pay ;
t2(k).BANK_CODE           :=     NULL;
t2(k).BRANCH_CODE           :=     NULL ;
t2(k).BANK_ACCOUNT_NAME     :=     p2(p).NODE_NAME ;
t2(k).BANK_ACCOUNT_NUMBER     :=     '1000000';
t2(k).BANK_ACCOUNT_REF      :=     v_agree;
t2(k).CARD_TYPE_CODE          := p2(p).CARD_TYPE_CODE     ;
t2(k).CARD_NUMBER          :=     p2(p).CARD_NUMBER ;
t2(k).CARD_EXPIRY_DATE          := NULL ;
t2(k).ASSIGNED_OPERATOR_ID      :=     NULL ;
t2(k).SALES_CHANNEL_CODE     :=     0;
t2(k).COMPANY_NUMBER          := NULL;
t2(k).INDUSTRY_CODE          :=     NULL;
t2(k).REGION_CODE           :=     NULL;
t2(k).GENERAL_1          :=     v_vat ;
t2(k).GENERAL_2           :=     svid_sr ;
if svid_sr is null then
raise exp;
end if;
t2(k).GENERAL_3           :=     v_social ;
t2(k).GENERAL_4           :=     v_driver_licence ;
t2(k).GENERAL_5           :=     v_vat;
t2(k).GENERAL_6           :=     v_res;
t2(k).GENERAL_7           :=     null||':'||null||':'||'1000000'||':'||null||':'||null||':'||null||':';
t2(k).GENERAL_8          :=     '2' ;
t2(k).GENERAL_9           :=     v_digit;
t2(k).GENERAL_10          :=     p2(p).CUSTOMER_NODE_ID;
exception when exp then
p_error:= sqlerrm;
insert into t2_error_table values ( 'CUSTOMER_NODE_HISTORY','CUSTOMER_NODE_ID',p_error,p2(p).customer_node_id
,null,null,null);
commit;
when exp1 then
p_error:= sqlerrm;
insert into t2_error_table values ( 'CUSTOMER_NODE_HISTORY','CUSTOMER_NODE_ID',p_error,p2(p).customer_node_id
,null,null,'customer_node_type_id is null');
commit;
when exp2 then
p_error:= sqlerrm;
insert into t2_error_table values ( 'CUSTOMER_NODE_HISTORY','CUSTOMER_NODE_ID',p_error,p2(p).customer_node_id
,null,null,'customer_node_status_code is null');
commit;
/*when exp3 then
p_error:= sqlerrm;
insert into t2_error_table values ( 'CUSTOMER_NODE_HISTORY','CUSTOMER_NODE_ID',p_error,p2(p).customer_node_id
,null,null,'credit_rating_code is null');
commit;
when exp4 then
p_error:= sqlerrm;
insert into t2_error_table values ( 'CUSTOMER_NODE_HISTORY','CUSTOMER_NODE_ID',p_error,p2(p).customer_node_id
,null,null,null);
commit;*/
when others then
p_error:= sqlerrm;
insert into t2_error_table values ( 'CUSTOMER_NODE_HISTORY','CUSTOMER_NODE_ID',p_error,p2(p).customer_node_id
,null,null,null);
commit;
end;
if mod(k,v_commit_count)=0 then
do_bulk_insert;
t2.delete;
end if;
end loop;
do_bulk_insert;
exit when c1%notfound;
end loop;
t2.delete;
exception when others then
p_error:= sqlerrm;
insert into t2_error_table values ( 'CUSTOMER_NODE_HISTORY','CUSTOMER_NODE_ID',p_error,null
,null,null,null);
commit;
RAISE;
end;
/

Hi there,
Following is the description of the error, you are getting.
ORA-06502:VALUE_ERROR
An arithmetic, conversion, truncation, or size-constraint error occurs. For example, when your program selects a column value into a character variable, if the value is longer than the declared length of the variable, PL/SQL aborts the assignment and raises VALUE_ERROR. In procedural statements, VALUE_ERROR is raised if the conversion of a character string into a number fails. (In SQL statements, INVALID_NUMBER is raised.)
Hopefully this will help.

-6502 ORA-06502: PL/SQL: numeric or value error when using 'Create CAPI Definition'

I get an error when I try to create a CAPI definition with Headstart untilities (6i). I use HSU_CAPI revision 6.5.2.0
The detailed information says the following:
Message
BLAPI.OPEN_ACTIVITY
Start HSU_CAPI.run
Number of Tables to create CAPI for 1
Initial checks for table KCS_TENDERS with id 692754610572409851363604771392473242
HSU_CAPT.initial_checks for table KCS_TENDERS
HSU_CAPF.initial_checks for table KCS_TENDERS
HSU_CAPC.initial_checks Custom Services for table KCS_TENDERS
HSU_CAPB.initial_checks BRDD for table KCS_TENDERS
bltext.get_lines_from_repository, p_text_type=CDINOT
bltext.get_line_containing
bltext.get_line_containing
bltext.get_lines_from_repository, p_text_type=CDIPLS
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
KCS_TENDERS Business Rule Design Definition BR_TNR001_CEV does not have any Trigger Columns. Rule will fire when any column is updated.
bltext.get_lines_from_repository, p_text_type=CDINOT
bltext.get_line_containing
bltext.get_line_containing
bltext.get_lines_from_repository, p_text_type=CDIPLS
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
bltext.get_line_containing
Creating CAPI for table KCS_TENDERS with id 692754610572409851363604771392473242
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Insert-stmt, Open transaction.
Write Text for element type APPLOG with id 753236628580304413262318236391196826 - Text type: ALCODE number of text lines = 6 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580304413262318236391196826 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Update-stmt, Open transaction.
Write Text for element type APPLOG with id 753236628580332747461215454262479002 - Text type: ALCODE number of text lines = 6 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580332747461215454262479002 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Delete-stmt, Open transaction.
Write Text for element type APPLOG with id 753236628580361081660112672133761178 - Text type: ALCODE number of text lines = 6 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580361081660112672133761178 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-After-Insert-stmt, Close transaction.
Write Text for element type APPLOG with id 753236628580389415859009890005043354 - Text type: ALCODE number of text lines = 6 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580389415859009890005043354 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-After-Update-stmt, Close transaction.
Write Text for element type APPLOG with id 753236628580417750057907107876325530 - Text type: ALCODE number of text lines = 6 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580417750057907107876325530 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-After-Delete-stmt, Close transaction.
Write Text for element type APPLOG with id 753236628580446084256804325747607706 - Text type: ALCODE number of text lines = 6 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580446084256804325747607706 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Delete-row, Save old data.
Write Text for element type APPLOG with id 753236628580474418455701543618889882 - Text type: ALCODE number of text lines = 404 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580474418455701543618889882 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Insert, Call CAPI.
Write Text for element type APPLOG with id 753236628580568865785358936523163802 - Text type: ALCODE number of text lines = 4 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580568865785358936523163802 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Update, Call CAPI.
Write Text for element type APPLOG with id 753236628580597199984256154394445978 - Text type: ALCODE number of text lines = 4 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580597199984256154394445978 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Delete, Call CAPI.
Write Text for element type APPLOG with id 753236628580625534183153372265728154 - Text type: ALCODE number of text lines = 17 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580625534183153372265728154 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-Insert, Call CAPI.
Write Text for element type APPLOG with id 753236628580653868382050590137010330 - Text type: ALCODE number of text lines = 7 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580653868382050590137010330 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-Update, Call CAPI.
Write Text for element type APPLOG with id 753236628580682202580947808008292506 - Text type: ALCODE number of text lines = 144 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580682202580947808008292506 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-Delete, Call CAPI.
Write Text for element type APPLOG with id 753236628580767205177639461622139034 - Text type: ALCODE number of text lines = 282 - REPLACE
Deleted old text
Write Text for element type APPLOG with id 753236628580767205177639461622139034 - Text type: ALCMNT number of text lines = 1 - REPLACE
Deleted old text
HSU_CAPF.create_or_find_capi_pack
hsu_capi.find_plm (kcs_tnr_capi, 692754610572409851363604771392473242, CAPI).
capi package found in the context folder
BLPLM.UPD
FREE_FORMAT_TEXT_FLAG......... = Y
IMPLEMENTATION_NAME........... = kcs_tnr_capi
PLSQL_MODULE_TYPE............. = PACKAGE
SCOPE......................... = PUBLIC
COMPLETION_STATUS............. = COMPLETED
NAME.......................... = kcs_tnr_capi
PURPOSE....................... = Custom API package for implementing Business Rules and supporting TAPI
Recreated Package KCS/ KCS_TNR_CAPI, preserving only the Revision History.
HSU_CAPF.add_tags_er_av
bltext.get_lines_from_repository, p_text_type=CDINOT
bltext.get_line_containing
bltext.get_line_containing
bltext.get_lines_from_repository, p_text_type=CDINOT
bltext.get_line_containing
bltext.get_line_containing
bltext.get_lines_from_repository, p_text_type=CDINOT
bltext.get_line_containing
bltext.get_line_containing
bltext.get_lines_from_repository, p_text_type=CDINOT
bltext.get_line_containing
bltext.get_line_containing
HSU_CAPF.create_specification
HSU_CAPF.create_c_tabalias
HSU_CAPF.create_c_tabalias_all
HSU_CAPF.create_aggregate_value
HSU_CAPF.create_aggregate_value
HSU_CAPF.create_aggregate_value
Activity aborted with ORACLE internal errors.
-6502 ORA-06502: PL/SQL: numeric or value error: character string buffer too small
What can I do about it???
Thanks in advance.
Menno Hoogsteen

Working on the same project as Menno, I had the time to look into the problem.
The problem is caused by the creation of the capi-function agregate_char_value in the packages hsu_capf. While creating this function the following code is executed:
add(' -- allowable values:');
add(' -- '||l_col_name_list);
This last statement causes the problem because this table is very big. L_col_name_list contains 2391 characters wich is 393 characters to long. So i changed this code into:
add(' -- allowable values:');
add(' -- '||substr(l_col_name_list,1,1990));
add(' -- '||substr(l_col_name_list,1990));
and everything works fine. Perhaps something for a patch?
Kind regards,
Ruben Spekle

ORA-06502: when creating a index

Hi,
i'm trying to create an index on a partitionned table, but i'm getting this error :
CREATE INDEX IDX_NDI_WTSCDRHISTO ON WTS_CDRHISTO(SUBSTR(NDI, GREATEST(LENGTH(NDI)-8,1))) Compress Local (
PARTITION WTS_CDRHISTO_2009070412 NOLOGGING COMPRESS TABLESPACE INDX_CDRHISTO_7 PCTFREE 0 INITRANS 2,
PARTITION WTS_CDRHISTO_2009070413 NOLOGGING COMPRESS TABLESPACE INDX_CDRHISTO_7 PCTFREE 0 INITRANS 2,
PARTITION WTS_CDRHISTO_2009070414 NOLOGGING COMPRESS TABLESPACE INDX_CDRHISTO_7 PCTFREE 0 INITRANS 2,
PARTITION WTS_CDRHISTO_2009070414 NOLOGGING COMPRESS TABLESPACE INDX_CDRHISTO_7 PCTFREE 0 INITRANS 2,
PARTITION WTS_CDRHISTO_2010070800 NOLOGGING COMPRESS TABLESPACE INDX_CDRHISTO_7 PCTFREE 0 INITRANS 2
PARALLEL 16;
the error code is : ORA-06502: PL/SQL: numeric or value error: character string buffer too small ???!!!!!!
Anyone can help me ?
Thks in advance

Post the section of code that is causing problem along with statements before and after the section as well.
For now, I can take a guess that you are trying to assign this entire statement as a string to a character variable. If so, then that variable length definition is too small to hold this entire string. In PL/SQL you can define VARCHAR2 to a maximum of 32767.

ORA-06502 encountered due to negative sign

Problem:
I encountered the error in my sql statement with the message:
declare
ERROR at line 1:
ORA-06502: PL/SQL: numeric or value error: character to number conversion error
ORA-06512: at line 144
I already found the problem:
v_str:= lpad(nvl(to_char((to_number(display_r.CO_AMOUNT)/100),'999,999,999.99'),' '),'15',' ');
DBMS_OUTPUT.PUT_LINE(v_str);Because the value of CO_AMOUNT has negative sign as: 00000000-381250
As such, I would like to seek help in resolving the problem I encountered. Is there a way to still display the output with the negative sign?
Thanks in advance.

The negative sign is not the problem, it's the fact that it's in the middle of the string. SQL expects the sign to be at the beginning (or end) of a number.
This is one of the side effects of using strings to hold numeric data. There are a number of reasons why you might have this behaviour, it really depends on what your app does and how it populates the CO_AMOUNT variable.
Anyway, you can solve this specific problem with a simple LTRIM:
SQL> SELECT to_number('00000000-381250') FROM dual
2 /
SELECT to_number('00000000-381250') FROM dual
ERROR at line 1:
ORA-01722: invalid number
SQL> SELECT to_number(ltrim('00000000-381250', '0')) FROM dual
2 /
TO_NUMBER(LTRIM('00000000-381250','0'))
-381250
SQL> Cheers, APC

Error ORA-06502 When using function REPLACE in PL/SQL

Hi,
I have a PL/SQL procedure which gives error 'Error ORA-06502 When using function REPLACE in PL/SQL' when the string value is quite long (I noticed this with a string 9K in length)
variable var_a is of type CLOB
and the assignment statement where it gives the error is
var_a := REPLACE(var_a, '^', ''',''');
Can anyone please help!
Thanks

Even then that shouldn't do so:
SQL> select overload, position, argument_name, data_type, in_out
2 from all_arguments
3 where package_name = 'STANDARD'
4 and object_name = 'LPAD'
5 order by 1,2
6 /
OVERLOAD   POSITION ARGUMENT_NAME                  DATA_TYPE                      IN_OUT
1                 0                                VARCHAR2                       OUT
1                 1 STR1                           VARCHAR2                       IN
1                 2 LEN                            BINARY_INTEGER                 IN
1                 3 PAD                            VARCHAR2                       IN
2                 0                                VARCHAR2                       OUT
2                 1 STR1                           VARCHAR2                       IN
2                 2 LEN                            BINARY_INTEGER                 IN
3                 0                                CLOB                           OUT
3                 1 STR1                           CLOB                           IN
3                 2 LEN                            NUMBER                         IN
3                 3 PAD                            CLOB                           IN
4                 0                                CLOB                           OUT
4                 1 STR1                           CLOB                           IN
4                 2 LEN                            NUMBER                         INI wonder what happened?

ORA-06502: PL/SQL: numeric or value error: in Inserting record in form 2.0

Hi All,
Can somebody help me out here urgently. I just added a New Column to a Table & when I try to use that Column in a Form & Insert using Automatic Row Processing(DML). I am getting this error, If I remove the newly created column, then it is fine.
Please help. I saw some posting on forum, but there was no solution.
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
Error Unable to process row of table <tablename>
OK
Thanks
Sandeep

Sandeep - Looks like you're hitting a 4096-character limit for the values portion of the insert statement because you have so many columns. This is a bug. A workaround would be to reduce the number of columns or create your own DML process for the insert operation.
Also just now I installed htmldb 2.0 in my laptop & trying to create the same table, but it is not creating ...no errors ..just a clue...I don't understand what you said.
Scott

ORA-06502: PL/SQL APEX 3.2 Upgrade problem

We have 2 APEX environments on our 2 servers. Both servers are running Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production.
One server was running APEX 3.0.0.00.24 (or thereabouts) and was upgraded to 3.2.0.00.27. The other server did not previously have APEX and so 3.2.0.00.27 has been installed as a new version.
We have a form that is filled in by the users. When they click submit the process adds an entry to a table, and then tries to send an email to our users as a HTML formatted email. The process creates a VARCHAR Variable and then using a cursor creates the text for the the email (including all the HTML tags). Running this process on the original server before the upgrade, but using the formatted email resulted in an ORA-06502: PL/SQL error. Creating an email that was a lot simpler (not html formated and therfore shorter) did actually work correctly.
I am lead to believe that there was a bug in Apex versions 3.0 that even if a PL/SQL VARCHAR2 variable was defined as 32000 characters it would actually only be able to use/store a lot less than that (1-2000 characters), and any attempt to use more would result in a ORA-06502: PL/SQL error (string buffer too small type message). I cannot seem to access Metalink at the moment so cannot confirm what the actual bug number is. I am also lead to believe that this error was actually addressed and fixed in one of the releases of APEX 3.1, and definitely in APEX 3.2.
So going with the advice that the issue had been resolved in APEX 3.2, I tried it out in the server with the brand new install. It worked perfectly. I then proceeded to try it in the server that had been upgraded to APEX 3.2.0.00.27. It fails with the same error as before even with the same data as used in the clean install.
Is there a file / setting / configuration somewhere that has to be changed so the APEX applications can use VARCHAR2 variable with more actual characters?
Here is a copy of the code being used:
for c1 in (select DISTINCT OUT_ID, OUT_REQUEST_DATE, OUT_ISSUE, OUT_ETA,
OUT_KEY_COMMENTS, STATUS_UPDATE_DATE, STATUS_NOTES,
OUT_EMAIL_TO, P_STATUS, P_SYS, SYS, STATUS,
ASSIGNED_TO, EMAIL_ADDR, USERNAME, STAT_USERNAME, OUTAGE_LENGTH_BUS_HRS,
AFFECTED_SYSTEM, SMSLIST, NVL(OUT_BUSINESS_IMPACT,'NOT KNOWN') OUT_BUSINESS_IMPACT,
OUT_CAUSE_COMMENT, FINAL_CAUSE, FIX,EM.EMAIL
from HTMLDB_DEV_OPP.VW_OUT_CURRENT_STATUS ST,
APEX_WORKSPACE_APEX_USERS EM
where OUT_ID = :P8_OUT_ID
AND INSTR(':'||ST.EMAIL_ADDR||':',':'||EM.USER_NAME||':') > 0
) loop
if c1.EMAIL is not null then
l_body_html := '<table align="center" border="0"
cellpadding="0" cellspacing="0" width="800">
<tbody>
<tr>
<td colspan="3"
bgcolor="#87b5ed">
Name of section within company here
</td>
</tr>
<tr>
<td colspan="3"
style="font-weight: bold; font-size: 28px; color: rgb(0, 0, 102); font-family: Arial,Helvetica,sans-serif;"
bgcolor="#87b5ed">DASS OUTAGE - ' || C1.SYS ||'</td>
</tr>
<tr>
<td colspan="3"
style="font-size: 12px; color: rgb(255, 255, 255); font-family: Arial,Helvetica,sans-serif;"
bgcolor="#87b5ed" valign="center">' ||
TO_CHAR(SYSDATE,'DY DD MON YYYY HH24:MI') || '</td>
</tr>
<tr>
<td bgcolor="#87b5ed" width="50"> 
</td>
<td rowspan="1"
bgcolor="#ffffff" valign="top" width="400">
<table
style="width: 808px; height: 63px;" border="0"
cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td
style="background-color: rgb(21, 103, 171); width: 800px; font-weight: bold; color: rgb(255, 255, 255); font-family: Arial,Helvetica,sans-serif;"
colspan="3"><img alt="" src="cbi_out2_files/spacer.gif" align="middle" height="30" width="20">' || C1.OUT_KEY_COMMENTS ||'</td>
</tr>
</tbody>
</table>
<table
style="height: 722px; width: 804px;" align="center"
border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="width: 802px;"
valign="top">
An
outage has been created in the CBI DASS System. 

What is the Outage? '||
C1.OUT_ISSUE||' 


What is the current status? '||
C1.STATUS||' 


Status update Comments? 
AT '||C1.STATUS_UPDATE_DATE || ' ' ||C1.STAT_USERNAME||' updated the system
with the following:'||C1.STATUS_NOTES ||' 


Streams Affected? 
Reported against '||C1.SYS||', also affecting downstream systems ' ||
C1.AFFECTED_SYSTEM ||' 


What is the Business Impact? ' ||
C1.OUT_BUSINESS_IMPACT||' 


What was the cause? ' ||
C1.FINAL_CAUSE||'. ('||C1.OUT_CAUSE_COMMENT||') 


Has a fix been identified? '||
C1.FIX||' 


When did the Outage commence? '||
C1.OUT_REQUEST_DATE||' (Length in Bus/Hrs '||C1.OUTAGE_LENGTH_BUS_HRS||') 

Estimated
Restore Time / Day? '||
C1.OUT_ETA||'


Click the link for further info View DASS '||:P8_OUT_ID||
'
</td>
</tr>
</tbody>
</table>
</td>
<td bgcolor="#87b5ed" width="50"></td>
</tr>
<tr>
<td bgcolor="#87b5ed"> 
</td>
<td bgcolor="#1567ab"> 
</td>
<td bgcolor="#87b5ed"> 
</td>
</tr>
<tr>
<td colspan="3"
bgcolor="#87b5ed"> </td>
</tr>
</tbody>
</table>
 ';
APEX_MAIL.SEND(
P_TO => c1.EMAIL,
P_FROM => '"CBI DASS Email"<OUR EMAIL ADDRESS>',
P_BODY => l_body_html,
P_BODY_HTML => l_body_html,
P_SUBJ => 'CBI System / Data Delay Notification '|| c1.OUT_ID || ' (System ' || c1.SYS ||') ');
end if;
end loop;
Thanks
Russell

bump ... does anyone have any ideas?
Thanks Russell

TextArea : ORA-06502: PL/SQL: numeric or value error (WWV-16016)

Was trying to use a TextArea in a form to submit some text to a procedure. Found that the text limit seems to be around 1700 bytes. If there is more text in the form I get the following error message:
Error: An unexpected error occurred: ORA-06502: PL/SQL: numeric or value error (WWV-16016)
The procedure that i recieveing the form is listed below:
procedure test
p_str in varchar2
as
begin
htp.p(p_str);
end;
Was expecting to be able to submit up to 32k of text using the TextArea this way.
Has anyone else run into this problem?
Is this a bug? Workaround???????
We really need to be able to submit at least 4k!

As a workaround,
1> you can create a table with varchar2(4000)
2> build a form on it and insert the data in the table
3> create a procedure to select the data from the table and publish it using htp.p(...)
4> call this procedure using go/call from the OnSuccess section
NOTE: you need to grant execute priv. on this procedure to <portal_schema>_PUBLIC db user

XML transform and ORA-06502:

When i update a limited set ( 1 row) of data with the statement in example 1 the statement works fine. When i delete the where clause i get ORA-06502: numeric or value error: character string buffer too small.
How can i make the statement work for a large amount of data.
example 1:
update udo.udo_cursus_beschrijvingen cbg
SET cbg.tekst = cbg.tekst.transform(XMLType(
'<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="url[(starts-with(child::text(),''www.''))]">
<url>http://<xsl:value-of select="."/></url>
</xsl:template>
<xsl:template match="@*|*|text()|processing-instruction()">
<xsl:copy>
<xsl:apply-templates select="@*|*|text()|processing-instruction()"/>
</xsl:copy>
</xsl:template>
</xsl:stylesheet>
')).getStringVal()
where cbg.id = 1672;

Sergio - I'm surprised that a hundred rows causes the Display As Text (based on LOV, save/does not save the state) to blow out. I'd expect no problems up to 5000 rows or so. I'd like to see an example of your case. The limitation on select lists is usually related to either the size of an individual report column (4000 max) or the size of a report row (32K max) in which a select-list lov is used. The total size of the HTML returned counts towards these limits. The problem for select-list items on a page is that large select lists mean lots of HTML on the page making the page heavy and burdening the network.
Scott

Scheduler agent can't submit state ORA-06502:

Similar Messages

Maybe you are looking for