InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.14: Administering database connections (overview) >
6.6.14.6: Notes about various databases

6.6.14.6: Notes about various databases

This article provides miscellaneous tips for using supported databases. See also the related links.

  Always consult the product prerequisites Web site for a list of the database brands and versions that are supported by your particular Application Server version, edition, and fix pack.

  • Do not drop the administrative database while the administrative server is running.
  • DB2 performance on a local machine can be improved by setting up a local database as a remote instance. On UNIX systems, this is required. The configuration uses TCP/IP instead of shared memory.

    Oracle and Sybase also support client/server connections. Consult their product documentation for specifics.

  • To use SQLJ static queries with DB2/MVS, be sure to add sqlj.jar and runtime.jar to the application server classpath only.
  • When using Sybase 11.x, you might encounter the following error when HttpSession persistence is enabled:
    DBPortability W Could not create database table: "sessions"
    com.sybase.jdbc2.jdbc.SybSQLException: The 'CREATE TABLE' command is not
    allowed within a multi-statement transaction in the 'database_name' database
    where 'database_name' is the name of the database for holding sessions.

    If you encounter the error, issue the following commands at the Sybase command line:

    use database_name
    go
    sp_dboption db,"ddl in tran ",true
    go
    
  • Sybase 12.0 does not support local transaction modes with a JTA enabled data source. To use a connection from a JTA enabled data source in a local transaction, Sybase patch EBF9422 must be installed.

Go to previous article: Additional administrative tasks for specific databases Go to next article: Failover support with HACMP

 

 
Go to previous article: Additional administrative tasks for specific databases Go to next article: Failover support with HACMP