rdbm.DatabasemetaDataImpl assumes incorrectly that database doesn't support features if database is down. This causes uPortal to fail if it is started before the database is avaliable. uPortal should be fixed so it will recover once the database is avaliable.

This is what you will get printed to the log if the database is unavaliable:


 INFO [main] rdbm.DatabaseMetaDataImpl.[] Feb/26 20:07:59 - null (null) / null (null) database/driver
    Connected To: null
    Supports:
        Prepared Statements: false
        Outer Joins: false
        Transactions: false
        {ts metasyntax: false
        TO_DATE(): false


This is what you'll see if it is avaliable:

INFO [main] rdbm.DatabaseMetaDataImpl.[] Feb/26 22:44:53 - Oracle (Oracle Database 10g Release 10.1.0.4.0 - Production
With the Real Application Clusters option) / Oracle JDBC driver (10.1.0.4.0) database/driver
    Connected To: jdbc:oracle:thin:@
          (DESCRIPTION =
            (ADDRESS = (PROTOCOL = TCP)
              (HOST = dbserver1.foo.edu)(PORT = 1521)
            )
            (ADDRESS = (PROTOCOL = TCP)
              (HOST = dbserver2.foo.edu)(PORT = 1521)
            )
            (LOAD_BALANCE = yes)
            (CONNECT_DATA = (SERVER = DEDICATED)
                (SERVICE_NAME = portal)
                (FAILOVER_MODE = (TYPE = SELECT)(METHOD = BASIC)(RETRIES = 180)(DELAY = 5))
            )
           )
    Supports:
        Prepared Statements: true
        Outer Joins: true
        Transactions: true
        {ts metasyntax: true
        TO_DATE(): false