ORA-01841 when refreshing materialized view

Question

Hi,
I have to upgrade my database from oracle 8.1.7.4 to 9.2.0.1.
I have tested two ways to do it :
1) I upgraded my database from 8i to 9i with the u0801070.sql script.
2) I created an empty 9i database and then I exported the data from the 8i database and imported them to the 9i database.
The two procedures worked fine.
But now, when I try to refresh the mateiralized views with DBA Studio on the database upgraded via export/import, I obtain the error : ORA-01841.
On the database upgraded via u0801070.sql, I don't have the problem.
Why do I have this error ?
Regards,
Rachel TREBUCHET DANJOU

Answer 1

Error: ORA 1841
Text: (full) year must be between -4713 and +4713 / +9999
Cause:
Action:
*** Important: The notes below are for experienced users - See Note 22080.1
Explanation:
     Eg: In a clause like "to_date('XXXX','YYYY')" XXXX is outside of the
     range -4713 and +4713.
     Note that Year 0 is invalid too. See Bug 106242 for an explanation..
     Typically this involves "to_date('00','YYYY')" or similar which is
     invalid. It is probably better to use 'RR' rather than 'YY' which
     prefixes with an appropriate century.
     Eg:
          select to_char(to_date('00','yyyy')) from dual;
          ORA-01841: (full) year must be between -4713 and +4713
          select to_char(to_date('00','rr')) from dual;
          01-MAR-2000
Year 2000
~~~~~~~~~
You may also see this error if using a TO_DATE() function
on a date column (or SYSDATE) and your sessions NLS_DATE_FORMAT
includes a 2 digit year mask (RR or YY).
eg: alter session set nls_date_format='DD-MON-RR';
select to_date(sysdate,'DD-MON-YYYY') from dual;
"ORA-01841: (full) year must be between -4713 and +9999, and not be 0"
This is because TO_DATE() expects to work on a CHARACTER
data type and so there is an implicit conversion from
DATE to CHAR.
eg: In the above example SYSDATE of 01-JAN-2000 is implictly
converted to the character string "01-JAN-00", which is
then converted back to a date using a DD-MON-YYYY date format.
This gives a year of 0000 which is invalid, hence ORA-1841.
Note:     From Oracle 7.2 onwards the UPPER bound is +9999 and not +4713
Regards,
Reza