internal consistency error

I am getting the following error when I am trying to
restore a database/differential backup. Any ideas about
what is going on ? I can not do DBCC CHECKDB on the
production server. I will do it on the backup server if I
can restore it of course.
An internal consistency error occurred. Contact technical
support for assistance. RESTORE DATABASE is terminating
abnormally.
Thanks.
Hi,
Could you please confirm that the SQL Server is up and running and the database in question is online.
And you are unable to run DBCC CHECKDB(<db name>)
On doing so what error you get? On running DBCC CHECKDB does it shows some inconsistency and allocation error on the second last line of output...
Also look for errors in the SQL Server error log for this database.
Regards
Abid
|||Why can't you run checkdb on your production server?
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tony" <anonymous@.discussions.microsoft.com> wrote in message
news:f56601c43dca$1cce0b50$a501280a@.phx.gbl...
> I am getting the following error when I am trying to
> restore a database/differential backup. Any ideas about
> what is going on ? I can not do DBCC CHECKDB on the
> production server. I will do it on the backup server if I
> can restore it of course.
> An internal consistency error occurred. Contact technical
> support for assistance. RESTORE DATABASE is terminating
> abnormally.
> Thanks.
|||Are you sure that you have a complete, valid .bak file?
|||Production database is heavyly transaction oriented and I
don't want to run into performance issues while all the
users are in. The size of the DB is ~45 GB.
Thanks.

>--Original Message--
>Why can't you run checkdb on your production server?
>--
>Paul Randal
>Dev Lead, Microsoft SQL Server Storage Engine
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>"Tony" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:f56601c43dca$1cce0b50$a501280a@.phx.gbl...
I[vbcol=seagreen]
technical
>
>.
>
|||Yes I do. Actually, I am getting the error when I am
restoring the Differential backup. And NO, there is no
other backup after the differential backup.
I have the FULL backup from sunday and the differential
backup from last night. Both backups were completed
successfully.

>--Original Message--
>Are you sure that you have a complete, valid .bak file?
>.
>
sql

internal consistency error

I am getting the following error when I am trying to
restore a database/differential backup. Any ideas about
what is going on ' I can not do DBCC CHECKDB on the
production server. I will do it on the backup server if I
can restore it of course.
An internal consistency error occurred. Contact technical
support for assistance. RESTORE DATABASE is terminating
abnormally.
Thanks.Hi,
Could you please confirm that the SQL Server is up and running and the datab
ase in question is online.
And you are unable to run DBCC CHECKDB(<db name> )
On doing so what error you get? On running DBCC CHECKDB does it shows some i
nconsistency and allocation error on the second last line of output...
Also look for errors in the SQL Server error log for this database.
Regards
Abid|||Why can't you run checkdb on your production server?
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tony" <anonymous@.discussions.microsoft.com> wrote in message
news:f56601c43dca$1cce0b50$a501280a@.phx.gbl...
> I am getting the following error when I am trying to
> restore a database/differential backup. Any ideas about
> what is going on ' I can not do DBCC CHECKDB on the
> production server. I will do it on the backup server if I
> can restore it of course.
> An internal consistency error occurred. Contact technical
> support for assistance. RESTORE DATABASE is terminating
> abnormally.
> Thanks.|||Are you sure that you have a complete, valid .bak file?|||Production database is heavyly transaction oriented and I
don't want to run into performance issues while all the
users are in. The size of the DB is ~45 GB.
Thanks.

>--Original Message--
>Why can't you run checkdb on your production server?
>--
>Paul Randal
>Dev Lead, Microsoft SQL Server Storage Engine
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>"Tony" <anonymous@.discussions.microsoft.com> wrote in
message
>news:f56601c43dca$1cce0b50$a501280a@.phx.gbl...
I[vbcol=seagreen]
technical[vbcol=seagreen]
>
>.
>|||Yes I do. Actually, I am getting the error when I am
restoring the Differential backup. And NO, there is no
other backup after the differential backup.
I have the FULL backup from sunday and the differential
backup from last night. Both backups were completed
successfully.

>--Original Message--
>Are you sure that you have a complete, valid .bak file?
>.
>

internal consistency error

I have a sql database
I run dbcc checkdb and get no errors
I go to backup the database in enterprise manager, and it won't
restore because it has internal consistency errors
I can go back to an older version of the database

I run a particular procedure in our accounting software package
Never do I get errors when running dbcc checkdb

Sometimes I get the backup and restore problem, sometimes I don't

I am doing this on a test server with about 220 megs of RAM

I am trying the dbcc checkdb ('dbname',REPAIR_REBUILD) command

Any other ideas?An update to the problem:

I ran the process on my test server on a one-gig or so database and it
runs fine but gets an internal consistency error when I backup and try
to restore (dbcc checkdb, with and without REPAIR_REBUILD, runs just
fine)

But I run the process on the real server and it backs up and restores
just fine

So .........

It points to a resource problem on the test server

But I am not sure of this

Any feedback on this from anyone?|||brucestromcpa@.aol.com (bruce strom) wrote in message news:<8a9196fd.0310300827.41041bda@.posting.google.com>...
> An update to the problem:
> I ran the process on my test server on a one-gig or so database and it
> runs fine but gets an internal consistency error when I backup and try
> to restore (dbcc checkdb, with and without REPAIR_REBUILD, runs just
> fine)
> But I run the process on the real server and it backs up and restores
> just fine
> So .........
> It points to a resource problem on the test server
> But I am not sure of this
> Any feedback on this from anyone?

A consistency error means that the backup set is corrupt, for some
reason. That could mean a hardware issue, or a bad tape, or perhaps
backing up across an unreliable network. There are also issues if the
two versions of MSSQL are not the same. Perhaps you can give some more
details - where are you backing up to (tape, local drive, network
drive)? What version of MSSQL do you have? What's the operating system
and filesystem? As a minimum test, is this reliable on your test
server:

backup database MyDB to disk = 'c:\MyDB.bak' -- or another local drive
restore database MyDB from disk = 'c:\MyDB.bak'

If that isn't reliable, do OS-level tools detect any integrity issues
with the filesystem?

Simon

Integrity Check and Transaction Log

Running the Integrity Check (I think this is DBCC CHECKDB)
as part of a Database Maintenance Plan creates a
transaction log that is roughly the size of the database.
This is causing a problem where a large database is
filling up the disk. The simple answer is to get a bigger
disk, but how can I run the Integrity Check and not have
my tlog grow so much? Is this possible?
SQL BOL says "If actively performing transactions while
DBCC CHECKDB is running, the transaction log continues to
grow because the DBCC command blocks log truncation until
it has finished reading the log." However, the integrity
check occurs early in the morning (1am) and there are no
users in the database.
Thanks,
DeanAfter you run the checkdb, you could kick off a full backup then
truncate the log if you do not have users connecting.
HTH
Ray Higdon MCSE, MCDBA, CCNA
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!|||Ray,
Yes, I could do that, and effectively am, only the next
day as part of the DB Maintenance Plan. My question comes
because I can't reproduce this tlog growth on other
databases. I've got several situations where it is
happening, but I can't pin down exactly why it's
occuring. I'm just about sure the DB Maint. Plan is the
culprit because of the timing.
Dean
>--Original Message--
>After you run the checkdb, you could kick off a full
backup then
>truncate the log if you do not have users connecting.
>HTH
>Ray Higdon MCSE, MCDBA, CCNA
>*** Sent via Developersdex http://www.developersdex.com
***
>Don't just participate in USENET...get rewarded for it!
>.
>|||Sounds more like the log is filling up due to the optimization (DBREINDEX)
portion of the MP and not the DBCC CHECKDB.
--
Andrew J. Kelly
SQL Server MVP
"Dean Beckley" <dean@.omegagroup.com> wrote in message
news:02f801c34a46$b1aff210$a401280a@.phx.gbl...
> Ray,
> Yes, I could do that, and effectively am, only the next
> day as part of the DB Maintenance Plan. My question comes
> because I can't reproduce this tlog growth on other
> databases. I've got several situations where it is
> happening, but I can't pin down exactly why it's
> occuring. I'm just about sure the DB Maint. Plan is the
> culprit because of the timing.
> Dean
> >--Original Message--
> >After you run the checkdb, you could kick off a full
> backup then
> >truncate the log if you do not have users connecting.
> >
> >HTH
> >
> >Ray Higdon MCSE, MCDBA, CCNA
> >
> >*** Sent via Developersdex http://www.developersdex.com
> ***
> >Don't just participate in USENET...get rewarded for it!
> >.
> >|||I can guarantee you that CHECKDB itself does not generate log records
(unless you're running repair) so something else _must_ be running at the
same as the check.
Regards,
Paul.
--
Paul Randal
DBCC Technical Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OkScA8mSDHA.3192@.tk2msftngp13.phx.gbl...
> Sounds more like the log is filling up due to the optimization (DBREINDEX)
> portion of the MP and not the DBCC CHECKDB.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Dean Beckley" <dean@.omegagroup.com> wrote in message
> news:02f801c34a46$b1aff210$a401280a@.phx.gbl...
> > Ray,
> >
> > Yes, I could do that, and effectively am, only the next
> > day as part of the DB Maintenance Plan. My question comes
> > because I can't reproduce this tlog growth on other
> > databases. I've got several situations where it is
> > happening, but I can't pin down exactly why it's
> > occuring. I'm just about sure the DB Maint. Plan is the
> > culprit because of the timing.
> >
> > Dean
> > >--Original Message--
> > >After you run the checkdb, you could kick off a full
> > backup then
> > >truncate the log if you do not have users connecting.
> > >
> > >HTH
> > >
> > >Ray Higdon MCSE, MCDBA, CCNA
> > >
> > >*** Sent via Developersdex http://www.developersdex.com
> > ***
> > >Don't just participate in USENET...get rewarded for it!
> > >.
> > >
>|||Yes, I guess I made it sound more like a question than a statement. DBCC
CHECKDB does not manipulate the data so there is no need to log.
--
Andrew J. Kelly
SQL Server MVP
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:Oxzrk7uSDHA.2276@.TK2MSFTNGP10.phx.gbl...
> I can guarantee you that CHECKDB itself does not generate log records
> (unless you're running repair) so something else _must_ be running at the
> same as the check.
> Regards,
> Paul.
> --
> Paul Randal
> DBCC Technical Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:OkScA8mSDHA.3192@.tk2msftngp13.phx.gbl...
> > Sounds more like the log is filling up due to the optimization
(DBREINDEX)
> > portion of the MP and not the DBCC CHECKDB.
> >
> > --
> >
> > Andrew J. Kelly
> > SQL Server MVP
> >
> >
> > "Dean Beckley" <dean@.omegagroup.com> wrote in message
> > news:02f801c34a46$b1aff210$a401280a@.phx.gbl...
> > > Ray,
> > >
> > > Yes, I could do that, and effectively am, only the next
> > > day as part of the DB Maintenance Plan. My question comes
> > > because I can't reproduce this tlog growth on other
> > > databases. I've got several situations where it is
> > > happening, but I can't pin down exactly why it's
> > > occuring. I'm just about sure the DB Maint. Plan is the
> > > culprit because of the timing.
> > >
> > > Dean
> > > >--Original Message--
> > > >After you run the checkdb, you could kick off a full
> > > backup then
> > > >truncate the log if you do not have users connecting.
> > > >
> > > >HTH
> > > >
> > > >Ray Higdon MCSE, MCDBA, CCNA
> > > >
> > > >*** Sent via Developersdex http://www.developersdex.com
> > > ***
> > > >Don't just participate in USENET...get rewarded for it!
> > > >.
> > > >
> >
> >
>