The Incident Archive

The move to Exadata and Cloud at Customer - Database:  Why Exadata:  Performance - Exadata is engineered to run the Oracle database, and we can now eliminate hardware as a cause of performance problems, eliminate storage latency issues. Every feature of the Oracle Database - enough said. Why Cloud at Customer:  Alleviates problems with hardware and avoiding patching and hardware problems seems like a big win to me. Data security: Unfortunately we have some very important information stored in our system and the cloud was not an option Scalability: With PAAS we will be able to meet our horizontal scalability needs. Interesting findings and other notes: 1) Maximum 8 VM's on the Exadata 2) Active / Active and RAC Database conversion: 1) Character Set Conversion:  https://docs.oracle.com/database/121/NLSPG/ch11charsetmig.htm#NLSPG983  there is a document and a utility ( DMU ), color me surprised. ( https://www.oracle.com/technetwork/database/dat...

After a two year of blogging break I am back to blogging. What has changed: in a nutshell new stuff and exciting new challenges, Why the break: I really can't say I have done any ground breaking work in the last couple of years and although I was still solving hard problems they seemed like the same pattern repeated. Also I have been quite disillusioned with ADF, Solaris, java and the general direction of the products I was using. What is to come: We will be moving off our current T5-8 Solaris hardware onto Oracle cloud @ Customer. This means a move from SPARC to x86. The initial plan was SPARC to Dell server on-prem. JCS and Exadata for now until we can do a port of our ADF applications onto a more cloud native platform.