Sybase 10.0.2 and Sun's Storage Arrays

Sybase 10.0.2 and Sun's Storage Arrays

Post by Guy Anderso » Tue, 24 Oct 1995 04:00:00


>The above combination causes my Sybase server to crash (once every few hours)
>with a 605 error. Anyone seen this before?

>Relevant System Details:
>    SPARCserver1000E
>    Solaris 2.4
>    Volume Manager version 2.1

>Already tried:  
>    Recommended patches for Sybase.
>    Turning off asynchronous writes.
>    Moving disks out of volume manager control (This seems to work, but I
>    haven't given it enough time).

So far, your troubleshooting looks pretty good.  Here are some more suggestions:

1.  Call Sybase tech support for and ask which Solaris patches are required for running
    the server in Solaris 2.4 .  I know that we had to load a couple.

2.  I know that for a while Online Disk Suite (the volume manager) was not certified  
    certified for use with the Sybase SQL Server.  Make sure that the version that
    you are using is O.K. with Sybase.

3.  Make absolutely sure that you do not use sector 0 on any disk in your Raid Array.  
    Here's what happens:  Typically, the disk label and other O/S housekeeping
    information is written to the first sector on an O/S disk.  Sybase, by default,
    writes its Object Allocation Map (OAM) to the first available 512K page in a
    database. If one of your Sybase virtual devices starts on the first sector, you
    run the risk of overwriting your disk label.  In the case of logical volume
    managers,  they also write their housekeeping information at the beginning of the
    disk (at least, this is what happens in AIX, I'm not as familiar with Online Disk
    Suite or Solstice).  Given this scenario, you can have Sybase and the O/S competing
    for to write information to the same place.  Either way, if you overwrite the disk
    label, or the OAM, you are heading for 605 city.

Sybase has some good technical information on this issue.  It is a fairly common
problem -- one which we have been through, and have since corrected.  Just make
absolutely, positively sure that at Sybase cannot write to the first 2 or 3 sectors on
your disks, and you should be fine.   Oh, by the way, we are using asynchronous I/O to
raw UNIX partitions with no problems.

Then again, you may have something else going on...


1. Sun Storage Array and Sybase (4.9.2 or System 10)

Does anyone know if Sybase (4.9.2 or System 10) has been tested with
Sun's new Storage Array (SA)?  We're considering a SA configuration (a SS1000
and a 18 gig SA) and wondered if the SA and Sybase are compatible.  Any
experiences or comments would be welcome. Thanks in advance...


* Disclaimer - My opinions are my own...  

2. How can I transfer data from an English code set database to a Chinese one?

3. Oracle in mirror'd or RAID'd storage arrays (SUN)

4. Scheduled tasks do not stay Enabled.

5. Sybase and Sun Storage Array

6. Open systems a marketing problem?

7. Sybase 10.0.2 and SUN's IPX 1.1

8. SUN Sparc 2000 with SUN Storage Array (30GB)`

9. Migrate Sybase SQL server from Netware NLM 4.2.2 to Sybase 10 on Sun

10. EBF's and Sybase vs

11. Sybase 10 runs on Sun IPX?

12. Sybase 10 on Sun 4/280?