Part Two – OMCS (Oracle Managed Cloud Service) to OPC (Oracle Public Cloud)

  • 25th July 2017
  • Cloud
  • Peak Indicators

Back in April, we shared the first part of a case study surrounding the migration of a customer from Oracle Managed Cloud Service (OMCS) to OPC (Oracle Public Cloud).

With Oracle’s cloud offering finally coming of age, this was the start of a great journey for the business in question*.

In the first blog, we looked at the positives of the OMCS to OPC move, as well as the early work involved. To quickly recap, we talked about:

  • Enjoying working with what is a refreshingly different side to Oracle software.
  • How co-operation and the introduction of a Customer Success Manager role are pleasing features.
  • Being able to deliver analytics projects in a far more agile fashion.
  • Built-in flexibility being a key feature of OPC.
  • How if we need a temporary UAT environment, we can spin up a metered environment for as long as needed, before deleting it.
  • How for production, we went with a non-metered environment. This was an extremely cost-effective approach to follow.

What Did We Do Next?

Since the first blog was published, things have progressed significantly. We have now completed the creation of the skeleton database server instances. We are currently setting up the OACS (Oracle Analytics Cloud Service) instances in the production, pre-production, development cloud environments.

Currently Oracle are also commissioning the VPN (Virtual Private Network) tunnels, for both metered and unmetered environments.

For reference, a VPN is used to link two locations as if they’re on a local private network. The tunnel is the encrypted link between the two locations. It is ideal for making the connection with the end user simpler, whilst also securing the communications.

Once the OACS’s instances have been set up Peak will then submit SR (support Request) to Oracle to request database dumps from the client's OMCS production data warehouse/repository and their OMCS test data warehouse/repository databases. These database dumps will then be transferred into the respective cloud environment and applied to the relevant databases.

Moving Forward

To date, the OMCS to OPC move has been a steep learning curve. Overall though, we’re really excited to be progressing towards the final stage. We now can’t wait to see the benefits of the move to the cloud being enjoyed by the client.

(*For confidentially, we haven’t mentioned the name of the client in question)

If you’d like to talk to the Peak Indicators team about help with moving to the OPC, please get in touch with us.

Subscribe to our Newsletter

If you enjoyed this article why not get great insights straight to your inbox

Leave a comment