Create databases and users for Oracle RAC

 

+
Search Tips   |   Advanced Search

 

 

Overview

Before beginning you should have completed Installing Oracle RAC.

If WebSphere Portal V6.0 and an earlier version of WebSphere Portal coexist, the database user IDs for WebSphere Portal Version 6.0 must be different than earlier versions to avoid conflicts during installation.

The tablespace LMTABLESPACE is reserved for LikeMinds. LikeMinds and Portal Personalization will drop this tablespace during uninstallation of LikeMinds and certain database transfer tasks.

 

Database considerations

When creating Oracle RAC databases for use with WebSphere Portal, you should consider the following information:

• The Oracle RAC databases must be created manually before configuring WebSphere Portal.

• All databases to be used with WebSphere Portal must be created as UTF-8 character set databases.

• Determine if the Oracle RAC server will be remote or local to the WebSphere Portal installation.

• After installing the database software for WebSphere Portal, set the buffer pools allocated to the Oracle RAC database in order for WebSphere Portal to communicate with the DB2 Content Manager Runtime Edition database. Use the following recommended values as a guide. Refer to Oracle product documentation for information on how to set the buffer pools. Recommended initial buffer pool sizes:

      db_block_size = 8192 
      db_cache_size = 300M
      shared_pool_size = 200M
      pre_page_sga = true     pga_aggregate_target = 200M
      db_files = 1024
      open_cursors = 1500
      processes = 300
      log_buffer = 65536
  

 

Set up databases and users

You must create the databases that you are planning to use, create users, and grant privileges before we can configure WebSphere Portal to use the database. After you finish setting up the databases, you should continue to Transferring Oracle RAC manually.

See Plan for Oracle RAC for database and user names.

 

Create Oracle RAC databases

A database might have several instances in RAC.

If when running the transfer-database task you get an error like...

action-drop-jcr-tables:
Wed May 16 18:27:35 CDT 2007
     [echo] Calling cmcfgdbu to drop LS tables      [echo] In case of error, refer to /u01/wp6/PortalServer/log/dbname.log
     [java] 2007-05-16 18:27:37 cmcfgdbu: ERROR ->Failed to connect to dbname
     [java] com.ibm.cm.dbutil.ICMDBUtilsException: Failed to connect to dbname
     [java]     at com.ibm.cm.dbutil.ICMConfigureLSDB.dropSchema(ICMConfigureLSDB.java:2168)
     [java]     at com.ibm.cm.dbutil.ICMConfigureLSDB.configureLSDB(ICMConfigureLSDB.java:1676)
     [java]     at com.ibm.cm.dbutil.ICMConfigureLSDB.start(ICMConfigureLSDB.java:2399)
     [java]     at com.ibm.cm.dbutil.cmcfgdbu.startSilentMode(cmcfgdbu.java:145)
     [java]     at com.ibm.cm.dbutil.cmcfgdbu.startConfig(cmcfgdbu.java:200)
     [java]     at com.ibm.cm.dbutil.cmcfgdbu.main(cmcfgdbu.java:216)

BUILD FAILED
file:../config/actions/jcrdb_cfg.xml:174: Java returned: 202

Total time: 12 minutes 31 seconds ictportal02:/u01/wp6/PortalServer/config#

...the solution is to create an instance with the same name as the RAC database....

 

Verify the status of all the instances

    SQL> select * from v$active_instances;
    INST_NUMBER    INST_NAME

    node1:instance1
    node2:instance2

 

Parent Topic

Configure Oracle RAC

 

Previous topic

Install Oracle RAC

 

Next topic

Transfer Oracle RAC

 

---