Installation and configuration of EM in Oracle 10g and 11g

Installation and configuration of EM in Oracle 10g and 11g

I set up an Oracle environment locally. I first installed the database with EM. After the installation, I wanted to modify the listener port and replace the port 15521 with another one, as a result, several parameter files are modified in the directory, and EM cannot be started directly. Finally, I analyzed it myself. In fact, there are several ways to change the password.

One is to directly Delete EM and then recreate it. You can use emca-deconfig dbcontrol db-repos drop to delete it, and then re-create EM through emca-config dbcontrol db-repos create,

Another method can be achieved through the graphical interface, which is more intuitive and clear.

There is also one of the most troublesome, and the most stupid way is to delete the database, rebuild the database, do not select EM installation, and then manually install EM after the database is rebuilt.
Because it takes a long time to wait for the first method, the third method is selected. As a result, some problems are encountered during EM creation. In fact, there are still a lot of details about a simple job. You have spent a lot of time on it.

First, you can use emca-config dbcontrol db-repos create to create EM in a 10 Gb environment.

EM in 10g is relatively simple. If the creation fails due to various reasons, it is very likely that the sysman user has not deleted the re-creation, and there are still some role and public synonym.

Relatively speaking, these problems are well-regulated. Basically, the configuration of the 10gEM is as powerful as the following method. The configuration of the 10gEM is clean and the reinstallation process is smooth.
Drop user sysman cascade;
Drop user MGMT_VIEW cascade;
Drop role MGMT_USER;
Drop public synonym MGMT_TARGET_BLACKOUTS;
Drop public synonym SETEMVIEWUSERCONTEXT;

Then reconfigure and use emca-config dbcontrol db-repos create

However, EM in the 11g encountered many problems using the same method.
First, we can see the following errors in the log.
Apr 6, 2015 9:33:45 oracle. sysman. emcp. util. GeneralUtil initSQLEngineLoacly
CONFIG: ORA-28000: the account is locked

CONFIG: ORA-20001: SYSMAN already exists ..
ORA-06512: at line 17

Further Check the log. It is found that DBSNMP is locked and sysman is created by default. Unlock DBSNMP, delete sysman, and then use the clean-up method of 10 Gb. Another error is returned.
Create public synonym MGMT_AVAILABILITY FOR MGMT_AVAILABILITY
*
ERROR at line 1:
ORA-00955: name is already used by an existing object
From this we can see that there are some differences between 10g and 11g.
The public synonoym MGMT_AVAILABILITY is cleared, and the EM reinstallation fails. At this time, another MGMT synonym error is reported.
Finally, we can use select * from dba_synonyms where synonym_name like 'mgm % 'to view the public synonym related to the associated MGM. We found that there are more than 300 public synonym, these public synonym cannot be deleted by dropping user sysman cascade. You can only delete them.
From this details, we can see that some configuration details in 10g and 11g EM are still very different.
After the public synonyms related to MGMT _ are deleted, we thought it could be done smoothly, and the SMP_EMD_AVAIL_OBJ problem was thrown out.
Create public synonym SMP_EMD_AVAIL_OBJ FOR SMP_EMD_AVAIL_OBJ
*
ERROR at line 1:
ORA-00955: name is already used by an existing object

Finally, we can use this SQL statement to check which Common synonyms are used to clean up sysman.
Select 'drop' | OWNER | 'synonym' | SYNONYM_NAME | ';' from dba_synonyms where TABLE_owner = 'sysmanc ';

It is found that there are nearly 20 such public synonym
After cleaning up again, the installation of EM is successfully completed.
However, when you want to view it through a browser, you will find that the default https protocol is used, and some certificate and security problems are encountered locally and remotely. It is easier to use http. You can use the unsecure method to solve the problem.
[Ora11g @ oel1 ~] $ Emctl unsecure dbconsole
Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
Copyright (c) 1996,200 9 Oracle Corporation. All rights reserved.
Https://oel1.oracle.com: 5500/em/console/aboutApplication
Refreshing DBConsole for HTTP... Done.
DBCONSOLE successfully stopped... Done.
Agent is already stopped... Done.
Unsecuring dbconsole... Started.
DBConsole is now unsecured... Done.
Unsecuring dbconsole... Sucessful.
DBCONSOLE successfully restarted... Done.
Let's take a look at the differences and improvements of EM in 10g and 11g.
The functional menus in 11G are much more detailed and more targeted than 10g. I want to put the data movement section in the maintenance Section of 10g Chinese style, A module is extracted from the 11g. It can be seen that this Part has been added and paid more attention in the 11g.
11g new SPA, SPM listed separately in the "software and Support" section, other features are indeed enriched.