Skip to main content

First steps using the Oracle Exadata Express Cloud Service

By
The Oracle Exadata Express Cloud Service was announced at Oracle Open World 2016. This service looks like an excellent use case for Oracle Database development purposes as well as setting up a test environment. And even for small to medium sized production situations it looks very promising as you can see in the table below. Especially the cheapest option offers a lot of bang for your bucks.
But alas, this service was not as widely available as I expected. The first months it was US-only and you could only figure out by ordering the service and then you would find out on the last page that you should "contact your Oracle sales rep". I sincerely doubt whether he or she could provide you with that service, so I just waited until it would be more generally available.
And since a few weeks the Oracle Exadata Express Cloud Service is also available in Europe - I don't know about other parts of the world. A missed chance though that Oracle didn't announce that properly. You can only find out by trial-and-error. And to be clear, your data will still reside on US soil...

After entering my credit card number I made my purchase irreversible and I immediately received an order confirmation. As I expected these cloud things go very fast I started waiting for the mail that would say that my service was ready. Not on that same day. Not on the next day. But two days later, I finally received my "Welcome to Oracle Cloud" email. If any webshop that ships physical items would move that slow, they would be out of business pretty soon. 
But now I was ready to go! First I had to create my "service instance". No clue what Oracle did the last two days, but effectively I only had access to a console where I could create such an instance. Why doesn't Oracle create that instance immediately? Because in the end what I ordered was a service instance - not the option to create one...

Nevertheless, with a few clicks I had requested my instance as seen in the screen below (notice the little missing icons / images on the upper left and right buttons...).
The only thing that had to be done was firing up a 20Gb Pluggable Database (PDB). On my VM that would take a few minutes. So on an Exadata beast ... a minute or maybe two?

Alas, no. For some reason it took 4 (four!) full days. All those days I logged in to see whether there was any progress and all I saw was:
After the Oracle internal issues were solved - the PDB was created super fast, but the registration process failed somewhere - I was finally up and running. 

It took a while, but I hope it was worth waiting for ....
Labels:

Comments

Post a Comment

Popular posts from this blog

Refresh selected row(s) in an Interactive Grid

By
In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...
Post a Comment
Read more

Stop using validations for checking constraints !

By
 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function ...
Post a Comment
Read more

Caution when using Suppress Change Event on an Interactive Grid Column

By
There are some, maybe rare, use case when you want to set the " Suppress Change Event " switch of a Dynamic Action to " Yes ". Usually that's only necessary when the Dynamic Action is fired On Change  and executes a Set Value  with the same field as a target. There might be a chain of events leading to this or just one. If you forget to set it you'll end up in an endless loop and your browser will choke. That works all fine and as expected with regular Page Items. However ... when you apply this to a column in an Interactive Grid something unexpected happens. When you set the Suppress Change Event of a Dynamic Action that fires on change of a column to Yes , the value of that item seems empty when you leave that field (column)! If you navigate back into that field, the (new) value does show up... You can call it a feature, you can call it a bug, but bottom line it is unexpected and undesired behaviour. The solution is to call the Grid method SetActiv...
Post a Comment
Read more