Long Value Error

I am getting the following error while runing an interface.
ORA-01461: can bind a LONG value only for insert into a LONG column
But there is no column with the datatype Long.
What could be the error?

Do you know what field and/or which record is causing the problem? If not, that's where I'd start in debugging this. ODI is attempting to insert a value which Oracle DB believes is a long data type - you'll need to understand what's causing this in order to fix it.

Similar Messages

Import Spreadsheet Long value error

Hi folks,
I'm trying to Import Text or Spreadsheet Data into a table in Htmldb.
It should create a new-table with some column names and it's data. I converted a Excel list and saved it to .txt.
When I try to import it into htmldb (al columns Varchar2) I get the following error message.
ORA-20001: Load csv data error: ORA-01461: can bind a LONG value only for insert into a LONG column ORA-01461: can bind a LONG value only for insert into a LONG column
Does Anyone know what I can do about this problem?
regards,
Richard

Richard,
I ran into a similar problem. I found that APEX is not to fond of 'cr + lf' characters in my spreadsheet.
Option 1:
Used the clean function (in excel) to remove all of the special characters. Also, check the length of the fields in excel and make sure your VARCHAR2 length is larger than the max entry length.
Option 2:
Change from VARCHAR2 to CLOB.
Derek

Error : ORA-06502: PL/SQL: numeric or value error while fetch LONG datatype

Hello All,
I have written a script to fetch the text for a view in PLSQL and it gives me the following error :
Error : ORA-06502: PL/SQL: numeric or value error
declare
l_text all_views.text%type;
begin
SELECT text INTO l_text FROM all_views WHERE view_name = 'XXVIEW';
exception
when others then
dbms_output.put_line('Error : '||sqlerrm);
end;
The above works for some views and not view other views. Can anyone let me know what could be the reason for ORA-06502 when fetching into a long variable in PLSQL.
Would appreciate any response.
Thanks,

If view 'XXVIEW' contains "no record" for field "text" then it'll show this error.
I mean "SELECT text FROM all_views WHERE view_name = 'XXVIEW';" returns "No record found" then how can you assign "no record" to a variable "l_text ".
try to execute : SELECT text FROM all_views WHERE view_name = 'XXVIEW';
What does it give you? any "Blank records"?
Edited by: H. on Feb 20, 2009 8:17 AM

Error: PL/SQL ORA-00932 inconsistent datatype when using LONG value

Good morning:
I am using a work PL/SQL script where I am using a LONG value in a cursor. When I execute it, I am receiving:
PL/SQL ORA-00932 inconsistent datatype: expected NUMBER got LONG
set serveroutput ON SIZE 1000000
set heading off
set feedback off
set trimspool off
set echo off
set term off
set pagesize 0
SPOOL &so_outfile;
DECLARE
v_data_file          varchar2(30);
--   v_sch_code            varchar2(10);
--   v_instance_name       varchar2(10);
    ws_path            payroll.pybutfl.pybutfl_utl_file_path%TYPE;
    v_data_line           VARCHAR2 (2000)                              := NULL;
    fhandle_o             UTL_FILE.file_type;
    v_line_count          NUMBER                                       := 0;
    v_selected_count      NUMBER                                       := 0;
    v_error_count         NUMBER                                       := 0;
    v_written_count       NUMBER                                       := 0;
    v_error_text          VARCHAR2 (50)       := ' AMACONF_ERR: Unable to write the line. ';
    v_errm                VARCHAR2 (255);
    v_sqlerrm             VARCHAR2 (255);
    v_payment_type        VARCHAR2(10);
CURSOR C1 IS
select RTRIM
        AMRCONF_PIDM_ERR            ||'|'||
        AMRCONF_IDEN_CODE_ERR       ||'|'||
        AMRCONF_ENTRY_DATE_ERR      ||'|'||
        AMRCONF_CONFID_IND_ERR      ||'|'||
       *AMRCONF_COMMENT_ERR        ||'|'||*
        AMRSUBJ_SUBJ_CODE_ERR       ||'|'||
        ERROR_CODE                  ||'|'||
        ERROR_CODE_TEXT                 ) data_line
        from WSUALUMNI.AMRCONF_ERR;
BEGIN
DBMS_OUTPUT.put_line ('Program Generating AMACOMT Mass Update Error File ');
IF UTL_FILE.is_open (fhandle_o)
    THEN
   UTL_FILE.fclose (fhandle_o);
END IF;
/* Name The File Here */
v_data_file := ('Amaconf_error.txt');
SELECT RTRIM (pybutfl_utl_file_path)
      INTO ws_path
      FROM payroll.pybutfl;
      fhandle_o := UTL_FILE.fopen (ws_path, v_data_file, 'w');
      DBMS_OUTPUT.put_line ('UTLFILE file for this run is: ' || ws_path||'/'||v_data_file);
      v_written_count := 0;
FOR c1_rec IN C1 LOOP
      BEGIN
        v_selected_count := v_selected_count + 1;
        v_data_line := rtrim(c1_rec.data_line);
        UTL_FILE.put_line (fhandle_o, v_data_line);
        v_written_count := v_written_count + 1;
    EXCEPTION
     WHEN OTHERS
      THEN
       DBMS_OUTPUT.put_line (v_error_text);
       v_error_count := v_error_count + 1;
    END;
END LOOP;
     DBMS_OUTPUT.put_line ('Number of Records Selected: ' || v_selected_count);
     DBMS_OUTPUT.put_line ('Number of Records Written: ' || v_written_count);
      IF UTL_FILE.is_open (fhandle_o)
      THEN
         UTL_FILE.fclose (fhandle_o);
      END IF;
END;
SPOOL OFF;If I comment out the "AMRCONF_COMMENT_ERR ||'|'||" line, then the script works fine. The table was created as:
Create Table WSUALUMNI.AMRCONF_ERR
    AMRCONF_PIDM_ERR             NUMBER (8)    NOT NULL,
    AMRCONF_IDEN_CODE_ERR        VARCHAR2(5)   NOT NULL,
    AMRCONF_ENTRY_DATE_ERR       DATE          NOT NULL,
    AMRCONF_CONFID_IND_ERR       VARCHAR2(1),
    AMRCONF_COMMENT_ERR          LONG,
    AMRSUBJ_SUBJ_CODE_ERR        VARCHAR2(5)   NOT NULL,
    ERROR_CODE                   VARCHAR2(12) NOT NULL,
    ERROR_CODE_TEXT              VARCHAR2(50) NOT NULL
); I don't get what is the problem here in the script.

Hi,
Feew suggestions
1) LONG is a deprecated type hence if possible start working on changing that column
2) CLOB will your preferred datatype over LONG.
3) you cannot use RTRIM on long.
here is a very quick example
drop table h
create table h (x long,y varchar2(100))
select rtrim(x) from h
select rtrim(y) from hSolution:
[http://www.oracle.com/technology/oramag/code/tips2003/052503.html]
need a better solution change the datatype to clob and
drop table h
create table h (x clob,y varchar2(100))
select dbms_lob.substr( x, 4000, 1 ) from h
select rtrim(y) from hCheers!!!
Bhushan

ORA-06502: PL/SQL: numeric or value error: raw variable length too long

Hi All,
Oracle 9.2.0.1.0 and Oracle 10g.
I the following procedure:
CREATE OR REPLACE TYPE Resource_TT AS TABLE OF RAW(16)
CREATE OR REPLACE PROCEDURE GET_ROLEMAPPING_Temp
RoleIds IN NVARCHAR2 DEFAULT NULL ,
Application IN NVARCHAR2 DEFAULT NULL ,
MappingExixts OUT NVARCHAR2
AS
     v_Application NVARCHAR2(150) := Application;
     resource_list CONSTANT Resource_TT := Resource_TT(RoleIds);
     v_temp NUMBER(1, 0) := 0;
BEGIN
     SELECT 1 INTO v_temp
FROM DUAL
WHERE EXISTS ( SELECT SecurityGroupId
FROM SKESGResourceMapping
WHERE APPLICATION = v_Application
AND RoleId IN
                                                  select column_value
                                                  from table(resource_list)
EXCEPTION
WHEN NO_DATA_FOUND THEN
MappingExixts := 'NO';
END;
IF v_temp = 1 THEN
MappingExixts := 'YES';
     END IF;
END;
while calling the procedure from sql*plus, the calling block is :
variable MappingExixts nvarchar2(100);
execute Get_RoleMapping_Temp('2f90e7969e0a9045aeb5b5ed7b3da9d6,363aef470e10094281e5040627e3b6f8', 'repo1', :MappingExixts);
print MappingExixts;
It is throwing an error saying:
ORA-06502: PL/SQL: numeric or value error: raw variable length too long
ORA-06512: at "ORACLE1.GET_ROLEMAPPING_TEMP", line 8
Thanks for your valuable time and suggestions

Hi Binoy,
Thanks for your quick response, I increased its size to 200, but I am getting the following error
ORA-06502: PL/SQL: numeric or value error: hex to raw conversion error
ORA-06512: at "ORACLE1.GET_ROLEMAPPING_TEMP", line 8

Agent Upload error: ERROR-400|ORA-01461: can bind a LONG value ...

Periodically receiving the following error on our Grid Control machine:
[oracle@lugc01 agent10g]$ ./bin/emctl upload agent
Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
EMD upload error: Failed to upload file B0000021.xml: HTTP error.
Response received: ERROR-400|ORA-01461: can bind a LONG value only for insert into a LONG column
This is the agent that is on the host that runs Grid Control. GC Seems to be running fine, but the agent has this problem quite regularly. This also seems to happen on other linux 10.2.0.4 agents as well.
To remedy it, I go in and remove the upload data in $AGENT_HOME/sysman/emd/upload and then restart the agent. I don't like doing this.
Any ideas?

Hi
The error display is very strong. The mean is that the agent try upload a file to the OMS and when the OMS Server go to insert the data in a SYSMAN Table , the value is of a LONG COLUMN and the table not have this type of column.
Please provide me:
- When the error appear , take the xml file and send me
- Run this comand in the agent:
emctl config agent listtargets
If i have the xml file, i can try to solve the problem
Regards
Roberto Hernandez
[email protected]

Why this Error comes "ORA-01461: can bind a LONG value only for insert into

I'm using Oracle 9.2 with Weblogic 8 server. After Googling i got to resolve this issue "ORA-01461: can bind a LONG value only for insert into a LONG column" by adding : oracle.jdbc.RetainV9LongBindBehavior=true in server properties for the datasource.
But why did this error come and after keeping the above property why did this error go away ?
Can anyone help me on this.....

You have an error in the code:
1. you don't provide a value for 'what' - you have to tell Oracle what it should execute when it submits the job.
And remember - with ISUBMIT the next_date parameter has datatype VARCHAR2 - SUBMIT uses datatype DATE. So make sure you provide a VARCHAR2 value and do not rely on implicit conversion.
>
PROCEDURE DBMS_JOB.ISUBMIT
(job IN BINARY_INTEGER
,what IN VARCHAR2
,next_date IN VARCHAR2
,interval IN VARCHAR2 DEFAULT 'null'
,no_parse IN BOOLEAN DEFAULT FALSE);
PROCEDURE DBMS_JOB.SUBMIT
(job OUT BINARY_INTEGER
,what IN VARCHAR2
,next_date IN DATE DEFAULT SYSDATE
,interval IN VARCHAR2 DEFAULT 'null'
,no_parse IN BOOLEAN DEFAULT FALSE);

ORA-01461: can bind a LONG value only for insert into a LONG column error

Oracle 11g R1 RHEL 5 64bit (Apex 3.1)
Hi all,
I am having a tough time with this error:
ORA-01461: can bind a LONG value only for insert into a LONG column
ORA-06512: at "FPRCHR.PKG_TRIGGER_EMAIL", line 39
ORA-06512: at "ISWRNEW.PKG_NOTIFICATION", line 310
ORA-06512: at "ISWRNEW.PKG_NOTIFICATION", line 1745
ORA-06512: at line 1
The FPRCHR.PKG_TRIGGER_EMAIL looks like follows:
INSERT INTO fprchr.trigger_email
(trigger_email_rid,
email_to,
email_from,
email_body,
email_subject,
email_cc,
email_bcc,
mime_type,
email_priority
VALUES (l_job,
p_recipients,
p_sender,
p_message,
p_subject,
p_cc,
p_bcc,
p_mime_type,
p_priority
execute immediate 'alter session set events ''10046 trace name context off''';
END submit;
It seems like the characters have exceeded the limit that VARCHAR2 can handle? What other data type could I change the fprchr.trigger_email table to? Is that all that is needed?
Thanks.

It seems like the characters have exceeded the limit that VARCHAR2 can handle? What other data type could I change the fprchr.trigger_email table to? Is that all that is needed?
Did you try with clob data type?
Regards.
Satyaki De

Insert Record Via Dblink Get Error ORA-01461: can bind a LONG value only

Hi
When i try to insert record in Htmldb 2.0 Form to a table that is locate in remote DB via DBlink , I get the error ORA-01461: can bind a LONG value only for insert into a LONG column ORA-02063: preceding line from SAPREPOS.ADBAZAN.COM.
My command is insert into [email protected]
(OVED_ID,
REPMONTH,
REPYEAR,
SAPDATE,
SAPTIME)
values
(:P1_XOVED_ID,
:P1_XMANTHLY,
:P1_XYEAR,
to_char(sysdate,'DDMMYYYY'),
to_char(sysdate,'HH:MI AM'));
I try on local Table and it work OK.
I try with sqlplus to the remote DB and it works OK.
Need Help !!!
Thanks

Hi
When i try to insert record in Htmldb 2.0 Form to a table that is locate in remote DB via DBlink , I get the error ORA-01461: can bind a LONG value only for insert into a LONG column ORA-02063: preceding line from SAPREPOS.ADBAZAN.COM.
My command is insert into [email protected]
(OVED_ID,
REPMONTH,
REPYEAR,
SAPDATE,
SAPTIME)
values
(:P1_XOVED_ID,
:P1_XMANTHLY,
:P1_XYEAR,
to_char(sysdate,'DDMMYYYY'),
to_char(sysdate,'HH:MI AM'));
I try on local Table and it work OK.
I try with sqlplus to the remote DB and it works OK.
Need Help !!!
Thanks

ORA- 01461 : Can Bind a long value only for insert into a column error

I was trying to create a new job using dbms_job.isubmit
begin
sys.dbms_job.isubmit(job => 1111,
what => '',
next_date => to_date('21-10-2011 03:00:00', 'dd-mm-yyyy hh24:mi:ss'),
interval => 'TRUNC(SYSDATE+1)+3/24');
commit;
end;
However, I am getting the error 'ORA- 01461 : Can Bind a long value only for insert into a column error'.
I tried a lot but cant get rid of.
Any help gurus ?

You have an error in the code:
1. you don't provide a value for 'what' - you have to tell Oracle what it should execute when it submits the job.
And remember - with ISUBMIT the next_date parameter has datatype VARCHAR2 - SUBMIT uses datatype DATE. So make sure you provide a VARCHAR2 value and do not rely on implicit conversion.
>
PROCEDURE DBMS_JOB.ISUBMIT
(job IN BINARY_INTEGER
,what IN VARCHAR2
,next_date IN VARCHAR2
,interval IN VARCHAR2 DEFAULT 'null'
,no_parse IN BOOLEAN DEFAULT FALSE);
PROCEDURE DBMS_JOB.SUBMIT
(job OUT BINARY_INTEGER
,what IN VARCHAR2
,next_date IN DATE DEFAULT SYSDATE
,interval IN VARCHAR2 DEFAULT 'null'
,no_parse IN BOOLEAN DEFAULT FALSE);

APex 4.1 Error ORA-01461: can bind a LONG value only for insert into a LONG

Hi There,
Facing a strange issue.
I have a regular cursor, and in that cursor loop I have a select statement into some variables based on cursor parameters.
I was getting the "ORA-01461: can bind a LONG value only for insert into a LONG column" error so I started individually checking each of the columns. Now it works fine for some column, but the moment I add this number field. It starts throwing this error. Now, the database source where the select is fired is of type number, the variable into which I select it is number .
Infact, I dont have any LONG column defined anywhere.
The strange thing is that the block executes perfectly fine in SQl developer. So looks like a Apex specific issue.
I am on 4.1/11g
Any ideas?
Thanks,
Sun

sun1977 wrote:
Now, I have put this inside a Dynamic action (PL/SQL procedure). I think this PL/SQL procedure will go up to about 1500 to 2000 lines of code. There are no long columns involved anywhere or even CLOB, BLOB etc.
Is there any limitation to the size of code? When you say size of a code. Are you saying the whole PL/SQL block is stored in one Varchar2(4000) field? :) Did not know that. I am quite sure, the PL/SQL compiled package on the database would work perfect. Just was wondering why it was not working within APEX!
Also, Is there any documentation regarding this that you might be aware of?You can look at the APEX views. Code for some purposes (like region source) is stored in CLOBs:
desc apex_application_page_regions
Name                           Null     Type
WORKSPACE                      NOT NULL VARCHAR2(255 BYTE)
WORKSPACE_DISPLAY_NAME                  VARCHAR2(4000 BYTE)
APPLICATION_ID                 NOT NULL NUMBER
APPLICATION_NAME               NOT NULL VARCHAR2(255 BYTE)
PAGE_ID                        NOT NULL NUMBER
PAGE_NAME                      NOT NULL VARCHAR2(255 BYTE)
REGION_NAME                    NOT NULL VARCHAR2(255 BYTE)
PARENT_REGION_ID                        NUMBER
PARENT_REGION_NAME                      VARCHAR2(255 BYTE)
TEMPLATE                                VARCHAR2(255 BYTE)
TEMPLATE_ID                             NUMBER
STATIC_ID                               VARCHAR2(255 BYTE)
REST_ENABLED                            VARCHAR2(3 BYTE)
DISPLAY_SEQUENCE               NOT NULL NUMBER
DISPLAY_REGION_SELECTOR                 VARCHAR2(3 BYTE)
REGION_ATTRIBUTES_SUBSTITUTION          VARCHAR2(4000 BYTE)
ESCAPE_ON_HTTP_OUTPUT                   VARCHAR2(3 BYTE)
DISPLAY_COLUMN                          NUMBER
DISPLAY_POSITION                        VARCHAR2(255 BYTE)
DISPLAY_POSITION_CODE                   VARCHAR2(255 BYTE)
REGION_SOURCE                           CLOB
...for others—like LOV source and DA actions (PL/SQL code is stored in <tt>ATTRIBUTE_01</tt>)—are only VARCHAR2(4000 BYTE):
desc apex_application_page_da_acts
Name                        Null     Type
WORKSPACE                   NOT NULL VARCHAR2(255 BYTE)
WORKSPACE_DISPLAY_NAME               VARCHAR2(4000 BYTE)
APPLICATION_ID              NOT NULL NUMBER
APPLICATION_NAME            NOT NULL VARCHAR2(255 BYTE)
PAGE_ID                     NOT NULL NUMBER
PAGE_NAME                   NOT NULL VARCHAR2(255 BYTE)
DYNAMIC_ACTION_ID           NOT NULL NUMBER
DYNAMIC_ACTION_NAME         NOT NULL VARCHAR2(255 BYTE)
ACTION_NAME                          VARCHAR2(100 BYTE)
ACTION_CODE                 NOT NULL VARCHAR2(50 BYTE)
ACTION_SEQUENCE             NOT NULL NUMBER
DYNAMIC_ACTION_EVENT_RESULT          VARCHAR2(5 BYTE)
EXECUTE_ON_PAGE_INIT                 VARCHAR2(3 BYTE)
AFFECTED_ELEMENTS                    VARCHAR2(4000 BYTE)
AFFECTED_ELEMENTS_TYPE               VARCHAR2(30 BYTE)
AFFECTED_REGION                      VARCHAR2(255 BYTE)
AFFECTED_REGION_ID                   NUMBER
ATTRIBUTE_01                         VARCHAR2(4000 BYTE)
ATTRIBUTE_02                         VARCHAR2(4000 BYTE)
ATTRIBUTE_03                         VARCHAR2(4000 BYTE)
ATTRIBUTE_04                         VARCHAR2(4000 BYTE)
ATTRIBUTE_05                         VARCHAR2(4000 BYTE)
ATTRIBUTE_06                         VARCHAR2(4000 BYTE)
ATTRIBUTE_07                         VARCHAR2(4000 BYTE)
ATTRIBUTE_08                         VARCHAR2(4000 BYTE)
ATTRIBUTE_09                         VARCHAR2(4000 BYTE)
ATTRIBUTE_10                         VARCHAR2(4000 BYTE)
ATTRIBUTE_11                         VARCHAR2(4000 BYTE)
ATTRIBUTE_12                         VARCHAR2(4000 BYTE)
ATTRIBUTE_13                         VARCHAR2(4000 BYTE)
ATTRIBUTE_14                         VARCHAR2(4000 BYTE)
ATTRIBUTE_15                         VARCHAR2(4000 BYTE)
STOP_EXECUTION_ON_ERROR              VARCHAR2(3 BYTE)
LAST_UPDATED_BY                      VARCHAR2(255 BYTE)
LAST_UPDATED_ON                      DATE
COMPONENT_COMMENT                    VARCHAR2(4000 BYTE)
ACTION_ID                   NOT NULL NUMBER
COMPONENT_SIGNATURE                  CHAR(15 BYTE)       Oracle presmably have reasons for this difference but it's not something that is made clear in any way through the Builder UI.
Common sense should come into play. As Tony points out, the proper way to develop and deploy complex PL/SQL is using modular subprograms stored in packages. Same for APEX as for anything else.

Sql load error: ORA-01461: can bind a LONG value only for insert into a LON

I have 3 columns of varchar2(4000) in my table. I used char(4000) in my ctl. Please see below..
LOAD DATA
TRUNCATE INTO TABLE sa.sudhir_MARRIOTT_RBP_FORMAT
fields terminated by ' '
TRAILING NULLCOLS
TARGETING_SECTION,
TAG_TYPE,
NO_OFFER_SUPPRESS,
MAX_OFFER,
HTML_REGEX,
HTML_HEADER char(4000),
HTML_FOOTER char(4000),
RICH_TEXT_REGEX,
RICH_TEXT_HEADER,
RICH_TEXT_FOOTER,
TEXT_REGEX,
TEXT_HEADER,
TEXT_FOOTER
If I specify char(3000) for HTML_HEADER and char(1000) for HTML_FOOTER it works! (because at this moment html_header is less than 3000 and html_footer data is less than 1000). But I want to load 4000 characters max into both columns too. When I add , it fails with following error,
ORA-01461: can bind a LONG value only for insert into a LONG column
Please help !!
Sudhir

Anybody have any ideas?

Error ORA-01461: can bind a LONG value only for insert into a LONG column

Within an existing application , i need to create a new report , i created a new page in it and then tried to create classic report , during wizard when i enter the same query which i have used for previous page , it gives me following error during the creation of report.
The following bind variable i have already used for previous page. I want to reuse the same bind variables. There is no any long dataype within column predicates.
Error ORA-01461: can bind a LONG value only for insert into a LONG column
OK
Following is the query
SELECT
   "VWSR_ALL_MERGED_DATA_MV"."SR_AREA" "SR_AREA",
   "VWSR_ALL_MERGED_DATA_MV"."SR_STATUS" "SR_STATUS",
   "VWSR_ALL_MERGED_DATA_MV"."SR_SUB_STATUS" "SR_SUB_STATUS",
   "VWSR_ALL_MERGED_DATA_MV"."SR_DATE_CREATED" "SR_DATE_CREATED",
   "VWSR_ALL_MERGED_DATA_MV"."SR_OPEN_DATE" "SR_OPEN_DATE",
   "VWSR_ALL_MERGED_DATA_MV"."SR_CLOSED_DATE" "SR_CLOSED_DATE",
   "VWSR_ALL_MERGED_DATA_MV"."SR_PRODUCT1" "SR_PRODUCT1",
   "VWSR_ALL_MERGED_DATA_MV"."SR_PRODUCT2" "SR_PRODUCT2",
   "VWSR_ALL_MERGED_DATA_MV"."SR_TIO_PRIORITY" "SR_TIO_PRIORITY",
   "VWSR_ALL_MERGED_DATA_MV"."SR_REF_NUMBER" "SR_REF_NUMBER",
   "VWSR_ALL_MERGED_DATA_MV"."SR_DATE_RECD" "SR_DATE_RECD",
   "VWSR_ALL_MERGED_DATA_MV"."SR_CIDN" "SR_CIDN",
   "VWSR_ALL_MERGED_DATA_MV"."SR_BUS_UNIT" "SR_BUS_UNIT",
   "VWSR_ALL_MERGED_DATA_MV"."SR_NUMBER" "SR_NUMBER",
   "VWSR_ALL_MERGED_DATA_MV"."SOURCE_SYSTEM" "SOURCE_SYSTEM",
   "VWSR_ALL_MERGED_DATA_MV"."BATCH_ID" "BATCH_ID"
FROM VWSR_ALL_MERGED_DATA_MV
WHERE trunc(VWSR_ALL_MERGED_DATA_MV.SR_DATE_RECD)=trunc(sysdate-1)
AND VWSR_ALL_MERGED_DATA_MV.SR_TIO_PRIORITY IN
                                                :P2_SR_TIO_PRIORITY
                                               ,'CEO'
                                               ,'TER'
                                               ,'Priority Assistance'
                                               ,'Enquiry'
AND   (
        (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                                     'Business Support and Improvement'
                                   , 'Finance and Administration'
                                   , 'Cust Sat Simplification and Productivity'
                                   , 'Project New and Customer Experience'
                                   , 'Corp Strategy and Customer Experience'
                                   , 'Other'
            AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('BS&I'))
   OR   (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                                     'Consumer'
                                   , 'Consumer Telstra Country Wide'
                                   , 'Customer Service and Sales'
                                   , 'Offshore Sales and Service'
                                   , 'TC and TCW Operations'
                                   , 'Telstra Country Wide'
                                   , 'Other'
            AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('TC&C'))
   OR   (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                         'Telstra Customer Sales and Service'
                        ,'Telstra Program Office'
                        ,'Human Resources'
                        ,'IT'
                        ,'Unallocated'
                        ,'Other'
            AND :P2_SR_BUSINESS_UNIT= 'OTHER')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                    'Telstra Operations'
                   ,'Telstra Networks and Services'
                   ,'Other'
            AND :P2_SR_BUSINESS_UNIT= 'TO')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Telstra Business'
            AND :P2_SR_BUSINESS_UNIT= 'TB')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Telstra Wholesale'
            AND :P2_SR_BUSINESS_UNIT= 'TW')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Telstra Enterprise and Government'
            AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('TE&G'))
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Sensis'
                 ,'Sensis Pty Ltd'
            AND :P2_SR_BUSINESS_UNIT= 'SENSIS')
AND :P2_SR_TIO_PRIORITY = 'Level 0'
UNION
SELECT
   "VWSR_ALL_MERGED_DATA_MV"."SR_AREA" "SR_AREA",
   "VWSR_ALL_MERGED_DATA_MV"."SR_STATUS" "SR_STATUS",
   "VWSR_ALL_MERGED_DATA_MV"."SR_SUB_STATUS" "SR_SUB_STATUS",
   "VWSR_ALL_MERGED_DATA_MV"."SR_DATE_CREATED" "SR_DATE_CREATED",
   "VWSR_ALL_MERGED_DATA_MV"."SR_OPEN_DATE" "SR_OPEN_DATE",
   "VWSR_ALL_MERGED_DATA_MV"."SR_CLOSED_DATE" "SR_CLOSED_DATE",
   "VWSR_ALL_MERGED_DATA_MV"."SR_PRODUCT1" "SR_PRODUCT1",
   "VWSR_ALL_MERGED_DATA_MV"."SR_PRODUCT2" "SR_PRODUCT2",
   "VWSR_ALL_MERGED_DATA_MV"."SR_TIO_PRIORITY" "SR_TIO_PRIORITY",
   "VWSR_ALL_MERGED_DATA_MV"."SR_REF_NUMBER" "SR_REF_NUMBER",
   "VWSR_ALL_MERGED_DATA_MV"."SR_DATE_RECD" "SR_DATE_RECD",
   "VWSR_ALL_MERGED_DATA_MV"."SR_CIDN" "SR_CIDN",
   "VWSR_ALL_MERGED_DATA_MV"."SR_BUS_UNIT" "SR_BUS_UNIT",
   "VWSR_ALL_MERGED_DATA_MV"."SR_NUMBER" "SR_NUMBER",
   "VWSR_ALL_MERGED_DATA_MV"."SOURCE_SYSTEM" "SOURCE_SYSTEM",
   "VWSR_ALL_MERGED_DATA_MV"."BATCH_ID" "BATCH_ID"
FROM
   VWSR_ALL_MERGED_DATA_MV
WHERE trunc(VWSR_ALL_MERGED_DATA_MV.SR_DATE_RECD)=trunc(sysdate-1)
   and VWSR_ALL_MERGED_DATA_MV.SR_TIO_PRIORITY IN (:P2_SR_TIO_PRIORITY)
AND (
     (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN (
                     'Business Support and Improvement'
                   , 'Finance and Administration'
                   , 'Cust Sat Simplification and Productivity'
                   , 'Project New and Customer Experience'
                   , 'Corp Strategy and Customer Experience'
                   , 'Other'
AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('BS&I'))
OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN (
                     'Consumer'
                   , 'Consumer Telstra Country Wide'
                   , 'Customer Service and Sales'
                   , 'Offshore Sales and Service'
                   , 'TC and TCW Operations'
                   , 'Telstra Country Wide'
                   , 'Other')
AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('TC&C'))
OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                         'Telstra Customer Sales and Service'
                        ,'Telstra Program Office'
                        ,'Human Resources'
                        ,'IT'
                        ,'Unallocated'
                        ,'Other'
        AND :P2_SR_BUSINESS_UNIT= 'OTHER')
OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                      'Telstra Operations'
                      ,'Telstra Networks and Services'
                      ,'Other'
        AND :P2_SR_BUSINESS_UNIT= 'TO')
OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                     'Telstra Business'
        AND :P2_SR_BUSINESS_UNIT= 'TB')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Telstra Wholesale'
        AND :P2_SR_BUSINESS_UNIT= 'TW')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Telstra Enterprise and Government'
        AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('TE&G'))
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Sensis'
                 ,'Sensis Pty Ltd'
        AND :P2_SR_BUSINESS_UNIT= 'SENSIS')
AND :P2_SR_TIO_PRIORITY = 'Level 1'Edited by: user13653962 on 30/01/2013 15:11
Edited by: user13653962 on 30/01/2013 15:14

You have an error in the code:
1. you don't provide a value for 'what' - you have to tell Oracle what it should execute when it submits the job.
And remember - with ISUBMIT the next_date parameter has datatype VARCHAR2 - SUBMIT uses datatype DATE. So make sure you provide a VARCHAR2 value and do not rely on implicit conversion.
>
PROCEDURE DBMS_JOB.ISUBMIT
(job IN BINARY_INTEGER
,what IN VARCHAR2
,next_date IN VARCHAR2
,interval IN VARCHAR2 DEFAULT 'null'
,no_parse IN BOOLEAN DEFAULT FALSE);
PROCEDURE DBMS_JOB.SUBMIT
(job OUT BINARY_INTEGER
,what IN VARCHAR2
,next_date IN DATE DEFAULT SYSDATE
,interval IN VARCHAR2 DEFAULT 'null'
,no_parse IN BOOLEAN DEFAULT FALSE);

"ORA-01461: can bind a LONG value.." error during INSERT with abap exec

Hi,
I have a problem with sap ecc 6.0 with UNICODE.
I have:
DATA: BEGIN OF mytable OCCURS 0 ,
            my_var(4000),
           end OF mytable.
EXEC SQL.
    INSERT INTO TABLE@IFSAP
       (EVENT_CODE)
    VALUES
       (:TO_SINGLE_BYTE(:mytable-my_var))
ENDEXEC.
Help ME!

ORA-01461: can bind a LONG value only for insert into a LONG column
You can not insert a value which is of length more than 4000 into a LONG column of a table. But, you can get fetch the LONG column from the table and store it into a variable of type LONG. That is why you are getting the error.
Hope this helps... !

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.

Long Value Error

Similar Messages

Maybe you are looking for