Jeg sidder med nogle natlige oprydnings scripts, der bl.a. rydder op i vores cache. Grundet ORA-00054: resource busy and acquire with NOWAIT specified, sidste uge ved oprydning, valgte vi før oprydning at lave følgende

  1. lock table "&2".TABELNAVN in exclusive mode
  2. truncate table "&2".TABELNAVN

Dvs. ORA-0054 havde åbenbart generet en del uger, og ingen kommentarer hertil :)

Definitionen af ORA-01466 er;

Error:  ORA 1466
Text:   unable to read data -- object definition has changed
------------------------------------------------------------------------------------------------------------------------------------------------
Cause:  This is a time-based read consistency error for a database object,  such as a table or index. Either of the following may have happened: The query was parsed and executed with a snapshot older than the time the object was changed.

The creation time-stamp of the object is greater than the current system time.  This happens, for example, when the system time is set to a time earlier than the creation time of the object.

Action: If the cause is an old snapshot, then commit or rollback the transaction and resume work. a creation time-stamp in the future, ensure the system time is set correctly. If the object creation time-stamp is still greater than the system time, then export the object's data, drop the object, recreate the object so it has a new creation time-stamp, import the object's data, and resume work.

Det er jo forsåvidt rimeligt at antage og undersøge, om der er et problem eftersom det blot er en uges tid siden, der havde været daglige ORA-0054. Men prøv at læse definitionen ovenfor, og jvf. med vores cron.

"The creation time-stamp of the object is greater than the current system time.  This happens, for example, when the system time is set to a time earlier than the creation time of the object."

Oprettelse tidspunkt > systemtid ....... Hmmmmm har vi lige været udefor noget med ændring af tid, som i en time tilbage.

Præsis ....... Vintertid.