12000-12019: Table Snapshots

This section lists messages generated when table snapshots are accessed.

Cause:	An attempt was made to create a snapshot log on a table that already has a snapshot log. Each master table can have only one snapshot log.

Action:	All snapshots on a table can use the same snapshot log for that table. To make changes to the existing log, use the ALTER SNAPSHOT LOG command or drop the snapshot log and create it again.

ORA-12001 cannot create log: table name already has a trigger

Cause:	An attempt was made to create a snapshot log on a table when the table already had an AFTER ROW trigger. Snapshot logs are filled by an AFTER ROW trigger on the master table, so the trigger cannot be created.

Action:	If it is necessary to create a snapshot log, drop the current trigger on the master table.

ORA-12002 there is no snapshot log on table name

Cause:	An attempt was made to drop a snapshot that does not exist.

Action:	Check spelling, syntax, and use an existing snapshot name.

ORA-12003 snapshot name does not exist

Cause:	An attempt was made to reference a snapshot that does not exist.

Action:	Check the name of the snapshot in the statement for typing errors. Retry the statement with an existing snapshot name.

ORA-12004 REFRESH FAST cannot be used

Cause:	An attempt to fast refresh a snapshot was made when the master table for the snapshot has no snapshot log, or the snapshot log cannot be used.

Action:	To REFRESH FAST, first create a snapshot log on the master table. Otherwise, use the REFRESH COMPLETE option of the ALTER SNAPSHOT command. If these options are omitted, Oracle decides the appropriate method for refreshing.

ORA-12005 may not schedule automatic refresh for times in the past

Cause:	An attempt was made to schedule an automated snapshot refresh for a time in the past.

Action:	Choose a time in the future for the automated snapshot refresh.

ORA-12006 a snapshot with the same user.name already exists

Cause:	An attempt was made to create a snapshot with the name of an existing snapshot.

Action:	Create the snapshot using a different name or drop the existing snapshot.

ORA-12007 snapshot reuse parameters are inconsistent

Cause:	During Import or Export, the CREATE SNAPSHOT or CREATE SNAPSHOT LOG.. REUSE command was given inconsistent parameters immediately after the REUSE.

Action:	Other messages will accompany this message. Examine the other messages for a more complete description of the problem.

ORA-12008 error in snapshot refresh path

Cause:	Some problem is preventing the snapshot from reading the view on the master table. A number of events could cause this problem, among them the following:

• The master table no longer exists.

• A column was added to the master table, and the view was not altered.

• The master is at a remote site and inaccessible.

Cause:	An attempt was made to create a snapshot with a long column.

Action:	Do not attempt to create snapshot logs with long columns.

ORA-12010 cannot create snapshot log on table owned by SYS

Cause:	CREATE SNAPSHOT LOG attempts to create a trigger on the table, but triggers cannot be created on SYS tables.

Action:	Do not create snapshot logs on SYS tables.

ORA-12011 execution of num jobs failed

Cause:	Some kind of error was caught in DBMS_IJOB.RUN. One or more jobs that were due to be run produced errors that they could not handle.

Action:	Look at the alert log for details on which jobs failed and why.

ORA-12012 error on auto execute of job num

Cause:	Some kind of error was caught while doing an automatic execute of a job.

Action:	Look at the accompanying errors for details on why the execute failed.

ORA-12013 updatable snapshots must be simple enough to do fast refresh

Cause:	The updatable snapshot query statement is specified with a join, subquery, union, CONNECT BY, ORDER BY, or GROUP BY.

Cause:	Specify a simpler snapshot statement. If a join is needed, create multiple simple snapshots, and then create a view on top of the multiple snapshots.