UNSOLVED
Rman Backup Session decrease problem
Hi,
We are backing up Oracle Db ( 10 g) with nmo 5.0 (from HPux), We are using 20 sessions for backing up. Backup is starting from 20 channell as expected but after first pieces finished, there were below error appears and backup is continuing with less (disabling channel count changes between 3-7) channels. Backup is finishing successfuly but it is increasing our backup duration. Is there any idea ?
Thanks.
RMAN-03009: failure of backup command on ORA_SBT_TAPE_18 channel at 06/23/2010 01:08:09
ORA-19506: failed to create sequential file,, parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
Direct saves are not enabled. (0:5:2)
channel ORA_SBT_TAPE_18 disabled, job failed on it will be run on another channel
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.
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
zodiaconline
1 Rookie
•
28 Posts
1146
0
Posted August 9th, 2011 23:00
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.
coganb
736 Posts
1563
0
Posted August 10th, 2010 03:00
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