Previous Topic: Test Oracle Environment Variables (UNIX Only)Next Topic: DB2 Database Requirements


Verify Oracle Native Connectivity Through a TNS (UNIX Only)

To verify Oracle native connectivity through a TNS

  1. Log in to the UNIX server with the user account and password which you will use to do your install.

    Note: This account should already be set up. See Create an Account, a Home Directory, and a Login Environment for more information about setting up a UNIX account to use when you install BusinessObjects Enterprise.

  2. Echo the following environment variables and ensure that their values correspond to your database client software installation.
    ORACLE_HOME

    This variable contains the path to the root directory of your Oracle client installation (one level above the Oracle bin and lib directories).

    library path

    The library search path (LD_LIBRARY_PATH on Solaris and Linux, and LIBPATH on AIX) must include the lib32 directory of your Oracle client installation.

    PATH

    The search path must include the bin directory of your Oracle client installation.

    This example checks the required variables and shows sample output values.

    $ echo $ORACLE_HOME
    /home/dbclient/oracle/10.1.0.3
    $ echo $LD_LIBRARY_PATH
    /home/dbclient/oracle/10.1.0.3/lib32
    $ echo $PATH
    /usr/local/bin:/home/dbclient/oracle/10.1.0.3/bin
    
  3. Issue the following command to run the Oracle SQL tool and connect to the appropriate service name:
    sqlplus accountname/password@tnsname
    

    Replace accountname, password and tnsname with the appropriate values. If the shell environment has been configured correctly, you are connected to Oracle.

    Note: The first time you log in with SQL Plus, use sys as the user, then create a new database user. Supply this new user to the BusinessObjects Enterprise installer when it ask for the oracle username, password and tnsname.

  4. Issue the following command to ensure that account has permission to create tables:
    create table sampletable (field1 char(10));
    
  5. Issue the following command to ensure that the account has permission to delete tables:
    drop table sampletable;
    
  6. Issue the following command to ensure that the account has permission to create procedures:
    CREATE PROCEDURE test_proc (foo_in VARCHAR, bar_in VARCHAR)
    IS
    BEGIN
    INSERT INTO test_table (foo, bar) VALUES (foo_in, bar_in);
    END;
    
  7. Issue the following command to ensure that the account has permission to drop procedures:
    DROP PROCEDURE TEST_PROC;
    
  8. Type exit.