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
>
>
Showing posts with label became. Show all posts
Showing posts with label became. Show all posts
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.
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
>
>
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
>
>
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
>
>
Wednesday, February 15, 2012
Error 208: Invaild object name msdb.dbo.MSdistpublishers
Recently my msdb database became corrupt so I had to reinstall SQL Server 7.0. In doing so new system databases were created. I was able to restore all databases and system databases from backups except for the msdb database (unfortunately my backup overwrote the good database before I realized there was a problem). Because of this I have lost publication and subscriber info from my distribution tables that resided in the old msdb database.
What I would like to do is delete all references to previous publications and subscribers and create them all over again. But it does not allow me to create new or delete old publishers or subscribers. I get this and other errors...
Error 208: Invaild object name 'msdb.dbo.MSdistpublishers'
There is in fact no MSdistpublishers table in msdb because it is a new db. Can anyone help me reverse out of this?
Thanks in advance.
SteveIn future make sure to have regular backups for SYSTEM databases too.
I suggest to delete the replication and recreate it freshly which will re-enable the task. Make sure to check all jobs and tasks are scheduled properly after the MSDB restore.
Refer to SQL error log for any information.
What I would like to do is delete all references to previous publications and subscribers and create them all over again. But it does not allow me to create new or delete old publishers or subscribers. I get this and other errors...
Error 208: Invaild object name 'msdb.dbo.MSdistpublishers'
There is in fact no MSdistpublishers table in msdb because it is a new db. Can anyone help me reverse out of this?
Thanks in advance.
SteveIn future make sure to have regular backups for SYSTEM databases too.
I suggest to delete the replication and recreate it freshly which will re-enable the task. Make sure to check all jobs and tasks are scheduled properly after the MSDB restore.
Refer to SQL error log for any information.
Subscribe to:
Posts (Atom)