Oracle Analytics Cloud and Server

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

Cloning Error - 'Essbase instance connection failed'

Received Response
3
Views
1
Comments
Charles M
Charles M Rank 6 - Analytics Lead

Hi -

I am facing an issue during a clone attempt. The issue is occurring on the source instance, while trying to copy the instance configuration - I am following OBIEE 11g Test-to-Production (T2P) / Clone Procedures Guide (Doc ID 1625533.1).

The error is thrown at step #4.

pastedImage_4.png

At first, I tried this command with the above parmaters. But, it failed with:

SEVERE : Mar 23, 2017 09:00:20 - ACTION - CLONE-20218   Provide the clone log and error file for investigation.

java.lang.RuntimeException: Essbase Server connection information is not provided,  specify additional parameter -additionalParams(-ap) essbaseServerUserName=xxx,essbaseServerPassword=yyy/pwdfile

So, I added the "addiotional" parameter. However, it now fails with:

SEVERE : [PLUGIN][BI] Essbase instance connection failed. Please make sure  Essbase server is up and running at localhost:9799

SEVERE : Mar 23, 2017 09:37:34 - ERROR - CLONE-20218   Cloning is not successful.

SEVERE : Mar 23, 2017 09:37:34 - CAUSE - CLONE-20218   An internal operation failed.

SEVERE : Mar 23, 2017 09:37:34 - ACTION - CLONE-20218   Provide the clone log and error file for investigation.

java.lang.RuntimeException: java.lang.RuntimeException: com.essbase.api.base.EssException: Cannot connect to olap service. Cannot connect to Essbase Server. Error:Essbase Error(1051293): Login fails due to invalid login credentials

        at oracle.bi.cloning.components.essbase.EssbaseCopyConfig.getEssbaseInstance(EssbaseCopyConfig.java:391)

        at oracle.bi.cloning.components.essbase.EssbaseCopyConfig.getStorageCustomizations(EssbaseCopyConfig.java:235)

        at oracle.bi.cloning.components.essbase.EssbaseCopyConfig.setEssbaseInstanceData(EssbaseCopyConfig.java:125)

        at oracle.bi.cloning.components.essbase.EssbaseCopyConfig.preCopyConfigValidation(EssbaseCopyConfig.java:69)

        at oracle.bi.cloning.base.AbstractCopyConfig.doCopyConfigValidation(AbstractCopyConfig.java:125)

        at oracle.as.clone.cloner.component.ComponentCreateCloner.doClone(ComponentCreateCloner.java:118)

        at oracle.as.clone.cloner.Cloner.doFinalClone(Cloner.java:63)

        at oracle.as.clone.request.CreateGenericArchive.doGenericArchive(CreateGenericArchive.java:162)

        at oracle.as.clone.cloner.component.ASInstanceCreateCloner.executeAllMCCloners(ASInstanceCreateCloner.java:323)

        at oracle.as.clone.cloner.component.ASInstanceCreateCloner.doClone(ASInstanceCreateCloner.java:122)

        at oracle.as.clone.cloner.Cloner.doFinalClone(Cloner.java:63)

        at oracle.as.clone.request.CreateGenericArchive.doGenericArchive(CreateGenericArchive.java:162)

        at oracle.as.clone.request.CreateGenericArchive.doGenericArchive(CreateGenericArchive.java:94)

        at oracle.as.clone.request.CreateCloneRequest._clone(CreateCloneRequest.java:69)

        at oracle.as.clone.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:131)

        at oracle.as.clone.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:114)

        at oracle.as.clone.client.CloningClient.executeT2PCommand(CloningClient.java:236)

        at oracle.as.clone.client.CloningClient.main(CloningClient.java:124)

Caused by: java.lang.RuntimeException: com.essbase.api.base.EssException: Cannot connect to olap service. Cannot connect to Essbase Server. Error:Essbase Error(1051293): Login fails due to invalid login credentials

        at oracle.bi.cloning.components.essbase.EssbaseMaxlSession.createMAXLSession(EssbaseMaxlSession.java:37)

        at oracle.bi.cloning.components.essbase.EssbaseMaxlSession.getMaxlSession(EssbaseMaxlSession.java:19)

        at oracle.bi.cloning.components.essbase.EssbaseInstance._setApplications(EssbaseInstance.java:269)

        at oracle.bi.cloning.components.essbase.EssbaseInstance._setEssbaseApplicationData(EssbaseInstance.java:31)

        at oracle.bi.cloning.components.essbase.EssbaseInstance.<init>(EssbaseInstance.java:27)

        at oracle.bi.cloning.components.essbase.EssbaseCopyConfig.getEssbaseInstance(EssbaseCopyConfig.java:387)

        ... 17 more

Caused by: com.essbase.api.base.EssException: Cannot connect to olap service. Cannot connect to Essbase Server. Error:Essbase Error(1051293): Login fails due to invalid login credentials

        at com.essbase.server.framework.EssOrbPluginDirect.essMainLoginSV(Unknown Source)

        at com.essbase.server.framework.EssOrbPluginDirect.essMainLoginSV(Unknown Source)

        at com.essbase.server.framework.EssMainConnectionContext.open(Unknown Source)

        at com.essbase.server.framework.EssOrbPluginDirect.essMainLogin(Unknown Source)

        at com.essbase.server.framework.EssOrbPluginDirect.essMainLogin(Unknown Source)

        at com.essbase.api.session.EssOrbPlugin._invokeMainMethod(Unknown Source)

        at com.essbase.api.session.EssOrbPlugin._invokeMethod2(Unknown Source)

        at com.essbase.api.session.EssOrbPlugin._invokeMethod(Unknown Source)

        at com.essbase.server.framework.EssOrbPluginDirect._invokeProtected(Unknown Source)

        at com.essbase.api.session.EssOrbPluginEmbedded.invokeMethod(Unknown Source)

        at com.essbase.api.session.EssOrbPluginEmbedded.invokeMethod(Unknown Source)

        at com.essbase.api.session.EssOrbPlugin.essMainLogin(Unknown Source)

        at com.essbase.api.datasource.EssOlapServer.connect(Unknown Source)

        at com.essbase.api.datasource.EssOlapServer.connect(Unknown Source)

        at oracle.bi.cloning.components.essbase.EssbaseMaxlSession.createMAXLSession(EssbaseMaxlSession.java:33)

        ... 22 more

I do not know the Essbase credentials. I don't believe we even use that component. I can see that the server shows as "up" in FMW EM:

pastedImage_7.png

I've tried some of the "default" credentails I found for this, such as: admin/password and Administrator/password. But neither one has worked. My assumption is that even though we do not use this component, we should move everything to the target server as it exists in the source.

How can I overcome this issue?

OBIA version 11.1.1.10.1

Regards,

Charles

Answers