Virtual devices not initialized

Virtual devices not initialized

Post by Cliff Vasice » Thu, 20 Mar 1997 04:00:00



I am running sybase 4.9 and have a problem that consists of one or two
virtual devices not being initialized correctly when I reboot an
HP-UX box.  Sybase itself gets started correctly, but the data and log
devices used by one of my databases don't always get initialized
correctly.  This, of course, prevents the database that depends on these
devices from being started corretly.  Below is a portion of the errorlog
that shows the problem:

00: 97/03/18 22:20:15.69 server: Opening Master Database ...
00: 97/03/18 22:20:17.17 server: Loading SQL Server's default sort order
and cha
racter set
00: 97/03/18 22:20:17.29 kernel: network name nimsvxi1, type hp-ether,
port 2028
00: 97/03/18 22:20:17.48 server: Recovering database 'master'
00: 97/03/18 22:20:17.56 server: Recovery dbid 1 ckpt (1994,23)
00: 97/03/18 22:20:17.58 server: Recovery no active transactions before
ckpt.
00: 97/03/18 22:20:18.47 server: server is unnamed
00: 97/03/18 22:20:18.65 server: Activating disk 'nimsdata_disk'.
00: 97/03/18 22:20:18.71 kernel: Initializing virtual device 1,
"/users/sybase/nimsdata"
00: 97/03/18 22:20:19.22 kernel: dopen: open "/users/sybase/nimsdata",
Permission denied
00: 97/03/18 22:20:19.43 kernel: udactivate: error starting virtual disk
1
00: 97/03/18 22:20:19.49 server: Activating disk 'nimslog_disk'.
00: 97/03/18 22:20:19.54 kernel: Initializing virtual device 2,
"/users/sybase/nimslog"
00: 97/03/18 22:20:19.57 kernel: dopen: open "/users/sybase/nimslog",
Permission denied
00: 97/03/18 22:20:19.59 kernel: udactivate: error starting virtual disk
2
00: 97/03/18 22:20:20.44 server: Recovering database 'model'.
00: 97/03/18 22:20:20.53 server: Recovery dbid 3 ckpt (141,3)
00: 97/03/18 22:20:20.55 server: Recovery no active transactions before
ckpt.
00: 97/03/18 22:20:20.64 server: Clearing temp db
00: 97/03/18 22:20:24.18 server: Recovering database 'pubs2'.
00: 97/03/18 22:20:24.26 server: Recovery dbid 4 ckpt (589,28)
00: 97/03/18 22:20:24.28 server: Recovery no active transactions before
ckpt.
00: 97/03/18 22:20:24.70 server: Recovering database 'newpub'.
00: 97/03/18 22:20:24.79 server: Recovery dbid 5 ckpt (345,4)
00: 97/03/18 22:20:24.82 server: Recovery no active transactions before
ckpt.
00: 97/03/18 22:20:24.89 kernel: udstartio: vdn 1 has not been set up
00: 97/03/18 22:20:24.96 server: Error: 840, Severity: 17, State: 1
00: 97/03/18 22:20:24.98 server: Device 'nimsdata_disk' (with physical
name 'nim
sdata_disk', and virtual device number 1) has not been correctly
activated at st
artup time.  Please contact System Administrator for assistance.
00: 97/03/18 22:20:25.55 server: Unable to proceed with the recovery of
dbid <6>
 because of previous errors.  Continuing with the next database.
00: 97/03/18 22:20:25.79 server: Recovering database 'nacms1'.
00: 97/03/18 22:20:25.85 server: Recovery dbid 7 ckpt (430,14)
00: 97/03/18 22:20:25.87 server: Recovery no active transactions before
ckpt.

If I log into sybase after this occurs, execute a shutdown command, then
restart sybase from the command line, the devices get initialized
correctly, but the database that depends upon the devices gets flagged
as suspect and does not get started.

Does anyone know what could be preventing the devices from being
initialized correctly some of the time?  If so, do you know how I
can fix the problem?

Thanks.
--
Cliff Vasicek
Applied Research Laboratories
(512) 835-3698, (512) 835-3808 (fax)

 
 
 

Virtual devices not initialized

Post by Stephen MacNei » Thu, 20 Mar 1997 04:00:00



> 00: 97/03/18 22:20:18.65 server: Activating disk 'nimsdata_disk'.
> 00: 97/03/18 22:20:18.71 kernel: Initializing virtual device 1,
> "/users/sybase/nimsdata"
> 00: 97/03/18 22:20:19.22 kernel: dopen: open "/users/sybase/nimsdata",
> Permission denied
> 00: 97/03/18 22:20:19.43 kernel: udactivate: error starting virtual disk
> 1
> 00: 97/03/18 22:20:19.49 server: Activating disk 'nimslog_disk'.
> 00: 97/03/18 22:20:19.54 kernel: Initializing virtual device 2,
> "/users/sybase/nimslog"
> 00: 97/03/18 22:20:19.57 kernel: dopen: open "/users/sybase/nimslog",
> Permission denied
> 00: 97/03/18 22:20:19.59 kernel: udactivate: error starting virtual disk
> 2

Check your write permissions on the files.  Also, does the boot process
mount the file system in time for Sybase to access during the server
startup?

Steve

 
 
 

Virtual devices not initialized

Post by Matthew D. Hea » Wed, 26 Mar 1997 04:00:00




> I am running sybase 4.9 and have a problem that consists of one or two
> virtual devices not being initialized correctly when I reboot an
> HP-UX box.  Sybase itself gets started correctly, but the data and log
> devices used by one of my databases don't always get initialized
> correctly.
...

> If I log into sybase after this occurs, execute a shutdown command, then
> restart sybase from the command line, the devices get initialized
> correctly

Sounds to me as though perhaps for some reason the devices are not yet
ready for Sybase to use it at the moment when Sybase wants to.

Was there ever a time when these devices initialized with no problems?
What has changed between that time and the first time you experienced
the errors?  If nothing in your configuration has changed, then one
possible explanation might be that the drive is mechanically aging and
needs more time to spin-up.  How old is that drive?

One possible workaround is to put a sleep command into your RUN_SERVER
script to make it wait a little while for whatever is delaying the
availability of that device.  I've never seen this kind of problem
with Sybase, but we did once have a problem with a different database
server which depended on a license manager starting up BEFORE the
database server tried to use it.  Putting '/usr/sbin/sleep 60' into
the shell script that launched the database server cured that one for us.

---------

http://paella.med.yale.edu/~healy
"But I thought it was pointed at the rabbit *between* my feet!"

 
 
 

1. Could not initialize the Java virtual machine

Hello
I use MS-SQL at work and just decided to give DB2 a try. I have version 6
trial version on CD. I installed it and created the sample database
successfully, but when I try to do anything else, I get the error: "Could
not initialize the Java Virtual Machine. Program will exit". What has this
got to do with Java anyway?!! Is DB2 written in Java?

Anyway, how can I get around that? I uninstalled the software, went to MS
website, installed the latest version of JVM and reinstalled and I am still
getting the same error !!

Please post only
Thanks
--

2. DB Ownership vs Object Ownership

3. Install failes (Initializing Java Virtual Machine...)

4. SQL Database auto instaalation.

5. Cannot initialize Java Virtual Machine

6. How can I set a ComboBox in a column of a Data Grid?

7. Restore from database device not backup device

8. How to: a list of currently connected users?

9. raw device or not raw device

10. still can't initialize the f*!@# raw devices

11. A question about virtual device numbers

12. Virtual Device Number

13. errors when use vdi(virtual device interface) to program for backup