Re: Sybase Database Becomes Corrupted on Reboot
- From: Paul Dow <Paul.Dow@xxxxxxxxxxxxxx>
- Date: Thu, 11 May 2006 12:06:18 +0100
.... if you are using raw devices, it may be worth checking out
your partitioning for overlaps with things that are allocated
to the OS etc. Also from the ASE docs:
If you are running the Logical Volume Manager (LVM) on an
AIX operating system, verify that the first AIX cylinder
of your raw partition is free (except for the master device)
and is available for the use of the LVM configuration. In
order to do this, make sure that vstart = 2 (one AIX
cylinder = 2 Sybase pages on default server) for all
user-defined disks.
If you are using file system devices, then it may be worth doing
an fsck etc on them just in case the OS has somehow allocated
disk blocks to the ASE file as well as some other file that
happens to get updated on a server reboot.
- Paul.
.
- Follow-Ups:
- Re: Sybase Database Becomes Corrupted on Reboot
- From: tsiaq
- Re: Sybase Database Becomes Corrupted on Reboot
- References:
- Sybase Database Becomes Corrupted on Reboot
- From: tsia_quithellen
- Re: Sybase Database Becomes Corrupted on Reboot
- From: Mark A. Parsons
- Re: Sybase Database Becomes Corrupted on Reboot
- From: tsiaq
- Sybase Database Becomes Corrupted on Reboot
- Prev by Date: Re: Help with SELECT needed
- Next by Date: syslogs op!
- Previous by thread: Re: Sybase Database Becomes Corrupted on Reboot
- Next by thread: Re: Sybase Database Becomes Corrupted on Reboot
- Index(es):