dbTalk Databases Forums  

Copying Database thru dd

comp.databases.sybase comp.databases.sybase


Discuss Copying Database thru dd in the comp.databases.sybase forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Charyulu
 
Posts: n/a

Default Copying Database thru dd - 08-23-2004 , 06:02 AM






Hello

We hv a Sybase 11.0.2 Installation on SGI IRIX6.2
The Storage is 12X1GB Drives with XLV.
There are four DBs created on 8 raw partitions (one
for Data and one for Log).

We planned to change the existing storage to 2X18GB Disk Drives
and copy all the DBs to the newly created raw partiotions.

I gather from the net that mirroring is the easiest way to do this.

Unfortunately mirroring master device has failed, since the
pubs2 db is corrupted.

So I used dd to copy all the raw partitions, Changed the entry in
RUN_file
and restarted the system. thru isql changed the device entries in
sysdevices table to point to the new devices. Verified New entries
exist in sysdevices table.

Shutdown the server
Restarted the server.
All the user dbs fail to come on line.
Errorlog show all the devices as suspect.

Where did I go wrong???
Any ideas???

Thanks
....Charyulu

Reply With Quote
  #2  
Old   
Michael Peppler
 
Posts: n/a

Default Re: Copying Database thru dd - 08-23-2004 , 07:38 AM






On Mon, 23 Aug 2004 04:02:16 -0700, Charyulu wrote:

Quote:
Hello

We hv a Sybase 11.0.2 Installation on SGI IRIX6.2
The Storage is 12X1GB Drives with XLV.
There are four DBs created on 8 raw partitions (one
for Data and one for Log).

We planned to change the existing storage to 2X18GB Disk Drives
and copy all the DBs to the newly created raw partiotions.

I gather from the net that mirroring is the easiest way to do this.

Unfortunately mirroring master device has failed, since the
pubs2 db is corrupted.
You could have dropped the pubs2 database - either with a normal drop
database command or with a dbcc dbrepair() command.

Quote:
So I used dd to copy all the raw partitions, Changed the entry in
RUN_file
and restarted the system. thru isql changed the device entries in
sysdevices table to point to the new devices. Verified New entries exist
in sysdevices table.
Did you shutdown the server when you ran the dd command?

Quote:
Shutdown the server
Restarted the server.
All the user dbs fail to come on line. Errorlog show all the devices as
suspect.
Most likely some of the data in the DBs was in cache when you ran the dd
command.

Or possibly the devices can't be opened for some reason (permissions for
example).

Michael
--
Michael Peppler Data Migrations, Inc.
mpeppler (AT) peppler (DOT) org http://www.peppler.org/
Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or
long term contract positions - http://www.peppler.org/resume.html



Reply With Quote
  #3  
Old   
Me
 
Posts: n/a

Default Re: Copying Database thru dd - 08-23-2004 , 10:51 AM



Charyulu wrote:
Quote:
Hello

We hv a Sybase 11.0.2 Installation on SGI IRIX6.2
The Storage is 12X1GB Drives with XLV.
There are four DBs created on 8 raw partitions (one
for Data and one for Log).

We planned to change the existing storage to 2X18GB Disk Drives
and copy all the DBs to the newly created raw partiotions.

I gather from the net that mirroring is the easiest way to do this.

Unfortunately mirroring master device has failed, since the
pubs2 db is corrupted.

So I used dd to copy all the raw partitions, Changed the entry in
RUN_file
and restarted the system. thru isql changed the device entries in
sysdevices table to point to the new devices. Verified New entries
exist in sysdevices table.

Shutdown the server
Restarted the server.
All the user dbs fail to come on line.
Errorlog show all the devices as suspect.

Where did I go wrong???
Any ideas???

Thanks
...Charyulu
Why don't you post the extract of the error log from when you tried to
bring the server up with the copied databases? That may provide a clue
as to what the problem may be.

I have seen cases where the raw device ownership looked ok
(sybase:sybase), but in fact the O/S didn't seem to recognize it. We
had to go in and manually run chown on the device file IIRC.

That's just one possibility. Again, post the pertinent entries from the
errorlog and see what it reveals.

-
Orion




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.