Contact Us

Three Methods for Restarting OAC

In this blog post, I’ll go through three different methods for restarting Oracle Analytics Cloud (OAC), including the uses cases and tutorials for each.

The steps in my previous two-minute tutorial — Opening Ports for OAC – EM Browser Access and RPD Admin Tool Access — are prerequisites for the tutorials below.

1. Services

The reasons for using Services to restart OAC include…

  • Users experiencing slow logins
  • An update to configuration files

Open a browser window and navigate to the following address:


Sign in with admin user.

Expand the Menu Navigator in the top left-hand corner and click on biinstance.

oac restart_1 

Click on the Availability Tab and select Restart All.

oac restart_2

Click Yes on the confirmation window and wait for the process to complete.

oac restart_3

oac restart_4

Once complete, click Close. If you wait for a few seconds, the window will go away on its own.

oac restart_5

Logins to the system take several minutes before they’re available again. It’s perfectly normal to get the following message after a restart…

oac restart_6

2. Server Stack

The reasons for restarting OAC using Server Stack, include…

  • Unable to log into EM (Enterprise Manager)
  • BI Server is unresponsive
  • An issue not resolved by Services restart
  • Snapshot restore — if not reflected in the analytics front end

Open Putty (Or SSH into the server) and select your OAC Instance, click Load and Open.

oac restart_7

oac restart_8

You will automatically be logged in as OPC which is a read-only user. Change to the Oracle user – sudo su oracle.

oac restart_9

Once logged in as the oracle user, change directory to the bitools/bin where many scripts live.

cd /bi/domain/fmw/user_projects/domain/bi/bitools/bin

oac restart_10

Once there, run the stop script ./

oac restart_11

When that completes after a few minutes, then you can run the start script ./

oac restart_12

After all of the components are finished starting, it might take several minutes to allow you to log into the front-end analytics server

3. OAC VM Instance Stop/Start

The reasons for restarting OAC through OAC VM Instance Stop/Start, include…

  • It’s the last resort.
  • Can’t log into EM or Putty on the server.

Note: This is stopping the entire VM Instance, and not cleanly shutting down OBIEE or applications that are running. Please see the OAC Server Stack Restart to cleanly shut down OBIEE if possible prior to doing this step to avoid any corruption of files.


Open a browser and navigate to

Click on Sign In at the top.

oac restart_13

Type in the second text box your OAC domain and click My Services blue button.

oac restart_14

Sign into My Services Dashboard.

Once you see the dashboard, click on the three bars at the top left-hand corner, expand Services and then select Analytics.

oac restart_15

oac restart_16

Identify the instance you want to stop/start and click on the four bars to the right.

oac restart_17

Click on stop/start, and you will a prompt to confirm. Click OK.

oac restart_18

Once the instance is stopped, you will see a RED exclamation point triangle and a status that says Service Stopped.

oac restart_19

And that concludes this OAC blog post! Be sure to subscribe to our blog for more technical tutorials and updates on OAC features.

Check out other OAC tutorials…

New call-to-action

Ask an EPM/BI Advisor

If you're here, you've got questions — and we've got answers. Book your consultation to ask us about any range of topics, including:

  • Evaluating EPM or BI technologies
  • Comparing on-prem vs. cloud
  • Planning upgrades and migrations
  • Estimating project costs and timeframes
  • And much more — ask us anything!

Let our experts tackle your toughest questions for you.

Let's Talk