| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 713.1 | SQL & Clusters | NETRIX::"harrisonbc@mail.dec.com" | Brynn Harrison | Tue Mar 25 1997 19:47 | 9 |
| I don't know a direct answer to your question, but the way I got around the
problem was to remove Clusters from one machine, then re-install, joining the
current cluster.
After this the registries synchronise and the SQL databases are available on
both nodes.
Brynn Harrison
[Posted by WWW Notes gateway]
|
| 713.2 | move SQL db from local disk to shared disk | AEOENG::16.40.240.154::annecy::lehy | | Fri Mar 28 1997 15:37 | 17 |
|
Another similar question
ServerA is running SQL with a database on a local disk
ServerB is running SQL with a database on a local disk
ServerA and ServerB are clusterized
I now want to move the SQL db onto shared storage and enroll the
existing DB for failover support. How do I do that ?
This is a real-life scenario.
Thanks
|
| 713.3 | Recovering from reinstallation | DECWET::CAPPELLOF | My other brain is a polymer | Tue Apr 01 1997 22:46 | 40 |
| >I have the case where someone re-installed SQL 6.5 on one of the cluster
>members (a demo cluster)
That's a bad thing to do, but you can recover.
> The existing enrolled databases do not failover
> or even show up in the enterprise manager.
Probably because reinstalling SQL 6.5 overwrote your SQL master
database, which contains the names of all other databases and their
locations.
>I had to "create procedure" for each sp_*.sql file I could find in the
>cluster directory (sp_DEC_*.sql and sp_fallback_DEC_*)
There are two ways to re-install the sp_*.sql files you need:
1) isql -Usa -Pxxxx -n -i sp_*.sql
for each .sql file in the cluster directory. ("xxxx" is your SQL
sa password)
or
2) Use regedt32 to delete the following registry VALUE:
machine\system\CurrentControlSet\Services\Cfmd\Database\FMtype\FMSql\Version
then restart the Digital Clusters Failover Manager service. Deleting
the "version" value will cause the Cluster Failover manager to
reinstall all the stored procedures from the cluster directory.
>I used sp_fallback_withdraw_xxx to remove the entries in the fallback
>tables
On the server where SQL 6.5 was reinstalled, you should see empty
spt_fallback_xxx tables. Did you execute the above procedure on the
server where SQL 6.5 was NOT reinstalled?
>Now, I have the situation where I have a .dat file (the database device) on
>a shared disk. This device and the database itself does not show up in
>Enterprise Manager. How can I do that ?
Look at SQL documentation for the DISK REINIT and DISK REFIT commands.
They may allow you to recover the database from the .DAT file.
|
| 713.4 | | AEOENG::16.40.240.154::annecy::lehy | | Tue Apr 08 1997 09:13 | 43 |
| Thanks Carl
I tried DISK REINIT and DISK REFIT successfully.
Because of the many warning messages displayed by DISK REFIT, I would not
recommend the following procedure to people running real data. I am only
setting-up/running demos and I am not really concerned with the
integrity of data.
From isql/W
select the master db
disk reinit
NAME = 'DeviceName',
PHYSNAME = 'x:\sqlData_Web.DAT'
VDEVNODE = <vdevno>,
SIZE = <size in 2kbytes units>
if sqlData_Web.DAT is 51200kb then size must be 25600
use sp_helpdevice to get a free vdevno
stop sqlserver service
start sql server service from the console (in standalone mode)
sqlservr -m
isql /U sa /P <password> /Q "DISK REFIT"
if you are prompted, type quit to exit
stop sqlservr (ctrl-c)
start sqlserver service with control panel
Check with Enterprise Mgr (for example) that your db is there
again.
|