Database Error Messages

PREPARE_REFRESH found that there was no materialized view (MV) registered for synchronous refresh that contained the specified fact table as one of its base tables and the changes to the dimension tables contained updates or deletes. This error will not occur if the changes to the dimension tables contain only inserts.

There are many ways to handle this situation. Refer to the documentation for details.

One way is to unregister all MV's, drop staging logs on the tables or alter them to ordinary logs and apply the changes to the tables. Then the MV's can be refreshed using conventional methods instead of synchronous refresh. If desired, the staging logs on the tables can be re-created and the MV's can be registered for synchronous refresh.

Another way is to register a MV which references the specified fact table for synchronous refresh. If no such MV exists, the user can first create one before registering it.

PREPARE_REFRESH found that there was no materialized view (MV) registered for synchronous refresh that contained the specified fact table as one of its base tables and the changes to the dimension tables contained updates or deletes. This error will not occur if the changes to the dimension tables contain only inserts.

There are many ways to handle this situation. Refer to the documentation for details.

One way is to unregister all MV's, drop staging logs on the tables or alter them to ordinary logs and apply the changes to the tables. Then the MV's can be refreshed using conventional methods instead of synchronous refresh. If desired, the staging logs on the tables can be re-created and the MV's can be registered for synchronous refresh.

Another way is to register a MV which references the specified fact table for synchronous refresh. If no such MV exists, the user can first create one before registering it.

PREPARE_REFRESH found that there was no materialized view (MV) registered for synchronous refresh that contained the specified fact table as one of its base tables and the changes to the dimension tables contained updates or deletes. This error will not occur if the changes to the dimension tables contain only inserts.

There are many ways to handle this situation. Refer to the documentation for details.

One way is to unregister all MV's, drop staging logs on the tables or alter them to ordinary logs and apply the changes to the tables. Then the MV's can be refreshed using conventional methods instead of synchronous refresh. If desired, the staging logs on the tables can be re-created and the MV's can be registered for synchronous refresh.

Another way is to register a MV which references the specified fact table for synchronous refresh. If no such MV exists, the user can first create one before registering it.