My Oracle database in my Dev environment was upgraded to 12c from 11g. It was not a seamless upgrade as far as Data Services (Version: 14.2.8.1354) was concerned. BOE and DS could not connect to the upgraded database server because Oracle 12c didn’t like the older 11g client. There is a fix you can do on the Oracle server side to work around that but I chose to upgrade the Oracle client software instead. The newer DS version may make these steps unnecessary but I wasn’t prepared to upgrade DS at this time.
Install full Oracle 12c client into directory C:\app\client\boptst. This is a different directory from the Oracle 11g client software.
Stop BOE and DS related services
[list] Apache Tomcat for BI 4
SAP Data Services
Server Intelligence Agent (VMWAS128)[/list]
Rename ojdbc6.jar files found in c:\program files (x86)\SAP Business Objects* to *.old
[list] C:\Program Files (x86)\SAP BusinessObjects\tomcat\webapps\DataServices\WEB-INF\lib
C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\DataServices\WEB-INF\lib
C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\lib\im\oracle
C:\Program Files (x86)\SAP BusinessObjects\Data Services\ext\lib[/list]
Open Command Prompt (as Administrator)
Place newer ojdbc6.jar and ojdbc7.jar files from Oracle web site into c:\temp
Copy newer ojdbc6.jar and ojdbc7.jar files from c:\temp into the same locations from step 3 above.
Copy TNSNames.ora file from Oracle 11g client install location (C:\app\BoPTST\product\11.2.0\client_1\network\admin) to Oracle 12c client install locations (C:\app\client\boptst\product\12.1.0\client_1\network\admin)
Restart BOE and DS related services in this order
[list] Server Intelligence Agent (VMWAS128)
Apache Tomcat for BI 4
SAP Data Services[/list]
Open the BOE Central Management Console and make sure all the Data Services repositories are “Active”.
From the Data Services Management Console, start ETL jobs as necessary.
eganjp 
(BOB member since 2007-09-12)