NAT - table is too small

Similar Questions

• Select this OPTION to generate XML data from the table using XMLELEMENT, XMLAGG gives error ORA-19011 string buffer too small

  My select statement fails with the error:

  
  

  The ORA-19011 string buffer too small

  
  

  The select statement looks like:

  
  

  SELECT TO_CLOB)

  XMLELEMENT ("accounts",

  XMLELEMENT ("count",

  XMLATTRIBUTES)

  rownum AS "recordId."

  To_date('20130520','YYYYMMDD') AS "datestarted."

  123456 AS "previousBatchId."

  56789 AS 'previousRecordId '.

  ),

  ....

  .... .

  .....

  XMLFOREST)

  SIG_ROLE AS "SignatoryRole."

  To_char(TRANSFER_DATE,'YYYY-mm-DD') AS "TransferDate."

  NVL(Reason,0) AS 'reason '.

  ) AS the 'transfer '.

  )

  ()) AS CRDTRPT

  OF ANY_TABLE;

  • It looks like I can choose only 4000 characters using the SELECT statement (please, correct me if I'm wrong)

  I'd use the XMLGEN package. But the environment team says no mounted drives in the future with the arrival of the EXADATA.

  NO HARD DRIVE MOUNTED, NO ACCESS TO THE DATABASE DIRECTORIES

  No UTL_FILE

  I need to use the REEL spool the resulting XML data of the SELECT query.

  SQL is a standard in my org, but I can do with a PL/SQL solution also to load data into a table (cannot use a COIL with PL/SQL)

  What I do is:

  1. a column of type CLOB to a xml_report of the loading of the above SELECT query table
  2. Then using SELECT * FROM xml_report to SPOOL the data to a file report.xml

  No need of XMLTYPE data behind. Xml data stream is fine for me.

  In addition, I need to validate the XML file, also using XSD.

  Problem is that the resulting lines of the select query are supposed to be from 15000 to 20000 bytes long.

  Oracle database version: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64 bit Production

  A Suggestion or a solution to this problem would be appreciated.

  (Sorry for the use of "BOLD", just to make it more readable and highlight the imp points)

  Bravo!

  Rahul

  It looks like I can choose only 4000 characters using the SELECT statement (please, correct me if I'm wrong)

  You use the right method.

  There is an implicit conversion from XMLType to the data type VARCHAR2 as expected by the function TO_CLOB, where the limitation, and the error.

  To serialize XMLType to CLOB, use the XMLSerialize function:

  SELECT XMLSerialize (DOCUMENT

  XMLELEMENT ("accounts",

  ...

  )

  )

  OF ANY_TABLE;

  For the rest of the requirement, I wish you good luck trying to spool the XML correctly.

  You may need to play around with the SET LONG and SET LONGCHUNKSIZE commands to operate.

• character string buffer too small error in table form

  Hi people,
  
  One of my tabular forms suddenly stopped working suddenly after 3 months of work perfectly. Then I ran into debugging and looks like something bad went my LOV like below:
  

       0.16968     0.00328     ...Execute Statement: begin begin SELECT TIME_DISPLAY D, TIME_RETURN R bulk collect into wwv_flow_utilities.g_display,wwv_flow_utilities.g_value FROM TS_HOURS ORDER BY 2; end; end;     4     
  8
       0.17292     0.03912     ...Execute Statement: begin begin select /*+ cardinality(t 10) */ disp, val bulk collect into wwv_flow_utilities.g_display,wwv_flow_utilities.g_value from table(wwv_flow_utilities.get_temp_lov_data(2)) t order by insert_order, disp; end; end;     4     
  100
       0.21211     0.00224     report error: ORA-06502: PL/SQL: numeric or value error: character string buffer too small

  I have looked around and I saw a few others with the same problems but nothing that has like mine. Could someone please help me to find what is the problem? Thank you.
  
  I use Apex 4.1.1

  Hello

  the LOVs are displayed as a row okay? I wonder if it's some kind of a problem with the tabular forms?

  Concerning
  André

• Exception occurred in the Microsoft Access database engine: the field is too small to accept the amount of data you attempted to add.

  Hello

  I try to save a path in a table in an access database, but an error occurs:

  "Exception occurred in the Microsoft Access database engine: the field is too small to accept the amount of data you attempted to add." Try insert or paste less data. "in create a NI_Database_API.lvlib:Rec - Command.vi-> NI_Database_API.lvlib:Cmd Execute.vi-> NI_Database_API.lvlibData.vi B tools insert-> project total.vi.

  I've attached a JPEG of a part of the code and the code, but it won't work because the database is not attached,

  any help please?

  Ok

  I solve the resized problem.i column size

  Thank you

• Getting ORA-22835: buffer too small for to CHAR CLOB or BLOB to RAW conversion in my ODI interface

  Hi all

  I am creating an interface ODI as explained below,

  I table A column 'Comments' and one other table with column B "No Comment." I create a view as shown below and use it as a source for my interface.

  SELECT * FROM WC_EQM_CSAP_FS_TMP WHERE to_char (QUESTION_COMMENT) IN (SELECT NO_COMMENTS FROM WC_EQM_NO_COMMENTS_LIST).

  But my interface fails with the error below

  ORA-22835: buffer too small for to CHAR CLOB or BLOB to RAW conversion (real: 4108, maximum: 4000)

  22835 00000 - "too small buffer tank CLOB or BLOB to RAW conversion (actual: %s, maximum: %s)) '

  * Cause: an attempt was made to convert CLOB to CHAR or BLOB to RAW, where

  LOB size was larger than the buffer for CHAR and RAW limit types.

  Note that the widths are reported in characters if characters length isadds are in effect for the column, other widths are

  in bytes.

  Here QUESTION_COMMENT is of type CLOB data. NO_COMMENTS is also CLOB data type. The maximum length of the data of QUESTION_COMMENT is also 11710

  Please tell us how to solve.

  Thank you

  Dany

  IMHO, it is not good to compare CLOB, can be that it is possible to use the primary key for the comments

  Is it QUESTION_COMMENT and NO_COMMENTS a PRIMARY INDEX,

  may be is the best solution to create vacabulary with comments (if it does not exist) and then compare it by id;

  You can simply use the left join and check for null in a CASE statement

  Try this, but I don't know... as I said before I have no Oracle DB

  SELECT INTEGRATION_ID, DATASOURCE_NUM_ID, QUESTIONNAIRE_ID, QUESTION_ID,

  CLIENT_ID, SITE_ID, CLIENT_REP, COMMITMENT, ENGAGEMENT_TYPE, TOP_CLIENT_FLG,

  INITIAL_PLANNED_DT, REVISED_PLANNED_DT, INTERVIEW_DT, RECEIVED_DT, QUESTION_SCORE,

  (

  CASE WHEN EXISTS (SOME T2.NO_COMMENTS OF WC_EQM_NO_COMMENTS_LIST T2 WHERE DBMS_LOB.COMPARE (TMP.) (QUESTION_COMMENT, T2.NO_COMMENTS) = 0)

  THEN NULL

  OF OTHER QUESTION_COMMENT

  END QUESTION_COMMENT),

  (CASE WHEN QUESTION_SCORE<=5 then="" 1="" else="" 0="" end)="">

  0 AS QWOCOMMENTS,

  CREATED_ON_DT, CHANGED_ON_DT OF WC_EQM_CSAP_FS_TMP as TMP

  P.S. does not use TO_CHAR (LOB) there are possible error

• ORA-06502: PL/SQL: digital or value error: character string buffer too small

  Hello

  I am facing infinity listagg that 4000 bytes in listagg issue, so I created a defined user aggregate function suggested by asking tom team,

  https://asktom.Oracle.com/pls/Apex/f?p=100:11:0% 3A % 3A % 3A % 3aP11_QUESTION_ID: 2196162600402

  But I am facing the error as "digital or value error: character string buffer too small" in the Type on line 27 when questioning this way

  Select stragg (val) in the dummy_tab;

  My table has a column and the data type is varchar2 (50) and he has more than 300 documents,.

  can someone here help me to solve this problem.

  Thanks and greetings

  Guru

  Now if you followed this link, so I hope that you:

  (a) set the attribute of the object type to be a CLOB

  (b) sets the return value of your Mapper function to be a CLOB

  and not as in the example (which is the time before the existence of LISTAGG) as a Varchar2...

  HTH

• PL/SQL error: digital or value error: character string buffer too small

  HI gurus of the oracle,.

  I'm new to PL/SQL,

  my version of oracle's oracle 11g.

  I create a procedure to insert data from flat file to a table using UTL_FILE.

  The 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),

  DATE OF DT_DOB,

  ID_SERIAL VARCHAR2 (BYTE 9),

  DATE OF DT_RESPONSE,

  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. Type of NM_FINAL %;

  F_NM_START EXT_PERSON_INFO. Type of NM_START %;

  F_DT_DOB EXT_PERSON_INFO. Type of DT_DOB %;

  F_ID_SERIAL EXT_PERSON_INFO.ID_SERIAL%type;

  F_DT_RESPONSE EXT_PERSON_INFO. Type of DT_RESPONSE %;

  F_TRANS_TYPE EXT_PERSON_INFO. Type of TRANS_TYPE %;

  F_REG_RESPONSE EXT_PERSON_INFO. Type of REG_RESPONSE %;

  BEGIN

  fname: = "D:\raj\raj.txt";

  f: = utl_file.fopen('RAJ',fname,'r');

  loop

  Start

  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: digital or value error: character string buffer too small

  Please help me in this regard. Impossible to trace the issue.

  Thanks in advance

  Kind regards

  REDA

  The error message should include a line number to reference your code to see what line the error occurred on.

  That said, look at the documentation for SUBSTR as you incorrectly use the third parm.  It's length, no end of race.  That's your problem.

• too small Oracle of the buffer character ora-19011 chain

  Hello.

  I have the following XML:

  rowset <>

  < row >

  < code > < code > 01

  < details > 123 < / details >

  < / row >

  < row >

  < code > < code > 03

  < details > 1233 < / details >

  < / row >

  < row >

  < code > < code > 07

  < details > 12333 < / details >

  < / row >

  < / lines >

  I have Norman to extract the data of 1 in the sql query in this format:

  CodesList

  --------------

  01,02,03

  I use following code e:

  Select RTRIM (XMLAGG (XMLELEMENT(E,t.process_xml ||) ',')). Extract (' Row/Rowset/Code / Text () '). GETStringVAL(), ',') from table1 t

  The XML is being clob "process_xml."

  But I got the error message: too small oracle of the buffer character ora-19011 chain

  Help, please.

  The result is:

  ORA-19280: XQuery dynamic type mismatch: expected has atomic value - get the node

  My bad, I didn't test it.

  It works on 10.2.0.5 (the closest version I have at my disposal):

  Select t.id

  dbms_xmlgen.convert (x.column_value.getstringval (), 1) as val

  Table 1 t

  xmltable ("string-join(/Rowset/Row/Code,",")"

  by the way of xmltype (t.myxml)

  ) x ;

  or equivalent:

  Select t.id

  dbms_xmlgen.convert)

  XMLQUERY ('string-join(/Rowset/Row/Code, ",")"

  by the way of xmltype (t.myxml)

  contents of return

  ). getStringVal()

  1

  ) as val

  Table 1 t;

  DBMS_XMLGEN. Call CONVERT is here to ensure that the entity is referred to in elements (if any) will be unescaped back to their readable forms.

  If you know for sure that there's no entity occurrence, you can remove that extra step.

• ORA-02354: Error exporting/importing data, ORA-01555: snapshot too old: rollback segment number with the name "" too small

  Hello

  I am getting below error while taking expdp backup table of BLOB.

  ORA-31693: Data Table object 'HCLM_ADMIN '. "' SCAN_UPLOADEDFILES_TEMP ' failed to load/unload and being ignored because of the error:

  ORA-02354: Error exporting/importing data

  ORA-01555: snapshot too old: rollback segment number with the name "" too small

  ORA-22924: snapshot too old

  ORA-31693: Data Table object 'HCLM_ADMIN '. "' TPA_FAXWATCHER ' failed to load/unload and being ignored because of the error:

  ORA-02354: Error exporting/importing data

  ORA-01555: snapshot too old: rollback segment number with the name "" too small

  ORA-22924: snapshot too old

  We have already set aside retention to 50000 .table structure are:

  SQL > show Cancel parameter

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  UNDO_MANAGEMENT string AUTO

  UNDO_RETENTION integer 50000

  undo_tablespace string UNDOTBS1

  SQL > alter table hclm_admin. SCAN_UPLOADEDFILES_TEMP modify lob (FILE_BLOB) (RETENTION);

  Modified table.

  SQL > select nom_de_colonne, pctversion and retention

  from dba_lobs where owner = 'HCLM_ADMIN' and table_name = "SCAN_UPLOADEDFILES_TEMP";

  COLUMN_NAME

  --------------------------------------------------------------------------------

  PCTVERSION RETENTION

  ---------- ----------

  FILE_BLOB

  50000

  SQL > alter table hclm_admin. TPA_FAXWATCHER modify lob (FILEDATA_BLOB) (RETENTION);

  Modified table.

  SQL > select column_name, pctversion and retention of dba_lobs where owner = 'HCLM_ADMIN' and table_name = "SCAN_UPLOADEDFILES_TEMP";

  Column_name PCTVERSION RETENTION

  ---------- ----------

  FILE_BLOB

  50000

  CREATE TABLE HCLM_ADMIN. TPA_FAXWATCHER

  (

  FILENAME_VAR VARCHAR2 (50 BYTE),

  DATE OF CREATED_DATE_DTE,

  FILEPATH_VAR VARCHAR2 (100 BYTE),

  DATE OF TIMESTAMP_DTE,

  FAXNO_VAR VARCHAR2 (15 BYTE),

  DEPARTMENT_VAR VARCHAR2 (50 BYTE),

  REQUESTTYPE_VAR VARCHAR2 (50 BYTE),

  TAGTO_VAR VARCHAR2 (50 BYTE),

  REMARK_VAR VARCHAR2 (1000 BYTE),

  DOCTYPE_VAR VARCHAR2 (50 BYTE),

  TAGTOVALUE_VAR VARCHAR2 (50 BYTE),

  DOCTYPE_OTHER_VAR VARCHAR2 (50 BYTE),

  HEGIC_NO_VAR VARCHAR2 (50 BYTE),

  RECORDNO_NUM NUMBER OF NON-NULL,

  FILEDATA_BLOB BLOB,

  DATE OF FAXLOCKDATE_DTE,

  NUMBER OF FAXLOCKSTATUS_VAR

  FAXLOCKBYUSER_VAR VARCHAR2 (50 BYTE)

  )

  (STORE AS) LOB (FILEDATA_BLOB)

  TABLESPACE HCLM_ALERTSVC

  ALLOW ONLINE STORAGE

  8192 CHUNK

  RETENTION

  NOCACHE

  LOGGING

  INDEX)

  TABLESPACE HCLM_ALERTSVC

  STORAGE)

  64K INITIALS

  ACCORDING TO 1 M

  MINEXTENTS 1

  MAXEXTENTS UNLIMITED

  PCTINCREASE 0

  DEFAULT USER_TABLES

  ))

  STORAGE)

  64K INITIALS

  ACCORDING TO 1 M

  MINEXTENTS 1

  MAXEXTENTS UNLIMITED

  PCTINCREASE 0

  DEFAULT USER_TABLES

  ))

  TABLESPACE HCLM_ALERTSVC

  PCTUSED 0

  PCTFREE 10

  INITRANS 1

  MAXTRANS 255

  STORAGE)

  64K INITIALS

  ACCORDING TO 1 M

  MINEXTENTS 1

  MAXEXTENTS UNLIMITED

  PCTINCREASE 0

  DEFAULT USER_TABLES

  )

  LOGGING

  NOCOMPRESS

  NOCACHE

  NOPARALLEL

  MONITORING;

  ALTER TABLE HCLM_ADMIN. (ADD) TPA_FAXWATCHER

  KEY ELEMENTARY SCHOOL

  (RECORDNO_NUM)

  USING INDEX

  TABLESPACE HCLM_ALERTSVC

  PCTFREE 10

  INITRANS 2

  MAXTRANS 255

  STORAGE)

  64K INITIALS

  ACCORDING TO 1 M

  MINEXTENTS 1

  MAXEXTENTS UNLIMITED

  PCTINCREASE 0

  ));

  CREATE TABLE HCLM_ADMIN. SCAN_UPLOADEDFILES_TEMP

  (

  NUMBER OF TEMPID_NUM

  SESSION_ID VARCHAR2 (200 BYTE),

  NUMBER OF UPLOADFILE_NUM

  NUMBER OF DOCNO_NUM

  NUMBER OF SCANJOB_NUM

  FILENAME_VAR VARCHAR2 (200 BYTE),

  FILETYPE_VAR VARCHAR2 (200 BYTE),

  FILE_BLOB BLOB,

  VARCHAR2 (200 BYTE) FLAG,

  NUMBER OF USERID_NUM

  CREATED_DATE DATE

  )

  (STORE AS) LOB (FILE_BLOB)

  TABLESPACE PHCLMDBTBS

  ALLOW ONLINE STORAGE

  8192 CHUNK

  RETENTION

  NOCACHE

  LOGGING

  INDEX)

  TABLESPACE PHCLMDBTBS

  STORAGE)

  64K INITIALS

  ACCORDING TO 1 M

  MINEXTENTS 1

  MAXEXTENTS UNLIMITED

  PCTINCREASE 0

  DEFAULT USER_TABLES

  ))

  STORAGE)

  64K INITIALS

  ACCORDING TO 1 M

  MINEXTENTS 1

  MAXEXTENTS UNLIMITED

  PCTINCREASE 0

  DEFAULT USER_TABLES

  ))

  TABLESPACE PHCLMDBTBS

  PCTUSED 0

  PCTFREE 10

  INITRANS 1

  MAXTRANS 255

  STORAGE)

  64K INITIALS

  ACCORDING TO 1 M

  MINEXTENTS 1

  MAXEXTENTS UNLIMITED

  PCTINCREASE 0

  DEFAULT USER_TABLES

  )

  LOGGING

  NOCOMPRESS

  NOCACHE

  NOPARALLEL

  MONITORING;

  Kind regards

  Hello

  First check the lob corrupt as:

  SQL > create table corrupted_lob_data (corrupted_rowid rowid);

  Table created.

  SQL > set off concat

  SQL >

  declare

  SQL > error_1555 exception;

  pragma exception_init (error_1555,-1555);

  number num.

  Start

  for cursor_lob in (select rowid r, & lob_column of table_owner. & table_with_lob) loop

  Start

  NUM: = dbms_lob.instr (. cursor_lob & lob_column, hextoraw ('889911'));

  exception

  When error_1555 then

  insert into corrupted_lob_data values (cursor_lob.r);

  commit;

  end;

  end loop;

  end;

  2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

  17.

  Enter the value of lob_column: FILE_BLOB

  Enter the table_owner value: hclm_admin

  Enter the value of table_with_lob: SCAN_UPLOADEDFILES_TEMP

  former 6: for cursor_lob in (select rowid r, & lob_column of table_owner. & table_with_lob) loop

  6 news: for cursor_lob (select rowid r, FILE_BLOB of hclm_admin loop SCAN_UPLOADEDFILES_TEMP.)

  old 8: num: = dbms_lob.instr (. cursor_lob & lob_column, hextoraw ('889911'));

  8 new: num: = dbms_lob.instr (cursor_lob. FILE_BLOB, hextoraw ('889911'));

  PL/SQL procedure successfully completed.

  SQL > select * from corrupted_lob_data;

  CORRUPTED_ROWID

  ------------------

  AAASF/AAKAABacyAAA

  To resolve this problem, we have 3 options

  (1) to restore and recover the LOB segment using physical backup.

  (2) empty LOBs affected using the UPDATE, as mentioned in the Note 787004.1statement:

  SQL > update SCAN_UPLOADEDFILES_TEMP

  Set FILE_BLOB = empty_blob()

  where rowid in (select corrupted_rowid

  of corrupted_lob_data);

  SQL > commit;

  (3) perform the export, excluding the corrupt ROWID. by adding the following to export command parameter

  Query =------"where rowid not in (\'AAASF/AAKAABacyAAA\'\) \ \" "

  Kind regards

  Alok Dwivedi

• PL/SQL: digital error or value (string buffer of characters too small)

  Hi all
  
  Here is the procedure used to send notifications. It worked very well in the previous version of DB :-10.1.0.5.0 and it has been recently upgraded to 11.2.0.2.0.
  
  I respond very well, but when running it throws the error.
  

  PROCEDURE PROC_STATUS_MAIL_UNADJ IS
  
         K_BOUNDARY CONSTANT VARCHAR2(1000) := 'a1b2c3d4e3f2g1';
        l_analysis_report  VARCHAR2(32767); --empty_clob; --clob :=
        l_header VARCHAR2(1000);
        l_footer VARCHAR2(200);
        cnxn UTL_SMTP.connection;
  
        cursor cloc is select location_id from locations order by location_id asc;
  
        loc_id cloc%rowtype;
  
  BEGIN
  
    dbms_output.enable (1000000);
  
       FOR loc_id in  cloc
  
       loop
  
       l_analysis_report := '<style type="text/css">
      <!--.style1 { font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10pt; font-style: normal; color: #FF0000}-->
      <!--.sidebar1 { font-family: Arial, Helvetica, sans-serif; font-size: 10px}-->
      <!--.text { font-family: Arial, Helvetica, sans-serif; font-size: 12px}-->
      </style>
      <center><b><font face="Arial">Run Summary Report'
                  || TO_CHAR(SYSDATE, 'DD-MON-YYYY HH:MI AM') || '<br><br></font></b></center>'
                  || ' <div align="center"><table width="95%" border="1" cellspacing="0" cellpadding="1" </div>'
                  || '<span style="font-size: 10pt; font-family: Arial"> </span> '
                  || '<tr bgcolor=b4b4b4><td align="center"> <font size="3"> <b>'
                  || 'Analysis</b></td><td align="center"><font size="3"> <b>'
                  || 'Start Time</b></td><td align="center"><font size="3"> <b>'
                  || 'End Time</b></td><td align="center"><font size="3"> <b>'
                  || 'Run Duration (mins)</b></td><td align="center"><font size="3"> <b>'
                  || 'Status</b></font></td></tr> ' || UTL_TCP.CRLF;
  
  
                  FOR curr_refresh IN (SELECT AN.ANALYSIS_ID,AN.NAME ANALYSIS_NAME,TO_CHAR(ARH.RUN_START_TIME,'DD/MM/YYYY HH:MI:SS') START_TIME,
                                       TO_CHAR(ARH.RUN_END_TIME,'DD/MM/YYYY HH:MI:SS')END_TIME,
                                       ROUND(((ARH.RUN_END_TIME-ARH.RUN_START_TIME)*24*60),2) RUN_TIME_SECS,ARH.JOB_STATUS STATUS
                                       FROM
                                       RUN_HISTORY ARH,ANALYSES AN
                                       WHERE
                                       AN.ANALYSIS_ID=ARH.ANALYSIS_ID
                                       AND AN.CYCLE_IND_ID IN (1,3)
                                       AND ARH.RUN_START_TIME>TO_DATE(SYSDATE-30)
                                       AND ARH.JOB_NAME LIKE 'RHS_QU%'                                   
                                       AND AN.LOCATION_ID = loc_id.location_id
                                       AND ARH.JOB_STATUS='Completed'
                                       ORDER BY ARH.RUN_START_TIME DESC)
  
                         LOOP
  
                     l_analysis_report  := l_analysis_report ||'<tr><td align="center">'|| curr_refresh.analysis_name
                        || '</td><td align="center">' || curr_refresh.start_time || '</td><td align="center">'
                        || curr_refresh.end_time || '</td><td align="center">'|| curr_refresh.RUN_TIME_SECS ||
                        '</td><td align="center">'|| curr_refresh.status ||
                        '</td> </tr>' || UTL_TCP.CRLF;
                    exit when length (l_analysis_report) > 32500;
  
  
                 END LOOP;
  
                l_analysis_report := l_analysis_report || '</table><br><br>';
                 l_footer := UTL_TCP.CRLF ||'<b> Note: This is an auto generated email. Please do not reply to it. Contact the IT team for any further information.</b>'||  UTL_TCP.CRLF;
  
  
                 FOR curr_email IN (SELECT GLOBAL_NAME INSTANCE_NAME,
                                    EU.EMAIL_USER_LAST_NAME last_name, EU.EMAIL_USER_FIRST_NAME ACNAME,
                                    EU.EMAIL_USER_EMAIL_ID,loc.LOCATION_NAME LOC_NAME,
                                    '[email protected]' MAIL_FROM
                                    FROM
                                    RHS_EMAIL_USER EU,LOCATIONS LOC,GLOBAL_NAME
                                    WHERE EU.LOCATION_ID=LOC.LOCATION_ID
                                    AND EU.LOCATION_ID=loc_id.location_id
                                ) LOOP
  
              cnxn := UTL_SMTP.open_connection('smtprelay.inc.com', 25);
              UTL_SMTP.helo(cnxn, 'smtprelay.inc.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: Un-Adjusted Analysis Report for ' || curr_email.loc_name || ' Location from' || 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_analysis_report || l_footer);
              UTL_SMTP.quit(cnxn);
  
              
              END LOOP;
  
              END LOOP;
  
  END PROC_STATUS_MAIL_UNADJ;
  
  
  Error :- 
  
  ORA-06502: PL/SQL: numeric or value error: character string buffer too small
  ORA-06512: at "SYS.UTL_SMTP", line 591
  ORA-06512: at "SYS.UTL_SMTP", line 497
  ORA-06512: at "SYS.UTL_SMTP", line 503
  ORA-06512: at "RISK_HISTORY.PKG_RHS_EMAIL_NOTIFY", line 206
  ORA-06512: at "RISK_HISTORY.PKG_RHS_EMAIL_NOTIFY", line 414
  ORA-06512: at line 2

  Can it please let me know if there is no problem with the code or upgrade questions?
  
  Kind regards
  Sunny
  
  Published by: k_17 on October 13, 2011 12:07

  You must move the thread {forum: id = 75}.

• GATHER_TABLE_STATS and character buffer too small string error

  Hello
  
  I am trying to run stats gather on a partition of a table. It gives me the error below.
  There is no trigger or whatever it is on the table. Can you please help...
  
  BEGIN
  DBMS_STATS. GATHER_TABLE_STATS (ownname = > 'AB', tabname = > 'SAMPLE_TABLE_NAME_FRTEST',)
  estimate_percent = > DBMS_STATS. AUTO_SAMPLE_SIZE,
  partName = > 'SAMPLE_TABLE_NAME_FRTEST_201011');
  END;
  
  ORA-06502: PL/SQL: digital or value error: character string buffer too small
  ORA-06512: at "SYS." DBMS_STATS", line 13437
  ORA-06512: at "SYS." DBMS_STATS", line 13457
  ORA-06512: at line 2
  
  Here are the details of the version:
  Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
  PL/SQL Release 10.2.0.4.0 - Production
  
  Thank you.
  
  Published by: me * on 21/08/2011 17:10

  me * wrote:
  Hello

  I am trying to run stats gather on a partition of a table. It gives me the error below.
  There is no trigger or whatever it is on the table. Can you please help...

  BEGIN
  DBMS_STATS. GATHER_TABLE_STATS (ownname => 'AB', tabname => 'SAMPLE_TABLE_NAME_FRTEST',
  estimate_percent-online DBMS_STATS. AUTO_SAMPLE_SIZE,
  partName => 'SAMPLE_TABLE_NAME_FRTEST_201011');
  END;

  ORA-06502: PL/SQL: digital or value error: character string buffer too small
  ORA-06512: at "SYS." DBMS_STATS", line 13437
  ORA-06512: at "SYS." DBMS_STATS", line 13457
  ORA-06512: at line 2

  Here are the details of the version:
  Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
  PL/SQL Release 10.2.0.4.0 - Production

  Thank you.

  Published by: me * on 21/08/2011 17:10

  You get a maximum of 30 characters in the array, column, etc. names in Oracle.

  You have really a partition name exceeds?

  SAMPLE_TABLE_NAME_FRTEST_201011

  At more than 30 characters...

• ORA-24331: buffer too small user (dbms_xslprocessor.valueOf)

  Hello
  
  I'm stuck with an XML file parsing problem... everything went perfectly fine until I hit a large XML file and now my procedure returns this error ORA-24331: buffer too small user. I Googled it a little and found out that it is the cause of dbms_xslprocessor.valueOf.
  
  Anyway could someone help me out? Below you will find my version of db Oracle and proceure I use.
  
  Thank you!
  
  Oracle:

  Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
  PL/SQL Release 10.2.0.5.0 - Production
  CORE    10.2.0.5.0      Production
  TNS for Linux: Version 10.2.0.5.0 - Production
  NLSRTL Version 10.2.0.5.0 - Production

  And procedure:
  

  PROCEDURE xml is
  BEGIN
   
   DECLARE
    l_parser  dbms_xmlparser.Parser;
    l_doc     dbms_xmldom.DOMDocument;
    l_nl      dbms_xmldom.DOMNodeList;
    l_n       dbms_xmldom.DOMNode;
    l_temp    VARCHAR2(1000); 
    v_lang_ctx NUMBER := dbms_lob.default_lang_ctx;
    v_warning NUMBER;
    v_dest_clob CLOB;
    v_src_clob BFILE; 
    v_amount NUMBER;
    v_src_offset NUMBER:=1;
    v_dest_offset NUMBER:=1;
  
    
    TYPE tab_type IS TABLE OF klasius_srv%ROWTYPE;  
    t_tab  tab_type := tab_type();
  BEGIN
  
     v_src_clob := bfilename( directory => 'XML_DIR',  filename => 'srv.xml');
  
    dbms_lob.createtemporary(v_dest_clob, cache=>FALSE);
    dbms_lob.open(v_src_clob, dbms_lob.file_readonly);
  
    dbms_lob.loadclobfromfile
      (dest_lob => v_dest_clob
      ,src_bfile => v_src_clob
      ,amount => dbms_lob.getlength( v_src_clob )
      ,dest_offset => v_dest_offset
      ,src_offset => v_src_offset
      ,bfile_csid => NLS_CHARSET_ID('UTF8')
      ,lang_context => v_lang_ctx
      ,warning => v_warning
    );
  
    dbms_lob.close(v_src_clob);
    
    dbms_session.set_nls('NLS_DATE_FORMAT','''DD-MON-YYYY''');
  
    l_parser := dbms_xmlparser.newParser;
  
    dbms_xmlparser.parseClob(l_parser, v_dest_clob);  
    l_doc := dbms_xmlparser.getDocument(l_parser);
  
    dbms_lob.freetemporary(v_dest_clob);
    dbms_xmlparser.freeParser(l_parser);
  
    l_nl :=  dbms_xslprocessor.selectNodes(dbms_xmldom.makeNode(l_doc),'/NewDataSet/Table');
  
  
    FOR cur_emp IN 0 .. dbms_xmldom.getLength(l_nl) - 1 LOOP
      l_n := dbms_xmldom.item(l_nl,cur_emp);
      t_tab.extend;
  
      dbms_xslprocessor.valueOf(l_n,'code_x0020_ra',t_tab(t_tab.last).srv);
      dbms_xslprocessor.valueOf(l_n,'code_x0020_kat',t_tab(t_tab.last).sif_srv);
      dbms_xslprocessor.valueOf(l_n,'Des',t_tab(t_tab.last).de_srv);
      dbms_xslprocessor.valueOf(l_n,'Deskriptor_x0020__x0028_ang_x0029_',t_tab(t_tab.last).ang_srv);
    END LOOP;
  
    FORALL i IN t_tab.first .. t_tab.last
      INSERT INTO klasius_srv VALUES t_tab(i);
  
    COMMIT; 
  
    dbms_xmldom.freeDocument(l_doc);
      
  END;
  END;

  Well, it depends on the definition of klasius_srv % RowType - like that the members of the structure (columns/fields) is used by dbms_xslprocessor. ValueOf() to write values in.

  To find this error, you will need to determine the size of a member in this structure and the size of the value being written inside.

  The error occurs in one (or more) of the following statements in your code:

  ..
      dbms_xslprocessor.valueOf(l_n,'code_x0020_ra',t_tab(t_tab.last).srv);
      dbms_xslprocessor.valueOf(l_n,'code_x0020_kat',t_tab(t_tab.last).sif_srv);
      dbms_xslprocessor.valueOf(l_n,'Des',t_tab(t_tab.last).de_srv);
      dbms_xslprocessor.valueOf(l_n,'Deskriptor_x0020__x0028_ang_x0029_',t_tab(t_tab.last).ang_srv);
  ..
  

  Thus, for example: what is the size of the of (description?) writing XML element in the .de_srv t_tab (t_tab.last) - in other words, in the de_srv of the klasius_srv table column?

  If this XML element is 200 characters and your database column is a 100 bytes in size, then dbms_xslprocessor. ValueOf() won't be able to write the value of the XML element in that column variable.

  Bottom line - you must debug 4 statements above of the source code you wrote - and ensure that the amount of data that you read from the XML element can be written in the variable (column) that is used to receive this value.

  The 4000 bytes, I mentioned is the largest size of column varchar2 (string), you can set in the SQL engine. If this XML value is 1 KB, then you cannot use varchar2. In this case, you will need to look at using the CLOB data type instead.

• Too small toolbar in Firefox

  Hello
  
  I have a problem of layout with ADF Faces 11.1.1.3.0. I have a table surrounded by a < tt > & lt; AF:panelCollection & gt; < /tt >. Inside of the facet of bar tools < /tt > < tt > < TT > & lt; AF:panelCollection & gt; < /tt > I have a toolbar. In Internet Explorer (7.0), the toolbar makes it very well. However, in Firefox (3.6.8), the toolbar is always a bit too small, causing the last button be replaced by an icon of overflow. The button turns when you press the icon of overflow. However, there is plenty of space to the right of the toolbar, if there is no reason to use the overflow mechanism.
  
  I tried to get around this problem by adding spacers and grouping buttons, but nothing seems to help, I'm still stuck with the last overflow-popup button. I suspect it is a rendering bug ADF Faces. Does anyone know a work around?
  
  Best regards
  Bart kummel

  The version of Firefox I have is earlier than yours, but I won't have the same problem. When you resize the Explorer (reduce its size for example), at what point do the buttons disappear. In my version they disapper when they run out of space. I would try to play maybe with the margins and filling in the browser (you can use firebug) and see if you can adjust it. I don't think you can enable the filter bar but no show hide it (if you use a collection of panels). However, I don't think it's your problem. Maybe you can try one of the other toolbar facets like after or high school to see if it makes a difference for you.

• PL/SQL: digital or value error: string buffer too small characters - LOV?

  Environment:
  
  APEX 3.1.1.00.09 under AIX 5.3 10.2.0.2 in
  
  Problem sample on apex.oracle.com:
  
  Workspace: GALWAY
  ID: GWICKE
  Password: GWICKE
  
  Application ID: 43172 (BUILDERPL) NOTE: there are three 3 applications with the same name, but this one is currently broken
  
  I get the dreaded "" ORA-06502: PL/SQL: digital or value error: character string buffer too small "when you try to create a new line."
  
  To reproduce the error:
  
  1 run page 3
  2 - Select any agency
  3 - Click on the button "create a new contract.
  4 - Select the start and end dates in the DATE picker
  5 - Click on the button "Add contract".
  
  If the line is added successfully if please go to Indianapolis and run the app for me since you obviously have the 'touch '! ;-) >
  
  But seriously folks,
  
  I've read many threads about this error and for the most part, they seem to point to large LOV. I have three 3 LOV on the page but only a 1 is dynamic and display and back elements are the same, a description in this case. There are 400 lines in the LOV table and the description is defined as VARCHAR2 (75), so we're not talking a huge amount of data.
  
  To further complicate the issue, this application was working just a couple of days. What changes I've made since a few days, you might ask?
  
  The only thing that comes to mind is I did go through the definitions of element and change the values of maximum size equal to the size of the columns in the target table, using a value of 22 for the NUMBER of columns.
  
  Since then I went back and changed at a much greater value than their corresponding column definitions, but nothing helped.
  
  Another interesting fact is that if an existing contract is selected on the page (Page 3 in my case) by selecting an agency that produces values in the second select list (selection of contract) and then clicking on "change this contract." After you change any value or fill in one of the missing values, click "Apply Changes" and he should have success.
  
  The new contract page and the page of modification of the contract are the same (Page 2) just with different buttons.
  
  Thanks a lot for any assistance. Indeed, it is greatly appreciated.
  
  -gary
  
  PS I also tried to change the LOV both given a popup and a standard text box I typed in, both received the same message.

  Gary - I deleted then recreated your DML process and it seems to have solved the problem. Export page reveals something odd in the process definition:

  declare  p varchar2(32767) := null;  l_clob clob;  l_length number := 1;beginp:=p||'F|#OWNER#:BUILDERPL_CONTRACT:P2_CONTRACT_SEQ:CONTRACT_SEQ|I';
  
  wwv_flow_api.create_page_process( ...
  

  That the assignment statement must not have ' F | "as the first two characters. There must be a bug in one of the wizards who created the process. Have you used a wizard to create the page?

  Scott

• Safari 10: too small font size

  After the installation of Safari 10.0 this morning, nothing is as it used to be - printing on most websites is too small for me to read. The option to adjust the size to a minimum size by default in the Preferences window has disappeared; pages can be enlarged in 125, 150% etc but not what I want.

  I no has not upgraded to the latest version of Safari to end up reading texts too small they are printed on stamps!

  Do these guys at apple all this walk with a watchmakers eyepiece? All solutions (style sheets?)?

  There are a number of discussions on this issue with your same concern. I agree, the issue of font size is really bad and the zoom function is NOT a way to solve this problem. As others have suggested sending back to Apple is a way of approaching the question with the hope that they give the choice of font size in preferences rather than this impassable zoom feature.