ERROR-400|ORA-01461

Hi
I have Oracle Enterprise Manager 10g Release 10.2.0.1.0 installed.
When i try to upload my agent i get the following message:
$ ./emctl upload agent
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
EMD upload error: Failed to upload file B0000315.xml, ret = -2
I know i have hit bug 5868789... is there any solution for this or a workaround to start my EM agent, as the status in EM console is AGENT UNREACHABLE.
Vikram

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]

Similar Messages

  • 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]

  • ERROR-400|ORA-01801:date format is too long for internal buffer on "upload"

    2006-06-23 16:23:39 Thread-2849151920 ERROR upload: Failed to upload file B0000001.xml, ret = -2
    2006-06-23 16:23:39 Thread-2849151920 ERROR upload: 3 Failures in a row for B0000001.xml, we give up
    2006-06-23 16:23:39 Thread-2849151920 ERROR upload: Error in uploadXMLFiles.  Trying again in 900.00 seconds or earlier.Ok, foolish me - I ran Redhat update and got a new kernel, libs etc. and basically got my OS current. But now OEM can't do uploads??
    I get the above errors and NOTHING on OEM has changed. I suspect a timezone issue; emd.properties sets the timezone to "US/Eastern" ... and has been like that ever since.
    Metalink doesn't mention this issue at all?
    I've done a clear-state; but that didn't fix the issue.
    Any ideas?
    Platform: RHES4 - OEM version 10.2.0.1 (straight out of the box).

    From emoms.trc:
    2006-06-23 16:06:59,893 [SeverityLoad https://oem.e-hms.net:3872/emd/main/] ERROR eml.XMLLoader markFileAsError.882
    - Failed to load B0000000001.xml because of errors; moving to errors directory. Error:
    ERROR-400|ORA-01861: literal does not match format string
            at oracle.sysman.emdrep.receiver.FxferRecv.DirectLoad(FxferRecv.java:1046)
            at oracle.sysman.emdrep.receiver.FxferRecv.loadSeverities(FxferRecv.java:1134)
            at oracle.sysman.emdrep.receiver.FxferRecv.receiveFile(FxferRecv.java:1609)
            at oracle.sysman.emdrep.receiver.FxferRecv.doPost(FxferRecv.java:764)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
            at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:336)
            at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
            at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
            at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
            at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
            at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
            at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186
            at java.lang.Thread.run(Thread.java:534)
    Caused by: java.sql.SQLException: ORA-01861: literal does not match format string
            at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
            at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:304)
            at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:271)
            at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:625)
            at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:184)
            at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:632)
            at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1162)
            at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2932)
            at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3004)
            at oracle.sysman.util.jdbc.PreparedStatementWrapper.executeUpdate(PreparedStatementWrapper.java:723)
            at oracle.sysman.emdrep.dbjava.loader.MultiTableInsertHandler.handleRow(MultiTableInsertHandler.java:277)
            at oracle.sysman.emdrep.dbjava.loader.XMLLoaderContext.handleSubDocument(XMLLoaderContext.java:1863)
            at oracle.sysman.emdrep.dbjava.loader.XMLDocumentSplitter.endElement(XMLDocumentSplitter.java:876)
            at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1257)
            at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:314)
            at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:281)
            at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:196)
            at oracle.sysman.emdrep.dbjava.loader.XMLDocumentSplitter.split(XMLDocumentSplitter.java:451)
            at oracle.sysman.emdrep.dbjava.loader.XMLLoaderContext.loadFromStream(XMLLoaderContext.java:1672)

  • 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);

  • Gettin ORA-01461 error in informatica level

    Hi All
    Iam getting following error at informatica level.
    WRT_8229 : Database errors occurred:
    ORA-01461: can bind a LONG value only for insert into a LONG column
    But we dont have any column with LONG datatype. only we have varchar2 datatype and date. its direct loading from source to target.
    could you please provide me the solution
    thanks
    LNR

    Looks like a bug..check metalink note 728074.1
    Pls mark correct/helpful...

  • Ora-01461

    Hi,
    I am working in oracle 10g. i am inserting the records in a table from the appliaction(Java application). In that i am getting an error as
    ORA-01461 .
    DB - 10.2.0.1.0 (i am using LONG datatype for the column)
    Kindly provide me a solution for this.
    Rgds...

    ORA-01461:     can bind a LONG value only for insert into a LONG column
    Cause:     An attempt was made to insert a value from a LONG datatype into another datatype. This is not allowed.
    Action:     Do not try to insert LONG datatypes into other types of columns.
    As you say you are using LONG data type for the column, could you post the exact INSERT statement that is generated (of course, I am not looking for values here)?
    Is your INSERT formed without a column list (like INSERT INTO TABLE VALUES (...) instead of INSERT INTO TABLE (col1, col2...) VALUES (....))? This could be the reason as columns won't match as expected.

  • Error ORA-01460 warning ORA-01461 during running a mapping with parameters

    Oracle 10g release2(10.2.0.1.0), OWB 10.2.0.1.31, Workflow server 2.6.4
    I have a simple process flow ( start -> mapping -> end).
    The mapping consists of 4 input groups(3 ordinary tables<INGRP1, INGRP2, INGRP3> and 1 mapping input parameter operator <INGRP4>), a joiner, a filter, an expression operator and 1 output group.
    I want to use two variables in join condition, so I bound two mapping input parameters(<INGRP4.SRC_SYS_CDE> and <INGRP4.ADMIN_ORG_NUM>) with two parameters of the process flow's start activity.
    Those two mapping input parameters are of type char, one is 4-char long and the other is 2-char long. So I set both of the two parameters of the start activity as String, one as 08, another as 7504.
    My join condition is:
    INGRP1.ORGIDT = INGRP2.SOURCEORGANIZATIONNO AND
    INGRP2.SOURCESYSTEMCODE = INGRP4.SRC_SYS_CDE AND
    INGRP2.ADMINORGANIZATIONNO = INGRP4.ADMIN_ORG_NUM AND
    INGRP1.CURCDE = INGRP3.NUM(+)
    There are no errors and warnings in validation, generation and deployment process, but when I run the process flow, it always finishes blankly(zero insert) with no error and warning messages. It should insert more than 20,000 rows.
    When I run the mapping and set the parameters 08 and 7504 at the parameter prompt, then start, the following error and warning occurs.
    Error ORA-01460: unimplemented or unreasonable conversion requested
    Warning ORA-01461: can bind a LONG value only for insert into a LONG column
    So what's the problem? How can I fix it?

    The problem was mapping input parameter type.
    VARCHAR2-type mapping input parameter works with String-type PF parameter. But CHAR-type won't.

  • ORA-01461 error

    Hi, all
    I am loading data in csv format into the Oracle 9i table. I can proceed with one a few lines, but end up with "ORA-01461 can bind a LONG value only for insert into a LONG column" error message. When I uncomment the setSQL call in earch loop, I got my job done with no complain. I wonder is there something wrong with my source code, or repeatedly bind and execute on a prepared statement are just disallowed.
    The csv data is something like:
    4409020,xxxxxx,6578B,,
    9901400,xxxxx,11CBM,,
    4447130,xxxx,6578H,,
    And the C++ source:
    PFile file("data.csv");
    int colCount = 5;
    int colTypes[] = {
         occi::OCCI_SQLT_CHR,
         occi::OCCI_SQLT_CHR,
         occi::OCCI_SQLT_CHR,
         occi::OCCI_SQLT_CHR,
         occi::OCCI_SQLT_NUM
    int count = 0;
    PString line;
    PStringArray fields;
    // prepare
    stmt->setSQL("INSERT INTO m_pckk_hatyu VALUES (:1,:2,:3,:4,:5)");
    while (file.ReadLine(line)) {
         //stmt->setSQL((const char *)sql);
         fields = line.Tokenise(",", TRUE);
         csvColCount = fields.GetSize();
         if (colCount != csvColCount) {
              cout << "Skip line " << (count+1) << ": " << line << endl;
              continue;
         // bind
         for (int j=0; j<colCount; j++) {
              if (colTypes[j] == occi::OCCI_SQLT_NUM) {                         // number
                   stmt->setNumber(j+1, occi::Number(fields[j].AsReal()));
              } else if (colTypes[j] == occi::OCCI_SQLT_CHR) {               // varchar2
                   stmt->setString(j+1, (const char *)fields[j]);
         // execute
         count += stmt->executeUpdate();

    When you are dealing with long varchars, try using the stmt->setMaxParamSize(index, maxSize) API. i beleive oracle has some predefined optimized sizes for the bind variables. Here the index is the index of the bind variable and the maxSize is the size of the varchar.

  • ORA-01461 error using jdbc 10.2.0.1.0

    I am using the oracle jdbc 10.2.0.1.0 ( the latest version) and oracle 10g (10.1.0.4.0) database. Sometimes, the error "ORA-01461: can bind a LONG value only for insert into a LONG column' if I use a java program to insert record to a table containing a 'long raw' field. Previously, the same java program work well with oracle 9i.
    Interestingly, the 'ORA-01461' only SOMETIMES happen. If the problem appears, I need to rename the table and create a new one and then the data can be inserted.

    After 3 days of deep analysis on my project, now I have a clear idea of the problem.
    As you can find on web, newer versions of Oracle drivers for Java have the possibility to set property :
    oracle.jdbc.RetainV9LongBindBehavior=true
    it's considered the fix for this bug, and effectively it seems to work.
    But also with this setting, drivers have one more bug!+
    The problem appears in these conditions:
    - Application tries to save a string into a LONG column database
    - String length is more than 4000 bytes
    - String has less than 4000 characters (it's possible in case of international characters, which takes more than 1 byte)
    With these conditions, we have again error ORA-01461: can bind a LONG value only for insert into a LONG column.
    It seems that drivers evaluate string length before saving it, and consider it as LONG only for 4000+ characters. The bug is just on this check, that must consider length in bytes, according to database character encoding, and not simply for character length.
    As workaround, on my application we added a logic that appends spaces (" ") until total characters are at least 4001. In this way, string is considered correctly as LONG and storage works correctly.
    The check is something similar to this:
    if(value.getBytes("UTF-8").length > 4000 && value.length() < 4000)
    for(int x = value.length(); x<=4000; x++)
    value += " "; // always use StringBuffer for appending
    This workaround works, but it's clear that it can be not acceptable in many cases, for application funcionalities. In my specific bug, it has been very useful.
    My customer opened a ticket to Oracle, asking for solution of this bug. I will wait for Oracle answer.
    Finally, we have to say that Oracle warned to not use anymore LONG datatype: it's deprecated since v8.0.
    Bye guys ;-)
    Edited by: user12274810 on 25-nov-2009 12.04

  • ORA-01461 error occurs

    Hi All.
    I'm using WLS6.1 on Soralis8.
    I try to use jdbc to store persistance
    sessions,but An ORA-01461 error occurs
    while the server is trying to write the
    session data in the JDBC managed
    persistence when using the Oracle thin
    Driver.
    How should I fix the problem?

    You should open a support case and request patch CR083912_610sp1.jar if you are
    seeing the exception below
    ORA-01461 error occurs while the server try to write the session data in the JDBC
    managed persistence (using Oracle thin Dricer).
    Configuration:
    WLS 6.1 SP1
    Oracle Server: 8.1.7.3
    Oracle thin driver and JDK come with WLS
    Error : This error comes to the server command line window when I first hit
    the jsp page.
    Error Details :
    java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into
    a LONG column
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
    at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
    at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)

  • 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&mdash;like LOV source and DA actions (PL/SQL code is stored in <tt>ATTRIBUTE_01</tt>)&mdash;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?

Maybe you are looking for

  • How to Get a Photoshop CS2 Legally?

    Call it a bit old school (very old)... but In our workplace, we really needed the Photoshop CS2 especially the photomerge function. Since CS3 to newer model, the Photoshop Merge does not work well with our need. It tries to merge automatically... whi

  • How can you make an smart playlist that uses another smart playlist when I can't see them all

    My whole family uses itunes.  I want to make a playlist that uses other playlist.  However, when I start a smart playlist and click playlist is I get a dropdown menue that doesn't show all my playlists.  My wife's name happens to start with a V so al

  • Do I need Adobe pro to use ensign?

    Had to wipe my hard drive, can't find ensign.

  • SLD Transport

    I would like to transport all the Product, Software Component , Technical System and Business System Information from DEV to Production SLD. The plan is to make the Production SLD, the only SLD in future. I am thinkin of going to SLD Administration ,

  • Magic mouse delay in scrolling

    When I scroll through pages in pdf documents, there is a definite response delay, which is very annoying. Any ideas on how to fix this?