Skip to main content

The Exadata move

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/database-technologies/globalization/dmu/overview/index.html)

2) Varchar2 sizes and upgrade to greater than 4000 chars: With the conversion to avoid truncation we moved to 4000 char instead of bytes and extended our string size. MAX_STRING_SIZE

3) Moving nightly jobs to the database using dbms_scheduler: Ended up being quite easy, just the zipping we where doing needed a bit of effort.

4) Export import
5) Possible 18c upgrade


Labels:

Comments

Post a Comment

Popular posts from this blog

ADF Encountered deferred syntax #{ in template text.

OracleJSP error: oracle.jsp.parse.JspParseException:  Error: Encountered deferred syntax #{ in template text.  If intended as a literal, escape it or set directive  deferredSyntaxAllowedAsLiteral This normally happens when you have some tag lib dependancy problems but this was  not the case for me... My problem: For some reason my model project had web stuff in it(public html etc)  so I had to remove the public html stuff from my project and manually edit the Model.jpr project file and remove the tag lib entries at the bottom o the file. Go figure.    
3 comments
Read more

JBO-25013: TooManyObjectsException

oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key[Key null ]. Ok so for you it may be trying to insert a duplicate record this should explain your problem (also check trigger they could be the cause.) NOTE: You can also try to create a new duplicate EO if you have a page with two VO's using the same EO. This could sort your problems. For me I needed to add a launch listener on my LOV and clear the cache of my vo. LOV <af:inputListOfValues id="NameId" popupTitle="#{bindings.Name.hints.label}" value="#{bindings.RolName1.inputValue}" label="#{bindings.RolName1.hints.label}" model="#{bindings.RolName1.listOfValuesModel}" required="#{bindings.RolName1.hints.mandatory}" columns="#{bindings.RolName1.hints.displayWidth}" shortDesc="#{bindings.RolName1.hints.tooltip}" launchPopupListener="#{backingBeanScope.backingBean.launchPop
Post a Comment
Read more

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