Showing posts with label suspect. Show all posts
Showing posts with label suspect. Show all posts

Tuesday, March 27, 2012

error 9004, severity 21, state 10

saw one of my database went suspect, I tried to load a restore from the backup, but this was going on for ever. I cancelled out, deleted the suspect database. Created a new database and tried to restore from the old backup, but this was going on for ever. It will not restore. I cannot stop and start mssql service on this server as it is production. what else can I do.Q1 On trying to restore from the old backup, this goes on forever. I cannot stop and start mssql service on this server as it is production. What else can I do?

A1 If the issue amounts to the Db remaining in 'Loading' status "forever"; it may simply be that the DB has not been recovered following the restore.

To test this possibility, one would execute a statement similar to the following:

Restore DataBase [DBName] With Recovery

Question I
Can the DB be restored to a development server successfully using the "old backup"?sql

Wednesday, March 7, 2012

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
>
>

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.
JohnnyHi 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/d...r />
_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/in..._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 increase
d
> like balloon 49.9GB, I don't know exactly what was the size before. The md
f
> 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
>
>

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.
JohnnyHi 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/default.asp?url=/library/en-us/architec/8_ar_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/info_corrupt_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
>
>