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

Hi,

The ownership didn't change.

I originally implemented the standby database using ALTER DATABASE BACKUP CONTROL FILE TO '/mycontrolfile.ctl' REUSE; and manually applied the archivelog files every day. One day I lost one of the archivelogs and had to redo the standby database. So I decided to use ALTER DATABASE CREATE STANDBY CONTROLFILE AS '/stby_mycontrolfile.ctl' REUSE;,
implement managed recovery, and further multiplex the archived redo logs.

'Curious thing about the Solaris operating system. If you copy one file over the other, the copied file retains the ownership and permissions of the original.
Being that there was no original for stby_mycontrolfile.ctl, the ownership took on my userid and group. An oversight on my part. Yes, I was a bad DBA; a very bad, bad DBA for not checking on that.

So the moral of the story is to always check ownership and permissions of your files, even if you're 101% sure that it's correct.

It wasn't the ownership that changed.
It was I who failed to change the ownership.

-- 
WARNING:
DO NOT REPLY TO THIS EMAIL
Reply to me only on this newsgroup
<yong321_at_yahoo.com> wrote in message 
news:1107980789.042878.6490_at_z14g2000cwz.googlegroups.com...


> Andreas Sheriff wrote:

> ...

>> I checked the permissions and ownership of the standby control file.
>> It had the right permissions, but the wrong ownership and group


> information.

> ...

>> 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.
>


> If you ever find out why the ownership got changed, please post back.

> Thanks.

>


> OS version difference just adds one more factor to your troubleshooting

> process. Once we cloned a big database from Solaris 2.6 to Solaris 8

> without any problems.

>


> If you see "Code xxxx" and interpreting it as ORA-xxxx doesn't work,

> try other facilities such as TNS-xxxx. Sometimes that error number is

> an OS error code. You can find the description of it by looking at

> platform-specific errno.h file on UNIX, or by "net helpmsg xxxx" on

> Windows. A generic way is to run the Perl one-liner: perl -e '$^E=123;

> print $^E' (change ' to " on Windows).

>


> Yong Huang

> yong321ATyahoo.com

>