When running copy, the following errors are observed:
sp_ctrl (bg570b18:2100)> copy status
Job ID : 1
Host : host_name
Started : 04-JUN-07 14:02:00
Job Type : Copy
Status : Failed
EXP-00008: ORACLE error 1466 encountered
See sync_svr_1 log file for details
ID Tablename Total Rows %Comp Status Status Time Total Time
------ ------------------------------------ ---------- ----- ---------- ----------- ----------
1 OWNER.table_name 8 Failed N/A 0:07
The copy server log shows the following errors:
Mon Jun 04/14:02:10.387:: 003: Error/Warning Detected: EXP-00008: ORACLE error 1466 encountered
Mon Jun 04/14:02:10.387:: 003: ERROR: Stopping export thread - EXP-00008: ORACLE error 1466 encountered at sync/svr/sync_export_thread.cpp:627
Mon Jun 04/14:02:10.394:: 003: WARNING: Sent a server control stop message (line=638) at sync/svr/sync_export_thread.cpp:676
Mon Jun 04/14:02:10.394:: 003: WARNING: Thread asked to stop, stopping export at sync/svr/sync_export_thread.cpp:266
Mon Jun 04/14:02:10.394:: 003: WARNING: Sent a server control stop message (line=268) at sync/svr/sync_export_thread.cpp:676
Mon Jun 04/14:02:10.394:: 003: External process pid = 884838 sent SIGTERM
Mon Jun 04/14:02:10.414:: 003: Export process returned status: 0
Mon Jun 04/14:02:10.496:: ERROR: A thread failed on target at sync/svr/sync_svr_messager.cpp:745
Mon Jun 04/14:02:10.500:: Abort remaining threads
The error is caused when the creation timestamp of the table is in a future time.
This error is typically observed when the the creation timestamp of the table is in a future time. The following query will return all such tables that meet this criterion:
select owner, object_name from dba_objects
where created > sysdate
or last_ddl_time > sysdate;
If the object on which the copy failed is returned by this query, then it needs to be dropped and recreated with the current sysdate. The issue occurs on systems where the sysdate may be changed frequently and in the process some objects may get created in future time when the sysdate is restored back to normal after being advanced earlier.
Objects that are returned by this query will need to be exported off dropped and recreated with the current sysdate. This issue is most common on development boxes where the sysdate is changed.
The resolution applies to a specific situation. There may be other reasons for encountering ORA-01466.
The following are details on the ORA-01466. Please note that not all of them may apply to the situation.
ORA-01466: unable to read data - table definition has changed
Cause:
Oracle has detected a problem when trying to read the database table (or index). The creation timestamp of the table (or index) is in the future.
Possible remedies:
According to Oracle this could be caused by a long running snapshot. Try committing or rolling-back all outstanding transactions and try again.
The system time has been changed. Oracle suggest exporting the affected tables, dropping the tables and importing them.
If this error is encountered when trying to export tables then try exporting the tables without the flag consistent=Y.
