Re: [Emerald] Emerald / SQL Problem?

Adam Greene ( (no email) )
Sat, 20 Feb 1999 11:10:53 -0500

Thanks -- it looks like the problem was with the Seagate BackupExec copy of
the Emerald database. I just ran the backup again and everything was fine
the second time.

I was afraid of running a checkdb. First, I wasn't sure how to do it in
SQL, and second, I was afraid that running that procedure from the Emerald
2.1.8 Administrator might cause damage to the database. Maybe these are
groundless fears... if I was sure that I could recover a database once it
was ruined, I suppose I wouldn't be so fearful about it.

-----Original Message-----
From: Dale E. Reed Jr. <>
To: <>
Date: Friday, February 19, 1999 12:46 PM
Subject: Re: [Emerald] Emerald / SQL Problem?

>Adam Greene wrote:
>> I use Seagate BackupExec 7.0 with an SQL module to backup our Emerald
>> database each night. This morning I found this error in our logs:
>> -------8<--------------------------------------------------------
>> Consistency checking Emerald
>> There was a problem running the DBCC.
>> SQL Server returned the following error message:
>> Allocation Discrepancy: Page is allocated but not linked; check the
>> following pages and ids: allocation pg#=15872 extent id=16024 logical
>> pg#=16028 object id on extent=1545056540 (object name = Calls) indid on
>> extent=0
>> ---------------------------------------------->8-----------------
>> Do you have any idea what this could mean, or what I should check to make
>> sure the Emerald database is functioning properly? Maybe it's a problem
>> with Seagate BackupExec and not Emerald/SQL.
>> I'm running SQL Server 6.5 and Emerald 2.1.8.
>These are the results from a "DBCC CheckDB" that it does before
>hand. I would run a checkdb again and see if it still had this
>Dale E. Reed Jr. Emerald and RadiusNT
>IEA Software, Inc.
>For more information about this list, including removal,
>please see

For more information about this list, including removal,
please see