March 13, 2003 at 7:54 am
Were in the process of installing SP3 and discovered few databaseses that are warm-standby (Read-Only). How can we change that to write so we can run SP3 install?
Thanks
March 13, 2003 at 8:54 am
Quoted from sp3readme.
"If SP3 Setup detects user databases or filegroups that are not writable, it:
Applies the SP3 replication updates to all writable user databases.
Writes a list of the non-writable databases to the Setup log, which is located at Winnt\Sqlsp.log.
Displays the following warning message:
Setup has detected one or more databases and filegroups which are not writable.
You can ignore this warning unless some of the databases listed in the Setup log are members of a replication topology. If any of the non-writable databases listed in the Setup log are members of a replication topology, you must make those databases writable and reapply SP3 Setup to that instance of SQL Server 2000.
Because non-writable databases no longer cause Setup to fail, you do not have to remove log shipping before upgrading to SP3.
3.12 Applying SP3 to Read-Only Databases or Filegroups
The following information applies only to SQL Server 2000 components that are part of a replication topology.
When non-writable databases or filegroups exist, Setup displays the following message:
Setup has detected one or more databases and filegroups which are not writable.
In general, you can ignore this warning and setup will continue. However, if any of the non-writable databases listed in the Setup log are members of a replication topology, you must make those databases writable and reapply SP3 Setup to that instance of SQL Server 2000.
Note This message does not affect unattended installations. For more information about unattended installations, see Section 4.1 Unattended Installations.
Note During installation, Setup makes no distinction between non-writable databases and databases that are offline or in a suspect state. If a database or filegroup is in any of these conditions during setup, you must reapply the service pack. For more information about bringing a database online, see the topic "Attaching and Detaching a Database" in SQL Server Books Online. For more information about diagnosing suspect databases, see the topic "Server and Database Troubleshooting" in SQL Server Books Online.
To apply SP3 to a read-only database
Make the read-only database writable using the ALTER DATABASE statement, as follows:
ALTER DATABASE database SET READ_WRITE
Repeat Step 1 for all read-only databases.
Apply (or reapply) the service pack.
If required, make the database read-only again using ALTER DATABASE, as follows:
ALTER DATABASE database SET READ_ONLY
To apply SP3 to a read-only filegroup
Make the read-only filegroup writable using ALTER DATABASE, as follows:
ALTER DATABASE Database
MODIFY FILEGROUP filegroup_name READWRITE
Repeat Step 1 for all read-only filegroups.
Apply (or reapply) the service pack.
Make the filegroup read-only again using ALTER DATABASE, as follows:
ALTER DATABASE Database
MODIFY FILEGROUP filegroup_name READONLY"
March 13, 2003 at 9:00 am
I tried that and received an error
Server: Msg 5063, Level 16, State 1, Line 1
Database ' ' is in warm standby. A warm-standby database is read-only.
quote:
Quoted from sp3readme."If SP3 Setup detects user databases or filegroups that are not writable, it:
Applies the SP3 replication updates to all writable user databases.
Writes a list of the non-writable databases to the Setup log, which is located at Winnt\Sqlsp.log.
Displays the following warning message:
Setup has detected one or more databases and filegroups which are not writable.
You can ignore this warning unless some of the databases listed in the Setup log are members of a replication topology. If any of the non-writable databases listed in the Setup log are members of a replication topology, you must make those databases writable and reapply SP3 Setup to that instance of SQL Server 2000.
Because non-writable databases no longer cause Setup to fail, you do not have to remove log shipping before upgrading to SP3.
3.12 Applying SP3 to Read-Only Databases or Filegroups
The following information applies only to SQL Server 2000 components that are part of a replication topology.
When non-writable databases or filegroups exist, Setup displays the following message:
Setup has detected one or more databases and filegroups which are not writable.
In general, you can ignore this warning and setup will continue. However, if any of the non-writable databases listed in the Setup log are members of a replication topology, you must make those databases writable and reapply SP3 Setup to that instance of SQL Server 2000.
Note This message does not affect unattended installations. For more information about unattended installations, see Section 4.1 Unattended Installations.
Note During installation, Setup makes no distinction between non-writable databases and databases that are offline or in a suspect state. If a database or filegroup is in any of these conditions during setup, you must reapply the service pack. For more information about bringing a database online, see the topic "Attaching and Detaching a Database" in SQL Server Books Online. For more information about diagnosing suspect databases, see the topic "Server and Database Troubleshooting" in SQL Server Books Online.
To apply SP3 to a read-only database
Make the read-only database writable using the ALTER DATABASE statement, as follows:
ALTER DATABASE database SET READ_WRITE
Repeat Step 1 for all read-only databases.
Apply (or reapply) the service pack.
If required, make the database read-only again using ALTER DATABASE, as follows:
ALTER DATABASE database SET READ_ONLY
To apply SP3 to a read-only filegroup
Make the read-only filegroup writable using ALTER DATABASE, as follows:
ALTER DATABASE Database
MODIFY FILEGROUP filegroup_name READWRITE
Repeat Step 1 for all read-only filegroups.
Apply (or reapply) the service pack.
Make the filegroup read-only again using ALTER DATABASE, as follows:
ALTER DATABASE Database
MODIFY FILEGROUP filegroup_name READONLY"
March 13, 2003 at 9:08 am
Are these database warm standby from log shipping or replication?
March 13, 2003 at 11:27 am
Replication.
quote:
Are these database warm standby from log shipping or replication?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply