problem restoring db
Dean Browett
I am new to db2 and I have hit a bit of a problem.
I have backed up one of our system databases and copied the resultant file
to another server running db2. When I try and restore the database on this
machine I get the error:
db2 => restore database BOL taken at 20010622153359 to /home/db2inst1 into
TESTDB with 2 buffers buffer 1024 without prompting
SQL2546N The image on media "/home/db2inst1" is not the first in sequence
from the backup or copy.
I have tried this with more recent backups with the same result. I need to
be able to shutdown the master db server (from which the back up was taken)
to carry out some essential work and I need the database running on another
machine.
I have tried creating an ixf file, but for some reason this crashes db2
without any error messages.
Any help would be appreciated.
--
Dean Browett
K. Petrossie
Here is the explanation of SQL2546N
SQL2546N The image on media "<media>" is not the first in
sequence from the backup or copy.
Explanation: During restore or load recovery, the first image
from the backup or copy must be processed first. The image found
on the media is not the first in sequence.
The utility waits for a response to continue.
User Response: Mount the media with the correct backup or copy
image and return to the utility with the correct caller action
parameter to indicate if processing should continue or
terminate.
According to the message the current directory (the default if you don't
specify one) does not have the first image sequence in it. There should be an
image file there with .001. Either that or specify the directory(s) where the
image(s are) is with "from <source dir>". To see full syntax of restore
command type "db2 ? restore" at your prompt.
Katherine Petrossie
Ekaterina Katritch
"Dean Browett" <dbro...@bizonline.net> wrote in message
news:3b3a1883$1...@news.bizonline.net...
David Mooney
> db2 => restore database BOL taken at 20010622153359 to /home/db2inst1 into
> TESTDB with 2 buffers buffer 1024 without prompting
> SQL2546N The image on media "/home/db2inst1" is not the first in sequence
> from the backup or copy.
You wouldn't happen to be backing up on one operating system and trying
to restore on another, would you?
dave
Michael Bhola
BOL.0.db2inst1.NODE0000.CATN0000.20010622153359.001
BOL.0.db2inst1.NODE0000.CATN0000.20010622153359.002
etc.
Could you post an 'ls -al' of the files here ?
What command do you use to do the backup ?
"Dean Browett" <dbro...@bizonline.net> wrote in message
news:3b3a1883$1...@news.bizonline.net...
Dean Browett
That's absolutely correct
(BOL.0.db2inst1.NODE0000.CATN0000.20010622153359.001)
This is the only file that is created. I used the backup command via the db2
control center with the command (via Show Command) 'BACKUP DATABASE BOL TO
/tmp WITH 2 BUFFERS BUFFER 1024'
--
Dean Browett
"Michael Bhola" <bho...@uk.ibm.com> wrote in message
news:9hes1b$1lr8$1...@sp15at20.hursley.ibm.com...
Dean Browett
Yes I am. The current db2 server is running on Solaris (sun sparc ultra10).
The new server is running db2 under Linux Redhat 6.2
It was because of this that I tried to create the ixf file. I have done some
reading since then and it seems that you can only create ixf files on a per
table basis rather than an entire database. Is this the case?
--
Dean Browett
"David Mooney" <d...@vnet.ibm.com> wrote in message
news:9hdet7$18ri$1...@tornews.torolab.ibm.com...
Bob Harbus
> Yes I am. The current db2 server is running on Solaris (sun sparc ultra10).
> The new server is running db2 under Linux Redhat 6.2
Backing Up and Restoring across platforms is not supported at this time I am
afraid - the only platforms that are supported for this today I believe are
Solaris and HP-UX.
> It was because of this that I tried to create the ixf file. I have done some
> reading since then and it seems that you can only create ixf files on a per
> table basis rather than an entire database. Is this the case?
Correct - you are export per table basis and creating an export file of some
format - per table.
>
>
> --
> Dean Browett
>
> "David Mooney" <d...@vnet.ibm.com> wrote in message
> news:9hdet7$18ri$1...@tornews.torolab.ibm.com...
> > Dean Browett <dbro...@bizonline.net> wrote:
> > > db2 => restore database BOL taken at 20010622153359 to /home/db2inst1
> into
> > > TESTDB with 2 buffers buffer 1024 without prompting
> > > SQL2546N The image on media "/home/db2inst1" is not the first in
> sequence
> > > from the backup or copy.
> >
> > You wouldn't happen to be backing up on one operating system and trying
> > to restore on another, would you?
> >
> > dave
--
Bob Harbus - Senior Consultant
DB2 UDB Data Management Consulting Services - IBM Toronto
Michael Bhola
What OSes on both boxes (looks UNIXy ) ?
What db2level on both boxes ?
How did you transfer the image between boxes ? Run 'sum' or 'cksum' on the
backup image at both ends to make sure it's not been converted in any way.
Maybe try backup and restore using default settings for buffers... ie. dont
specify anything.
"Dean Browett" <dbro...@bizonline.net> wrote in message
news:3b3c61fd$3...@news.bizonline.net...
Michael Bhola
"Dean Browett" <dbro...@bizonline.net> wrote in message
news:3b3c61fd$3...@news.bizonline.net...
Fabrizio Napolitano
<from a previous post>
> > It was because of this that I tried to create the ixf file. I have done some
> > reading since then and it seems that you can only create ixf files on a per
> > table basis rather than an entire database. Is this the case?
>
> Correct - you are export per table basis and creating an export file of some
> format - per table.
Creation of .ixf file is done by exports and these are on a per table
basis, Yes but I would like to add something, , still you can run
db2move to export all of your db; just issue the command:
db2move "dbname" export
and then
db2move "dbname" import (look for the right parameters)
being all .ixf file these will also create for you the tables, but you
need to create the DB dbname and the tablespaces before... at least
that's what I think, if I'm not wrong.
Any way look at Data Movement Utilities Guide and Reference p.184 for
more information on db2move
hope this helps
Fabrizio