Change Oracle R12 Homepage navigation back to 11i

Hi,

We used to have weird requests from customers during upgrade from 11i to R12 like they want look & feel of 11i to be same as R12 and should not be changed.

here I would like to update how to revert back homepage navigation (with slideout menu ) of 12.1.3 to back old style of 11.5.10.2.

We just need to make quick modifications of profiles and then login.

below are the details.

FND: Personalization Region Link Enabled: Yes
FND: Disable Configurable Home Page: True
FND Slideout menu: Enabled
Enable Configurable HomePage: No

These should make your R12 page as 11i.

Hope this helps...

 

Running autoconfig erroring out with error >: XML-20190: (Fatal Error)

Hi,

Some times after manual modification of context file we might face weird errors during execution of autoconfig as below.

        at java.awt.EventDispatchThread.run(Unknown Source)

AC-10006: Exception - org.xml.sax.SAXParseException: file$CONTEXT_FILE<Line 57, Column 45>: XML-20190: (Fatal Error) Whitespace required. thrown while creating OAVars object for file: $CONTEXT_FILE

Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException

        at oracle.apps.ad.rapidwiz.data.AppsServer.<init>(AppsServer.java:144)

        at oracle.apps.ad.rapidwiz.data.AppsInstance.instantiate(AppsInstance.java:1038)

        at oracle.apps.ad.rapidwiz.data.AppsInstance.instantiate(AppsInstance.java:1023)

        at oracle.apps.ad.rapidwiz.data.AppsConfig.readContextFile(AppsConfig.java:1054)

        at oracle.apps.ad.rapidwiz.ui.UpgradePanel.OnNext(UpgradePanel.java:309)

        at oracle.apps.ad.rapidwiz.RIWizard.wizardValidatePage(RIWizard.java:1366)

Solution:

This happens when you do manual chnages and don't update the values properly. To resolve the issue need to review the changes in the context file and make sure that the syntax is correct in the context file.
 

export of partitioned tables from 10 to 11g resulted in huge increase in size

Observation :

performed completed export of 10g database to 11g Database using datapump utility. Some of the tablespaces are have default initial extent defined at database level. Due to this the import of objects lying under this tablespaces have grown hugely while importing.

 

e.g: Tablespace test has been created with default storage extents as 10g and any object create in this tablespace without nay storage clause has been allocated 64 KB. When this object is imported to 11g tablespace this object had been allocated a default of 8MB space even there is no data in this object.

 

Cause :

                10g

                The custom tablespaces in 10g are created with default initial extent size of database (64K by default for 10g) whereas the standard tablespaces are created with its own initial extent(Uniform) of 1MB. Each subpartition in custom tablespaces are created with a default initial extent of 64KB even there is no data in the database.

                11g

                Whereas the default initial extent size allocation for database from 11.2.0.2 is 8MB to improve performance. Hence as part of import the partitions created in custom tablespaces has picked up default value of 8MB for every empty sub partition created resulting in huge increase of database.

 

 

Solution:

                To prevent this default allocation we need set the hidden parameter _partition_large_extents to FALSE explicitly and then initiate the import.

 

Initial Extent Size of a Partition Changed to 8MB from 64KB After Upgrade to 11.2.0.2 or Later (Doc ID 1295484.1) explains on allocation of default size

 

I tested the scenario by creating one test partition with and without the init parameter and the results are as expected. I will include this step to my import process document.

1)      Create a empty table with partitions and it allocated 8MB ß Init parameter _partition_large_extents is not defined in pfile

2)      Set init parameter _partition_large_extents to FALSE and created a empty table with partitions in custom ts and it allocated only 64KB.