Or just create the new mountpoint as a symbolic link pointing to somewhere
with some free space - that way a full refresh won't be such a big deal, and
the datafiles could be copied back directly to the original server without
any need to do anything else.
They are a lot of fun, these standby databases, but need careful management
and planning.
"-=-> ^~^ Rikoos ^~^ <-=-" <nospam_rick_at_rikoos.com> wrote in message
news:394hevodnengq9tqrd2jm6l19q17mc1s71_at_4ax.com...
> Hello,
>
> i got a small question:
>
> I have 2 sun servers. 1 is the host for the primary (PRD1) database.
> the second is just for a hot standby and it used to work great. But
> now i have a problem. One extra disk is added to the primary because
> there was no space left on this machine (the is one extra database
> running on this machine).
>
> The uses to have identical mount pount (/u01, /u02, etc....) but no
> the primary has one extra mount point (/u05). The secondary has this
> mount point not.
>
> One datafile is now on this mount point and the hot standby is
> compaining now that he doesn't have this mount point.
>
>
> How can i solve this ?
>
>
> Please help?
>
Received on Fri Jun 13 2003 - 20:10:17 CDT
