Rman Backup Session decrease problem

If you run this on a reduced amount of channels, does it fail like this also or does it run without error?  I know this isn't what you want to do, but it would be interesting to test to see what number of channels it can't handle to see if this error is load-related or not.

-Bobby

Hello

My name is David Pravia, I am Networker and Oracle expert.

The error you mentioned in your post is a well known issue. I would like to ask u what version of Networker client is running in the Oracle server. I would suggest you to upgrade the client to at least 7.5.3 or 7.6.1

Direct save not enable is a well known error produced by a misleading between NMO and NW client

Please let me know how it goes

Many thanks

David S Pravia

Hi David,

  Networker  version is 7.4.4 and we are planning to upgrade that storage node to 7.4.5. We can' t upgrade it to 7.5.3 or 7.6 now, because nw server version is 7.4.5.

  By the way ıf it was  a known issue, could you sent me article number ?

Thanks.

Ok thank you, I will thy it, and I will inform you.

Mr Can,

Try first to disable the strong auth before downgrading and let me know

Thanks

Strong auth may solve the problem, and I am planning to downgrade nmo version to 4.5

Hello Mr Can

This is one of the statemnst that suggest NMO would better run on 7.5 or later, I found it in the NMO 5.0 Technical releases:

NMO release 5.0 provides new support for deduplication backups and restores, which requires NetWorker server and client release 7.5 or later.

Also I would suggest you to remove the strong auth too

Thanks

Mr Can

Could you please let us know whether the strong authentication has resolved this issue?

Many thanks

David S Pravia

Hi David,

  Customer will inform me when he changed auth method, I will inform you when he test your advice...

Thanks.

Hi,

we are also getting the same error with networker server 7.6.1.7 and client version 7.6.1. we are using nmda 1.1 with oracle 11gR2 on the RHEL 5.6 server.

the same error also occurred with SAP backups. we are using nmsap 4.1 with nw client 7.6.1.

The interesting point is that we are not getting this error a few weeks ago. There is inconsistent situation i think. what can be the problem. Any ideas?

thank you.

With SAP you are using BRTools or RMAN option?  Nevertheless, one instance when I have seen this in the past is when you use nsruauth.  Disabling may do the trick.

Hi  David,

I am getting below error on Linux server   for DB oracle running on NDMA   oracle backup 1.2  and networker version is 8.0.1

channel t4: starting piece 1 at 01-FEB-14

RMAN-03009: failure of backup command on t1 channel at 02/01/2014 23:00:39

ORA-19502: write error on file "bk_1313_1_838411278", block number 3246417 (block size=16384)

ORA-27030: skgfwrt: sbtwrite2 returned error

ORA-19511: Error received from media manager layer, error text:

   asdf_output_section1() failed

xdr=0x0xc8b5f30: bp=0x0xc8b5f50: send_len=262144: type=12800: fhand=0x0xc8b6f70: wrapper=0x0xc8b6f90: directp=0x0xc8b5fd0 (1:4:104)

channel t1 disabled, job failed on it will be run on another channel

Please help me in resolving issue   ..

Thanks in advance ...

Its an error from the media management layer. Has this worked before ? I would start checking the availability of devices. Can you share the script used ?

Sent from mobile device please ignore typo

--- Original Message ---

Hi ,

No this backup was never successful ..

Please find below script …

#######################

#!/bin/bash

export ORACLE_SID=QADB

export ORACLE_HOME=/u01/app/oracle/product/11.2.0

export PATH=$ORACLE_HOME/bin:$PATH

v_dbtag=QADB_COLD_l0_`date +%Y%m%dT%H%M`

1. 1. Backup database ##

rman target / <

run

{

sql 'alter system checkpoint';

shutdown abort;

startup;

shutdown immediate;

startup mount;

allocate channel t1 type='sbt_tape' parms='ENV=(NSR_SERVER=dwhbackup,NSR_CLIENT=prodetldw,NSR_DATA_VOLUME_POOL=WeeklyOnsite)' MAXOPENFILES 1;

allocate channel t2 type='sbt_tape' parms='ENV=(NSR_SERVER=dwhbackup,NSR_CLIENT=prodetldw,NSR_DATA_VOLUME_POOL=WeeklyOnsite)' MAXOPENFILES 1;

allocate channel t3 type='sbt_tape' parms='ENV=(NSR_SERVER=dwhbackup,NSR_CLIENT=prodetldw,NSR_DATA_VOLUME_POOL=WeeklyOnsite)' MAXOPENFILES 1;

allocate channel t4 type='sbt_tape' parms='ENV=(NSR_SERVER=dwhbackup,NSR_CLIENT=prodetldw,NSR_DATA_VOLUME_POOL=WeeklyOnsite)' MAXOPENFILES 1;

BACKUP INCREMENTAL LEVEL=0 TAG $v_dbtag FILESPERSET 10 FORMAT 'bk_%s_%p_%t' DATABASE INCLUDE CURRENT CONTROLFILE;

BACKUP FORMAT 'cntrl_%s_%p_%t' CURRENT CONTROLFILE;

release channel t1;

release channel t2;

release channel t3;

release channel t4;

}

exit

EOF

rman target / CATALOG RMANDWH/RMANDWH@RMANDB <

run

{

alter database open;

allocate channel t1 type='sbt_tape' parms='ENV=(NSR_SERVER=dwhbackup,NSR_CLIENT=prodetldw,NSR_DATA_VOLUME_POOL=WeeklyOnsite)' MAXOPENFILES 1;

RESYNC CATALOG;

CROSSCHECK ARCHIVELOG ALL;

CROSSCHECK BACKUPSET;

CROSSCHECK BACKUP OF ARCHIVELOG ALL;

CROSSCHECK BACKUP OF DATABASE;

CROSSCHECK BACKUP OF CONTROLFILE;

CROSSCHECK BACKUP OF SPFILE;

release channel t1;

release channel t2;

release channel t3;

release channel t4;

}

exit

EOF

rman target / CATALOG RMANDWH/RMANDWH@RMANDB <

run

{

alter database open;

allocate channel t1 type='sbt_tape' parms='ENV=(NSR_SERVER=dwhbackup,NSR_CLIENT=prodetldw,NSR_DATA_VOLUME_POOL=WeeklyOnsite)' MAXOPENFILES 1;

RESYNC CATALOG;

CROSSCHECK ARCHIVELOG ALL;

CROSSCHECK BACKUPSET;

CROSSCHECK BACKUP OF ARCHIVELOG ALL;

CROSSCHECK BACKUP OF DATABASE;

CROSSCHECK BACKUP OF CONTROLFILE;

CROSSCHECK BACKUP OF SPFILE;

release channel t1;

}

exit

EOF

1. End of backupdb #

Cheers,

Bhanu Prakash K | VFQ- IMS

Vodafone Qatar – Level 2, Tech 2, Qatar Science & Technology Park.

Al Gharaffa Street, Al Rayyan Education City, Doha, Qatar

Mobile: +974 30191587

The pool weeklyOnsite used tapes or data domain or aftd ? Try a filesystem backup for the same client using the same pool.

Sent from mobile device please ignore typo

--- Original Message ---