ShackDaddy
MIS
I just installed SQL2000 on a Compaq CL380 2-node cluster. The installation
went beautifully, but I'm having some strange problems trying to create
databases. When I use SQL2000 Enterprise Manager on the node of the cluster
that currently is hosting the SQL2000 resource and create a database,
Enterprise Manager stops responding, and after about 20 minutes of waiting,
I just end the task and reopen Enterprise Manager and the database does not
exist.
I'm creating a 3gig empty database with a 300mb transaction log. I'm putting
the database and log files on separate partitions on the shared storage
array. While I'm waiting for Enterprise Manager to unlock, I'm able to
browse the directories and see that the files for the log and database have
been created, but when I eventually kill the Enterprise Manager process, the
files that were created immediately disappear from the folders they were
created in.
I tried creating a 1mb database and 1mb log in the same locations, and it
seemed to work fine (the database was created and showed up in the EM list),
although the EM did freeze up for a little while. I've tried using EM to do
this both locally and from another workstation. The behavior is the same in
both places. I went and set the memory on SQL to use at least 1/2 of the
available physical memory, just in case it was having trouble initializing
the memory, but that didn't help.
A couple of days ago, after I did the install, I did fail the resource group
back and forth a few times, and there didn't seem to be any problems with
the failover mechanisms.
Anybody have any idea what might be going on here?
David Shackelford
went beautifully, but I'm having some strange problems trying to create
databases. When I use SQL2000 Enterprise Manager on the node of the cluster
that currently is hosting the SQL2000 resource and create a database,
Enterprise Manager stops responding, and after about 20 minutes of waiting,
I just end the task and reopen Enterprise Manager and the database does not
exist.
I'm creating a 3gig empty database with a 300mb transaction log. I'm putting
the database and log files on separate partitions on the shared storage
array. While I'm waiting for Enterprise Manager to unlock, I'm able to
browse the directories and see that the files for the log and database have
been created, but when I eventually kill the Enterprise Manager process, the
files that were created immediately disappear from the folders they were
created in.
I tried creating a 1mb database and 1mb log in the same locations, and it
seemed to work fine (the database was created and showed up in the EM list),
although the EM did freeze up for a little while. I've tried using EM to do
this both locally and from another workstation. The behavior is the same in
both places. I went and set the memory on SQL to use at least 1/2 of the
available physical memory, just in case it was having trouble initializing
the memory, but that didn't help.
A couple of days ago, after I did the install, I did fail the resource group
back and forth a few times, and there didn't seem to be any problems with
the failover mechanisms.
Anybody have any idea what might be going on here?
David Shackelford