• Find us:
    +1 415 655 1723   |   +91-844-844-8901
  • Free Newsletter

     
     

  • Archive

  • Categories


  • Troubleshooting : oam_admin status is failed in WebLogic deployment for OAM Server

    Posted by "" in "OAM, WebLogic" on 2014-06-27

    Share on FacebookTweet about this on TwitterShare on Google+Share on LinkedInEmail this to someone

    Recently I came across the error where OAMConsole (Admin Console for Oracle Access Manager) was not working. This post covers steps to troubleshoot issues with OAM Console.

     

    OAM console is J2EE application, deployed on WebLogic’s Admin Server. You access OAM console using http://webLogicHost:AdminPort/oamconsole . For me OAM console was resulting in 404 Not Found.

    Screen shot 2014-06-28 at 12.13.24

     

     

    If you hit error like above then check status of oam_admin application under deployments in WebLogic Admin Server Console (/console)

     

    Status of  oam_admin(11.1.2.0.0) status was FAILED

     

    Screen shot 2014-06-28 at 12.13.24 Screen shot 2014-06-28 at 09.15.51

     

     

    I then checked log file at $DOMAIN_HOME/servers/AdminServer/[base_domain].log and error mentioned in log file was

    ______

    ####<Jun 28, 2014 7:40:43 AM BST> <Warning> <HTTP> <iamtr53.k21technologies.com> <AdminServer> <[ACTIVE] ExecuteThread: ‘3’ for qu
    eue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <0000KRXCG7xFc5WFLzJN8A1Jfa8p000006> <1403937643485> <BEA-101162>
    <User defined listener oracle.security.am.lifecycle.ApplicationLifecycle failed: oracle.security.am.common.utilities.exception.AmR
    untimeException: Component Bootstrap Failed.
    oracle.security.am.common.utilities.exception.AmRuntimeException: Component Bootstrap Failed
    at oracle.security.am.lifecycle.ApplicationLifecycle.contextInitialized(ApplicationLifecycle.java:109)

    Caused By: java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

    Caused By: oracle.security.am.install.AMInstallException: DB Policy not configured in mixed mode
    at oracle.security.am.install.startup.AMBootstrapListener.checkDBPolicyStoreConfigured(AMBootstrapListener.java:160)
    at oracle.security.am.install.startup.AMBootstrapListener.initialize(AMBootstrapListener.java:95)

     

    ####<Jun 28, 2014 7:40:44 AM BST> <Error> <Deployer> <iamtr53.k21technologies.com> <AdminServer> <[ACTIVE] ExecuteThread: ‘3’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <0000KRXCG7xFc5WFLzJN8A1Jfa8p000006> <1403937644587> <BEA-149231> <Unable to set the activation state to true for the application ‘oam_admin [Version=11.1.2.0.0]’.
    weblogic.application.ModuleException:
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1520)

    ______

     

    I reviewed few My Oracle Support (MOS) notes .

    • OAM Fails to Start After Applying Patch 11.1.1.5.2 (Doc ID 1439201.1)
    • OAM 11g : OAM Server Key Initialization Failed (Doc ID 1354918.1)
    • OAM 11gR2 : OAM Server Deployment Shows Status “Failed” and Error “Datasource jdbc/oamds not found” is Displayed (Doc ID 1586388.1)

     

    At the end I found that there is some problem in configure security store to Database (wrong parameters used).

    Error:

    $MW_HOME/oracle_common/common/bin/wlst.sh

    $ORACLE_HOME/common/tools/configureSecurityStore.py -d $DOMAIN_HOME

    –t DB_ORACLE –j cn=jpsroot –m create –<OPSS_SCHEMA_PASSWORD>     (ERROR)

    _______

    Correct parameter is :

    $MW_HOME/oracle_common/common/bin/wlst.sh

    $ORACLE_HOME/common/tools/configureSecurityStore.py -d $DOMAIN_HOME

    –c IAM –p <OPSS _SCHEMA_PASSWORD> –m create          (Right)

    So by correctly configuration of security store to database problem was solved .

     

     

    Share on FacebookTweet about this on TwitterShare on Google+Share on LinkedInEmail this to someone

    4 thoughts on “Troubleshooting : oam_admin status is failed in WebLogic deployment for OAM Server”

    1. Devang says:

      Hi,

      In our env.
      oam-admin is not available in deployments of adminserver and hence we are unable to access oamconsole

      1. Atul Kumar says:

        @ Devang, You can manually deploy OAM Console ear file from WebLogic Console. Search for OAMConsole EAR file and then using weblogic console manually deploy it to Admin Server .

    2. Snehal Patel says:

      I ran into similar issue. Problem was fixed with finding missing jar file in classpath.

    3. Ove says:

      Hi,
      Now i am also facing the same error.When i try to configure the security store it shows the,
      Unique constraint violated error,So i try to fix that error using the validate_fix option then it is success.After i start the admin server the oamconsole application status is failed.I am also refer the above mentioned document but i am not able to find the exact error .I am stuck in that place for more than one month.Please guide me.

    Leave a Reply

    Your email address will not be published. Required fields are marked *



  • K21 Technologies is among the most experienced Oracle Gold Partner for Identity Access Management service providers. We work with application development companies and in-house technology division to help achieve significant returns on their IT security investment. Our clientele includes some of the globally renowned corporate, which speaks of our expertise in our field.

    We have the most talented and experienced team that can swiftly deploy security solutions even in complex IT ecosystem. Our clients highly appreciate our timely implementation, interactive training, on-demand support and community resources.
  • CONTACTS

    K21 Technologies
    128 Uxbridge Road, Hatchend,,
    London, HA5 4DS

    US: +1 415 655 1723
    India: +91-844-844-8901

  • Copyright 2019, K21 Technologies. All rights reserved
  • TOP
    TOP