SAPDBA: Error - global buffer too short

Hi,
When I run SAPDBA and do a 'Check of freespace of objects in all tablespaces', I encounter the error:
bdf: could not find the mount point for /oracle/<SID>/sapdata<n>/btabd_<xx>
SAPDBA: Error - global buffer too short
This error sometimes appear and at times it doesn't. What does this error mean and how can i resolve it?
Many thanks,
Kris

Hi Kristoffer,
Kindly gothrough the following link. It will lead you to solve your problem,
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/sapdba-error-1244276#
Regards,
Harish

Similar Messages

Error "602" System error: AK Datapart too short

Hi all,
Ok, I have looked just about everywhere for an answer to this but to no avail...I even tried under a few rocks we have laying around.
Anyway here it is:
While running a compression in BW we get Error "602" System error: AK Datapart too short.
This is happening while doing a select statement during the compression of the infocube. It does not happen all the time, just kind like when ever it feels like. The only note I could find in OSS was one about Live Cache and it does not seem to apply.
Here is the dump which I really hate doing this, but it gives all the info needed :
untime Error          DBIF_DSQL2_SQL_ERROR
Except.                CX_SY_NATIVE_SQL_ERROR
Date and Time          08/15/2007 12:23:09
ShrtText
An SQL error occurred when executing Native SQL.
What happened?
Error "-602" occurred in the current database connection "DEFAULT".
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
How to correct the error
Database error text........: "System error: AK Datapart too short"
Database error code .......: "-602"
Triggering SQL statement...: "INSERT INTO "/BIC/EZPSD_C03" ( "KEY_ZPSD_C03P",
"KEY_ZPSD_C03T", "KEY_ZPSD_C03U", "KEY_ZPSD_C031", "KEY_ZPSD_C032",
"KEY_ZPSD_C033", "KEY_ZPSD_C034", "/BIC/ZNET_ASP" ) SELECT ? ,
F."KEY_ZPSD_C03T", F."KEY_ZPSD_C03U", F."KEY_ZPSD_C031", F."KEY_ZPSD_C032","
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_DSQL2_SQL_ERROR" CX_SY_NATIVE_SQL_ERRORC
"GP31VIZWJDTT90894L1IA5YAC7G" or "GP31VIZWJDTT90894L1IA5YAC7G"
"TRANSFER_ALL"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"TRANSFER_ALL"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "sdcbw03"
Network address.......... "10.64.18.76"
Operating system......... "Linux"
Release.................. "2.6.9-55.ELsmp"
Hardware type............ "x86_64"
Character length......... 16 Bits
Pointer length........... 64 Bits
Work process number...... 21
Short dump setting....... "full"
Database server.......... "sdcbw03"
Database type............ "ADABAS D"
Database name............ "BWP"
Database owner........... "SAPBWP"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Nov 5 2006 19:46:34"
Created in............... "Linux GNU SLES-9 x86_64 cc3.3.3"
Database version......... "SAPDB 7.5.0.030 "
Patch level.............. "156"
Patch text............... " "
Supported environment....
Database................. "MaxDB 7.5.0"
SAP database version..... "640"
Operating system......... "Linux 2.6"
Memory usage.............
Roll..................... 16192
EM....................... 20949280
Heap..................... 0
Page..................... 24576
MM Used.................. 9235016
MM Free.................. 3331560
SAP Release.............. "640"
User and Transaction
Client.............. 011
User................ "ALEREMOTE"
Language key........ "E"
Transaction......... " "
Program............. "GP31VIZWJDTT90894L1IA5YAC7G"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "GP31VIZWJDTT90894L1IA5YAC7G" in
"TRANSFER_ALL".
The main program was "RSPROCESS ".
The termination occurred in line 573 of the source code of the (Include)
program "GP31VIZWJDTT90894L1IA5YAC7G"
of the source code of program "GP31VIZWJDTT90894L1IA5YAC7G" (when calling the
editor 5730).
The program "GP31VIZWJDTT90894L1IA5YAC7G" was started as a background job.
Job name........ "BI_PROCESS_COMPRESS"
Job initiator... "ALEREMOTE"
Job number...... 12185102
Processing was terminated because the exception "CX_SY_NATIVE_SQL_ERROR"
occurred in the
procedure "TRANSFER_ALL" "(FORM)" but was not handled locally, not declared in
the
RAISING clause of the procedure.
The procedure is in the program "GP31VIZWJDTT90894L1IA5YAC7G ". Its source code
starts in line 557
of the (Include) program "GP31VIZWJDTT90894L1IA5YAC7G ".
Source Code Extract
Line
SourceCde
543
ENDIF.
544
545
COMMIT WORK.   " commit and close cursors
546
547
l_str = i_max_requid.
548
PERFORM msg_append(saplrscondense)
549
USING    'S' '355' l_str space space space
550
CHANGING c_t_msg.
551
552
ENDFORM.                               " CONDENSE_FACTTABLE_NEW
553
554
555
     Form TRANSFER_ALL
556
557
FORM TRANSFER_ALL USING i_ref_update       TYPE rs_bool
558
i_pdimid           TYPE I
559
i_pdimid_ref_point TYPE rsd_sid
560
i_pdimid_normal    TYPE rsd_sid
561
i_recordtp         TYPE rsd_sid
562
CHANGING e_ref_ins_cnt TYPE I
563
e_ins_cnt     TYPE I
564
c_t_msg       TYPE rs_t_msg.
565
566
CALL FUNCTION 'RSDU_INFOCUBE_INDEXES_DROP'
567
EXPORTING
568
I_INFOCUBE = 'ZPSD_C03'
569
I_FACTTAB = '/BIC/EZPSD_C03'.
570
571
572
EXEC SQL.
>>>>>
INSERT INTO "/BIC/EZPSD_C03"
574
( "KEY_ZPSD_C03P"
575
, "KEY_ZPSD_C03T"
576
, "KEY_ZPSD_C03U"
577
, "KEY_ZPSD_C031"
578
, "KEY_ZPSD_C032"
579
, "KEY_ZPSD_C033"
580
, "KEY_ZPSD_C034"
581
, "/BIC/ZNET_ASP"
582
583
SELECT :i_pdimid_normal
584
, F."KEY_ZPSD_C03T"
585
, F."KEY_ZPSD_C03U"
586
, F."KEY_ZPSD_C031"
587
, F."KEY_ZPSD_C032"
588
, F."KEY_ZPSD_C033"
589
, F."KEY_ZPSD_C034"
590
, SUM( F."/BIC/ZNET_ASP" )
591
FROM "/BIC/FZPSD_C03" F
592
WHERE F."KEY_ZPSD_C03P" = :i_pdimid
Any thoughts would be helpful,
Thanks,
David

This error usually occurs when there is a database lock or no space in teh database. Got DB02 and Click on Space critical objects to see whether any entries are there. If yes contact your basis to increase the space.
Hope this helps
Thanks,
Satish

SP01 - display spool request, buffer too short

Dear all,
when trying to display spool request in transaction SP01, we are getting the error: internal error 0000000040/ 32 in spooler (buffer too short)
But the same request could be displayed via transaction SPO10.
R/3 4.6C.
Any idea ?
Thank you for the answer.
Pavol Simko
Edited by: Pavol Simko on Nov 3, 2009 3:18 AM

In SM37:
Goto>Display Requests>Settings...
Then in "Display area"-->"From page"
Set it to from page 1 - "no of pages" then try to display
the spool again.

Error message "paper too short to autoduplex" on Officejet Pro 8600

I have this problem with my new HP Officejet Pro 8600 Plus. I have standard letter size paper in Tray 1, and have all the printer setup set for letter size paper. No matter what program I print from, I recieve the error message "paper too short to auto-duplex". I click the close button, and the page prints. It is aggravating to take the extra step to close this error message every time I print. I shut the printer down for 30-60 seconds and this took the problem away. Is this normal? Will I have to do this often?

The fix is available in printer firmware (Software within the Printer). You can download it from hp.com and install from you pc to printer.
Here is the link. click download buttong to download the latest firmware.
http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=bi-102210-1&cc=us&dlc=en&lc=en...
Happy Printing...
Click on the "Thumbs up"button on the left to say "Thanks"
Please mark the post that solves your problem as "Accepted Solution"
(Although I am employed by HP, I am speaking for myself and not for HP)

UCS240 error loading /state.tgz fatal error 6 (buffer too small)

Hello
When start the EXSi 5.1, I have the follow error :
error loading /state.tgz fatal error 6 (buffer too small)
Any idea?
TIA
Cristian

Hi Christian,
Did you find the solution?
I am going to try to repair with the ISO. Is it the solution you used?

Oracle Report Error (string buffer too small) in Portal

Hi,
I have registered an oracle report (.rdf) with portal which works fine outside in Reports Builder, but when I try to run it in Portal it keeps throwing this error:
SQL-6502: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "PORTAL.WWV_RW_USR", line 444
ORA-06512: at "PORTAL.WWV_RW_USR", line 923
ORA-06512: at line 1
Anyone know what needs to be done to fix this?
Thanks

Sean:
Thank you very much for wading through my post.
>"if (NIerror = DAQmxCfgInputBuffer(h, numSamples*4))"
>I would leave this line out. DAQmx should create an input buffer automatically
>based on the number of channels and number of samples per channel.
Yeah- I put that in trying to fix the problem. The error message doesn't say *which* buffer is too small
>If you just call the DAQmxReadDigitalLines() function with "numSampsPerChan" set to -1,
>DAQmx will wait until all samples are acquired before performing the read.
I'm trying to avoid the wait. That's why I'm trying to figure out how many samples are ready.
I suppose I can try numSampsPerChan=-1, set a short timeout and check for the timeout error.
>If this does not help, please send me a small section of code that reproduces that behavior,
>and I will try running it on my machine.
I will try modifying one of the examples to do what I'm trying to do.
Again, Thank you!
John Weeks
WaveMetrics, Inc.
Phone (503) 620-3001
Fax (503) 620-6754
www.wavemetrics.com

Error:numeric or value error : buffer too small

hi
can any one please help me?
i am developing the application in HTMLDB. i have an error numeric or value error: char buffer too small.
i have an attributes plan_name,type......att_header1 in the database. The data's were inserted to the database, without the att_header item but if i have the item att_header int the HTMLDB then the insertion is not working. and also i was able to insert the data into the database for the field att_header1 through sql command . i think the problem is onle in my HTMLDB application.
please tell me the solution for this error.
thanx in advance
valli
Message was edited by:
valli

Valli,
I don't think you understood my post, above:
Can you please create an application that shows the problem on apex.oracle.com? Then we'll be able to see all your code together with the database tables, etc.
If you do not have a workspace you can request one.
Please request a workspace on apex.oracle.com. After your workspace request is approved, create an application there that shows this problem you are having. Create the necessary tables, packages, and other database objects in the database to support the example.
As the last step, post here the workspace name, the application ID, and detailed instructions explaining how to use your application to demonstrate the problem.
Scott

ORA-06502: PL/SQL: numeric or value error: character string buffer too smal

Hi Guys I am getting error ORA-06502: PL/SQL: numeric or value error: character string buffer too small as it said i thought it would be issue with length of feild but i tried to change is nothihg work i am posing code here if any one can please help me on this
PROCEDURE REPORT
p_rpt_from_dt in varchar2,
p_rpt_to_dt in varchar2,
p_apvr_id in tc_wkr.tc_row_id%type default NULL,
p_rpt_type in varchar2 default NULL,
p_backto_pg in varchar2 default NULL
IS
v_rpt_from_dt date := var_to_date(p_rpt_from_dt);
v_rpt_to_dt date := var_to_date(p_rpt_to_dt);
v_time_str varchar2(15);
cursor period_cur
cp_from_dt date,
cp_to_dt date
is
select beg_dt, end_dt
from jmcs_wk_tprd
where beg_dt <= cp_to_dt -- report end date
and end_dt >= cp_from_dt -- report start date
BEGIN
if sys_security('tcsys', 'tc_reports') != 'GRANTED' then
apps_main.access_denied;
return;
end if;
if lg_debug_fl then
v_time_str := to_char(lg_sysdate, 'hh:mi:ss a.m.');
else
v_time_str := tc_time(lg_sysdate);
end if;
/* get the time card time periods applicable to the report */
lga_tc_strt_dt := lga_null_date;
for recs in period_cur(v_rpt_from_dt, v_rpt_to_dt) loop
lga_tc_strt_dt(lga_tc_strt_dt.count+1) := recs.beg_dt;
lga_tc_end_dt(lga_tc_end_dt.count+1) := recs.end_dt;
end loop;
--if p_apvr_id is NULL then
if p_rpt_type != 'D' then
tc_reporting.reports_header
1,
'Time Card Status Report',
'for '||dd_mon_yyyy(v_rpt_from_dt)||' through '||dd_mon_yyyy(v_rpt_to_dt)||' '||
'Report Date: '||dd_mon_yyyy(lg_sysdate)||' Time: '||v_time_str,
NULL,
NULL,
NULL,
'javascript:window.close()', /* Backto */
'alert(''Reminder! Click on logo when you are ready to return to previous page'')'
end if;
if p_apvr_id is NULL then
sub_STATUS_BD_ALPHA (v_rpt_from_dt, v_rpt_to_dt, TRUE, p_rpt_type, p_apvr_id);
else
htp.p('');
sub_STATUS_BD_APVR (v_rpt_from_dt, v_rpt_to_dt, p_rpt_type, p_apvr_id);
end if;
htp.p('</body></html>');
EXCEPTION
WHEN OTHERS THEN
error_proc(SQLERRM, SQLCODE, owa_util.get_cgi_env('PATH_INFO'));
htp.p('Error Code is :'||SQLERRM);
END REPORT;
This package in trun call other procedure like below
PROCEDURE sub_STATUS_BD_ALPHA
p_rpt_from_dt in date,
p_rpt_to_dt in date,
p_display_hdr in boolean,
p_rpt_type in varchar2 default 'B',
p_apvr_id in tc_wkr.tc_row_id%type default NULL,
p_tcs_user_id in tc_wkr.tc_row_id%type default NULL
IS
v_time_str varchar2(15);
v_apvr_id tc_wkr.tc_row_id%type := 0;
v_a_user_id tc_wkr.tc_row_id%type; -- approver tcs_user_id
v_cnt integer := 0;
v_people_cnt integer := 0;
v_stat_cd varchar2(2000);
v_display_fl boolean := FALSE;
/*===========================================================================*/
cursor people_cur
cp_from_dt in date,
cp_to_dt in date
is
select
d_full_nm_lfm as name,
tc_row_id as tcs_user_id,
tcw_typ as pay_typ,
tcw_id as pay_id,
sys_strt_date as sys_strt_dt,
sys_end_dt
from tc_wkr
where sys_strt_date <= cp_to_dt
and nvl(sys_end_dt, cp_to_dt) >= cp_from_dt
order by upper(d_full_nm_lfm);
/* find the current or the most recent (if no current) approver */
cursor apvr_cur
cp_tcs_user_id in tc_wkr.tc_row_id%type
is
select
a.f_tc_apvr_id as fk_tcs_apvr_id,
w.d_full_nm_lfm as apvr_name,
w.tcw_typ as apvr_pay_typ,
w.tcw_id as apvr_pay_id,
a.strt_dt,
a.end_dt
from tc_wkr w, tc_ap_asmt a
where a.f_tc_wkr_id = cp_tcs_user_id
and w.tc_row_id = a.f_tc_apvr_id
order by a.strt_dt desc;
/* list of existing time cards UNION required time cards */
cursor tc_cur
cp_tcs_user_id in tc_wkr.tc_row_id%type, /* who's time cards */
cp_from_dt in date, /* report period from date */
cp_to_dt in date /* report period to date */
is
select
stat_cd,
strt_dt,
end_dt
from tc
where strt_dt <= cp_to_dt
and end_dt >= cp_from_dt
and fk_tc_wkrtcw_id = cp_tcs_user_id
UNION
select
'Required' as stat_cd,
beg_dt as strt_dt,
end_dt
from jmcs_wk_tprd
where beg_dt <= cp_to_dt
and end_dt >= cp_from_dt
and beg_dt not in (
select strt_dt
from tc
where strt_dt <= cp_to_dt
and end_dt >= cp_from_dt
and fk_tc_wkrtcw_id = cp_tcs_user_id
order by strt_dt;
BEGIN
if lg_debug_fl then
v_time_str := to_char(lg_sysdate, 'hh:mi:ss a.m.');
else
v_time_str := tc_time(lg_sysdate);
end if;
if p_apvr_id > 0 then
lga_report_out := lga_report_out_null;
v_apvr_id := p_apvr_id;
lga_apvr := lga_apvr_null;
select
d_full_nm_lfm,
tc_row_id,
tcw_id,
tcw_typ
into
lga_apvr(1).apvr_name,
lga_apvr(1).apvr_tcs_id,
lga_apvr(1).apvr_pay_id,
lga_apvr(1).apvr_pay_typ
from tc_wkr
where tc_row_id = v_apvr_id;
if lga_apvr(1).apvr_pay_typ != 'S' then
select decode(bend_empl_fl, 'Y', 'E', 'W')
into lga_apvr(1).apvr_pay_typ
from empl
where empl_id = lga_apvr(1).apvr_pay_id;
end if;
end if;
if p_display_hdr then
if lga_tc_strt_dt.count > 6 then /* more than 6 time periods (1 month) */
lga_width(1) := to_char(.15 * lg_page_width_standard);
lga_width(2) := to_char(.08 * lg_page_width_standard);
for i in 1..lga_tc_strt_dt.count loop
lga_width(lga_width.count+1) := to_char(.09 * lg_page_width_standard);
end loop;
lg_page_width_standard := to_number(lga_width(1)) + to_number(lga_width(2));
if nvl(p_apvr_id, 0) = 0 then
lg_page_width_standard := lg_page_width_standard * 2;
end if;
htp.p('');
for i in 3..lga_width.count loop
lg_page_width_standard := lg_page_width_standard + to_number(lga_width(i));
htp.p('');
end loop;
lg_page_width := to_char(lg_page_width_standard);
else
lga_width(1) := '15%';
lga_width(2) := '8%';
lga_width(3) := '9%';
lga_width(4) := '9%';
lga_width(5) := '9%';
lga_width(6) := '9%';
lga_width(7) := '9%';
lga_width(8) := '9%';
end if;
sub_DETAIL_PAGE_HD(p_apvr_id);
end if;
/* cursor loop */
for p in people_cur(p_rpt_from_dt, p_rpt_to_dt) loop
/* is/was this person assigned to the selected approver for the report period */
v_display_fl := FALSE;
if nvl(p_tcs_user_id, 0) > 0 then
if p_tcs_user_id = p.tcs_user_id then
htp.p(' Selected User');
v_display_fl := TRUE;
end if;
elsif nvl(p_apvr_id, 0) = 0 then
if nvl(p_apvr_id, 0) = 0 then
v_display_fl := TRUE;
elsif p_apvr_id > 0 or p_apvr_id = -1 then
v_display_fl := fct_ASSIGNED_APVR(p.tcs_user_id, p_apvr_id, p_rpt_from_dt, p_rpt_to_dt);
end if;
if v_display_fl then
v_people_cnt := v_people_cnt + 1;
lg_tcs_owner_info.USER_ID := p.tcs_user_id;
lg_tcs_owner_info.PAY_ID := p.pay_id;
lg_tcs_owner_info.PAY_TYPE := p.pay_typ;
lg_tcs_owner_info.SYS_STRT_DT := p.sys_strt_dt;
lg_tcs_owner_info.TERM_DT := p.sys_end_dt;
if p.pay_typ = 'S' then
begin
select wrk_hire_dt
into lg_tcs_owner_info.hire_dt
from subcntr
where sub_id = p.pay_id;
exception
when no_data_found then
tc_debug.html_message('subcntr.pay_id('||p.pay_id||')');
end;
else
select
wrk_hire_dt,
decode(bend_empl_fl, 'Y', 'E', 'W')
into
lg_tcs_owner_info.hire_dt,
lg_tcs_owner_info.pay_type
from empl
where empl_id = lg_tcs_owner_info.PAY_ID;
end if;
if lga_report_out.count = 0 then
lga_report_out(lga_report_out.count+1) := '<table border="1" cellpadding="3" width="'||lg_page_width||'">';
end if;
if mod(v_people_cnt,2) = 1 then
lga_report_out(lga_report_out.count+1) := ('<tr bgcolor="'||lg_odd_bgcolor||'">');
else
lga_report_out(lga_report_out.count+1) := ('<tr bgcolor="'||lg_even_bgcolor||'">');
end if;
lga_report_out(lga_report_out.count+1) := ('<td valign="top">'||p.name||'</td >');
lga_report_out(lga_report_out.count+1) := ('<td valign="top">'||p.pay_typ||'-'||lpad(p.pay_id,4,'0')||'</td >');
if nvl(p_apvr_id, 0) > 0 then /* Single Approver */
/* need approver ID for time card "status" */
lga_apvr := lga_apvr_null; /* clear the approver id array */
lga_apvr(1).apvr_tcs_id := p_apvr_id;
elsif nvl(p_apvr_id, 0) = 0 then /* ALL Approvers */
lga_apvr := lga_apvr_null; /* clear the approver id array */
v_cnt := 0;
for ap in apvr_cur (p.tcs_user_id) loop
if v_cnt = 0 then
/* most recent approver may not be the applicable approver */
v_cnt := 1;
lga_apvr(v_cnt).apvr_name := ap.apvr_name; -- identify multiple approvers for the "status"
lga_apvr(v_cnt).apvr_tcs_id := ap.fk_tcs_apvr_id; -- identify multiple approvers for the "status"
lga_apvr(v_cnt).apvr_pay_id := ap.apvr_pay_id; -- identify multiple approvers for the "status"
v_apvr_id := ap.fk_tcs_apvr_id;
if ap.apvr_pay_typ = 'S' then
lga_apvr(v_cnt).apvr_pay_typ := ap.apvr_pay_typ; -- identify multiple approvers for the "status"
else
select decode(bend_empl_fl, 'Y', 'E', 'W')
into lga_apvr(1).apvr_pay_typ
from empl
where empl_id = lga_apvr(1).apvr_pay_id;
end if;
end if;
if ap.strt_dt <= p_rpt_to_dt and nvl(ap.end_dt, p_rpt_to_dt) >= p_rpt_from_dt then
/* approver record */
lg_tcs_owner_info.APVR_ID := ap.fk_tcs_apvr_id;
lg_tcs_owner_info.APVR_STRT_DT := ap.strt_dt;
lg_tcs_owner_info.APVR_END_DT := ap.end_dt;
don't enter same approver name multiple times
when same approver has been assigned more than once
Example: approver1, approver_2, approver_1 (change back to approver 1)
for i in 1..lga_apvr.count loop
v_apvr_id := ap.fk_tcs_apvr_id;
if lga_apvr(i).apvr_tcs_id = ap.fk_tcs_apvr_id then
/* don't add again */
v_apvr_id := NULL;
exit;
end if;
end loop;
if v_apvr_id is not NULL then
v_cnt := v_cnt + 1;
lga_apvr(v_cnt).apvr_name := ap.apvr_name; -- identify multiple approvers for the "status"
lga_apvr(v_cnt).apvr_tcs_id := ap.fk_tcs_apvr_id; -- identify multiple approvers for the "status"
lga_apvr(v_cnt).apvr_pay_id := ap.apvr_pay_id; -- identify multiple approvers for the "status"
lga_apvr(v_cnt).apvr_pay_typ := ap.apvr_pay_typ; -- identify multiple approvers for the "status"
end if;
end if;
end loop;
/* list approver pay IDs */
lga_report_out(lga_report_out.count+1) := ('<td valign="top">');
if lga_apvr.count = 0 then
lga_report_out(lga_report_out.count+1) := 'Approver Unassigned';
else
for i in 1..lga_apvr.count loop
if i > 1 then
lga_report_out(lga_report_out.count+1) := ' ';
end if;
lga_report_out(lga_report_out.count+1) := (lga_apvr(i).apvr_name);
end loop;
end if;
lga_report_out(lga_report_out.count+1) := ('<td valign="top">');
if lga_apvr.count = 0 then
lga_report_out(lga_report_out.count+1) := 'N/A';
else
for i in 1..lga_apvr.count loop
if i > 1 then
lga_report_out(lga_report_out.count+1) := ' ';
end if;
lga_report_out(lga_report_out.count+1) := (lga_apvr(i).apvr_pay_typ)||'-'||lpad(lga_apvr(i).apvr_pay_id,4,'0');
end loop;
end if;
lga_report_out(lga_report_out.count+1) := ('</td >');
end if;
for t in tc_cur(p.tcs_user_id, p_rpt_from_dt, p_rpt_to_dt) loop
htp.p('<! '||t.strt_dt||', '||t.end_dt||', '||t.stat_cd||' -->');
--lga_report_out(lga_report_out.count+1) := ('<td valign="top">');
--lga_report_out(lga_report_out.count+1) := (t.stat_cd);
--lga_report_out(lga_report_out.count+1) := ('</td >');
/* has the selected approver has completed processing */
if p_apvr_id > 0
and v_apvr_id = p_apvr_id
and v_a_user_id != p_apvr_id
then
exit;
end if;
for ap in apvr_cur (p.tcs_user_id) loop
if apvr_cur%rowcount = 1 then
/* most recent approver assigned */
lg_tcs_owner_info.apvr_id := ap.fk_tcs_apvr_id;
end if;
if ap.strt_dt <= t.end_dt and nvl(ap.end_dt, t.end_dt) >= t.strt_dt then
/* approver assigned during time card period */
lg_tcs_owner_info.apvr_id := ap.fk_tcs_apvr_id;
exit;
end if;
end loop;
lg_tc_status.strt_dt := t.strt_dt;
lg_tc_status.end_dt := t.end_dt;
lg_tc_status.stat_cd := t.stat_cd;
v_stat_cd := fct_TC_STATUS(nvl(p_apvr_id, 0));
lga_report_out(lga_report_out.count+1) := ('<td align="center" valign="top" bgcolor="'||lg_tc_status.bg_color||'">');
lga_report_out(lga_report_out.count+1) := ('');
lga_report_out(lga_report_out.count+1) := v_stat_cd;
lga_report_out(lga_report_out.count+1) := ('</td >');
end loop;
lga_report_out(lga_report_out.count+1) := '</tr>';
end if; /* v_display_fl */
end loop;
if p_rpt_type in ('B', 'S') then
lg_page_cnt := lg_page_cnt + 1;
sub_DISPLAY_STATUS_SUMMARY;
end if;
if lga_report_out.count > 0 then
lga_report_out(lga_report_out.count+1) := '</table>';
end if;
if lga_report_out.count > 0 then
if p_rpt_type = 'B' or p_apvr_id > 0 then
if p_display_hdr then
if lg_page_cnt > 0 then
if p_apvr_id > 0 then /* selected individual approver */
htp.p('</table>');
end if;
htp.p(' ');
 htp.p('');
 htp.p('');
end if;
lg_page_cnt := lg_page_cnt + 1;
tc_reporting.reports_header
1,
'Time Card Status Report',
'for '||dd_mon_yyyy(p_rpt_from_dt)||' through '||dd_mon_yyyy(p_rpt_to_dt)||' '||
'Report Date: '||dd_mon_yyyy(lg_sysdate)||' Time: '||v_time_str,
NULL,
NULL,
NULL,
NULL, -- p_backto_pg, /* Backto */
'focus()',
lg_page_cnt
end if;
end if;
if p_rpt_type in ('B', 'D') then
for i in 1..lga_report_out.count loop
htp.p(lga_report_out(i));
end loop;
end if;
end if;
END sub_STATUS_BD_ALPHA;
Some veriable
type report_tc_rec is record
tc_owner_name tc_wkr.d_full_nm_lfm%type,
o_user_id tc_wkr.tc_row_id%type,
o_pay_id varchar2(10),
o_sys_strt_dt date,
o_sys_end_dt date,
tc_apvr_name tc_wkr.d_full_nm_lfm%type,
a_pay_id varchar2(10),
a_user_id tc_wkr.tc_row_id%type,
tc_strt_dt date,
tc_end_dt date,
tc_stat_cd varchar2(50),
ap_strt_dt date,
ap_end_dt date
/* time card owner information */
TYPE tcs_owner_info_rec IS RECORD
USER_ID tc_wkr.tc_row_id%type,
PAY_ID tc_wkr.tcw_id%type,
PAY_TYPE tc_wkr.tcw_typ%type,
HIRE_DT date,
SYS_STRT_DT date,
TERM_DT date,
APVR_ID tc_wkr.tc_row_id%type,
APVR_STRT_DT date,
APVR_END_DT date
/* status code determines report cell font and background colors */
TYPE tc_status_rec IS RECORD
STRT_DT date,
END_DT date,
STAT_CD tc.stat_cd%type,
FONT_COLOR varchar2(16),
BG_COLOR varchar2(16)
/* count of all time card status for report summary */
TYPE tc_status_summary_rec IS RECORD
APPROVED_CNT integer := 0,
REJECTED_CNT integer := 0,
SUBMITTED_CNT integer := 0,
POSTED_CNT integer := 0,
VERIFIED_CNT integer := 0,
OPEN_CNT integer := 0,
NEW_CNT integer := 0,
REQUIRED_CNT integer := 0,
TOTAL_CNT integer := 0
/* determine multiple approvers for individual for selected report period */
TYPE apvr_rec IS RECORD
apvr_name tc_wkr.d_full_nm_lfm%type,
apvr_tcs_id tc_wkr.tc_row_id%type,
apvr_pay_id tc_wkr.tcw_id%type,
apvr_pay_typ tc_wkr.tcw_typ%type
TYPE apvr_id_array_table IS TABLE OF apvr_rec
index by binary_integer;
type output_array is table of varchar2(1000)
index by binary_integer;
type date_array is table of date
index by binary_integer;
type status_array is table of varchar2(1000)
index by binary_integer;
type apvr_array is table of number(8)
index by binary_integer;
lga_report_out output_array; /* array of HTML code to be output to browser */
lga_report_out_null output_array; /* null array of HTML code */
lga_tc_status status_array;
lga_null_status status_array;
lga_tc_strt_dt date_array;
lga_tc_end_dt date_array;
lga_tc_disp date_array; /* start dates of displayed TC for selected user */
lga_null_date date_array; /* null array used to clear other date arrays */
/* LOCAL GLOBAL VARIABLES */
lg_tcs_owner_info tcs_owner_info_rec; /* time card owner information */
lg_tc_status tc_status_rec; /* time card status information */
lg_tc_status_summary tc_status_summary_rec; /* time card count by status */
lg_tc_rec report_tc_rec; /* time card */
lga_apvr apvr_id_array_table; /* array of approver Names and Payroll IDs */
lga_apvr_null apvr_id_array_table; /* clear the lga_apvr array for each user */
lg_sysdate date := sysdate;
lg_debug_fl boolean := FALSE;
lg_debug_owner_id tc_wkr.tc_row_id%type := 9905;
lg_debug_apvr_id tc_wkr.tc_row_id%type := 1000;
The chnages i have done its in bold
Please Advice
Thanks
Edited by: Purvik on Aug 25, 2009 11:59 AM

There is not a chance in the world, especially not knowing column definitions that I, and I suspect most anyone else, is going to wade through this much unformated code looking for an error you couldn't bother to copy in full.
Either tell us, specifically, the line on which the error is occurring or, better yet, start whacking stuff out of your code until you find the offending definition. That is certainly what I would do. Commenting out sections is a marvelous way to quickly find an issue.
Before you post again please read the FAQ. It will explain to you how to properly post and use the tags.

Bug: Report Column based on LOV character string buffer too small error

When using a column type of "Display as Text (based on LOV, does not save state)" with a result set that is rather large causes a character or string buffer too small oracle error.
See the below page for an example.
The example page below has a single report off a table called "HUGE_TABLE" which has two columns: display and code
Code contains a number between 0 and 100000.
Display contains the number in code appended to a block of text.
When I display the report with no Display As Text (based on LOV does not save state) it displays fine.
If I make the "Code" column display as text based on LOV and make the LOV
"SELECT display, code FROM huge_table"
I get the error you see on the page.
http://apex.oracle.com/pls/otn/f?p=32149:1
Thanks.

Thanks for your help Scott.
So from what I've gathered from my own tests and the discussions you linked me to the LOVs based on SQL queries are being converted into "static LOV" strings before being used.
As such they are limited to the PL/SQL VARCHAR2 max size of 32767
Which means given the static reduction of the string 'STATIC:' that we have 32760 characters left.
Which is where your SUM( LENGTH( display ) + LENGTH( return ) + 2 ) comes in.
In short, if:
sum( length( display ) + length( return ) + 2 ) + 7 > 32767
would evaluate to true then you have a problem. :)
I'll use this to track down my problems and switch them over to inline queries.
Thanks.
Cheers,
Joe

BI Publisher Report Query Error: "character string buffer too small"

Using apex.oracle.com, I am trying to make a Report Query (Shared Components > Report Queries) based on many columns (around 60).
When I enter my SQL in the "Source Query" Text Area and then click Test Report I get the following error:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small In order to try to make the simplest test case possible for this, I then tried entering SQL selecting just from DUAL.
The following SQL fails with the error mentioned above.
SELECT
'wibble' as a
,'wibble' as b
,'wibble' as c
,'wibble' as d
,'wibble' as e
,'wibble' as f
,'wibble' as g
,'wibble' as h
,'wibble' as i
,'wibble' as j
,'wibble' as k
,'wibble' as l
,'wibble' as m
,'wibble' as n
,'wibble' as o
,'wibble' as p
,'wibble' as q
,'wibble' as r
,'wibble' as s
,'wibble' as t
,'wibble' as u
,'wibble' as v
,'wibble' as w
,'wibble' as x
,'wibble' as y
,'wibble' as z
,'wibble' as ab
,'wibble' as ac
,'wibble' as ad
,'wibble' as ae
,'wibble' as af
,'wibble' as ag
,'wibble' as ah
,'wibble' as ai
,'wibble' as aj
,'wibble' as ak
,'wibble' as al
,'wibble' as am
,'wibble' as an
,'wibble' as ao
,'wibble' as ap
,'wibble' as aq
,'wibble' as ar
,'wibble' as at
,'wibble' as au
,'wibble' as av
FROM dualRemoving the last column from this SQL query (bringing the total number of columns down to 45) as follows and then clicking "Test Report" works successfully.
SELECT
'wibble' as a
,'wibble' as b
,'wibble' as c
,'wibble' as d
,'wibble' as e
,'wibble' as f
,'wibble' as g
,'wibble' as h
,'wibble' as i
,'wibble' as j
,'wibble' as k
,'wibble' as l
,'wibble' as m
,'wibble' as n
,'wibble' as o
,'wibble' as p
,'wibble' as q
,'wibble' as r
,'wibble' as s
,'wibble' as t
,'wibble' as u
,'wibble' as v
,'wibble' as w
,'wibble' as x
,'wibble' as y
,'wibble' as z
,'wibble' as ab
,'wibble' as ac
,'wibble' as ad
,'wibble' as ae
,'wibble' as af
,'wibble' as ag
,'wibble' as ah
,'wibble' as ai
,'wibble' as aj
,'wibble' as ak
,'wibble' as al
,'wibble' as am
,'wibble' as an
,'wibble' as ao
,'wibble' as ap
,'wibble' as aq
,'wibble' as ar
,'wibble' as at
,'wibble' as au
FROM dualSo the question is: Is there a hard-coded limit of 45 columns for a Source Query? Or is there something else causing this error message?
(For information in the above example I have "Use Generic Report Layout" selected and the output format set to "PDF")
Thanks very much in advance for any comments or suggestions,
Andy

Thanks for the suggestion Simon.
I just created a view based on the 46-column SELECT statement from dual above and then set "SELECT * FROM myview" as the Source Query.
Unfortunately I get exactly the same error.
Thanks,
Andy

Report error:ORA-06502:character string buffer too small. urgent!!

Hi guys,
My APEX version is 3.0.1.00.08, my application run on my test environment, but on PROD environment, it raised the error:
report error:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
In this page, on the left is a tree, the right side is a tabular form, when I click one tree node, it will pass the current node id to the form and the form will display the children data. When I click some tree node, it will raise the ORA-06502 error, but when click some other nodes, it is correct. I don't know why. And on my test environment, it has no this error, the test environment has same version with prod environment, only has less data in database. Could you help me???
I searched in forum, someone says it's LOV problem, if it's LOV problem, all the nodes should have error, why click some nodes are ok?
Thanks !
Jessica

I don't think it is related only to the number of rows but also to the content of the rows. So, counting only the number of rows doesn't say anything about if it is going to work or not. My question: can't you filter those entries? Making a choice between 250 entries in a tabular form isn't a simple task. Using popup-key LOV instead would also be a solution. However, if you use popup-key LOV be aware of the fact that you need two index numbers for those.
Denes Kubicek
http://deneskubicek.blogspot.com/
http://www.opal-consulting.de/training
http://apex.oracle.com/pls/otn/f?p=31517:1
-------------------------------------------------------------------

Numeric or value error: character string buffer too small

Hi,
I have no problem with this code :
select htmldb_item.text(3,nom,20) nom,
htmldb_item.select_list_from_query(9,v_urba_rue.ref_fantoir,'select distinct(nom_voie),v_urba_rue.ref_fantoir from adresse,v_urba_rue where adresse.ref_fantoir(+)=v_urba_rue.ref_fantoir and ref_commune=20 and v_urba_rue.ref_fantoir between 1280 and 1370') rue
from personne,participe,adresse,v_urba_rue
where ...
but when i modify :
...and v_urba_rue.ref_fantoir between 1280 and 1400') rue...
i have this error :
ORA-06502 PL/SQL: numeric or value error: character string buffer too small
any solution?
thank you very much

Is this the same posting as
ORA-06502 numeric or value error string

Error PL/SQL: numeric or value error: character string buffer too small

HI oracle gurus,
I am new to PL/SQL,
my oracle version is oracle 11g.
i have create a procedure to insert data from flat file to a table using UTL_FILE.
Table is
CREATE TABLE EXT_PERSON_INFO
ID_PERSON              NUMBER(38),
ID_BATCH             NUMBER(38),
ID_PERSON_NBR        VARCHAR2(3 BYTE),
ID_AREA              VARCHAR2(5 BYTE),
NM_FINAL              VARCHAR2(20 BYTE),
NM_START             VARCHAR2(20 BYTE),
DT_DOB             DATE,
ID_SERIAL               VARCHAR2(9 BYTE),
DT_RESPONSE          DATE,
TRANS_TYPE VARCHAR2(2 BYTE),
REG_RESPONSE VARCHAR2(1 BYTE),
TM_RX          TIMESTAMP(6)
my procedure is
CREATE OR REPLACE PROCEDURE PROC_PERSON
IS
f_line VARCHAR2(2000);
f utl_file.file_type;
f_dir VARCHAR2(250);
fname VARCHAR2(50);
F_ID_PERSON EXT_PERSON_INFO.ID_PERSON%type :=1;
F_ID_BATCH EXT_PERSON_INFO.ID_BATCH%type :=1;
F_ID_PERSON_NBR EXT_PERSON_INFO.ID_PERSON_NBR%type;
F_ID_AREA EXT_PERSON_INFO.ID_AREA%type;
F_NM_FINAL EXT_PERSON_INFO.NM_FINAL%type;
F_NM_START EXT_PERSON_INFO.NM_START%type;
F_DT_DOB EXT_PERSON_INFO.DT_DOB%type;
F_ID_SERIAL EXT_PERSON_INFO.ID_SERIAL%type;
F_DT_RESPONSE EXT_PERSON_INFO.DT_RESPONSE%type;
F_TRANS_TYPE EXT_PERSON_INFO.TRANS_TYPE%type;
F_REG_RESPONSE EXT_PERSON_INFO.REG_RESPONSE%type;
BEGIN
fname := 'D:\raj\raj.txt';
f:= utl_file.fopen('RAJ',fname,'r');
loop
begin
utl_file.get_line(f,f_line);
exception
when no_data_found then
exit;
end;
F_ID_PERSON := 1;
F_ID_BATCH := 1;
F_ID_PERSON_NBR :=substr(f_line,1,3);
F_NM_FINAL := substr(f_line,4,22);
F_NM_START := substr(f_line,23,34);
F_DT_DOB := substr(f_line,35,44);
F_ID_SERIAL := substr(f_line,45,48);
F_DT_RESPONSE := substr(f_line,49,58);
F_TRANS_TYPE := substr(f_line,59,60);
F_REG_RESPONSE := substr(f_line,61,61);
F_ID_AREA := substr(f_line,62,64);
insert into EXT_PERSON_INFO VALUES (F_ID_PERSON,F_ID_BATCH,F_ID_PERSON_NBR,F_ID_AREA,F_NM_FINAL,F_NM_START,F_DT_DOB,F_ID_SERIAL,F_DT_RESPONSE,F_TRANS_TYPE,F_REG_RESPONSE);
end loop;
utl_file.fclose(f);
commit;
end;
am getting error
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
please help me in this regard. unable to trace the issue.
Thanks in advance
Regards,
raj

The error message should have included a line number for you to reference back to your code to know what line the error was occurring on.
That said, look at the documentation for SUBSTR as you are using the third parm incorrectly. It is length, not end position. That's your issue.

PL/SQL numeric error:character buffer string too small

I am always getting this error message when I first try to run my package.
But this always happen on the first time. When I then try to run it for second time, no problem.
So it can't be due to syntax or logic.
Could it be due to package state?

How are they being initialised? Is it just a straight assignment?
Can you copy + paste the exact error you are getting...
SQL> CREATE OR REPLACE PACKAGE pkg_Test
2 IS
3 pc_TooBig CONSTANT VARCHAR2(1) := 'AB';
4
5     PROCEDURE p_test;
6 END;
7 /
Package created.
SQL> CREATE OR REPLACE PACKAGE BODY pkg_Test
2 IS
3
4     PROCEDURE p_test
5     IS
6
7     BEGIN
8
9             dbms_output.put_line('Test');
10
11     END;
12 END;
13 /
Package body created.
SQL> exec pkg_test.p_test;
BEGIN pkg_test.p_test; END;
ERROR at line 1:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "BULK1.PKG_TEST", line 3
ORA-06512: at line 1
SQL> exec pkg_test.p_test;
Test
PL/SQL procedure successfully completed.As it probably tells you exactly where the problem is arrising.
David

ORA-6502: PL/SQL: numeric or value error: character string buffer too small WWV-11230

Hi,
I'm trying to create an UI Template. I've generated the html using Frontpage and am successfully able to see in a browser.
I've copied the html to the UI form, but when I try to preview or execute the UI template, I get the following error:
Error: ORA-06502: PL/SQL: numeric or value error: character string buffer too small (WWV-11230)
null

I AM FACING SIMILAR PROBLEM, THE EXACT ERROR IS:
Error: Excepcisn de wwv_generate_component.build_procedure (WWV-01821)
No se ha podido generar la pantalla de interfaz de usuario: ORA-06502: PL/SQL: numeric or value error: character string buffer too small (WWV-16409)
(SORRY , PART OF THE ERROR IS IN SPANISH!)
I CREATED A FORM , WORKED WITH IT A LOT WITHOUT PROBLEMS. NOW I NEED TO DO SOME CHANGES ON CERTAIN FIELDS AND WHEN I TRY TO SAVE IT I GET THE ABOVE ERROR.
THEN I GO BACK TO AN OLDER VERSION, COPY AND TRY TO DO CHANGES AND AGAIN THE ERROR COMES UP.
THE CHANGES I AM TRYING TO DO ARE TO SOME OF THE EXISTING FIELDS IN THE FORM WHICH NEED TO BE PUT AS "INSERTABLE".
THE SCREEN LAYOUT IS DISPLAYED WITHOUT PROBLEM.
(THE FORM IS BASED ON A TABLE WITH APROX 80 FIELDS).
I NEED SOME URGENT HELP. PLS LET ME KNOW ANY OTHER INFO YOU MAY NEED TO HELP ME SOLVE THIS PROBLEM.
FYI I AM WORKING ON PORTAL VERSION 3.0.9 / ON Windows 2000 (DATABASE 8.1.7.0 AND iAS ARE ON DIFFERENT MACHINES).
TKS IN ADVANCE

SAPDBA: Error - global buffer too short

Similar Messages

Maybe you are looking for