Cluster Problem -
02-02-2004
, 09:18 PM
Hi,
We have two machines running SQL Server 2000 SP4 and Windows 2000 Advanced
Server SP4. Both have processors P4 2.4 HT with 4GB RAM.
This two machines acts as cluster active/active. After installing Oracle
Client version 9.2.0.1.0 on a node, the other node fail and all cluster be
turned off. The only solution was restarting the system and this turn-on
again.
There's two production Databases and the two have a Primary File Group and a
Second File Group to Logs and the Database maximum size is fixed and the
grow is restrict too but there an increment of 100mb in Data and Logs.
NT Fibers are turned off. There's a storage too.
Anyone can help-me? The servers are ok now, but I need know what's happening
at this time.
Follow the log of the two nodes:
--------CUT---------
NODE 1 - DATE ORDER ASC
2004-01-30 02:00:14.10 backup Database log truncated: Database: ScarDB01.
2004-01-30 12:49:49.50 server The Scheduler 3 appears to be hung. SPID 0,
ECID 0, UMS Context 0x04886620.
2004-01-30 12:49:49.50 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:49:49.50 server The Scheduler 2 appears to be hung. SPID 0,
ECID 0, UMS Context 0x0488D898.
2004-01-30 12:49:49.50 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:49:49.50 server The Scheduler 1 appears to be hung. SPID 0,
ECID 0, UMS Context 0x0486E9C8.
2004-01-30 12:49:49.50 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:49:49.50 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x04877300.
2004-01-30 12:49:49.50 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:50:49.51 server The Scheduler 3 appears to be hung. SPID 0,
ECID 0, UMS Context 0x04886620.
2004-01-30 12:50:49.51 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:50:49.51 server The Scheduler 2 appears to be hung. SPID 0,
ECID 0, UMS Context 0x0488D898.
2004-01-30 12:50:49.51 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:50:49.51 server The Scheduler 1 appears to be hung. SPID 0,
ECID 0, UMS Context 0x0486E9C8.
2004-01-30 12:50:49.51 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:50:49.51 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x04877300.
2004-01-30 12:50:49.51 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:51:49.51 server The Scheduler 3 appears to be hung. SPID 0,
ECID 0, UMS Context 0x04886620.
2004-01-30 12:51:49.51 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:51:49.51 server The Scheduler 2 appears to be hung. SPID 0,
ECID 0, UMS Context 0x0488D898.
2004-01-30 12:51:49.51 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:51:49.51 server The Scheduler 1 appears to be hung. SPID 0,
ECID 0, UMS Context 0x0486E9C8.
2004-01-30 12:51:49.51 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:51:49.51 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x04877300.
2004-01-30 12:51:49.51 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:52:49.51 server The Scheduler 3 appears to be hung. SPID 0,
ECID 0, UMS Context 0x04886620.
2004-01-30 12:52:49.51 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:52:49.51 server The Scheduler 2 appears to be hung. SPID 0,
ECID 0, UMS Context 0x0488D898.
2004-01-30 12:52:49.51 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:52:49.51 server The Scheduler 1 appears to be hung. SPID 0,
ECID 0, UMS Context 0x0486E9C8.
2004-01-30 12:52:49.51 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:52:49.51 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x04877300.
2004-01-30 12:52:49.51 server Error: 17883, Severity: 1, State: 0
2004-01-30 12:53:43.77 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86) ...
2004-01-30 12:53:43.80 server Logging SQL Server messages in file
'G:\Program Files\Microsoft SQL Server\MSSQ
2004-01-30 12:53:43.80 server Server Process ID is 352.
2004-01-30 12:53:43.80 server All rights reserved.
2004-01-30 12:53:43.80 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-01-30 12:53:43.84 server SQL Server is starting at priority class
'high'(4 CPUs detected).
2004-01-30 12:53:44.63 server SQL Server configured for thread mode
processing.
2004-01-30 12:53:44.66 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2004-01-30 12:53:44.90 server Attempting to initialize Distributed
Transaction Coordinator.
2004-01-30 12:55:17.35 server Resource Manager Creation Failed: Result Code
= 0x8004d102
2004-01-30 12:55:17.63 spid3 Starting up database 'master'.
2004-01-30 12:55:18.35 spid3 Recovery is checkpointing database 'master'
(1)
2004-01-30 12:55:18.35 spid3 0 transactions rolled back in database
'master' (1).
2004-01-30 12:55:18.48 spid12 Starting up database 'Integrador'.
2004-01-30 12:55:18.48 spid10 Starting up database 'SCARDB01'.
2004-01-30 12:55:18.48 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-01-30 12:55:18.48 spid8 Starting up database 'model'.
2004-01-30 12:55:18.48 spid7 Starting up database 'Northwind'.
2004-01-30 12:55:18.48 spid6 Starting up database 'pubs'.
2004-01-30 12:55:18.48 spid5 Starting up database 'msdb'.
2004-01-30 12:55:18.48 spid3 Server name is 'SQLCLUSTER1'.
2004-01-30 12:55:18.68 spid8 0 transactions rolled back in database 'model'
(3).
2004-01-30 12:55:18.68 spid6 1 transactions rolled forward in database
'pubs' (5).
2004-01-30 12:55:18.68 spid8 1 transactions rolled forward in database
'model' (3).
2004-01-30 12:55:18.70 spid6 0 transactions rolled back in database 'pubs'
(5).
2004-01-30 12:55:18.70 spid8 Recovery is checkpointing database 'model' (3)
2004-01-30 12:55:18.71 spid6 Recovery is checkpointing database 'pubs' (5)
2004-01-30 12:55:18.71 server SQL server listening on 10.10.30.5: 1433.
2004-01-30 12:55:18.73 spid12 1 transactions rolled forward in database
'Integrador' (8).
2004-01-30 12:55:18.74 spid12 0 transactions rolled back in database
'Integrador' (8).
2004-01-30 12:55:18.74 spid7 1 transactions rolled forward in database 'Nor
thwind' (6).
2004-01-30 12:55:18.76 spid7 0 transactions rolled back in database
'Northwind' (6).
2004-01-30 12:55:18.76 spid8 Clearing tempdb database.
2004-01-30 12:55:18.84 spid12 Recovery is checkpointing database
'Integrador' (8)
2004-01-30 12:55:18.93 spid7 Recovery is checkpointing database 'Northwind'
(6)
2004-01-30 12:55:18.99 spid5 363 transactions rolled forward in database
'msdb' (4).
2004-01-30 12:55:19.20 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2004-01-30 12:55:19.21 server SQL Server is ready for client connections
2004-01-30 12:55:19.27 spid5 0 transactions rolled back in database 'msdb'
(4).
2004-01-30 12:55:19.29 spid5 Recovery is checkpointing database 'msdb' (4)
2004-01-30 12:55:19.49 spid8 Starting up database 'tempdb'.
2004-01-30 12:55:25.00 spid10 1545 transactions rolled forward in database
'SCARDB01' (7).
2004-01-30 12:55:25.33 spid10 0 transactions rolled back in database
'SCARDB01' (7).
2004-01-30 12:55:25.34 spid10 Recovery is checkpointing database 'SCARDB01'
(7)
2004-01-30 12:55:25.52 spid3 SQL global counter collection task is created.
2004-01-30 12:55:25.52 spid3 Recovery complete.
2004-01-30 12:55:26.59 spid52 Using 'xpsqlbot.dll' version '2000.80.194' to
execute extended stored procedure
2004-01-30 12:56:18.39 spid310 Using 'xpstar.dll' version '2000.80.760' to
execute extended stored procedure '
2004-01-30 14:37:46.80 spid62 Configuration option 'show advanced options'
changed from 1 to 1. Run the RECON
2004-01-30 14:37:46.80 spid62 Error: 15457, Severity: 0, State: 1
2004-01-30 14:37:46.87 spid62 Using 'xplog70.dll' version '2000.80.760' to
execute extended stored procedure
2004-01-30 14:43:02.15 server SQL Server terminating because of system
shutdown.
2004-01-30 14:51:16.26 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86) ...
2004-01-30 14:51:16.27 server SQL Server is starting at priority class
'high'(4 CPUs detected).
2004-01-30 14:51:16.27 server Logging SQL Server messages in file
'G:\Program Files\Microsoft SQL Server\MSSQ
2004-01-30 14:51:16.27 server Server Process ID is 2656.
2004-01-30 14:51:16.27 server All rights reserved.
2004-01-30 14:51:16.27 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-01-30 14:51:16.58 server SQL Server configured for thread mode
processing.
2004-01-30 14:51:16.60 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2004-01-30 14:51:16.69 server Attempting to initialize Distributed
Transaction Coordinator.
2004-01-30 14:51:19.19 spid3 Starting up database 'master'.
2004-01-30 14:51:19.55 spid12 Starting up database 'Integrador'.
2004-01-30 14:51:19.55 spid11 Starting up database 'SCARDB01'.
2004-01-30 14:51:19.55 spid8 Starting up database 'model'.
2004-01-30 14:51:19.55 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-01-30 14:51:19.55 spid7 Starting up database 'Northwind'.
2004-01-30 14:51:19.55 spid6 Starting up database 'pubs'.
2004-01-30 14:51:19.55 spid5 Starting up database 'msdb'.
2004-01-30 14:51:19.55 spid3 Server name is 'SQLCLUSTER1'.
2004-01-30 14:51:19.57 server SQL server listening on 10.10.30.5: 1433.
2004-01-30 14:51:19.65 server SQL Server is ready for client connections
2004-01-30 14:51:19.65 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2004-01-30 14:51:19.83 spid5 Recovery is checkpointing database 'msdb' (4)
2004-01-30 14:51:19.83 spid8 Clearing tempdb database.
2004-01-30 14:51:20.15 spid8 Starting up database 'tempdb'.
2004-01-30 14:51:22.58 spid3 SQL global counter collection task is created.
2004-01-30 14:51:22.58 spid3 Recovery complete.
2004-01-30 14:51:23.54 spid52 Using 'xpsqlbot.dll' version '2000.80.194' to
execute extended stored procedure
2004-01-30 14:52:07.87 spid394 Using 'xpstar.dll' version '2000.80.760' to
execute extended stored procedure '
2004-01-30 14:59:19.77 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
2004-01-30 14:59:39.45 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86) ...
2004-01-30 14:59:39.46 server Logging SQL Server messages in file
'G:\Program Files\Microsoft SQL Server\MSSQ
2004-01-30 14:59:39.46 server Server Process ID is 2664.
2004-01-30 14:59:39.46 server All rights reserved.
2004-01-30 14:59:39.46 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-01-30 14:59:39.48 server SQL Server is starting at priority class
'high'(4 CPUs detected).
2004-01-30 14:59:39.84 server SQL Server configured for thread mode
processing.
2004-01-30 14:59:39.85 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2004-01-30 14:59:40.01 server Attempting to initialize Distributed
Transaction Coordinator.
2004-01-30 14:59:42.65 spid3 Starting up database 'master'.
2004-01-30 14:59:42.99 spid12 Starting up database 'Integrador'.
2004-01-30 14:59:42.99 spid9 Starting up database 'SCARDB01'.
2004-01-30 14:59:42.99 spid8 Starting up database 'model'.
2004-01-30 14:59:42.99 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-01-30 14:59:42.99 spid7 Starting up database 'Northwind'.
2004-01-30 14:59:42.99 spid6 Starting up database 'pubs'.
2004-01-30 14:59:42.99 spid5 Starting up database 'msdb'.
2004-01-30 14:59:42.99 spid3 Server name is 'SQLCLUSTER1'.
2004-01-30 14:59:43.06 server SQL server listening on 10.10.30.5: 1433.
2004-01-30 14:59:43.23 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2004-01-30 14:59:43.24 spid8 Clearing tempdb database.
2004-01-30 14:59:43.24 server SQL Server is ready for client connections
2004-01-30 14:59:43.46 spid8 Starting up database 'tempdb'.
2004-01-30 14:59:43.85 spid9 32 transactions rolled forward in database
'SCARDB01' (7).
2004-01-30 14:59:44.04 spid9 0 transactions rolled back in database
'SCARDB01' (7).
2004-01-30 14:59:44.05 spid9 Recovery is checkpointing database 'SCARDB01'
(7)
2004-01-30 14:59:44.15 spid3 SQL global counter collection task is created.
2004-01-30 14:59:44.15 spid3 Recovery complete.
2004-01-30 14:59:46.06 spid52 Using 'xpsqlbot.dll' version '2000.80.194' to
execute extended stored procedure
2004-01-30 15:00:01.45 spid248 Using 'xpstar.dll' version '2000.80.760' to
execute extended stored procedure '
2004-01-30 15:11:58.54 spid54 Configuration option 'show advanced options'
changed from 1 to 1. Run the RECON
2004-01-30 15:11:58.54 spid54 Error: 15457, Severity: 0, State: 1
2004-01-30 15:11:58.74 spid54 Using 'xplog70.dll' version '2000.80.760' to
execute extended stored procedure
--------CUT---------
NODE 2 - DATE ORDER DESC
2004-01-30 15:12:26.49 spid80 Using 'xplog70.dll' version '2000.80.760' to
execute extended stored procedure
2004-01-30 15:12:26.41 spid80 Configuration option 'show advanced options'
changed from 1 to 1. Run the RECON
2004-01-30 15:12:26.41 spid80 Error: 15457, Severity: 0, State: 1
2004-01-30 14:52:05.77 spid160 Using 'xpstar.dll' version '2000.80.760' to
execute extended stored procedure '
2004-01-30 14:50:12.57 spid132 Using 'xpsqlbot.dll' version '2000.80.194'
to execute extended stored procedure
2004-01-30 14:50:11.74 spid3 SQL global counter collection task is created.
2004-01-30 14:50:11.74 spid3 Recovery complete.
2004-01-30 14:49:51.65 spid10 Recovery is checkpointing database 'DETRAN'
(7)
2004-01-30 14:49:51.62 spid10 0 transactions rolled back in database
'DETRAN' (7).
2004-01-30 14:49:51.56 spid10 11 transactions rolled forward in database
'DETRAN' (7).
2004-01-30 14:49:51.56 spid10 Recovery of database 'DETRAN' (7) is 100%
complete (approximately 0 more second
2004-01-30 14:49:51.54 spid10 Recovery of database 'DETRAN' (7) is 0%
complete (approximately 3 more seconds)
2004-01-30 14:49:51.53 spid10 Analysis of database 'DETRAN' (7) is 100%
complete (approximately 0 more second
2004-01-30 14:49:49.25 spid8 Starting up database 'tempdb'.
2004-01-30 14:49:49.03 spid5 Recovery is checkpointing database 'msdb' (4)
2004-01-30 14:49:49.01 spid5 0 transactions rolled back in database 'msdb'
(4).
2004-01-30 14:49:48.90 server SQL Server is ready for client connections
2004-01-30 14:49:48.90 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2004-01-30 14:49:48.84 spid5 19 transactions rolled forward in database
'msdb' (4).
2004-01-30 14:49:48.82 spid8 Clearing tempdb database.
2004-01-30 14:49:48.81 spid7 Recovery is checkpointing database 'Northwind'
(6)
2004-01-30 14:49:48.76 spid6 Recovery is checkpointing database 'pubs' (5)
2004-01-30 14:49:48.76 spid7 0 transactions rolled back in database
'Northwind' (6).
2004-01-30 14:49:48.74 spid7 1 transactions rolled forward in database
'Northwind' (6).
2004-01-30 14:49:48.73 spid6 0 transactions rolled back in database 'pubs'
(5).
2004-01-30 14:49:48.71 spid8 Recovery is checkpointing database 'model' (3)
2004-01-30 14:49:48.71 spid8 0 transactions rolled back in database 'model'
(3).
2004-01-30 14:49:48.71 spid6 1 transactions rolled forward in database
'pubs' (5).
2004-01-30 14:49:48.71 spid8 1 transactions rolled forward in database
'model' (3).
2004-01-30 14:49:48.68 server SQL server listening on 10.10.30.6: 1433.
2004-01-30 14:49:48.60 spid10 Starting up database 'DETRAN'.
2004-01-30 14:49:48.60 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-01-30 14:49:48.60 spid8 Starting up database 'model'.
2004-01-30 14:49:48.60 spid7 Starting up database 'Northwind'.
2004-01-30 14:49:48.60 spid6 Starting up database 'pubs'.
2004-01-30 14:49:48.60 spid5 Starting up database 'msdb'.
2004-01-30 14:49:48.60 spid3 Server name is 'SQLCLUSTER2\SQLCLUSTER2'.
2004-01-30 14:49:48.48 spid3 Recovery is checkpointing database 'master'
(1)
2004-01-30 14:49:48.46 spid3 0 transactions rolled back in database
'master' (1).
2004-01-30 14:49:47.90 spid3 Starting up database 'master'.
2004-01-30 14:49:43.65 server Attempting to initialize Distributed
Transaction Coordinator.
2004-01-30 14:49:43.39 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2004-01-30 14:49:43.37 server SQL Server configured for thread mode
processing.
2004-01-30 14:49:43.01 server SQL Server is starting at priority class
'high'(4 CPUs detected).
2004-01-30 14:49:42.98 server Logging SQL Server messages in file
'S:\Program Files\Microsoft SQL Server\MSSQ
2004-01-30 14:49:42.98 server Server Process ID is 2944.
2004-01-30 14:49:42.98 server All rights reserved.
2004-01-30 14:49:42.98 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-01-30 14:49:42.93 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86) ...
2004-01-30 13:13:27.55 server The Scheduler 3 appears to be hung. SPID 56,
ECID 0, UMS Context 0x0457A7B0.
2004-01-30 13:13:27.55 server Error: 17883, Severity: 1, State: 0
2004-01-30 13:13:27.55 server The Scheduler 2 appears to be hung. SPID 0,
ECID 0, UMS Context 0x0457EA00.
2004-01-30 13:13:27.55 server Error: 17883, Severity: 1, State: 0
2004-01-30 13:13:27.55 server The Scheduler 1 appears to be hung. SPID 78,
ECID 0, UMS Context 0x045853C8.
2004-01-30 13:13:27.55 server Error: 17883, Severity: 1, State: 0
2004-01-30 13:13:27.55 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x0457C5C8.
2004-01-30 13:13:27.55 server Error: 17883, Severity: 1, State: 0
2004-01-30 13:12:27.55 server The Scheduler 3 appears to be hung. SPID 56,
ECID 0, UMS Context 0x0457A7B0.
2004-01-30 13:12:27.55 server Error: 17883, Severity: 1, State: 0
2004-01-30 13:12:27.55 server The Scheduler 2 appears to be hung. SPID 0,
ECID 0, UMS Context 0x0457EA00.
2004-01-30 13:12:27.55 server Error: 17883, Severity: 1, State: 0
2004-01-30 13:12:27.55 server The Scheduler 1 appears to be hung. SPID 78,
ECID 0, UMS Context 0x045853C8.
2004-01-30 13:12:27.55 server Error: 17883, Severity: 1, State: 0
2004-01-30 13:12:27.55 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x0457C5C8.
2004-01-30 13:12:27.55 server Error: 17883, Severity: 1, State: 0
2004-01-30 13:11:27.55 server The Scheduler 3 appears to be hung. SPID 56,
ECID 0, UMS Context 0x0457A7B0.
2004-01-30 13:11:27.55 server Error: 17883, Severity: 1, State: 0
2004-01-30 13:11:27.55 server The Scheduler 2 appears to be hung. SPID 0,
ECID 0, UMS Context 0x0457EA00.
2004-01-30 13:11:27.55 server Error: 17883, Severity: 1, State: 0
2004-01-30 13:11:27.55 server The Scheduler 1 appears to be hung. SPID 78,
ECID 0, UMS Context 0x045853C8.
2004-01-30 13:11:27.55 server Error: 17883, Severity: 1, State: 0
2004-01-30 13:11:27.55 server The Scheduler 0 appears to be hung. SPID 0,
ECID 0, UMS Context 0x0457C5C8.
2004-01-30 13:11:27.55 server Error: 17883, Severity: 1, State: 0
2004-01-30 13:10:27.56 server The Scheduler 3 appears to be hung. SPID 56,
ECID 0, UMS Context 0x0457A7B0.
2004-01-30 13:10:27.56 server Error: 17883, Severity: 1, State: 0
2004-01-30 13:10:27.56 server The Scheduler 2 appears to be hung. SPID 0,
ECID 0, UMS Context 0x0457EA00.
2004-01-30 13:10:27.56 server Error: 17883, Severity: 1, State: 0 |