Lock OBIEE/access during data load

aPsikus

Hi,

We are loading data weekly (on Sundays) and on 1st day of the month (possible that will be on week day).

Are there any mechanisms which will give possibility to lock access to OBIEE during data load process?

We have information when data load is planned on welcome page, but users are often trying to open reports before load is finished.

I have found information about Maintenance Mode, but it looks like it is not the solution in this case.

[Deleted User]

Maintenance Mode isn't the solution since that just puts the catalog in read-only mode.

Do you have an Apache in front of OBI?

Gianni Ceresa

Christian Berg wrote:Do you have an Apache in front of OBI?

Or any other proxy, Apache is just one of the many possible

(Nginx is great!)

[Deleted User]

Yes I just used "Apache" as an example. Point is: put a proxy in front of it ans redirect all traffic to a maintenance landing page

aPsikus

Can load balancer do the trick?

Gianni Ceresa

aPsikus wrote:Can load balancer do the trick?

In theory yes, practically depends on your load balancer ...

The thing would be to remove the OBIEE servers from the pool of backend server to forward connections to, and instead add a webserver which will return the "maintenance page".

There are other ways to manage that, but it all depends on your load balancer and how things are setup etc.

You can also cheat by playing with permissions, removing permissions to users to login till your loading isn't done.

For sure the proxy solution is the "cheapest" in a simple config, yours seems to be already a bit more as you have a load balancer and so, I guess, an OBIEE cluster.

aPsikus

On PROD environment there are two clusters.

How to find out of proxy is used?

Are there any articles describing the setup?

Gianni Ceresa

Do you have a port number in your OBIEE url? A proxy is often used to redirect from standard http 80 or https 443 to the obiee port number, can also do SSL offloading by action as the ssl endpoint.

As you have a loadbalanicer there are chances you don’t have a proxy in front of your obiee. You would need to ask your infra team.

aPsikus

Not parsed address (direct to server) contains port number in the address.

Thomas Dodds

This is a data management issue ... your front end shouldn't have to be unavailable WHILE you load data ... users should get frozen data while you are loading fresh.  Trunc and reload of your production sets is a very bad thing to do.

Robert Angel

Agreed - though wholly read consistent data did worry me during the ETL window, subject area to subject area.