Re: Standby database problem - ARC0: Error closing standby archivelog file at host 'myhost.name.com' Code '210'

Thank you.
That bit of insight helped tremendously.

I queried v$archive_dest on the production and it gave me the ora-0210 error for the standby dest.
I checked the permissions and ownership of the standby control file. It had the right permissions, but the wrong ownership and group information.

I changed the ownership and group to oracle:dba and the managed recovery mode now works.
Incidentally, as for the requirements for the same O/S version, I still have the production on Solaris 2.6 and standby on Solaris 8, so I guess that requirement was more like a guide rather than a hard coded rule. :-D

In future reference, I guess when I see an error of the format Code xxxx, I should interpret it as error ora-xxxx.

Thanks for all your help!

-- 
WARNING:
DO NOT REPLY TO THIS EMAIL
Reply to me only on this newsgroup
"Sybrand Bakker" <sybrandb_at_hccnet.nl> wrote in message 
news:vnlk01doaprddi51hv0p032k75493mqb08_at_4ax.com...


> On Tue, 8 Feb 2005 16:39:11 -0800, "Andreas Sheriff"

> <spamcontrol_at_iion.com> wrote:

>

>>What am I doing wrong?  What?  What?

>

> One general requirement for standby databases is they run the same

> database and O/S version.

> I don't know from the top of my head what ora-0210 is, but I do know

> it does exist, and has to do with archiving.

> You could also query v$archive_dest on both your databases (even on

> the standby one) to see what is going on.

>

>

> --

> Sybrand Bakker, Senior Oracle DBA