Showing posts with label dbcc. Show all posts
Showing posts with label dbcc. Show all posts

Tuesday, March 27, 2012

Error: Backup Log terminating abnormally

hi
i am using sql server 2000. when i try to backup log file it throws out the following error and hence the second command that is dbcc shrinkfile never gets executed. if i restart sql server and re-run these commands ... no error pops up ... both the comma
nds get completed sccessfully and log file gets shrunk too.
these are the commands that i run
BACKUP LOG BAMPrimaryImport WITH TRUNCATE_ONLY
DBCC SHRINKFILE ( BAMPrimaryImport_log, 500 )
this is the error that i get
Server: Msg 3023, Level 16, State 3, Line 1
Backup and file manipulation operations (such as ALTER DATABASE ADD FILE) on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
I am quite sure that no other command is active at the time when i issue these commands, still i get error. any help will be appreciated.
regards
yashrah.
Hi
Can you check your SQL Error log for the message when this command failed,
also can you please provide the SQL Server 2000 Service pack level.
you can get the Service pack level by running select @.@.version from query
analyzer.
Also, do you have replication set up, if yes, what kind of replication?
3023 means, It thinks there is some concurrent database operation going on
that is blocking the ALTER DATABASE, because it is unable to acquire the
database lock.
Regards
Sadeesh
This posting is provided AS IS with no warranties, and confers no rights.
"Yashrah [Xavor]" <YashrahXavor@.discussions.microsoft.com> wrote in message
news:73E811CE-FCBF-4D29-9538-6D22F842A8EC@.microsoft.com...
> hi
> i am using sql server 2000. when i try to backup log file it throws out
> the following error and hence the second command that is dbcc shrinkfile
> never gets executed. if i restart sql server and re-run these commands ...
> no error pops up ... both the commands get completed sccessfully and log
> file gets shrunk too.
> these are the commands that i run
> BACKUP LOG BAMPrimaryImport WITH TRUNCATE_ONLY
> DBCC SHRINKFILE ( BAMPrimaryImport_log, 500 )
> this is the error that i get
> Server: Msg 3023, Level 16, State 3, Line 1
> Backup and file manipulation operations (such as ALTER DATABASE ADD FILE)
> on a database must be serialized. Reissue the statement after the current
> backup or file manipulation operation is completed.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
> I am quite sure that no other command is active at the time when i issue
> these commands, still i get error. any help will be appreciated.
> regards
> yashrah.
|||thanx for ur concern...
SQL Error Log says
2004-07-22 02:40:23.10 backup BACKUP failed to complete the command exec shrink_bamprimaryimport_logfile
infact "shrink_bamprimaryimport_logfile" is my stored procedure that contains the two commands (backup log and dbcc shrinkfile) written below.
servie pack 3a is installed and no replication set up is there.
"Sadeesh[MSFT]" wrote:

> Hi
> Can you check your SQL Error log for the message when this command failed,
> also can you please provide the SQL Server 2000 Service pack level.
> you can get the Service pack level by running select @.@.version from query
> analyzer.
> Also, do you have replication set up, if yes, what kind of replication?
> 3023 means, It thinks there is some concurrent database operation going on
> that is blocking the ALTER DATABASE, because it is unable to acquire the
> database lock.
> Regards
> Sadeesh
> --
> This posting is provided AS IS with no warranties, and confers no rights.
> "Yashrah [Xavor]" <YashrahXavor@.discussions.microsoft.com> wrote in message
> news:73E811CE-FCBF-4D29-9538-6D22F842A8EC@.microsoft.com...
>
>

Error: Backup Log terminating abnormally

hi
i am using sql server 2000. when i try to backup log file it throws out the
following error and hence the second command that is dbcc shrinkfile never g
ets executed. if i restart sql server and re-run these commands ... no error
pops up ... both the comma
nds get completed sccessfully and log file gets shrunk too.
these are the commands that i run
BACKUP LOG BAMPrimaryImport WITH TRUNCATE_ONLY
DBCC SHRINKFILE ( BAMPrimaryImport_log, 500 )
this is the error that i get
Server: Msg 3023, Level 16, State 3, Line 1
Backup and file manipulation operations (such as ALTER DATABASE ADD FILE) on
a database must be serialized. Reissue the statement after the current back
up or file manipulation operation is completed.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
I am quite sure that no other command is active at the time when i issue the
se commands, still i get error. any help will be appreciated.
regards
yashrah.Hi
Can you check your SQL Error log for the message when this command failed,
also can you please provide the SQL Server 2000 Service pack level.
you can get the Service pack level by running select @.@.version from query
analyzer.
Also, do you have replication set up, if yes, what kind of replication?
3023 means, It thinks there is some concurrent database operation going on
that is blocking the ALTER DATABASE, because it is unable to acquire the
database lock.
Regards
Sadeesh
--
This posting is provided AS IS with no warranties, and confers no rights.
"Yashrah [Xavor]" <YashrahXavor@.discussions.microsoft.com> wrote in mess
age
news:73E811CE-FCBF-4D29-9538-6D22F842A8EC@.microsoft.com...
> hi
> i am using sql server 2000. when i try to backup log file it throws out
> the following error and hence the second command that is dbcc shrinkfile
> never gets executed. if i restart sql server and re-run these commands ...
> no error pops up ... both the commands get completed sccessfully and log
> file gets shrunk too.
> these are the commands that i run
> BACKUP LOG BAMPrimaryImport WITH TRUNCATE_ONLY
> DBCC SHRINKFILE ( BAMPrimaryImport_log, 500 )
> this is the error that i get
> Server: Msg 3023, Level 16, State 3, Line 1
> Backup and file manipulation operations (such as ALTER DATABASE ADD FILE)
> on a database must be serialized. Reissue the statement after the current
> backup or file manipulation operation is completed.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
> I am quite sure that no other command is active at the time when i issue
> these commands, still i get error. any help will be appreciated.
> regards
> yashrah.|||thanx for ur concern...
SQL Error Log says
2004-07-22 02:40:23.10 backup BACKUP failed to complete the command exec
shrink_bamprimaryimport_logfile
infact "shrink_bamprimaryimport_logfile" is my stored procedure that contain
s the two commands (backup log and dbcc shrinkfile) written below.
servie pack 3a is installed and no replication set up is there.
"Sadeesh[MSFT]" wrote:

> Hi
> Can you check your SQL Error log for the message when this command failed,
> also can you please provide the SQL Server 2000 Service pack level.
> you can get the Service pack level by running select @.@.version from query
> analyzer.
> Also, do you have replication set up, if yes, what kind of replication?
> 3023 means, It thinks there is some concurrent database operation going on
> that is blocking the ALTER DATABASE, because it is unable to acquire the
> database lock.
> Regards
> Sadeesh
> --
> This posting is provided AS IS with no warranties, and confers no rights.
> "Yashrah [Xavor]" <YashrahXavor@.discussions.microsoft.com> wrote in me
ssage
> news:73E811CE-FCBF-4D29-9538-6D22F842A8EC@.microsoft.com...
>
>sql

Monday, March 26, 2012

Error: 644

I get this warning when I do a dbcc checkdb:

Server: Msg 2750, Level 16, State 4, Line 2
Warning: Page (1:300465), Slot 9 in object 2009058193 Index 0 Column Val value -1.#QNAN is out of range for data type "real". Update column to a legal value.

A service using a stored procedure result in the following errir in the event log:

Error 644, Severity: 21, State 5
Could not find the index entry for RID '16ca8880200' in index page (1:31928), index ID 7, database 'BPS'.

I have tried 'dbcc checkdb' and 'dbcc checktable' both with option REPAIR_REBUILD and I have tried 'dbcc reindex' but none of them helped.

Are there other options or can I find the column that shall be updated to a legal value?Did you get any error messages when your ran the DBCC's?

Sounds like a corruption problem to me...

Can you export the data? You may need to do it in ranges...you'll find there will be probably 1 corrupt row...

SELECT * FROM myTable WHERE identity < 1000
and so on...do a binary search..start at the middle your data...

In either Case, you'll either need to do a restore (which hopefully isn't corrupt), or export the data and build a new db...don't know what else could be hosed..

But that's only my own opinion (MOO)|||Have you tried to drop the index and recreate it ?
Have you used the REPAIR_ALLOW_DATA_LOSS option ?

Thursday, March 22, 2012

Error: 5180 - Could not open FCB for invalid file ID #

When we do a DBCC SHRINKDATABASE <dbname>, 5 on one of our high volume
databases we get following errors:
- spid333 Error: 5180, Severity: 22, State: 1
- spid333 Could not open FCB for invalid file ID <#> in database '<dbname>'.
Is there anyone here that has a hint on what is causing this.
This error stated that the file was dropped or the database was corrupted.
- Please run DBCC SHRINKDATABASE again.
- If the error shows up again, please run DBCC CHECKDB to see if the
database is corrupted.
- If the database is not corrupted, then probably there is a bug in shrink
code, you can contact PSS for further assistant.
Stephen Jiang
Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tor Lynge Olsen" <TorLyngeOlsen@.discussions.microsoft.com> wrote in message
news:A5E9AA7C-6A4D-4527-A9EC-687A15216E91@.microsoft.com...
> When we do a DBCC SHRINKDATABASE <dbname>, 5 on one of our high volume
> databases we get following errors:
> - spid333 Error: 5180, Severity: 22, State: 1
> - spid333 Could not open FCB for invalid file ID <#> in database
'<dbname>'.
> Is there anyone here that has a hint on what is causing this.
>
sql

Error: 5180 - Could not open FCB for invalid file ID #

When we do a DBCC SHRINKDATABASE <dbname>, 5 on one of our high volume
databases we get following errors:
- spid333 Error: 5180, Severity: 22, State: 1
- spid333 Could not open FCB for invalid file ID <#> in database '<dbname>'.
Is there anyone here that has a hint on what is causing this.This error stated that the file was dropped or the database was corrupted.
- Please run DBCC SHRINKDATABASE again.
- If the error shows up again, please run DBCC CHECKDB to see if the
database is corrupted.
- If the database is not corrupted, then probably there is a bug in shrink
code, you can contact PSS for further assistant.
--
Stephen Jiang
Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tor Lynge Olsen" <TorLyngeOlsen@.discussions.microsoft.com> wrote in message
news:A5E9AA7C-6A4D-4527-A9EC-687A15216E91@.microsoft.com...
> When we do a DBCC SHRINKDATABASE <dbname>, 5 on one of our high volume
> databases we get following errors:
> - spid333 Error: 5180, Severity: 22, State: 1
> - spid333 Could not open FCB for invalid file ID <#> in database
'<dbname>'.
> Is there anyone here that has a hint on what is causing this.
>

Error: 5180 - Could not open FCB for invalid file ID #

When we do a DBCC SHRINKDATABASE <dbname>, 5 on one of our high volume
databases we get following errors:
- spid333 Error: 5180, Severity: 22, State: 1
- spid333 Could not open FCB for invalid file ID <#> in database '<dbname>
'.
Is there anyone here that has a hint on what is causing this.This error stated that the file was dropped or the database was corrupted.
- Please run DBCC SHRINKDATABASE again.
- If the error shows up again, please run DBCC CHECKDB to see if the
database is corrupted.
- If the database is not corrupted, then probably there is a bug in shrink
code, you can contact PSS for further assistant.
Stephen Jiang
Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tor Lynge Olsen" <TorLyngeOlsen@.discussions.microsoft.com> wrote in message
news:A5E9AA7C-6A4D-4527-A9EC-687A15216E91@.microsoft.com...
> When we do a DBCC SHRINKDATABASE <dbname>, 5 on one of our high volume
> databases we get following errors:
> - spid333 Error: 5180, Severity: 22, State: 1
> - spid333 Could not open FCB for invalid file ID <#> in database
'<dbname>'.
> Is there anyone here that has a hint on what is causing this.
>

Error: 3624 - SQL Server Assertion

Ok, I keep getting SQL Server assertions in the event log, with the
following stack dump message in the SQL Server logs. Any ideas?
DBCC CHECKDB reveals no problems.
* ----
--
2004-04-02 04:03:13.39 spid234 Stack Signature for the dump is 0x2EF0EDAD
2004-04-02 04:03:13.39 spid234 SQL Server Assertion: File: <insert.c>,
line=573
Failed Assertion = 'sdesP->m_pIndex->indindid == CLUSTIND'.
2004-04-02 04:03:13.39 spid234 Error: 3624, Severity: 20, State: 1.
*Dump thread - spid = 84, PSS = 0x3e049238, EC = 0x3e049560
*Stack Dump being sent to I:\Microsoft SQL Server\MSSQL\log\SQLDump0033.txt
*
****************************************************************************
***
Thanks in advance,
Jerry DennanyJerry,
If you search MS site for error 3624, which is mentioned in the stack dump,
you will find plenty of articles
(http://search.microsoft.com/search/results.aspx?View=en-us&p=1&s=0&c=3&st=b
&qu=3624&na=32). There are many possible reasons for this error. Just by
reading the article titles I guess you will be able to narrow the search to
your problem.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Jerry Dennany" <jerry@.dennany.org> wrote in message
news:uMM$BVDJEHA.556@.TK2MSFTNGP10.phx.gbl...
>
> Ok, I keep getting SQL Server assertions in the event log, with the
> following stack dump message in the SQL Server logs. Any ideas?
> DBCC CHECKDB reveals no problems.
>
>
* ----
> --
> 2004-04-02 04:03:13.39 spid234 Stack Signature for the dump is
0x2EF0EDAD
> 2004-04-02 04:03:13.39 spid234 SQL Server Assertion: File: <insert.c>,
> line=573
> Failed Assertion = 'sdesP->m_pIndex->indindid == CLUSTIND'.
> 2004-04-02 04:03:13.39 spid234 Error: 3624, Severity: 20, State: 1.
> *Dump thread - spid = 84, PSS = 0x3e049238, EC = 0x3e049560
> *Stack Dump being sent to I:\Microsoft SQL
Server\MSSQL\log\SQLDump0033.txt
> *
>
****************************************************************************
> ***
>
> Thanks in advance,
> Jerry Dennany
>|||I suppose that I should have mentioned that I've already performed the
typical google and support.microsoft.com searches, without finding anything
applicable. Any other ideas?
Thanks,
Jerry Dennany
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:OTZriQGJEHA.3704@.TK2MSFTNGP11.phx.gbl...
> Jerry,
> If you search MS site for error 3624, which is mentioned in the stack
dump,
> you will find plenty of articles
>
(http://search.microsoft.com/search/results.aspx?View=en-us&p=1&s=0&c=3&st=b
> &qu=3624&na=32). There are many possible reasons for this error. Just by
> reading the article titles I guess you will be able to narrow the search
to
> your problem.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
> "Jerry Dennany" <jerry@.dennany.org> wrote in message
> news:uMM$BVDJEHA.556@.TK2MSFTNGP10.phx.gbl...
> >
> >
> > Ok, I keep getting SQL Server assertions in the event log, with the
> > following stack dump message in the SQL Server logs. Any ideas?
> >
> > DBCC CHECKDB reveals no problems.
> >
> >
> >
>
* ----
> > --
> > 2004-04-02 04:03:13.39 spid234 Stack Signature for the dump is
> 0x2EF0EDAD
> > 2004-04-02 04:03:13.39 spid234 SQL Server Assertion: File: <insert.c>,
> > line=573
> > Failed Assertion = 'sdesP->m_pIndex->indindid == CLUSTIND'.
> > 2004-04-02 04:03:13.39 spid234 Error: 3624, Severity: 20, State: 1.
> > *Dump thread - spid = 84, PSS = 0x3e049238, EC = 0x3e049560
> > *Stack Dump being sent to I:\Microsoft SQL
> Server\MSSQL\log\SQLDump0033.txt
> > *
> >
>
****************************************************************************
> > ***
> >
> >
> > Thanks in advance,
> >
> > Jerry Dennany
> >
> >
>|||> I suppose that I should have mentioned that I've already performed the
> typical google and support.microsoft.com searches, without finding
anything
> applicable. Any other ideas?
Sorry, not directly. Maybe you can track down what happens before this
error, which command makes the problem? It would be nice if the problem
would be reproducable.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com|||This is a multi-part message in MIME format.
--=_NextPart_000_01B4_01C42527.F1365AC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
The following is the SqlException our code got when that happens. What =Jerry and I don't understand is that the error message "Duplicate key =was ignored" should be associated with SQL error 3604, which is only on =severity level 16 that will not throw the exception, (while error 3624 =is on level 20).
The database table has a composit unique index (Odometer, QueueID) with ="Ignore duplicate key", and a composit cluster index (QueuedTime, =Odometer). The Odometer column (int) is involved in both indexes.
Also, the server has 4 physical CPUs with hypertheading to 8 virtual =processors.
Error: 3624
General message: Location: insert.c:573
Expression: sdesP->m_pIndex->indindid =3D=3D CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored. Detailed message: =ELKUpdateStatusFromAnyStatus:System.Data.SqlClient.SqlException: Location: insert.c:573
Expression: sdesP->m_pIndex->indindid =3D=3D CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior =cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at =?RunCommand@.@.$$FYAXHPADPAV?$list@.PAU_PARAM@.@.V?$allocator@.PAU_PARAM@.@.@.std@.=@.@.std@.@.W4COMMANDTYPE@.@.@.Z(Int32
Yang Cao
MCSD, MCDBA
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote =in message news:ecsLMESJEHA.3068@.TK2MSFTNGP10.phx.gbl...
> > I suppose that I should have mentioned that I've already performed =the
> > typical google and support.microsoft.com searches, without finding
> anything
> > applicable. Any other ideas?
> > Sorry, not directly. Maybe you can track down what happens before this
> error, which command makes the problem? It would be nice if the =problem
> would be reproducable.
> > -- > Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
> >
--=_NextPart_000_01B4_01C42527.F1365AC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

The following is the SqlException our =code got when that happens. What Jerry and I don't understand is that the error =message "Duplicate key was ignored" should be associated with SQL error 3604, =which is only on severity level 16 that will not throw the exception, (while =error 3624 is on level 20). The database table has a composit unique index (Odometer, QueueID) with "Ignore duplicate key", and a composit cluster =index (QueuedTime, Odometer). The Odometer column (int) is involved in =both indexes.Also, the server has 4 physical CPUs with hypertheading =to 8 virtual processors. Error: 3624General message: Location: insert.c:573Expression: sdesP->m_pIndex->indindid =3D=3D =CLUSTINDSPID: 168Process ID: 2920Duplicate =key was ignored. Detailed message: ELKUpdateStatusFromAnyStatus:System.Data.SqlClient.SqlException: Location: insert.c:573Expression: sdesP->m_pIndex->indindid =3D=3D CLUSTINDSPID: =168Process ID: 2920Duplicate key was ignored. at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior =cmdBehavior, RunBehavior runBehavior, Boolean returnStream) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at ?RunCommand@.@.$$FYAXHPADPAV?$list@.PAU_PARAM@.@.V?$allocator@.PAU_PARAM@.@.@.std@.=@.@.std@.@.W4COMMANDTYPE@.@.@.Z(Int32
Yang CaoMCSD, =MCDBA"Dejan Sarka" wrote in =message news:ecsLMESJEHA.3068@.TK2MSFTNGP10.phx.gbl...> > I suppose =that I should have mentioned that I've already performed the> > =typical google and support.microsoft.com searches, without finding> anything> > applicable. Any other ideas?> => Sorry, not directly. Maybe you can track down what happens before this> =error, which command makes the problem? It would be nice if the problem> =would be reproducable.> > -- > Dejan Sarka, SQL Server MVP> Associate Mentor> Solid Quality Learning> More =than just Training> www.SolidQualityLearning.com> >

--=_NextPart_000_01B4_01C42527.F1365AC0--|||This is a multi-part message in MIME format.
--=_NextPart_000_003E_01C425F6.395B16F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Can you send me the code directly to my e-mail (just take out the ="_please_reply..." part out of the address and I will try to reproduce =the error? BTW, which versions of SQL Server and .NET Framework are you =using?
-- Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Yang Cao" <yang@.yangcao88.com> wrote in message =news:uu3i%23lUJEHA.3436@.tk2msftngp13.phx.gbl...
The following is the SqlException our code got when that happens. =What Jerry and I don't understand is that the error message "Duplicate =key was ignored" should be associated with SQL error 3604, which is only =on severity level 16 that will not throw the exception, (while error =3624 is on level 20).
The database table has a composit unique index (Odometer, QueueID) =with "Ignore duplicate key", and a composit cluster index (QueuedTime, =Odometer). The Odometer column (int) is involved in both indexes.
Also, the server has 4 physical CPUs with hypertheading to 8 virtual =processors.
Error: 3624
General message: Location: insert.c:573
Expression: sdesP->m_pIndex->indindid =3D=3D CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored. Detailed message: =ELKUpdateStatusFromAnyStatus:System.Data.SqlClient.SqlException: Location: insert.c:573
Expression: sdesP->m_pIndex->indindid =3D=3D CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior =cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at =?RunCommand@.@.$$FYAXHPADPAV?$list@.PAU_PARAM@.@.V?$allocator@.PAU_PARAM@.@.@.std@.=@.@.std@.@.W4COMMANDTYPE@.@.@.Z(Int32
Yang Cao
MCSD, MCDBA
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> =wrote in message news:ecsLMESJEHA.3068@.TK2MSFTNGP10.phx.gbl...
> > I suppose that I should have mentioned that I've already performed =the
> > typical google and support.microsoft.com searches, without finding
> anything
> > applicable. Any other ideas?
> > Sorry, not directly. Maybe you can track down what happens before =this
> error, which command makes the problem? It would be nice if the =problem
> would be reproducable.
> > -- > Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
> >
--=_NextPart_000_003E_01C425F6.395B16F0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

Can you send me the code directly to my =e-mail (just take out the "_please_reply..." part out of the address and I will =try to reproduce the error? BTW, which versions of SQL Server and .NET =Framework are you using?
-- Dejan Sarka, SQL Server =MVPAssociate MentorSolid Quality LearningMore than just Traininghttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com= "Yang Cao" wrote in =message news:uu3i%23lUJEHA.=3436@.tk2msftngp13.phx.gbl...
The following is the SqlException our =code got when that happens. What Jerry and I don't understand is that the =error message "Duplicate key was ignored" should be associated with SQL =error 3604, which is only on severity level 16 that will not throw the exception, =(while error 3624 is on level 20). The database table has a composit =unique index (Odometer, QueueID) with "Ignore duplicate key", and a composit =cluster index (QueuedTime, Odometer). The Odometer column (int) is =involved in both indexes.Also, the server has 4 physical CPUs with =hypertheading to 8 virtual processors. Error: 3624General message: Location: insert.c:573Expression: sdesP->m_pIndex->indindid ==3D=3D CLUSTINDSPID: 168Process ID: =2920Duplicate key was ignored. Detailed message: ELKUpdateStatusFromAnyStatus:System.Data.SqlClient.SqlException: = Location: insert.c:573Expression: sdesP->m_pIndex->indindid =3D=3D CLUSTINDSPID: 168Process ID: 2920Duplicate key was =ignored. at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior =cmdBehavior, RunBehavior runBehavior, Boolean returnStream) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at =?RunCommand@.@.$$FYAXHPADPAV?$list@.PAU_PARAM@.@.V?$allocator@.PAU_PARAM@.@.@.std@.=@.@.std@.@.W4COMMANDTYPE@.@.@.Z(Int32
Yang CaoMCSD, =MCDBA"Dejan Sarka" wrote in =message news:ecsLMESJEHA.3068@.TK2MSFTNGP10.phx.gbl...> > I suppose =that I should have mentioned that I've already performed the> > =typical google and support.microsoft.com searches, without finding> anything> > applicable. Any other ideas?> => Sorry, not directly. Maybe you can track down what happens before =this> error, which command makes the problem? It would be nice if the problem> would be reproducable.> > -- > =Dejan Sarka, SQL Server MVP> Associate Mentor> Solid Quality Learning> More than just Training> www.SolidQualityLearning.com> >

--=_NextPart_000_003E_01C425F6.395B16F0--sql

Wednesday, March 21, 2012

Error: 18456, Severity: 14, State: 16

DBCC TRACEON 4808, server process ID (SPID) 58. This is an
informational message only; no user action is
required.
2007-02-26 16:01:43.270 spid58 DBCC TRACEON 4808, server process
ID (SPID) 58. This is an informational message only; no user action is
required.
2007-02-26 16:02:12.590 spid62 Starting up database
'MYDB'.
2007-02-26 16:02:34.840 spid62 Starting up database
'MYDB'.
2007-02-26 16:02:47.410 Logon Error: 18456, Severity: 14,
State:
16.
2007-02-26 16:02:47.410 Logon Login failed for user 'NT
AUTHORITY\SYSTEM'. [CLIENT: <local
machine>]
2007-02-26 16:02:48.580 Logon Error: 18456, Severity: 14,
State:
16.
2007-02-26 16:02:48.580 Logon Login failed for user 'NT
AUTHORITY\SYSTEM'. [CLIENT: <local
machine>]
2007-02-26 16:02:50.410 Logon Error: 18456, Severity: 14,
State:
16.
2007-02-26 16:02:50.410 Logon Login failed for user 'NT
AUTHORITY\SYSTEM'. [CLIENT: <local
machine>]
2007-02-26 16:02:52.930 spid55 Starting up database
'sampledb'.
2007-02-26 16:02:59.160 Logon Error: 18456, Severity: 14,
State: 16.
The Connection is maded from .net application using trusted connectionIt looks like you're running your .NET application as LocalSystem. You
need to run it as a user who has an account defined in the database with
the appropriate credentials. If you're running an ASP.NET app on
Windows 2003, you'll generally be able to find the configuration for
your identity under "Application Pools" in the IIS configuration.
AMBROSE wrote:
> DBCC TRACEON 4808, server process ID (SPID) 58. This is an
> informational message only; no user action is
> required.
> 2007-02-26 16:01:43.270 spid58 DBCC TRACEON 4808, server process
> ID (SPID) 58. This is an informational message only; no user action is
> required.
> 2007-02-26 16:02:12.590 spid62 Starting up database
> 'MYDB'.
> 2007-02-26 16:02:34.840 spid62 Starting up database
> 'MYDB'.
> 2007-02-26 16:02:47.410 Logon Error: 18456, Severity: 14,
> State:
> 16.
> 2007-02-26 16:02:47.410 Logon Login failed for user 'NT
> AUTHORITY\SYSTEM'. [CLIENT: <local
> machine>]
> 2007-02-26 16:02:48.580 Logon Error: 18456, Severity: 14,
> State:
> 16.
> 2007-02-26 16:02:48.580 Logon Login failed for user 'NT
> AUTHORITY\SYSTEM'. [CLIENT: <local
> machine>]
> 2007-02-26 16:02:50.410 Logon Error: 18456, Severity: 14,
> State:
> 16.
> 2007-02-26 16:02:50.410 Logon Login failed for user 'NT
> AUTHORITY\SYSTEM'. [CLIENT: <local
> machine>]
> 2007-02-26 16:02:52.930 spid55 Starting up database
> 'sampledb'.
> 2007-02-26 16:02:59.160 Logon Error: 18456, Severity: 14,
> State: 16.
> The Connection is maded from .net application using trusted connection
>

Error: 18456, Severity: 14, State: 16

DBCC TRACEON 4808, server process ID (SPID) 58. This is an
informational message only; no user action is
required.
2007-02-26 16:01:43.270 spid58 DBCC TRACEON 4808, server process
ID (SPID) 58. This is an informational message only; no user action is
required.
2007-02-26 16:02:12.590 spid62 Starting up database
'MYDB'.
2007-02-26 16:02:34.840 spid62 Starting up database
'MYDB'.
2007-02-26 16:02:47.410 Logon Error: 18456, Severity: 14,
State:
16.
2007-02-26 16:02:47.410 Logon Login failed for user 'NT
AUTHORITY\SYSTEM'. [CLIENT: <local
machine>]
2007-02-26 16:02:48.580 Logon Error: 18456, Severity: 14,
State:
16.
2007-02-26 16:02:48.580 Logon Login failed for user 'NT
AUTHORITY\SYSTEM'. [CLIENT: <local
machine>]
2007-02-26 16:02:50.410 Logon Error: 18456, Severity: 14,
State:
16.
2007-02-26 16:02:50.410 Logon Login failed for user 'NT
AUTHORITY\SYSTEM'. [CLIENT: <local
machine>]
2007-02-26 16:02:52.930 spid55 Starting up database
'sampledb'.
2007-02-26 16:02:59.160 Logon Error: 18456, Severity: 14,
State: 16.
The Connection is maded from .net application using trusted connectionIt looks like you're running your .NET application as LocalSystem. You
need to run it as a user who has an account defined in the database with
the appropriate credentials. If you're running an ASP.NET app on
Windows 2003, you'll generally be able to find the configuration for
your identity under "Application Pools" in the IIS configuration.
AMBROSE wrote:
> DBCC TRACEON 4808, server process ID (SPID) 58. This is an
> informational message only; no user action is
> required.
> 2007-02-26 16:01:43.270 spid58 DBCC TRACEON 4808, server process
> ID (SPID) 58. This is an informational message only; no user action is
> required.
> 2007-02-26 16:02:12.590 spid62 Starting up database
> 'MYDB'.
> 2007-02-26 16:02:34.840 spid62 Starting up database
> 'MYDB'.
> 2007-02-26 16:02:47.410 Logon Error: 18456, Severity: 14,
> State:
> 16.
> 2007-02-26 16:02:47.410 Logon Login failed for user 'NT
> AUTHORITY\SYSTEM'. [CLIENT: <local
> machine>]
> 2007-02-26 16:02:48.580 Logon Error: 18456, Severity: 14,
> State:
> 16.
> 2007-02-26 16:02:48.580 Logon Login failed for user 'NT
> AUTHORITY\SYSTEM'. [CLIENT: <local
> machine>]
> 2007-02-26 16:02:50.410 Logon Error: 18456, Severity: 14,
> State:
> 16.
> 2007-02-26 16:02:50.410 Logon Login failed for user 'NT
> AUTHORITY\SYSTEM'. [CLIENT: <local
> machine>]
> 2007-02-26 16:02:52.930 spid55 Starting up database
> 'sampledb'.
> 2007-02-26 16:02:59.160 Logon Error: 18456, Severity: 14,
> State: 16.
> The Connection is maded from .net application using trusted connection
>

Sunday, February 19, 2012

Error while shrinking transaction log

Hi all,

while I shrinked transaction log using command "dbcc shrinkfile (logfile)" in query analyzer, the error message " cannot find logfile in sysfiles" was shown up.

The I list out content of sysfiles, and found that sysfiles doesn't contain logfile.

Can anybody tell me how to eliminate error in order to shrink transaction log?

Thanks in advances.

PaulYou need to enter the correct filename for your tempdb database. Default is templog. Right click on tempdb to find your correct filename.
Try:
USE tempdb
go
DBCC SHRINKFILE (TEMPLOG)|||Martsar,

Thanks for your input.

I checked and found that my syntax and log file name were correct, but preceding error message was still there. But I did successfully to shrink TEMPLOG.|||to check the filenames of db and log execute from your database:

use yourDB
go
sp_helpfile

The syntax to shrink db and log is:
DBCC SHRINKDATABASE (N'dbName/or logName', 0)

Also, try to shrink log in EM.