Oracle Enterprise Manager: Agent commands

Here is the list of Oracle Enterprise Manager (OEM) Agent basic commands -

1. Start EM agent - emctl start agent

2. Get EM agent status - emctl status agent

3. Stop EM agent - emctl stop agent

4. Find the timeout value of the EM agent - emctl status agent [TIMEOUT]

5. Upload of metrics from agent to the EM server - emctl upload agent

6. Display the status of the connection pools - emctl status agent dbconnections

7. Print the version of the EM agent - emctl getversion

Weblogic: Datasource error - Maximum Capacity of Pool

Error Details -

Error An error occurred during activation of changes, please see the log for details.
Error prepareUpdate failed for JDBC Module DSName: Cannot set Maximum Capacity of Pool DSName to (10), this value is lower than the configured Minimum Capacity of the pool (20).
Error Cannot set Maximum Capacity of Pool DSName to (10), this value is lower than the configured Minimum Capacity of the pool (20).

Occurs when -

While trying to activate the datasource connection pool changes (update of Minimum capacity and Maximum capacity), the above error is displayed.

Solution -

1. First make the changes to the Minimum capacity of the connection pool
2. Save and activate the changes
3. Change the Maximum capacity of the connection pool
4. Save and activate the changes
5. Restart the managed server for the changes to take effect

BEA-090403: Authentication for user denied

Error message from weblogic - 

<DATE> <Critical> <Security> <BEA-090403> <Authentication for user  denied>

<DATE> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user  denied

weblogic.security.SecurityInitializationException: Authentication for user  denied

        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:965)

        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)

        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)

        at weblogic.security.SecurityService.start(SecurityService.java:141)

        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)

        Truncated. see log file for complete stacktrace

Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User  javax.security.auth.login.LoginException: [Security:090301]Password Not Supplied

        at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)

        at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)

        at java.security.AccessController.doPrivileged(Native Method)

        at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        Truncated. see log file for complete stacktrace

> 

<DATE> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>

Solution - 

1. validate the boot.properties files if the username and password have been set

2. If not, update the boot.properties files with the username, password of the weblogic server and restart the managed server. Username/password can be provided in cleartext which will be encrypted by weblogic server

3. If the boot.properties file does not exist, please create a new file.

OSB: Debug logs and troubleshooting

OSB troubleshooting and debugging could be more easier after enabling the below settings

Debug file settings -

alsbdebug.xml can be found in the domain home path. 

Set module debug to true in alsbdebug.xml -

<java:alsb-module-debug>true</java:alsb-module-debug>

Restart the managed server for the change to take effect