| Title: | WinNT-Clusters |
| Notice: | Info directories moved to DECWET::SHARE1$:[NT_CLSTR] |
| Moderator: | DECWET::CAPPELLOF |
| Created: | Thu Oct 19 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 863 |
| Total number of notes: | 3478 |
Hello.
3.51 SP5 1.0 SP2 6.5 SP1 on Alpha..lots of numbers:-)
Need some help to understand how SQL and Cluster
work together and what the FMlog really say..
1. Is there any recommendation on do/don't when doing
SQL server management AFTER cluster is installed in
order not to disturbe the cluster..
Like adding more stored procedures,
Changing size of db/devices on enrolled databases
And how important to keep the 2 SQL servers in
sync,
Yes I know the question is kind of vauge so general
comments are also welcome.
2. Had a scenario where a connection to a network drive
made the driveletter busy when a failover to that sys
was performed..
"Drive letter F: could not be assigned to
\Device\Harddisk0\Partition1
because it already has definition"
The drive got another driveletter, in this case J:
If an enrolled database on that drive..
Will SQL handle this if the database "move" to another
drive? If changes is being made to the master database to
update the change of "drive" when/how will the other node
get that information at the failback..
Some extracts form FMlog..
SQLDLL: Activating DBs...
SQLDLL: Remap drive(BEMAS_SERVER_2, F:, J:)
SQLDLL: Remap drive(BEMAS_SERVER_2, J:, M:)
SQLDLL: Remap drive(BEMAS_SERVER_2, F:, J:)
SQLDLL: Remap drive(BEMAS_SERVER_2, F:, J:)
Looks that drive F: gets a new name J: but what is
the second line J:,M? and should I read one line
Remap for each databasedevice?
Procedure 'sp_fallback_upd_dev_drive',
Line 81 Fallback drive data was updated for 5 devices.
What kind of drive data is updated?
Procedure 'sp_dboption',
Line 374
Opening device 'bemas_dv_1' and marking it as non-deferred
sp_dboption..working on DEVICE? and non-deferred..extension
to the procedure? I can not find the info in SQL 6.5 online books.
Questions, questions.. I hold my fire for the moment.
Thanks in advance!
Regards/Sven in the ceNTer of Sweden
[Posted by WWW Notes gateway]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 800.1 | SQL DLL logs a lot of internal info | DECWET::CAPPELLOF | My other brain is a polymer | Wed May 14 1997 17:40 | 57 |
> Like adding more stored procedures,
Should be no problem.
> Changing size of db/devices on enrolled databases
Follow the procedures outlined in the Cluster Administrator's Guide
Chapter 3 to change the size of db/devices on enrolled databases. This
is very important!
...
>Will SQL handle this if the database "move" to another
>drive?
Yes. The "Remap drive" log entries you see show that the cluster
software is changing the drive letter used by SQL for a "device". The
"Remap drive(BEMAS_SERVER_2, F:, J:)" log entry means that the cluster
software changes the a device entry in the master database to use drive
letter "J:" instead of drive letter "F:". You will see one "remap"
command for each database that is enrolled. (Actually, if your database
is split across several devices, you may see several remap commands for
that database).
I don't know why you see a remap (J:, M:), though. Maybe there is a
database that was originally on drive J:, and that drive has been
renamed to M:.
>If changes is being made to the master database to
>update the change of "drive" when/how will the other node
>get that information at the failback..
Information about the original drive letter is kept in a SQL table
called "spt_fallback_dev". Rows in this table are created on both
cluster nodes when a database is enrolled for fallback support. The
cluster software also keeps information about the ACTUAL drive letters
in the cluster "database", and knows how to remap drive letter
assignments each time a database is brought online.
> Procedure 'sp_dboption',
> Line 374
> Opening device 'bemas_dv_1' and marking it as non-deferred
>
>sp_dboption..working on DEVICE? and non-deferred..extension
>to the procedure? I can not find the info in SQL 6.5 online books.
This part of the log records output from the 'sp_dboption' stored
procedure, which is used to put a database online. One of the steps
in putting a database online looks like this:
sp_dboption 'database_name', offline, false
You can use SQL 6.5 Enterprise Manager to look at the source code for
sp_dboption. At line number 374 in this procedure, you will see a line
that prints the message you see in the log.
| |||||