SSIS OLE DB Data Source: literal does not match format string

Dear All,
this is my first post on this forum, so sorry if I choose wrong category for this question, but I stuck...
I'm using SSIS from SQL Server 2k8 R2 in Windows Server 2k8 R2. I have installed Oracle Client 10.2.0.2 32 bits and Oracle Client 10.2.0.4 64bits. I want to connect to Oracle 8i and Oracle 9i by these clients.
Unfortunately when I want to see a preview, only error occurs to me:
ORA-01861: literal does not match format string (OraOLEDB)
I have read a lot about this issue but nothing helps me (to_date, cast, convert etc.).
This is query which I use:
SELECT COMPANYID, TRANSACTIONTYPE, TRANSACTIONDATE,
PRODUCT, PRODUCTIONSITE, BATCHNUMBER,
BINNUMBER, QUANTITYSTOCKUNIT, QUANTITY,
UNITOFMEASURE, TRANSACTIONCURRENCYID, COST
FROM APPS.DW_PRODUCTION
WHERE TRANSACTIONDATE >= '20050101'
AND TRANSACTIONDATE < '99991231'I have investigated that the problem is with TRANSACTIONDATE column (which is VARCHAR2 data type in database).
I want also inform You that the same query in SSIS 2005 on Windows 2005 64 bits worked fine.
Could You help me to find a solution?
Thanks in advance,
Łukasz - chalunster
PS. Sorry for my english
Edited by: BluShadow on 16-May-2011 15:15
put {noformat}{noformat} tags into the message and encoded the < symbol so that it formats correctly.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

user10450810 wrote:
Dear All,
this is my first post on this forum, so sorry if I choose wrong category for this question, but I stuck...
I'm using SSIS from SQL Server 2k8 R2 in Windows Server 2k8 R2. I have installed Oracle Client 10.2.0.2 32 bits and Oracle Client 10.2.0.4 64bits. I want to connect to Oracle 8i and Oracle 9i by these clients.
Unfortunately when I want to see a preview, only error occurs to me:
ORA-01861: literal does not match format string (OraOLEDB)
I have read a lot about this issue but nothing helps me (to_date, cast, convert etc.).
This is query which I use:
SELECT COMPANYID, TRANSACTIONTYPE, TRANSACTIONDATE,
PRODUCT, PRODUCTIONSITE, BATCHNUMBER,
BINNUMBER, QUANTITYSTOCKUNIT, QUANTITY,
UNITOFMEASURE, TRANSACTIONCURRENCYID, COST
FROM APPS.DW_PRODUCTION
WHERE TRANSACTIONDATE >= '20050101'
AND TRANSACTIONDATE < '99991231'
I have investigated that the problem is with TRANSACTIONDATE column (which is VARCHAR2 data type in database).
I want also inform You that the same query in SSIS 2005 on Windows 2005 64 bits worked fine.
Could You help me to find a solution?
Thanks in advance,
Łukasz - chalunster
PS. Sorry for my englishHi
Welcome to OTN Forums!
Are you sure you are using following code
SELECT COMPANYID, TRANSACTIONTYPE, TRANSACTIONDATE,
PRODUCT, PRODUCTIONSITE, BATCHNUMBER,
BINNUMBER, QUANTITYSTOCKUNIT, QUANTITY,
UNITOFMEASURE, TRANSACTIONCURRENCYID, COST
FROM APPS.DW_PRODUCTION
WHERE TRANSACTIONDATE >= '20050101'
AND TRANSACTIONDATE < 'If yes, then youistake is there,
WHERE TRANSACTIONDATE >= '20050101'
AND TRANSACTIONDATE < 'your script is not ended you can use this
WHERE TRANSACTIONDATE >= '20050101'
AND TRANSACTIONDATE < '20110101'or
WHERE to_date(TRANSACTIONDATE,'YYYYMMDD')  >= to_date('20050101','YYYYMMDD')
AND to_date(TRANSACTIONDATE,'YYYYMMDD') < to_date('20110101','YYYYMMDD')Edited by: Mahir M. Quluzade on May 16, 2011 6:59 PM

Similar Messages

  • SQL LOADER and ORA-01861: literal does not match format string

    Hi,
    I've to load data through control_file(.ctl) into oracle table through sqlldr. Oracle 11g, win xp.
    as soon as I use - sqlldr dss/dss control=orders.ctl I get error or nothing.
    Text file that is generated after loading fails has the following error.
    Record 1: Rejected - Error on table ORDERS, column O_ORDERDATE.
    ORA-01861: literal does not match format string
    I have checked the format of data to be loaded into Orders table is like this : *1996-01-02.*
    I checked the format of data in my database by querying sysdate from dual i.e. 10-JAN-10
    I thought that changing its format might solve my problem so i tried this:
    SQL> alter session set nls_date_format='YYYY-MM-DD';
    Session altered.
    SQL> select sysdate from dual;
    SYSDATE
    2010-01-10but still i'm getting the same error. I've to load millions of data. how I can solve this issue.
    Please suggest.
    Thanks alot.
    Best Regads,
    Kam

    Hi,
    It's strange ....nobody knew it?. I think this type of load problem will be very common isn't it.... where date column data is in a different format than in the db i.e.
    How to change *1996-01-02* in the Control_file to make it able to load in the table where sysdate is like this: *11-JAN-10*
    Sample data to be loaded is :
    1|36901|O|173665.47|1996-01-02|5-LOW|Clerk#000000951|0|nstructions sleep furiously among |
    Desc Orders
    O_ORDERDATE NOT NULL DATEI have tested this by creating a test table and a test control file by omitting this O_ORDERDATE and then everything was fine, data was inserted but don't know how to load this DATE also.
    Also not able to understand about POSITION in the control file...?
    Regards,
    Kam

  • SQL Error: ORA-01861: literal does not match format string

    Hello,
    I'm trying to do data mining on a web log which recorded one day web access information from a busy web server. I imported the data into Oracle Data miner, and created a table (WEBLOG). The idea is to create a new field, i.e. session, for the users so that each session could be thought as a representative of a user-intent (aka topic). Now based on this, data mining models would be used to cluster(group) the users based on their similarity. The first step is to prepare the data which involves using SQL queries. So first, all I did was to create a function for date and time. This is the following code I used,
    create or replace function ssndate(p_date in varchar2 default '03-01-18',
    p_time in varchar2)
    return number
    $if dbms_db_version.ver_le_10 $then
    deterministic
    $elsif dbms_db_version.ver_le_11 $then
    result_cache
    $end
    as
    begin
    return trunc((to_date(p_date||' '||p_time, 'dd-mm-yy hh24:mi:ss')
    - to_date('01-01-90','dd-mm-yy')) * (86400/2400));
    end ssndate;
    The function ssndate compiled successfully.
    The next step I took was to create a view through the following query,
    create or replace view WEBLOG_VIEWS
    as
    select (select ssndate(LOG_DATE, LOG_TIME) from dual) as "SESSION_DT",
    C_IP,
    CS_USER_AGENT,
    (CS_URI_STEM||'?'||CS_URI_QUERY) as WEB_LINK
    from WEBLOG;
    This was successful as well. The problem is in the next step where I try to do data grouping.
    create table FINAL_WEBLOG as
    select SESSION_DT, C_IP, CS_USER_AGENT,
    listagg(WEB_LINK, ' ')
    within group(order by C_IP, CS_USER_AGENT) "WEB_LINKS"
    from WEBLOG_VIEWS
    group by C_IP, CS_USER_AGENT, SESSION_DT
    order by SESSION_DT
    For this, I got the error,
    Error starting at line 1 in command:
    create table FINAL_LOG as
    select SESSION_DT, C_IP, CS_USER_AGENT,
    listagg(WEB_LINK, ' ')
    within group(order by C_IP, CS_USER_AGENT) "WEB_LINKS"
    from WEBLOG_VIEWS
    group by C_IP, CS_USER_AGENT, SESSION_DT
    order by SESSION_DT
    Error at Command Line:1 Column:7
    Error report:
    SQL Error: ORA-01861: literal does not match format string
    ORA-06512: at "DMUSER.SSNDATE", line 11
    ORA-06512: at line 1
    01861. 00000 - "literal does not match format string"
    *Cause:    Literals in the input must be the same length as literals in
    the format string (with the exception of leading whitespace).
    If the "FX" modifier has been toggled on, the literal must
    match exactly, with no extra whitespace.
    *Action:   Correct the format string to match the literal.
    I don't know where I'm going wrong with this.. the to_date function should be fine. In the data that I possess, the date and time are in no format. Example: 30118 and 0:00:09 respectively. If anyone has any clue about this I would be sincerely grateful for any help that I can get!! It's quite urgent..
    The Oracle version is 11.2.0.1.0
    Edited by: 975265 on Dec 5, 2012 5:31 PM

    975265 wrote:
    Ok.. Looks like I touched a nerve there. I apologize. I'm still a student, and this is the first time that I've tried something at this level. I'm still in the learning process, so I was hoping that someone could point me in the right direction in order to "fix" the data.Not so much touching a nerve as simply trying to implement a very very poor, but all too common, practice. Since you are a student (which we didn't know until this post) most people will cut you some slack. However, this little exchange should now be burned into your brain as you move forward. One of the very first rules of programming is to ALWAYS use the correct data types for your data. And along with that, never ever depend on implicit type conversions - always use the proper explicit conversion functions.
    And as a slight follow-on, when considering the appropriate data type, don't assume that just because we refer to a given element as a 'something number' that it is indeed a number. Telephone "numbers" are NOT numbers. U.S. Social Security "numbers" are NOT numbers. U.S. Postal Zip codes are NOT numbers. All are just character strings which, by convention, we limit to the same characters we use to represent numbers.
    And since this entire discussion came up around the representation of dates, you might want to take a look at http://edstevensdba.wordpress.com/2011/04/07/nls_date_format/
    Now, go forth and be a smarter programmer than your peers.
    Edited by: EdStevens on Dec 6, 2012 6:12 AM

  • ORA-01861 literal does not match format string, ORA-02063preceding line fro

    We have upgraded a client from 8.0.5 to 9.2.03. The following query is called from a report that was built using Cold Fusion5. It worked in 8.0.5, but not 9.2.03. When you run the report you get the errors
    [Oracle][ODBC][Ora]ORA-01861: literal does not match format string ORA-02063: preceding line from FRPE
    Here's the query:
    SELECT x.acct, x.obj, x.offn, x.status, x.asofdate, max( decode( x.func_id, 1, t, null ) ) UOB, max( decode( x.func_id, 12, t, null ) ) COB, max( decode( x.func_id, 24, t, null ) ) Rate_Warning, max( decode( x.func_id, 2, t, null ) ) Sector_Change, max( decode( x.func_id, 2006, t, null) ) FRRFRD , max( decode( x.func_id, 2003, t, null ) ) No_Tcode , max( decode( x.func_id, 2004, t, null) ) No_Sector FROM ( SELECT a.acct, a.func_id, count(*) cnt, 'Fail' t, b.obj, b.offn, b.status,a.asofdate FROM frpfaud@FRPE a, frpair@FRPE b WHERE a.acct=b.acct AND a.asofdate='2008-02-29 00:00:00' AND b.bnk not like 'B%' and b.obj not in ('KL') and b.obj in ('GAF') GROUP BY a.acct, a.func_id,b.obj,b.offn,b.status,a.asofdate) x GROUP BY x.acct, x.obj,x.offn,x.status,x.asofdate
    Now, this query will not work by running straight through SQL worksheet in either the 8.0.5 or 9.2.03 regions. So I guess it has something to do with Cold Fusion- which I know nothing about. Has anyone had any experience using Cold Fusion to issue a query? What would be the cause of the difference between the Oracle versions? That is the only thing that changed.
    Thanks for any input.

    I actually want the date format of DD-MON-YY. Which, from what I understand, is the default format for both Oracle 8.0.5 and 9.2.03. I'm trying to figure out why it is now displaying as 'yyyy-mm-dd hh24:mi:ss'. I could convince the client that the code needs changing if I had evidence that this version of Oracle (9.2.03) used a different default date format. Or if Cold Fusion pulls the date differently. Ughh.
    Here are the database parameters:
    SQL> show parameter nls_date_format
    NAME TYPE VALUE
    nls_date_format string
    select sysdate from dual;
    SYSDATE
    26-FEB-08
    1 row selected.
    select * from nls_session_parameters
    PARAMETER VALUE
    NLS_LANGUAGE AMERICAN
    NLS_TERRITORY AMERICA
    NLS_CURRENCY $
    NLS_ISO_CURRENCY AMERICA
    NLS_NUMERIC_CHARACTERS .,
    NLS_CALENDAR GREGORIAN
    NLS_DATE_FORMAT DD-MON-RR
    NLS_DATE_LANGUAGE AMERICAN
    NLS_SORT BINARY
    NLS_TIME_FORMAT HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY $
    NLS_COMP BINARY
    NLS_LENGTH_SEMANTICS BYTE
    NLS_NCHAR_CONV_EXCP FALSE
    17 rows selected.
    select * from v$nls_parameters
    PARAMETER VALUE
    NLS_LANGUAGE AMERICAN
    NLS_TERRITORY AMERICA
    NLS_CURRENCY $
    NLS_ISO_CURRENCY AMERICA
    NLS_NUMERIC_CHARACTERS .,
    NLS_CALENDAR GREGORIAN
    NLS_DATE_FORMAT DD-MON-RR
    NLS_DATE_LANGUAGE AMERICAN
    NLS_CHARACTERSET WE8MSWIN1252
    NLS_SORT BINARY
    NLS_TIME_FORMAT HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY $
    NLS_NCHAR_CHARACTERSET AL16UTF16
    NLS_COMP BINARY
    NLS_LENGTH_SEMANTICS BYTE
    NLS_NCHAR_CONV_EXCP FALSE
    19 rows selected.

  • ORA-01861: literal does not match format string

    Hi Experts,
    Whenever i am running the my procedure in oracle appliactions i am getting this error.
    ORA-01861: literal does not match format string .
    pkg is below:--->
    CREATE OR REPLACE PACKAGE Arc0471_Pending_Crc_Prc_Pkg IS
      --Insert into Custom Table
        PROCEDURE Arc_Insert_Data(P_ORG_ID VARCHAR2, P_BC_CODE VARCHAR2, P_GL_DATE VARCHAR2, P_DB_LINK VARCHAR2);
    END Arc0471_Pending_Crc_Prc_Pkg;
    CREATE OR REPLACE PACKAGE BODY Arc0471_Pending_Crc_Prc_Pkg IS
            PROCEDURE Arc_Insert_Data(P_ORG_ID VARCHAR2, P_BC_CODE VARCHAR2, P_GL_DATE VARCHAR2, P_DB_LINK VARCHAR2)
            IS
              v_val         varchar2(32000);          
              v_cursor1     integer;
              v_cursor2     integer;
              v_returncode  integer;
            BEGIN
           v_val   := ' ';
            v_val :=' INSERT INTO ARC.ARC_CRC_PRC_INVC ';
              v_val := v_val||' (CTA_TRX_NUMBER ,CTA_TRX_DATE ,DUE_DATE ,';
              v_val := v_val||' BILL_TO_CUSTOMER_NO,     BILL_TO_CUSTOMER_NAME ,     BILL_TO_LOCATION ,';
              v_val := v_val||' BILL_TO_ADDRESS ,ORIGINAL_AMOUNT ,APPLIED_AMOUNT , EXCHANGE_RATE     ,';
              v_val := v_val||' INVOICE_CURRENCY_CODE , ACCOUNT_CLASS , GL_DATE  , CTA_CUSTOMER_TRX_ID ,';
              v_val := v_val||' ORG_ID , CREATED_BY , CREATION_DATE ,LAST_UPDATE_BY , LAST_UPDATE_DATE , LAST_UPDATE_LOGIN )';
            v_val := v_val||' SELECT  CTA.TRX_NUMBER ,     CTA.TRX_DATE , APS.DUE_DATE ,';
              v_val := v_val||' HCA.ACCOUNT_NUMBER ,     HP.PARTY_NAME ,     HCSUA.LOCATION ,';
              v_val := v_val||' SUBSTR(HL.ADDRESS1 ||'||''' '''||'|| HL.ADDRESS2 ||'||'''  '''|| '||HL.ADDRESS3||'||'''  '''|| '||HL.ADDRESS4|| '||'''  ''' ||'||HL.PROVINCE||'||'''  '''||'|| HL.CITY ||'||'''  '''||'|| HL.STATE ||'||'''  '''||'|| HL.POSTAL_CODE ||'||'''  '''||'||FTL.TERRITORY_SHORT_NAME,0,1500),';
              v_val := v_val||' APS.AMOUNT_DUE_ORIGINAL , APS.AMOUNT_APPLIED,APS.EXCHANGE_RATE, APS.INVOICE_CURRENCY_CODE, CTLA.ACCOUNT_CLASS,';
              v_val := v_val||' APS.GL_DATE , CTA.CUSTOMER_TRX_ID , CTA.ORG_ID ,FND_GLOBAL.USER_ID ,';
              v_val := v_val||' SYSDATE , FND_GLOBAL.USER_ID , SYSDATE , FND_GLOBAL.LOGIN_ID '  ;  
             v_val := v_val||' FROM ' ;
             v_val := v_val||' AR.RA_CUSTOMER_TRX_ALL CTA,';
              v_val := v_val||' AR.RA_CUST_TRX_TYPES_ALL CTTA,';
              v_val := v_val||' AR.RA_CUST_TRX_LINE_GL_DIST_ALL CTLA,';
              v_val := v_val||' AR.HZ_PARTIES HP,';
              v_val := v_val||' AR.HZ_CUST_ACCOUNTS HCA,';
              v_val := v_val||' AR.HZ_CUST_SITE_USES_ALL HCSUA,';
              v_val := v_val||' AR.HZ_LOCATIONS HL,';
              v_val := v_val||' AR.HZ_PARTY_SITES HPS,';
              v_val := v_val||' AR.AR_PAYMENT_SCHEDULES_ALL APS,';
              v_val := v_val||' AR.HZ_CUST_ACCT_SITES_ALL HCASA,';
              v_val := v_val||' GL.GL_CODE_COMBINATIONS GCC,';
              v_val := v_val||' AR.AR_RECEIVABLE_APPLICATIONS_ALL ARAA,';
              v_val := v_val||' APPLSYS.FND_TERRITORIES_TL FTL ,';
              v_val := v_val||' ONT.OE_TRANSACTION_TYPES_TL'|| P_DB_LINK ||' IND_OTT, ' ;
              v_val := v_val||' ONT.OE_ORDER_HEADERS_ALL'||P_DB_LINK ||'  IND_OH, ';
              v_val := v_val||' AR.RA_CUSTOMER_TRX_ALL'||P_DB_LINK ||' IND_RCTA   ';
             v_val := v_val||' WHERE   CTA.ORG_ID = '||''''|| P_ORG_ID||'''';
             v_val := v_val||' AND   CTTA.ORG_ID = '||''''|| P_ORG_ID||'''' ;
             v_val := v_val||' AND   CTLA.ORG_ID = '||''''|| P_ORG_ID||'''' ;
             v_val := v_val||' AND   HCSUA.ORG_ID = '||''''|| P_ORG_ID||'''' ;
             v_val := v_val||' AND   APS.ORG_ID =  '||''''||P_ORG_ID||'''';
             v_val := v_val||' AND   HCASA.ORG_ID = '||''''|| P_ORG_ID||'''' ;
             v_val := v_val||' AND   CTLA.ACCOUNT_CLASS     =     '||'''REC''';
              v_val := v_val||' AND   CTLA.GL_DATE <= TRUNC(TO_DATE( '||''''||P_GL_DATE||''''||','||'''DD/MM/RRRR HH24:MI:SS'''||'))';
             v_val := v_val||' AND   NVL(ARAA.APPLY_DATE,TO_DATE( '||''''||P_GL_DATE||''''||','||'''DD/MM/RRRR HH24:MI:SS'''||')) <= TRUNC(TO_DATE ('||''''||P_GL_DATE||''''||','||'''DD/MM/RRRR HH24:MI:SS'''||'))';
             v_val := v_val||' AND   TO_DATE(APS.TRX_DATE,'||'''DD-MON-RRRR'''||') >'|| '''02-SEP-2007''' ;
             v_val := v_val||' AND     CTA.CUST_TRX_TYPE_ID    =     CTTA.CUST_TRX_TYPE_ID';
             v_val := v_val||' AND     CTLA.CUSTOMER_TRX_ID     =     CTA.CUSTOMER_TRX_ID';
             v_val := v_val||' AND     HCA.CUST_ACCOUNT_ID     =     CTA.BILL_TO_CUSTOMER_ID';
             v_val := v_val||' AND     HCA.PARTY_ID          =     HP.PARTY_ID';
             v_val := v_val||' AND     HCSUA.SITE_USE_ID     =     CTA.BILL_TO_SITE_USE_ID';
             v_val := v_val||' AND     HL.LOCATION_ID          =     HPS.LOCATION_ID';
             v_val := v_val||' AND     HPS.PARTY_ID          =     HCA.PARTY_ID';
               v_val := v_val||' AND     APS.CUSTOMER_TRX_ID     =     CTLA.CUSTOMER_TRX_ID';
             v_val := v_val||' AND     HCASA.CUST_ACCOUNT_ID     =     HCA.CUST_ACCOUNT_ID';
             v_val := v_val||' AND   HCASA.CUST_ACCT_SITE_ID =HCSUA.CUST_ACCT_SITE_ID';
             v_val := v_val||' AND   HCASA.PARTY_SITE_ID=HPS.PARTY_SITE_ID';
             v_val := v_val||' AND     ARAA.APPLIED_CUSTOMER_TRX_ID(+) = CTA.CUSTOMER_TRX_ID';
             v_val := v_val||' AND   IND_RCTA.TRX_NUMBER = CTA.TRX_NUMBER';
             v_val := v_val||' AND     TO_CHAR(IND_OH.ORDER_NUMBER) = IND_RCTA.CT_REFERENCE';
             v_val := v_val||' AND     IND_OTT.TRANSACTION_TYPE_ID = IND_OH.ORDER_TYPE_ID';
              --v_val := v_val||' AND   ARC.Arc0463_Get_Remng_Amt(APS.TRX_NUMBER,'||''''|| P_GL_DATE||''''||','||'APS.INVOICE_CURRENCY_CODE) <> 0';
             v_val := v_val||' AND   IND_OTT.NAME IN ('||'''D0M RC Imported Sale'''||','||'''D0M RC Indigenous Sale'''||')';
             v_val := v_val||' AND   GCC.CODE_COMBINATION_ID = CTLA.CODE_COMBINATION_ID';
             v_val := v_val||' AND   GCC.SEGMENT1 = '|| ''''||P_BC_CODE||'''';
             v_val := v_val||' AND   HL.COUNTRY = FTL.TERRITORY_CODE';
             v_val := v_val||' AND   FTL.LANGUAGE = USERENV('||'''LANG'''||')';          
                v_cursor1 := dbms_sql.open_cursor;
              dbms_sql.parse(v_cursor1,v_val,DBMS_SQL.NATIVE);
              v_returncode := dbms_sql.execute(v_cursor1);
              dbms_sql.close_cursor(v_cursor1);
         COMMIT;
         EXCEPTION     
                    WHEN DUP_VAL_ON_INDEX THEN
                                    NULL;
                   WHEN OTHERS THEN
                        COMMIT;
                   FND_FILE.PUT_LINE(FND_FILE.OUTPUT, 'IN WHEN OTHERS THEN OF INSERT INTO ARC.ARC_CRC_PRC_INVC'||SQLCODE || ' - ' || SQLERRM);
                -- dbms_output.put_line(sqlcode||sqlerrm);
            END Arc_Insert_Data;
    END Arc0471_Pending_Crc_Prc_Pkg;in above procdure APS.TRX_DATE having the format like this..23/3/2006. in Backend this procedure is working fine ..in toad(version 8.0.0.47). database is 9.0.
    but in oracle apps it is giving error like "literal does not match format string".
    please give me the solution...
    Thanks in ADv...

    Hi,
    It is the Date Data type...There's your problem then; NEVER, EVER, EVER to_date a date!! As you have discovered, it leads to problems when your code is run on different clients due to the different NLS settings they may have. You've been lucky, in other words, that your code has been working at all!
    What to_dating a date does is this:
    to_date(to_char(date_value, <format in NLS_DATE_FORMAT parameter>), <format in NLS_DATE_FORMAT parameter>) You've been lucky because your NLS_DATE_FORMAT has the same format as the data, on your client. On the database, however, it is clearly different.
    Simply remove the to_date from your already-a-date value, and you should find that it works fine.

  • SQL query error - Literal does not match format string

    Hi All,
    When I am removing these code form query then it is running fine else it is giving error of "Literal does not match format string."
    AND trunc((SYSDATE)) > DECODE(fifs.id_flex_structure_name, 'XXX Service Agreement', trunc(TO_DATE
    (pac.segment3, 'YYYY/MM/DD HH24:MI:SS')),trunc(SYSDATE) )
    Regards,
    Ajay

    Ajay Sharma wrote:
    It is flexfield segment so it can contain anything. For my query it is returning date.....Oh dear. Two really bad design decisions in one, there - storing dates as varchar2 and storing more than one type of data in one column. I suggest you read this: http://www.simple-talk.com/opinion/opinion-pieces/bad-carma/ in order to see just why that might be a bad design.
    If you have any influence at all over the way your tables/app is designed, then I would highly recommend changing the design, as it will save you countless headaches like the one you've currently got.
    If you are absolutely stuck with that design, then a) poor you and b) you'll have to add in some filters onto your queryto make sure you're only selecting rows with dates in that column.

  • Error: Literal does not match format string

    Can anyone help me with the query below. I am trying to insert CMPGN_ID, PGM_KEY, CMPGN_BEGIN_DT into TEMP.
    I get an error 'Literal does not match format string' for 'SELECT to_char(add_months(SYSDATE,-1),'YYYYMM') from dual'
    CMPGN_BEGIN_DT has a data type of DATE.
    INSERT INTO TEMP (CMPGN_ID, PGM_KEY, CMPGN_BEGIN_DT)
    VALUES(
    ('NCR_'|| (select to_char(add_months(SYSDATE,-1),'YYYYMM') from dual)),
    (SELECT PGM_KEY FROM PROGRAM WHERE PGM_NAME = 'NCR'),
    (SELECT to_char(add_months(SYSDATE,-1),'YYYYMM') from dual)
    Thanks

    INSERT INTO TEMP (CMPGN_ID, PGM_KEY, CMPGN_BEGIN_DT)
    SELECT 'NCR_'|| to_char(add_months(SYSDATE,-1),'YYYYMM'),
         PGM_KEY,
         to_char(add_months(SYSDATE,-1),'YYYYMM')
    FROM PROGRAM
    WHERE PGM_NAME = 'NCR';Datatypes are unclear, may need datatype casting with date column, but otherwise the above should work.
    Thx,
    SriDHAR

  • Error: ORA-01861: literal does not match format string

    Hi,
    I am doing a RFC-XI-JDBC scenario.
    In the CC monitoring , i am getting this error for the reciver CC:
    "Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. "TableNAMe"(structure 'STATEMENTNAME'): java.sql.SQLException: ORA-01861: literal does not match format string "
    Please guide me what can be the cause and how to solve it.
    Thanks,
    Puneet

    This is how my payload looks like :
    <?xml version="1.0" encoding="UTF-8"?>
    <ns1:MT_JDBC_REC xmlns:ns1="https:namespace.scene3">
    <STATEMENTNAME>
    <TABLE_NAME action="INSERT">
    <TABLE>ggclgis</TABLE>
    <access>
    <VALVE_ID>12584</VALVE_ID>
    <EQUNR>122</EQUNR>
    <ERNAM>12122</ERNAM>
    <INVNR>1212</INVNR>
    <GROES>1212</GROES>
    <ELIEF>123</ELIEF>
    <GWLEN>21-jul-2008</GWLEN>
    <GWLDT>12-jun-2006</GWLDT>
    <SERGE>wqwqw</SERGE>
    <TYPBZ>wqwqwq</TYPBZ>
    </access>
    </TABLE_NAME>
    </STATEMENTNAME>
    </ns1:MT_JDBC_REC>
    Please tell me if it looks fine.

  • The '' secondary data source is not a relational data source, or does not use an OLE DB provider.

    Hi,
    We are using Teradata as data source in SSAS 2008R2, it’s using ‘.Net Providers\.Net Data Provider for Teradata’.
    In DSV, we have two data sources both using Teradata. While processing dimensions, all dimensions coming from secondary data source has error message”
    The '' secondary data source is not a relational data source, or does not use an OLE DB provider.”
    But we are not using OLE DB provider for now, we’ve searched some threads that named queries can be replaced for secondary ds, but since we have a lot of tables, it’s hard to implement using named queries.
    Any inputs would be appreciated. 

    Hi memostone,
    When defining a data source view that contains tables, views, or columns from multiple data sources, the first data source from which you add objects to the data source view is designated as the primary data source (you cannot change the primary data
    source after it is defined). After defining a data source view based on objects from a single data source, you can then add objects from other data sources.
    If an OLAP processing or a data mining query requires data from multiple data sources in a single query, the primary data source must support remote queries using
    OpenRowset. Typically, this will be a SQL Server data source.
    Here are the restrictions:
    The primary data source should be SQL Server and support OpenRowset to the secondary data source.
    Or you design the cube in such a way that rocessing for each object only needs to access data from a single data source
    I recommand you refer to the following article:
    Defining a Data Source View (Analysis Services):
    http://technet.microsoft.com/en-us/library/ms174600.aspx
    Regards,
    Bin Long
    TechNet Community Support

  • Errors in the high-level relational engine. The data source view does not contain a definition for the table or view. The Source property may not have been set.

    Hi All,
    I have a cube in which i'm using the TIME DIM that i created in the warehouse. But now i wanted a new measure in the cube which is Average over time and when i wanted to created the new measure i got a message that no time dim was defined, so i created a
    new time dimension in the SSAS using wizard. But when i tried to process the new time dimension i'm getting the follwoing error message
    "Errors in the high-level relational engine. The data source view does not contain a definition for "SSASTIMEDIM" the table or view. The Source property may not have been set."
    Can anyone please tell me why i cannot create a new measure average over the time using my time dimension? Also what am i doing wrong with the SSASTIMEDIM, that i'm getting the error.
    Thanks

    Hi PMunshi,
    According to your description, you get the above error when processing the time dimension. Right?
    In this scenario, since you have updated the DSV, it should have no problem on the table existence. One possibility is that table has been specified for tracking in the notifications for proactive caching, but isn't available any more for some
    reason. Please change the setting in Proactive Caching into "MOLAP".
    Reference:
    How To Implement Proactive Caching in SQL Server Analysis Services SSAS
    If you have any question, please feel free to ask.
    Best Regards,
    Simon Hou
    TechNet Community Support

  • Data source 80BP_ID does not exists in source system

    Hi All,
    I have just started with standard content for SD module.
    I activated my datasources 2lis_11_vaitm and 2lis_12_vcitm in my R3 system.
    After replicating these data sources in my BI system i went to BI Content to activate my Info sources.
    While installing info sources 2lis_11_vaitm and 2lis_12_vcitm i got  errors  namely
    Data source 80BP_ID does not exists in source system
    Datasource 80BP_REL not maintained.
    Can somebody pls suggest a way out.
    Thanks in advance..
    Regards,
    Rohit

    Hi Rohit,
    When ever you try to install the SD related Standard business content then it will automatically pick up the CRM related data. the 0BP_ID, these are related to the CRM.
    Please uncheck the unrelated objects while installing the STD content.
    you can select the option in the grouping as ONLY NECESSARY OBJECTS.
    Regards,
    Ravi Kanth

  • "Source File does not match XML Schema"

    Using MDM 5.5 SP4 Patch 2 (Build 5.5.34.26) on a 32-bit system (WinServer 2003, Enterprise Edition SP1.
    This source file and schema have been verified by SAP Tech Support and again using Altova XML Spy. The schema was loaded into MDM through the console and the source file was successfully mapped against it and the data manually imported into MDM. The customer record was then cleansed using the Data Manager and the import map was used to create an inbound port. However, when the Import Server goes to import the file using the map, the following error is dropped into the log: "Source File does not match XML Schema". Has anyone else seen this error?
    Thanks,  Don
    IMPORT LOG ENTRY:
    <?xml version="1.0" encoding="utf-8"?>
    <?xml-stylesheet type="text/xsl" href="MDM_Log.xsl"?>
    <MDM_Log version="1.0" path="H:PROGRA~1SAPMDM~1.5IMPORT~1TempMDIS_TASK@@U@[email protected]"
    >
         <Open ts-long="18:24:35 GMT, Saturday, February 03, 2007" ts="2007/02/03 18:24:35.108 GMT" pid="8640" host="bp1tulap452" compile-type="RELEASE_32">
              <Trace ts="2007/02/03 18:24:35.249 GMT" tid="7216" entry-no="3">[BP US FUELS CUSTOMER MASTER] Import Task Started. Chunk size[50000], No. parallel chunks[1]</Trace>
              <Trace ts="2007/02/03 18:24:43.890 GMT" tid="5980" entry-no="11">xSaxParser: Starting.</Trace>
              <Trace ts="2007/02/03 18:24:43.937 GMT" tid="5980" entry-no="19">xSaxParser: Ending.</Trace>
              <Trace ts="2007/02/03 18:24:43.937 GMT" tid="5980" entry-no="20">Source file does not conform to XML Schema!<LINE-FEED/></Trace>
              <Trace ts="2007/02/03 18:24:45.312 GMT" tid="7216" entry-no="29">[RESPOSITORY]Import Task Finished. Chunk size[50000], No. parallel chunks[1]</Trace>
         </Open>
    </MDM_Log>
    SOURCE FILE:
      <?xml version="1.0" encoding="UTF-8" ?>
    - <ns1:CustomerCreateResp xmlns:ns1="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100">
    - <CUSTOMER>
    - <item>
      <CUSTOMERNO>0090154474</CUSTOMERNO>
      <MDMCUSTOMER>2463</MDMCUSTOMER>
      <CREATE_DATE>22/01/2007,11:43:49</CREATE_DATE>
    - <RETURN>
      <TYPE />
      <MESSAGE />
      </RETURN>
    - <PT_CONTPART_RETURN>
    - <item>
      <MDM_CONTACT>0000000001</MDM_CONTACT>
      <CONTACT>0001111119</CONTACT>
      </item>
    - <item>
      <MDM_CONTACT>0000000004</MDM_CONTACT>
      <CONTACT>0002222229</CONTACT>
      </item>
      </PT_CONTPART_RETURN>
    - <PARTNERS>
    - <item>
      <CUSTOMERNO>0090154474</CUSTOMERNO>
      <PARTNER_FUNCTION>RE</PARTNER_FUNCTION>
      <PARTNER_NUMBER>0001333329</PARTNER_NUMBER>
      <DEFAULT_PARTNER>X</DEFAULT_PARTNER>
      </item>
    - <item>
      <CUSTOMERNO>0090154474</CUSTOMERNO>
      <PARTNER_FUNCTION>WE</PARTNER_FUNCTION>
      <PARTNER_NUMBER>0001555559</PARTNER_NUMBER>
      <DEFAULT_PARTNER />
      </item>
      </PARTNERS>
      </item>
      </CUSTOMER>
      </ns1:CustomerCreateResp>
    SCHEMA:
       <?xml version="1.0" encoding="UTF-8" ?>
    - <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100" targetNamespace="urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100" elementFormDefault="unqualified">
      <xsd:element name="CustomerCreateResp" type="CustomerCreateResp" />
    - <xsd:complexType name="CustomerCreateResp">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">682cc2d0aa6e11db9b800015c5888624</xsd:appinfo>
      </xsd:annotation>
    - <xsd:sequence>
    - <xsd:element name="CUSTOMER">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">f68988f0a02e11db94bb00166f98336c</xsd:appinfo>
      </xsd:annotation>
    - <xsd:complexType>
    - <xsd:sequence>
    - <xsd:element name="item" maxOccurs="unbounded">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b20a75811dba9d400166f983d94</xsd:appinfo>
      </xsd:annotation>
    - <xsd:complexType>
    - <xsd:sequence>
    - <xsd:element name="CUSTOMERNO" type="xsd:string" minOccurs="0">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b21a75811db9c4800166f983d94</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
    - <xsd:element name="MDMCUSTOMER" type="xsd:string" minOccurs="0">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b22a75811dbcbac00166f983d94</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
    - <xsd:element name="CREATE_DATE" type="xsd:string" minOccurs="0">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b23a75811dbcc0300166f983d94</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
    - <xsd:element name="RETURN" minOccurs="0">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b24a75811db8d5500166f983d94</xsd:appinfo>
      </xsd:annotation>
    - <xsd:complexType>
    - <xsd:sequence>
    - <xsd:element name="TYPE" type="xsd:string" minOccurs="0">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b25a75811db876d00166f983d94</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
    - <xsd:element name="MESSAGE" type="xsd:string" minOccurs="0">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b26a75811db85c400166f983d94</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
    - <xsd:element name="PT_CONTPART_RETURN" minOccurs="0">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b27a75811db8ca900166f983d94</xsd:appinfo>
      </xsd:annotation>
    - <xsd:complexType>
    - <xsd:sequence>
    - <xsd:element name="item" minOccurs="0" maxOccurs="unbounded">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b28a75811dbaae100166f983d94</xsd:appinfo>
      </xsd:annotation>
    - <xsd:complexType>
    - <xsd:sequence>
    - <xsd:element name="MDM_CONTACT" type="xsd:string" minOccurs="0">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b29a75811dbaade00166f983d94</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
    - <xsd:element name="CONTACT" type="xsd:string" minOccurs="0">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2aa75811dbc24c00166f983d94</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
    - <xsd:element name="PARTNERS" minOccurs="0">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ba75811dbb74500166f983d94</xsd:appinfo>
      </xsd:annotation>
    - <xsd:complexType>
    - <xsd:sequence>
    - <xsd:element name="item" minOccurs="0" maxOccurs="unbounded">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ca75811db9f6500166f983d94</xsd:appinfo>
      </xsd:annotation>
    - <xsd:complexType>
    - <xsd:sequence>
    - <xsd:element name="CUSTOMERNO" type="xsd:string" minOccurs="0">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2da75811db9bd800166f983d94</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
    - <xsd:element name="PARTNER_FUNCTION" type="xsd:string" minOccurs="0">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2ea75811dbb84100166f983d94</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
    - <xsd:element name="PARTNER_NUMBER" type="xsd:string" minOccurs="0">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b2fa75811db852800166f983d94</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
    - <xsd:element name="DEFAULT_PARTNER" type="xsd:string" minOccurs="0">
    - <xsd:annotation>
      <xsd:appinfo source="http://sap.com/xi/TextID">72ea9b30a75811db968400166f983d94</xsd:appinfo>
      </xsd:annotation>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:sequence>
      </xsd:complexType>
      </xsd:schema>

    You have to define the namespace in the URI field of XML Schmea in Console.
    In MDM Console,
    Admin -> XML Schemas -> Create XML Schema
    You have to specify the namespace urn:bp:xi:up:re:cust_mdm:cmdm:pr5:100 in the URI property.
    Please update this post if fixed your problem.

  • Under Save as, extension does not match format chosen (ie, if I choose JPG, it gives my file a IIF e

    Under Save as, extension does not match format chosen (ie, if I choose JPG, it gives my file a IIF extension. I have to choose JPEG 2000 to get JPG, all are off by one position)

    Did you install plug-ins from a previous version of Photosop (or point the additional plug-ins to a previous version)? Photoshop CS6 has changed the location and way of installing plug-ins. All required plug-ins are stored internally–the location depends on the OS–and only non-Adobe 3rd party plug-ins should now be installed in the main Plug-ins folder.
    You'll need to clean out and/or fix your plug-ins to get the correct behavior back...

  • Unique Identifier of the source style does not match the target st

    I'm running into a bunch of problems with an export/import, but I'll limit myself to the more opaque ones for the moment. We've got a page group in place and are trying to overwrite it, or at least parts of it, with a revised version. The export appears to succeed, but the pre-check (and consequently, it appears, the entire import) fails. One of the few specific errors has to do with a style:
    [ERROR] id = NULL context = style_pre_check user = PORTAL The Unique Identifier of the source style MY_STYLE does not match the target style MY_STYLE.
    The style in question exists in both our development environment (from which we're exporting) and our target environment (into which we're importing, of course). It hasn't even been changed in the development environment, so it's identical to what it's replacing. Does anybody know what's going on here and how it might be fixed?

    This indicates the style in the production did not come from the same development system as the one you're attempting the new import from. Also, this could happen, if for some reason you had deleted the style in the development after it was deployed to production and (re-) created a new style with the same name.
    In order for pre-check to succeed, you would need to either rename the style on the production or rename it on development and re-export and import the transport set again.

  • Error Message - Value Entered Does Not Match Format of Field

    I keep getting an error message in Adobe Pro X: "The value entered does not match the format of the field [JF13]".
    I have JF13 programmed as follows:
    On Calculate tab:
    if(Number(this.getField("ck4").value) > 0) this.getField("JF13").value = Number(this.getField("FL019").value); else this.getField("JF13").value = " ";
    It is programmed this way so if the user checks the check box before the field, only then will JF13 populate a value, which pulls from FL019. I also have the settings set to "number" because the data needs to display as a dollar amount $xxx.xx.
    FL019 is a hidden field on the form which pulls a dollar amount from a Mainframe, and its settings are also set to "Number" :
    I get four pop up windows with the above mentioned error message, and the only way to make the message stop is to remove the "number" format from the fields. However, when this is done, if any number which ends in a zero is entered, it cuts off the zero. This is not acceptable either.
    Is there some sort of script I could add or some other way to prevent both the error message and the cutting off of the zero on JF13?
    I am not very proficient with javascript, so any assistance would be appreciated!

    Thank you so much for your response!!
    Forgive me for my lack of knowledge - but where exactly would I add that in the script?
    I tried it like this:
    if(Number(this.getField("ck4").value) > 0) this.getField("JF13").value = Number(this.getField("FL019").value); else this.getField("JF13").value = ""(empty string);
    And I got an error saying I was missing a parenthesis. Should it go somewhere else or am I completely off?

Maybe you are looking for