Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> 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.
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
-- http://www.freelists.org/webpage/oracle-l Received on Mon Oct 29 2007 - 15:02:21 CDTThe 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@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 viceversa...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 forthetype of application that "$ORACLE_HOME/bin/rman"? I'm thinking that perhaps LD_LIBRARY_PATH or SHLIB_PATH (or whateverisappropriate for your platform) is pointing to the wrong shared libraries... Just a guess....