RE: rman errors
Date: Sat, 28 Feb 2009 16:43:14 -0500
I looked and it has some dates of yesterday, some of today and dates all over the place. Should they all be the same? I just don't know what to look for any more. Is there something that needs to be done to rman after an upgrade or patch? I don't recall doing it on my test box though. I looked at the patch logs and other than OCM being configured and not running, there are no errors or other warnings.
From: Mark W. Farnham [mailto:mwf_at_rsiz.com] Sent: Saturday, February 28, 2009 12:07 PM To: tanel_at_poderc.com; Zelli, Brian; 'Oracle-L Group' Subject: RE: rman errors
What Tanel wrote, plus, a common reason for the patched binary(ies) to
not actually get slapped into place is if another instance on that node
is running the same binary (or one of the tools is being executed while
the relink is supposed to happen). Less common is an improperly killed
process still having a file handle on the executable that you're trying
I would think your logs from patching would show the failure, but looking at the date last modified for the files in your "oracle" bins and library might also be useful.
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Tanel Poder
Sent: Saturday, February 28, 2009 7:51 AM To: Brian.Zelli_at_RoswellPark.org; 'Oracle-L Group' Subject: RE: rman errors
Every parameter has an internal constant number associated with it. These numbers may change between releases/patchsets as new parameters are added (and some removed).
The Oracle binary patching works roughly like this on Unix:
- replace the Oracle kernel module files (.o or .so files) in libserver.a with new versions
- relink Oracle and tools (relink takes the module files from libserver.a and links them to oracle binary)
So I suspect something failed either in step 1 or 2.
You can start with relinking Oracle binary and all the tools (rman too).
If it still doesn't work, then compare the contents of libserver.a's on both installations.
Btw, are you running RMAN from the patched Oracle home and not the old one, right?
-- Regards, Tanel Poder http://blog.tanelpoder.comReceived on Sat Feb 28 2009 - 15:43:14 CST
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Zelli, Brian
> Sent: 28 February 2009 13:46
> To: Oracle-L Group
> Subject: rman errors
> I upgraded yesterday from 10.2.0.1 to 10.2.0.4 and now I get this
> error when running rman:
> RMAN-10002: ORACLE error: ORA-00096: invalid value SIGNATURE for
> parameter remote_dependencies_mode, must be from among 10.2.0.4.1,
> 10.2.0.4, 10.2.0.3,10.2.0.2 , 10.2.0.1, 10.1.0.5, 10.1.0.4, 10.1.0.3,
> 10.1.0, 126.96.36.199, 9.2.0, 9.0.1, 9.0.0, 8.1.7, 8.1.6, 8.1.5, 8.1.4,
> 8.1.3, 8.1.0
> I set the init parameter remote_dependencies_mode=SIGNATURE
> and that still failed with the same error.
> I set it back to TIMEZONE which is the default and that doesn't
> work.Docs say it's one or the other.
> What am I missing?
> Funny thing is I upgrade another instance earlier in the week that was
> exactly the same and I am not having this problem.
-- http://www.freelists.org/webpage/oracle-l This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited. If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you. -- http://www.freelists.org/webpage/oracle-l