Chris Slattery oracle and Miscellaneous tech Blog: Upgrading to Oracle Cloud Control 12.1.0.5 Cloud Control

OK so we'll do a few posts on running the upgrade process

So go to http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html

and download the software ( this will be on Linux 64 bit )

You download three large zip files ; create a directory and unzip them all into it. You will end up with the typical large Oracle staging directory tree.

... so run the Installer

As usual we do not want to receive security updates at this point so deselect the option and remain "uninformed".

We also wish to skip software updates as this is a brand new product

It now runs some checks to see if it is a supported system platform

If it turns out that ulimit is needing fixing then don't forget to look in a: limits.conf and b : limits.d - this is a recent EL change in how userlimits are broken out. ( limits.conf now takes a back seat )

Note that if you do need to do this in a vnc window you'll need to exit the installer, kill VNCserver and restart it to make the env change be picked up, but this should be a fairly quick change

Now everything works

In the next screen we want to do a 1-system upgrade ( that is all that is supported, we see the existing OMS in the list below )

On the next screen you are ( really confusingly ) asked to select a middleware home. It does not tell you if this is an existing one or a new one ( since it is an upgrade process you do not know ) . We will hope it is a new one. Reading the documentation does not make it any clearer.

We will try for a new directory as it does not seem to like the old one

On the next screen enter the sys password for the DB ::

You will get a warning to apply some possibly mandatory patches.

( see http://docs.oracle.com/cd/E24628_01/upgrade.121/e22625/toc.htm )

These may not be mandatory ( e.g 11.2.0.4 )

If you have checked and they are OK , click OK and next

OK now we are warned about emkey not being copied :

OK so we can fix this by

oracle@ebscloud ~]$ source oms_home.sh

[oracle@ebscloud ~]$ emctl config emkey -copy_to_repos -sysman_pwd xxxxxx

Oracle Enterprise Manager Cloud Control 12c Release 4

The EMKey has been copied to the Management Repository. This operation will cause the EMKey to become unsecure.

After the required operation has been completed, secure the EMKey by running "emctl config emkey -remove_from_repos".

[oracle@ebscloud ~]$

OK Let's try again

click back through the last two screens and now

Click YES

We get some warnings, let's fix them .. first one should be easy by running utlrp on the database to recompile the brokens

so this leaves the EM triggers problem

Looking in Metalink doesn't help. Searching the logs in emdbprereqs shows some SQL which if we run it

select trigger_name, trigger_type, table_name from (select trigger_name, trigger_type, table_name from DBA_TRIGGERS where table_owner ='SYSMAN' and status = 'DISABLED');

TRIGGER_NAME TRIGGER_TYPE TABLE_NAME

------------------------------ ---------------- ------------------------------

EM_ASSOC_INS_TRIG AFTER EACH ROW MGMT_ASSOC_INSTANCES

EM_ASSOC_DEL_TRIG AFTER EACH ROW MGMT_ASSOC_INSTANCES

SQL>

Interesting. Why are they disabled; a search in Metalink shows someone else has had the problem but no fix was ever done. Let's enable them and see what happens

SQL> alter trigger EM_ASSOC_INS_TRIG enable;

Trigger altered.

SQL> alter trigger EM_ASSOC_DEL_TRIG enable;

Trigger altered.

SQL> select trigger_name, trigger_type, table_name from (select trigger_name, trigger_type, table_name from DBA_TRIGGERS where table_owner ='SYSMAN' and status = 'DISABLED');

no rows selected

SQL>

OK let's have another go at the above

Press Cancel, then Next

It still recurs; I think there is a bug here . even though there are no triggers disabled ( there are SYS triggers yes, but there is a specific note from metalink NOT to enable them )

so just press OK