Error 207: log

Showing posts with label log. Show all posts

Tuesday, March 27, 2012

Error 9004 attaching a database

I've been given a database backup in the form of an .mdf file, a bunch
of .ndf files, and a .log file. When I try to attach the .mdf file in
Server Management Studio, I get error 9004, An error occurred while
processing the log.
Any suggestions?
Phil Hibbs.Phil,
Kevin Farlee's answer has helped a couple of people with your problem.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=598396&SiteID=1
RLF
"PhilHibbs" <snarks@.gmail.com> wrote in message
news:1193140510.353843.250240@.y27g2000pre.googlegroups.com...
> I've been given a database backup in the form of an .mdf file, a bunch
> of .ndf files, and a .log file. When I try to attach the .mdf file in
> Server Management Studio, I get error 9004, An error occurred while
> processing the log.
> Any suggestions?
> Phil Hibbs.
>|||On 23 Oct, 13:31, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Kevin Farlee's answer has helped a couple of people with your problem.
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=598396&SiteID=1
Hm, looked promising, but when I try to "bring online" the database
with the files replaced, I get a load of errors in this form:
E:\data\data_file_09.ndf is not a primary database file
I have a .mdf file and 26 .ndf files, it looks like the creation of
the empty database is creating these files in a different way to the
original database.
Phil Hibbs.|||Phil,
Did you first create the 26 ndf files in your database to be replaced before
trying to copy the files into place?
RLF
"PhilHibbs" <snarks@.gmail.com> wrote in message
news:1193148065.531336.193770@.e34g2000pro.googlegroups.com...
> On 23 Oct, 13:31, "Russell Fields" <russellfie...@.nomail.com> wrote:
>> Kevin Farlee's answer has helped a couple of people with your problem.
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=598396&SiteID=1
> Hm, looked promising, but when I try to "bring online" the database
> with the files replaced, I get a load of errors in this form:
> E:\data\data_file_09.ndf is not a primary database file
> I have a .mdf file and 26 .ndf files, it looks like the creation of
> the empty database is creating these files in a different way to the
> original database.
> Phil Hibbs.
>|||On 23 Oct, 20:15, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Did you first create the 26 ndf files in your database to be replaced before
> trying to copy the files into place?
Yep. I made a big CREATE DATABASE statement with the .mdf and all
the .ndf files specified in it.
Phil Hibbs.|||On 23 Oct, 20:15, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Did you first create the 26 ndf files in your database to be replaced before
> trying to copy the files into place?
Yep. I made a big CREATE DATABASE statement with the .mdf and all
the .ndf files specified in it.
Phil Hibbs.|||Phil,
I understand that you are using SQL Server 2005, since you mention
Management Studio. I have tested and not been able to duplicate your
problem. When you use SSMS to do the attach, have you pressed the Script
command at the top of the panel. This will provide an exact script of the
commands to be run. If you do that, perhaps you will see something helpful.
Or, you can post it here for review.
Obviously something is different between our setups. I am running SQL
Server 2005 SP2. Are you also running SP2? I ask because SP2 fixed some
Management Studio problems and you should update to it (plus some hotfixes)
if you have not done so.
This describe my patch level:
http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
For more recent fixes, see also: http://support.microsoft.com/kb/937137/LN/
RLF
"PhilHibbs" <snarks@.gmail.com> wrote in message
news:1193222031.764752.35650@.v29g2000prd.googlegroups.com...
> On 23 Oct, 20:15, "Russell Fields" <russellfie...@.nomail.com> wrote:
>> Did you first create the 26 ndf files in your database to be replaced
>> before
>> trying to copy the files into place?
> Yep. I made a big CREATE DATABASE statement with the .mdf and all
> the .ndf files specified in it.
> Phil Hibbs.
>|||On 25 Oct, 17:34, "Russell Fields" <russellfie...@.nomail.com> wrote:
> I have tested and not been able to duplicate your
> problem.
I suspect that is because you don't have the same .mdf and .ndf
and .log files that I have.
Phil Hibbs.|||Phil, No doubt about that. Sorry this did not help. - RLF
"PhilHibbs" <snarks@.gmail.com> wrote in message
news:1193761341.010344.78000@.k79g2000hse.googlegroups.com...
> On 25 Oct, 17:34, "Russell Fields" <russellfie...@.nomail.com> wrote:
>> I have tested and not been able to duplicate your
>> problem.
> I suspect that is because you don't have the same .mdf and .ndf
> and .log files that I have.
> Phil Hibbs.
>

Error 9003 : fail to attach a database

Hi,
I sucessful attached a database, but deleted it without detach. When I tried
to attach again got this error 9003: The LSN(12:32:1) passed to log scan in
database "Contacts" is invalid.
I tried to detach it, but I can't find the database in system, so it fails t
oo.
Please help, thanks in advance!
IreneIrene,
Do you have the .mdf and .ldf files for Contacts?
Did you use the Enterprise Manager or issue the sp_attach_db and sp_detach_d
b from the Query Analyzer?
...but deleted it without detach...
What does this mean? How was this accomplished? Explain...
Does Contacts show up when you run this...
SELECT * FROM master..sysdatabases
Norman|||Hi, Norman
I used the Enterprise Manager to attach the Contact.mdf and Contact.ldf.
After attached it, I found the new database "Contact" was readonly. I
made a mistake to del the database "Contact" directly in the Enterprise
Manager explorer.
When I tried to attach the file again in the Enterprise Manager
explorer, it shows the error 9003. Then I tried sp_detach_db "Contact",
it fails.
When I run "SELECT * FROM sysdatabases", no "Contact" database record
in.
I guest it still has some reference files exist in database server, but
I don't know how to restore it.
Thanks again.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Hi, Norman
I used the Enterprise Manager to attach the Contact.mdf and Contact.ldf.
After attached it, I found the new database "Contact" was readonly. I made a
mistake to del the database "Contact" directly in the Enterprise Manager ex
plorer.
When I tried to attach the file again in the Enterprise Manager explorer, it
shows the error 9003. Then I tried sp_detach_db "Contact", it fails.
When I run "SELECT * FROM sysdatabases", no "Contact" database record in.
I guest it still has some reference files exist in database server, but I do
n't know how to restore it.

Error 9003 : fail to attach a database

Hi
I sucessful attached a database, but deleted it without detach. When I tried to attach again got this error 9003: The LSN(12:32:1) passed to log scan in database "Contacts" is invalid
I tried to detach it, but I can't find the database in system, so it fails too
Please help, thanks in advance
IreneIrene
Do you have the .mdf and .ldf files for Contacts
Did you use the Enterprise Manager or issue the sp_attach_db and sp_detach_db from the Query Analyzer
...but deleted it without detach..
What does this mean? How was this accomplished? Explain..
Does Contacts show up when you run this..
SELECT * FROM master..sysdatabase
Norman|||Hi, Norma
I used the Enterprise Manager to attach the Contact.mdf and Contact.ldf
After attached it, I found the new database "Contact" was readonly. I made a mistake to del the database "Contact" directly in the Enterprise Manager explorer
When I tried to attach the file again in the Enterprise Manager explorer, it shows the error 9003. Then I tried sp_detach_db "Contact", it fails.
When I run "SELECT * FROM sysdatabases", no "Contact" database record in
I guest it still has some reference files exist in database server, but I don't know how to restore it.

Error 9002, tempdb log full

We have a reporting database that end users run ad-hoc queries against (SQL
Server 2000 SP 4 running on Windows 2000). Periodically, we'll get the
following error message:
Error: 9002, Severity: 17, State: 6
The log file for database 'tempdb' is full. Back up the transaction log for
the database to free up some log space.
When I track down the user associated with the Event Log message, he/she is
running a huge query that needs better selection criteria, but I don't
believe that the tempdb log is truely out of space. We have plenty of disk
space, and have gotten this message with tempdb log set to unrestricted and
with a limit of 15 GB.
Question: Is this a sql server bug or related to an i/o problem, because it
really isn't a true tempdb log full condition. Does this impact all users
using tempdb (I would think so) and any suggestions on how to prevent this?
Thanks,
DanDan,
This is not a bug. It is truly a tempdb log full alert. It does not matter
how much space you have because you are limiting the log to 15 GB. It is ver
y
much possible for the log to be full on a reporting database. Remember, all
sorting, agregations and temp tables are created in the tempdb.
I don't think there is a right answer for the size, you will have to
increase it and watch it and increase it again as needed.
hth
DeeJay
"Dan H" wrote:

> We have a reporting database that end users run ad-hoc queries against (SQ
L
> Server 2000 SP 4 running on Windows 2000). Periodically, we'll get the
> following error message:
> Error: 9002, Severity: 17, State: 6
> The log file for database 'tempdb' is full. Back up the transaction log fo
r
> the database to free up some log space.
> When I track down the user associated with the Event Log message, he/she i
s
> running a huge query that needs better selection criteria, but I don't
> believe that the tempdb log is truely out of space. We have plenty of dis
k
> space, and have gotten this message with tempdb log set to unrestricted an
d
> with a limit of 15 GB.
> Question: Is this a sql server bug or related to an i/o problem, because
it
> really isn't a true tempdb log full condition. Does this impact all users
> using tempdb (I would think so) and any suggestions on how to prevent this
?
> Thanks,
> Dan

Error 9002, tempdb log full

We have a reporting database that end users run ad-hoc queries against (SQL
Server 2000 SP 4 running on Windows 2000). Periodically, we'll get the
following error message:
Error: 9002, Severity: 17, State: 6
The log file for database 'tempdb' is full. Back up the transaction log for
the database to free up some log space.
When I track down the user associated with the Event Log message, he/she is
running a huge query that needs better selection criteria, but I don't
believe that the tempdb log is truely out of space. We have plenty of disk
space, and have gotten this message with tempdb log set to unrestricted and
with a limit of 15 GB.
Question: Is this a sql server bug or related to an i/o problem, because it
really isn't a true tempdb log full condition. Does this impact all users
using tempdb (I would think so) and any suggestions on how to prevent this?
Thanks,
Dan
Dan,
This is not a bug. It is truly a tempdb log full alert. It does not matter
how much space you have because you are limiting the log to 15 GB. It is very
much possible for the log to be full on a reporting database. Remember, all
sorting, agregations and temp tables are created in the tempdb.
I don't think there is a right answer for the size, you will have to
increase it and watch it and increase it again as needed.
hth
DeeJay
"Dan H" wrote:

> We have a reporting database that end users run ad-hoc queries against (SQL
> Server 2000 SP 4 running on Windows 2000). Periodically, we'll get the
> following error message:
> Error: 9002, Severity: 17, State: 6
> The log file for database 'tempdb' is full. Back up the transaction log for
> the database to free up some log space.
> When I track down the user associated with the Event Log message, he/she is
> running a huge query that needs better selection criteria, but I don't
> believe that the tempdb log is truely out of space. We have plenty of disk
> space, and have gotten this message with tempdb log set to unrestricted and
> with a limit of 15 GB.
> Question: Is this a sql server bug or related to an i/o problem, because it
> really isn't a true tempdb log full condition. Does this impact all users
> using tempdb (I would think so) and any suggestions on how to prevent this?
> Thanks,
> Dan

Error 9002, tempdb log full

We have a reporting database that end users run ad-hoc queries against (SQL
Server 2000 SP 4 running on Windows 2000). Periodically, we'll get the
following error message:
Error: 9002, Severity: 17, State: 6
The log file for database 'tempdb' is full. Back up the transaction log for
the database to free up some log space.
When I track down the user associated with the Event Log message, he/she is
running a huge query that needs better selection criteria, but I don't
believe that the tempdb log is truely out of space. We have plenty of disk
space, and have gotten this message with tempdb log set to unrestricted and
with a limit of 15 GB.
Question: Is this a sql server bug or related to an i/o problem, because it
really isn't a true tempdb log full condition. Does this impact all users
using tempdb (I would think so) and any suggestions on how to prevent this?
Thanks,
DanDan,
This is not a bug. It is truly a tempdb log full alert. It does not matter
how much space you have because you are limiting the log to 15 GB. It is very
much possible for the log to be full on a reporting database. Remember, all
sorting, agregations and temp tables are created in the tempdb.
I don't think there is a right answer for the size, you will have to
increase it and watch it and increase it again as needed.
hth
DeeJay
"Dan H" wrote:
> We have a reporting database that end users run ad-hoc queries against (SQL
> Server 2000 SP 4 running on Windows 2000). Periodically, we'll get the
> following error message:
> Error: 9002, Severity: 17, State: 6
> The log file for database 'tempdb' is full. Back up the transaction log for
> the database to free up some log space.
> When I track down the user associated with the Event Log message, he/she is
> running a huge query that needs better selection criteria, but I don't
> believe that the tempdb log is truely out of space. We have plenty of disk
> space, and have gotten this message with tempdb log set to unrestricted and
> with a limit of 15 GB.
> Question: Is this a sql server bug or related to an i/o problem, because it
> really isn't a true tempdb log full condition. Does this impact all users
> using tempdb (I would think so) and any suggestions on how to prevent this?
> Thanks,
> Dan

Error 9002 tempdb log file is full

Hi,
I've the following error message, which doesn't make sense to me.
The log file is not full, it has autogrow set to on and the disk drive on
which it
resides has 256GB free space. I hope i'm missing something and welcome
any suggestions on what to do or what to look at.
"Server: Msg 9002, Level 17, State 6, Line 1
The log file for database 'tempdb' is full. Back up the
transaction log for the database to free up some log space."If the application is requesting space in TempDB and the request interval is
faster than the disk can allocate the space then you will see this message
whilst the Autogrow is happening.
If you have this much space then try pre allocating a larger TempDB
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Stressed" <k@.c.co.uk> wrote in message
news:ufQ6UCJlDHA.2536@.tk2msftngp13.phx.gbl...
> Hi,
>
> I've the following error message, which doesn't make sense to me.
> The log file is not full, it has autogrow set to on and the disk drive on
> which it
> resides has 256GB free space. I hope i'm missing something and welcome
> any suggestions on what to do or what to look at.
>
> "Server: Msg 9002, Level 17, State 6, Line 1
>
> The log file for database 'tempdb' is full. Back up the
> transaction log for the database to free up some log space."
>|||Thanks for that, it all makes sense now.
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:O$FlXLJlDHA.1084@.tk2msftngp13.phx.gbl...
> If the application is requesting space in TempDB and the request interval
is
> faster than the disk can allocate the space then you will see this message
> whilst the Autogrow is happening.
> If you have this much space then try pre allocating a larger TempDB
>
> --
> --
> Allan Mitchell (Microsoft SQL Server MVP)
> MCSE,MCDBA
> www.SQLDTS.com
> I support PASS - the definitive, global community
> for SQL Server professionals - http://www.sqlpass.org
> "Stressed" <k@.c.co.uk> wrote in message
> news:ufQ6UCJlDHA.2536@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> >
> >
> > I've the following error message, which doesn't make sense to me.
> >
> > The log file is not full, it has autogrow set to on and the disk drive
on
> > which it
> >
> > resides has 256GB free space. I hope i'm missing something and welcome
> >
> > any suggestions on what to do or what to look at.
> >
> >
> >
> > "Server: Msg 9002, Level 17, State 6, Line 1
> >
> >
> >
> > The log file for database 'tempdb' is full. Back up the
> >
> > transaction log for the database to free up some log space."
> >
> >
>|||Just to add - check with Profiler what is going on. TempDb could be a target
of a DoS attack.
--
Dejan Sarka, SQL Server MVP
Please reply only to the newsgroups.
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:O$FlXLJlDHA.1084@.tk2msftngp13.phx.gbl...
> If the application is requesting space in TempDB and the request interval
is
> faster than the disk can allocate the space then you will see this message
> whilst the Autogrow is happening.
> If you have this much space then try pre allocating a larger TempDB
>
> --
> --
> Allan Mitchell (Microsoft SQL Server MVP)
> MCSE,MCDBA
> www.SQLDTS.com
> I support PASS - the definitive, global community
> for SQL Server professionals - http://www.sqlpass.org
> "Stressed" <k@.c.co.uk> wrote in message
> news:ufQ6UCJlDHA.2536@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> >
> >
> > I've the following error message, which doesn't make sense to me.
> >
> > The log file is not full, it has autogrow set to on and the disk drive
on
> > which it
> >
> > resides has 256GB free space. I hope i'm missing something and welcome
> >
> > any suggestions on what to do or what to look at.
> >
> >
> >
> > "Server: Msg 9002, Level 17, State 6, Line 1
> >
> >
> >
> > The log file for database 'tempdb' is full. Back up the
> >
> > transaction log for the database to free up some log space."
> >
> >
>|||The server isn't exposed to the outside world, although the point has been
taken
on board for future occurences of the same.
Thanks.
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:OPFEUOJlDHA.3024@.tk2msftngp13.phx.gbl...
> Just to add - check with Profiler what is going on. TempDb could be a
target
> of a DoS attack.
> --
> Dejan Sarka, SQL Server MVP
> Please reply only to the newsgroups.
> "Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
> news:O$FlXLJlDHA.1084@.tk2msftngp13.phx.gbl...
> > If the application is requesting space in TempDB and the request
interval
> is
> > faster than the disk can allocate the space then you will see this
message
> > whilst the Autogrow is happening.
> >
> > If you have this much space then try pre allocating a larger TempDB
> >
> >
> >
> > --
> > --
> >
> > Allan Mitchell (Microsoft SQL Server MVP)
> > MCSE,MCDBA
> > www.SQLDTS.com
> > I support PASS - the definitive, global community
> > for SQL Server professionals - http://www.sqlpass.org
> >
> > "Stressed" <k@.c.co.uk> wrote in message
> > news:ufQ6UCJlDHA.2536@.tk2msftngp13.phx.gbl...
> > > Hi,
> > >
> > >
> > >
> > > I've the following error message, which doesn't make sense to me.
> > >
> > > The log file is not full, it has autogrow set to on and the disk drive
> on
> > > which it
> > >
> > > resides has 256GB free space. I hope i'm missing something and welcome
> > >
> > > any suggestions on what to do or what to look at.
> > >
> > >
> > >
> > > "Server: Msg 9002, Level 17, State 6, Line 1
> > >
> > >
> > >
> > > The log file for database 'tempdb' is full. Back up the
> > >
> > > transaction log for the database to free up some log space."
> > >
> > >
> >
> >
>sql

error 9002 occur

I found this error on my sql server:
The log file for database dbname is full. Back up the transaction log for
the database to free up some log space.
Then I run the backup program for transaction log, now my sql can work fine.
But the .LDF file still very big. Can I decrease this file's size?
Such as defrag or compress'Dear all:
I've check the file again and find out that the .LDF file was smaller then
before!
From 3G to 1M !!! I think its because the backup.
But why not change size immedialy?
Thank you very much!
"LetsCount" <come2@.ms1.pchome.com.tw> ¦b¶l¥ó
news:u82uPwQxDHA.2356@.TK2MSFTNGP12.phx.gbl ¤¤¼¶¼g...
> I found this error on my sql server:
> The log file for database dbname is full. Back up the transaction log for
> the database to free up some log space.
> Then I run the backup program for transaction log, now my sql can work
fine.
> But the .LDF file still very big. Can I decrease this file's size?
> Such as defrag or compress'
>|||Check out below KB articles:
INF: How to Shrink the SQL Server 7.0 Transaction Log
http://support.microsoft.com/default.aspx?scid=kb;en-us;256650
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/default.aspx?scid=kb;en-us;272318
Log File Grows too big
http://www.support.microsoft.com/?id=317375
Log file filling up
http://www.support.microsoft.com/?id=110139
Considerations for Autogrow and AutoShrink
http://www.support.microsoft.com/?id=315512
http://www.mssqlserver.com/faq/logs-shrinklog.asp
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"LetsCount" <come2@.ms1.pchome.com.tw> wrote in message news:u82uPwQxDHA.2356@.TK2MSFTNGP12.phx.gbl...
> I found this error on my sql server:
> The log file for database dbname is full. Back up the transaction log for
> the database to free up some log space.
> Then I run the backup program for transaction log, now my sql can work fine.
> But the .LDF file still very big. Can I decrease this file's size?
> Such as defrag or compress'
>

Monday, March 26, 2012

Error 823 that I cant fix

Hi,

I am running SQL 2000 server for datawarehousing and I am getting the following error in the application log when I build large tables:

Error: 823, Severity: 24, State: 3
I/O error 33(The process cannot access the file because another process has locked a portion of the file.) detected during write at offset 0x00000829618000 in file '<file name.mdf>'

I have run through MS Support and really haven't found helpful info on this. I don't know what process is locking the mdf file, but I don't beleive there are any server or even client side programs running against this datafile.

Any thoughts?

joeNot come across that error before, but I would try looking under the Managment section of your server in Enterprise Manager then Locks/Objects and see if you can spot an offending process. If there is one it may be worth trying to kill it.

Sunday, March 11, 2012

Error 605

I'm currently helping in error-checking problematic SQL-server 2000
installation.
They've started to get this error in the log usually when the reindex-job is
running on the database but sometimes at other times too:
DBCC CHECKDB (ProductionDB) executed by DOMAIN\user01 found 0 errors and
repaired 0 errors.
Getpage: bstat=0x9, sstat=0, cache
pageno is/should be: objid is/should be:
Getpage: bstat=0x9, sstat=0, cache
Getpage: bstat=0x9, sstat=0, cache
pageno is/should be: objid is/should be:
Getpage: bstat=0x9, sstat=0, cache
(1:1772011)/(1:1772011) 0/930818378
pageno is/should be: objid is/should be:
pageno is/should be: objid is/should be:
(1:1772011)/(1:1772011) 0/930818378
(1:1772011)/(1:1772011) 0/930818378
(1:1772011)/(1:1772011) 0/930818378
... IAM indicates that page is allocated to this object
... IAM indicates that page is allocated to this object
... IAM indicates that page is allocated to this object
... IAM indicates that page is allocated to this object
Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:1772011) in database 'ProductionDB' belongs
to object '0', not to object 'Table1'..
The server is a failover-clustered server with SQL 2000 and Windows 2000.
Before this problem they had a problematic HD that they replaced. The
problem seemed to be gone after the replacement but resurfaced a little
later.
I started to think that the problem was related to the write-cache, so I
checked the write-cache on raid-controller and it was turned off. Wanting to
know if there was a possibility that the write-cache on the HDs was the
problem I got the answer that there is no cache on the disks or at least no
possablity to turn of the disk cache on them?
I also get this message in the beginning of the sqliostress-testlog:
"*** WARNING: Write caching ALLOWED"
I still had a feeling that the problem was hardware related and ran
sqliostress.exe and it came through fine. Thinking that the problem just
appears under load I ran 5 simultanious instances of sqliostress and got a
problem in one of the logs:
Pattern for page 1 is A
ERROR: LSN not found for page 1. Currently at slot 1 page 1 in log
searching for LSN 3
---
ERROR: Did not find expected pattern in file for page 1.
Bytes read = 8192
Potential torn write
---
Sector: 0 LSN: 3 Page: 0
[AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA...[sic]
ERROR: Appears to be a premature truncation of file. Pages expected: 32000,
Pages Read: 1, Last Error: 0
Current LSN is 32001
Verifing complete.
Ok, what next? Is the problem the HD-cache or something else in the
raid-system that possibly could create this problem or should I look
somewhere else?Anyone?|||Hi John, your assumptions are the same as the ones I would have
probably jumped to. Lets assume that the DB is inconsistent (perhaps
down to that faulty drive) ....
You say you are running the DBCC checkdb command, however have you
tried actually repairing the db using on of the repair parameters. I
would probably start off with the REPAIR_FAST option (if it is a
production db), but you might have to bite the bullet and use
REPAIR_ALLOW_DATA_LOSS might be an idea to do it with WITH ALL_ERRORMSGS
Br,
Mark Broadbent
mcdba , mcse+i
=============|||Mark Broadbent wrote:
> Hi John, your assumptions are the same as the ones I would have
> probably jumped to. Lets assume that the DB is inconsistent (perhaps
> down to that faulty drive) ....
> You say you are running the DBCC checkdb command, however have you
> tried actually repairing the db using on of the repair parameters. I
> would probably start off with the REPAIR_FAST option (if it is a
> production db), but you might have to bite the bullet and use
> REPAIR_ALLOW_DATA_LOSS might be an idea to do it with WITH
> ALL_ERRORMSGS
and I should add.. make sure you have a current backup to rely upon
before you start this process.
--
Br,
Mark Broadbent
mcdba , mcse+i
=============|||Thanks for your answer Mark!
Yes, I've tried running dbcc repair and it showed no problems.
After these error is reported I always also run a dbcc checkdb which
doesen't indicate any problems.
The problem is that the nightly reindex job is failing about half the times
with this error (it runs 3 times a week).
I started to belive that there was an "erranous errormessage" and that the
data wasn't damaged becaus the checks and repairs never reported any
problems.
However two weeks ago the same problem appeared and this time there was some
damage to one of the tables...after a repair with dataloss the problem was
fixed though (luckily it wasn't any table that contained uniqe data this
time...).
I also have tried to create a new empty database and transfer the data
there, in the case that the disk problems that has been fixed had made some
sort of "invisible" damage to the database that the checks couldn't fix. It
didn't fix the problem however.
The breakthrough as I see it is that I think that I've managed to reproduced
the problem by running sqliostress in five parallel instances and got one a
possible torn page in one of the logs...that should indicate a problem in
the disk-subsystem...right?
"Mark Broadbent" <no-spam-please_mark.broadbent@.virgin.net> wrote in message
news:#kMJelDqDHA.644@.TK2MSFTNGP11.phx.gbl...
> Hi John, your assumptions are the same as the ones I would have
> probably jumped to. Lets assume that the DB is inconsistent (perhaps
> down to that faulty drive) ....
> You say you are running the DBCC checkdb command, however have you
> tried actually repairing the db using on of the repair parameters. I
> would probably start off with the REPAIR_FAST option (if it is a
> production db), but you might have to bite the bullet and use
> REPAIR_ALLOW_DATA_LOSS might be an idea to do it with WITH ALL_ERRORMSGS
>
> --
> Br,
> Mark Broadbent
> mcdba , mcse+i
> =============|||John Horn wrote:
> Thanks for your answer Mark!
> Yes, I've tried running dbcc repair and it showed no problems.
> After these error is reported I always also run a dbcc checkdb which
> doesen't indicate any problems.
> The problem is that the nightly reindex job is failing about half the
> times with this error (it runs 3 times a week).
> I started to belive that there was an "erranous errormessage" and
> that the data wasn't damaged becaus the checks and repairs never
> reported any problems.
> However two weeks ago the same problem appeared and this time there
> was some damage to one of the tables...after a repair with dataloss
> the problem was fixed though (luckily it wasn't any table that
> contained uniqe data this time...).
> I also have tried to create a new empty database and transfer the data
> there, in the case that the disk problems that has been fixed had
> made some sort of "invisible" damage to the database that the checks
> couldn't fix. It didn't fix the problem however.
> The breakthrough as I see it is that I think that I've managed to
> reproduced the problem by running sqliostress in five parallel
> instances and got one a possible torn page in one of the logs...that
> should indicate a problem in the disk-subsystem...right?
>
>
> "Mark Broadbent" <no-spam-please_mark.broadbent@.virgin.net> wrote in
> message news:#kMJelDqDHA.644@.TK2MSFTNGP11.phx.gbl...
> > Hi John, your assumptions are the same as the ones I would have
> > probably jumped to. Lets assume that the DB is inconsistent (perhaps
> > down to that faulty drive) ....
> > You say you are running the DBCC checkdb command, however have you
> > tried actually repairing the db using on of the repair parameters. I
> > would probably start off with the REPAIR_FAST option (if it is a
> > production db), but you might have to bite the bullet and use
> > REPAIR_ALLOW_DATA_LOSS might be an idea to do it with WITH
> > ALL_ERRORMSGS
> >
> >
> > --
> >
> > Br,
> > Mark Broadbent
> > mcdba , mcse+i
> > =============
Yes I certainly think you are looking in the right place. I would
expect it to be either the disks or controller -the former you would
expect to fail in array eventually if there was a problem.
I once had a problem with a server (non sql) where every now and again
a disk would fail OR the server would crash. Every time we would chkdsk
/f it and get the thing going. All hardware looked fine (compaq insight
didnt report problems). We software monitored it for yonks -fine...
again a crash would happen. Failed Disks were replaced left/right and
centre ....then eventually we replaced the external disk array and
the raid controller, and to be honest I cant remember which one
resolved the problem, -but the problem WAS resolved. Your best bet is
to swap out the controller first and then take it from there.
Good Luck with troubleshooting!
--
Br,
Mark Broadbent
mcdba , mcse+i
=============

Error 602: Could not find row in sysindexes for....HELP HELP HELP

Hi,
I am getting following error in SQL Server (SQL Server 6.5) Log.
"Could not find row in sysindexes for database ID %d, object ID %ld, index
ID %d. Run DBCC CHECKTABLE on sysindexes"
I have checked on MSDN but no help. The MSDN artical is saying that there
could be some SP that is uding either a dropped table or dropped index but i
n
my case neither a table is drooped not an index...
Further more (if it helps..)...My application has an inbuild error logger
which logs the error into out table whenever it occurs which tells us the
error line number in VB code. This error line number is defined by me and
logged as well. So in this case it it pointing to the SQL which is a left
join between 2 tables which doesn't join on the column specified by index ID
specified in the error.
Please help me in solving this...as this has stopped our one of the live
site and its not working ny more and my manager is behind me...
I am really on my nees...
All the help are appriciated...but please helpIn addition to the following details, I think one more information may also
helpful. I am getting this error in the interval of every 3 to 4 minutes and
I don't know how SQL server writes this message in log with a consistant
interval.
Any ideas or help?
"Prateek Baxi" wrote:

> Hi,
> I am getting following error in SQL Server (SQL Server 6.5) Log.
> "Could not find row in sysindexes for database ID %d, object ID %ld, index
> ID %d. Run DBCC CHECKTABLE on sysindexes"
> I have checked on MSDN but no help. The MSDN artical is saying that there
> could be some SP that is uding either a dropped table or dropped index but
in
> my case neither a table is drooped not an index...
> Further more (if it helps..)...My application has an inbuild error logger
> which logs the error into out table whenever it occurs which tells us the
> error line number in VB code. This error line number is defined by me and
> logged as well. So in this case it it pointing to the SQL which is a left
> join between 2 tables which doesn't join on the column specified by index
ID
> specified in the error.
> Please help me in solving this...as this has stopped our one of the live
> site and its not working ny more and my manager is behind me...
> I am really on my nees...
> All the help are appriciated...but please help

Error 602: Could not find row in sysindexes for....HELP HELP HELP

Hi,
I am getting following error in SQL Server (SQL Server 6.5) Log.
"Could not find row in sysindexes for database ID %d, object ID %ld, index
ID %d. Run DBCC CHECKTABLE on sysindexes"
I have checked on MSDN but no help. The MSDN artical is saying that there
could be some SP that is uding either a dropped table or dropped index but in
my case neither a table is drooped not an index...
Further more (if it helps..)...My application has an inbuild error logger
which logs the error into out table whenever it occurs which tells us the
error line number in VB code. This error line number is defined by me and
logged as well. So in this case it it pointing to the SQL which is a left
join between 2 tables which doesn't join on the column specified by index ID
specified in the error.
Please help me in solving this...as this has stopped our one of the live
site and its not working ny more and my manager is behind me...
I am really on my nees...
All the help are appriciated...but please helpIn addition to the following details, I think one more information may also
helpful. I am getting this error in the interval of every 3 to 4 minutes and
I don't know how SQL server writes this message in log with a consistant
interval.
Any ideas or help?
"Prateek Baxi" wrote:
> Hi,
> I am getting following error in SQL Server (SQL Server 6.5) Log.
> "Could not find row in sysindexes for database ID %d, object ID %ld, index
> ID %d. Run DBCC CHECKTABLE on sysindexes"
> I have checked on MSDN but no help. The MSDN artical is saying that there
> could be some SP that is uding either a dropped table or dropped index but in
> my case neither a table is drooped not an index...
> Further more (if it helps..)...My application has an inbuild error logger
> which logs the error into out table whenever it occurs which tells us the
> error line number in VB code. This error line number is defined by me and
> logged as well. So in this case it it pointing to the SQL which is a left
> join between 2 tables which doesn't join on the column specified by index ID
> specified in the error.
> Please help me in solving this...as this has stopped our one of the live
> site and its not working ny more and my manager is behind me...
> I am really on my nees...
> All the help are appriciated...but please help

Error 602: Could not find row in sysindexes for....HELP HELP HELP

Hi,
I am getting following error in SQL Server (SQL Server 6.5) Log.
"Could not find row in sysindexes for database ID %d, object ID %ld, index
ID %d. Run DBCC CHECKTABLE on sysindexes"
I have checked on MSDN but no help. The MSDN artical is saying that there
could be some SP that is uding either a dropped table or dropped index but in
my case neither a table is drooped not an index...
Further more (if it helps..)...My application has an inbuild error logger
which logs the error into out table whenever it occurs which tells us the
error line number in VB code. This error line number is defined by me and
logged as well. So in this case it it pointing to the SQL which is a left
join between 2 tables which doesn't join on the column specified by index ID
specified in the error.
Please help me in solving this...as this has stopped our one of the live
site and its not working ny more and my manager is behind me...
I am really on my nees...
All the help are appriciated...but please help
In addition to the following details, I think one more information may also
helpful. I am getting this error in the interval of every 3 to 4 minutes and
I don't know how SQL server writes this message in log with a consistant
interval.
Any ideas or help?
"Prateek Baxi" wrote:

> Hi,
> I am getting following error in SQL Server (SQL Server 6.5) Log.
> "Could not find row in sysindexes for database ID %d, object ID %ld, index
> ID %d. Run DBCC CHECKTABLE on sysindexes"
> I have checked on MSDN but no help. The MSDN artical is saying that there
> could be some SP that is uding either a dropped table or dropped index but in
> my case neither a table is drooped not an index...
> Further more (if it helps..)...My application has an inbuild error logger
> which logs the error into out table whenever it occurs which tells us the
> error line number in VB code. This error line number is defined by me and
> logged as well. So in this case it it pointing to the SQL which is a left
> join between 2 tables which doesn't join on the column specified by index ID
> specified in the error.
> Please help me in solving this...as this has stopped our one of the live
> site and its not working ny more and my manager is behind me...
> I am really on my nees...
> All the help are appriciated...but please help

Friday, March 9, 2012

Error 5020 after try to delete one of log files

Platform: SQL Server 2k with sp2
OS: W2k sp2
I tried to move log files at one database from location A
to another location B. I first created new log fileB.ldf
for this database at locationB. Then shrank the original
log fileA.ldf as much as possible. Next I tried to
delete fileA from SQL Server EM -> properties ->
transaction log-> highligt fileA.ldf -> delete. But I got
error 5020: The primary data or log file cannot be removed
from a database.
How can I drop or move log files from database?
Thanks.Maggie,
First, detach the database using sp_detach_db after making sure that users
are not accessing it.Once done, the database is thus offline.Now copy the
.ldf file to location B.Attach the database using sp_attach_db, mentioning
the new location for .ldf.
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Maggie" <seamorning@.yahoo.com> wrote in message
news:5d4901c35781$4df49c60$a001280a@.phx.gbl...
> Platform: SQL Server 2k with sp2
> OS: W2k sp2
> I tried to move log files at one database from location A
> to another location B. I first created new log fileB.ldf
> for this database at locationB. Then shrank the original
> log fileA.ldf as much as possible. Next I tried to
> delete fileA from SQL Server EM -> properties ->
> transaction log-> highligt fileA.ldf -> delete. But I got
> error 5020: The primary data or log file cannot be removed
> from a database.
> How can I drop or move log files from database?
> Thanks.|||Go to EM, right click the database, then Transaction Log tab, select the 2nd
log file, press Delete button.
You can't delete first log file, but other log files you can delete.
"Maggie" <seamorning@.yahoo.com> wrote in message
news:5e5d01c3578e$5cd34cb0$a001280a@.phx.gbl...
> How can just delete the extra log files from one
> location? I only want to keep one?
> >--Original Message--
> >Maggie,
> >
> >First, detach the database using sp_detach_db after
> making sure that users
> >are not accessing it.Once done, the database is thus
> offline.Now copy the
> >..ldf file to location B.Attach the database using
> sp_attach_db, mentioning
> >the new location for .ldf.
> >
> >--
> >Dinesh.
> >SQL Server FAQ at
> >http://www.tkdinesh.com
> >
> >"Maggie" <seamorning@.yahoo.com> wrote in message
> >news:5d4901c35781$4df49c60$a001280a@.phx.gbl...
> >> Platform: SQL Server 2k with sp2
> >> OS: W2k sp2
> >> I tried to move log files at one database from location
> A
> >> to another location B. I first created new log
> fileB.ldf
> >> for this database at locationB. Then shrank the
> original
> >> log fileA.ldf as much as possible. Next I tried to
> >> delete fileA from SQL Server EM -> properties ->
> >> transaction log-> highligt fileA.ldf -> delete. But I
> got
> >> error 5020: The primary data or log file cannot be
> removed
> >> from a database.
> >>
> >> How can I drop or move log files from database?
> >>
> >> Thanks.
> >
> >
> >.
> >

Wednesday, March 7, 2012

Error 3627 (Could not create worker thread) - Transaction Log Back

Recieved this error this morning, at the same time are users were kicked out
of SQL Server.
We have anout 1500 connections at a time. There are no SQL Error log entries
other than the Transaction Log failing, no Application Events or System
Events.
The server did not go down, the CPUs (8) went to almost zero.
SQL Server Enterprise Manager was getting a network error message when
trying to connect and within 5 minutes everything was OK.
Any help?
Thanks,
ThomasLLCould it be that you were over your max worker threads?
http://msdn2.microsoft.com/en-us/library/ms187024.aspx
When all worker threads are active with long running queries, SQL Server may
appear unresponsive until a worker thread completes and becomes available.
Though not a defect, this can sometimes be undesirable. If a process appears
to be unresponsive and no new queries can be processed, then connect to SQL
Server using the dedicated administrator connection (DAC), and kill the
process. To prevent this, increase the number of max worker threads.
--
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Thomas.LeBlanc@.NoSpam.Com"
<ThomasLeBlancNoSpamCom@.discussions.microsoft.com> wrote in message
news:759C0C8D-1413-45CB-BE38-743CF952CBF5@.microsoft.com...
> Recieved this error this morning, at the same time are users were kicked
> out
> of SQL Server.
> We have anout 1500 connections at a time. There are no SQL Error log
> entries
> other than the Transaction Log failing, no Application Events or System
> Events.
> The server did not go down, the CPUs (8) went to almost zero.
> SQL Server Enterprise Manager was getting a network error message when
> trying to connect and within 5 minutes everything was OK.
> Any help?
> Thanks,
> ThomasLL|||Are you using any third party backup software?
You can also get this error if you are running low on system
resources - mostly memory.
You may have too much of a server load at the time you tried
to do the backup. You'd want to get some baselines numbers
using Performance Monitor.
-Sue
On Mon, 9 Oct 2006 09:54:02 -0700, Thomas.LeBlanc@.NoSpam.Com
<ThomasLeBlancNoSpamCom@.discussions.microsoft.com> wrote:
>Recieved this error this morning, at the same time are users were kicked out
>of SQL Server.
>We have anout 1500 connections at a time. There are no SQL Error log entries
>other than the Transaction Log failing, no Application Events or System
>Events.
>The server did not go down, the CPUs (8) went to almost zero.
>SQL Server Enterprise Manager was getting a network error message when
>trying to connect and within 5 minutes everything was OK.
>Any help?
>Thanks,
>ThomasLL|||We are on SQL Server 2000, no error message that we have exceeded Work Threads.
We do have 8 processors and 64 Gigs, neither are maxed out.
Thanks for your responce.
Most sites I have read say you should NOT increase worker threads because of
overhead with more threads.
Cache Hit Ratio 101.05824
Cache Flushes 0.0
Free Page Scan (Avg) 0.0
Free Page Scan (Max) 0.0
Min Free Buffers 331.0
Cache Size 4362.0
Free Buffers 2261.0
--
Thanks,
ThomasLL
"Warren Brunk" wrote:
> Could it be that you were over your max worker threads?
> http://msdn2.microsoft.com/en-us/library/ms187024.aspx
> When all worker threads are active with long running queries, SQL Server may
> appear unresponsive until a worker thread completes and becomes available.
> Though not a defect, this can sometimes be undesirable. If a process appears
> to be unresponsive and no new queries can be processed, then connect to SQL
> Server using the dedicated administrator connection (DAC), and kill the
> process. To prevent this, increase the number of max worker threads.
> --
> /*
> Warren Brunk - MCITP - SQL 2005, MCDBA
> www.techintsolutions.com
> */
>
> "Thomas.LeBlanc@.NoSpam.Com"
> <ThomasLeBlancNoSpamCom@.discussions.microsoft.com> wrote in message
> news:759C0C8D-1413-45CB-BE38-743CF952CBF5@.microsoft.com...
> > Recieved this error this morning, at the same time are users were kicked
> > out
> > of SQL Server.
> >
> > We have anout 1500 connections at a time. There are no SQL Error log
> > entries
> > other than the Transaction Log failing, no Application Events or System
> > Events.
> >
> > The server did not go down, the CPUs (8) went to almost zero.
> >
> > SQL Server Enterprise Manager was getting a network error message when
> > trying to connect and within 5 minutes everything was OK.
> >
> > Any help?
> >
> > Thanks,
> > ThomasLL
>
>|||> Are you using any third party backup software?
No
We are on SQL Server 2000, no error message that we have exceeded Work
Threads.
We do have 8 processors and 64 Gigs, neither are maxed out.
Thanks for your responce.
Most sites I have read say you should NOT increase worker threads because of
overhead with more threads.
Cache Hit Ratio 101.05824
Cache Flushes 0.0
Free Page Scan (Avg) 0.0
Free Page Scan (Max) 0.0
Min Free Buffers 331.0
Cache Size 4362.0
Free Buffers 2261.0
--
Thanks,
ThomasLL
--
Thanks,
ThomasLL,
"Sue Hoegemeier" wrote:
> Are you using any third party backup software?
> You can also get this error if you are running low on system
> resources - mostly memory.
> You may have too much of a server load at the time you tried
> to do the backup. You'd want to get some baselines numbers
> using Performance Monitor.
> -Sue
> On Mon, 9 Oct 2006 09:54:02 -0700, Thomas.LeBlanc@.NoSpam.Com
> <ThomasLeBlancNoSpamCom@.discussions.microsoft.com> wrote:
> >Recieved this error this morning, at the same time are users were kicked out
> >of SQL Server.
> >
> >We have anout 1500 connections at a time. There are no SQL Error log entries
> >other than the Transaction Log failing, no Application Events or System
> >Events.
> >
> >The server did not go down, the CPUs (8) went to almost zero.
> >
> >SQL Server Enterprise Manager was getting a network error message when
> >trying to connect and within 5 minutes everything was OK.
> >
> >Any help?
> >
> >Thanks,
> >ThomasLL
>|||You are correct about the worker threads which is why I
didn't suggest changing that setting. On SQL 2000, you will
almost always have problems if you increase the value from
the default 255. It is not advisable and you would want to
be monitoring UMS stats as well as other indicators before
even considering changing that.
But...most of the time the error you received is really due
to resource constraints. A one time snapshot of a few
performance metrics isn't going to tell you much. The
article on sql-server-performance.com for performance audits
provides some good information on what you want to check:
http://www.sql-server-performance.com/sql_server_performance_audit.asp
-Sue
On Mon, 9 Oct 2006 13:32:01 -0700, Thomas.LeBlanc@.NoSpam.Com
<ThomasLeBlancNoSpamCom@.discussions.microsoft.com> wrote:
>> Are you using any third party backup software?
>No
>We are on SQL Server 2000, no error message that we have exceeded Work
>Threads.
>We do have 8 processors and 64 Gigs, neither are maxed out.
>Thanks for your responce.
>Most sites I have read say you should NOT increase worker threads because of
>overhead with more threads.
>Cache Hit Ratio 101.05824
>Cache Flushes 0.0
>Free Page Scan (Avg) 0.0
>Free Page Scan (Max) 0.0
>Min Free Buffers 331.0
>Cache Size 4362.0
>Free Buffers 2261.0
>--
>Thanks,
>ThomasLL|||Thanks everyone!!!
--
Thanks,
ThomasLL, MCDBA
"Thomas.LeBlanc@.NoSpam.Com" wrote:
> Recieved this error this morning, at the same time are users were kicked out
> of SQL Server.
> We have anout 1500 connections at a time. There are no SQL Error log entries
> other than the Transaction Log failing, no Application Events or System
> Events.
> The server did not go down, the CPUs (8) went to almost zero.
> SQL Server Enterprise Manager was getting a network error message when
> trying to connect and within 5 minutes everything was OK.
> Any help?
> Thanks,
> ThomasLL

Error 3627 (Could not create worker thread) - Transaction Log Back

error 3624 severity 20 SQL server was stopped often

hi~~
anyone met this error message
server is SQL2000(sp3)
below is the error log
---
spid66 Using 'dbghelp.dll' version '4.0.5'...
spid66 Stack Signature for the dump is 0x50347D98
spid66 SQL Server assertion : file : <recbase.cpp>,line=1378 ...
spid66 Using 'dbghelp.dll' version '4.0.5'...
spid66 SQL Server assertion: file: <umsio.cpp>,line=117 ...
spid66 Stack Signature for the dump is 0x57421D8E
Using 'dbghelp.dll' version '4.0.5'...
spid119 error: 3624, severity 20, state: 1.
spid66 SQL Server assertion file: <umsio.cpp>,line=563 ...
---
help me~~~~These types of problems are most often bugs in SQL Server. If you are up on service pack and didn't
find anything in KB about your problems you should open a case with MS Support.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"changsoon" <pcs73@.chol.com> wrote in message news:OrsfPMOrDHA.920@.TK2MSFTNGP10.phx.gbl...
> hi~~
> anyone met this error message
> server is SQL2000(sp3)
> below is the error log
> ---
> spid66 Using 'dbghelp.dll' version '4.0.5'...
> spid66 Stack Signature for the dump is 0x50347D98
> spid66 SQL Server assertion : file : <recbase.cpp>,line=1378 ...
> spid66 Using 'dbghelp.dll' version '4.0.5'...
> spid66 SQL Server assertion: file: <umsio.cpp>,line=117 ...
> spid66 Stack Signature for the dump is 0x57421D8E
> Using 'dbghelp.dll' version '4.0.5'...
> spid119 error: 3624, severity 20, state: 1.
> spid66 SQL Server assertion file: <umsio.cpp>,line=563 ...
> ---
> help me~~~~
>

Error 3624 doing trans log backup

I get Error 3624 sporadically when doing trans log backups,
Any clues as to why?
ThanksIt is helpful if you post the actual error message, as most of us haven't memorized all error
messages. Actually, I didn't even find 3624 in sysmessages, so that doesn't seem to be an SQL Server
error message.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Richard Buchner" <rbuchner@.hpsg.com> wrote in message
news:019001c37f99$de393200$a101280a@.phx.gbl...
> I get Error 3624 sporadically when doing trans log backups,
> Any clues as to why?
> Thanks|||Tibor,
below is the messages, this is wile doing trans log dump
of Great Plains db's, Thanks
________________________________________________________
2003-09-11 00:27:10.45 spid54 Stack Signature for the
dump is 0x21F5A243
2003-09-11 00:27:10.49 spid54 SQL Server Assertion:
File: <p:\sql\ntdbms\storeng\drs\include\record.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <=MAXDATAROW'.
2003-09-11 00:27:10.49 spid54 Error: 3624, Severity:
20, State: 1.
______________________________________________________
>--Original Message--
>It is helpful if you post the actual error message, as
most of us haven't memorized all error
>messages. Actually, I didn't even find 3624 in
sysmessages, so that doesn't seem to be an SQL Server
>error message.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
>"Richard Buchner" <rbuchner@.hpsg.com> wrote in message
>news:019001c37f99$de393200$a101280a@.phx.gbl...
>> I get Error 3624 sporadically when doing trans log
backups,
>> Any clues as to why?
>> Thanks
>
>.
>

Error 3624 - SQL-DMO(ODBC SQLState:HY000)

My ProjectServer database suddenly became (suspect), the log file increased
like balloon 49.9GB, I don't know exactly what was the size before. The mdf
file is about 640MB. To get the situation worst, the backup wasn't good,
tried to copy the file to a different folder, so a detached the DB to copy
both of them.
Later I tried to attach the DB back and it gave me this error message.
(SQL2000 SP3)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:321
Expression: m_len !=0
SPID: 54
Process ID: 1832"
================================
(After applying SP4)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:359
Expression: m_len !=0
SPID: 54
Process ID: 1896"
Where do I start, is there any repai utility to fix this problem?
I am not a database or SQL expert, any help will be very appreciated.
I can't attach the database back anymore.
Johnny
Hi Johnny
You have probably run out of space where the log file is located. You can
check for open transactions in the database using DBCC OPENTRAN, but there
should not be any as you have detached the database. Use BACKUP LOG to free
up the log file and DBCC SHRINKFILE to shrink it. You may want to see
http://msdn.microsoft.com/library/de...r_da2_1uzr.asp
Once a reasonable size you should change the growth amount to be a fixed
value and not a percentage.
To change the database so it is not suspect see
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
You should also implement a backup schedule or maintenance plan that will
backup the database and also backup the logs.
John
"Johnny" wrote:

> My ProjectServer database suddenly became (suspect), the log file increased
> like balloon 49.9GB, I don't know exactly what was the size before. The mdf
> file is about 640MB. To get the situation worst, the backup wasn't good,
> tried to copy the file to a different folder, so a detached the DB to copy
> both of them.
> Later I tried to attach the DB back and it gave me this error message.
> (SQL2000 SP3)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:321
> Expression: m_len !=0
> SPID: 54
> Process ID: 1832"
> ================================
> (After applying SP4)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:359
> Expression: m_len !=0
> SPID: 54
> Process ID: 1896"
> Where do I start, is there any repai utility to fix this problem?
> I am not a database or SQL expert, any help will be very appreciated.
> I can't attach the database back anymore.
> Johnny
>
>

Tuesday, March 27, 2012

Error 9004 attaching a database

Error 9003 : fail to attach a database

Error 9003 : fail to attach a database

Error 9002, tempdb log full

Error 9002, tempdb log full

Error 9002, tempdb log full

Error 9002 tempdb log file is full

error 9002 occur

Monday, March 26, 2012

Error 823 that I cant fix

Sunday, March 11, 2012

Error 605

Error 602: Could not find row in sysindexes for....HELP HELP HELP

Error 602: Could not find row in sysindexes for....HELP HELP HELP

Error 602: Could not find row in sysindexes for....HELP HELP HELP

Friday, March 9, 2012

Error 5020 after try to delete one of log files

Wednesday, March 7, 2012

Error 3627 (Could not create worker thread) - Transaction Log Back

Error 3627 (Could not create worker thread) - Transaction Log Back

Error 3627 (Could not create worker thread) - Transaction Log Back

error 3624 severity 20 SQL server was stopped often

Error 3624 doing trans log backup

Error 3624 - SQL-DMO(ODBC SQLState:HY000)

Error 207

Blog Archive

About Me