Maintenance Notice - PDF Generation
Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.

Note: Access to static files, including PDF files that are not dynamically generated from our web-based content, is unaffected.

Jump to: navigation, search

Creating the Oracle Schema for Advisors

This page describes how to create a generic Oracle schema for Advisors. Each individual Oracle schema in an Advisors implementation has its own creation script in the 8.5 release.

In 8.5.x releases, all Oracle scripts are creation scripts except those that contain the word migrate in the name. Any existing schema with the same name must be dropped prior to running the scripts. Use the migration scripts when upgrading your software version.

If, due to security restrictions, administrator or security administrator access cannot be granted, the local Database Administrator (DBA) should implement the steps described in the procedure.

The procedure applies to an Oracle user who has permissions to create tablespaces, users, and to grant permissions. Follow your enterprise’s policies in production environments. If necessary, have the DBA create tablespaces, users, and grant permissions. Use scripts relevant to your environment after the DBA completes the work. Refer to the script content description contained in Advisors Software Distribution Contents.

[+] See recommended database names.


Before You Begin=

You must perform all the steps in the procedure on a machine where you have Oracle client installed. The installation scripts require SQLPlus which is installed as part of Oracle client installation. Please verify that you have your ORACLE_HOME environment variable and tnsnames.ora content set properly. Verify the connectivity to the instance by running the following command line:
tnsping <alias for the oracle instance contained in the local tnsnames.ora file>

It is important to use <alias for the oracle instance contained in the local tnsnames.ora file> as a response on all prompts where the database scripts ask you to <Enter the database instance alias>.

For example:
Your tnsnames.ora contains the following entry:

wolf =
    (ADDRESS = (PROTOCOL = TCP)(HOST = = 1521))

To check the connectivity type:

C:>tnsping wolf

The successful message will look as follows:

Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = = 1521)) 
OK (0 msec)

|-| Procedure=

Procedure: Creating the Advisors Oracle Schema


  1. Copy all of your Oracle database scripts to a folder on the machine where you have the Oracle client installed. The path name for this location must not contain spaces.
  2. On the machine where the Oracle client is installed, open a command prompt and change directory to the folder where the database scripts now reside.
  3. Review the readme files located in the script directories.
  4. Database scripts are encoded in Windows-1252 format. Before you start SQL*Plus, be sure to set your session to a value with this encoding. See the Oracle NLS_LANG FAQ for more information.
    Set the NLS_LANG variable and start SQL*Plus.
    The figure below shows an example of the commands for Linux and Oracle 11g.
    SQL Command Prompt
  5. Using a user account that has DBA privileges (for example, SYSTEM), enter the following at the prompt to connect to the Oracle instance:
    conn <User>/<Password>@<alias for the Oracle instance contained in your local tnsnames.ora file>
    See the following figure for an example of the command entry.
    SQL Command Prompt 2
  6. [ 35px
This page was last edited on August 14, 2019, at 13:50.


Comment on this article:

blog comments powered by Disqus