Where to load thin driver

where do you load the thin driver in a machine with oracle8 enterprise version and how do you call the driver in the program

You have to download Oracle's JDBC type 4 driver, or thin driver, for your specific machine. After installing it, on the client machine, you can access the API through Java's java.sql package. The documentation that comes with the driver is a great place to start.
I hope this helps you,
Mabel

Similar Messages

  • Steps to load Oracle JDBC Thin driver onto Tomcat

    I have Oracle JDBC working with thin driver on my local Tomcat container and now need to put it on a server but forgot how I set it up and want to make sure I do it correctly when I put it on the server.
    Please advise if this is correct?
    1- Load the thin driver (ojdbc14.jar ) in Tomcat 4.1.27 Container into the common/lib directory
    2- Set the classpath on the Windows server to allow me to use the ojdbc14.jar driver?
    If so then I need to do this using Windows DOS where I add the thin driver to my Classpath?
    Set CLASSPATH=%CLASSPATH%;C:\TomcatHome\common\lib\servlet-api.jar;C:\TomcatHome\common\lib\ojdbc14.jar
    Or do I NOT need to set the classpath and just restart the Tomcat container??

    Thanks,
    I loaded the ojdbc14.jar file in common/lib and restarted the container and I can now connect to Oracle.
    What you mean by not needing ojdbc14 for compilation and it would be better to use a build tool[b] to do what?

  • When I attempt to open iphoto, I get the loading icon in the working space/picture area.  If I try to reinstall ilife '11, will I lose any pictures?  Where, on the hard drive, are all my pictures actually stored?

    When I attempt to open iphoto, I get the loading icon in the working space/picture area.  If I try to reinstall ilife '11, will I lose any pictures?  Where, on the hard drive, are all my pictures actually stored?

    You won't lose anything because you have a back up, right?
    Most Simple Back Up
    Drag the iPhoto Library from your Pictures Folder to another Disk. This will make a copy on that disk.
    Slightly more complex:
    Use an app that will do incremental back ups. This is a very good way to work. The first time you run the back up the app will make a complete copy of the Library. Thereafter it will update the back up with the changes you have made. That makes subsequent back ups much faster. Many of these apps also have scheduling capabilities: So set it up and it will do the back up automatically. Examples of such apps: Chronosync or DejaVu . But are many others. Search on MacUpdate
    Option 1
    Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Rebuild iPhoto Library Database from automatic backup.
    If that fails:
    Option 2
    Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
    Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one. .
    Regards
    TD

  • Bug in Oracle JDBC thin driver (parameter order)

    [ I'd preferably send this to some Oracle support email but I
    can't find any on both www.oracle.com and www.technet.com. ]
    The following program illustrates bug I found in JDBC Oracle thin
    driver.
    * Synopsis:
    The parameters of prepared statement (I tested SELECT's and
    UPDATE's) are bound in the reverse order.
    If one do:
    PreparedStatement p = connection.prepareStatement(
    "SELECT field FROM table WHERE first = ? and second = ?");
    and then bind parameter 1 to "a" and parameter to "b":
    p.setString(1, "a");
    p.setString(2, "b");
    then executing p yields the same results as executing
    SELECT field FROM table WHERE first = "b" and second = "a"
    although it should be equivalent to
    SELECT field FROM table WHERE first = "a" and second = "b"
    The bug is present only in "thin" Oracle JDBC driver. Changing
    driver to "oci8" solves the problem.
    * Version and platform info:
    I detected the bug using Oracle 8.0.5 server for Linux.
    According to $ORACLE_HOME/jdbc/README.doc that is
    Oracle JDBC Drivers release 8.0.5.0.0 (Production Release)
    * The program below:
    The program below illustrates the bug by creating dummy two
    column table, inserting the row into it and then selecting
    the contents using prepared statement. Those operations
    are performed on both good (oci8) and bad (thin) connections,
    the results can be compared.
    You may need to change SID, listener port and account data
    in getConnecton calls.
    Sample program output:
    $ javac ShowBug.java; java ShowBug
    Output for both connections should be the same
    --------------- thin Driver ---------------
    [ Non parametrized query: ]
    aaa
    [ The same - parametrized (should give one row): ]
    [ The same - with buggy reversed order (should give no answers):
    aaa
    --------------- oci8 driver ---------------
    [ Non parametrized query: ]
    aaa
    [ The same - parametrized (should give one row): ]
    aaa
    [ The same - with buggy reversed order (should give no answers):
    --------------- The end ---------------
    * The program itself
    import java.sql.*;
    class ShowBug
    public static void main (String args [])
    throws SQLException
    // Load the Oracle JDBC driver
    DriverManager.registerDriver(new
    oracle.jdbc.driver.OracleDriver());
    System.out.println("Output for both connections should be the
    same");
    Connection buggyConnection
    = DriverManager.getConnection
    ("jdbc:oracle:thin:@localhost:1521:ORACLE",
    "scott", "tiger");
    process("thin Driver", buggyConnection);
    Connection goodConnection
    = DriverManager.getConnection ("jdbc:oracle:oci8:",
    "scott", "tiger");
    process("oci8 driver", goodConnection);
    System.out.println("--------------- The end ---------------");
    public static void process(String title, Connection conn)
    throws SQLException
    System.out.println("--------------- " + title + "
    Statement stmt = conn.createStatement ();
    stmt.execute(
    "CREATE TABLE bug (id VARCHAR(10), val VARCHAR(10))");
    stmt.executeUpdate(
    "INSERT INTO bug VALUES('aaa', 'bbb')");
    System.out.println("[ Non parametrized query: ]");
    ResultSet rset = stmt.executeQuery(
    "select id from bug where id = 'aaa' and val = 'bbb'");
    while (rset.next ())
    System.out.println (rset.getString (1));
    System.out.println("[ The same - parametrized (should give one
    row): ]");
    PreparedStatement prep = conn.prepareStatement(
    "select id from bug where id = ? and val = ?");
    prep.setString(1, "aaa");
    prep.setString(2, "bbb");
    rset = prep.executeQuery();
    while (rset.next ())
    System.out.println (rset.getString (1));
    System.out.println("[ The same - with buggy reversed order
    (should give no answers): ]");
    prep = conn.prepareStatement(
    "select id from bug where id = ? and val = ?");
    prep.setString(1, "bbb");
    prep.setString(2, "aaa");
    rset = prep.executeQuery();
    while (rset.next ())
    System.out.println (rset.getString (1));
    stmt.execute("DROP TABLE bug");
    null

    Horea
    In the ejb-jar.xml, in the method a cursor is closed, set <trans-attribute>
    to "Never".
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name></ejb-name>
    <method-name></method-name>
    </method>
    <trans-attribute>Never</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    Deepak
    Horea Raducan wrote:
    Is there a known bug in Oracle JDBC thin driver version 8.1.6 that would
    prevent it from closing the open cursors ?
    Thank you,
    Horea

  • Can't create connection pool using weblogic 6.1 with Oracle thin driver

    Hi !
    I have tried to create a connection pool from adminconsole. My CLASSPATH setting
    is as follows :
    F:\SOAP\soap-2_2\lib;F:\SOAP\soap-2_2;
    D:\Oracle\Ora81\jdbc\lib\classes12.zip;
    D:\Oracle\Ora81\jdbc\lib\nls_charset12.zip;
    D:\Oracle\Ora81\jdbc\lib\classes111.zip;
    F:\SOAP\soap-2_2\lib\jaf-1.0.1\activation.jar;
    D:\Oracle\Ora8\Apache\Jsdk\src\javax\servlet\http;
    D:\Oracle\Ora81\Apache\Jsdk\src\javax\servlet;
    D:\Oracle\Ora81\lib;
    F:\ant\jakarta-ant1.\bin;
    E:\weblogic\oci\classes;
    E:\weblogic\oci\classes\weblogic\xml\license;
    E:\weblogic\oci\license;
    E:\bea\wlserver6.1\lib;
    E:\PetStoreHome\petstore1.3;
    Following is the configuration.
    #Oracle thin driver Method #2
    weblogic.jdbc.connectionPool.thin=\      
    url=jdbc:oracle:thin:@test:1521:PROJECT,\      
    driver=oracle.jdbc.driver.OracleDriver,\
         initialCapacity=4,\
         maxCapacity=10,\
         capacityIncrement=1,\
         props=user=xxx;password=xxx;server=test
    #Add a TXDataSource for the connection pool:
    weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.thin=thin
    # Add an ACL for the connection pool:
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.thin=everyone
    I did append the file weblogic.properties with the above config. Now when I start
    the Weblogic server I get the following error :
    Starting WebLogic Server ....
    <Nov 29, 2001 2:24:16 PM EST> <Notice> <Management> <Loading configuration file
    .\config\petstore\config.xml ...>
    <Nov 29, 2001 2:24:22 PM EST> <Notice> <WebLogicServer> <Starting WebLogic Admin
    Server "petstoreServer" for domain "petstore">
    <Nov 29, 2001 2:24:26 PM EST> <Notice> <Management> <Starting discovery of Manag
    ed Server... This feature is on by default, you may turn this off by passing -Dw
    eblogic.management.discover=false>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
    weblogic.common.ResourceException: DataSource(jdbcthin.SignOnDB) can't be creat
    ed with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
    weblogic.common.ResourceException: DataSource(jdbcthin.EstoreDB) can't be creat
    ed with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
    weblogic.common.ResourceException: DataSource(jdbcthin.InventoryDB) can't be
    cr
    eated with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data Source creation:
    weblogic.common.ResourceException: DataSource(weblogic.jdbc.jts.thin) can't be
    created with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:41 PM EST> <Notice> <Management> <Application Poller not star
    ted for production server.>
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    After the server has booted, your browser should
    automatically launch and point to the WebLogic Server
    Tour running on this server. If your browser fails to
    launch, point your browser to the URL
    "http://burtsun:7001"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    <Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <ListenThread listening
    on port 7001>
    <Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <SSLListenThread listeni
    ng on port 7002>
    <Nov 29, 2001 2:24:42 PM EST> <Notice> <WebLogicServer> <Started WebLogic Admin
    Server "petstoreServer" for domain "petstore" running in Production Mode>
    Could anyone please help me ?
    Thanks
    ..Madhuri

    Madhuri wrote:
    >
    Hi Joe !
    I didn't get what you would like to point out. Actully, I am using same config.,
    but not to disclose the info. I gave you @test and username/password xxx/xxx.Ok. Now, assuming your pool looks like what I showed, the issue is probably
    that there are multiple Oracle driver zips around, and your standlaone program
    is using a different, newer, better one than the server. Our weblogic jar files
    include a classes12.zip Oracle thin driver, but there are multiple versions of
    classes12.zip, and the latest from oracle is better than the one we sealed into
    our packaging. Please use jave -verbose to identify exactly which Oracle sip file
    you are using in the successful case, then make sure this zip file comes before
    any weblogic stuff in your weblogic server's classpath, so we'll use the same
    driver. This should work. Edit the script you sue to start weblogic to verify
    the classpath does end up with the oracle driver ahead of all weblogic stuff.
    Joe
    >
    Please let me know.
    Thanks
    .Madhuri
    Joseph Weinstein <[email protected]> wrote:
    Madhuri wrote:
    Hi Joe !
    Here is the sample java code. Please let me know how I can test thisin weblogic
    6.1.
    Thanks
    .MadhuriWell fine! That was easy. Your pool definition didn't have the same URL
    or
    user or password as this code. Try this for your pool definition:
    weblogic.jdbc.connectionPool.thin=\
    url=jdbc:oracle:thin:@adl-gbsdevel:1521:PROJECT,\
    driver=oracle.jdbc.driver.OracleDriver,\
    initialCapacity=10,\
    maxCapacity=10,\
    capacityIncrement=1,\
    testConnsOnReserve=true,\
    testTable=dual,\
    props=user=mkelkar;password=mkelkar
    Let me know,,,
    Joe
    Joseph Weinstein <[email protected]> wrote:
    The key is in the log:
    Could not create pool connection.
    The DBMS driver exception was:
    java.sql.SQLException: invalid arguments in call
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
    Now we need to simplify the problem. Please make a simple 15-line
    standalone
    Java program like you'd find with the Oracle driver's examples, with
    no
    weblogic code in the picture. Just make a JDBC connection using Oracle's
    driver, and show me that code. Then I can translate that into a pool
    definition.
    Joe
    Madhuri wrote:
    Hi Joe !
    Thanks for your prompt reply. I tried the way you suggested but
    it
    still it gives
    me the same error. I am attching here the weblogic.log file.
    Thanks again
    ..Madhuri
    Joseph Weinstein <[email protected]> wrote:
    We'd want to see the log during booting, where the pool
    is being created to see why that failed. Try a pool
    definition with no blank lines, no whitespace at the
    end of lines, and no server property. The thin driver
    doesn't like that:
    weblogic.jdbc.connectionPool.thin=\
    url=jdbc:oracle:thin:@test:1521:PROJECT,\
    driver=oracle.jdbc.driver.OracleDriver,\
    initialCapacity=4,\
    maxCapacity=10,\
    capacityIncrement=1,\
    props=user=xxx;password=xxx
    Joe
    Madhuri wrote:
    Hi !
    I have tried to create a connection pool from adminconsole. My
    CLASSPATH
    setting
    is as follows :
    F:\SOAP\soap-2_2\lib;F:\SOAP\soap-2_2;
    D:\Oracle\Ora81\jdbc\lib\classes12.zip;
    D:\Oracle\Ora81\jdbc\lib\nls_charset12.zip;
    D:\Oracle\Ora81\jdbc\lib\classes111.zip;
    F:\SOAP\soap-2_2\lib\jaf-1.0.1\activation.jar;
    D:\Oracle\Ora8\Apache\Jsdk\src\javax\servlet\http;
    D:\Oracle\Ora81\Apache\Jsdk\src\javax\servlet;
    D:\Oracle\Ora81\lib;
    F:\ant\jakarta-ant1.\bin;
    E:\weblogic\oci\classes;
    E:\weblogic\oci\classes\weblogic\xml\license;
    E:\weblogic\oci\license;
    E:\bea\wlserver6.1\lib;
    E:\PetStoreHome\petstore1.3;
    Following is the configuration.
    #Oracle thin driver Method #2
    weblogic.jdbc.connectionPool.thin=\
    url=jdbc:oracle:thin:@test:1521:PROJECT,\
    driver=oracle.jdbc.driver.OracleDriver,\
    initialCapacity=4,\
    maxCapacity=10,\
    capacityIncrement=1,\
    props=user=xxx;password=xxx;server=test
    #Add a TXDataSource for the connection pool:
    weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.thin=thin
    # Add an ACL for the connection pool:
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.thin=everyone
    I did append the file weblogic.properties with the above config.
    Now
    when I start
    the Weblogic server I get the following error :
    Starting WebLogic Server ....
    <Nov 29, 2001 2:24:16 PM EST> <Notice> <Management> <Loading
    configuration
    file
    \config\petstore\config.xml ...>
    <Nov 29, 2001 2:24:22 PM EST> <Notice> <WebLogicServer> <Starting
    WebLogic
    Admin
    Server "petstoreServer" for domain "petstore">
    <Nov 29, 2001 2:24:26 PM EST> <Notice> <Management> <Starting
    discovery
    of Manag
    ed Server... This feature is on by default, you may turn this
    off
    by
    passing -Dw
    eblogic.management.discover=false>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
    Source
    creation:
    weblogic.common.ResourceException: DataSource(jdbcthin.SignOnDB)
    can't
    be creat
    ed with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
    Source
    creation:
    weblogic.common.ResourceException: DataSource(jdbcthin.EstoreDB)
    can't
    be creat
    ed with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
    Source
    creation:
    weblogic.common.ResourceException: DataSource(jdbcthin.InventoryDB)can't be
    cr
    eated with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:35 PM EST> <Error> <JDBC> <Error during Data
    Source
    creation:
    weblogic.common.ResourceException: DataSource(weblogic.jdbc.jts.thin)can't be
    created with non-existent Pool (connection or multi) (thin)>
    <Nov 29, 2001 2:24:41 PM EST> <Notice> <Management> <Application
    Poller
    not star
    ted for production server.>
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    After the server has booted, your browser should
    automatically launch and point to the WebLogic Server
    Tour running on this server. If your browser fails to
    launch, point your browser to the URL
    "http://burtsun:7001"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    <Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <ListenThreadlistening
    on port 7001>
    <Nov 29, 2001 2:24:41 PM EST> <Notice> <WebLogicServer> <SSLListenThreadlisteni
    ng on port 7002>
    <Nov 29, 2001 2:24:42 PM EST> <Notice> <WebLogicServer> <Started
    WebLogic
    Admin
    Server "petstoreServer" for domain "petstore" running in ProductionMode>
    Could anyone please help me ?
    Thanks
    ..Madhuri
    Name: weblogic.log
    weblogic.log Type: Text Document (application/x-unknown-content-type-txtfile)
    Encoding: base64
    Name: PrintColumns.java
    PrintColumns.java Type: Visual Cafe File (application/x-unknown-content-type-VisualCafeFile.Document)
    Encoding: base64

  • Oracle JDBC Thin Driver

    I am using CLOBS with the Oracle thin driver and am experiencing horrible performance. We need datavalues more than a VARCHAR2 and have used CLOB but the method Oracle uses to get the data in and out is super slow.
    MS SQL Server JDBC with text is awesome and fast. But Oracle is slow and very cumbersome.
    Help

    We are using 9.0.2.
    So what you are saying is although the column is CLOB
    in Oracle 10 g we can use a normal result set
    rset.getString( 1 ) no special oracle stuff just the
    e Oracle thin driver for 10g?
    Also this will retrieve a String greater than 4000
    bytes?Exactly. Not only you can retieve a clob as string, you can also insert clob
    as a string too. Here is the code I referred in last post in case you do not
    have access to oracle ten network:
    * @author Savitha
    * @version 1.0
    * Development Environment : Oracle JDeveloper 10g
    * Name of the Application : ClobManipulationIn10g.java
    * Creation/Modification History :
    * Savitha 17-Mar-2004 Created.
    package oracle.otnsamples.jdbc;
    // Java SQL classes
    import java.sql.Connection;
    import java.sql.DriverManager;
    import java.sql.Statement;
    import java.sql.PreparedStatement;
    import java.sql.ResultSet;
    import java.sql.SQLException;
    // Oracle JDBC driver class
    import oracle.jdbc.OracleDriver;
    // Java IO classes
    import java.io.IOException;
    import java.io.BufferedReader;
    import java.io.FileNotFoundException;
    import java.io.FileReader;
    //Java Util classes
    import java.util.Properties;
    * This class demonstrates the Oracle JDBC 10g enhanced features for inserting
    * and retrieving CLOB data from the database. Using the new features, large
    * data of more than 32765 bytes can be inserted into the database using the
    * existing PreparedStatement.setString() and PreparedStatement.getString()
    * methods.
    public class ClobManipulationIn10g {
    /* Database Connection object */
    private Connection conn = null;
    /* Variables to hold database details */
    private String url = null;
    private String user = null;
    private String password = null;
    // Create a property object to hold the username, password and
    // the new property SetBigStringTryClob.
    private Properties props = new Properties();
    /* String to hold file name */
    private String fileName = null;
    * Default Constructor to instantiate and get a handle to class methods
    * and variables.
    public ClobManipulationIn10g(String fileName) {
    this.fileName = fileName;
    * Main runnable class.
    public static void main(String[] args) throws SQLException {
    // Instantiate the main class.
    ClobManipulationIn10g clobManipulationIn10g =
    new ClobManipulationIn10g(args[0]);
    // Load the Oracle JDBC driver class.
    DriverManager.registerDriver(new OracleDriver());
    // Load the database details into the variables.
    String dbUrl = "jdbc:oracle:thin:@<database host machine>:<port>:<SID>";
    clobManipulationIn10g.url = dbUrl;
    // Replace the username where the table 'clob_tab' was created.
    clobManipulationIn10g.user = "scott";
    // Replace the password of the username.
    clobManipulationIn10g.password = "tiger";
    // Populate the property object to hold the username, password and
    // the new property 'SetBigStringTryClob' which is set to true. Setting
    // this property allows inserting of large data using the existing
    // setString() method, to a CLOB column in the database.
    clobManipulationIn10g.props.put("user", clobManipulationIn10g.user );
    clobManipulationIn10g.props.put("password", clobManipulationIn10g.password);
    clobManipulationIn10g.props.put("SetBigStringTryClob", "true");
    // Check if the table 'CLOB_TAB' is present in the database.
    clobManipulationIn10g.checkTables();
    // Call the methods to insert and select CLOB from the database.
    clobManipulationIn10g.insertClob();
    clobManipulationIn10g.selectClob();
    * This method will insert the data into a CLOB column in the database.
    * Oracle JDBC 10g has enhanced the existing PreparedStatement.setString()
    * method for setting the data more than 32765 bytes. So, using setString(),
    * it is now easy to insert CLOB data into the database directly.
    private void insertClob() throws SQLException {
    // Create a PreparedStatement object.
    PreparedStatement pstmt = null;
    try {
    // Create the database connection, if it is closed.
    if ((conn==null)||conn.isClosed()){
    // Connect to the database.
    conn = DriverManager.getConnection( this.url, this.props );
    // Create SQL query to insert data into the CLOB column in the database.
    String sql = "INSERT INTO clob_tab VALUES(?)";
    // Read a big file(larger than 32765 bytes)
    String str = this.readFile();
    // Create the OraclePreparedStatement object
    pstmt = conn.prepareStatement(sql);
    // Use the same setString() method which is enhanced to insert
    // the CLOB data. The string data is automatically transformed into a
    // clob and inserted into the database column. Make sure that the
    // Connection property - 'SetBigStringTryClob' is set to true for
    // the insert to happen.
    pstmt.setString(1,str);
    // Execute the PreparedStatement
    pstmt.executeUpdate();
    } catch (SQLException sqlex) {
    // Catch Exceptions and display messages accordingly.
    System.out.println("SQLException while connecting and inserting into " +
    "the database table: " + sqlex.toString());
    } catch (Exception ex) {
    System.out.println("Exception while connecting and inserting into the" +
    " database table: " + ex.toString());
    } finally {
    // Close the Statement and the connection objects.
    if (pstmt!=null) pstmt.close();
    if (conn!=null) conn.close();
    * This method reads the CLOB data from the database by using getString()
    * method.
    private void selectClob() throws SQLException {
    // Create a PreparedStatement object
    PreparedStatement pstmt = null;
    // Create a ResultSet to hold the records retrieved.
    ResultSet rset = null;
    try {
    // Create the database connection, if it is closed.
    if ((conn==null)||conn.isClosed()){
    // Connect to the database.
    conn = DriverManager.getConnection( this.url, this.props );
    // Create SQL query statement to retrieve records having CLOB data from
    // the database.
    String sqlCall = "SELECT clob_col FROM clob_tab";
    pstmt= conn.prepareStatement(sqlCall);
    // Execute the PrepareStatement
    rset = pstmt.executeQuery();
    String clobVal = null;
    // Get the CLOB value from the resultset
    while (rset.next()) {
    clobVal = rset.getString(1);
    System.out.println("CLOB length: "+clobVal.length());
    } catch (SQLException sqlex) {
    // Catch Exceptions and display messages accordingly.
    System.out.println("SQLException while connecting and querying the " +
    "database table: " + sqlex.toString());
    } catch (Exception ex) {
    System.out.println("Exception while connecting and querying the " +
    "database table: " + ex.toString());
    } finally {
    // Close the resultset, statement and the connection objects.
    if (rset !=null) rset.close();
    if (pstmt!=null) pstmt.close();
    if (conn!=null) conn.close();
    * Method to check if the table ('CLOB_TAB') exists in the database; if not
    * then it is created.
    * Table Name: CLOB_TAB
    * Column Name Type
    * col_col CLOB
    private void checkTables() {
    Statement stmt = null;
    ResultSet rset = null;
    try {
    // Create the database connection, if it is closed.
    if ((conn==null)||conn.isClosed()){
    // Connect to the database.
    conn = DriverManager.getConnection( this.url, this.props );
    // Create Statement object
    stmt = conn.createStatement();
    // Check if the table is present
    rset = stmt.executeQuery(" SELECT table_name FROM user_tables "+
    " WHERE table_name = 'CLOB_TAB' ");
    // If the table is not present, then create the table.
    if (!rset.next()) {
    // Table does not exist, create it
    stmt.executeUpdate(" CREATE TABLE clob_tab(clob_col CLOB)");
    } catch (SQLException sqlEx) {
    System.out.println("Could not create table clob_tab : "
    +sqlEx.toString());
    } finally {
    try {
    if( rset != null ) rset.close();
    if( stmt != null ) stmt.close();
    if (conn!=null) conn.close();
    } catch(SQLException ex) {
    System.out.println("Could not close objects in checkTables method : "
    +ex.toString());
    * This method reads the specified text file and, returns the content
    * as a string.
    private String readFile()
    throws FileNotFoundException, IOException{
    // Read the file whose content has to be passed as String
    BufferedReader br = new BufferedReader(new FileReader(fileName));
    String nextLine = "";
    StringBuffer sb = new StringBuffer();
    while ((nextLine = br.readLine()) != null) {
    sb.append(nextLine);
    // Convert the content into to a string
    String clobData = sb.toString();
    // Return the data.
    return clobData;
    }

  • Load JDBC driver class 'null'

    hi all :)
    i'm using a datasource (tomcat 4.1.18 with jdk 1.4)
    i'm the following error :
    java.sql.SQLException: Cannot load JDBC driver class 'null'my classes12.jar find in $CATALINA_HOME/common/lib
    where is ma error ?
    thanks a lot.

    GlobalNamingResources?
    I sent up a data source for each app, like this:
    <Context    path="/api-prototype"
                docBase="api-prototype.war"
                debug="1"
                reloadable="true"
                crossContext="true"
                useNaming="true">
        <Logger className="org.apache.catalina.logger.FileLogger"
                prefix="localhost-api-prototype-log."
                suffix=".txt"
                timestamp="true"/>
        <Resource   name="jdbc/APIPrototype"
                    auth="Container"
                    type="javax.sql.DataSource"/>
    <!-- Oracle 9.2.0.1 data source -->
        <ResourceParams name="jdbc/APIPrototype">
            <parameter>
                <name>factory</name>
                <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
            </parameter>
            <parameter>
                <name>driverClassName</name>
                <value>oracle.jdbc.driver.OracleDriver</value>
            </parameter>
            <parameter>
                <name>url</name>
                <value>jdbc:oracle:thin:@elvis:1521:CAPP</value>
            </parameter>
            <parameter>
                <name>username</name>
                <value>api</value>
            </parameter>
            <parameter>
                <name>password</name>
                <value>mod</value>
            </parameter>
            <parameter>
                <name>maxActive</name>
                <value>20</value>
            </parameter>
            <parameter>
                <name>maxIdle</name>
                <value>0</value>
            </parameter>
            <parameter>
                <name>maxWait</name>
                <value>60000</value>
            </parameter>
            <parameter>
                <name>removeAbandoned</name>
                <value>true</value>
            </parameter>
            <parameter>
                <name>removeAbandonedTimeout</name>
                <value>300</value>
            </parameter>
        </ResourceParams>
    </Context>This works fine on Tomcat 4.1.24. I don't know where you got that example from, but I'd recommend that you look at the Tomcat JNDI How-to:
    http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html
    Why go anywhere else? - MOD

  • How to Install JDBC Thin Driver

    Hi all,
    I will connect to a RDBMS the first time and do not know how to do that.
    I need to install JDBC Driver and use but how would i install it? There is a ojdbc14_g.jar file when i search on google i downloaded it but where should i locate it to
    see it from Eclipse(Spring Source Tool indeed).
    I went to preferences -> data management -> driver definitions in Eclipse when i select ORACLE Thin Driver it says the jar file above is not found in the file system.
    Thanks all...
    Edited by: user9371286 on 06-Aug-2010 00:16

    Installing a jdbc driver is as easy as downloading it and putting it in your classpath. The prereqs are getting the correct jar for your version of Oracle and having a database to connect to. This is a good place to start for JDBC related questions:
    http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.html
    And here is a little demo to load and run a Java class in eclipse:
    http://www.oracledepot.com/demos/2010-08-06_JdbcTest.swf

  • P-R-O-B-L-E-M with JDBC thin driver

    Thank you gmagana!
    I did not manage to make this code connect to Oracle at all:
    import java.sql.*;
    public class jdbcThin {
    public static void connect() {
              String     url = "jdbc:oracle:thin:uName/passW@myDatabase:1521:orcl";
              try {
                        Class.forName ("oracle.jdbc.driver.OracleDriver");
                   Connection conn = DriverManager.getConnection( url );
                   System.out.println ("The Oracle thin driver loaded!");
              catch (ClassNotFoundException e) {
                   System.out.println ("Did not load driver.");
                   e.printStackTrace ();
              catch (SQLException e) {
                   System.out.println ("Did not load driver.");
                   e.printStackTrace ();
    public static void main( String args[] ) {
              connect();
    // Do "statement" stuff after I successfully connect to Oracle.
    My setup:
    1. jdbcThin.class in located in: ~/runMe/jdbcThin.class
    2. Unextracted classes12.zip in: ~/runMe/classes12.zip
    3. Java Runtime: ~/runMe/bin or
    ~/runMe/jre/bin
    Command line:
    %~/runMe> java jdbcThin
    Message:
    Did not load driver.
    java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver
    at jdbcThin.connect(Compiled Code)
    at jdbcThin.main(Compiled Code)
    %~/runMe>
    Tried running it with classpath re-direction:
    %~/runMe> java -classpath /runMe classes12.zip.jdbcThin
    Message:
    zip.jdbcThin
    Can't find class classes12.zip.jdbcThin
    %~/runMe>
    I am not permitted to change anything in .cshrc or .profile where
    I could use/> setenv classpath path1:path2: ~etc.
    Oh, JAVA gods(!) I am stuck. <quite pissed> :(
    ...and what am I doing wrongly with JDBC thin?!
    H E L P !!!!!!!!!!!!!!!!!!!

    Thanks Shirish! (Symmetrical WRT sound!)
    Here is my adaptation of that snippet which compiles, except for one error:
    Class OracleDriver not found. How did you handled your classes12.zip and
    your class path? Exactly what should happen at the command line?!
    That is really my BIGGEST issue with these vendor drivers outside JDK.
    I am aware that many styles work, but given the EXACTLY correct environment
    setting. This is my main issue and why I specified my exact directories.
    1. If Oracle is in: ~ root/Oracle
    2. Thin driver in: ~ root/drivers/classes12.zip
    3. My connection code in: ~root/sources/connDB.class
    What EXACTLY should happen to compile and run:
    import java.sql.*;
    public class connDB {
    public static void connect() {
              Connection     conn;
              Statement     stmt;
              ResultSet          rtset;
              String          SQL;
              try {
    DriverManager.registerDriver(new OracleDriver());
    conn = DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:" + instance, username, password);
    stmt = conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE);
    rtset = stmt.executeQuery(SQL);
    catch( SQLException sqle ) {
                   System.out.println ("Did not load driver.");
                   sqle.printStackTrace ();
    public static void main( String args[] ) {
              connect();
    I am sitting @~root/sources>
    So far I have no problem running any non-driver associated classes from there.
    But how do I make my code find this OracleDriver?! And should classes12.zip
    be extracted? I was told it should remain intact. Point is where should it be
    or what command line "command" gets this connDB.class + OracleDriver to run?

  • Testing connection with Oracle thin driver

    Hi !
    I am testing Oracle connection from dos prompt and I get the SQL Error SQLEXCEPTION.
    How do I connect Petstore to Oracle database? When I test the connection I get error message that java.sql.SQLException No License: weblogic.comon.LicenseNotFoundException. The file is in weblogic home directory.

    Hi Sree !
    Thanks !
    After I ran the SetEnv.cmd, this is working and I guess I am ok now to use this
    connection pool.
    Thank you very much.
    .Madhuri
    "Sree Bodapati" <[email protected]> wrote:
    can you point me to the doc which talks about the valid DBTYPE values
    (url)?
    java utils.dbping ORACLE_THIN scott tiger
    <machineip_or_name>:1521:<tns_alias >
    this should work fine. for out of box usage, just goto the the folder
    <wl_home>/config/mydomain and execute setenv.cmd / setenv.sh then execute
    the above command from the same shell.
    This command is not testing connection pool. its making sure that you
    can
    connect to the db and it will not take you into sqlplus, it will show
    you
    multiple ways to code your connections to the database.
    sree
    "Madhuri" <[email protected]> wrote in message
    news:[email protected]...
    Hi Sree !
    Thanks for your prompt reply. I have tried your solution but stillI am
    having
    problem and I don't find more info. about this on Bea site. Pleasesee
    following
    E:\bea\wlserver6.1>java utils.dbping ORACLE_THIN <username> <password>host:port:database
    name
    Valid DBTYPE values:
    ORACLE, ORACLE_JDBC20, INFORMIX4, [JCONNECT | SYBASE], MSSQLSERVER4
    Where I should have to use dbtype, is there something missing in command?
    Please let me know.
    After the connection pool test is successful, it should take me toSQLPLUS, am
    I right? What message I should be expecting?
    Thanks
    ..Madhuri
    "Sree Bodapati" <[email protected]> wrote:
    The license file for WLS6.1 is license.bea file that is normally in
    the
    BEA_HOME folder.
    Usage for utils.dbping:
    Usage: java utils.dbping ORACLE USER PASS DBNAME
    or java utils.dbping ORACLE_THIN USER PASS HOST:PORT:DBNAME
    or java utils.dbping JCONNECT USER PASS HOST:PORT/DBNAME
    or java utils.dbping INFORMIX4 USER PASS DBNAME@HOST:PORT
    or java utils.dbping MSSQLSERVER4 USER PASS DBNAME@HOST:PORT
    Try to use the second one and it should work. What you were usingwas
    the
    dbping for OCI driver.
    sree
    "Madhuri" <[email protected]> wrote in message
    news:[email protected]...
    Hi Sree !
    I tried this but still I get an error. Please see the following
    E:\bea\wlserver6.1>java -classpath%WL_HOME%;%WL_HOME%\license;%CLASSPATH%
    utils
    dbping ORACLE <username> <password> <database>
    Missing license file for: WebLogic Server 6.1
    Error encountered:
    java.sql.SQLException: Fail to load jDriver/Oracle due to license
    checking
    faile
    d!
    at
    weblogic.jdbc.oci.Driver.loadLibraryIfNeeded(Driver.java:182)
    at weblogic.jdbc.oci.Driver.connect(Driver.java:76)
    at java.sql.DriverManager.getConnection(DriverManager.java:517)
    at java.sql.DriverManager.getConnection(DriverManager.java:146)
    at utils.dbping.main(dbping.java:167)
    Hi why it is complaining for OCI drivers when I am using thin driver?
    Thanks
    ..Madhuri
    "Sree Bodapati" <[email protected]> wrote:
    Try,
    java -classpath %WL_HOME%;%WL_HOME%\license;%CLASSPATH% utils.dbping
    ORACLE
    scott tiger TNS_alias
    and see if it helps, make sure WL_HOMe is set properly.
    sree
    "Madhuri" <[email protected]> wrote in message
    news:[email protected]...
    Hi Sree !
    Following is the error message I am getting:
    java.sql.SQLException: No License:weblogic.common.LicenseNotFoundException:
    weblogic.common.LicenseNotFoundException:
    Could not find licensing file:
    Your WebLogic license file, named either WebLogicLicense.xmlor
    WebLogicLicense.class must be located in a directory
    that
    is
    in your CLASSPATH. By default, your license file is locatedin the
    /license directory located in your WebLogic home directory
    (the root directory of your WebLogic installation).
    As of version 4.0 of WebLogic, a new XML-format license
    file
    has
    replaced the older, compiled class format license file.
    The WebLogic Server will recognize either format.
    For additional information on WebLogic licenses or on
    setting
    your
    class
    path, see the installation instructions in the WebLogic Serverdocumentation,
    av
    ailable at
    http://e-docs.bea.com/
    at weblogic.jdbcbase.oci.Driver.connect(Driver.java:72)
    at java.sql.DriverManager.getConnection(Unknown Source)
    at java.sql.DriverManager.getConnection(Unknown Source)
    at utils.dbping.main(dbping.java:156)
    One more thing I would like to tell you that the file (including
    class
    file) is
    in the weblogic directory and the folder is also in the classpath.I am
    trying
    the following command :
    java utils.dbping ORACLE scott tiger TNS_alias
    Thanks in advance.
    .Madhuri
    "Sree Bodapati" <[email protected]> wrote:
    Hi Madhuri,
    Try placing the folder in which you have the license file in
    your
    classpath.
    Can you post the SQL Exception?
    sree
    "Madhuri" <[email protected]> wrote in message
    news:[email protected]...
    Hi !
    I am testing Oracle connection from dos prompt and I get the
    SQL
    Error
    SQLEXCEPTION.
    How do I connect Petstore to Oracle database? When I test
    the
    connection
    I
    get error message that java.sql.SQLException No License:
    weblogic.comon.LicenseNotFoundException. The file is in weblogic
    home
    directory.

  • Problem with oracle 9i personal and thin driver

    hi all,
    this is the code i test the connection of thin driver and oracle 9i personal database.
    but i got the error below, could someone tell me where i did wrong.
    thank you...
    import java.sql.*;
    import java.math.*;
    import java.io.*;
    import java.awt.*;
    import oracle.jdbc.driver.*;
    class JdbcTest
      public static void main(String arg[])
        try
          // load oracle driver
          DriverManager.registerDriver(new oracle.jdbc.OracleDriver());
          //connect to the local database
          Connection connection = DriverManager.getConnection
                                 ("jdbc:oracle:thin:@myhost:1521:ORCL","scott","tiger");
          Statement statement = connection.createStatement();
          ResultSet resultset = statement.executeQuery("SELECT ename FROM emp");
          //print the name out
          while(resultset.next())
            System.out.println(resultset.getString(1));
          //close the resultset, statement, and connection
          resultset.close();
          statement.close();
          connection.close();
        catch(SQLException sqle)
          System.err.println(sqle);
    }  C:\CODE-JDBC\ORACLE\TEST-CONNECT>java JdbcTest
    java.sql.SQLException: Io exception: The Network Adapter could not establish the connection

    Replace this line:
    DriverManager.registerDriver(new racle.jdbc.OracleDriver());with this one:
    Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();

  • BLOB insert behavior with thin driver using standard JDBC2.0 and ORACLE-JDBC2.0API

    We have a problem with a BLOB insert to an oracle 8.1.7 DB using Oracle 8.1.7 JDBC thin driver.We get socket read/write error after inserting 32k of data using the standard JDBC2.0 API but using the Oracle JDBC2.0API (using OracleResultSet) it goes fine. We have a requirement to use the standard JDBC2.0 so that our code works with multiple database vendors. Is there another way to get in the blob data with standard JDBC API & using thin driver...?
    thanks,
    Madhu
    Here is my sample test program that does both standard & oracle specific JDBC Blob test insert.
    import java.sql.*;
    import java.io.*;
    import oracle.sql.BLOB;
    import oracle.jdbc.driver.OracleResultSet;
    public class testBLOB {
    //trying to insert a huge file to a BLOB
    static String fileName = "/kernel/genunix";
    public static void main(String[] args) {
    String driverName = "oracle.jdbc.driver.OracleDriver";
    String dbURL = "jdbc:oracle:thin:@localhost:1521:test"; //thin driver
    String user = "BlobTest";
    String passwd = "BlobTest";
    Connection con=null;
    try {
    Class.forName(driverName);
    con=DriverManager.getConnection(dbURL, user,passwd);
    catch (Exception e) {
    e.printStackTrace();
    close(con);
    int i = 0;
    while (i < args.length) {
    if (args.equals("-f"))
    fileName = args[++i];
    i++;
    System.out.println("The file being Stored is: "+fileName);
    createTable(con);
    insertUsingOracleAPI(con);
    insertUsingJDBC20API(con);
    //readDB(con);
    static String getFileName() {
    return fileName;
    public static void close(Connection con) {
    try {
    if (con != null) {
    con.close();
    catch (Exception e) {
    System.exit(-1);
    public static void createTable(Connection con) {
    Statement stmt ;
    try {
    stmt = con.createStatement();
    stmt.execute("DROP TABLE basic_blob_table");
    stmt.close();
    catch (SQLException sqlEx) {
    System.out.println("Dropped the Table");
    try {
    stmt = con.createStatement();
    stmt.execute("CREATE TABLE basic_blob_table ( x varchar2(30), b blob)");
    stmt.close();
    catch (SQLException sqlEx) {
    sqlEx.printStackTrace();
    close(con);
    System.out.println("Created the Table");
    public static void insertUsingOracleAPI(Connection con) {
    OutputStream os = null;
    Statement stmt = null;
    ResultSet rs = null;
    FileInputStream is = null;
    try {
    con.setAutoCommit(false);
    stmt = con.createStatement();
    stmt.execute("INSERT INTO basic_blob_table VALUES( 'OracleAPI', empty_blob())");
    System.out.println("Inserted the dummy Row");
    rs = stmt.executeQuery("Select * from basic_blob_table where x='OracleAPI'");
    if (rs != null && rs.next()) {
    BLOB blob = ((OracleResultSet)rs).getBLOB(2);
    File file = new File(getFileName());
    is = new FileInputStream(file);
    os = blob.getBinaryOutputStream();
    byte[] chunk = new byte[1024];
    int length = -1;
    while((length = is.read(chunk)) != -1)
    os.write(chunk, 0,length);
    System.out.println("Inserted the File " + getFileName() );
    catch (Exception e) {
    e.printStackTrace();
    finally {
    try {
    if (os != null) {
    os.flush();
    os.close();
    if (is != null)
    is.close();
    stmt.close();
    con.commit();
    con.setAutoCommit(true);
    catch (Exception e) {}
    public static void insertUsingJDBC20API(Connection con) {
    PreparedStatement stmt = null;
    FileInputStream is = null;
    try {
    stmt = con.prepareStatement("INSERT INTO basic_blob_table VALUES(?,?)");
    File file = new File(getFileName());
    is = new FileInputStream(file);
    stmt.setString(1,"JDBC20API");
    stmt.setBinaryStream(2,is,(int)file.length());
    stmt.executeUpdate();
    catch (Exception e) {
    e.printStackTrace();
    finally {
    try {
    if (is != null)
    is.close();
    stmt.close();
    catch (Exception e) {}
    null

    Thanks for the response.
    I understand what you are saying...
    that readers don't block writers in Oracle (the same is true in SQL Server 2000).
    However, I don't see how my test case is working correctly with Oracle (the exact same code acting as I'm thinking it should with SQL Server, but I still think it is acting incorrectly with Oracle).
    I have transaction A do this:
    update <table> set <column2>=<value> where <column1>='1'
    then I use Thread.sleep() to make that program hang around for a few minutes.
    Meanwhile I sneak off and start another program which begins transaction B. I have transaction B do this:
    select * from <table> where <column1>='1'
    and the read works immediately (no blocking... just as you have said) however, transaction A is still sleeping, it has not called commit() or rollback() yet.
    So what if transaction A were to call rollback(), the value read by transaction B would be incorrect wouldn't it ?
    Both A and B use setAutoCommit(false) to start their transactions, and then call setTransactionIsolation(Connection.TRANSACTION_READ_COMMITTED).
    Isn't that supposed to guarantee that a reader can only read what is committed ?
    And if a row is in "flux"... in the process of having one or more values changed, then the database cannot say what the value will be ?
    I can almost see what you are saying.
    In letting the reader have what it wants without making it wait, I suppose it could be said that Oracle is holding true to the "only let committed data be read"
    So if that's it, then what if I want the blocking ?
    I want an entire row to be locked until whoever it in the middle of updating, adding, or removing it has finished.
    Do you know if that can be done with Oracle ? And how ?
    Thanks again for helping me.

  • [SOLVED] XOrg fails to load Nvidia driver on startup

    Hi,
    I'm having a fairly strange issue where XOrg is failing to load my driver when I start up my laptop. I'm using kdm, but this is causing it to fail. However, doing a simple
    $sudo systemctl restart kdm
    works, and everything starts up fine. When kdm is in the failed state, I see this:
    $sudo systemctl status kdm
    ● kdm.service - K Display Manager
    Loaded: loaded (/usr/lib/systemd/system/kdm.service; enabled; vendor preset: disabled)
    Active: active (running) since Fri 2014-12-19 18:47:26 EST; 41s ago
    Main PID: 247 (kdm)
    CGroup: /system.slice/kdm.service
    └─247 /usr/bin/kdm -nodaemon
    Dec 19 18:47:26 laptop systemd[1]: Started K Display Manager.
    Dec 19 18:47:27 laptop kdm[247]: X server died during startup
    Dec 19 18:47:27 laptop kdm[247]: X server for display :0 cannot be started, session disabled
    And in my XOrg log, I see:
    [ 3.639]
    This is a pre-release version of the X server from The X.Org Foundation.
    It is not supported in any way.
    Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
    Select the "xorg" product for bugs you find in this release.
    Before reporting bugs in pre-release versions please check the
    latest version in the X.Org Foundation git repository.
    See http://wiki.x.org/wiki/GitPage for git access instructions.
    [ 3.639]
    X.Org X Server 1.16.2.901 (1.16.3 RC 1)
    Release Date: 2014-12-09
    [ 3.639] X Protocol Version 11, Revision 0
    [ 3.639] Build Operating System: Linux 3.17.2-1-ARCH x86_64
    [ 3.639] Current Operating System: Linux laptop 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64
    [ 3.639] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw initrd=../initramfs-linux.img
    [ 3.639] Build Date: 10 December 2014 02:34:24PM
    [ 3.639]
    [ 3.639] Current version of pixman: 0.32.6
    [ 3.639] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 3.639] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 3.639] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 19 18:47:26 2014
    [ 3.645] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 3.649] (==) No Layout section. Using the first Screen section.
    [ 3.649] (==) No screen section available. Using defaults.
    [ 3.649] (**) |-->Screen "Default Screen Section" (0)
    [ 3.649] (**) | |-->Monitor "<default monitor>"
    [ 3.650] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 3.650] (==) Automatically adding devices
    [ 3.650] (==) Automatically enabling devices
    [ 3.650] (==) Automatically adding GPU devices
    [ 3.658] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 3.658] Entry deleted from font path.
    [ 3.659] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 3.659] Entry deleted from font path.
    [ 3.659] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 3.660] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 3.660] Entry deleted from font path.
    [ 3.660] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 3.660] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 3.660] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 3.660] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 3.660] (II) Loader magic: 0x818d80
    [ 3.660] (II) Module ABI versions:
    [ 3.660] X.Org ANSI C Emulation: 0.4
    [ 3.660] X.Org Video Driver: 18.0
    [ 3.660] X.Org XInput driver : 21.0
    [ 3.660] X.Org Server Extension : 8.0
    [ 3.662] (EE) systemd-logind: failed to get session: PID 267 does not belong to any known session
    [ 3.663] (--) PCI:*(0:1:0:0) 10de:11a1:1558:0371 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
    [ 3.663] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 3.664] (II) LoadModule: "glx"
    [ 3.675] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 3.767] (II) Module glx: vendor="NVIDIA Corporation"
    [ 3.767] compiled for 4.0.2, module version = 1.0.0
    [ 3.767] Module class: X.Org Server Extension
    [ 3.768] (II) NVIDIA GLX Module 343.36 Mon Dec 1 15:50:02 PST 2014
    [ 3.769] (==) Matched nouveau as autoconfigured driver 0
    [ 3.769] (==) Matched nv as autoconfigured driver 1
    [ 3.769] (==) Matched modesetting as autoconfigured driver 2
    [ 3.769] (==) Matched fbdev as autoconfigured driver 3
    [ 3.769] (==) Matched vesa as autoconfigured driver 4
    [ 3.769] (==) Assigned the driver to the xf86ConfigLayout
    [ 3.769] (II) LoadModule: "nouveau"
    [ 3.769] (WW) Warning, couldn't open module nouveau
    [ 3.769] (II) UnloadModule: "nouveau"
    [ 3.769] (II) Unloading nouveau
    [ 3.769] (EE) Failed to load module "nouveau" (module does not exist, 0)
    [ 3.769] (II) LoadModule: "nv"
    [ 3.769] (WW) Warning, couldn't open module nv
    [ 3.769] (II) UnloadModule: "nv"
    [ 3.769] (II) Unloading nv
    [ 3.769] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 3.769] (II) LoadModule: "modesetting"
    [ 3.769] (WW) Warning, couldn't open module modesetting
    [ 3.769] (II) UnloadModule: "modesetting"
    [ 3.769] (II) Unloading modesetting
    [ 3.769] (EE) Failed to load module "modesetting" (module does not exist, 0)
    [ 3.769] (II) LoadModule: "fbdev"
    [ 3.769] (WW) Warning, couldn't open module fbdev
    [ 3.769] (II) UnloadModule: "fbdev"
    [ 3.769] (II) Unloading fbdev
    [ 3.769] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 3.769] (II) LoadModule: "vesa"
    [ 3.770] (WW) Warning, couldn't open module vesa
    [ 3.770] (II) UnloadModule: "vesa"
    [ 3.770] (II) Unloading vesa
    [ 3.770] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 3.770] (EE) No drivers available.
    [ 3.770] (EE)
    Fatal server error:
    [ 3.770] (EE) no screens found(EE)
    [ 3.770] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 3.770] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 3.770] (EE)
    Which looks like it loads my nvidia driver, but then just decides not to use it for some reason... After I restart kdm, it seems to use the driver fine:
    [ 78.897]
    This is a pre-release version of the X server from The X.Org Foundation.
    It is not supported in any way.
    Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
    Select the "xorg" product for bugs you find in this release.
    Before reporting bugs in pre-release versions please check the
    latest version in the X.Org Foundation git repository.
    See http://wiki.x.org/wiki/GitPage for git access instructions.
    [ 78.897]
    X.Org X Server 1.16.2.901 (1.16.3 RC 1)
    Release Date: 2014-12-09
    [ 78.897] X Protocol Version 11, Revision 0
    [ 78.897] Build Operating System: Linux 3.17.2-1-ARCH x86_64
    [ 78.897] Current Operating System: Linux laptop 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:43:32 UTC 2014 x86_64
    [ 78.897] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw initrd=../initramfs-linux.img
    [ 78.897] Build Date: 10 December 2014 02:34:24PM
    [ 78.897]
    [ 78.897] Current version of pixman: 0.32.6
    [ 78.897] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 78.897] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 78.897] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 19 18:48:38 2014
    [ 78.897] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 78.897] (==) No Layout section. Using the first Screen section.
    [ 78.897] (==) No screen section available. Using defaults.
    [ 78.897] (**) |-->Screen "Default Screen Section" (0)
    [ 78.897] (**) | |-->Monitor "<default monitor>"
    [ 78.898] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 78.898] (==) Automatically adding devices
    [ 78.898] (==) Automatically enabling devices
    [ 78.898] (==) Automatically adding GPU devices
    [ 78.898] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 78.898] Entry deleted from font path.
    [ 78.898] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 78.898] Entry deleted from font path.
    [ 78.898] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 78.898] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 78.898] Entry deleted from font path.
    [ 78.898] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 78.898] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 78.898] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 78.898] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 78.898] (II) Loader magic: 0x818d80
    [ 78.898] (II) Module ABI versions:
    [ 78.898] X.Org ANSI C Emulation: 0.4
    [ 78.898] X.Org Video Driver: 18.0
    [ 78.898] X.Org XInput driver : 21.0
    [ 78.898] X.Org Server Extension : 8.0
    [ 78.900] (EE) systemd-logind: failed to get session: PID 542 does not belong to any known session
    [ 78.900] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 78.901] (--) PCI:*(0:1:0:0) 10de:11a1:1558:0371 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
    [ 78.901] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 78.901] (II) LoadModule: "glx"
    [ 78.902] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 78.913] (II) Module glx: vendor="NVIDIA Corporation"
    [ 78.913] compiled for 4.0.2, module version = 1.0.0
    [ 78.913] Module class: X.Org Server Extension
    [ 78.913] (II) NVIDIA GLX Module 343.36 Mon Dec 1 15:50:02 PST 2014
    [ 78.914] (II) Applying OutputClass "nvidia" to /dev/dri/card0
    [ 78.914] loading driver: nvidia
    [ 78.914] (==) Matched nvidia as autoconfigured driver 0
    [ 78.914] (==) Matched nouveau as autoconfigured driver 1
    [ 78.914] (==) Matched nv as autoconfigured driver 2
    [ 78.914] (==) Matched nouveau as autoconfigured driver 3
    [ 78.914] (==) Matched nv as autoconfigured driver 4
    [ 78.914] (==) Matched modesetting as autoconfigured driver 5
    [ 78.914] (==) Matched fbdev as autoconfigured driver 6
    [ 78.914] (==) Matched vesa as autoconfigured driver 7
    [ 78.914] (==) Assigned the driver to the xf86ConfigLayout
    [ 78.914] (II) LoadModule: "nvidia"
    [ 78.914] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 78.920] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 78.920] compiled for 4.0.2, module version = 1.0.0
    [ 78.920] Module class: X.Org Video Driver
    [ 78.920] (II) LoadModule: "nouveau"
    [ 78.921] (WW) Warning, couldn't open module nouveau
    [ 78.921] (II) UnloadModule: "nouveau"
    [ 78.921] (II) Unloading nouveau
    [ 78.921] (EE) Failed to load module "nouveau" (module does not exist, 0)
    [ 78.921] (II) LoadModule: "nv"
    [ 78.921] (WW) Warning, couldn't open module nv
    [ 78.921] (II) UnloadModule: "nv"
    [ 78.921] (II) Unloading nv
    [ 78.921] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 78.921] (II) LoadModule: "modesetting"
    [ 78.921] (WW) Warning, couldn't open module modesetting
    [ 78.921] (II) UnloadModule: "modesetting"
    [ 78.921] (II) Unloading modesetting
    [ 78.921] (EE) Failed to load module "modesetting" (module does not exist, 0)
    [ 78.921] (II) LoadModule: "fbdev"
    [ 78.922] (WW) Warning, couldn't open module fbdev
    [ 78.922] (II) UnloadModule: "fbdev"
    [ 78.922] (II) Unloading fbdev
    [ 78.922] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 78.922] (II) LoadModule: "vesa"
    [ 78.922] (WW) Warning, couldn't open module vesa
    [ 78.922] (II) UnloadModule: "vesa"
    [ 78.922] (II) Unloading vesa
    [ 78.922] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 78.922] (II) NVIDIA dlloader X Driver 343.36 Mon Dec 1 15:28:39 PST 2014
    [ 78.922] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 78.922] (++) using VT number 7
    [ 78.935] (II) Loading sub module "fb"
    [ 78.935] (II) LoadModule: "fb"
    [ 78.935] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 78.936] (II) Module fb: vendor="X.Org Foundation"
    [ 78.936] compiled for 1.16.2.901, module version = 1.0.0
    [ 78.936] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 78.936] (II) Loading sub module "wfb"
    [ 78.936] (II) LoadModule: "wfb"
    [ 78.936] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 78.937] (II) Module wfb: vendor="X.Org Foundation"
    [ 78.937] compiled for 1.16.2.901, module version = 1.0.0
    [ 78.937] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 78.937] (II) Loading sub module "ramdac"
    [ 78.937] (II) LoadModule: "ramdac"
    [ 78.937] (II) Module "ramdac" already built-in
    [ 78.939] (II) NVIDIA(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 78.939] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
    [ 78.939] (==) NVIDIA(0): RGB weight 888
    [ 78.939] (==) NVIDIA(0): Default visual is TrueColor
    [ 78.939] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 78.940] (**) NVIDIA(0): Enabling 2D acceleration
    [ 79.610] (II) NVIDIA(0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
    [ 79.610] (II) NVIDIA(0): 3D Vision stereo.
    [ 79.610] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
    [ 79.612] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 670MX (GK104) at PCI:1:0:0 (GPU-0)
    [ 79.612] (--) NVIDIA(0): Memory: 3145728 kBytes
    [ 79.612] (--) NVIDIA(0): VideoBIOS: 80.04.67.00.06
    [ 79.612] (II) NVIDIA(0): Detected PCI Express Link width: 16X
    [ 79.616] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 670MX at PCI:1:0:0
    [ 79.616] (--) NVIDIA(0): Chi Mei Optoelectronics corp. (DFP-0) (boot, connected)
    [ 79.616] (--) NVIDIA(0): Samsung SyncMaster (DFP-1) (connected)
    [ 79.616] (--) NVIDIA(0): DFP-2
    [ 79.616] (--) NVIDIA(0): DFP-3
    [ 79.616] (--) NVIDIA(0): DFP-4
    [ 79.616] (--) NVIDIA(0): Chi Mei Optoelectronics corp. (DFP-0): Internal LVDS
    [ 79.616] (--) NVIDIA(GPU-0): Chi Mei Optoelectronics corp. (DFP-0): 330.0 MHz maximum pixel clock
    [ 79.616] (--) NVIDIA(0): Samsung SyncMaster (DFP-1): Internal TMDS
    [ 79.616] (--) NVIDIA(GPU-0): Samsung SyncMaster (DFP-1): 165.0 MHz maximum pixel clock
    [ 79.616] (--) NVIDIA(0): DFP-2: Internal TMDS
    [ 79.616] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
    [ 79.616] (--) NVIDIA(0): DFP-3: Internal DisplayPort
    [ 79.616] (--) NVIDIA(GPU-0): DFP-3: 960.0 MHz maximum pixel clock
    [ 79.616] (--) NVIDIA(0): DFP-4: Internal DisplayPort
    [ 79.616] (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
    [ 79.616] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 79.616] (**) NVIDIA(0): device Chi Mei Optoelectronics corp. (DFP-0) (Using EDID
    [ 79.616] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 79.616] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 79.616] (**) NVIDIA(0): device Samsung SyncMaster (DFP-1) (Using EDID frequencies
    [ 79.616] (**) NVIDIA(0): has been enabled on all display devices.)
    [ 79.618] (==) NVIDIA(0):
    [ 79.618] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
    [ 79.618] (==) NVIDIA(0): will be used as the requested mode.
    [ 79.618] (==) NVIDIA(0):
    [ 79.619] (II) NVIDIA(0): Validated MetaModes:
    [ 79.619] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
    [ 79.619] (II) NVIDIA(0): Virtual screen size determined to be 3600 x 1080
    [ 80.144] (--) NVIDIA(0): DPI set to (128, 130); computed from "UseEdidDpi" X config
    [ 80.144] (--) NVIDIA(0): option
    [ 80.144] (--) Depth 24 pixmap format is 32 bpp
    [ 80.144] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
    [ 80.144] (II) NVIDIA: access.
    [ 80.150] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 80.150] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
    [ 80.150] (II) NVIDIA(0): configuration option may not be set correctly. When the
    [ 80.150] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
    [ 80.150] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
    [ 80.150] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
    [ 80.150] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 80.150] (II) NVIDIA(0): Config Options in the README.
    [ 80.155] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
    [ 80.532] (==) NVIDIA(0): Disabling shared memory pixmaps
    [ 80.532] (==) NVIDIA(0): Backing store enabled
    [ 80.532] (==) NVIDIA(0): Silken mouse enabled
    [ 80.533] (==) NVIDIA(0): DPMS enabled
    [ 80.533] (II) Loading sub module "dri2"
    [ 80.533] (II) LoadModule: "dri2"
    [ 80.533] (II) Module "dri2" already built-in
    [ 80.533] (II) NVIDIA(0): [DRI2] Setup complete
    [ 80.533] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
    [ 80.533] (--) RandR disabled
    [ 80.539] (II) Initializing extension GLX
    [ 80.605] (II) config/udev: Adding input device Power Button (/dev/input/event14)
    [ 80.605] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 80.605] (II) LoadModule: "evdev"
    [ 80.606] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 80.607] (II) Module evdev: vendor="X.Org Foundation"
    [ 80.607] compiled for 1.16.2, module version = 2.9.1
    [ 80.607] Module class: X.Org XInput Driver
    [ 80.607] ABI class: X.Org XInput driver, version 21.0
    [ 80.607] (II) Using input driver 'evdev' for 'Power Button'
    [ 80.607] (**) Power Button: always reports core events
    [ 80.607] (**) evdev: Power Button: Device: "/dev/input/event14"
    [ 80.608] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 80.608] (--) evdev: Power Button: Found keys
    [ 80.608] (II) evdev: Power Button: Configuring as keyboard
    [ 80.608] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input18/event14"
    [ 80.608] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 80.608] (**) Option "xkb_rules" "evdev"
    [ 80.608] (**) Option "xkb_model" "pc104"
    [ 80.608] (**) Option "xkb_layout" "us"
    [ 80.635] (II) config/udev: Adding input device Video Bus (/dev/input/event15)
    [ 80.635] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 80.635] (II) Using input driver 'evdev' for 'Video Bus'
    [ 80.635] (**) Video Bus: always reports core events
    [ 80.635] (**) evdev: Video Bus: Device: "/dev/input/event15"
    [ 80.635] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 80.635] (--) evdev: Video Bus: Found keys
    [ 80.635] (II) evdev: Video Bus: Configuring as keyboard
    [ 80.635] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/LNXVIDEO:00/input/input19/event15"
    [ 80.635] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 80.635] (**) Option "xkb_rules" "evdev"
    [ 80.635] (**) Option "xkb_model" "pc104"
    [ 80.635] (**) Option "xkb_layout" "us"
    [ 80.636] (II) config/udev: Adding input device Power Button (/dev/input/event13)
    [ 80.636] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 80.636] (II) Using input driver 'evdev' for 'Power Button'
    [ 80.636] (**) Power Button: always reports core events
    [ 80.636] (**) evdev: Power Button: Device: "/dev/input/event13"
    [ 80.636] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 80.636] (--) evdev: Power Button: Found keys
    [ 80.636] (II) evdev: Power Button: Configuring as keyboard
    [ 80.636] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input17/event13"
    [ 80.636] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
    [ 80.636] (**) Option "xkb_rules" "evdev"
    [ 80.636] (**) Option "xkb_model" "pc104"
    [ 80.636] (**) Option "xkb_layout" "us"
    [ 80.637] (II) config/udev: Adding input device Lid Switch (/dev/input/event11)
    [ 80.637] (II) No input driver specified, ignoring this device.
    [ 80.637] (II) This device may have been added with another device file.
    [ 80.637] (II) config/udev: Adding input device Sleep Button (/dev/input/event12)
    [ 80.637] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 80.637] (II) Using input driver 'evdev' for 'Sleep Button'
    [ 80.637] (**) Sleep Button: always reports core events
    [ 80.637] (**) evdev: Sleep Button: Device: "/dev/input/event12"
    [ 80.637] (--) evdev: Sleep Button: Vendor 0 Product 0x3
    [ 80.637] (--) evdev: Sleep Button: Found keys
    [ 80.637] (II) evdev: Sleep Button: Configuring as keyboard
    [ 80.637] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input16/event12"
    [ 80.637] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
    [ 80.637] (**) Option "xkb_rules" "evdev"
    [ 80.637] (**) Option "xkb_model" "pc104"
    [ 80.637] (**) Option "xkb_layout" "us"
    [ 80.638] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event18)
    [ 80.638] (II) No input driver specified, ignoring this device.
    [ 80.638] (II) This device may have been added with another device file.
    [ 80.638] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event19)
    [ 80.638] (II) No input driver specified, ignoring this device.
    [ 80.638] (II) This device may have been added with another device file.
    [ 80.639] (II) config/udev: Adding input device LOGITECH G110 G-keys (/dev/input/event3)
    [ 80.639] (**) LOGITECH G110 G-keys: Applying InputClass "evdev keyboard catchall"
    [ 80.639] (II) Using input driver 'evdev' for 'LOGITECH G110 G-keys'
    [ 80.639] (**) LOGITECH G110 G-keys: always reports core events
    [ 80.639] (**) evdev: LOGITECH G110 G-keys: Device: "/dev/input/event3"
    [ 80.639] (--) evdev: LOGITECH G110 G-keys: Vendor 0x46d Product 0xc22b
    [ 80.639] (--) evdev: LOGITECH G110 G-keys: Found keys
    [ 80.639] (II) evdev: LOGITECH G110 G-keys: Configuring as keyboard
    [ 80.639] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.1/3-4.1.1:1.0/0003:046D:C22B.0003/input/input7/event3"
    [ 80.639] (II) XINPUT: Adding extended input device "LOGITECH G110 G-keys" (type: KEYBOARD, id 10)
    [ 80.639] (**) Option "xkb_rules" "evdev"
    [ 80.639] (**) Option "xkb_model" "pc104"
    [ 80.639] (**) Option "xkb_layout" "us"
    [ 80.639] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event4)
    [ 80.639] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
    [ 80.639] (II) Using input driver 'evdev' for 'Gaming Keyboard G110'
    [ 80.639] (**) Gaming Keyboard G110: always reports core events
    [ 80.639] (**) evdev: Gaming Keyboard G110: Device: "/dev/input/event4"
    [ 80.640] (--) evdev: Gaming Keyboard G110: Vendor 0x46d Product 0xc22a
    [ 80.640] (--) evdev: Gaming Keyboard G110: Found keys
    [ 80.640] (II) evdev: Gaming Keyboard G110: Configuring as keyboard
    [ 80.640] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.3/3-4.1.3:1.0/0003:046D:C22A.0004/input/input8/event4"
    [ 80.640] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 11)
    [ 80.640] (**) Option "xkb_rules" "evdev"
    [ 80.640] (**) Option "xkb_model" "pc104"
    [ 80.640] (**) Option "xkb_layout" "us"
    [ 80.640] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event5)
    [ 80.640] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
    [ 80.640] (II) Using input driver 'evdev' for 'Gaming Keyboard G110'
    [ 80.640] (**) Gaming Keyboard G110: always reports core events
    [ 80.640] (**) evdev: Gaming Keyboard G110: Device: "/dev/input/event5"
    [ 80.640] (--) evdev: Gaming Keyboard G110: Vendor 0x46d Product 0xc22a
    [ 80.640] (--) evdev: Gaming Keyboard G110: Found keys
    [ 80.640] (II) evdev: Gaming Keyboard G110: Configuring as keyboard
    [ 80.640] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.1/3-4.1.3/3-4.1.3:1.1/0003:046D:C22A.0005/input/input9/event5"
    [ 80.640] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 12)
    [ 80.640] (**) Option "xkb_rules" "evdev"
    [ 80.640] (**) Option "xkb_model" "pc104"
    [ 80.641] (**) Option "xkb_layout" "us"
    [ 80.641] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/event1)
    [ 80.641] (**) Razer Razer Lachesis: Applying InputClass "evdev pointer catchall"
    [ 80.641] (II) Using input driver 'evdev' for 'Razer Razer Lachesis'
    [ 80.641] (**) Razer Razer Lachesis: always reports core events
    [ 80.641] (**) evdev: Razer Razer Lachesis: Device: "/dev/input/event1"
    [ 80.641] (--) evdev: Razer Razer Lachesis: Vendor 0x1532 Product 0xc
    [ 80.641] (--) evdev: Razer Razer Lachesis: Found 12 mouse buttons
    [ 80.641] (--) evdev: Razer Razer Lachesis: Found scroll wheel(s)
    [ 80.641] (--) evdev: Razer Razer Lachesis: Found relative axes
    [ 80.641] (--) evdev: Razer Razer Lachesis: Found x and y relative axes
    [ 80.641] (II) evdev: Razer Razer Lachesis: Configuring as mouse
    [ 80.641] (II) evdev: Razer Razer Lachesis: Adding scrollwheel support
    [ 80.641] (**) evdev: Razer Razer Lachesis: YAxisMapping: buttons 4 and 5
    [ 80.641] (**) evdev: Razer Razer Lachesis: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 80.641] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.2/3-4.2:1.0/0003:1532:000C.0001/input/input5/event1"
    [ 80.641] (II) XINPUT: Adding extended input device "Razer Razer Lachesis" (type: MOUSE, id 13)
    [ 80.642] (II) evdev: Razer Razer Lachesis: initialized for relative axes.
    [ 80.642] (**) Razer Razer Lachesis: (accel) keeping acceleration scheme 1
    [ 80.642] (**) Razer Razer Lachesis: (accel) acceleration profile 0
    [ 80.642] (**) Razer Razer Lachesis: (accel) acceleration factor: 2.000
    [ 80.642] (**) Razer Razer Lachesis: (accel) acceleration threshold: 4
    [ 80.642] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/mouse0)
    [ 80.642] (II) No input driver specified, ignoring this device.
    [ 80.642] (II) This device may have been added with another device file.
    [ 80.643] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/event2)
    [ 80.643] (**) Razer Razer Lachesis: Applying InputClass "evdev keyboard catchall"
    [ 80.643] (II) Using input driver 'evdev' for 'Razer Razer Lachesis'
    [ 80.643] (**) Razer Razer Lachesis: always reports core events
    [ 80.643] (**) evdev: Razer Razer Lachesis: Device: "/dev/input/event2"
    [ 80.643] (--) evdev: Razer Razer Lachesis: Vendor 0x1532 Product 0xc
    [ 80.643] (--) evdev: Razer Razer Lachesis: Found keys
    [ 80.643] (II) evdev: Razer Razer Lachesis: Configuring as keyboard
    [ 80.643] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.2/3-4.2:1.1/0003:1532:000C.0002/input/input6/event2"
    [ 80.643] (II) XINPUT: Adding extended input device "Razer Razer Lachesis" (type: KEYBOARD, id 14)
    [ 80.643] (**) Option "xkb_rules" "evdev"
    [ 80.643] (**) Option "xkb_model" "pc104"
    [ 80.643] (**) Option "xkb_layout" "us"
    [ 80.643] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
    [ 80.643] (II) No input driver specified, ignoring this device.
    [ 80.643] (II) This device may have been added with another device file.
    [ 80.644] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event7)
    [ 80.644] (II) No input driver specified, ignoring this device.
    [ 80.644] (II) This device may have been added with another device file.
    [ 80.644] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
    [ 80.644] (II) No input driver specified, ignoring this device.
    [ 80.644] (II) This device may have been added with another device file.
    [ 80.644] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event9)
    [ 80.644] (II) No input driver specified, ignoring this device.
    [ 80.644] (II) This device may have been added with another device file.
    [ 80.645] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event10)
    [ 80.645] (II) No input driver specified, ignoring this device.
    [ 80.645] (II) This device may have been added with another device file.
    [ 80.645] (II) config/udev: Adding input device BisonCam, NB Pro (/dev/input/event17)
    [ 80.645] (**) BisonCam, NB Pro: Applying InputClass "evdev keyboard catchall"
    [ 80.645] (II) Using input driver 'evdev' for 'BisonCam, NB Pro'
    [ 80.645] (**) BisonCam, NB Pro: always reports core events
    [ 80.645] (**) evdev: BisonCam, NB Pro: Device: "/dev/input/event17"
    [ 80.645] (--) evdev: BisonCam, NB Pro: Vendor 0x5986 Product 0x512
    [ 80.645] (--) evdev: BisonCam, NB Pro: Found keys
    [ 80.645] (II) evdev: BisonCam, NB Pro: Configuring as keyboard
    [ 80.645] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input23/event17"
    [ 80.645] (II) XINPUT: Adding extended input device "BisonCam, NB Pro" (type: KEYBOARD, id 15)
    [ 80.645] (**) Option "xkb_rules" "evdev"
    [ 80.645] (**) Option "xkb_model" "pc104"
    [ 80.645] (**) Option "xkb_layout" "us"
    [ 80.646] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 80.646] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 80.646] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 80.646] (**) AT Translated Set 2 keyboard: always reports core events
    [ 80.646] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 80.646] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 80.646] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 80.646] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 80.646] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 80.646] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 16)
    [ 80.646] (**) Option "xkb_rules" "evdev"
    [ 80.646] (**) Option "xkb_model" "pc104"
    [ 80.646] (**) Option "xkb_layout" "us"
    [ 80.646] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event20)
    [ 80.646] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 80.647] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 80.647] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 80.647] (II) LoadModule: "synaptics"
    [ 80.647] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [ 80.647] (II) Module synaptics: vendor="X.Org Foundation"
    [ 80.647] compiled for 1.16.0, module version = 1.8.1
    [ 80.647] Module class: X.Org XInput Driver
    [ 80.647] ABI class: X.Org XInput driver, version 21.0
    [ 80.647] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 80.647] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 80.647] (**) Option "Device" "/dev/input/event20"
    [ 80.756] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
    [ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5662 (res 42)
    [ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4660 (res 47)
    [ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
    [ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 80.757] (**) Option "TapButton1" "1"
    [ 80.757] (**) Option "TapButton2" "2"
    [ 80.757] (**) Option "TapButton3" "3"
    [ 80.757] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
    [ 80.757] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 80.757] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 80.810] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio2/input/input22/event20"
    [ 80.810] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 17)
    [ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
    [ 80.810] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.038
    [ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 80.810] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 80.810] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 80.811] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
    [ 80.811] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
    [ 80.811] (II) config/udev: Adding input device PC Speaker (/dev/input/event16)
    [ 80.811] (II) No input driver specified, ignoring this device.
    [ 80.811] (II) This device may have been added with another device file.
    [ 88.265] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
    [ 88.265] (II) NVIDIA(GPU-0): 3D Vision stereo.
    [ 88.282] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
    [ 88.282] (II) NVIDIA(GPU-0): 3D Vision stereo.
    [ 88.291] (II) NVIDIA(0): Setting mode "LVDS-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, HDMI-0: 1680x1050_60_0 @1680x1050 +1920+0 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0}"
    [ 89.221] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
    [ 89.221] (II) NVIDIA(GPU-0): 3D Vision stereo.
    [ 90.639] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
    [ 90.639] (II) NVIDIA(GPU-0): 3D Vision stereo.
    [ 93.745] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
    [ 93.745] (II) NVIDIA(GPU-0): 3D Vision stereo.
    Notably, the following lines appear in the working case, but not the broken case:
    [ 78.914] (II) Applying OutputClass "nvidia" to /dev/dri/card0
    [ 78.914] loading driver: nvidia
    Does anyone know what might be going on here?
    Last edited by straemer (2014-12-20 13:03:58)

    Hmmmm, that doesn't seem to be the issue. I have a nvidia geforce gtx 670mx. The nvidia website does link me to the 340xx driver for that card, but downgrading to that version still has the same issue. I suspect the issue is in Xorg, since it seems to load the module, but then decides it doesn't have a driver to run for some reason.

  • Thin driver connection in oracle8i(8.1.5) on Linux with JDK1.2.2

    JDBC Development team quote:
    You can download the JDK 1.2 version of the 8.1.6 Thin driver from this site. It is 100% Pure Java and will run on Linux.
    As you replied, I downloaded 8.1.6 Thin driver(classes12.zip) and nls_charset12.zip. Then, as instructed in readme file of 8.1.6, I modified CLASSPATH and add LD_LIBRARY_PATH.
    I wrote a test program, and it compiled without errors. But when I excuted it, I got the error message below:
    java.sql.SQLException: Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNU
    M=135286784)(ERR=12505)(ERROR_STACK=(ERROR=(CODE=12505)(EMFI=4))))
    Is there any other installation procedures I missed?
    Below is the test program I used:
    import java.sql.*;
    import oracle.jdbc.driver.*;
    public class Test
    public static void main (String args [])throws SQLException
    //DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
    try{
    Class.forName("oracle.jdbc.driver.OracleDriver");
    catch(ClassNotFoundException e){
    System.out.println("Cannot load the Driver");
    Connection conn = DriverManager.getConnection ("jdbc:oracle:thin:@host:port:sid","id", "password");
    Statement stmt = conn.createStatement ();
    ResultSet rset = stmt.executeQuery ("select sysdate from dual");
    while (rset.next ())
    System.out.println (rset.getString (1));
    I'd appreciate if you give me some insight.
    null

    It seems like the database listener is not setup properly. Please double check the listener is up and it's listening to the port you specified.
    Thanks.

  • (applet,thin driver): IE works, appletviewer not; driver location?

    Hi,
    there are a lot of questions around this topic but I couldn't find a specific answer to this:
    I programmed an applet under WinNT (connection to Oracle 8i thru thin driver) and keep the Oracle drivers in the ..\Ora8i\jdbc\lib\ place (ZIPped), classpath set correctly.
    The applet works fine in IE on my local machine, but not in the appletviewer (it can't find the driver class). Without applet-specific part it works fine using 'java ...'.
    I use the suggested 'import oracle.jdbc.driver.OracleDriver' statement.
    2nd question: since this applet is supposed to run on a webserver (and not only my local machine...), where do I place the driver (class or whole zip-file?) and how do I tell the main class / applet where to look for it instead of Ora8i\jdbc\lib\ ?
    Thanks for any help!!

    There's a fair amount of fiddling you can do with packets sent over the network by SQL*Net, but that requires the OCI driver. The thin driver is writing out Oracle's wire protocol which isn't publicly documented.
    The OCI driver is going to be faster in general than the thin driver, and you're going to have more flexibility to optimize its network traffic.
    Justin

Maybe you are looking for