home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!usc!venice!lung
- From: lung@venice.sedd.trw.com (Diane Lung)
- Subject: Re: Sybase and Interactive woes
- Message-ID: <1992Jul22.173512.15663@venice.sedd.trw.com>
- Sender: H. Ackerman
- Organization: TRW Systems Engineering & Development Division, Carson, CA
- References: <1992Jul16.173500.1075@asc386> <rjmartin.711764896@extro.ucc.su.OZ.AU>
- Date: Wed, 22 Jul 1992 17:35:12 GMT
- Lines: 48
-
- In article <rjmartin.711764896@extro.ucc.su.OZ.AU> rjmartin@extro.ucc.su.OZ.AU (Trilogy Business Systems) writes:
- >mosmith@asc386 (Matt Smith) writes:
- >
- >>We are currently using version 3.2 of Interactive and
- >>version 4.2 of Sybase. As the subject implies, we seems to be having
- >>great difficulty keeping the Sybase server up. If there is anybody
- >>out there using this configuration or could suggest a better one, I would
- >>really like to hear from you.
- >
- >We are currently running 4.2 on SCO ODT 1.1 and SCO Unix 3.2., and while we
- >have had our fair share of problems, the system is up around 99%+ of the time.
- >Our local sybase people are fairly helpful, although when we get really
- >hairy problems they are referred back to the U.S.
- >
- >Something to be really careful about is the number of streams parameters
- >configured in the kernal. The first set of release notes were ** WRONG **
- >about how many to set up (I think they just thought of some numbers that
- >would never be exceeded). You can use the crash command, and then use strstat
- >to see how these are going, also make sure you have a good reliable maths
- >co-processor (387 compatable), apparently this can cause problems. One last
- >thing to look at is the amount of available free ram, and if all else fails,
- >try dumping the database, re-install, and start from scratch. We had some
- >problems with a demo machine that used unix files as the database devices,
- >and occasionally it wouldn't be able to open the log device, thereby marking
- >the associated database as being hopelessly corrupt. I then manually changed
- ...
-
- Another item you might check (related to the number of streams) is the
- number of connections that your SQL Server is configured for - remember
- that each database device requires a connection. On Interactive I have had
- similar problems when the Server would come up and fail on bringing up
- database/log devices and mark them corrupt. In this situation, it was the
- case that the SQL Server had not been configured for enough connections.
-
- Howie
-
- **********************************************************
- Internet: howie%ranger@venice.sedd.trw.com
- Prodigy : DBKX34A
-
- All opinions are my own and not my employer's.
- **********************************************************
-
-
-
-
- --
- lung@venice.SEDD.TRW.COM
-