v9 and Oracle

[Hauke]

Hello,

what do I need to configure on the Oracle side to backup it with veeam?
I'm always getting this error:

Code: Select all

13.01.2016 14:47:22 :: Failed to retrieve Oracle database (SID: P4J) settings required to perform archived logs backup. Oracle error has occurred. ORA-12557: TNS:protocol adapter not loadable

--tr:OracleSession: failed to init server.
--tr:Failed to create oracle session.
--tr:Failed to create oracle session holder. SID: P4J. 

I tried with different accounts, ORACLE_HOME and path variables are set correctly, I can use sqlplus, brbackup etc. without any issues.
Users are added to ora_dba group.

Oracle is version 12, Windows x64, SAP System.

Thanks,
Hauke

[Vitaliy S.]

Hi Hauke,

These are the only requirements I'm currently aware of. Can you please confirm that everything is configured correctly? If this is the case, then please open a support case and let us know your case ID.

Thanks!

[nielsengelen]

Did you try changing the Windows path order via SYSDM.CPL? I ran into this issue before and changed the following (other version but it should work for you as well):

From: D:\oracle\product\10.2.0\client_1\bin;D:\oracle\product\10.2.0\db_1\bin;
To: D:\oracle\product\10.2.0\db_1\bin;D:\oracle\product\10.2.0\client_1\bin;

Modify the path name to your installation dir ofcourse.

[Hauke]

After a reboot the warning changed to this:

Code: Select all

13.01.2016 20:25:52 :: Failed to retrieve Oracle database (SID: P4J) settings required to perform archived logs backup. Failed to create oracle session holder. Session is invalid.
--tr:Failed to create oracle session holder. SID: P4J. 

After changing the path variable to %oracle_home%\bin from user to system type the backup is now working.

[ReKoR]

I got this error on two of three Oracle VMs.

Code: Select all

14.01.2016 13:50:14 :: Failed to retrieve Oracle database (SID: xxxxx) settings required to perform archived logs backup. Failed to create OCI env. Code: -1
--tr:Failed to create oracle session.
--tr:Failed to create oracle session holder. SID: xxxxx.

In my case this error occured on these VMs which have Oracle Database and Oracle Middleware installed. I changed the path variable so the database bin path comes first. Now it's working fine. Thanks.

[ReKoR]

I've recognized that I get an error calling reports now. Let me explain it in detail. The specific VM has Oracle Database and Oracle Middleware with Forms & Reports installed. At default the Oracle Middleware paths come first, followed by the Oracle Database paths. I switched this order to fix the Veeam error. But now, we cannot call reports via URL anymore.

We get this error

REP-52266: Starten von In-Process-Reports Server rep_wls_reports_{SERVER_NAME}_asinst_1 nicht erfolgreich.oracle.reports.RWException: IDL:oracle/reports/RWException:1.0

This is the URL

http://{SERVER_NAME}.{DOMAIN_NAME}:9002/reports/rwservlet?report={COMPLETE_PATH_TO_REPORT.RDF}&userid={USER}/{PASSWORD}@{ORACLE_SID}&desformat=pdf&destype=cache&paramform=yes

If I switch the paths order back to default, calling reports is working fine but I get the Veeam error again.

Do you have some advice for me?

[foggy]

We haven't tested such configuration specifically, so need to investigate it closer. Thanks for the heads up.

[ReKoR]

Finally and with some help from an Oracle expert, we could fix the error.

The Oracle Report server uses the Windows paths per default. Through changing the paths to allow Veeam to successfully backup the Oracle data, Report server gets wrong paths. On a windows system there is a reports.bat who must be edited to use separate paths. The file is located at

Code: Select all

~\Middleware\asinst_1\config\reports\bin\reports.bat

You have to uncomment the following section. The paths behind should already be correct. But have a closer look.

Code: Select all

set REPORTS_CLASSPATH=...

Second thing we had to do, was changing some settings via Enterprise Manager.

Our Report server consists of two servers

• RbtSvr_{SERVER_NAME}_asinst_1
• reports(11.1.2) (WLS_REPORTS)

For both we changed
Minimal amount of engines from 1 to 0
Maximum amount of engines from 1 to 20


If anyone has similar problems, this might help you