FAQ
In working with Oracle on this issue, they had me recreate my controlfiles, then add a second channel allocation as part of the DELETE OBSOLETE, this one to disk.

All backups perform the following as their last step:

SQL 'ALTER SESSION SET tracefile_identifier=CONTROLFILE';
SQL 'ALTER DATABASE BACKUP CONTROLFILE TO trace';

... and for some reason not being able to automatically remove obsolete versions of this controlfile backup was part of the problem.

Thanks to all who helped. Now onto the next problem...

Dave

David C. Herring, DBA | A c x i o m Delivery Center Organization

630-944-4762 office | 630-430-5988 wireless | 630-944-4989 fax
-----Original Message-----
From: Herring Dave - dherri
Sent: Monday, October 29, 2007 12:34 PM
To: oracle-l
Subject: RMAN "Memory fault"

Folks,

I've got a regular job to delete obsolete pieces from our RMAN catalog,
which now is failing with "Memory fault". The system is Tru64 5.1b
running Oracle 9.2.0.6 and the RMAN catalog is 10.2.0.2. Backups are to
tape using Legato Networker 7.1.1.

The procedure is very simple, just connecting to the target and catalog,
allocating a channel and deleting:

CONNECT CATALOG ../..@..
CONNECT TARGET ../..@..
ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE sbt_tape;
DELETE NOPROMPT OBSOLETE;
The ONLY thing I get back is:

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 4
Memory fault

No Oracle errors show up in either database. I can't find messages or
info anywhere as to why this is happening. I tried setting my retention
to larger numbers, thinking there's too many pieces to delete, but that
didn't work. Current retention is 4 copies. I also tried using RECOVERY
WINDOW TO xxx DAYS, which failed too. I even truss'ed the session and it
ends with:

...
write(10, "\0BD\0\006\0\0\0\0\003 ^".., 189) = 189
read(10, "01 m\0\006\0\0\0\0\00701".., 2064) = 365
write(10, "\0BD\0\006\0\0\0\0\003 ^".., 189) = 189
read(10, "01 t\0\006\0\0\0\0\00701".., 2064) = 372
Incurred fault #32, FLTBOUNDS %pc = 0x000000012105DD84 addr =
0x000000011FFF4D00
Received signal #11, SIGSEGV [default]
siginfo: SIGSEGV SEGV_MAPERR addr=0x0000000000000058
Err#11 Error 11 occurred.
*** process killed ***

Anyone run into something similar or have any good suggestions of what
else to check?

Dave
___________________________________
David C. Herring, DBA  |   A c x i o m  Delivery Center Organization
630-944-4762 office | 630-430-5988 wireless | 630-944-4989 fax
The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be legally
privileged.

If the reader of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.

If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.

Thank You.

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouporacle-l @
categoriesoracle
postedNov 5, '07 at 2:02p
activeNov 5, '07 at 2:02p
posts1
users1
websiteoracle.com

1 user in discussion

Herring Dave - dherri: 1 post

People

Translate

site design / logo © 2022 Grokbase