StoreEver Tape Storage
1755386 Members
3398 Online
108832 Solutions
New Discussion юеВ

Re: what is the meaning of this parameter?

 
thebeatlesguru
Regular Advisor

what is the meaning of this parameter?

DLT 8000,these days DLT 8000 always report Major:[Major] From: BMA@dbbak-lc "Drive 4" Time: 02/25/02 06:27:19
[90:181] Can not backspace segment. ([5] I/O error)

[Minor] From: BMA@dbbak-lc "Drive 4" Time: 02/25/02 06:27:19
[90:65] /dev/rmt/1m
Can not append to medium ([5] I/O error)

HP engineer tell me to revise a parameter in /etc/opt/omni/options:SmPeerID,
SmPeerID=15

i dont konw what does parameter mean.

hihi
3 REPLIES 3
A. Clay Stephenson
Acclaimed Contributor

Re: what is the meaning of this parameter?

Hi:

This is basically a parameter that adjusts the timeout period in minutes between session managers [Backup Session Manager (bsm), Restore Session Manager (rsm), Database Session Manager (dbsm), or Media Session Manager (msm)] and their clients. You are being told to increase the timeout from the default of 5 minutes to 15 minutes.

Regards, Clay
If it ain't broke, I can fix that.
Curtis Ballard
Honored Contributor

Re: what is the meaning of this parameter?

According to the Quantum web site the timeout value for DLT 8000 drives is 16 minutes for a load or unload so a setting of 15 minutes is probably reasonable. If you only have a 5 minute timeout then load a tape and send a space command you will get the errors you observed.
thebeatlesguru
Regular Advisor

Re: what is the meaning of this parameter?

after increase 5 to 15 mins two days before,yesterday's sessiones is complete,but today's session has failure,report as following:[Major] From: BMA@dbbak-lc "Drive 3" Time: 02/26/02 04:11:35
[90:51] /dev/rmt/0m
Can not write to device ([5] I/O error)

[Major] From: BMA@dbbak-lc "Drive 3" Time: 02/26/02 04:11:35
[90:51] /dev/rmt/0m
Can not write to device ([5] I/O error)

[Critical] From: OB2BAR@dbbak-lc "mdb" Time: 02/26/02 04:11:36
Received ABORT request from SM => aborting.

[Critical] From: OB2BAR@dbbak-lc "mdb" Time: 02/26/02 04:11:36
Received ABORT request from SM => aborting.

[Critical] From: OB2BAR@dbbak-lc "mdb" Time: 02/26/02 04:11:36
Received ABORT request from SM => aborting.

[Major] From: BMA@dbbak-lc "Drive 3" Time: 02/26/02 04:11:36
[90:180] Can not rewind medium. ([5] I/O error)

[Major] From: BMA@dbbak-lc "Drive 3" Time: 02/26/02 04:11:36
[90:64] Can not unload exchanger medium (Details unknown.)

[Normal] From: BMA@dbbak-lc "Drive 3" Time: 02/26/02 04:11:36
ABORTED Medium Agent "Drive 3"

[Normal] From: OB2BAR@dbbak-lc "mdb" Time: 02/26/02 04:11:38
Completed OB2BAR Backup: mdb_online_full_backup<454823208>.dbf

RMAN-00569: ================error message stack follows================
RMAN-03007: retryable error occurred during execution of command: backup
RMAN-07004: unhandled exception during command execution on channel dev_5
RMAN-10032: unhandled exception during execution of job step 198: ORA-06512: at line 88
RMAN-10035: exception raised in RPC: ORA-19624: operation failed, retry possible
ORA-27015: skgfcls: failed to close the file
HP-UX Error: 1: Not owner
Additional information: 1074567480
ORA-19502: write error on file "mdb_online_full_backup<454821708>.dbf", blockno 1540801 (blocksize=1024)
ORA-27010: skgfwrt: write to file failed
Additional information: 1073745920
ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 411
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE


how can i deal with this problem

hihi