by on
  • With a cloud service, customers expect an “always on” capability – “maintenance mode” and other activities should be minimised.
  • Moreover, with the advent of metered services, it’s important that available uptime (burning credits) is maximised – you don’t want the server burning credits if it’s not available for use.
  • On premises Essbase can easily be backed up with no downtime with some custom backup scripts – let’s get the cloud to do the same.
  • OAC essbase backups are somewhat CPU intensive
  • The 2x most common use cases are:
    • Restore an individual application
    • Restore the server and rebuild an application
  • This post shows you how to turbocharge your backups!

(more…)

by on
  • OAC has been working fine for….180 days….and now won’t start!
  • Service appears to come up OK, but no services accessible & reboots don’t fix it.
  • The short answer – DBCS “as provisioned” has a 180 day expiry on all schemas – and officially there’s no way to unexpire the accounts without changing the passwords, which’ll break “everything”.
  • This post shows how to identify & debug the problem, fix it quickly and simply, and then prevent it happening again!

(more…)

by on

It’s interesting that the ancient Greeks understood that the revelations of the Oracles were not seen as the objective truth and they were fully aware of the unknowability of the divine. I think everyone went to the Oracle Analytics Partner Forum in Athens with some trepidation about what the future holds for Analytics & the Cloud @ Oracle Corporation. The news is good….

(more…)

by on

I was in a conference yesterday and there was some lively debate about the pros and cons of APEX vs Oracle Analytics Cloud, OBIEE & BICS. I thought I’d drill in to this a little further and explore what role does Oracle Application Express plays in a Business Analytics environment and should (or could) Application Express be used instead of Oracle Analytics Cloud?

(more…)

by on

I’ve been asked a number of times whether we can run existing “on premises” rules files in OAC, and also run in OAC using a SQL data source.

We’ve tested out both of these features and both work well:

  • Use Essbase 11.1.2.4 SQL based rules files
  • Developing them off-line on an on-premises install in EAS
  • Setting the SQL connection string to be a substitution variable
  • Deploy them to OAC
  • Update the substitution variable to point to the cloud RDBMS
alter application 'TBC' set variable 'OCIString' 'QUBIXDB:1521/pdb1.a28217.oraclecloud.internal';
import database 'TBC'.'TBC' data connect as 'admin' identified by 'password' using server rules_file 'data' on error write to 'c:\eastemp\data.err';
execute aggregate process on database 'TBC'.'TBC' stopping when total_size exceeds 10;