DRD fail with a hang-up signal

[NDO]

Any ideas how to solve this?

[Pete Randall]

/dev/dsk/c40t0d0 seems like a kind of an unusual device (c40?).  What does "diskinfo /dev/rdsk/c40t0d0" return?

[NDO]

its

#diskinfo /dev/rdsk/c40t0d0
SCSI describe of /dev/rdsk/c40t0d0:
             vendor: NETAPP
         product id: LUN
               type: direct access
               size: 262144000 Kbytes
   bytes per sector: 512

[Patrick Wallek]

A "hang-up" indicates to me that something, or someone, did a 'kill -1' on the DRD process.

I just duplicated your error by doing just that.

[Pete Randall]

It seems you're running this through some sort of job scheduler perhaps????  Have you tried just doing it from the command line?

Thanks, Patrick!

[NDO]

Hi

I did run it from the command line, for sure

Patrick!

I am using ssh putty session that if stays idle for more than 10 minutes losses the connection to the server. Would this be the culprit, causing a kill -1?

[Pete Randall]

> if stays idle for more than 10 minutes . . . .Would this be the culprit

You tell us.  Did it take 10 minutes to fail?  How is "idle" defined?  Screen I/O activity?

[James R. Ferguson · Accepted solution]

---

@Nandinho wrote:

I am using ssh putty session that if stays idle for more than 10 minutes losses the connection to the server. Would this be the culprit, causing a kill -1?

---

As the parent process the PuTTY session,  a SIGHUP would be sent to the DRD process, killing it.  You could avoid this by starting it with 'nohup' in the background.  You could defeat whatever timeout the session enforces too.

Regards!

...JRF...

[NDO]

sorry I should have look it, I can see on /var/opt/drd/drd.log, that yesterday session started at 17:12:57 and ended with error at 19:27:16.

[NDO]

Thanks JRF,

I will try that in couple hours when the database can be shutdown.

FR