RMAN problem

Hello,

Until today our RMAN backup policy has been working fine (about 6 months) - however recently I spotted the following error message, and am wondering what to do ......

channel d1: starting piece 1 at 15-JUN-06
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10006: error running SQL statement: select sofar, context, start_time     from v$session_longops    where (start_time > nvl(:1, sysdate-100)  or            start_time = nvl(:2, sysdate+100)) and          sid = :3 and          serial# = :4 and          opname like 'RMAN:%'    order by start_time desc, context desc
RMAN-10002: ORACLE error: ORA-01041: internal error. hostdef extension doesn't exist
Alistair_WilliamsAsked:
Who is Participating?
 
RomModConnect With a Mentor Commented:
Question closed - 250 points refunded.

Best regards,
RomMod
Experts Exchange
Community Support Moderator
0
 
MohanKNairCommented:
>> ORACLE error: ORA-01041: internal error. hostdef extension doesn't exist

There is some problem with either the target database or the database of RMAN schema. See if it is possible to query the database. Otherwise you may have to restart the database.
0
 
Alistair_WilliamsAuthor Commented:
Hi,

Yes I can connect to the data base and do a query, all seems to be o.k. apart from the RMAN bit. I can even connect to the target via RMAN.

Thanks

Alistair
0
Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

 
MohanKNairCommented:
What about catalog database? What is the value for REMOTE_LOGIN_PASSWORDFILE in catalog DB?

Also check the value for LARGE_POOL_SIZE in target DB and if it too low increase the value.
0
 
Alistair_WilliamsAuthor Commented:
We are not using a cataloge at the moment. I have found this article on metalink though - any coments ?!?

<Bug:3123232> It is possible for longop statistics to be corrupted and possibly
cause internal errors or core dumps.
eg: Dumps when selecting from v$session_longops/x$ksulop
ORA-600 [ksuloget] during or after a 'long op' (eg, RMAN operation)

This problem can also result in NULL values in V$SESSION_LONGOPS.


Solution
----------
Bug 3123232 is fixed in 9.2.0.6 so apply 9206 PSR or use the workaround:

Add to the init.ora/spfile  of the target database

Switch off long-op statistics by setting the following (9.2 specific) settings in the (s)pfile :
optimizer_features_enable=9.2.0.1
_subquery_pruning_mv_enabled=false

Instance will have to be restarted.

0
 
actonwangCommented:
make sure you've use decidated connection instead of shared server connection.
0
 
Alistair_WilliamsAuthor Commented:
It would certainly seem that v$session_longops is corrupt. If I query the table, then I get a end of communication on channel error. Is their anyway of flushing this table ?

0
 
Alistair_WilliamsAuthor Commented:
It would seem that the suggested method from metalink has worked - so I think I have answered my own question here.

Switch off long-op statistics by setting the following (9.2 specific) settings in the (s)pfile :
optimizer_features_enable=9.2.0.1
_subquery_pruning_mv_enabled=false

Restart Instance.

Thanks

Alistair
0
 
actonwangCommented:
which metalink note you were referring to? please share.
0
 
Alistair_WilliamsAuthor Commented:
Hi,

The doc id from metalink is Note:341184.1

Thanks

Alistair
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.