Re-configure Essbase

If you have tried re-configuring Essbase you would notice that it is not able to connect to Shared Service anymore. Authentication error is thrown every time you connect to Essbase from different clients.

Reason: The reason is Essbase is not able to connect with Shared Services. It is unable to create "EssbaseCluster-1" Application group and neither add new application to it as it already exists.
Following error is seen in Essbase_ODL.log files

Failed to create Essbase project [EssbaseCluster-1] at Shared Services with Error [Application group already exist.]
[2013-10-18T05:48:09.953-05:00] [ESSBASE0] [WARNING:1] [AGENT-6822] [] [ecid: 138209328157,0] [tid: 4140] Failed to migrate Essbase to HSS security mode during startup. Check SharedServices_Security_client.log. May need to remove essbase.sec and any of the newly migrated Essbase applications from HSS, then rerun configuration tool.
[2013-10-18T05:48:09.953-05:00] [ESSBASE0] [NOTIFICATION:16] [AGENT-6800] [] [ecid: 138209328157,0] [tid: 4140] Validation of back up file [D:\Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin\ESSBASETS_1382093289.BAK] completed with status 0
[2013-10-18T05:48:30.96-05:00] [ESSBASE0] [NOTIFICATION:16] [TCP-59] [] [ecid: 138209328157,0] [tid: 3028] Connected from [2002:adcc:7c91::adcc:7c91]


Solution
1. Delete the EssbaseCluster-1 from the application group in shared service.
2. Re configure Essbase (If you already have ignore)
3. Go to this location D:\Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin (appropriately)
4. Cut the files like Essbase.SEC, ESSBASE.BAK_postUPM, ESSBASE.BAK_preUPM and paste it in some other location
5. Restart Essbase
6. It automatically creates and connects to Shared Service.

Read More

Unable to start Web Analysis.

Problem:WebAnalysis URL not reachable/accessible.
Weblogic has started but the application WebAnalysis.ear file is in prepared state hence the URL is not accessible.
Error:weblogic.application.ModuleException: [HTTP:101216]Servlet: "InitServlet" failed to preload on startup in Web application: "WebAnalysis". com.hyperion.atf.services.ServiceManager$ServiceRecursiveInitException: Could not start critical service: "assignable.admin", all services are being rolled back. at com.hyperion.atf.services.ServiceManager.setServiceContainer(ServiceManager.java:591) at com.hyperion.atf.services.ServiceManager.getService(ServiceManager.java:309) at com.hyperion.atf.services.ServiceManager.getService(ServiceManager.java:341) at com.hyperion.atf.security.assignables.AssignableManager.getAssignableAdmin(AssignableManager.java:28) at com.hyperion.atf.security.assignables.AssignableManager.getDefaultHomeDirLocation(AssignableManager.java:77) at com.hyperion.analyzer.servlet.HYAInitServlet.checkUserDir(Unknown Source) at com.hyperion.analyzer.servlet.HYAInitServlet.init(Unknown Source) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3155) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:487) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:672) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:149) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) :com.hyperion.atf.services.ServiceManager.ServiceRecursiveInitException:Could not start critical service: "assignable.admin", all services are being rolled back.
Cause:Web Analysis tables are not created in RDBMS Repository while configuring with database

SolutionIt is strongly recommended that you take a backup of the database before executing the steps below. 1. Stop All EPM Services2. Take a Backup of Database [RDBMS]3. Execute below queries from SQL Client: %MW_HOME%\EPMSystem11R1\products\biplus\database\Oracle\database-analyzer-schema.sql %MW_HOME%\EPMSystem11R1\products\biplus\database\Oracle\database-atf-schema.sql %MW_HOME%\EPMSystem11R1\products\biplus\database\Oracle\database-internal-schema.sql4. Start All EPM Services

Read More

Hyperion 11.1.2.3 user provisioning issue

ARCHITECTURE:
==============

Hyperion Version : 11.1.2.3

DB -  11.2.0.3 single instance exadata DB
Exalytic Linux - PCM, EAS, ESS, Planning, EIS , OHS, Calcmanager,APS, Essbase Server
Exalytic Win - FCM, HFM, HSF, Foundation(shared Services and workspace), FR, WA, FDM, IR, Reporting and Analysis, SOA,


ISSUE DETAILS :
Testing is failing for the following components

--> HSS Provisioning few roles is failing with error "apache bridge failure" or "Page cannot be displayed 400 error message"
--> Not able to connect to FR Studio using BIG IP URL or either OHS physical URL
--> After launching Webanalysis Login page when trying to login its giving " Page cannot be displayed 400 error message"
--> HFM Sample application creation from workspace is taking long time and getting timed out.
--> OHS is not able to connect to any of the manage servers on windows MT box, For the applications deployed on windows manage server it is failing with "apache bridge failure error message"
--> Here OHS is running on linux and HSS on windows machine, I am able to test other components running on linux machine - PCM, Planning (able to create the application successfully)
--> I am able to connect to FR Studio using the ManageServerIP:ManageServerPort , and I am able to provision all roles without any issues when i login to workspace using ManageServerIP:ManageServerPort, So this tells there is no issues with component wise.


--> OHS port is opened from windows(HSS) server to linux (OHS) server and All manage server ports running on windows server is opened from OHS box.
--> Tried reconfiguring OHS but still same issue and also tried enabling weblogicplugin on windows domain, But still same issue

Solution:

Suggested:
uncomment the following lines in the mod_wl_ohs.conf file on the OHS server:

Debug ALL
WLLogFile /tmp/weblogic.log

stop/start OHS retest HSS URL via port 19000 and check the /tmp/weblogic.log file for where the plugin is trying to send traffic to.


Implemented:
 After enabling the DEBGUG ALL option

The following error message was occurring in the debug log file

2013-08-08T07:45:06.1439-05:00 <13082137596590645> Error 13 in opening temp request body file '/tmp/_wl_proxy/_post_13082_0'
2013-08-08T07:47:26.4328-05:00 <13082137596604649> Error 13 in opening temp request body file '/tmp/_wl_proxy/_post_13082_1'


Final Solution: changed the file permission of /tmp/_wl_proxy/ file.

Read More

Important Views in Oracle DB

1. dba_tablespaces
SQL> desc dba_tablespaces;
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 TABLESPACE_NAME                           NOT NULL VARCHAR2(30)
 BLOCK_SIZE                                NOT NULL NUMBER
 INITIAL_EXTENT                                     NUMBER
 NEXT_EXTENT                                        NUMBER
 MIN_EXTENTS                               NOT NULL NUMBER
 MAX_EXTENTS                                        NUMBER
 MAX_SIZE                                           NUMBER
 PCT_INCREASE                                       NUMBER
 MIN_EXTLEN                                         NUMBER
 STATUS                                             VARCHAR2(9)
 CONTENTS                                           VARCHAR2(9)
 LOGGING                                            VARCHAR2(9)
 FORCE_LOGGING                                      VARCHAR2(3)
 EXTENT_MANAGEMENT                                  VARCHAR2(10)
 ALLOCATION_TYPE                                    VARCHAR2(9)
 PLUGGED_IN                                         VARCHAR2(3)
 SEGMENT_SPACE_MANAGEMENT                           VARCHAR2(6)
 DEF_TAB_COMPRESSION                                VARCHAR2(8)
 RETENTION                                          VARCHAR2(11)
 BIGFILE                                            VARCHAR2(3)
 PREDICATE_EVALUATION                               VARCHAR2(7)
 ENCRYPTED                                          VARCHAR2(3)
 COMPRESS_FOR                                       VARCHAR2(12)



Common Usage:
SQL> select TABLESPACE_NAME from dba_tablespaces where TABLESPACE_NAME='HSS';

TABLESPACE_NAME
------------------------------
HSS

SQL> select TABLESPACE_NAME from dba_tablespaces where TABLESPACE_NAME='EAS';

no rows selected
=============================================================

Read More

xhost command in Linux

xhost 

Description
       The xhost program is used to add and delete host names or user names to
       the list allowed to make connections to the X server.  In the  case  of
       hosts,  this  provides  a rudimentary form of privacy control and secu-
       rity.  It is only sufficient for a workstation (single  user)  environ-
       ment,  although  it  does  limit  the worst abuses.  Environments which
       require more sophisticated measures  should  implement  the  user-based
       mechanism  or use the hooks in the protocol for passing other authenti-
       cation data to the server.
Learning
     Assuming we have two hosts one 'local host' and the other where connection is being established as 'remote host'  . Giving xhost + <hostname> gives permission to which host(s) should be able to establish a connection with the localhost.

Typical usage with VNC. 
     On remote host:
                                vncserver 
    Enter the password and end result is obtained as <hostname>:<display#>

  Download vncviewer clients like TightVNC, Run VNC.
connect as <hostname/ipaddress>:<display#> enter the password that was provided and the connection is established.

Now on vncserver enter xhost + or xhost + `hostname`
set display 
                  export DISPLAY=:<display#> or
                  export DISPLAY=<hostname>:<display#>

Then type
                               xclock

to validate if clock is shown and display is set right.

This is a non secure way of working but a secure connection can be established via tunneling.

Can learn about usage by using man xhost on linux/unix systems.

Read More

Essbase Spreadsheet ad-in Installation Error

Version :
 11.1.2.0  and later

Error:

Error 1904 Module C:\Oracle\Middleware\EPMSystem11R1\products\Essbase\EssbaseClient\bin\essegd.dll failed to register. HRESULT -2147220473. Contact your support personnel

 Solution:

 Try registring the dll manually by using regsvr32 command

CMD> regsvr32  C:\Oracle\Middleware\EPMSystem11R1\products\Essbase\EssbaseClient\bin\essegd.dll 

 If that does not pass through apply following patch: 

The patch has a new set of installers use it, follow the readme.

Patch 14291917

 Reason: Could be due to already existing EPMSystem setup already existing and some of the files that were missing during the setup. Not very sure why the error but the patch does speak there was a bug reported 

 

 

 

Read More

Unable to lock central inventory

Error: Unable to lock central inventory
Description: There could be many reasons for this error
Troubleshooting:
 Check permissions on .patch_storage
Cause: Central inventory has a lock hence current opatch process is not able to obtain lock on it.
Meanwhile there are a lot of toher
Solution:

Read More