As Oracle announce in there MOS Note 793512.1 EM 12c Cloud Control will be release in Q4. I would have bet it comes on 31 December, but Oracle just released EM12c for SPARC Solaris as well as for Solaris x86_64. I’ve just stated to download the software. Like for Linux there also two ZIP archive for each solaris release. Total size for each OS is almost 6GB. In addition to EM12c you have to download Oracle database 11g if you haven’t done it yet.
Ok, here are the links and information related to EM12c for Solaris:
Beside the EM12c downloads, there are also EM12c agents as separate download for Linux x86 (32-bit), Linux x86-64 (64-bit), Solaris Operating System (SPARC) and Solaris Operating System (x86-64) available. Download URL’s and documentation is available at the OTN page Enterprise Manager Agent Downloads. Each agent is about 250MB but these files can not be used to install a fresh 12.1 agent. This file will be used by 12.1 Self Update feature in offline mode. For information on using the Self Update feature, refer to the Oracle Enterprise Manager Cloud Control Administrator’s Guide.
Mmh, now I just need a solaris test box to start with EM12c…
I was on leave for the past few weeks. After digging through tons of e-mails I finally found time to look into EM 12 Cloud Control. Unfortunately, I’ve forgotten my SYSMAN password and the EM 12c test installation is no longer running. As you say: “Holidays where one forgets everything, must be good holidays.”
So far so good, but what about my problems. Lets start with EM 12c which is not running. I started the VM from scratch. After login in over ssh I’ve realized that the EM 12c infrastructure is running. To my surprise the installer configured the start / stop script gcstartup in /etc/init.d and the corresponding rc directories. The script exists already since EM 10g but I’ve never used it. Unfortunately nobody created the start / stop script for the database and the listener. As soon as starting them manually I’ve just have to bounce the EM 12c to be up and ready again. It is not enough to just start the database. Restarting or starting the OMS is also necessary due to the fact that the OMS is not started when the database is not available during the startup of EM 12c. Oracle described this in a MOS Note EM Cloud Control 12c OMS not able to start after server reboot [1367876.1]
My second problem is quite a common issue. You’ll find some notes on how to change the SYSMAN password for EM 10/11g, DB Console and new as well for EM 12c. Basically it is done in a similar way as in EM 11g. It is just a little easier because it is not necessary to do the change in two steps. You may use use emctl to change the SYSMAN password for the OMS infrastructure and well the database account. That’s also what you can specify the SYS password when using emctl.
- Stop all OMS: emctl stop oms
- Change the password: emctl config oms -change_repos_pwd -use_sys_pwd -sys_pwd sys user password -new_pwd new sysman password
- Stop the Admin server and restart all OMS: emctl stop oms -all; emctl start oms
An example output:
emctl config oms -change_repos_pwd -use_sys_pwd -sys_pwd manager -new_pwd tiger
Oracle Enterprise Manager Cloud Control 12c Release 188.8.131.52.0
Copyright (c) 1996, 2011 Oracle Corporation. ALL rights reserved.
Changing passwords IN backend ...
Passwords changed IN backend successfully.
Updating repository password IN Credential Store...
Successfully updated Repository password IN Credential Store.
Restart ALL the OMSs USING 'emctl stop oms -all' AND 'emctl start oms'.
Successfully changed repository password.
More information on these topic’s can be found in the following MOS notes:
- 12C Cloud Control: Steps to Modify the SYSMAN Password at OMS and Repository [1365930.1]
- How to Change the Password of SYSMAN User in 10g and 11g Grid Control? [270516.1]
- EM Cloud Control 12c OMS not able to start after server reboot [1367876.1]