@SteveF-Oracle

stopped server

Updated source path to point to em.ear file

Verified if the below config exists on the respective file. they do exist already.

this entry log4j_jar\#1.3@1.2.15=oracle.sysman.fmw.core_12.2.1.4.0/em_ORACLE_HOME in [DOMAIN_HOME]/init-info/config-path.properties

the following entry after the library named: 'bitech.analysis.application.libs' on config.xml

<library>
<name>log4j_jar#1.3@1.2.15</name>
<target>AdminServer</target>
<source-path>[ORACLE_HOME path]/em/../oracle_common/modules/com.bea.core.apache.log4j.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>

Deleted tmp folder

Started Server

Still em deployment is in failed state.

Error from AdminServer log file when i try to start failed em deployment

<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)

@SteveF-Oracle @Federico Venturin

Even if i manually try to start the em deployment from Weblogic, it fails immediately, and below is the error from the 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

I have downloaded and applied the below patches for the Weblogic server 12.2.1.4. For OAS 2024, no patches are available i think as it got released a month ago on March 18, 2024.

Do i need to apply FMW Infrastructure 12.2.1.4 patches as well?

@SteveF-Oracle @Federico Venturin

Thanks for your inputs.

i have applied all the below patches, and now the em service is UP

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

I applied all the below policies individually and now i can see all the options under the DV console.

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

I can download the rpd but when i try to upload the same rpd i have downloaded it fails with the below error, where should i look for rpd upload error log.

datamodel uploadrpd -I D:\oracle\product\RPD\DEV_2_20240418.rpd -W xxxxxx -U weblogic -P xxxxxxxx -SI ssi -S 99.99.99.99 -N 9502

Operation Failed.

An exception occurred during execution, please check server logs.

System exit code:1