BUG: Error 5105 if Disk Init Reuses vdevnoID: Q112589
|
BUG# OS/2: 1569 (4.2)
NT: 436 (4.2)
A device activation error may occur if a device is dropped, then a
subsequent disk init incorrectly reuses the same vdevno. However, the 5105
error issued is misleading as to the true cause of the error.
The system administrator assigns each SQL Server device a virtual device
number (vdevno) unique for that SQL Server. As noted in the remarks
section of the DISK INIT command, vdevno's and physical file names are
not reusable. If the SA drops a device and then attempts to initialize
another device with the same vdevno, the disk init command will fail
with a 5105 error:
Device activation error.
The physical file name '%.*s' may be incorrect.
kernel udactivate: vdn X already active
disk init name='test5105', physname='c:\test5105.dat',
vdevno=5, size=512
go
sp_dropdevice test5105
go
disk init name='next5105', physname='c:\next5105.dat',
vdevno=5, size=512
go
Device number %ld already used.
Rerun the disk init command with a new vdevno and a new physical file
name. If the SQL Server is shutdown and then restarted, the physical
file that was created by the disk init, which failed with the error 5105,
can be deleted manually, and the name respecified.
NOTE: After SQL Server has been stopped and restarted the vdevno can also
be reused.
Microsoft has confirmed this to be a problem in SQL Server version 4.2 for OS/2 and Microsoft SQL Server version 4.2. This problem does not occur in version 6.0.
Keywords : kbother kbbug4.20 kbbug4.21 kbbug4.21a SSrvServer SSrvWinNT
Version : 4.2 | 4.2 4.21 4.21a
Platform : OS/2 WINDOWS
Issue type :
Last Reviewed: March 18, 1999