Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Oracle snapshot refresh problem

Posted on 2010-11-18
4
Medium Priority
?
1,265 Views
Last Modified: 2012-08-14
Hi,
When we refresh snapshots using dbms_refresh.refresh stored procedure, it always fails at a table "AXIUM"."ODLIMITS" with the following error message:
     ERROR: ORA-32320: REFRESH FAST of "AXIUM"."ODLIMITS" unsupported after container table PMOPs.
After I dropped/re-created both snapshot log in database A and snapshot in database B, the refresh can work for about 1 day, and then fails again after 1day.
The following are the commands to create snapshots and snapshot logs:
(1)In database A: create materialized view log on <tablename> tablespace <tablespacename>;
(2)In database B: create materialized view <tablename> on prebuilt table
        refresh fast
        start with sysdate + 1/288
        enable query rewrite
        as select * from <tablename>@prod;

Thanks a lot for your help,
Luchuan



0
Comment
Question by:luchuanc
  • 2
  • 2
4 Comments
 
LVL 35

Expert Comment

by:johnsone
ID: 34168242
According to the documentation, that would mean some sort of partition maintenance operation has occurred.  Try using the procedure call listed in the actions to see what was done.


ORA-32320:
REFRESH FAST of "string"."string" unsupported after container table PMOPs
Cause:       A Partition Maintenance Operation (PMOP) has been performed on the materialized view, and no materialized view supports fast refersh after container table PMOPs.
Action:       Use REFRESH COMPLETE. Note: you can determine why your materialized view does not support fast refresh after PMOPs using the DBMS_MVIEW.EXPLAIN_MVIEW() API.
0
 

Author Comment

by:luchuanc
ID: 34168696
Hi johnsone:,
I ran DBMS_MVIEW.EXPLAIN_MVIEW() for this snapshot and another snapshot that has no problem, did comparison. Results look similar for them in mV_CAPABILITIES_TABLE. This snapshot was created using the same command for other snapshots that are all fine.
Thanks,

Luchuan
0
 
LVL 35

Accepted Solution

by:
johnsone earned 1500 total points
ID: 34172958
According to the message, it has nothing to do with how the snapshot was created.  It has to do with some partition maintenance that was done.
0
 

Author Closing Comment

by:luchuanc
ID: 34219149
Hi,
I ran a refresh complete command in database, and that seems solved problem.
Thanks for your help
Luchuan
0

Featured Post

[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Checking the Alert Log in AWS RDS Oracle can be a pain through their user interface.  I made a script to download the Alert Log, look for errors, and email me the trace files.  In this article I'll describe what I did and share my script.
When it comes to protecting Oracle Database servers and systems, there are a ton of myths out there. Here are the most common.
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…

564 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question