Tag Archives: 12.1

Oracle R12 (and others) OA Framework Dislikes IE 8/9/10 Compatibility View

In our environment we try to have a newer/fresher set of web applications, but

Tools -> Compatibility View Settings
Tools -> Compatibility View Settings

some are simply too old to upgrade.  They like running in the pre-Microsoft Silverlight days of old Active-X controls and scripted Java. But Internet Explorer needed to move forward, and with version 8 was introduced a feature called “Compatibility View” which reverts back to older IE6/7 style page handling.

So what’s the big deal here? Well, in mixed-legacy environments some standard Windows administrators set the following as a default – Display Intranet sites in Compatibility View.  That makes older Sharepoint sites happy. Makes old web software happy.

Makes new software go from this:

Internet Explorer Browser 10 Compatibility View Oracle R12
Looks fine at first. (IE10 w/Compatibility View)
Internet Explorer Browser 10 Compatibility View Oracle R12 - Broken
Refreshed…cleared cache…I have a broken R12 page.

to this:

 

 

 

 

 

 

 

 

So, the fix is as simple as unchecking that box for [ ] Display Intranet sites in Compatibility View, and specifically adding only those URI’s (web addresses/URLs) that actually require the original browser “old” security model.

Otherwise, you’ll see more pages like this:

PasswordsMax JavaScript error in IE10 with Compatibility View
It’s all because of that same Compatibility View checkbox setting.

 

Change VARCHAR2 to 32K – 12c Edition

Oracle has made a few changes to the database to allow organizations to reduce the cost of migrating to Oracle 12c.  One of these changes is with the size limits that have been placed on the VARCHAR2, NVARCHAR2 and RAW data types.  In past versions of Oracle database the maximum size for these data types were 4,000 bytes.  In Oracle 12c, these data types can now  be increased to 32,767 bytes.

In order to set these data types to use the larger setting, the MAX_STRING_SIZE parameter needs to be set.  The only values that this parameter can take is STANDARD and EXTENDED.  Once the parameter has been set to EXTENDED, you cannot go back to STANDARD.

Note: Altering MAX_STRING_SIZE will update database objects and possibly invalidate them

To increase the size of the VARCHAR2, NVARCHAR2 and RAW columns for a non-CDB database,  these steps need to be followed: 

   …

View original post 96 more words