Backup Exec 2015 - Oracle 12 backup linux - OCI_ERROR: ORA-24300: bad value for mode

[BE_user-nl]

Dear Everyone,

We have installed Backup Exec 2015 FP1 on our server to backup Oracle 12 databases (no RAC) with it.

All the 11 and 10 databases are backupped fine except for Oracle 12. The DBA initiated job runs fine.

Every time I want to create jobs for this database, the database will show "unavailable" but checkable in the Media Server.

When i start the beremote agent in --log-console mode, i see the following:

I replaced the database name with <SID NAME>.

49c18940 Mon Aug 10 10:27:42 2015 : A Agent config has been setup on (<SID NAME>)
49c18940 Mon Aug 10 10:27:42 2015 :  RMAN_GetDBStatus: home_dir = (/)
49c18940 Mon Aug 10 10:27:42 2015 :  RMAN_GetDBStatus: db is (A)
49c18940 Mon Aug 10 10:27:42 2015 :  Current Oracle user name (SYSBACKUP)
49c18940 Mon Aug 10 10:27:42 2015 : putenv(ORACLE_SID=<SID_NAME>)
49c18940 Mon Aug 10 10:27:42 2015 : putenv(ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1)
49c18940 Mon Aug 10 10:27:42 2015 : OCIServerAttach() Linux with dbname: <SID_NAME>
49c18940 Mon Aug 10 10:27:42 2015 : OCISessionBegin() with database credentials as sysbackup user.
49c18940 Mon Aug 10 10:27:42 2015 : OCISessionBegin() failed with database credentials.
49c18940 Mon Aug 10 10:27:42 2015 : OCI_ERROR: ORA-24300: bad value for mode

I can't find anything about the error: "OCI_ERROR: ORA-24300: bad value for mode."

As i said, when i start the job manually, there is no problem. As i prefer to start the jobs on the backup exec server, i want to get this working.

DBA started job:

RMAN> CONNECT target <SID_NAME>

target database Password:
connected to target database: <SID_NAME> (DBID=296797****)

RMAN> RUN {
2> SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO 'BE_%F';
3> ALLOCATE CHANNEL ch0
4> TYPE 'SBT_TAPE';
5> SEND 'BSA_SERVICE_HOST=10.91.0.13,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={31A5203F-A15F-4CDB-BE6B-0AC7AA79C567},NBBSA_DB_DEVICE_NAME=Oracle-Linux::\\db32acc.anwb\<SID_NAME>';
BACKUP
INCREMENTAL LEVEL=1
6> 7> 8> FORMAT 'BE_%U'
9> DATABASE FORCE;
10> RELEASE CHANNEL ch0;
11> }

executing command: SET CONTROLFILE AUTOBACKUP FORMAT

using target database control file instead of recovery catalog
allocated channel: ch0
channel ch0: SID=799 device type=SBT_TAPE
channel ch0: Symantec/BackupExec/1.1.0

sent command to channel: ch0

Starting backup at 10-AUG-15
no parent backup or copy of datafile 3 found
no parent backup or copy of datafile 4 found
no parent backup or copy of datafile 2 found
no parent backup or copy of datafile 1 found
channel ch0: starting compressed incremental level 1 datafile backup set
channel ch0: specifying datafile(s) in backup set
input datafile file number=00022 name=+DATA/<SID_NAME>/DATAFILE/file_index.368.886327481
input datafile file number=00009 name=+DATA/<SID_NAME>/datafile/file_index.270.787666767
input datafile file number=00010 name=+DATA/<SID_NAME>/datafile/file_index.271.787666769
input datafile file number=00011 name=+DATA/<SID_NAME>/datafile/file_index.272.787666769
input datafile file number=00012 name=+DATA/<SID_NAME>/datafile/file_index.273.787666769
input datafile file number=00013 name=+DATA/<SID_NAME>/datafile/file_data.274.787666769
input datafile file number=00020 name=+DATA/<SID_NAME>/DATAFILE/file_index.375.879852115
input datafile file number=00017 name=+DATA/<SID_NAME>/datafile/file_data.379.805723531
input datafile file number=00007 name=+DATA/<SID_NAME>/datafile/file_data.268.787666767
input datafile file number=00008 name=+DATA/<SID_NAME>/datafile/file_data.269.787666767
input datafile file number=00018 name=+DATA/<SID_NAME>/datafile/file_data.330.830855665
input datafile file number=00005 name=+DATA/<SID_NAME>/datafile/file_data.266.787666765
input datafile file number=00019 name=+DATA/<SID_NAME>/datafile/file_data.391.833839061
input datafile file number=00021 name=+DATA/<SID_NAME>/DATAFILE/file_data.439.883332653
input datafile file number=00006 name=+DATA/<SID_NAME>/datafile/file_data.267.787666765
input datafile file number=00015 name=+DATA/<SID_NAME>/datafile/file_data.276.787666771
input datafile file number=00014 name=+DATA/<SID_NAME>/datafile/file_index.275.787666771
input datafile file number=00016 name=+DATA/<SID_NAME>/datafile/file_data.277.787666771
channel ch0: starting piece 1 at 10-AUG-15

Any Ideas?

[VJware]

Every time I want to create jobs for this database, the database will show "unavailable" but checkable in the Media Server.

Pls post a screenshot of the backup selections.

Also, have you tried to reinstall and reconfigure the Oracle Agent ?

[BE_user-nl]

@VJware,

I tried to reinstall the agent multiple times, with reboots and all, but without any succes. See the screenshot attached.

All the other databases that are open or mounted, are oracle 11 databases wich work fine. When i try to check the Oracle 12 database or when i try to open this box, its asking for login credentials. When i use the SYSBACKUP user (same as the SYS user with oracle 11) i get the error message in the agent as seen above:

49c18940 Mon Aug 10 10:27:42 2015 : A Agent config has been setup on (<SID NAME>)
49c18940 Mon Aug 10 10:27:42 2015 :  RMAN_GetDBStatus: home_dir = (/)
49c18940 Mon Aug 10 10:27:42 2015 :  RMAN_GetDBStatus: db is (A)
49c18940 Mon Aug 10 10:27:42 2015 :  Current Oracle user name (SYSBACKUP)
49c18940 Mon Aug 10 10:27:42 2015 : putenv(ORACLE_SID=<SID_NAME>)
49c18940 Mon Aug 10 10:27:42 2015 : putenv(ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1)
49c18940 Mon Aug 10 10:27:42 2015 : OCIServerAttach() Linux with dbname: <SID_NAME>
49c18940 Mon Aug 10 10:27:42 2015 : OCISessionBegin() with database credentials as sysbackup user.
49c18940 Mon Aug 10 10:27:42 2015 : OCISessionBegin() failed with database credentials.
49c18940 Mon Aug 10 10:27:42 2015 : OCI_ERROR: ORA-24300: bad value for mode

[VJware]

Are you using the actual SYSBACKUP user or another user which has the SYSBACKUP privilege ?

If the former, pls log a formal support case for an engineer to have a look @ your setup. Thanks.

[BE_user-nl]

Yes they have SYSbackup privileges.

I also notice that Backup Exec 2015 is very unstable on a CentOS 5 or 6 server, the agent crashes multiple times or is just unresponsive. Even so much that jobs get stuck on 12, 24 hours or even days without the Backup Exec server 2015 able to cancel them when they go out of their time window.

I presume your product is tested before coming in the consumer market? I cannot imagine that im the only one having this kind of problem.

If anyone can help me...

[pkh]

CentOS is never supported by any version of BE