We upgraded to sql 2000 last night and now the maintenance
plans do not work. I'm using simple model, no tlog backup.
The error I'm working with is this:
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The
step failed.
The log looks like this:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server '1s' as 'NT AUTHORITY\SYSTEM' (trusted)
Starting maintenance plan 'DB Maintenance Plan1' on
7/31/2003 2:00:02 AM
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070:
[Microsoft][ODBC SQL Server Driver][SQL Server]Database
state cannot be changed while other users are using the
database 'r'
[Microsoft][ODBC SQL Server Driver][SQL Server]ALTER
DATABASE statement failed.
[Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption
command failed.
[1] Database rbcs: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919:
[Microsoft][ODBC SQL Server Driver][SQL Server]Repair
statement not processed. Database needs to be in single
user mode.
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]Repair
statement not processed. Database needs to be in single
user mode.
** Execution Time: 0 hrs, 0 mins, 1 secs **
[2] Database t: Check Data and Index Linkage...
** Execution Time: 0 hrs, 0 mins, 2 secs **
[3] Database r: Database Backup...
The backup was not performed since data verification
errors were found.
[4] Database t: Database Backup...
Destination: [D:\mssql7\BACKUP\t\t_db_200307310200.BAK]
** Execution Time: 0 hrs, 0 mins, 14 secs **
[5] Database t: Verifying Backup...
** Execution Time: 0 hrs, 0 mins, 5 secs **
Deleting old text reports... 1 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan1' on
7/31/2003 2:00:23 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)D
You are geting this error because the maintenance plan is
trying to put the database into single user mode. It fails
because there is a user (or at least an open transaction)
in the database. It is attempting to do this so it can
perform a dbcc checkdb with repair.
If this worked before, perhaps something in the upgrade
has lead to open transactions? Or have you changed the
time the job runs?
If you change the dbcc part of the maint plan, not to do
the repair it would not try to put the database into
single user mode. Check the output from your dbcc checkdb
and if you find you do need to run with repair, schedule a
job to run at a time when you can switch to single user
mode.
Hope this helps
John|||The plan was setup under sql 7 so I guess there wasnt a
problem in that version. I will remove the repair option,
but I suppose I'll have to run dbcc later.
Thanks
>--Original Message--
>D
>You are geting this error because the maintenance plan is
>trying to put the database into single user mode. It
fails
>because there is a user (or at least an open transaction)
>in the database. It is attempting to do this so it can
>perform a dbcc checkdb with repair.
>If this worked before, perhaps something in the upgrade
>has lead to open transactions? Or have you changed the
>time the job runs?
>If you change the dbcc part of the maint plan, not to do
>the repair it would not try to put the database into
>single user mode. Check the output from your dbcc checkdb
>and if you find you do need to run with repair, schedule
a
>job to run at a time when you can switch to single user
>mode.
>Hope this helps
>John
>.
>
Showing posts with label model. Show all posts
Showing posts with label model. Show all posts
Friday, March 30, 2012
Monday, March 12, 2012
Main requirements per A-A model
Dear all,
I would like to build an Active-Active model with two nodes (Win200 AdServer)
question is easy: which are the most important parameters as well as little
things that then are so important when everything is running in production?
Same memory for both?
Same processor type for both?
Thanks a lot for your response.
Regards,
To make sure that the cluster that you will build will be "Highly Available", the most important thing is to make sure that it is "HCL or WSC-compliant cluster "
Additional Information
===================
The Microsoft support policy for server clusters, the Hardware Compatibility List, and the Windows Server Catalog
http://support.microsoft.com/default...b;en-us;309395
The Microsoft support policy for a SQL Server failover cluster
http://support.microsoft.com/default...b;en-us;327518
Network-Attached Storage and Server Cluster Support
http://support.microsoft.com/default...b;en-us;812504
Once you have a HCL or WSC-Compliant cluster, then the following Microsoft whitepaper will be helpful
Step-by-Step Guide to Installing Windows 2000 Cluster Service
http://www.microsoft.com/windows2000...ustersteps.asp
Step-by-Step Guide to Installing SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/pro.../failclus.mspx
--> This whitepaper helps with your design of single instance cluster (replaces A/P terminology) or multiple instance cluster (replaces A/A terminology) and helps you determine how much processor, memory, etc
will be required.
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Here is a post that I had recently written for a similar qs.
With instances in SQL Server 2000, come two new concepts for failover clustering:
* Single instance cluster: replaces an active/passive cluster. A single instance cluster means there is one SQL Server 2000 virtual server installed.
* Multiple instance cluster: replaces an active/active cluster. A multiple instance cluster is one in which there is more than one SQL Server 2000 virtual server installed. Because of the way the implementation of
clustering is different with SQL Server 2000, using the active/active terminology does not really apply.
Here is some info that you may find helpful
Single-Instance Cluster
A single-instance cluster has only one active instance of SQL Server owned by a single server node, and all other nodes of the cluster are in a wait state. Another node is enabled in the event of a failure on the
active
node, or during a manual failover for maintenance.
Multiple-Instance Cluster
A multiple-instance cluster has up to four server nodes and supports up to 16 instances (1 default, 15 named or 16 named). Each SQL Server 2000 virtual server requires its own disk resources that cannot be used
by
other instances. These disk resources are the logical drive names (for example, drive F:\) used by SQL Server on which to store data and log files. Separate physical disk sets are needed to make up the logical
drive, unless your disk subsystem supports multiple logical drives on one physical drive set. SQL Server in a clustered environment also behaves differently from a stand-alone named instance in relation to IP
ports.
During the installation process, a dynamic port that may be something other than 1433 is configured, and that port number is reserved for the instance.
For additional information, refer to
Microsoft Whitepaper - SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/pro.../failclus.mspx
Specifically read the following sections in the whitepaper
* Memory Configuration
-This section presents considerations for memory usage in a SQL Server 2000 failover cluster.
* Processor Capacity
* Using More Than Two Nodes
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Thanks a lot Uttam,
"Uttam Parui[MS]" wrote:
> Here is a post that I had recently written for a similar qs.
>
> With instances in SQL Server 2000, come two new concepts for failover clustering:
> * Single instance cluster: replaces an active/passive cluster. A single instance cluster means there is one SQL Server 2000 virtual server installed.
> * Multiple instance cluster: replaces an active/active cluster. A multiple instance cluster is one in which there is more than one SQL Server 2000 virtual server installed. Because of the way the implementation of
> clustering is different with SQL Server 2000, using the active/active terminology does not really apply.
> Here is some info that you may find helpful
> Single-Instance Cluster
> A single-instance cluster has only one active instance of SQL Server owned by a single server node, and all other nodes of the cluster are in a wait state. Another node is enabled in the event of a failure on the
> active
> node, or during a manual failover for maintenance.
> Multiple-Instance Cluster
> A multiple-instance cluster has up to four server nodes and supports up to 16 instances (1 default, 15 named or 16 named). Each SQL Server 2000 virtual server requires its own disk resources that cannot be used
> by
> other instances. These disk resources are the logical drive names (for example, drive F:\) used by SQL Server on which to store data and log files. Separate physical disk sets are needed to make up the logical
> drive, unless your disk subsystem supports multiple logical drives on one physical drive set. SQL Server in a clustered environment also behaves differently from a stand-alone named instance in relation to IP
> ports.
> During the installation process, a dynamic port that may be something other than 1433 is configured, and that port number is reserved for the instance.
> For additional information, refer to
> Microsoft Whitepaper - SQL Server 2000 Failover Clustering
> http://www.microsoft.com/technet/pro.../failclus.mspx
> Specifically read the following sections in the whitepaper
> * Memory Configuration
> -This section presents considerations for memory usage in a SQL Server 2000 failover cluster.
> * Processor Capacity
> * Using More Than Two Nodes
>
> HTH,
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>
I would like to build an Active-Active model with two nodes (Win200 AdServer)
question is easy: which are the most important parameters as well as little
things that then are so important when everything is running in production?
Same memory for both?
Same processor type for both?
Thanks a lot for your response.
Regards,
To make sure that the cluster that you will build will be "Highly Available", the most important thing is to make sure that it is "HCL or WSC-compliant cluster "
Additional Information
===================
The Microsoft support policy for server clusters, the Hardware Compatibility List, and the Windows Server Catalog
http://support.microsoft.com/default...b;en-us;309395
The Microsoft support policy for a SQL Server failover cluster
http://support.microsoft.com/default...b;en-us;327518
Network-Attached Storage and Server Cluster Support
http://support.microsoft.com/default...b;en-us;812504
Once you have a HCL or WSC-Compliant cluster, then the following Microsoft whitepaper will be helpful
Step-by-Step Guide to Installing Windows 2000 Cluster Service
http://www.microsoft.com/windows2000...ustersteps.asp
Step-by-Step Guide to Installing SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/pro.../failclus.mspx
--> This whitepaper helps with your design of single instance cluster (replaces A/P terminology) or multiple instance cluster (replaces A/A terminology) and helps you determine how much processor, memory, etc
will be required.
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Here is a post that I had recently written for a similar qs.
With instances in SQL Server 2000, come two new concepts for failover clustering:
* Single instance cluster: replaces an active/passive cluster. A single instance cluster means there is one SQL Server 2000 virtual server installed.
* Multiple instance cluster: replaces an active/active cluster. A multiple instance cluster is one in which there is more than one SQL Server 2000 virtual server installed. Because of the way the implementation of
clustering is different with SQL Server 2000, using the active/active terminology does not really apply.
Here is some info that you may find helpful
Single-Instance Cluster
A single-instance cluster has only one active instance of SQL Server owned by a single server node, and all other nodes of the cluster are in a wait state. Another node is enabled in the event of a failure on the
active
node, or during a manual failover for maintenance.
Multiple-Instance Cluster
A multiple-instance cluster has up to four server nodes and supports up to 16 instances (1 default, 15 named or 16 named). Each SQL Server 2000 virtual server requires its own disk resources that cannot be used
by
other instances. These disk resources are the logical drive names (for example, drive F:\) used by SQL Server on which to store data and log files. Separate physical disk sets are needed to make up the logical
drive, unless your disk subsystem supports multiple logical drives on one physical drive set. SQL Server in a clustered environment also behaves differently from a stand-alone named instance in relation to IP
ports.
During the installation process, a dynamic port that may be something other than 1433 is configured, and that port number is reserved for the instance.
For additional information, refer to
Microsoft Whitepaper - SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/pro.../failclus.mspx
Specifically read the following sections in the whitepaper
* Memory Configuration
-This section presents considerations for memory usage in a SQL Server 2000 failover cluster.
* Processor Capacity
* Using More Than Two Nodes
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Thanks a lot Uttam,
"Uttam Parui[MS]" wrote:
> Here is a post that I had recently written for a similar qs.
>
> With instances in SQL Server 2000, come two new concepts for failover clustering:
> * Single instance cluster: replaces an active/passive cluster. A single instance cluster means there is one SQL Server 2000 virtual server installed.
> * Multiple instance cluster: replaces an active/active cluster. A multiple instance cluster is one in which there is more than one SQL Server 2000 virtual server installed. Because of the way the implementation of
> clustering is different with SQL Server 2000, using the active/active terminology does not really apply.
> Here is some info that you may find helpful
> Single-Instance Cluster
> A single-instance cluster has only one active instance of SQL Server owned by a single server node, and all other nodes of the cluster are in a wait state. Another node is enabled in the event of a failure on the
> active
> node, or during a manual failover for maintenance.
> Multiple-Instance Cluster
> A multiple-instance cluster has up to four server nodes and supports up to 16 instances (1 default, 15 named or 16 named). Each SQL Server 2000 virtual server requires its own disk resources that cannot be used
> by
> other instances. These disk resources are the logical drive names (for example, drive F:\) used by SQL Server on which to store data and log files. Separate physical disk sets are needed to make up the logical
> drive, unless your disk subsystem supports multiple logical drives on one physical drive set. SQL Server in a clustered environment also behaves differently from a stand-alone named instance in relation to IP
> ports.
> During the installation process, a dynamic port that may be something other than 1433 is configured, and that port number is reserved for the instance.
> For additional information, refer to
> Microsoft Whitepaper - SQL Server 2000 Failover Clustering
> http://www.microsoft.com/technet/pro.../failclus.mspx
> Specifically read the following sections in the whitepaper
> * Memory Configuration
> -This section presents considerations for memory usage in a SQL Server 2000 failover cluster.
> * Processor Capacity
> * Using More Than Two Nodes
>
> HTH,
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>
Subscribe to:
Posts (Atom)