Hi Bhaskar,
Before running the command to create a replication instance file mumps.repl,
I used to create a new mumps.repl file manually.
While following the given steps, I forgot to create new mumps.repl file and
the secondary server worked.
Thanks
Usha
----- Original Message -----
From: "Bhaskar, KS" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, January 10, 2006 5:25 AM
Subject: Re: [Hardhats-members] Creating a receiver server for replication

> Usha --
>
> I don't know exactly how you got to where you are. A replication
> instance file should not need a rundown except after a crash, and the
> mupip rollback operation should take care of that, so you should never
> have to rundown a replication instance file.
>
> Here is how you create a secondary from a backup of the primary.
>
> 1. Create a replication instance file on the secondary - you can't copy
> this from the primary because the secondary is a separate instance.
mupip replicate -instance_create
>
> 2. Restore the databases from a backup of the primary. If the journal
> file locations are different, use mupip set
> -journal="enable,on,before,file=/path/to/journal/file.jnl" to specify
> the journal file locations on the secondary.
>

> 3. Execute mupip set -replication=on to turn on replication.
>
> 4. Use mupip replicate -receiver with the -updateresync command to start
> replication.
>
> -- Bhaskar
>
> On Sun, 2006-01-08 at 22:01 -0600, Usha wrote:
> > The path of the replication instance file on the secondary is
> > /home/demo/g/mumps.repl.
> > $ cd /home/demo/g
> > $ ls -l
> > total 4076752
> > -rw-rw-rw- 1 demo demo 246268416 Jan 5 12:35
> > demobackup200060105.dat
> > -rwxrwxrwx 1 root root 4169708032 Jan 6 16:27 mumps.dat
> > -rw-rw-rw- 1 demo demo 2336 Jan 6 16:27 mumps.mjl
> > -rw-rw-rw- 1 demo demo 2336 Jan 4 15:27
> > mumps.mjl_2006004152722
> > -rw-rw-rw- 1 demo demo 4896 Jan 5 15:09
> > mumps.mjl_2006005150927
> > -rw-rw-rw- 1 demo demo 2336 Jan 6 14:19
> > mumps.mjl_2006006141903
> > -rw-rw-rw- 1 demo demo 2336 Jan 6 15:29
> > mumps.mjl_2006006152924
> > -rwxrwxrwx 1 demo demo 44 Jan 6 16:19 mumps.repl
> > $ mupip rundown -file mumps.repl
> > mumps.repl -> Error reading from file.
> > Success
> > %GTM-W-MUNOTALLSEC, WARNING: not all global sections accessed were
> > successfully rundown
> > $
> > Usha
> > ----- Original Message -----
> > From: "Bhaskar, KS"
> > To:
> > Sent: Saturday, January 07, 2006 1:11 AM
> > Subject: Re: [Hardhats-members] Creating a receiver server for
> > replication
> >
> > > Did you create a replication instance file on the secondary?
> > >
> > > -- Bhaskar
> > >
> > > On Fri, 2006-01-06 at 04:57 -0600, Usha wrote:
> > > > After the first block over, this seems to be the next one at the
> > > > secondary server
> > > >
> > > > $mupip replicate -receive -start -listenport=9300 -buf=1
> > > > -log=receive.log -updateresync
> > > > %GTM-E-REPLREQRUNDOWN, Error accessing replication
> > > > instance /home/demo/g/mumps.repl. Must be rundown on cluster node
> > > > local.cmpio.org.
> > > > $ mupip rundown -file "g/mumps.repl"
> > > > g/mumps.repl -> Error reading from file.
> > > > Success
> > > > %GTM-W-MUNOTALLSEC, WARNING: not all global sections accessed were
> > > > successfully rundown
> > > > $ mupip integ -full -file "g/mumps.repl"
> > > > g/mumps.repl -> Error reading from file.
> > > > Success
> > > > %GTM-I-MUSTANDALONE, Could not get exclusive access to
> > g/mumps.repl
> > > > %GTM-E-INTEGERRS, Database integrity errors
> > > > $
> > > >
> > > > Shutting and starting the system again does not help. How can this
> > be
> > > > rectified?
> > > >
> > > > Regards
> > > > Usha
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc. Do you grep through
> > log
> > files
> > > for problems? Stop! Download the new AJAX search engine that makes
> > > searching your log files as easy as surfing the web. DOWNLOAD
> > SPLUNK!
> > > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> > > _______________________________________________
> > > Hardhats-members mailing list
> > > Hardhats-members@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/hardhats-members
> > >
> > >
> > >
> >
> >
> >
> >
> > Make sure YOUR emails don't get lost!Download Mailinfo here
> > ------------------------------------------------------- This SF.net
> > email is sponsored by: Splunk Inc. Do you grep through log files for
> > problems? Stop! Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> > http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
> > _______________________________________________ Hardhats-members
> > mailing list Hardhats-members@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/hardhats-members
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Hardhats-members mailing list
> Hardhats-members@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
>
>
>



Make sure YOUR emails don't get lost! Download Mailinfo here ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to