Unable to start application / Unable to load database %s

Unable to start application / Unable to load database %s

This is one of the most recurring issues in Essbase database. Let’s discuss the causes and resolution to this issue.

Causes:

•  In between an Essbase transaction (data load, calculation script execution, data backup, planning database refresh etc.) Essbase server shuts down abnormally.
• You try to force kill specific processes (data load, data backup, calculation script execution, planning database refresh etc.) and Essbase not being able to kill the process. Essbase starts showing never ending terminating process in sessions. Be sure, this is the start of the end of application which will eventually give above error.

These are few causes that I have faced during my Hyperion tenure. Share your thoughts if you could add up to these causes.

My take on this is I can understand this issue occurring during abnormal shut down, but what I am not very comfortable is with the second reason.

Planning based Essbase applications are more prone to this issue.

Here’s the fix to this issue that works for me,

• Login to Essbase server
• Go to task manager -> processes in case your server is windows based / Enter command ps –ef grep|’hyperionadmin’ in case your server is Linux based
•  (ps -ef | grep oracle)
• Force kill all the ESSSVR process which are tampering your application
• Restart the Essbase server

In most of the cases, these steps should resolve your issue.

Source: http://hyperion-blog.blogspot.mx/2012/10/unable-to-start-application-unable-to.html

Resolver problema al instalar obiee 11g con sqlserver 2005

Para resolver este error:

2014-04-29 15:09:40.800 ERROR rcu: oracle.sysman.assistants.rcu.backend.task.ActualTask::run: RCU Operation Failed
oracle.sysman.assistants.common.task.TaskExecutionException: RCU-6083:Fallo: Comprobar requisitos para el componente seleccionado:MDS
Consulte el log de RCU en C:\ofm_rcu_win_11.1.1.7.0_32_disk1_1of1\rcuHome\rcu\log\logdir.2014-04-29_15-03\rcu.log para obtener más información.
------------------------------------------------------------------------------
Component     : MDS
Error         : Repository creation check failed.
Cause         : Database: 'BI' is not configured correctly.
Action        : Alter database to turn on the READ_COMMITTED_SNAPSHOT option.
                Ensure you have DBA priviliges. Also the DBA should not have
                multiple logins on this database - else it will result in a
                lock error.
Command       : ALTER database BI SET READ_COMMITTED_SNAPSHOT ON
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Component     : MDS
Error         : Repository creation check failed.
Cause         : Database: 'BI' is not configured correctly.
Action        : Alter database to apply the correct collate to the database.
                Ensure you have DBA priviliges. Also, the DBA should not have
                multiple logins on this database - else it will result in a
                lock error.
Command       : DECLARE @collate   sysname
                SELECT @collate = convert(sysname, serverproperty('COLLATION'))
                IF ( charindex(N'_CI', @collate) > 0 )
                BEGIN
                  select @collate = replace(@collate, N'_CI', N'_CS')
                  exec ('ALTER database $(DATABASE_NAME) COLLATE ' + @collate)
                END
                GO
-------------------------------------------------------------------------------

at oracle.sysman.assistants.rcu.backend.task.PrereqTask.execute(PrereqTask.java:76)
at oracle.sysman.assistants.rcu.backend.task.ActualTask.run(TaskRunner.java:306)
at java.lang.Thread.run(Thread.java:662)

2014-04-29 15:17:56.203 NOTIFICATION rcu: oracle.sysman.assistants.common.wizard.WizardExt::doCancel: User Canceled the operation
2014-04-29 15:17:56.204 NOTIFICATION rcu: oracle.sysman.assistants.common.wizard.WizardExt::doCancel: User cleanup the tablespaces: false

Se requiere ejecutar los siguientes comandos:

ALTER database NombreBD SET READ_COMMITTED_SNAPSHOT ON;
ALTER database NombreBD SET ALLOW_COMMITTED_SNAPSHOT ON;

ALTER DATABASE NombreBD SET SINGLE_USER WITH ROLLBACK IMMEDIATE
Go
ALTER DATABASE NombreBD COLLATE Latin1_General_CS_AS
Go
ALTER DATABASE NombreBD SET MULTI_USER
Go