Please repeat this for all the datasources.
For example: Click on emgc-sysman-pool > Connection Pool tab > Enter Password and Confirm Password as formula1Īnd Save each change. Click on “Lock and Edit” on top corner left side. Here you will have list of all datasources. From the admin console, Leftpanel > Services > Datasources OMS_HOME/bin>./emctl start oms -admin_only 3. If the weblogic admin server is not up, then start it using: Įnter ‘weblogic’ as the username and its password. Take a backup of the directory /app/oracle/product/middleware/gc_inst/user_projects/domains/GCDomain/config/jdbc 2. Used “/app/oracle/product/middleware/gc_inst/user_projects/domains/GCDomain/config/jdbc/*” to find details. Providing logs to Oracle Support we came to know that there is mismatch of the information in JDBC xml files. Check error and log files.ĮM log files: /app/oracle/product/middleware/gc_inst/em/EMGC_OMS1/sysman/log/emctl.log, c, bin]$ Oracle Management Server is not functioning because of the following reason: Starting Oracle Management Server... Starting WebTier... With the Partitioning, OLAP, Data Mining and Real Application Testing options Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 – 64bit Production Now I had to open case with MOS and they guided me to reset the password of all four dependent users “sysman, sysman_apm, sysman_mds, sysman_opss” to common password and then try to start oms, so I did. emctl config oms -change_repos_pwd -use_sys_pwd -sys_pwd formula123 -new_pwd formula1 I started Admin server using ” >emctl start oms -admin_only”įollowed by this I again tried to reset the sysman password using “EMCTL” but again no luck ? bin]$. : Connection refused No available router to destination 07:03:33,854 ERROR oms.ChangeReposPwd logp.251 –Īt .ClientProviderBase.makeConnection(ClientProviderBase.java:178)Ĭaused by: : t3s://:7102: Destination unreachable nested exception is: 07:03:33,851 INFO util.EmctlUtil logp.251 – Unable to get mbean conn over t3s :null 07:03:33,221 INFO util.EmctlUtil logp.251 – Connecting over t3s to: /7102 using id: weblogic 07:03:33,218 INFO oms.AdminCredsWalletUtil setInstanceHome.192 – Read the credentials from wallet 07:03:32,915 INFO oms.AdminCredsWalletUtil setInstanceHome.177 – Getting credentials from wallet
I checked the logs and find that my “Admin Server” was not up and running but even after bringing Admin Server up I was not allowed to change password. Check the log /app/oracle/product/middleware/gc_inst/em/EMGC_OMS1/sysman/log/secure.log Oracle Enterprise Manager Cloud Control 12c Release 4Ĭopyright (c) 1996, 2014 Oracle Corporation. emctl config oms -change_repos_pwd -use_sys_pwd -sys_pwd formula123 -new_pwd formula123 So next thing I tried was reset SYSMAN password using “emctl” bin]$. The ONLY way to change SYSMAN password is using emctl command. Key Point to remember is that “SYSMAN” password should not be changed directly in repository database. Verify that the repository connection information provided is correct.” “failureReason: DB Connection service is invalid or temporarily unavailable” and “ERROR commands.BaseCommand logAndPrint.623 – Oracle Management Server is not functioning because of the following reason:Ĭonnection to the repository failed. Something like this popped up in the logs. This led the OMS not to connect with the repository. When I explored the logs I came across that some has changed the repository credentials for SYSMAN, which was done at the backend and was not synchronized with the OMS.
Since it was running fine earlier but this time when I start OMS using the command “>emctl start oms” it failed. Recently one issue blew my mind off, when all of a sudden my OEM test environment failed to startup.