Free oracle jdbc driver software for linux

Oracle client is a simplistic Perl-based Oracle client that tries to mimic some of the functionality of PostgreSQL and MySQLs text-based SQL clients.

It is relatively simplistic, but much more useful than dbishell or sqlplus.

The project supports readline, history, desc, and various shorthand commands like d, , c, etc.

Clevo Mail LED Linux Driver operates the mail LED on the Clevo notebook model D4J.
Enhancements:
- The DMI_BOARD_VENDOR string has been corrected for D410V autodetection.

Oracle::CAPI is a Perl XS wrapper extension for the Oracle Collaboration Suite CAPI SDK.

SYNOPSIS

use Oracle::CAPI;
use Text::vCard;

Oracle::CAPI::SetConfigFile($CAPI_INI_FNAME,$CAPI_LOG_FNAME) && die("Cant init/log CAPI");
$capi_session = Oracle::CAPI::CreateSession() || die("Cant create CAPI session");

# Authenticate to OCS
$rv = Oracle::CAPI::ReconnectAuthUser($capi_session,$HOSTNAME,$nodeid,$pass,$uname);

$rv = Oracle::CAPI::FetchContactsFile($capi_session,$VCARD_NAME_TYPE,$VCARD_STARTSWITH_OP,$chr,$filename);
$rv = Oracle::CAPI::CreateContact($capi_session,$vcard);
$rv = Oracle::CAPI::DeleteContact($capi_session,$uid);

$rv = Oracle::CAPI::DestroyPerlSession($capi_session);

A perl XS wrapper to ctapi.h from the Oracle Collaboration Suite CAPI SDK. This was built and tested against OCS version 9.0.4.2 on Linux.

PowerDNS Oracle Backend provides a backend which allows PowerDNS to use Oracle as its data store.

PowerDNS Oracle Backend is a backend driver for the PowerDNS nameserver which allows DNS data to be stored in an Oracle database. PowerDNS can load backend modules at runtime. This backend is fully configurable, and SQL statements can be specified in the configuration file.

HDBC Sqlite3 Driver is the Haskell Sqlite v3 backend driver for HDBC.

Please see HDBC itself for documentation on use. If you dont already
have it, you can browse this documentation at
http://darcs.complete.org/hdbc/doc/index.html.

This package provides one function in module Database.HDBC.Sqlite3:

{- | Connect to an Sqlite version 3 database. The only parameter needed is
the filename of the database to connect to.

All database accessor functions are provided in the main HDBC module. -}
connectSqlite3 :: FilePath -> IO Connection

Oracle::Sqlldr is a Perl wrapper around Oracles sqlldr utility.
SYNOPSIS
use Oracle::Sqlldr;
my $sqlldr = Oracle::Sqlldr->new(); # get new sqlldr object
Oracle::Sqlldr is an object-oriented class that provides a convenient Perl wrapper around Oracles sqlldr utility.
SQL*Loader (sqlldr) is the utility to use for high performance data loading from a text file into a an Oracle database.
Version restrictions:
- No WIN32 support
- No fixed format record support
- Assumes table owner and user to load data as are the same
- No support for parameter file

GTK Oracle is a GTK+ 2 interface to Oracle that aids in Oracle application development and testing.
Its features include a schema browser, multiple SQL work areas, SQL syntax highlighting, bind variable entry widgets in the command window, and SQL*Plus-style command scripting.
For SQL statement analysis and tuning there is a tree-style SQL statement "explain plan" facility and the ability to load SQL statements from the runtime cursor cache (V$SQL table), Oracle Statspack repository, and the Oracle Automatic Workload Repository in Oracle version 10g. Full statistics are available on loaded statements.
Main features:
- manually running your applications SQL, outside of the application itself
- trying to find out what queries your application is even running
- checking and gathering statistics
- comparing plans
- running statspack to evaluate results
- autotracing
- peeking in AWR
- peeking the shared pool / v$sqlarea / statspack SQL
- identifying high-resource SQL then this might be of some help.
Usage:
- SQL in the text buffer (anything that gets run via the Execute button) is run on its own thread in the background so it will not block the GUI part, and you can cancel it. This execution thread is started when you start up the program, hopefully never exits, and receives commands via a GLib asynchronous queue, so you can safely keep hitting Execute while a command is running, it will just execute them in order.
- If you log in as SYSDBA you will get a combo box just under the main menubar. Changing the value will execute ALTER SESSION SET CURRENT_SCHEMA=somebody; so when you browse it will be as if you were this user. Be aware that any SQL you execute will result in SYS being recorded as the parsing user in the cursor cache, however.
- If you want to access the cursor cache or statspack or AWR you will need to log in with SYSDBA privileges. You might be able to get away with simply having SELECT on SYS.V$SQLAREA and SYS.V$SQLTEXT.
- SYS is excluded from the cursor cache browsing results. Otherwise you end up with a mass of recursive SQL, which you are not going to be able to tune and that is the point here. If youre a masochist and you do want to browse recursives I suppose you can just modify the relevant SQL so that SYS is not exculded and recompile. Have fun.
- AWR features are only available on 10G servers.
- DBMS_OUTPUT works, go to Edit->DBMS OUTPUT Enable

Need a Type 3 JDBC Driver for MS Access or SQL Server? Think RmiJdbc!
RmiJdbc project is a client/server JDBC Driver that relies on Java RMI.
All JDBC classes (like Connection, ResultSet, etc...) are distributed as RMI objects, so that you can distribute as you like the access to any database supporting the JDBC API.
In fact, RmiJdbc is just a bridge to allow remote access to JDBC drivers.
Why RmiJdbc?
- You develop a client/server application with databases on Windows (NT)? Use RmiJdbc along with the JDBC/ODBC Bridge, your Windows (NT) databases become remotely accessible in Java.
- You implement a JDBC Driver? Just implement the JDBC classes locally, dont bother with remote access!
- You need serializable JDBC classes? Here they are.
Enhancements:
- Add features/limitations/changes here