Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Help dbcc rebuild_log !!!

162 views
Skip to first unread message

Valera Molyakov

unread,
Apr 27, 2000, 3:00:00 AM4/27/00
to
Hi !

As I can execute the command dbcc rebuild_log ?

SQL server Version :
SQL Server/11.0.3/P/PC Intel/Windows NT 3.5/SWR 7305 Rollup/OPT/Fri Jul
19 1997

--
Best regards !

Jason Froebe

unread,
Apr 27, 2000, 3:00:00 AM4/27/00
to Valera Molyakov
Valera Molyakov wrote:

Hi Valera,

Please don't cross-post. WHY do you want to run dbcc rebuild_log?

Jason

jfroebe.vcf

Valera Molyakov

unread,
Apr 27, 2000, 3:00:00 AM4/27/00
to
When I executed bcp copying of data in SQL server there was a failure of
copying,
after reboot SQL server not started.

I don't have database and transaction log dump !!!

SQL log:

00:00/04/27 15:39:25.73 server Error: 614, Severity: 21, State: 1
00:00/04/27 15:39:25.73 server A row on page 134906 was accessed that has
an i134906
was accessed that has an illegal length of 8224 in database 'gai'.


Jason Froebe <jfr...@sybase.com> сообщил в новостях
следующее:39087EFF...@sybase.com...

Valera Molyakov

unread,
Apr 27, 2000, 3:00:00 AM4/27/00
to

User DB not started. At attempt to be connected to it produces the message :

Database 'gai' has not been recovered yet -- please wait and try again.


Jason Froebe

unread,
Apr 27, 2000, 3:00:00 AM4/27/00
to
Hi Valera,

Your best bet would be to call Sybase TechSupport. I'm only posting this in
the sybase.public.sqlserver.general newsgroup

I assume you are attempting to suicide the log, which is a far better option
than rebuilding it. Suiciding the log entails inserting a final checkpoint
record at the end of the log. The recovery process will assume that all
transactions before the checkpoint were completed. The problem with this is
that you could end up with some corruption because of half completed
transactions. It's up to you if you want to do this.

To suicide the log:
1) change status column in sysdatabases to -32768 for the "bad" database
2) shutdown with nowait
3) start server
4) go into the "bad" database and issue a checkpoint
5) change status column to 0
6) shutdown with nowait
7) start server
8) run dbcc checkdb & checkalloc

Jason

jfroebe.vcf

Valera Molyakov

unread,
Apr 27, 2000, 3:00:00 AM4/27/00
to
After execution described steps database successfully run.

Thank!

Jason Froebe <jfr...@sybase.com> сообщил в новостях

следующее:390883CD...@sybase.com...

0 new messages