Enable Enterprise Manager on the Oracle E-Business Suite Release 12

Enable Enterprise Manager on the Oracle E-Business Suite Release 12

Keep the database and listener running. It is not necessary that any other Application services to be running for this process to complete.

- As the owner of the 10gR2 ORACLE_HOME, run the following command to create the Enterprise Manager repository:

$ emca -config dbcontrol db -repos create

When the command is run, EMCA prompts for the following values

Database SID: VIS
Listener port number: 1521

Password for SYS user: xxxxxxxxxx
Password for DBSNMP user: xxxxxxxxxx
Password for SYSMAN user: xxxxxxxxxx
Email address for notifications (optional):Outgoing Mail (SMTP) server for notifications (optional):
- Enter the values

- EMCA shows a summary of the entered values

—————————————————————–
You have specified the following settings

Database ORACLE_HOME ……………. /orahome/oravis/db/tech_st/10.2.0

Database hostname ……………. Si3test.erp.com
Listener port number ……………. 1521
Database SID ……………. VIS
Email address for notifications ……………Outgoing Mail (SMTP) server for notifications —————————————————————–

Do you wish to continue? [yes(Y)/no(N)]: Y

- Type ‘Y” to start the configuration.
The configuration will take anywhere between 10 min to an hour depending on the machine configuration and database size.

Once it gets completes Enterprise manager can be accessed from the URL

http://localhost.domain.com:1158/em

Troubleshooting 

$ emca -config dbcontrol db -repos create
STARTED EMCA at Sep 27, 2005 2:08:57 PM
EM Configuration Assistant, Version 10.2.0.2.0 Production
Copyright (c) 2003, 2005, Oracle.  All rights reserved.
Enter the following information:
Database SID: VIS
Listener port number: 1521
Password for SYS user:
Password for DBSNMP user:
Invalid username/password.
Password for DBSNMP user:
Invalid username/password.
Password for DBSNMP user:
Invalid username/password.
Password for DBSNMP user:
Invalid username/password.
LOG FILE
----------
emca_2005-09-28_10-09-54-AM.log
Sep 28, 2005 10:13:40 AM oracle.sysman.emcp.util.GeneralUtil initSQLEngine
CONFIG: SQLEngine connecting with SID: ldb009, oracleHome: /oracle/app/10.2.0, and user: SYS
Sep 28, 2005 10:13:40 AM oracle.sysman.emcp.util.GeneralUtil initSQLEngine
CONFIG: SQLEngine created successfully and connected
Sep 28, 2005 10:13:40 AM oracle.sysman.emcp.DatabaseChecks validateUserCredentials
CONFIG: Failed to update account status.
oracle.sysman.assistants.util.sqlEngine.SQLFatalErrorException: ORA-01034: ORACLE not available
 at oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeImpl(SQLEngine.java:1467)
 at oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeQuery(SQLEngine.java:694)
 at oracle.sysman.emcp.DatabaseChecks.updateAccountStatus(DatabaseChecks.java:1040)
 at oracle.sysman.emcp.DatabaseChecks.validateUserCredentials(DatabaseChecks.java:1013)
 at oracle.sysman.emcp.ParamsManager.validatePassword(ParamsManager.java:2694)
 at oracle.sysman.emcp.EMConfigAssistant.promptForData(EMConfigAssistant.java:583)
 at oracle.sysman.emcp.EMConfigAssistant.promptForParams(EMConfigAssistant.java:2231)
 at oracle.sysman.emcp.EMConfigAssistant.displayWarnsAndPromptParams(EMConfigAssistant.java:2257)
 at oracle.sysman.emcp.EMConfigAssistant.getDisplayAndPromptWarnsParms(EMConfigAssistant.java:2284)
 at oracle.sysman.emcp.EMConfigAssistant.performConfiguration(EMConfigAssistant.java:928)
 at oracle.sysman.emcp.EMConfigAssistant.statusMain(EMConfigAssistant.java:463)
 at oracle.sysman.emcp.EMConfigAssistant.main(EMConfigAssistant.java:412)

Cause

This error is mainly due to profile limits which prevent emca to reset the password for any of the following:

• SYSMAN
• DBSNMP
• MGMT_VIEW

In Release 10.1, emca resets the password with the one provided at prompt:

• SYSMAN => Always
• DBSNMP=> Always
• MGMT_VIEW=> Always

In Release 10.2, emca resets the password with the one provided at prompt:

SYSMAN => If password expired
DBSNMP=> If password expired
MGMT_VIEW=> Always

If the user has a profile limit for the resource type PASSWORD which is violated by the password provided, then emca will fail with the error "Invalid username/password".
In Release 11G, emca will prompt for the password only if the account is EXPIRED & LOCKED or if the account does not exist.
If the password is required, and if the password provided does not meet the password policy for the user profile, the error message will clearly state that there is a policy violation.

Solution

·         In order to fix the Invalid username/password message

select u.username, u.profile, p.resource_name, p.limit
from dba_profiles p, dba_users u
where p.profile=u.profile
and u.username in ('DBSNMP')
and p.resource_type = 'PASSWORD'
order by u.username, p.resource_name;

USERNAME   PROFILE    RESOURCE_NAME                  LIMIT

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

DBSNMP     DEFAULT    FAILED_LOGIN_ATTEMPTS          10

DBSNMP     DEFAULT    PASSWORD_GRACE_TIME            UNLIMITED

DBSNMP     DEFAULT    PASSWORD_LIFE_TIME             UNLIMITED

DBSNMP     DEFAULT    PASSWORD_LOCK_TIME             UNLIMITED

DBSNMP     DEFAULT    PASSWORD_REUSE_MAX             UNLIMITED

DBSNMP     DEFAULT    PASSWORD_REUSE_TIME            UNLIMITED

DBSNMP     DEFAULT    PASSWORD_VERIFY_FUNCTION       NULL

7 rows selected.

• If the value of LIMIT for PASSWORD_VERIFY_FUNCTION is not NULL:
  Change the password so that it meets the function requirements.
• If the value of LIMIT for PASSWORD_REUSE_MAX is not UNLIMITED:
  Change the password so that it is different from a password that has already been used the number of times set in PASSWORD_REUSE_MAX.
  Or
  Change the value of LIMIT for PASSWORD_REUSE_MAX to UNLIMITED for the profile.

2^nd solution very 

useful 

Solution

Workaround:
When the emca command prompts for the dbsnmp,sysman password, provide the dbsnmp, sysman password in double quotes. Like this “dbsnmp” “sysman”

Error:

ORA-01034: ORACLE not available

Solution

There was an extra "/" in ORACLE_HOME environment variable setting
and the database was started with this setting.
eg: ORACLE_HOME=”/orahome/oravis/db/tech_st/10.2.0/”
Remove “/”
Change : ORACLE_HOME=”/orahome/oravis/db/tech_st/10.2.0”.

Restart emca 

Reference Metalink Doc ID: 458533.1

Syed Shabuddin

Technical Consultant