Oracle DIVArchive Error: "Drive Not Accessible" in Scandrive After Library Hardware Changes
(Doc ID 2149622.1)
Last updated on SEPTEMBER 11, 2018
Applies to:Oracle DIVArchive - Version 6.5 and later
Information in this document applies to any platform.
For tape drive requests, every write operation for the library in question is getting error "Drive not accessible" after the mount step completes.
New drives go offline and consistently error with "Drive out of order" or "No actor connected to this drive".
When using scandrive.exe (found in C:\DIVA\Program\Actor\bin\scandrive.exe, ran on actor server in CMD) the drives in question show the error "Drive is Not Accessible" for the status.
If incorrect drivers were installed, Actor logs will show "invalid handle value error code=170" when IBM exclusive drivers are used.
Drives have been added, removed or changed order.
Recent LTO-7 drives were added to the system, or Multi-Pathing was enabled on drives. Multipathing is a NON-DIVA configuration that would be made by the Library or Drive configurations, that allows for more than one physical path to transfer data. This may or may not present as drives showing multiple times in Device Manager or scandrive.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document