Ora-01406

Lobs are often troublesome .
I have to fetch the concatenated result of few long varchar columns(all of them are of over 3888 bytes)  over a dblink from my staging schema . I have made a procedure to do this .
Similar to
create or replace function lob (par1 varchar2)return clob
as
l_clob  clob;
l_clob2 clob;
l_clob3 clob;
BEGIN
  select source_col1,source_col2,source_col3 into l_clob,l_clob2,l_clob3 from source_table_over_db_link where col1=par1;
return (lcob||l_cob2||l_clob3);
END;
when i simply call this function ,it works fine .i.e.
select lob('ABCC') from dual; Returns me result
But when i use this function inside another select statement as below
SELECT TO_CLOB(local_table.col1),to_clob(local_table.col2)||lob('ABCC') from local_table ;
I get the below ora error.
I get ORA-01406 .i.e. the fetched column value was truncated .
I am cluless ?  The version is 11.2.0.3.0 Production 64 bit Tns  for linus versio  11.2.0.3.0

OracleManiac,
This error is environment specific too and it also comes when we are using DB links. Which tool are you using?
If possible try it out from SQL*PLUS as well. If you are on TOAD, use this VIEW:OPTIONS:ORACLE:OCI buffer array size
You need to increase Buffer Array Size to fit your value.
Ishan

Similar Messages

  • ORA-01406 error encountered when using database link

    I am moving data between two different databases using a database link on Oracle 8.1.5. The database statement looks like:
    insert into TABLE@DATABASELINK
    (COLUMNS)
    select (COLUMNS) from TABLE
    One of the database columns is defined as varchar2(4000) on both the source and target database tables. When the data in this column on the source database is greater than 2000 characters, the database query generates the message:
    ORA-01406: fetched column value was truncated
    I have verified that the target column is defined as varchar2(4000), and have also verified that it is this varchar2(4000) column that is causing the problem. I have also tested out that this error only occurs when the varchar field is more than 2000 characters; if I remove characters so that the source field is less than or equal to 2000 characters, this error is no longer generated and the data is inserted to the target database table.
    Is this a limit with database links or some other database parameter that is not set up correctly?
    Thanks...Theresa Tucci

    Could you change the following entry in your 'sqlnet.ora' file and try?
    SQLNET.AUTHENTICATION_SERVICES = (NONE)

  • Regarding ORA-01406

    Hi,
    While executing a query we are getting this error ,
    ORA-01406: fetched column value was truncated
    ORA-01406: fetched column value was truncated
    We are getting this error for the first time. Please suggest us how to overcome it.
    The database is 10.2.0.1 on HP-UX B11.23

    Hi,
    We were using this below query when we got the error.
    SELECT
    LTRIM(RTRIM(STG_PI_EXTRACT.PC_NUM)),
    STG_PI_EXTRACT.PI_CREATED_DT,
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_ASSIGNED_TO)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_FILE_TYPE)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDR_DECISION)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDR_DECISION_MAKER)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDV_DECISION)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDV_DECISION_MAKER)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_PROCEDURE)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_EVENT_DESC)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_STATUS_CD)),
    LTRIM(RTRIM(STG_PI_EXTRACT.SR_SALES_REP_LOGIN)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_PROD_CODE)),
    LTRIM(RTRIM(STG_PI_EXTRACT.ACCOUNT_JJHCS_NUM)),
    REPLACE(STG_PI_EXTRACT.ACCOUNT_SITE,' ',''),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_LITIGATION_FLG)),
    LTRIM(RTRIM(STG_PI_EXTRACT.ASSET_SERIAL_NUM)),
    STG_PI_EXTRACT.PI_CLOSED_DT,
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_REASON_FOR_CLOSE)), STG_PI_EXTRACT.PI_INITIAL_REVIEW_DT, LTRIM(RTRIM(STG_PI_EXTRACT.PI_INITIAL_REVIEWER)),
    STG_PI_EXTRACT.PI_AGE,
    LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_ANALYSIS_SITE)), STG_PI_EXTRACT.PI_EXPIRATION_DATE, LTRIM(RTRIM(STG_PI_EXTRACT.PI_DISTRIBUTED_FLG)),
    STG_PI_EXTRACT.PI_QTY_INVOLVED, STG_PI_EXTRACT.PI_QTY_TO_BE_RETURNED, STG_PI_EXTRACT.PI_QTY_REPLACED,
    STG_PI_EXTRACT.PI_MFG_DT,
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_USEAGE_OF_DEVICE)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_LOANER_TYPE)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_WARRANTY_NAME)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_WARRANTY_DESC)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_WARRANTY_TYPE)),
    STG_PI_EXTRACT.PI_WARRANTY_END_DT, LTRIM(RTRIM(STG_PI_EXTRACT.PI_SOFTWARE_VERSION)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_HARDWARE_UPGRADE)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_FDA_REPORTABLE_FLG)), STG_PI_EXTRACT.PI_FDA_REPORT_DATE,
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_PROTOCOL_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_MODALITY)),
    STG_PI_EXTRACT.PI_ALERT_DT,
    STG_PI_EXTRACT.PI_RECEIVED_DT,
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_ROW_ID)),
    STG_PI_EXTRACT.PI_LAST_UPD_DT,
    LTRIM(RTRIM(STG_PI_EXTRACT.SR_PRIMARY_SR_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_EVENT_DAY)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_EVENT_OCCURED)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_CST_REF_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_DISP_SERIAL_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.ASSET_ASSET_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_AVAILABLE_CD)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_TT_RESULTS)),
    LTRIM(RTRIM(STG_PI_EXTRACT.CONTACT_SALES_REP)), LTRIM(RTRIM(STG_PI_EXTRACT.CONTACT_CUSTOMER_TYPE)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDR_OTHER)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_SUBMITTED_TO_AFFILIATE)), LTRIM(RTRIM(STG_PI_EXTRACT.MFG_SITE_NAME)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_FOREIGN_FLG)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_HEALTH_PROFESSIONAL_FLG)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_USER_FACILITY_FLG)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_REPRESENTATIVE_FLG)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_DISTRIBUTOR_FLG)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_A_NDA_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_IND_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_STN_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_501K_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_PRE_1938)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_OTC_PRODUCT)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_COMBINATION_PRODUCT)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_AE_TERMS)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_PERIODIC_FLG)), STG_PI_EXTRACT.PI_INITIAL_REPORT_DATE, STG_PI_EXTRACT.PI_FOLLOW_UP_DATE, STG_PI_EXTRACT.PI_FINAL_REPORT_DATE,
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_LOCK_ACCOUNT_NAME)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_CLOSED_BY)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_REPORTED_BY)),
    NVL(LTRIM(RTRIM(STG_PI_EXTRACT.ACCOUNT_ADDRESS_COUNTRY)),LTRIM(RTRIM(STG_PI_EXTRACT.ACCOUNT_ADDRESS_CITY))),
    PI_RR_TYPE_CD
    FROM
    STG_PI_EXTRACT
    --where UPPER(LTRIM(RTRIM(STG_PI_EXTRACT.PI_REASON_FOR_CLOSE))) <> 'VOID'
    Database driver error...
    Function Name : Fetch
    SQL Stmt : SELECT
    LTRIM(RTRIM(STG_PI_EXTRACT.PC_NUM)),
    STG_PI_EXTRACT.PI_CREATED_DT,
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_ASSIGNED_TO)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_FILE_TYPE)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDR_DECISION)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDR_DECISION_MAKER)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDV_DECISION)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDV_DECISION_MAKER)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_PROCEDURE)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_EVENT_DESC)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_STATUS_CD)),
    LTRIM(RTRIM(STG_PI_EXTRACT.SR_SALES_REP_LOGIN)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_PROD_CODE)),
    LTRIM(RTRIM(STG_PI_EXTRACT.ACCOUNT_JJHCS_NUM)),
    REPLACE(STG_PI_EXTRACT.ACCOUNT_SITE,' ',''),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_LITIGATION_FLG)),
    LTRIM(RTRIM(STG_PI_EXTRACT.ASSET_SERIAL_NUM)),
    STG_PI_EXTRACT.PI_CLOSED_DT,
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_REASON_FOR_CLOSE)), STG_PI_EXTRACT.PI_INITIAL_REVIEW_DT, LTRIM(RTRIM(STG_PI_EXTRACT.PI_INITIAL_REVIEWER)),
    STG_PI_EXTRACT.PI_AGE,
    LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_ANALYSIS_SITE)), STG_PI_EXTRACT.PI_EXPIRATION_DATE, LTRIM(RTRIM(STG_PI_EXTRACT.PI_DISTRIBUTED_FLG)),
    STG_PI_EXTRACT.PI_QTY_INVOLVED, STG_PI_EXTRACT.PI_QTY_TO_BE_RETURNED, STG_PI_EXTRACT.PI_QTY_REPLACED,
    STG_PI_EXTRACT.PI_MFG_DT,
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_USEAGE_OF_DEVICE)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_LOANER_TYPE)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_WARRANTY_NAME)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_WARRANTY_DESC)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_WARRANTY_TYPE)),
    STG_PI_EXTRACT.PI_WARRANTY_END_DT, LTRIM(RTRIM(STG_PI_EXTRACT.PI_SOFTWARE_VERSION)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_HARDWARE_UPGRADE)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_FDA_REPORTABLE_FLG)), STG_PI_EXTRACT.PI_FDA_REPORT_DATE,
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_PROTOCOL_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_MODALITY)),
    STG_PI_EXTRACT.PI_ALERT_DT,
    STG_PI_EXTRACT.PI_RECEIVED_DT,
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_ROW_ID)),
    STG_PI_EXTRACT.PI_LAST_UPD_DT,
    LTRIM(RTRIM(STG_PI_EXTRACT.SR_PRIMARY_SR_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_EVENT_DAY)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_EVENT_OCCURED)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_CST_REF_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_DISP_SERIAL_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.ASSET_ASSET_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_AVAILABLE_CD)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_TT_RESULTS)),
    LTRIM(RTRIM(STG_PI_EXTRACT.CONTACT_SALES_REP)), LTRIM(RTRIM(STG_PI_EXTRACT.CONTACT_CUSTOMER_TYPE)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_MDR_OTHER)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_SUBMITTED_TO_AFFILIATE)), LTRIM(RTRIM(STG_PI_EXTRACT.MFG_SITE_NAME)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_FOREIGN_FLG)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_HEALTH_PROFESSIONAL_FLG)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_USER_FACILITY_FLG)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_REPRESENTATIVE_FLG)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_DISTRIBUTOR_FLG)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_A_NDA_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_IND_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_STN_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_501K_NUM)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_PRE_1938)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PRODUCT_OTC_PRODUCT)), LTRIM(RTRIM(STG_PI_EXTRACT.PI_COMBINATION_PRODUCT)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_AE_TERMS)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_PERIODIC_FLG)), STG_PI_EXTRACT.PI_INITIAL_REPORT_DATE, STG_PI_EXTRACT.PI_FOLLOW_UP_DATE, STG_PI_EXTRACT.PI_FINAL_REPORT_DATE,
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_LOCK_ACCOUNT_NAME)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_CLOSED_BY)),
    LTRIM(RTRIM(STG_PI_EXTRACT.PI_REPORTED_BY)),
    NVL(LTRIM(RTRIM(STG_PI_EXTRACT.ACCOUNT_ADDRESS_COUNTRY)),LTRIM(RTRIM(STG_PI_EXTRACT.ACCOUNT_ADDRESS_CITY))),
    PI_RR_TYPE_CD
    FROM
    STG_PI_EXTRACT
    --where UPPER(LTRIM(RTRIM(STG_PI_EXTRACT.PI_REASON_FOR_CLOSE))) <> 'VOID']

  • ORA-00604   ;  ORA-01406

    Hi all,
    11.2.0.3
    I am dropping a user with QUEUE objects but I got error
    SQL> /
    drop user Q_ADMIN
    ERROR at line 1:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-01406: fetched column value was truncated
    Please help...
    Thanks,
    pK

    No help is required.
    Your posting history shows you have a general inability to Google anything before asking a question and basically you expect this forum to that for you.
    I just Googled for 'drop user with queue objects' and got some responses that looked valid, I also noticed this topic has discussed earlier in this forum.
    Every single question you have asked here is abuse of this forum!
    I would love to see moderators taking appropriate action and remove your account.
    Yes, I am quite aware you will create a new account, and you will continue to abuse this forum.
    However, people like you have to be stopped somewhere.
    I will also address, again, your posting history in the community feedback forum.
    Sybrand Bakker
    Senior Oracle DBA

  • Help Needed: Facing the error ORA-01406: fetched column value was truncated

    Hi Everyone,
    When I run a particular PL/SQL query using Oracle 9i ODBC driver, it is working fine and fetching me the desired results.
    However, when I run the same query using the Oracle 10g ODBC driver, I am getting the error: ORA-01406: fetched column value was truncated.
    I have checked all the fields of the table and they are well within the allowable limit.
    Can you please let us know what needs to be done to resolve this issue?
    Thanks and Regards,
    Sudhindra

    Well it's obviously a problem with the client software. Doesn't Datastage have some way of configuring these things?
    rgds, APC

  • Weird ORA-01406: fetched column value was truncated error for SELECT query

    DB version:10gR2
    When one of our application fires the below query, we get
    ORA-01406: fetched column value was truncatederror.
    select     trk_dtl,
         trk_type,
         trk_id,
         trk_desc,
    from     shp_dtl
    where     shp_type = 'HN'
    and     shp_type = 828;The documentation says
    Cause:In a host language program, a FETCH operation was forced to truncate a character string. The program buffer area for this column was not large enough to contain the entire string. The cursor return code from the fetch was +3.But when the application is pointed to an identical schema in the same instance, we don't get this error. So, this has got nothing to do client application as the documentation says.
    Any idea what other possibilities are there?

    Post description of shp_dtl.

  • How to resolve ORA-01406: fetched column value was truncated

    I tried to export with the parameter full=yes....when i did tat i ma gettin ORA-01406: fetched column value was truncated error...
    the following gives the sequence
    About to export the entire database ...
    . exporting tablespace definitions
    . exporting profiles
    . exporting user definitions
    . exporting roles
    EXP-00008: ORACLE error 1406 encountered
    ORA-01406: fetched column value was truncated
    EXP-00000: Export terminated unsuccessfully
    pls revert back with an answer....

    http://www.orafaq.com/forum/t/145219/2/

  • ORA-01406: fetched column value was truncated

    When I execute a query, this erro appear.
    What this error means?
    Thanks.

    Hi,
    A buffer area in your program is too small. Try to increase it.
    hth
    Paolo

  • While doing a export I am having the following error:ORA-1406....

    EXP-00008: ORACLE error 1406 encountered
    ORA-01406: fetched column value was truncated
    EXP-00000: Export terminated unsuccessfully
    We have:
    Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bi
    PL/SQL Release 10.2.0.2.0 - Production
    CORE 10.2.0.2.0 Production
    TNS for HPUX: Version 10.2.0.2.0 - Production
    NLSRTL Version 10.2.0.2.0 - Production

    Hi,
    See if the Note:367831.1 from Oracle Metalink can help you
    Cheers
    @Manesh
    Sorry for duplicate, I don't refresh the page before posting ...
    Message was edited by:
    Legatti

  • Oracle 11g 逻辑备份

    做11.2.0.2全备包括逻辑备份和rman备份,备份机上的版本是10.2.0.3 操作系统windows server 2003;目标数据库是11.2.0.2,操作系统是linux ;现在有两种方案:
    一是直接在备份机上调用exp连接到目标数据库做全备,但是这个方案目前还行不通,报错:
    EXP-00008:遇到 ORACLE错误1406
    ORA-01406:提取的列值被截断
    EXP-00000:导出终止失败
    这个方案本身是否可行,用10.2.0.3导出后以后做数据恢复再导入11.2.0.2是否有问题,如果没有问题,那以上报错能怎么解决?
    二是在备份机上再装一个11.2.0.1的客户端(备份机上已经有一个10.2.0.3的服务器端):
    这个方案存在两个问题,一是用11.2.0.1做exp报错 :
    EXP-00003: 未找到段 (0,0) 的存储定义
    . . 正在导出表 CWM$CLASSIFICATION导出了 41 行
    . . 正在导出表 CWM$CLASSIFICATIONENTRY导出了 5 行
    . . 正在导出表 CWM$CLASSIFICATIONTYPE导出了 15 行
    EXP-00107: 不支持特征 (BINARY XML) (属于列 XSLT, 表 ORDDATA.ORDDCM_MAPPING_DOCS_TMP)。不会导出该表。
    二是在备份机上安装11.2.0.2是否会影响原本10.2.0.3下的实例运行,请大神指教。

    兄弟 如果要跨平台恐怕只能exp/imp

  • Length of "out char" parameter in stored procedure

    I call a SP with an output char parameter, the type is defined as a field in a table -- char(3),
    but when calling from stored procedure, it throws an exception:
    "ORA-01406: fetched column value was truncated"
    the exception happens in line 4:
    1. stmt->setSQL("call OUTPUT_CHAR1(:1)");
    2. stmt->registerOutParam(1, OCCISTRING, 10);          
    3. stmt->execute();
    4. string result = stmt->getString(1);
    One interesting thing is: if I use the same type as function return value(not output parameter), it works.
    Friends, please give me some idea..

    Just before commending about anyone it is good idea to go through Oracle Documentation .
    Go through the following link
    http://www.orafaq.com/faq/what_is_the_difference_between_varchar_varchar2_and_char_data_types
    and
    http://ora-01406.ora-code.com/ also
    Basic difference is CHAR is fixed length and VARCHAR2 variable length which takes more buffer than a fixed length since the length is also stored.
    Your error 'ORA-01406' is a common one in any place holder which does not have space to hold enough data. Thats why I told you to change to Varchar2 which is common fix in this case where exact data is not send to client unlike CHAR.
    It is good that you are rude to me , so that I learned a lesson not help others much.
    If you think the above explanation is also wrong , there are other experts in this forum , they will comment and not you alone

  • DB upgrade error

    Hi,
    I have a wierd problem.
    I had ERP04 on Oracle 9.2.0.6. We are going to ERP05
    So i was upgrading my DB to 10.2.0.2
    I had completed all the prerequisites, installed 10.0.0.1 and upgraded to patch 10.0.0.2 according to DB upgrade guide.
    I was running DBUA, it was upgrading and was around 10-12% complete.
    Then suddenly network broke for a min or 2. And DBUA screen went off.
    When I am starting to restart DBUA, it is working.
    I changed again name back to my old DB in /etc/oratab.
    Old DB is getting mounted but not getting opened.
    My trace file under /oracle/RD1/saptrace/usertrace gives the below listed error
    ORA-00704: bootstrap process failure
    ORA-00604: error occurred at recursive SQL level 1
    ORA-01406: fetched column value was truncated
    And alert log files says that there was an error shown in trace file above.
    Is there anything i can do to solve this?
    Regards,
    Tajinder

    Hello Tajinder,
    > Is there anything i can do to solve this?
    Unfortunately not. This problem is described in metalink note #427585.1.
    Solution: Restore a cold backup of the database from before the upgrade attempt was made and then reaccomplish the upgrade
    I had this issue once. Also restored the database and restarted.
    Regards
    Stefan

  • Example Error: Search Form

    Hi every one,
    I use this sample in
    http://otn.oracle.com/sample_code/products/jdev/jsp/SearchSample.zip
    But I met error:
    1. Application Error
    Return
    Error Message: JBO-27122: SQL error during statement preparation. Statement: SELECT ProductInformation.PRODUCT_ID, ProductInformation.PRODUCT_NAME, ProductInformation.PRODUCT_DESCRIPTION, ProductInformation.CATEGORY_ID, ProductInformation.WEIGHT_CLASS, ProductInformation.WARRANTY_PERIOD, ProductInformation.SUPPLIER_ID, ProductInformation.PRODUCT_STATUS, ProductInformation.LIST_PRICE, ProductInformation.MIN_PRICE, ProductInformation.CATALOG_URL FROM PRODUCT_INFORMATION ProductInformation WHERE ( ( (ProductInformation.CATALOG_URL like '%%') ) )
    Error Message: ORA-00932: inconsistent datatypes: expected NUMBER got INTERVAL
    oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation. Statement: SELECT ProductInformation.PRODUCT_ID, ProductInformation.PRODUCT_NAME, ProductInformation.PRODUCT_DESCRIPTION, ProductInformation.CATEGORY_ID, ProductInformation.WEIGHT_CLASS, ProductInformation.WARRANTY_PERIOD, ProductInformation.SUPPLIER_ID, ProductInformation.PRODUCT_STATUS, ProductInformation.LIST_PRICE, ProductInformation.MIN_PRICE, ProductInformation.CATALOG_URL FROM PRODUCT_INFORMATION ProductInformation WHERE ( ( (ProductInformation.CATALOG_URL like '%%') ) )
         at oracle.jbo.server.QueryCollection.buildResultSet(QueryCollection.java:760)
         at oracle.jbo.server.QueryCollection.executeQuery(QueryCollection.java:521)
         at oracle.jbo.server.ViewObjectImpl.executeQueryForCollection(ViewObjectImpl.java:3200)
         at oracle.jbo.server.ViewRowSetImpl.execute(ViewRowSetImpl.java:597)
         at oracle.jbo.server.ViewRowSetImpl.executeQueryForMasters(ViewRowSetImpl.java:700)
         at oracle.jbo.server.ViewRowSetImpl.executeQuery(ViewRowSetImpl.java:638)
         at oracle.jbo.server.ViewObjectImpl.executeQuery(ViewObjectImpl.java:3145)
         at oracle.jbo.html.jsp.datatags.ViewCriteriaTag.doEndTag(ViewCriteriaTag.java:88)
         at ProductInformationView_Browse._jspService(ProductInformationView_Browse.jsp:73)
         at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:139)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:349)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
         at oracle.security.jazn.oc4j.JAZNFilter.doFilter(Unknown Source)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:604)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
         at java.lang.Thread.run(Thread.java:534)
    ## Detail 0 ##
    java.sql.SQLException: ORA-00932: inconsistent datatypes: expected NUMBER got INTERVAL
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:189)
         at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:242)
         at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:554)
         at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1478)
         at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:888)
         at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2346)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2660)
         at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:457)
         at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:387)
         at oracle.jbo.server.QueryCollection.buildResultSet(QueryCollection.java:665)
         at oracle.jbo.server.QueryCollection.executeQuery(QueryCollection.java:521)
         at oracle.jbo.server.ViewObjectImpl.executeQueryForCollection(ViewObjectImpl.java:3200)
         at oracle.jbo.server.ViewRowSetImpl.execute(ViewRowSetImpl.java:597)
         at oracle.jbo.server.ViewRowSetImpl.executeQueryForMasters(ViewRowSetImpl.java:700)
         at oracle.jbo.server.ViewRowSetImpl.executeQuery(ViewRowSetImpl.java:638)
         at oracle.jbo.server.ViewObjectImpl.executeQuery(ViewObjectImpl.java:3145)
         at oracle.jbo.html.jsp.datatags.ViewCriteriaTag.doEndTag(ViewCriteriaTag.java:88)
         at ProductInformationView_Browse._jspService(ProductInformationView_Browse.jsp:73)
         at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:139)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:349)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
         at oracle.security.jazn.oc4j.JAZNFilter.doFilter(Unknown Source)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:604)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
         at java.lang.Thread.run(Thread.java:534)
    2. This error raised because a query:
    SELECT ProductInformation.PRODUCT_ID, ProductInformation.PRODUCT_NAME, ProductInformation.PRODUCT_DESCRIPTION, ProductInformation.CATEGORY_ID, ProductInformation.WEIGHT_CLASS, ProductInformation.WARRANTY_PERIOD, ProductInformation.SUPPLIER_ID, ProductInformation.PRODUCT_STATUS, ProductInformation.LIST_PRICE, ProductInformation.MIN_PRICE, ProductInformation.CATALOG_URL FROM PRODUCT_INFORMATION ProductInformation WHERE ( ( (ProductInformation.CATALOG_URL like '%%') ) )
    ORA-01406: fetched column value was truncated
    (WARRANTY_PERIOD)
    Could you help me?
    Thanks in advanced,
    Nguyen Hung Linh.

    Hi,
    The error may be related to some special data in the customer DB. Would you please check if you are using any stored procedure.
    Regards
    Vikas
    SAP Business One Product Support

  • Data pump export with error

    Hi All,
    I am new to DBA and when I run expdp for the full database,I am getting the below error
    " ORA-39139: Data Pump does not support XMLSchema objects. TABLE_DATA:"APPS"."abc_TAB" will be skipped.
    I am facing issue with exp utility,so I have to use expdp.
    Kindly help me to avoid these errors.
    Thank,

    Thanks Srini for the Doc - A good one.
    We have scheduled a daily full export backup. Now this is having problems.
    -> exp expuser/exppaswd file=/ora/exp.dmp log=/ora/exp.log direct=Y statistics=none full=Y
    error=
    Table window348_TAB will be exported in conventional path.
    . . exporting table window348_TAB 0 rows exported
    Table wtpParameters350_TAB will be exported in conventional path.
    . . exporting table wtpParameters350_TAB 0 rows exported
    . exporting synonyms
    EXP-00008: ORACLE error 1406 encountered
    ORA-01406: fetched column value was truncated
    EXP-00000: Export terminated unsuccessfully
    Oracle requested to drop/disable the policy. But one policy assigned to many tables and one table having more than one policies.
    We haven't set any policy, all are default one.
    1. If I disable/drop policies how it will affect the application?
    2. How I can disable or drop it for all the objects in the database?
    3. How I can identify the policies - whether OLS or VPD
    Pelase help me to get a daily full export backup or any alternate solution for the same.
    Thanks,
    Asim

  • What is Column Buffer area?

    What on earth is Column Buffer area? How do i increase it?
    While issuing a simple SELECT query i received the error ORA-01406 fetched column value was truncated . It is a 9i Error. The solution for this mentioned in documentations is : Action: Increase the column buffer area to hold the largest column value or perform other appropriate processing .
    The weird thing is , this query works on our sample database, Oracle version 9.2.0.5.0 . But it doesn't work in our client site on the same version (9.2.0.5.0) .
    Any thoughts?

    I have an SQR that reads a CLOB field. I had one value returned that was > 12,000 bytes.
    Apparently, the SQR db drivers can't handle an entire CLOB as a single column in a select statement. The trick is to break up the CLOB into chunks of 12,000 KB columns and combine them later in order for the SQR to handle it.
    begin-select
    clobfield
    let $myclob = &clobfield
    show $myclob
    end-select
    The above SQL would return an error:
    (SQR 5528) ORACLE OCIStmtFetch error 1406 in cursor 18:
    ORA-01406: fetched column value was truncated
    Error on line 67:
    (SQR 3725) Bad return fetching row from database.
    To avoid this error, I used the following:
    begin-select
    substr(clobfield, 0, 12000) &clobfield1
    substr(clobfield, 12000, 24000) &clobfield2
    !Add more if your data will be > 24000 bytes
    let $myclob = &clobfield1 || &clobfield2
    show $myclob
    end-select

Maybe you are looking for

  • Creative Zen Sl

    i bought a zen sleek in august last year, since then I've had two replacements. The first player gathered so much dust between the screen cover and the LCD screen that it obscured the menu, the second player had the wrong firmware and was incompatibl

  • Will Not Boot from Install Disc  & 4SNS/1/40000000: TG0D - Thermal Sensor?

    *Will Not Boot from Install Disc* I used the "option key" approach with the gray start up disk. At first it ejected the start up disk. Then I nudged the disk back in the machine and it showed on the screen as an option. I clicked on the start up disk

  • Header Condition Records for Promotions

    Hi, I have created a sales deal with a promotion with say X payment terms and customer/material promotional discounts. The issue is that the while order is created deal is being picked up at the item level for material price conditions. i.e. it shows

  • Is "SET TRANSACTION USE ROLLBACK SEGMENT" only a hint

    I have two users, one makes some inserts in a table. The other makes a select which visits many rows. I have a big rollback-segment. To ensure, both users use this rollback-segment I created a logon-trigger: CREATE OR REPLACE TRIGGER a_logon AFTER LO

  • Problem in configuring windows in FPM

    Need Suggestions to configure windows with message types with FPM