Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

OBIEE 12.2.1.3 to OAS 2024 (7.6) Upgrade - EM Not Starting & Missing Options under Console

Accepted answer
1468
Views
17
Comments
userva
userva Rank 4 - Community Specialist
edited Apr 15, 2024 1:39PM in Oracle Analytics Cloud and Server

We are currently doing an out-of-place upgrade of OBIEE 12.2.1.3 to OAS 2024(7.6) POC on a Windows sandbox. Downloaded and installed all the steps as mentioned in the link https://www.oracle.com/solutions/business-analytics/analytics-server/analytics-server.html#

OAS 7.6 was Installed successfully, and then the following command was used to generate the bar file on OBIEE 12.2.1.3, it got generated successfully.

export_service_instance ssi D:\temp\obiee12c.bar

Imported the bar file onto OAS using the snapshots option under DV and once imported clicked on Restore. Restore was successful, but since then the em page has not loaded and all the options under the the dv/console were not visible.

Em Page Error:

http://xxxxxxxxx:9500/em

image.png

Missing all options under Console (http://xxxxxxxx:9502/dv/ui/home.jsp?pageid=console

image.png

Could someone please help me on this on how to debug the issue and resolve the issue?

Best Answer

  • Federico Venturin - Oracle
    Federico Venturin - Oracle Mod
    edited Apr 16, 2024 1:27PM Answer ✓

    Hi @userva ,

    You have to apply Weblogic and FMW Infrastructure patches (which are listed for OAS 2023) to OAS 2024:

    https://support.oracle.com/epmos/faces/PatchDetail?patchId=28186730
    https://support.oracle.com/epmos/faces/PatchDetail?patchId=36178496
    https://support.oracle.com/epmos/faces/PatchDetail?patchId=36074941
    https://support.oracle.com/epmos/faces/PatchDetail?patchId=34809489
    https://support.oracle.com/epmos/faces/PatchDetail?patchId=36034300
    https://support.oracle.com/epmos/faces/PatchDetail?patchId=35868571
    https://support.oracle.com/epmos/faces/PatchDetail?patchId=34542329
    https://support.oracle.com/epmos/faces/PatchDetail?patchId=33950717

«1

Answers

  • Federico Venturin - Oracle
    Federico Venturin - Oracle Mod
    edited Apr 15, 2024 1:56PM

    Hi @userva,

    When you restore an OBIEE snapshot in OAS, all default role policies are overwritten with the content of the snapshots. OAS contains new policies that are required in order to use DV properly and you have to restore them: https://docs.oracle.com/en/middleware/bi/analytics-server/security-oas/grant-or-revoke-permissions-assignments.html

    If you grant all policies to BIServiceAdministrator than you should be able to fix your issues.

  • userva
    userva Rank 4 - Community Specialist
    edited Apr 15, 2024 2:55PM

    Thanks, @Federico Venturin for your response.

    as mentioned in the URL, i will try to grant all policies.

    I need a few clarifications:

    1) Example, has used myAdministrator role and how can i know the role name i have to use to grant permissions, or does myAdministrator default role come with OAS for administrators?

    2) I need to grant all the following permissions ?

    grantPermissionSetsToBIRole -r myAdministrator -p actio.admin,actio.author,actio.operator,actio.viewer,bilifecycle.admin,bip.administrator,bip.author,bip.consumer,bisecurity.admin,bisecurity.author,bisecurity.GBUAdmin,bisecurity.impersonate
    ,bisecurity.lifecycle.admin,customScripts.admin,dataReplication.access,infer.administrator,majel.administrator,obips.administrator,obis.administrator,obisch.administrator,obisch.author
    ,oracle.bi.dss.CustomKnowledge.admin,oracle.bi.dss.CustomKnowledge.consumer,oracle.bi.dss.SystemKnowledge.admin,oracle.bi.tech.dv.consumer,pod.admin,rdc.admin,rdc.consumer,rdc.monitor
    ,sac.advanced.approle.administrator,sac.approle.administrator,sac.snapshot.administrator,semanticmodeler.author,va.admin,va.author,va.interactor

  • Federico Venturin - Oracle
    Federico Venturin - Oracle Mod

    Hi @userva ,

    You assign security policies / permission sets to application roles, not to individual users.

    BIServiceAdministrator is the default application role in OAS that allows you to manage the application, and the administrator user created during the installation is member of it.

    Since you restored an OBIEE snapshot, you should double-check that your administrator user is actually a member of the BIServiceAdministratorRole (e.g. login to Classic Analytics, click on your profile icon and select MyAccount). In the past BIServiceAdministrator used to be called BIAdministrator and there is a chance it has been migrated with that name to OAS from old OBIEE versions in your case.

    BIServiceAdministrator (or BIAdministrator if you are still using the old naming convention) is expected to have all permission sets, so you can safely run the command with all the options listed in the documentation.

  • userva
    userva Rank 4 - Community Specialist
    edited Apr 15, 2024 5:22PM

    i have run the below command to grant all policies and restarted the server. still, i have the same behavior em login page won't come up and all options under dv/console missing.

    image.png

    image.png
  • Mallikarjuna Kuppauru-Oracle
    Mallikarjuna Kuppauru-Oracle Rank 8 - Analytics Strategist

    Hi @userva

    Can you confirm your em deployment is active from web-logic console page? If yes are you in the latest patch set?

    Regards,

    Arjun

  • SteveF-Oracle
    SteveF-Oracle Mod
    edited Apr 15, 2024 5:25PM

    @userva,

    The Fusion Middleware Control (Enterprise Manager) not available is a known issue/bug.

    Please see:

    After Upgrade To Oracle Analytics Server (OAS), Fusion Middleware Control Enterprise Manager Is Not Accessible And Fails To Load (Doc ID 2948266.1)

    t.gif

    Two separate issues are being reported in this thread.

  • Federico Venturin - Oracle
    Federico Venturin - Oracle Mod

    Hi @userva ,

    Can you confirm that your administrator user is a member of the BIServiceAdministrator role?

    Can you rerun the command and grant only policies containing admin/administrator in the name?

  • userva
    userva Rank 4 - Community Specialist

    @Mallikarjuna Kuppauru-Oracle

    em is in the failed state

    image.png
  • userva
    userva Rank 4 - Community Specialist

    @Federico Venturin

    administrator user created as part of the OAS installation is Weblogic and he is part of the BIServiceAdministrator role, verified using my account option on the analytics console.

    image.png
  • userva
    userva Rank 4 - Community Specialist
    edited Apr 15, 2024 6:07PM

    @SteveF-Oracle

    we are doing only the out-of-place upgrade, based on the document i have verified the source path for em deployment in the config file.

    Current Code: in the path for em.ear it has all backslash until bi and frontslash before em.ear and all other ear paths in the file have front slash only in full path, it may be the reason

    <app-deployment>
    <name>em</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>D:\oracle\product\oas-2024\user_projects\applications\bi/em.ear</source-path>
    <deployment-order>400</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </app-deployment>

    changed to below

    <app-deployment>
    <name>em</name>
    <target>AdminServer</target>
    <module-type>ear</module-type>
    <source-path>D:/oracle/product/oas-2024/user_projects/applications/bi/em.ear</source-path>
    <deployment-order>400</deployment-order>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
    </app-deployment>

    Will restart the server and will update if it resolves the issue or not.

    same behavior after restart, em is in failed and below is the error message from adminserver log

    <BEA-149004> <Failures were detected while initiating start task for application "em".>
    ####<Apr 15, 2024 3:22:02,498 PM EDT> <Warning> <Deployer> <MADPAPPD01> <AdminServer> <[ACTIVE] ExecuteThread: '24' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <9e1289a2-18e4-46e9-b4a1-4bf3b35b5228-000001ed> <1713208922498> <[severity-value: 16] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: java.lang.ClassNotFoundException: org.apache.log4j.FileAppender
    at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:233)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:228)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:78)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:52)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:752)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:262)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:66)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:90)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:631)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:171)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:121)
    at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:151)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:348)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:906)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1467)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:458)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:181)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:217)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:14)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:681)
    at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
    at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
    at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
    at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
    at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:360)