UD Connect: Installation of JDBC Driver for Oracle

[Former Member]

Hello

Environment: SAP BW 3.5

Objective: Configure J2EE for UDI connect to Oracle

Question: What's the correct installation procedure

for the installation of the Oracle JDBC driver?

The white paper "how to...configure UD Connect on the

J2EE Server for JDBC Access to external databases" shows

how to add a JDBC driver to the resource adapter (example for SQL).

According to the installations instruction in OSS Note 509719 "Installation of Oracle JDBC-Drivers" there is

no registration mentioned by means of the Visual Administrator.

What is the exact installation procedure for the

Oracle JDBC-Driver-Installation?

Thanks for your help.

Regards

Chris Johner

[Former Member · Accepted solution]

Hi Christof,

I don't have any clue, what UD is, but if it uses the connector framework, note 773401 is really good.

Regards, Karsten

[Former Member · Accepted solution]

Hi Karsten

UD stands for Universal Data Connect and is a feature of BI (see also http://help.sap.com/saphelp_erp2004/helpdata/en/78/ef1441a509064abee6ffd6f38278fd/frameset.htm).

The problem is that the note doesn't say how

to register the JDBC driver with the visual administrator.

Regards

Christof

[Former Member · Accepted solution]

Hi Christof,

I had a look at the how-to-guide and it looks quite understandable for me. The only difference when you use an oracle driver is, that you add just one jar, the classes12.jar.

How to add a reference is described as well. (You can forget the note, it's a different approach there.)

Just one more question, on which database is your java stack running on? If it's an oracle db, you don't have to upload another oracle driver and just reference the system driver...

Regards, Karsten

[Former Member · Accepted solution]

Hi Karsten

Thanks for your input.

Yes it's a oracle database,

Thats actually a good hint about the system driver, but

what are the values that I have to enter in the

visual aedministrator according to

the "how to paper"?

My geuss is for the library reference: library:ORACLE.

But what are the values that I have to enter in the properties-tab for "managed connection factory" for

the field Driver-name and URL?

I think Driver-name is something like

"jdbc:oracle:@hostname:1521:SID" but what do

I have to enter for the URL field?

Regards

Christof

[Former Member · Accepted solution]

Now we've succeeded to establish a connection

to the database but it fails with the message "invalid username/password".

The URL value is

jdbc:oracle:thin:@<hostname>:1527,<username>,<password>

I tried different flavours like

jdbc:oracle:thin:@<hostname>:1527;<username>;<password>

jdbc:oracle:thin:@<hostname>:1527:<username>:<password>

jdbc:oracle:thin:@<hostname>:1527,"<username>","<password>"

but it doesn't work.

Does anybody know the syntax for the URL?

Thanks

Christof

[Former Member · Accepted solution]

Hi Christof,

for the reference, try library:core_lib or library:SYSTEM_DRIVER

DriverName is oracle.jdbc.driver.OracleDriver

URL is jdbc:oracle:<drivertype>:<user>/<password>@<database>

Example: jdbc:oracle:thin:scott/tiger@myhost:1521:orcl

Regards, Karsten

[Former Member · Accepted solution]

Hi Karsten,

thanks for your feedback.

I tried the URL jdbc:oracle:<drivertype>:<user>/<password>@<database> and it produces the same error: invalid/username.

However, when I put in a blank the fields

UserName (before with value "sa") and Password (before with value "admin") in the configuration properties of the VA, then the following error message below appears that seems to imply that the connect succeeded but the JDBC metadata cannot be read. What else can be wrong?

Thanks, Christof

*********************************************************

com.sap.ip.bi.sdk.exception.BIResourceException: Cannot access JDBC metadata at com.sap.ip.bi.sdk.dac.connector.jdbc.impl.JdbcMDRConnection.assertTablesLoaded(JdbcMDRConnection.java:465) at com.sap.ip.bi.sdk.dac.connector.relational.RelationalMDRConnection.getTable(RelationalMDRConnection.java:1279) at com.sap.ip.bi.sdk.dac.connector.relational.CommonConnection.getTable(CommonConnection.java:488) at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcRelational.getTable(JdbcRelational.java:229) at com.sap.ip.bi.sdk.trialarea.connector.servlet.TestJdbc630.service(TestJdbc630.java:69) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159) Caused by: java.sql.SQLException: ORA-00600: internal error code, arguments: [ttcgcshnd-1], [0], [], [], [], [], [], [] at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:169) at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208) at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543) at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1405) at oracle.jdbc.ttc7.TTC7Protocol.fetch(TTC7Protocol.java:889) at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:1826) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2015) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:395) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:339) at oracle.jdbc.OracleDatabaseMetaData.getTables(OracleDatabaseMetaData.java:2274) at com.sap.ip.bi.sdk.dac.connector.jdbc.impl.JdbcMDRConnection.assertTablesLoaded(JdbcMDRConnection.java:458) ... 21 more exception:Cannot access JDBC metadata

[Former Member · Accepted solution]

Oooh, now it's getting tough. Sorry, I can't help any further - I'm no BI expert.

Regards, Karsten

[Former Member]

Hi,

Can you please tell me where to get this jar file from.

and what guide do u use to UD connect the BI 7.0. I am struck and cant find the right guide any help will be apperciated.

Thanks

Ibrahim

[Former Member]

Chris,

I am also trying to configure UDI connection to Oracle in AV and have the same problem. What jar file did you use in the reference and what exactly did you use in the driver name?

Glenn

[Former Member]

Hello Christof,

Are you still having issues with UD Connect? I believe the user name and password should be entered as separate parameteres in the setup within Visual administrator. The whitepaper states that they are entered separately from JDBC URL.

[Former Member]

Yes, the problem is solved now:

the right URL is: jdbc:oracle:thin:@<hostname>:1527,<username>,<password>

The password and the user have to be entered in the VA in the separate fields. The last problem that has arised with ther eroor "com.sap.ip.bi.sdk.exception.BIResourceException: Cannot access JDBC metadata at " is due to a Oracle bug:

Oracle Metalink:

Bug 1725012 OERI:ttcgcshnd-1 using JDBC thin pre-9i to 9i database

When using pre-9i Jdbc-Thin to talk to a 9i (or post-9i)

database, you will see an ORA-600 exception on almost

everything you do. eg: ORA-600 [ttcgcshnd-1 ].

Workaround:

Set event="10841 trace name context forever"

in the init.ora file

After that the UDI connect finally worked, thanks!

Cheers

Christof