I encountered a situation where I was trying to
configure OEM Database Control (11.2.0.4) on Windows based system using command
similar to the following
emca
-config dbcontrol db -repos recreate
|
But command was always getting stuck for hours and
hours until I stop the configuration. Last line displayed at the command prompt
was “INFO: Uploaded configuration data successfully”. Emca log had last few
lines similar to the following
…
…
…
CONFIG:
Copying file D:\ORACLE\11204\rdbms\install\install.excl.emca.util.tmp to D:\ORACLE\11204\rdbms\install\install.excl
Oct
30, 2015 4:56:11 PM oracle.sysman.emcp.util.FileUtil addLine
CONFIG:
File D:\ORACLE\11204\rdbms\install\install.excl is successfully updated
Oct
30, 2015 4:56:11 PM oracle.sysman.emcp.util.PlatformInterface serviceCommand
CONFIG:
cmdType: 2
Oct
30, 2015 4:56:11 PM oracle.sysman.emcp.util.PlatformInterface isPre112Home
CONFIG:
oracleHome: D:\ORACLE\11204 isPre112Home: false
Oct
30, 2015 4:56:11 PM oracle.sysman.emcp.util.PlatformInterface serviceCommand
CONFIG:
Service does not exist
|
After several weeks of working (also involved oracle
support), I just realized that the Windows OS user name (that I was using to
log in to the system) started with a number (OS user name was similar to
0148-DBADMIN). I have seen same kind of issues while using an OS user on
windows that started with a special character ($, #, @ etc.).
I tried a different OS user (of course user must be
member of Administrator and ORA_DBA OS groups), and this time I was able to
configure OEM Successfully.
Moral
of the story: OS user being used to configure
Oracle/OEM should not have name starting with number of special character.
No comments:
Post a Comment