Re: [Emerald] Clearing out history - pointers?

Mike Davis ( (no email) )
Sat, 23 Sep 2000 22:37:27 -0400

Make sure you allocate alot of space. It really takes alot of room to do
its thing. You can "dump tran emerald to diskdump with no_log" but it can
be risky. I would only do it as a last resort.

----- Original Message -----
From: "Bob's Lists" <bob.lists@raha.com>
To: <emerald@iea-software.com>
Sent: Saturday, September 23, 2000 8:30 PM
Subject: RE: [Emerald] Clearing out history - pointers?

> >
> > Be sure to refresh the sql server screen while its recovering.
> > Sometimes it
> > will continue to show "recovering" when it is really finished. Just
right
> > click and select refresh. I once let it run for about 8 hrs when it was
> > done in 1.
>
> Dammit, it ran for an hour then gave me the same error message again...
>
> Error : 1105, Severity: 17, State: 2
> Can't allocate space for object 'Syslogs' in database 'Emerald' because
the
> 'logsegment' segment is full. If you ran out of space in Syslogs, dump the
> transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
> increase the size of the segment.
>
> No-one out there SQL savvy offer a method to fix this?
>
> Regards
>
> Bob
>
>
> For more information about this list (including removal) go to:
> http://www.iea-software.com/support/maillists/liststart
>

For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart