Not valid month Error Ora 01843

hi
This is an error while running a report 6i. in Oracle 8i Environment.
"Not valid month Error Ora 01843"
This report is working fine in Production. But it is not working in Development Database.
Development database is the image of Production system.
Any reason for this Error?

Dear Naseer C ,
We got similar experiences for several time.
We quried like that.
Selet moth from table;
08-AUG-1988
08-08-1988
08-08-88
We changed several time until diappear the message.
Hopefully, it will help you.
Best regards,
S!G

Similar Messages

Throwing not a valid month error(ORA-01843)

Hi,
Can you please tell me whats wrong with the statement
select Fas_Rpt_Disclose_Summ_Pkg.F_EXR_COLUMN_VALUES(3,5207773,TO_DATE('28-JUN-06','DD-MON-YY'),TO_DATE('26-Sep-06','DD-MON-YY'),TO_DATE('26-SEP-06:23:59:59','DD-MON-YY:HH24:MI:SS'),'INTRINSICVALEXR') from dual;
Thanks

What is the current value of NLS_DATE_LANGUAGE?
SQL> alter session set nls_date_language='ENGLISH';
Session altered.
SQL> select TO_DATE('28-JUN-06','DD-MON-YY'),
2         TO_DATE('26-Sep-06','DD-MON-YY'),
3         TO_DATE('26-SEP-06:23:59:59','DD-MON-YY:HH24:MI:SS')
4 from dual;
TO_DATE(' TO_DATE(' TO_DATE('
28-JUN-06 26-SEP-06 26-SEP-06
SQL> alter session set nls_date_language='FRENCH';
Session altered.
SQL> select TO_DATE('28-JUN-06','DD-MON-YY'),
2         TO_DATE('26-Sep-06','DD-MON-YY'),
3         TO_DATE('26-SEP-06:23:59:59','DD-MON-YY:HH24:MI:SS')
4 from dual;
select TO_DATE('28-JUN-06','DD-MON-YY'),
ERROR at line 1:
ORA-01843: not a valid month
SQL>

[PL/SQL Error] ORA-01843: not a valid month, not sure how to troubleshoot

Trying to use PL/SQL to automatically create a report that show the following:
Daily:
# of Registered Users
# of Completes (assessment)      Average per User
# of Starts (assessment)      Average per User
Weekly:
# of Registered Users
# of Completes (assessment)      Average per User
# of Starts (assessment)      Average per User
Yearly:
# of Registered Users
# of Completes (assessment)      Average per User
# of Starts (assessment)      Average per User
When I run the PL/SQL I get the following
[error]
ORA-01843: not a valid month
[error]
The error occurs on this part of the PL/SQL
--registered users weekly starts
select count(*), trunc(next_day(sysdate-29, 'SUNDAY')-7), trunc(sysdate-29)
     into v_weekly_count_total_ru, v_weekly_start_date, v_weekly_end_date
          from entities
               where list_id = 3290
               and participation_code_id = 10
               and trunc(participation_date)
               between trunc(next_day(sysdate-29, 'SUNDAY')-7) and
                        trunc(sysdate-29);I'm using the number 29 because I'm using a test database to test this first before moving it into production. And my test data only goes back to early August 2006.
Also, I'm not doing anything with months, so I am suprised that it is throwing this type of error.
thanks

I tested a snippet of code in my production environment, just to see if I would get any results:
--registered users weekly starts
select count(*), trunc(next_day(sysdate-1, 'SUNDAY')-7), trunc(sysdate-1)
     --into v_weekly_count_total_ru, v_weekly_start_date, v_weekly_end_date
          from entities
               where list_id = 3290
               and participation_code_id = 10
               and trunc(participation_date)
               between trunc(next_day(sysdate-1, 'SUNDAY')-7) and trunc(sysdate-1);
COUNT(*)     TRUNC(NEXT_DAY(SYSDATE-1,'SUND     TRUNC(SYSDATE-1)--INTOV_WEEKLY
1     09/10/2006 00:00:00     09/11/2006 00:00:00I did a double check in my test DB to make sure there is data there:
select count(*)
     from entities
          where trunc(participation_date)
          between to_date('01-08-2006','DD-MM-YYYY')
          and to_date('14-08-2006','DD-MM-YYYY')
          and list_id = 3290;
COUNT(*)
11So I'm pretty sure that I'm not pulling anything null.
thanks

Need help in understanding the error ORA-01843: not a valid month - ECX_ACT

Hello All,
We need help in understanding the Transaction Monitor -> Processing Message (error "ORA-01843: not a valid month - ECX_ACTIONS.GET_CONVERTED_DATE").
And how to enable the log for Transaction Monitor -> Processing Logfile.
Actually we are trying to import the Purchase Order XML (OAG) into eBusiness Suite via BPEL Process Manager using the Oracle Applications Adapter. The process is working fine with expected payload until it reaches the XML Gateway Transaction Monitor, where we are getting this error.
thanks
muthu.

Hello All,
We need help in understanding the Transaction Monitor -> Processing Message (error "ORA-01843: not a valid month - ECX_ACTIONS.GET_CONVERTED_DATE").
And how to enable the log for Transaction Monitor -> Processing Logfile.
Actually we are trying to import the Purchase Order XML (OAG) into eBusiness Suite via BPEL Process Manager using the Oracle Applications Adapter. The process is working fine with expected payload until it reaches the XML Gateway Transaction Monitor, where we are getting this error.
thanks
muthu.

How to solve ORA-01843: not a valid month error

i am gettion ORA-01843: not a valid month error how to solve it. and how to find which record causing
proble.
Thanks in advance.

EdStevens wrote:
Ramin Hashimzadeh wrote:
user1571313 wrote:
i am gettion ORA-01843: not a valid month error how to solve it. and how to find which record causing
proble.
Thanks in advance.Bring for me something from somewhere... :)Bring me a shrubbery.
When you have found the shrubbery, then you must cut down the mightiest tree in the forest ... with a herring.We are no longer the knights who say ni! We are now the knights who say "i am gettion ORA-01843"!

SQL execution error, ORA-01843: not a valid month

Im using ASP/VBScript and its my first time starting to use Oracle as a DB provider.
Just having an issue with a statement that I have.
Heres my statement:
SELECT T592_NOON.SHIP_CODE, T592_NOON.REPORT_DATE, T592_NOON.L_B, T592_NOON.AVERAGE_SPEED, T592_NOON.SEASTATE, T592_NOON.DISTANCE, T592_NOON.WIND_DIRECTION, T592_NOON.IFO_MAIN, T592_NOON.IFO_BOILER, T592_NOON.IFO_AUXENGINE FROM T592_NOON WHERE (((SHIP_CODE)='S271') AND (REPORT_DATE BETWEEN to_date('08/02/2004 13:00:00', 'DD-MON-YYYY HH24:MI') and to_date('28/02/2004 18:15:00', 'DD-MON-YYYY HH24:MI')))
Whenever I run it it errors and returns:
SQL execution error, ORA-01843: not a valid month
Can anyone tell why this wouldnt work?
REPORT_DATE type is DATE
REPORT_DATE Sample data: 2003-04-28-12.00.00.000000

Changing the format of the date seemed to fix it.
Incorrect: '08/02/2004 13:00:00'
Correct: '08-FEB-2004 13:00'

ORA-01843 Not a valid month Error

Dear all,
We did a database upgrade from 9.2.0.1 to 11gR2 and after that everything is working fine.
But now we noticed that the users are getting ORA-01843 Not a valid month Error.
I changed the NLS_DATE_FORMAT in the init.ora file, but still the error persist.
As a work around I changed the NLS_DATE_FORMAT=DD-MM-YYYY on the client pc registry and now its working in that pc..
Is there any other way so that the change gets affected globally ??
Any tips
Thanks in adv,
Mahesh

mahesh wrote:
Dear all,
We did a database upgrade from 9.2.0.1 to 11gR2 and after that everything is working fine.
But now we noticed that the users are getting ORA-01843 Not a valid month Error.
I changed the NLS_DATE_FORMAT in the init.ora file, but still the error persist.
As a work around I changed the NLS_DATE_FORMAT=DD-MM-YYYY on the client pc registry and now its working in that pc..
Is there any other way so that the change gets affected globally ??
Any tips
Thanks in adv,
MaheshNLS_DATE_FORMAT can be set in multiple places, but it's not an either/or situation. Setting it in an init parm at the db level is the WEAKEST setting. That setting is overridden by the client OS, which in turn can be overridden by an ALTER SESSION, which in turn can be overridden by use of TO_CHAR and TO_DATE at the individual sql statement. and if the date is being entered by a human at a keyboard (actually keyed in, not picked from a calendar tool or some sort of drop-down pick list) you really have no direct control over the format of the string they key in. So ultimately it is up to the application to insure that character strings presented as dates are in the correct format.
Which is why I advise developers to ALWAYS use to_char and to_date at the sql statement level. It is the only way they can insure control over the setting.

Error - ORA-01843: NOT A VALID MONTH

I get this Error when I execute a procedure which accepts input paramters to insert into a table. I tried using TO_DATE(Input_param,'MM/DD/YY') too but it still gives me the error. Plz. Help.

> However if I make this modification in the values clause of the insert statement
and if I dont used "TO_DATE" function in the procedure call its giving me the above error.
SQL> values(
,TO_DATE(p_date,'DD/MM/YYYY'));
I'm not clear what modification you are making to what. If p_date is a DATE, there should not be a TO_DATE conversion applied to it inside the procedure - it's already a DATE.
How is your case different from the following example?
SQL> CREATE TABLE testit
2 ( id INTEGER, dateval DATE );
Table created.
SQL> CREATE OR REPLACE PROCEDURE testproc
2     ( p_id INTEGER
3     , p_dateval DATE )
4 AS
5 BEGIN
6     INSERT INTO testit (id, dateval)
7     VALUES (p_id, p_dateval);
8 END testproc;
9 /
Procedure created.
SQL> desc testproc
PROCEDURE testproc
Argument Name                  Type                    In/Out Default?
P_ID                           NUMBER(38)              IN
P_DATEVAL                      DATE                    IN
SQL> exec testproc(1, sysdate);
PL/SQL procedure successfully completed.
SQL> exec testproc(2, DATE '2006-03-24');
PL/SQL procedure successfully completed.
SQL> exec testproc (3, TO_DATE('23/03/2006','DD/MM/YYYY'))
PL/SQL procedure successfully completed.
SQL> SELECT * FROM testit;
        ID DATEVAL
         1 24-MAR-2006
         2 24-MAR-2006
         3 23-MAR-2006
3 rows selected.If the procedure parameter is a DATE and the column is also a DATE, there should be no conversion involved. The "Not a valid month" error occurs when you try to convert a string to a DATE using either the wrong format or a nonsense string such as '2005-94-01'. You need to be clear what is a DATE and what is a string at each stage of processing.
Notice that the default date format can be changed:
SQL> ALTER SESSION SET nls_date_format = 'YYYY-MM-DD';
Session altered.
SQL> SELECT * FROM testit;
        ID DATEVAL
         1 2006-03-24
         2 2006-03-24
         3 2006-03-23
3 rows selected.
SQL> ALTER SESSION SET nls_date_format = 'RRRR-MM-DD HH24:MI:SS';
Session altered.
SQL> SELECT * FROM testit;
        ID DATEVAL
         1 2006-03-24 11:55:45
         2 2006-03-24 00:00:00
         3 2006-03-23 00:00:00
3 rows selected.

How to trap 1843 error. .nOT Valid month..

This is in my cursor for loop
mstart_issue := TO_CHAR(to_date(mstart_issue,'YY-MON'),'Mon.YYYY') ;
               mend_issue := to_char(to_date(mend_issue,'YY-MON'),'Mon.YYYY');
But it throws 1843 error..
i Have execptions for finding value error like
when value_error then
warn('value error'||moldmembership);
But i need something to trap the following error ie ..The moment not a valid month error occurs. .It should trap that error
Like warn('not validm onth'||membershpnumber)
What shall be the exeption to catch . .the 1843 error...
Like we got exceptions like when too many rows to catch duplicate records..
And this is how my end_issue data looks like .. . 10-jul
12-Aug date in yy-mon format..
But seems there is error..
Kindly help..
Thanks

susf wrote:
Hi Thanks i am implementing both part of code.. Thanks ..
But ..When i use nls_date_language= 'AMERICAN' I see the output of date in some other language in sql
The output is like this..
Loka .2010
Loka .2010
Loka .2010
Loka .2010
Loka .2010
Loka .2010
Loka .2010
Marras.2010
Marras.2010
Marras.2010which line below generates the output above?
Here is the part of my code
declare
msno sub.sno%type;
e;
mSTART_ISSUE sub.start_issue%type;
MEND_ISSUE SUB.END_ISSUE%TYPE;
MCOMMENTS SUB.COMMENTS%TYPE;
MPCODE SUB.POSTCODE%TYPE;
mpay_mode sub.pay_mode%type;
mrmember sub.rmember%type;
mflag varchar2(1);
cursor c1 is select * from htmldb_collections     where collection_name = 'CSV_DATA' and c001 != 'SNO';
invalid_month exception;
pragma exception_init( invalid_month, -1843 );
begin
mflag := 'N';
          FOR XXX IN C1
               LOOP
               begin
mrmember := xxx.c023;
mstart_issue := xxx.c019;
mend_issue := xxx.c020;
               BEGIN
IF SUBSTR ( UPPER (mstart_issue)
     , -3
     ) IN ( 'JAN', 'FEB', 'MAR'
          , 'APR', 'MAY', 'JUN'
          , 'JUL', 'AUG', 'SEP'
          , 'OCT', 'NOV', 'DEC'
THEN
     MSTART_ISSUE := TO_CHAR(to_date(mstart_issue,'YY-MON','NLS_DATE_LANGUAGE=AMERICAN'),'Mon.YYYY') ;
mflag := 'Y';
ELSE
     warn('not valid month startissue ' || moldmembership);
mflag := 'N';
END IF;
IF SUBSTR ( UPPER (mend_issue)
     , -3
     ) IN ( 'JAN', 'FEB', 'MAR'
          , 'APR', 'MAY', 'JUN'
          , 'JUL', 'AUG', 'SEP'
          , 'OCT', 'NOV', 'DEC'
THEN
     mend_issue := to_char(to_date(mend_issue,'YY-MON','NLS_DATE_LANGUAGE=AMERICAN'),'Mon.YYYY');
mflag := 'Y';
ELSE
     warn('not valid month endissue ' || moldmembership);
mflag := 'N';
END IF;
exception
when invalid_month then
warn('EXCEPTIONnot valid month xx ' || moldmembership);
END;
IF mflag = 'Y' then
               insert into sub (sno,rno,designation,old,start_issue,end_issue,comments,pay_mode,rmember)
               values
               (msno,mrno,mdesignation,moldmem e,maddressedas,madd1,
               madd2,mcounty,mcity,mstate,mcountry,mph_no,memail,mpostcode,mstart_issue,mend_issue,mco );
end if;
exception
when value_error then
warn('value error'||moldmembership);
          end;
END LOOP;
END;

Period Comparison - getting not a valid month error

I am trying to do a period comparison. I have the query condition as
select ppv.draft_invoice_num
,ppv.ra_invoice_number
,ppv.invoice_date
, idv.expenditure_item_date
,ppv.gl_date
,ppv.gl_period
,to_date(ppv.gl_period,'MON-YY')
--,idv.bill_amount
-- ,ppv.org_id
from pa_proj_invoices_view ppv
,pa_proj_invoice_details_view idv
where ppv.project_id= idv.project_id
and ppv.draft_invoice_num = idv.draft_invoice_num
and ppv.project_id = 25
and idv.expenditure_item_date between '01-MAR-09' and '30-APR-09'
and to_date(ppv.gl_period,'MON-YY') between to_date('MAR-09','MON-YY') and last_day(to_date('MAY-09','MON-YY'))
group by ppv.draft_invoice_num
,ppv.ra_invoice_number
,ppv.invoice_date
, idv.expenditure_item_date
,ppv.gl_date
,ppv.gl_period
order by ppv.draft_invoice_num;
I get an "Not a Valid Month" error. How can I do the date comparison? I have tried number of options . How can I compare the ppv.gl_period for a range of periods?
Thanks

Hi,
1)
lv_date := '09/25/2009';lv_date is a variable of datatype date, but you are assigning a varchar, which Oracle is not able to do implicit conversion because of nls_date_format
change to something like to_date('09/25/2009','mm/dd/yyyy')
2)
lv_date:= TO_DATE(lv_date,'MM/DD/YY');
lv_date:= TO_CHAR(lv_date,'MM/DD/YY');Why would be assinging a char value to date datatype. Use any one depending on datatype of lv_date
Regards
Anurag Tibrewal.

Using Oracle OLE DB provider (with ADO) generates error: ORA-01843 while using date

Were using OLE DB provider in order to connect to our Oracle 9i database. When executing the following query in a SQL Plus window I will get the correct results:
SELECT gum_seu_syo_id, seu_userid, seu_first_name, seu_last_name
From group_user_mapping, security_users
Where gum_seu_syo_id = seu_syo_id
and gum_term_date > '8/19/2002'
and gum_seg_syo_id = 11
However if will execute the same query from the our application (VB using ADO) I will get the following error:
ORA-01843: Not a valid month
Checking with our Oracle DBA we made sure my registry is correct and includes the correct format under HEKY_LOCAL_MACHINE\SOFTWARE\ORACLE\ORACLE_HOME,
where the key is NLS_DATE_FORMAT (of type REG_EXPAND_SZ) with the value:
MM/DD/YYYY HH:MI:SS AM
I also run the following query in a SQL Plus window:
select sysdate from dual;
and got the following result:
08/19/2002 10:27:20 AM
which shows that the data format is correct.
Trying to switch between the month and day in the query (put '19/8/2002') worked from the application but generated ORA-01843: Not a valid month in the SQL Plus window.
Any ideas?

try using
to_char function
for eg.
select * from emp where to_char(hiredate,'dd/mm/yy') > '20/3/83'.
Jagriti

Oracle error "ORA-01843: not a valid month" when trying to run sqlldr

Hi all,
I'm trying to load some data into a staging database via a CSV file using sqlldr, and am running into an issue where it doesn't like the date format I'm using.
Here is my input data:
2012-01-09 16:28:12 -05:00Here is the entry in the .ctl file:
created TIMESTAMP WITH TIME ZONE 'yyyy-mm-dd HH24:MI:SS TZR'And finally, here is the entry in the .sql file:
created TIMESTAMP WITH TIME ZONEAfter I try to load, I get greeted with the dreaded error message: Record 1: Rejected - Error on table WTPART, column CREATED. ORA-01843: not a valid month
I'm really confused as to why it's blowing up on the date, because it seems to me that "01" is indeed a valid date in terms of the date format I'm using. Any ideas? Thanks!
Edited by: Nick Tiberi on Jan 10, 2012 8:06 AM

Hmmm, not sure exactly what the problem is. It works fine for me on my XE instance.
Set up the control and data files....
tubby@Tubbz:~/test$ cat >> WTPart.csv <<EOF
2012-01-09 16:28:12 -05:00
EOF
tubby@Tubbz:~/test$
tubby@Tubbz:~/test$ cat >> load.ctl <<EOF
LOAD DATA
INFILE WTPart.csv
APPEND INTO TABLE WTPart
FIELDS TERMINATED BY '|' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
created TIMESTAMP WITH TIME ZONE 'yyyy-mm-dd HH24:MI:SS TZR'
EOF
tubby@Tubbz:~/test$
tubby@Tubbz:~/test$ /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/bin/sqlldr tubby/pswd@xe control=load.ctl
SQL*Loader: Release 10.2.0.1.0 - Production on Tue Jan 10 10:21:28 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Commit point reached - logical record count 1
tubby@Tubbz:~/test$
{code}
Query the result from the database
{code}
ME_XE?select * from wtpart;
CREATED
09-JAN-12 04.28.12.000000 PM -05:00
1 row selected.
Elapsed: 00:00:00.01
ME_XE?
ME_XE?select * from v$version;
BANNER
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Product
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
5 rows selected.
Elapsed: 00:00:00.01
ME_XE?
{code}
Are you sure your CSV file doesn't have some "funky" data in it?

Getting Ora 01843 not a Valid month Error

Hi
I was trying to assign the data in MM/DD/YY format
from a date value '09/25/2009'..
I cannot Obain the result i always get this
ORA-01843: not a valid month
May i ask you kindly to help me out here.
Below is the code Snippet;
DECLARE
lv_date DATE;
BEGIN
lv_date := '09/25/2009';
BEGIN
lv_date:= TO_DATE(lv_date,'MM/DD/YY');
lv_date:= TO_CHAR(lv_date,'MM/DD/YY');
-- I slso tried this way but same error.
-- lv_date := TO_CHAR(TO_DATE(lv_date,'MM/DD/YYYY'),'MM/DD/YY');
END;
DBMS_OUTPUT.PUT_LINE('the date format is = '|| lv_date);
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE ('Err from MainBlock '|| SQLCODE || SQLERRM);
END;

Hi,
1)
lv_date := '09/25/2009';lv_date is a variable of datatype date, but you are assigning a varchar, which Oracle is not able to do implicit conversion because of nls_date_format
change to something like to_date('09/25/2009','mm/dd/yyyy')
2)
lv_date:= TO_DATE(lv_date,'MM/DD/YY');
lv_date:= TO_CHAR(lv_date,'MM/DD/YY');Why would be assinging a char value to date datatype. Use any one depending on datatype of lv_date
Regards
Anurag Tibrewal.

Date error ORA-01843: not a valid month

Hi,
I am in a 4.01 Apex environment with NLS_DATE_FORMAT mm/dd/yyyy. I created a view with a CASE statements using 'when eventstartdate between '08/15/2010' and '06/1/2011' then...' clauses and the view is created fine. I also can query the view with no problem with SQL workshop and the CASE statements work as expected. When I create an interactive report on that view I keep getting ORA-01843: not a valid month. I even tried matching the format in the Interactive Report column format mask to the NLS format for the date and still get error.
What seems especially strange to me is that even if I have the view column defined with a 'to_char' I still get the same error when I use the CASE statement to build the view. Doesn't the Interactive Report just 'see' the View column definitions-- why should it 'care' how the view was built?
The only way I can get the View to work with an Interactive report in any manner is to remove all the CASE statements and define the 'eventstartdate' as text using to_char but that then eliminates my ability to do any filters that require date comparisons with between or '>', '<'.
Help would be appreciated!
Thanks,
Pat

Quick late night response - always convert your dates for comparison. Apples to apples
Instead of between '01/31/2012', use either
TO_DATE('01/31/2012', 'MM/DD/YYYY')or
DATE '2012-01-31'More related info
http://www.grassroots-oracle.com/2011/03/date-format-tolerance.html
Sorry if I'm off target, thought it may help

ORA-01843:This is not a valid month error

One of our french customer using Oracle 11g R2 on RHEL is getting following error while running a stored procedure:
ORA-01843: ce n'est pas un mois valide
20120123::05:41:10 ended rebuilding cmroll table
The error reported by ORACLE, in French « ce n'est pas un mois valide », means : « This is not a valid month ».I have asked him to verify the following settings on his machine:
Please run the following query on Oracle Server to get the NLS settings. It specifies the settings both on Oracle client and Server.
select * from nls_database_parameters;
select * from nls_instance_parameters;
However, you can override this setting by specifying the following environment variables in client or server. So kindly verify them on both as well:
1.     NLS_LANG
2.     NLS_LANGUAGE
3.     NLS_TERRITORYIs there anything further that can help me to trace this error?

Moazzam wrote:
ORA-01843: ce n'est pas un mois valide
Is there anything further that can help me to trace this error?ORA-01843 Sounds a LOT more interesting in French :)
I have to agree with the others that there is a problem with the code somewhere - again, the implicit conversion sounds promising. Or possibly a language issue (hopefully not)
You should be getting a line number where the error is occurring. This can sometimes be deceptive; we use a WHEN-OTHERS exception handler but mark the code with a location marker throughout so we can look up errors and their locations in an exceptions table - in other words, the line cited in the error message may/may not be where the error happened. 11g sometimes reports errors on block headers too. There are other ways of finding the line the error is occurring on too, including just looking at the code (which is usually harder). Start by finding the line the error is occurring at.
The "brute force" approach (if possible find an easier way) is to either use the debugger in a GUI tool or use DBMS_OUTPUT.PUT_LINE to trace your way through executions.
When you find out where the error is occurring you can use DBMS_OUTPUT.PUT_LINE to display the value, find out what it is, and figure out what is causing the error, and fix it.
Edited by: riedelme on Mar 13, 2012 7:11 AM

Not valid month Error Ora 01843

Similar Messages

Maybe you are looking for