Re: v$rman_status problem

Hi Steve,

I've got the answer from the Oracle support. In my case was enought just to delete the statistics against the base tables of the V$RMAN_STATUS view. Below is the complete answer from the TAR:

"Similar incidents were resolved by deleting the statisicts on v$rman_status base tables, please perform the following action plan: .
ACTION PLAN

1. Exec dbms_stats.delete_table_stats('SYS', 'X$KRBMRST')
2. Exec dbms_stats.delete_table_stats('SYS', 'X$KSFQP ')
3. Exec dbms_stats.delete_table_stats('SYS', 'X$KCCRSR')
4. Retry quering v$rman_status, and the normal operations."

Best regards,
alec.

Steve Howard wrote:
> alek wrote:
> > Hi Steve,
> >
> > and thanks for your reply. The Oracle guy's answer is really amazing
> > because, in our case, a high availability solution is involved and
> > recreating the control file cannot be easily done on our side. I will
> > open a TAR to see if I receive the same answer as you.
> >
>
> alek,
>
> I should note that re-creating it did, in fact, solve our probelm. I
> just wanted a better answer as to the root cause. Hopefully, you'll
> get one, and if you do, please post back.
>
> Regards,
>
> Steve
Received on Tue Jul 11 2006 - 04:12:53 CDT