RE: RMAN "Memory fault"

From: <Joel.Patterson_at_crowley.com>
Date: Mon, 29 Oct 2007 16:42:05 -0400
Message-ID: <0684DA55864E404F8AD2E2EBDFD557DA3AA7FF@JAXMSG01.crowley.com>

Joel Patterson
Database Administrator
joel.patterson_at_crowley.com
x72546
904 727-2546

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Tim Gorman Sent: Monday, October 29, 2007 4:02 PM
To: Herring Dave - dherri
Cc: oracle-l
Subject: Re: RMAN "Memory fault"

LD_LIBRARY_PATH and/or SHLIB_PATH are UNIX environment variables, and easy to get wrong when switching environments, unless you've got your environment-setting scripts solid.

Also, could be fun to compare "ulimit -a" output in the environment where it works and where it doesn't...

Database parms are almost certainly blameless for this type of error. It is probably environment (i.e. env variables, process limits, etc) or it could be an executable shared-library file that's been overwritten or had it's permissions hosed, or something like that. That's why I suggest running "file" against each of the shared libraries returned in the "ldd" command -- one of those shared libraries might just come back as "data" instead of "executable", indicating that someone or something reset permissions so the file is no longer executable, for example...

Might also try something like the following:

for _Dir in `echo $LD_LIBRARY_PATH | sed 's/:/ /'` do

echo "\nSearching \"${_Dir}\" for files newer than \"\$ORACLE_HOME/bin/rman\"..."

find ${_Dir}-name "*.so" -newer $ORACLE_HOME/bin/rman -exec ls -l {} \;
done

On the off-chance that a shared-library used by RMAN is newer than the RMAN executable file...

Herring Dave - dherri wrote:

The platform is 64-bit. We've got 2 databases on this server, one working fine with the RMAN "DELETE OBSOLETE" command, the other not. My assumption is that something has passed a threshold causing this error. No database parameters have been changed from when this command worked until it doesn't.

I did validate that the "ldd" command comes back clean, though.

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: Tim Gorman [mailto:tim_at_evdbt.com]
	Sent: Monday, October 29, 2007 2:32 PM
	To: Herring Dave - dherri
	Cc: oracle-l
	Subject: Re: RMAN "Memory fault"
	 
	Not sure what platform you're on, but it sounds to me like a
64-bit
	shared library being referenced by a 32-bit executable.  Or vice

versa...

Have you used "ldd $ORACLE_HOME/bin/rman" and seen it come back clean

without error messages? Have you used the UNIX command "file <xxx>"

	where "<xxx>" is the filename of the RMAN
	executable as well as each of the shared libraries displays by

the

"ldd"

command, and had the output from the "file" come back consistent for

the

type of application that "$ORACLE_HOME/bin/rman"?

I'm thinking that perhaps LD_LIBRARY_PATH or SHLIB_PATH (or whatever

	appropriate for your platform) is pointing to the wrong shared
	libraries...
	 
	Just a guess....

http://www.freelists.org/webpage/oracle-l

--
http://www.freelists.org/webpage/oracle-l

Received on Mon Oct 29 2007 - 15:42:05 CDT