Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Sybase Data Fragement fails

2 posts in Backup and Recovery Last posting was on 2001-04-14 07:47:12.0Z
Raman Posted on 2001-04-12 18:50:40.0Z
From: raman
Date: Thu, 12 Apr 2001 14:50:40 -0400
Newsgroups: sybase.public.sqlserver.backup+recovery
Subject: Sybase Data Fragement fails
Message-ID: <372BC146AE16AA360067843E85256A2C.0067844D85256A2C@webforums>
Lines: 4
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!!!!news
Xref: forums-1-dub sybase.public.sqlserver.backup+recovery:318
Article PK: 1060835

Sybase Data fragements exists on a particular drive and drive crashed, what
do i do, any help would be appreciated.

Thanks for your help.

Anthony Mandic <amandic Posted on 2001-04-14 07:47:12.0Z
Date: Sat, 14 Apr 2001 17:47:12 +1000
From: Anthony Mandic <amandic@*>
Organization: Mandic Consulting Pty. Ltd.
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Sybase Data Fragement fails
References: <372BC146AE16AA360067843E85256A2C.0067844D85256A2C@webforums>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <UBs$>
Newsgroups: sybase.public.sqlserver.backup+recovery
Lines: 38
Path: forums-1-dub!!
Xref: forums-1-dub sybase.public.sqlserver.backup+recovery:317
Article PK: 1060834

raman wrote:
> Sybase Data fragements exists on a particular drive and drive crashed, what
> do i do, any help would be appreciated.

Do you have backups of the database(s) affected by the disk crash?
If not, you are out of luck. If you do, the following steps depend
on how these fragments were located on the disk. If you were using
raw devices with Unix, repartition the new disk to match the previous
layouts, reconfigure the server to allow updates to system tables,
change the status of the affected databases to match the status of
the 'for load' option (I'm not sure what it is at the moment, you'll
need to look it up. Be careful when doing this. You may need to merge
it with the existing options), bounce the server and then load your
dumps and online the dbs. Everything should come up OK but the data
will be as it was at the time of the dump.

For devices that were on files, you'll need to recreate these files
thru the OS. If you have filesystem dumps, you could try restoring
them with a filesystem restore. Then proceed as above from the
reconfigure step onwards.

If you have any transaction log dumps made after the db dumps, apply
these too. If the server is still up after the crash and you haven't
done anything to it yet, you could dump any logs for the affected
dbs with the "dump tran <dbname> to ... with no_truncate". You could
then apply these log dumps later after following the above steps.

-am © 2001