+

Search Tips   |   Advanced Search

Create Oracle databases manually


Overview

Create Oracle databases with SQL scripts instead of the database wizard.

The SQL scripts archive file is located under...

When extracted, SQL scripts are created in...

...where application is the directory containing the SQL scripts for each application.

If the database server and Connections are installed on different systems, copy the SQL scripts to the system hosting the database server.

Specify the Unicode AL32UTF8 character set.

To capture the output of each command to a log file, run...

After completing the task below, run:


Manually create the application database, and tables

  1. Log in with the same user ID used to install the Oracle database system.

  2. Create an Oracle user ID with system database administrator privileges.

    Alternatively, use an existing ID that has administrative privileges, such as SYS.

  3. Start SQL Plus:

      ORACLE_SID=mySID
      export ORACLE_SID
      sqlplus /NOLOG

  4. Log in as an administrator with the sysdba role ...

      connect as sysdba

    If not logged in as sysdba, the statistics gathering job for the Bookmarks database is not created or correctly scheduled. As a result, database performance is impacted.

  5. Enter the Oracle user ID and password.
  6. Files only: Create tables for Push notification:

      @application/pns-createDb.sql password
      @application/pns-appGrants.sql

  7. Create the application database tables:

      @application/createDb.sql password

    Repeat this step for each Connections application to install.

    The createDB script creates a dedicated user ID for the JDBC connector for an application database. Later, when we run the Connections installation wizard, provide the user ID specified in this step.

      Database Default user ID
      Activities OAUSER
      Blogs BLOGSUSER
      Bookmarks DOGEARUSER
      Cognos COGNOS
      Communities SNCOMMUSER
      Files FILESUSER
      Forums DFUSER
      Global Configuration Database
      Connections Content Manager       		FNGCDUSER
      Home page HOMEPAGEUSER
      Metrics METRICSUSER
      Mobile MOBILEUSER
      Object Store
      Connections Content Manager       		FNOSUSER
      Profiles PROFUSER
      Wikis WIKISUSER

    Each of these default user IDs has a narrower set of privileges than an administrative user ID.

    We can change the passwords for these database users later in Oracle Enterprise Manager Console. If we change the passwords there, also change them in the J2C authentication alias settings in the WAS console.

    If we plan to install the Metrics application, we can create the database now but the tables are not created until you start the Cognos BI Server for the first time.

  8. Communities only:

      @application/calendar-createDb.sql
      @application/calendar-appGrants.sql
  9. Dogear only:

      @application/createHistogramStatsJob.sql

    This script creates a job to collect histogram statistics.

    Run this command while logged in with the SYS ID.

    For this command to run successfully, grant the following privileges to the DOGEAR account...

      grant ANALYZE ANY DICTIONARY
      grant ANALYZE ANY system

  10. Home page only...

      @application/initData.sql

  11. Grant access privileges for each application:

      @application/appGrants.sql

    For Connections Content Manager, the appGrants.sql scripts in libraries.gcd and libraries.os require a password for FNGCDUSER and FNOSUSER. Runs:

      libraries.gcd/oracle/appGrants.sql password
      libraries.os/oracle/appGrants.sql password

  12. Close the SQL Plus window.


Parent topic:
Create databases with SQL scripts