Menu
- Cognos 11 Oracle Jdbc Connection
- Oracle 19c Jdbc Driver
- Oracle Jdbc Driver Class
- Cognos Oracle Jdbc Driver
- Cognos 11 Oracle Jdbc Driver
0
- The TAR archive contains the latest 11.2.0.4 JDBC Thin driver (ojdbc6.jar and ojdbc5.jar), Universal Connection Pool (ucp.jar), other companion jars, and README that has more information about the contents of the tar file.Unzipped JDBC Driver and Companion JARs. The JARs included in the ojdbc-full.tar.gz are also available as individual downloads in this section.
- I'm on a Windows 8 machine and attempting to connect IBM's COGNOS BI (I'm using the trial version - it's on the cloud) to MySQL, upon setting up the connection COGNOS always feed back. XQE-JDB-0004 A problem occurred finding the driver class 'com.mysql.jdbc.Driver'.
Failed to find or load the JDBC driver: tibcosoftwareinc.jdbc.oracle.OracleDriver'Please provide a solution to resolve this.Regards,VasanthHi,I am using BW 5.9. When I Tibco Oracle Driver Issue.
reset
I'm assuming you already have tra installed on your system. If so you should see another directory in <TIBCO_HOME>/tpcl/<VER>/jdbc
Verify that you have the appropriate jars(oracle) in this directory. I guess the error must be because you don't have them.
-Libu
0 Comments
+ Add a Comment0
reset
Hi Vasanth,
As of TRA 5.7 the TIBCO (DataDirect) drivers are no longer bundled with the product. They are still supported though and may be used with BW 5.9. If you have previous TRA version installed such as 5.6.x, you can copy the necessary drivers from the /tibco/tpcl/5.6/jdbc directory to tibco/tpcl/5.7/jdbc. Alternatively the method I prefer is to add the /tibco/tpcl/5.6/jdbc directory to the end of the ‘tibco.env.STD_EXT_CP’ property in your BW/5.9/bin/bwengine.tra.
If you don't have an earlier TRA version I believe you are out of luck.
Cognos 11 Oracle Jdbc Connection
I hope this helps!
Nochum
0 Comments
+ Add a Comment0
reset
Hi Vasanth,
Please keep the TIoracle.jar file in C:tibcotpcl5.5jdbc in this location.Mean while please check in designer.tra
C:tibcodesigner5.5bindesigner.tra. Check the tibco.env.STD_CP_EXT=TPCL_HOME%/jdbc.
Thanks
Sreekanth
0 Comments
+ Add a Comment0
Oracle 19c Jdbc Driver
reset
0
reset
Thanks Amit.
This is what I thought.
I'll see with tibco support to get those 'TIBCO DB Drivers 1.0.1'.
0 Comments
+ Add a Comment
| Oracle Database JDBC Java API Reference 11g Release 2 E13995-03 | ||||||||
All Classes | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
oracle.jdbc
Class OracleDriver
java.lang.Object
oracle.jdbc.driver.OracleDriver
oracle.jdbc.OracleDriver
- All Implemented Interfaces:
- java.sql.Driver
- extends oracle.jdbc.driver.OracleDriver
The Oracle JDBC driver class that implements the
java.sql.Driver
interface.To access a database from a Java application, you must first provide the code to register your installed driver with your program. You do this with the static
registerDriver()
method of the java.sql.DriverManager
class. This class provides a basic service for managing a set of JDBC drivers. The registerDriver()
method takes as input a 'driver' class, that is, a class that implements the java.sql.Driver
interface, as is the case with OracleDriver
.Note: Alternatively, you can use the
forName()
method of the java.lang.Class
class to load the JDBC drivers directly. For example: Class.forName ('oracle.jdbc.OracleDriver');
. However, this method is valid only for JDK-compliant Java virtual machines. It is not valid for Microsoft Java virtual machines.You register the driver only once in your Java application.
Once you have registered the driver, you can open a connection to the database with the static
getConnection()
method of the java.sql.DriverManager
class. The type of the object returned is java.sql.Connection
.Understanding the Forms of getConnection()
Specifying a Databse URL, User Name, and Password
The following signature takes the URL, user name, and password as separate parameters:
getConnection(String URL, String user, String password);
Where the URL is of the form:
jdbc:oracle:<drivertype>:@<database>
The following example connects user
scott
with password tiger
to a database with SID orcl
through port 1521 of host myhost
, using the Thin driver.Connection conn = DriverManager.getConnection
('jdbc:oracle:thin:@myhost:1521:orcl', 'scott', 'tiger');
Specifying a Databse URL That Includes User Name and Password
The following signature takes the URL, user name, and password all as part of a URL parameter:
getConnection(String URL);
Where the URL is of the form:
jdbc:oracle:<drivertype>:<user>/<password>@<database>
The following example connects user
scott
with password tiger
to a database on host myhost
using the OCI driver. In this case, however, the URL includes the userid and password, and is the only input parameter.Connection conn = DriverManager.getConnection
('jdbc:oracle:oci8:scott/tiger@myhost);
If you want to connect with the Thin driver, you must specify the port number and SID. For example, if you want to connect to the database on host
myhost
that has a TCP/IP listener up on port 1521, and the SID
(system identifier) is orcl
:Connection conn = DriverManager.getConnection
('jdbc:oracle:thin:scott/tiger@myhost:1521:orcl);
Specifying a Database URL and Properties Object
The following signature takes a URL, together with a properties object that specifies user name and password (perhaps among other things):
getConnection(String URL, Properties info);
Where the
URL
is of the form:jdbc:oracle:<drivertype>:@<database>
In addition to the URL, use an object of the standard Java
Properties
class as input. For example:java.util.Properties info = new java.util.Properties();
info.put ('user', 'scott');
info.put (
'password','tiger'
);info.put ('defaultRowPrefetch','15');
getConnection ('jdbc:oracle:oci8:@',info);
The table below lists the connection properties that Oracle JDBC drivers support.
Connection Properties Recognized by Oracle JDBC Drivers
Name | Short Name | Type | Description |
---|---|---|---|
user | n/a | String | the user name for logging into the database |
password | n/a | String | the password for logging into the database |
database | server | String | the connect string for the database |
internal_logon | n/a | String | a role, such as sysdba or sysoper , that allows you to log on as sys |
defaultRowPrefetch | prefetch | String (containing integer value) | the default number of rows to prefetch from the server (default value is '10') |
remarksReporting | remarks | String (containing boolean value) | 'true' if getTables() and getColumns() should report TABLE_REMARKS; equivalent to using setRemarksReporting() (default value is 'false') |
defaultBatchValue | batchvalue | String (containing integer value) | the default batch value that triggers an execution request (default value is '10') |
includeSynonyms | synonyms | String (containing boolean value) | 'true' to include column information from predefined 'synonym' SQL entities when you execute a DataBaseMetaData getColumns() call; equivalent to connection setIncludeSynonyms() call (default value is 'false') |
processEscapes | n/a | String (containing boolean value) | 'false' to disable escape processing for statements (Statement or PreparedStatement) created from this connection. Set this to 'false' if you want to avoid many calls to Statement.setEscapeProcessing(false); . This is espcially usefull for PreparedStatement where a call to setEscapeProcessing(false) would have no effect. The default is 'true'. |
defaultNChar | n/a | String (containing boolean value) | 'false' is the default. If set to 'true', the default behavior for handling character datatypes is changed so that NCHAR/NVARCHAR2 become the default. This means that setFormOfUse() won't be needed anymore when using NCHAR/NVARCHAR2. This can also be set as a java property :java -Doracle.jdbc.defaultNChar=true myApplication |
useFetchSizeWithLongColumn | n/a | String (containing boolean value) | 'false' is the default. THIS IS A THIN ONLY PROPERTY. IT SHOULD NOT BE USED WITH ANY OTHER DRIVERS. If set to 'true', the performance when retrieving data in a 'SELECT' will be improved but the default behavior for handling LONG columns will be changed to fetch multiple rows (prefetch size). It means that enough memory will be allocated to read this data. So if you want to use this property, make sure that the LONG columns you are retrieving are not too big or you may run out of memory. This property can also be set as a java property : java -Doracle.jdbc.useFetchSizeWithLongColumn=true myApplication |
SetFloatAndDoubleUseBinary | n/a | String (containing boolean value) | 'false' is the default. If set to 'true', causes the java.sql.PreparedStatment setFloat and setDouble API's to use internal binary format as for BINARY_FLOAT and BINARY_DOUBLE parameters. See oracle.jdbc.OraclePreparedStatement setBinaryFloat and setBinaryDouble |
Select your driver type : thin, oci, kprb...
Oralce provides four types of JDBC driver.
- Thin Driver, a 100% Java driver for client-side use without an Oracle installation, particularly with applets. The Thin driver type is
thin
. To connect userscott
with passwordtiger
to a database withSID
(system identifier)orcl
through port 1521 of hostmyhost
, using the Thin driver, you would write : - OCI Driver for client-side use with an Oracle client installation. The OCI driver type is
oci
. To connect userscott
with passwordtiger
to a database withSID
(system identifier)orcl
through port 1521 of hostmyhost
, using the OCI driver, you would write :Note that you can also specify the database by aTNSNAMES
entry. You can find the availableTNSNAMES
entries listed in the filetnsnames.ora
on the client computer from which you are connecting. For example, if you want to connect to the database on hostmyhost
as userscott
with passwordtiger
that has aTNSNAMES
entry ofMyHostString
, enter:If your JDBC client and Oracle server are running on the same machine, the OCI driver can use IPC (InterProcess Communication) to connect to the database instead of a network connection. An IPC connection is much faster than a network connection. - Server-Side Thin Driver, which is functionally the same as the client-side Thin driver, but is for code that runs inside an Oracle server and needs to access a remote server, including middle-tier scenarios. The Server-Side Thin driver type is
thin
and there is no difference in your code between using the Thin driver from a client application or from inside a server. - Server-Side Internal Driver for code that runs inside the target server, that is, inside the Oracle server that it must access. The Server-Side Internal driver type is
kprb
and it actually runs within a default session. You are already 'connected'. Therefore the connection should never be closed.
To access the default connection, write:You can also use the Oracle-specific defaultConnection() method of the OracleDriver class which is generally recommended:Note: You are no longer required to register theOracleDriver
class for connecting with the Server-Side Internal driver, although there is no harm in doing so. This is true whether you are usinggetConnection()
ordefaultConnection()
to make the connection.
Any user name or password you include in the URL string is ignored in connecting to the server default connection. TheDriverManager.getConnection()
method returns a new JavaConnection
object every time you call it. Note that although the method is not creating a new physical connection (only a single implicit connection is used), it is returning a new object.
Again, when JDBC code is running inside the target server, the connection is an implicit data channel, not an explicit connection instance as from a client. It should never be closed.
Field Summary | |
---|---|
static boolean | TRACE |
Fields inherited from class oracle.jdbc.driver.OracleDriver |
---|
access_string, accumulate_batch_result, batch_string, convert_nchar_literals_string, database_string, dataSizeBytes, dataSizeChars, dataSizeUnitsPropertyName, default_execute_batch_string, default_row_prefetch_string, defaultnchar_string, defaultncharprop_string, disable_defineColumnType_string, dll_string, execute_batch_string, fixed_string_string, include_synonyms_string, j2ee_compliance, jdbc_string, logon_as_internal_str, nls_lang_backdoor, no_caching_buffers, oracle_string, password_string, permit_timestamp_date_mismatch_string, prefetch_string, prelim_auth_string, process_escapes_string, protocol_string, protocolFullName_string, proxy_client_name, read_timeout, remarks_string, report_remarks_string, restrict_getTables_string, retain_v9_bind_behavior_string, row_prefetch_string, server_string, set_new_password_string, SetFloatAndDoubleUseBinary_string, StreamChunkSize_string, synonyms_string, systemTypeMap, tcp_no_delay, useFetchSizeWithLongColumn_prop_string, useFetchSizeWithLongColumn_string, user_string, v8compatible_string, xa_trans_loose |
Constructor Summary | |
---|---|
OracleDriver() |
Method Summary | |
---|---|
static java.lang.String | getBuildDate() Returns a String that specifies exactly when the jar file was built. |
static java.lang.String | getDriverVersion() Returns a String that specifies the Oracle version number of the driver. |
static java.lang.String | getJDBCVersion() Returns a String that specifies the version of the JDBC spec supporte by the driver. |
static boolean | isDebug() Returns true if this jar includes debug code. |
static boolean | isDMS() Returns true if this jar includes DMS instrumentaion. |
static boolean | isInServer() Returns true if this jar was built to run in the Oracle Java VM. |
static boolean | isJDK14() Deprecated. |
static boolean | isPrivateDebug() Returns true if this jar includes Oracle internal debug code. |
static void | main(java.lang.String[] args) Prints a description of the Oracle JDBC driver .jar file to System.out. |
Methods inherited from class oracle.jdbc.driver.OracleDriver |
---|
acceptsURL, connect, defaultConnection, getCompileTime, getMajorVersion, getMinorVersion, getPropertyInfo, getSystemPropertyFastConnectionFailover, jdbcCompliant, processSqlEscapes, registerMBeans |
Methods inherited from class java.lang.Object |
---|
equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Field Detail |
---|
TRACE
- See Also:
- Constant Field Values
Constructor Detail |
---|
OracleDriver
Method Detail |
---|
isDMS
- Returns true if this jar includes DMS instrumentaion.
- Returns:
- true if DMS jar
isInServer
- Returns true if this jar was built to run in the Oracle Java VM.
- Returns:
- true if server jar
isJDK14
![Driver Driver](/uploads/1/2/6/4/126477837/902759798.png)
- Deprecated.
- Returns true if this is a JDK 1.4 or later compliant jar. Since JDK 1.3 is desupported, always returns true.
- Returns:
- true
isDebug
- Returns true if this jar includes debug code.
- Returns:
- true if debug jar
isPrivateDebug
- Returns true if this jar includes Oracle internal debug code.
- Returns:
- true if private debug jar
getJDBCVersion
- Returns a String that specifies the version of the JDBC spec supporte by the driver.
- Returns:
- JDBC spec version
getDriverVersion
- Returns a String that specifies the Oracle version number of the driver.
- Returns:
- version number
getBuildDate
- Returns a String that specifies exactly when the jar file was built.
- Returns:
- build date
main
Oracle Jdbc Driver Class
- Prints a description of the Oracle JDBC driver .jar file to System.out.
- Parameters:
args
- Ignored- Throws:
java.lang.Exception
Cognos Oracle Jdbc Driver
| Oracle Database JDBC Java API Reference 11g Release 2 E13995-03 | ||||||||
All Classes | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |