Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. andys288

    ORA-01843 NOT A VALID MONTH ERROR

    The last time I tried that I completely screwed up our Sage Accounts system, so I SCARED to do it! Thanks again for your help
  2. andys288

    ORA-01843 NOT A VALID MONTH ERROR

    Fantastic! Thats done just what I needed! Thanks Dima
  3. andys288

    ORA-01843 NOT A VALID MONTH ERROR

    The format they currently are in is "13/08/03". I have already been able to extract the information incluidng order_no into excel using microsoft query, and now have manipulated them into the format "13-AUG-03". All I want to do now is put them back into oracle.
  4. andys288

    ORA-01843 NOT A VALID MONTH ERROR

    I've worked out what my problem is! Oracle (as you all will know and I should have remembered!) stores dates in the format 13-AUG-03, but my Supplier_ref column is storing the data 13/08/03, therefore causing the "invalid month" error. Now that I have solved that mystery, my next...
  5. andys288

    ORA-01843 NOT A VALID MONTH ERROR

    I used the amended script of dima's as the first one just scrolled and scrolled. Routine ran and did not find any dodgy data, but when I try my to-date command I still get an invalid month error. The supplier_ref field was originally a 20 character text field on a Sage line 500 database...
  6. andys288

    ORA-01843 NOT A VALID MONTH ERROR

    declare mRowid rowid; mDate date; begin for f in (select rowid, supplier_ref from poheadm) loop mRowid := f.rowid; mDate := to_date(f.supplier_ref); end loop; exception when others then dbms_output.put_line('Rowid you need is '||mRowid); end; I got the following output...
  7. andys288

    ORA-01843 NOT A VALID MONTH ERROR

    I have a similar problem when running Cognos Impromptu and oracle 8i database. I have "tweaked" the above script to fit by data structure and found some erroneous values which I have updated. BUT I am still getting the invalid month problem. Anybody got any other ideas?

Part and Inventory Search

Back
Top