Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Standby databases and different sids

Re: Standby databases and different sids

From: Juhan Kundla <juhan_at_ensib.NICHT-SPAM.ee>
Date: Fri, 13 Oct 2000 15:47:53 +0200
Message-ID: <39E71289.D06916FA@ensib.NICHT-SPAM.ee>

Well, Oracle docs say:

"Primary and standby databases must have the same version, release and patch for:
- Oracle RDBMS and
- Operating System".

So upgrade your Standby to Solaris 8. AFAIK it is not required, that stanby db has the same sid, as primary, although it is recommended.

HTH,
Juhan

williamhargrove_usenet_at_hotmail.com wrote:
>
> Hello All,
>
> I am trying to set up a standby database, using Oracle 8.1.6 on Solaris
> 8 and 7
> (the production machine is running 8 - it is actually a development
> machine,
> and the standby machine - even more of a development machine is running
> 7.)
>
> The instance on the production machine is called 'td4', and the instance
> on the standby is
> called 'td6'. And I think this is probably the cause of the problems
> that I am having. I've
> copied the datafiles, redo logs, and archived redo logs from the
> production server, and
> the standby control file that I have created on the production server,
> and placed then on
> the standby machine, update the init.ora files on both machines, to copy
> log files via net8
> and for the standby machine to read the standby control files and
> standby log archive dest.
> I also copied the production init.ora file to the standby machine, and
> changed the references
> to the sid and db_name from td4 to td6.
>
> So I go to startup the standby dd, and get the error below. Thinking
> about what has hapenned
> here, I have taken a standby control file from the production machine,
> which thinks the sid
> and db are called 'td4' and placed them on a machine with an identical
> db that I have created
> using the scripts from the production machine, but with a sid set to
> td6, and no wonder
> it doesn't work. The control files say td4, but the ORACLE_SID says td6,
> and so does the
> init.ora file
>
> So, does the sid on the standby machine have to be the same as the
> production machine, so the
> standby control files think it is the 'same' database? And furthermore,
> is there any need
> to even bother using dbassist / running scripts to create a new database
> on the standby
> machine, since I am going to be copying the files over from the
> production machine and
> replacing the ones what I will have just created.
>
> Connected to an idle instance.
>
> SQL> startup nomount
> pfile=/opt/oracle/OraHome1/admin/td6/pfile/inittd6.ora
> ORACLE instance started.
>
> Total System Global Area 166301680 bytes
> Fixed Size 69616 bytes
> Variable Size 63651840 bytes
> Database Buffers 102400000 bytes
> Redo Buffers 180224 bytes
> SQL> alter database mount standby database;
> alter database mount standby database
> *
> ERROR at line 1:
> ORA-01103: database name 'TD4' in controlfile is not 'TD6'
>
> SQL> quit
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
 

-- 
+-----------------+
|NB! Please remove|
|   .NICHT-SPAM   |
|  when replying  |
|    to get my    |
|     *REAL*      |
| e-mail address! |
|                 |
|  Cheers, Juhan  |
+-----------------+
Received on Fri Oct 13 2000 - 08:47:53 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US