Database marked as suspect when bringing up a clustered server

We have a 2 node clustered server (active/passive failover) that when it
fails over (forced or otherwise) or if we just reboot the server, when it
comes up, some of the user databases come up marked as suspect. Which
databases get marked varies each time. If I execute an sp_resetstatus on the
database it tells me that nothing was changed because the flags are fine. I
then run a restore database with recovery it tells me that it completed
successfully and processed 0 pages in 0 sec.
I then go into the cluster administrator, take sql server offline and then
bring it back up and the databases will be ok. We're looking for some sort of
explanation of this behavior.
What does the SQL Server error logs say when the system is coming online and the databases are marked suspect?
I'd check the SQL Server cluster resource dependencies. When you say that after you've repaired everything and recycle SQL Server, how are you doing that? Are you just restarting services, taking cluster resources offline, taking the entire resource group offline, or using SQL EM to stop and restart the services?
Sincerely,
Anthony Thomas

"tim" <tim@.discussions.microsoft.com> wrote in message news:6B363DFC-293D-46F4-9F5E-CAAB0A669B33@.microsoft.com...
We have a 2 node clustered server (active/passive failover) that when it
fails over (forced or otherwise) or if we just reboot the server, when it
comes up, some of the user databases come up marked as suspect. Which
databases get marked varies each time. If I execute an sp_resetstatus on the
database it tells me that nothing was changed because the flags are fine. I
then run a restore database with recovery it tells me that it completed
successfully and processed 0 pages in 0 sec.
I then go into the cluster administrator, take sql server offline and then
bring it back up and the databases will be ok. We're looking for some sort of
explanation of this behavior.|||The SQL Server error log shows: Error 9004, Severity: 21, State 10
An error occurred when processing the log for database .....
As far as stopping and restarting SQL Server, I'm doing it from the Cluster
Administrator, go to the Active Resources folder and take SQL Server offline
and
then bring it back online. And then the database(s) will be available.
"AnthonyThomas" wrote:

> What does the SQL Server error logs say when the system is coming online and the databases are marked suspect?
> I'd check the SQL Server cluster resource dependencies. When you say that after you've repaired everything and recycle SQL Server, how are you doing that? Are you just restarting services, taking cluster resources offline, taking the entire resource g
roup offline, or using SQL EM to stop and restart the services?
> Sincerely,
>
> Anthony Thomas
>
> --
> "tim" <tim@.discussions.microsoft.com> wrote in message news:6B363DFC-293D-46F4-9F5E-CAAB0A669B33@.microsoft.com...
> We have a 2 node clustered server (active/passive failover) that when it
> fails over (forced or otherwise) or if we just reboot the server, when it
> comes up, some of the user databases come up marked as suspect. Which
> databases get marked varies each time. If I execute an sp_resetstatus on the
> database it tells me that nothing was changed because the flags are fine. I
> then run a restore database with recovery it tells me that it completed
> successfully and processed 0 pages in 0 sec.
> I then go into the cluster administrator, take sql server offline and then
> bring it back up and the databases will be ok. We're looking for some sort of
> explanation of this behavior

Database marked as suspect when bringing up a clustered server

We have a 2 node clustered server (active/passive failover) that when it
fails over (forced or otherwise) or if we just reboot the server, when it
comes up, some of the user databases come up marked as suspect. Which
databases get marked varies each time. If I execute an sp_resetstatus on the
database it tells me that nothing was changed because the flags are fine. I
then run a restore database with recovery it tells me that it completed
successfully and processed 0 pages in 0 sec.
I then go into the cluster administrator, take sql server offline and then
bring it back up and the databases will be ok. We're looking for some sort of
explanation of this behavior.The SQL Server error log shows: Error 9004, Severity: 21, State 10
An error occurred when processing the log for database .....
As far as stopping and restarting SQL Server, I'm doing it from the Cluster
Administrator, go to the Active Resources folder and take SQL Server offline
and
then bring it back online. And then the database(s) will be available.
"AnthonyThomas" wrote:
> What does the SQL Server error logs say when the system is coming online and the databases are marked suspect?
> I'd check the SQL Server cluster resource dependencies. When you say that after you've repaired everything and recycle SQL Server, how are you doing that? Are you just restarting services, taking cluster resources offline, taking the entire resource group offline, or using SQL EM to stop and restart the services?
> Sincerely,
>
> Anthony Thomas
>
> --
> "tim" <tim@.discussions.microsoft.com> wrote in message news:6B363DFC-293D-46F4-9F5E-CAAB0A669B33@.microsoft.com...
> We have a 2 node clustered server (active/passive failover) that when it
> fails over (forced or otherwise) or if we just reboot the server, when it
> comes up, some of the user databases come up marked as suspect. Which
> databases get marked varies each time. If I execute an sp_resetstatus on the
> database it tells me that nothing was changed because the flags are fine. I
> then run a restore database with recovery it tells me that it completed
> successfully and processed 0 pages in 0 sec.
> I then go into the cluster administrator, take sql server offline and then
> bring it back up and the databases will be ok. We're looking for some sort of
> explanation of this behavior

Database marked as suspect when bringing up a clustered server

We have a 2 node clustered server (active/passive failover) that when it
fails over (forced or otherwise) or if we just reboot the server, when it
comes up, some of the user databases come up marked as suspect. Which
databases get marked varies each time. If I execute an sp_resetstatus on the
database it tells me that nothing was changed because the flags are fine. I
then run a restore database with recovery it tells me that it completed
successfully and processed 0 pages in 0 sec.
I then go into the cluster administrator, take sql server offline and then
bring it back up and the databases will be ok. We're looking for some sort o
f
explanation of this behavior.What does the SQL Server error logs say when the system is coming online and
the databases are marked suspect?
I'd check the SQL Server cluster resource dependencies. When you say that a
fter you've repaired everything and recycle SQL Server, how are you doing th
at? Are you just restarting services, taking cluster resources offline, tak
ing the entire resource group offline, or using SQL EM to stop and restart t
he services?
Sincerely,
Anthony Thomas
--
"tim" <tim@.discussions.microsoft.com> wrote in message news:6B363DFC-293D-
46F4-9F5E-CAAB0A669B33@.microsoft.com...
We have a 2 node clustered server (active/passive failover) that when it
fails over (forced or otherwise) or if we just reboot the server, when it
comes up, some of the user databases come up marked as suspect. Which
databases get marked varies each time. If I execute an sp_resetstatus on t
he
database it tells me that nothing was changed because the flags are fine.
I
then run a restore database with recovery it tells me that it completed
successfully and processed 0 pages in 0 sec.
I then go into the cluster administrator, take sql server offline and then
bring it back up and the databases will be ok. We're looking for some sort
of
explanation of this behavior.|||The SQL Server error log shows: Error 9004, Severity: 21, State 10
An error occurred when processing the log for database .....
As far as stopping and restarting SQL Server, I'm doing it from the Cluster
Administrator, go to the Active Resources folder and take SQL Server offline
and
then bring it back online. And then the database(s) will be available.
"AnthonyThomas" wrote:

> What does the SQL Server error logs say when the system is coming online a
nd the databases are marked suspect?
> I'd check the SQL Server cluster resource dependencies. When you say that after y
ou've repaired everything and recycle SQL Server, how are you doing that? Are you j
ust restarting services, taking cluster resources offline, taking the entire resourc
e g
roup offline, or using SQL EM to stop and restart the services?
> Sincerely,
>
> Anthony Thomas
>
> --
> "tim" <tim@.discussions.microsoft.com> wrote in message news:6B363DFC-293
D-46F4-9F5E-CAAB0A669B33@.microsoft.com...
> We have a 2 node clustered server (active/passive failover) that when it
> fails over (forced or otherwise) or if we just reboot the server, when i
t
> comes up, some of the user databases come up marked as suspect. Which
> databases get marked varies each time. If I execute an sp_resetstatus on
the
> database it tells me that nothing was changed because the flags are fine
. I
> then run a restore database with recovery it tells me that it completed
> successfully and processed 0 pages in 0 sec.
> I then go into the cluster administrator, take sql server offline and th
en
> bring it back up and the databases will be ok. We're looking for some so
rt of
> explanation of this behavior

Database maintence plan

I have looked at the wizard for creating a database
maintenance plan and there are a lot of options. We have
30 databases on each of 2 clustered SQL2000 servers.
Originally I set up seperate backup jobs for each
database and transaction log and scheduled them to run
each night. This leaves to much room for error. I may
forget a backup or transaction log. I assume that the
maint. plan will backup databases and transaction logs
and truncate the transaction logs on all databases. There
is less chance of me forgetting to add a backup. What
options are recommended when running the database maint.
plan wizard?
Thank You
TomWe have quite a few databases on one of our servers. I threw together a
quick and simple way to back them up using sp_MSforeachdb:
If you want to see how it works on your server, replace
EXEC (@.sql)
with
PRINT @.sql
and run it on your server
You will probably have to change the backup location to fit your
environment.
EXEC sp_MSforeachdb
'IF N''?'' NOT IN(''model'' ,''tempdb'', ''distribution'', ''Northwind'',
''pubs'')
BEGIN
DECLARE @.sql varchar(1000);
set @.sql = ''BACKUP DATABASE '' + (''?'') + '' TO DISK =''''D:\MSSQL2000\MSSQL\BACKUP\'' + (''?'') + ''.bak'''' WITH INIT''
EXEC (@.sql)
END'
Keith
"Tom" <anonymous@.discussions.microsoft.com> wrote in message
news:137b01c47bc0$0d162970$a301280a@.phx.gbl...
> I have looked at the wizard for creating a database
> maintenance plan and there are a lot of options. We have
> 30 databases on each of 2 clustered SQL2000 servers.
> Originally I set up seperate backup jobs for each
> database and transaction log and scheduled them to run
> each night. This leaves to much room for error. I may
> forget a backup or transaction log. I assume that the
> maint. plan will backup databases and transaction logs
> and truncate the transaction logs on all databases. There
> is less chance of me forgetting to add a backup. What
> options are recommended when running the database maint.
> plan wizard?
> Thank You
> Tom

Database maintence plan

I have looked at the wizard for creating a database
maintenance plan and there are a lot of options. We have
30 databases on each of 2 clustered SQL2000 servers.
Originally I set up seperate backup jobs for each
database and transaction log and scheduled them to run
each night. This leaves to much room for error. I may
forget a backup or transaction log. I assume that the
maint. plan will backup databases and transaction logs
and truncate the transaction logs on all databases. There
is less chance of me forgetting to add a backup. What
options are recommended when running the database maint.
plan wizard?
Thank You
Tom
We have quite a few databases on one of our servers. I threw together a
quick and simple way to back them up using sp_MSforeachdb:
If you want to see how it works on your server, replace
EXEC (@.sql)
with
PRINT @.sql
and run it on your server
You will probably have to change the backup location to fit your
environment.
EXEC sp_MSforeachdb
'IF N''?'' NOT IN(''model'' ,''tempdb'', ''distribution'', ''Northwind'',
''pubs'')
BEGIN
DECLARE @.sql varchar(1000);
set @.sql = ''BACKUP DATABASE '' + (''?'') + '' TO DISK =
''''D:\MSSQL2000\MSSQL\BACKUP\'' + (''?'') + ''.bak'''' WITH INIT''
EXEC (@.sql)
END'
Keith
"Tom" <anonymous@.discussions.microsoft.com> wrote in message
news:137b01c47bc0$0d162970$a301280a@.phx.gbl...
> I have looked at the wizard for creating a database
> maintenance plan and there are a lot of options. We have
> 30 databases on each of 2 clustered SQL2000 servers.
> Originally I set up seperate backup jobs for each
> database and transaction log and scheduled them to run
> each night. This leaves to much room for error. I may
> forget a backup or transaction log. I assume that the
> maint. plan will backup databases and transaction logs
> and truncate the transaction logs on all databases. There
> is less chance of me forgetting to add a backup. What
> options are recommended when running the database maint.
> plan wizard?
> Thank You
> Tom

Database maintence plan

I have looked at the wizard for creating a database
maintenance plan and there are a lot of options. We have
30 databases on each of 2 clustered SQL2000 servers.
Originally I set up seperate backup jobs for each
database and transaction log and scheduled them to run
each night. This leaves to much room for error. I may
forget a backup or transaction log. I assume that the
maint. plan will backup databases and transaction logs
and truncate the transaction logs on all databases. There
is less chance of me forgetting to add a backup. What
options are recommended when running the database maint.
plan wizard?
Thank You
TomWe have quite a few databases on one of our servers. I threw together a
quick and simple way to back them up using sp_MSforeachdb:
If you want to see how it works on your server, replace
EXEC (@.sql)
with
PRINT @.sql
and run it on your server
You will probably have to change the backup location to fit your
environment.
EXEC sp_MSforeachdb
'IF N''?'' NOT IN(''model'' ,''tempdb'', ''distribution'', ''Northwind'',
''pubs'')
BEGIN
DECLARE @.sql varchar(1000);
set @.sql = ''BACKUP DATABASE '' + (''?'') + '' TO DISK =
''''D:\MSSQL2000\MSSQL\BACKUP'' + (''?'') + ''.bak'''' WITH INIT''
EXEC (@.sql)
END'
Keith
"Tom" <anonymous@.discussions.microsoft.com> wrote in message
news:137b01c47bc0$0d162970$a301280a@.phx.gbl...
> I have looked at the wizard for creating a database
> maintenance plan and there are a lot of options. We have
> 30 databases on each of 2 clustered SQL2000 servers.
> Originally I set up seperate backup jobs for each
> database and transaction log and scheduled them to run
> each night. This leaves to much room for error. I may
> forget a backup or transaction log. I assume that the
> maint. plan will backup databases and transaction logs
> and truncate the transaction logs on all databases. There
> is less chance of me forgetting to add a backup. What
> options are recommended when running the database maint.
> plan wizard?
> Thank You
> Tom