Avamar Oracle plugin backup failing

Hi Friends,

In our environment, Avamar oracle plugin backups failing with the below error, please let me know if anyone came accross the same issue..

My setup is:

Avamar server on 7.2

Avamar client and oracle plugin is on 7.1

Failed Backup log details,

------------------------------------

Log #2: avoracle log 2018-07-03 13:18:06 CDT [7.1.101-145 AIX-00F847D44C00]

2018-07-03 13:18:06 avoracle Info <5008>: Logging to /usr/local/avamar/var/clientlogs/MOD-1530641885468-5002-Oracle.log

2018-07-03 13:18:06 avoracle Info <16787>: vardir = /usr/local/avamar/var/clientlogs

2018-07-03 13:18:06 avoracle Info <6673>: CTL listening on port 42550

2018-07-03 13:18:06 avoracle Info <10684>: Setting ctl message version to 3 (from 1)

2018-07-03 13:18:06 avoracle Info <16136>: Setting ctl max message size to 268435456

2018-07-03 13:18:06 avoracle Info <7084>: target[0]=clar10g

2018-07-03 13:18:06 avoracle Info <7384>: Getting the oracle_home for clar10g

2018-07-03 13:18:06 avoracle Info <7390>: Found Service Name (SID): clar10g ORACLE_HOME: /ora12c/product/12.1.0

2018-07-03 13:18:06 avoracle Info <7276>: runflags.orahome=/ora12c/product/12.1.0

2018-07-03 13:18:06 avoracle Info <7950>: No codepage specified

2018-07-03 13:18:06 avoracle Info <14190>: sqlplus cmd:/ora12c/product/12.1.0/bin/sqlplus var:/usr/local/avamar/var/clientlogs

2018-07-03 13:18:06 avoracle Info <7783>: Setting spawn user/group ( )

2018-07-03 13:18:06 avoracle Info <7953>: Username set to "oracle"

2018-07-03 13:18:06 avoracle Info <11908>: Oracle version 12

2018-07-03 13:18:06 avoracle Info <7956>: MML set to libobk_avamar64.so

2018-07-03 13:18:06 avoracle Info <18466>: RMAN is connecting to the Oracle DB using OS authentication.

2018-07-03 13:18:06 avoracle Info <7289>: RMAN=/ora12c/product/12.1.0/bin/rman

2018-07-03 13:18:06 avoracle Info <7783>: Setting spawn user/group ( )

2018-07-03 13:18:06 avoracle Info <7953>: Username set to "oracle"

2018-07-03 13:18:06 avoracle Info <7782>: User 'oracle' is uid=11000, gid=2000

2018-07-03 13:18:23 avoracle Error <7934>: Snapup of clar10g aborted due to rman terminated abnormally - check the logs

2018-07-03 13:18:23 avoracle Info <7271>: Final summary generated subwork 1, cancelled/aborted 1, snapview 0, exitcode 157

END avoracle log 2018-07-03 13:18:28 CDT (0 warnings, 1 error, 0 fatal errors)

Log #4: usr/local/avamar/var/clientlogs/MOD-1530641885468-5002-Oracleclar10g-rman1.log

Recovery Manager: Release 12.1.0.2.0 - Production on Tue Jul 3 13:18:06 2018

Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved.

RMAN> @@clar10g-15431.tmp

2> connect target *;

3> **end-of-file**

4> run {

5> configure controlfile autobackup on;

6> set controlfile autobackup format for device type sbt to 'CONTROLFILE.clar10g.%F';

7> allocate channel c0 type sbt PARMS="SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so" format '%d_%U';

8> send  channel 'c0' '"--libport=42552" "--force-expires" "--cacheprefix=clar10g_c0" "--sysdir=/usr/local/avamar/etc" "--bindir=/usr/local/avamar/bin" "--vardir=/usr/local/avamar/var/clientlogs" "--logfile=/usr/local/avamar/var/clientlogs/MOD-1530641885468-5002-Oracleclar10g-avtar0.log" "--ctlcallport=42550"';

9> backup filesperset = 1  database;

10> }

11>

connected to target database: CLAR10G (DBID=2764947226)

using target database control file instead of recovery catalog

old RMAN configuration parameters:

CONFIGURE CONTROLFILE AUTOBACKUP ON;

new RMAN configuration parameters:

CONFIGURE CONTROLFILE AUTOBACKUP ON;

new RMAN configuration parameters are successfully stored

executing command: SET CONTROLFILE AUTOBACKUP FORMAT

allocated channel: c0

channel c0: SID=985 device type=SBT_TAPE

channel c0: EMC|Avamar (avtar backup)

sent command to channel: c0

Starting backup at 03-JUL-18

RMAN-06169: could not read file header for datafile 1955 error reason 4

released channel: c0

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of backup command at 07/03/2018 13:18:22

RMAN-06056: could not access datafile 1955

Recovery Manager complete.