For information on adding view currencies, refer to the
“Defining Administrative Preferences and Categories”
chapter of the Project Management Reference Manual.
The base currency is the monetary unit used to store cost data for all projects in the database and is controlled by a global administrative setting in the Project Management module. The default base currency for Primavera is US dollars ($). The view currency is the monetary unit used to display cost data in Primavera and is controlled by a user preference.
The exchange rate for the base currency is always 1.0. When a user selects a different currency than the base currency to view cost data, the base currency value is multiplied times the current exchange rate for the view currency to calculate the values displayed in cost and price fields.
For example, if the base currency is U.S. Dollars, the view currency is Euros, and the exchange rate for Euros is .75, a value of $10 stored in the database is displayed as 7.5 Euros in cost and price fields. Similarly, if you enter 7.5 Euros in a cost or price field, it is stored in the database as $10.
When data is displayed in a view currency that is different than the base currency, some cost and price values may vary slightly (e.g., due to rounding). As long as the correct base currency is selected during database installation, a user can view completely accurate cost and price data by changing the view currency to match the base currency.
6 On the Select Application Database dialog box, choose the database for which you are installing data.
7 On the Select Installation Method dialog box:
• Choose Create database and load application data.
• Decide whether to mark Load license key file.
• If you choose to load the license key file now, browse to the location of the LICENSE.TXT file. If the LICENSE.TXT file is not available at this time, you can clear this checkbox and load the file later using the Database wizard. Refer to “Changing Database Configuration Settings” on page 299 for more information.
8 On the Oracle Server Details dialog box:
• In the DBA Username field, type the Oracle system user name to log on to the database; for example, system (which is the default).
• In the DBA Password field, type the password to log on to the database. If you chose system for the DBA Username, use manager as the password. Otherwise, enter the password associated with the Username you entered.
• In the Oracle connect string field, enter the Oracle connect string. It can be found in the TNSNAMES.ORA file. The TNSNAMES.ORA file is created when you or your DBA set up the Oracle client.
9 On the Configure Oracle Tablespaces dialog box, click Next to accept the name for the Data, Index, and LOB tablespaces and estimated tablespace sizes.
The wizard automatically names the tablespaces using the Oracle connect string you previously specified as the prefix (for example, PMDB).
You can change the estimated tablespace sizes. Refer to “Project Management Database Server Sizing Guide” on page 21 for guidelines on sizing.
Mark Use existing tablespaces only if the database to which you are connecting already has existing tablespaces. For a new database, do not mark this option.
10 On the Configure Oracle Tablespaces dialog box, accept the default location for the Oracle tablespaces, Data, Index, and LOB, or specify different locations.
11 On the Configure Oracle Users dialog box, accept the default names for the Oracle administrative user, privileged user, and public user, or specify the appropriate names. If necessary, choose a different default tablespace and temporary tablespace from the dropdown list.
You cannot enter PRIVUSER as the administrative username;
doing so will cause conflicts.
You can choose a default tablespace from the dropdown list in the Default Tablespace field. In the Temporary Tablespace field, use the temporary tablespace that you created prior to starting this procedure.
The temporary tablespace must be of temporary type;
otherwise, errors can occur to your database.
12 On the Ready to Begin Creating Database Structure dialog box, choose Yes, I want to create database tables and structure.
If the database creation fails before completion, a Database Creation Failed dialog box appears with messages stating the errors. Click Copy to Clipboard on this dialog box to record the messages and contact Customer Support for more information.
13 On the Load Application Data dialog box, click Next to start the process of loading the database tables with application data.
When the process has completed, the message “Data Loading Completed” appears. Click Finish to exit the wizard.
14 If prompted, run the RUN_AS_SYS.SQL and GATHER_STATS.SQL scripts. If you are not prompted, you can access these scripts in the
\install\database folder on CD 1.
Running these scripts will improve database performance.
The V_$TRANSACTION table stores the earliest login time that data was changed. This improves performance when refreshing data because data before that login time is not accessed. Users must have access to view the V_$TRANSACTION table.
Otherwise, the earliest login time cannot be viewed and redundant data is accessed which causes slower performance.
To grant access to this table, run the RUN_AS_SYS.SQL script when prompted.
Oracle 10g and later supports only cost-based optimization, which relies on accurate statistics to determine the optimal access path for a query. To gather the appropriate statistics for the optimizer, run the GATHER_STATS.SQL script.
15 Run the Database wizard again if you will be using the Methodology Management module.
Once both sets of application data are installed (Project Management and Methodology Management), you can begin to install client modules and additional components. Refer to Part 3 and Part 4 for more information on configuring the servers and installing client module(s) and additional components.