Enterprise Elements Upgrade Guide For Version 4.0

The following steps should be taken to insure a safe and simple upgrade to Elements 4.0:

1. Do backups before starting anything. It is recommended that you do a cold backup of the ORACLE directory (if possible) or at a minimum, an EE Disaster Recovery Backup (See Disaster Recovery Instructions)., and a backup of your Elements directory.

2. Before you run the installer to do the upgrade, we must first determine what version of Elements your running, and run a prep script to prepare the system for upgrading.

To determine what version of Elements you’re currently running, examine your current Login Screen.

You are running version 1.1 if your current login page looks like this:

Versions 2.0 and above show the version number on the login page.

4. Open a dos box and change your current directory to the Elements install CD. From there go to the /upgrading directory.

5. From there, log into SQL*Plus as the EE user.

6. If you are running Version 1.1, you need to run the following command:

@ Pre_Upgrade_From_1.1.sql

If you are running Version 2.0, you need to run the following command:

@ Pre_Upgrade_From_2.0.sql

If you are running Version 2.1, you need to run the following command:

@ Pre_Upgrade_From_2.1.sql

Later versions do not need to run a Pre_Upgrade script.

7. Exit from SQL*Plus and close the dos box.

If upgrading from Versions 1.1, 2.0, 2.1, or 2.2 we need to make some modifications to the ORACLE initialization file (init.ora) (If you are upgrading from versions 3.0 and later, this should have already been done, if this wasn’t done as part of your last upgrade, please do this now.)

To make these changes, we need 4 things:

1. The SID of the database
2. The SYS password
3. The full path to your Oracle installation directory. (ex, D:\ORACLE)
4. To be physically at the database server, logged in and ready to type.

Find and Modify the Oracle Initialization file

To find the file we need to change, we need to go to the root Oracle install directory, usually called \ORACLE, be it on your C or D or E drive...

Within the \ORACLE directory, is a directory called ADMIN. And with in that may be several directories, one of which will have the same name as the SID of your EE database.

Within that directory, will be several other directories, and the one we want is calld pfile.

Within the pfile directory you should see a file called something like init.ora.xxxxxxxxxxx where the xs are all numbers.

Lets make a copy of that file and call it init.<SID>.ora (Where SID is the SID of your EE database).

Now we can edit that file (init.<SID>.ora) and make our changes there without chance of messing up the original.

One word of warning here….Change only those things listed in this document, and be very careful to use the values given…any mistakes here can cause serious damage to your database, perhaps even catastrophic data loss….(You did make a cold backup of the ORACLE directory before we started didn’t you ?) Double check any and all changes

made to this file.

Ok, with that out of the way, lets get to work…

We need to search for the line that contains the parameter: job_queue_processes.

If you see it, and the number is less than 10, please make it 10. If it is more than 10, please add 10 to that number.

If it doesn’t exist in the file, then we need to add it, so add this block of text to the bottom of the file:

###########################################

# Job Queues

###########################################

job_queue_processes=10

Next we need to search for the line that contains the parameter: open_cursors.

If you see it, and the number is less than 8000, please make it 8000. If the number is greater than 8000, then we are good to go and don’t need to change it.

If it doesn’t exist in the file, then we need to add it, so add this block of text to the bottom of the file:

###########################################

# Open Cursors Setting

###########################################

open_cursors=8000

Next we need to search for the line that contains the parameter: max_enabled_roles.

If you see it, and the number is not 148, please make it 148.

If it doesn’t exist in the file, then we need to add it, so add this block of text to the bottom of the file:

###########################################

# Max Enabled Roles

###########################################

max_enabled_roles=148

Once these three updates have been made, save the file in the same directory as the original init.ora.xxxxxxxxxxxxx file.

Next we need to use that file we just created and convert it into a SP file so Oracle knows what to do with it.

Create the Oracle SP Initialization File

1. First thing we need to do is insure that the webserver is shut down, and there are no users connected to the database via SQL*Plus, TOAD, or any other 3^rd party tool.
2. Then we need to shut the database down by logging into SQL*Plus as the sys user.
3. An easy way to do this is to run SQL*Plus, and at the login prompt, type in /nolog and press enter.
4. This will take you to the SQL prompt, but you are not logged into the database as anyone. From there we can now log in by typing: CONNECT SYS/<xxx> AS SYSDBA where <xxx> is your sys password.
5. Once connected, we shut the database down by typing SHUTDOWN IMMEDIATE. This is where it is important that no one is connected to the database….because the system will sit there and wait until everyone and everything is no longer connected.
6. If no one is connected, the system will return to the SQL prompt very soon. If this takes more than a min or so, someone is still connected, and they need to log out immediately.
7. Once you get the database shutdown , we can create the binary file by typing the following line in SQL*Plus:
8. CREATE SPFILE=’<x>:\ORACLE\ORA92\DATABASE\SPFILE<sid>.ORA’
9. FROM PFILE=’<x>:\ORACLE\ADMIN\<sid>\PFILE\INIT.<sid>.ORA’;
10. Where <x> is the drive Oracle is installed on, and <sid> is the ORACLE SID for your EE Database. For my test system, where the SID is TEST, and Oracle is installed on my D drive, my statements look like this:
11. SQL> connect sys/xxx as sysdba
12. Connected.
13. SQL> shutdown immediate
14. Database closed.
15. Database dismounted.
16. ORACLE instance shut down.
17. SQL> CREATE SPFILE='D:\ORACLE\ORA92\DATABASE\SPFILETEST.ORA'
18. FROM PFILE='D:\ORACLE\ADMIN\TEST\PFILE\INIT.TEST.ORA';
19. File created.
20. Now we can start the database back up by entering:
21. STARTUP;
22. And then leave SQL*Plus by entering EXIT.

Below lists screen shots of the installer running to complete the update (After the initial screens have been done already):

Note the Update Existing Elements Installation is checked, and the SYS User password, and Schema Owner password are required. Click Next to continue.

You can just click Next here, your Service shouldn’t need to change.

Need to make sure the Elements box is checked to install the update. If your upgrading from version 1.1, you also need to click the Enterprise Architecture (EA) option.

Then just click thru and the new files will be laid down,

and the update SQL script will be automatically run.

When the script is done, just click thru Next and then Done.