home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.sybase
- Path: sparky!uunet!elroy.jpl.nasa.gov!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!newsaintmail
- From: kfreytag@mdtf14 (Kelley Trombly-Freytag)
- Subject: Re: Recovering from a log segment full condition
- Message-ID: <VO!K2YHW3@linac.fnal.gov>
- Sender: daemon@linac.fnal.gov (The Background Man)
- Nntp-Posting-Host: mdtf14.fnal.gov
- Organization: Fermilab, Batavia, IL
- X-Newsreader: TIN [version 1.1 PL8]
- References: <1992Dec22.173634.4259@sunova.ssc.gov>
- Date: Tue, 22 Dec 1992 18:44:46 GMT
- Lines: 24
-
- Jeff Baron (jbaron@higgs.ssc.gov) wrote:
- : Warren Finnerty writes:
- : -
- : - Strange that model being full would be a problem.
- : - ( I'll take your word for it. :) )
- : - Do any of you SYBASE types want to confess to what futz'ing around in model
- : - goes on in conjunction with createing objects in tempdb. ( Not at startup )
-
- : ...
-
- : There is one piece of information that *is* kept in model; perhaps
- : it is a duplicate pointer to other transaction logs, or something of
- : a like systemish nature. It does change, and the transaction log
- : *will* fill eventually. (This was server version 4.0 or somesuch.)
-
- : --
- : Jeff Baron
- : jbaron@gauss.ssc.gov
-
- Given this information, is there any reason not to have
- `truncate transaction log on checkpoint` set for model??
-
- --
- Kelley Trombly-Freytag
-