+

Search Tips   |   Advanced Search

Oracle: Database transfer

Portal is installed with an Apache Derby database. The database that is immediately available for use is good for demonstration and portlet and theme development environments. Otherwise, configure portal to use a production-level database. We can use the Configuration Wizard to transfer the data and configure a new database server.

Before doing portal database transfer, increase DB transaction log size.


Configuration Wizard

The primary Configuration Wizard options are based on the target configuration topology, such as a stand-alone server or a cluster. The database transfer option is included with both...

  • Set Up a Stand-alone Server
  • Set Up a Cluster

For the stand-alone server topology, run the database transfer option before running the federated security option. For the cluster option, run the database transfer before creating the deployment manager profile.

See: Oracle worksheet: Transfer the database


Transfer data to a different database server

Depending on the environment, the wizard generates a configuration process. The following steps reflect all possible steps in the configuration process. The steps do not represent a literal configuration. The steps are provided as a reference.

If we click View Step Command, we can see the task and properties associated with each step in the wizard.

  1. Back up the properties files the wizard uses during the configuration.

      Condition None
      ConfigEngine task backup-property-files-for-dbxfer

  2. Manual Step: Create the Oracle database.

      Condition None
      ConfigEngine task None

  3. Manual Step: Create the data directory, data, and the index directory, index, on the database server.

      Condition Select to manually create users and assign them permissions.
      ConfigEngine task None

  4. Set up the database.

  5. Manual Step: Download the script and run it on the database server to set up the database.

      Condition Select to manually create users and assign them permissions.
      ConfigEngine task None

  6. Validate the database connection and environment.

      Condition None
      ConfigEngine task validate-database validate-database-environment

  7. Stop the portal server.

      Condition collation support
      ConfigEngine task stop-portal-server

  8. Transfer the database.

      Condition None
      ConfigEngine task database-transfer enable-profiles-check-managed package-profiles

  9. Grant privileges to the database runtime users.

      Condition None
      ConfigEngine task grant-runtime-db-user-privileges

  10. Manual Step: Download the script and run it to grant the database runtime user the appropriate privileges to work with database tables.

      Condition Select to manually create users and assign them permissions.
      ConfigEngine task None

  11. Manual Step: Improve database response time for the database containing the JCR domain.

      Condition None
      ConfigEngine task None

  12. Start the portal server.

      Condition None
      ConfigEngine task start-portal-server


Parent Database Management Systems