Skip to main content

Oracle Cloud @ Customer

 So now that we have two Exadata machines and have gone through the process of migrating all our applications to Exadata was it worth it.


Notes:

Learning curve - this was significantly greater than expected. The solution keeps evolving and the rate of change is sometimes staggering.


Pros:

  • Multi-tenant and RAC by default
  • Speed - we had an enormous increase in performance (after tuning our queries for Exadata)
  • It is great to have some of the hardware issues abstracted away from us.
  • Oracles monitoring of the hardware on our system is great

Cons:

  • Cost - the solution is more expensive than what we had but you get what you pay for
  • Loss of control in some areas and then dealing with Oracle support.
  • What happens after a refresh cycle.


All things considered it was a good move for us. Looking forward to our new move to Gen 2 and a true hybrid cloud experience.

Comments

Post a Comment

Popular posts from this blog

MANIFEST.MF merge JDeveloper for an executable jar

Goto your project > properties. Then click on deployment in the menu. Edit or add a jar deployment profile. Fill in the details under jar options (select Include manifest and give it a main class name) Also remember that the merge functionality only works with a BLANK line at the end of the merge file. REALLY this caught me. My merge file contents: Class-Path: commons-codec-1.3.jar [...empty line here CRLF...]
1 comment
Read more

ADF sort of generic screen for tables with the same structure

We have a couple (about a hundred) of tables with the same structure (Code, Description, Create Date, Update Date). So I wanted to do something simple so that I did not have to create all these screens 1) EO   I created the EO based on one of the tables I had that had the above columns. I then Added a transient attribute called table name to my EO based on a groovy expression. (the expression needs to change as I am reading web tier stuff from the model layer but I will fix this later) I then generated a java class for my EO. And added the following overriden method to my newly created java class. protected StringBuffer buildDMLStatement(int i, AttributeDefImpl[] attributeDefImpl,   AttributeDefImpl[] attributeDefImpl2, AttributeDefImpl[] attributeDefImpl3, boolean b) {   StringBuffer statement = super.buildDMLStatement(   i, attributeDefImpl, attributeDefImpl2, attributeDefImpl3, b); return new StringBuffer(StringUtils.replace(statement.to...
Post a Comment
Read more

ADF: LOV Description instead of code

I keep on forgetting how to do this so this is a note to self in terms I understand (ie pictures): Add the related entiy object to yours (in the example we are adding RegionEO(list of values) to CountryEO) Now add the RegionName field from the EO and a transient attribute (I named mine RegionNameLOV) Make the transient attribute updateable and base it on the expression RegionName (the description you wish to display) Add a list of values to RegionNameLOV and map BOTH key to parent fk (region id here) AND RegionName to your transient coulmn (RegionNameLOV).  Map the transient as an Input text with List of Values. Then just drag the lov item onto the page (RegionNameLOV)
Post a Comment
Read more