Session Timeout for OAF Pages in EBS 12.2

Follow the below procedure to change the session timeout for EBS 12.2 OAF(Web HTML) Pages and set in sync with profile "ICX: Session Timeout"

Login to EBS Application Server. Navigate to ${EBS_ORACLE_HOME}/deployment_plansdirectory and modify the timeout values for all below plan.xml files

./oafm/plan.xml

./forms/plan.xml

./oacore/plan.xml

Change the value for variable "WeblogicApplication_SessionDescriptor_TimeoutSecs" from default 1800 to required value (e.g. 14400(4hrs))

WeblogicApplication_SessionDescriptor_TimeoutSecs

1800

To

WeblogicApplication_SessionDescriptor_TimeoutSecs

14400

Perform these steps for all the plan.xml files listed above.

Once the changes are made bounce all the below services to reflect the changes.

1.       Apache, oafm, oacore, forms.

Once bounce is completed, verify the timeout by navigating to application deployment screen as below:

Login to WebLogic Console à Deployments à expand oacore(1.0.0) application à Click on /OA_HTML

Navigate to Configuration tab and verify timeout value for field "Session Timeout"

adop fs_clone/prepare fails with [UNEXPECTED]Invalid worker Count: 0

We recently added a node to our current EBS application. As part of the node addition steps, tried to executed adop phase=fs_clone but it failed immediately with errors.


Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Validating credentials.
Initializing.
    Run Edition context  : /app/EBD//fs2/inst/apps/EBD_oraapp01/appl/admin/EBD_oraapp01.xml
    Patch edition context: /app/EBD//fs1/inst/apps/EBD_oraapp01/appl/admin/EBD_oraapp01.xml
    Patch file system free space: 41.85 GB
Validating system setup.
    [UNEXPECTED]Invalid worker Count: 0
    [UNEXPECTED]Error validating worker count

Later tried to assign worker count of value 8 manually as below but it also failed
  $ adop phase=fs_clone workers=8
 
Validating credentials.
Initializing.
    Run Edition context  : /app/EBD//fs2/inst/apps/EBD_oraapp01/appl/admin/EBD_oraapp01.xml
    Patch edition context: /app/EBD//fs1/inst/apps/EBD_oraapp01/appl/admin/EBD_oraapp01.xml
    Patch file system free space: 41.85 GB
    [UNEXPECTED]Specified value 8 is not supported by the database.
    [UNEXPECTED]A maximum of 1 workers can be invoked.
    [UNEXPECTED]Error validating worker count

Observed the same issue with prepare phase as well.

Solution:
The default worker count information(recomm & max)  is stored in a file adpawc.xml that can be found under $APPL_TOP/admin/$TWO_TASK/log

Somehow this file has been modified with recommended value as 0 and max value as 1 during node addition.

FileContent:
<?xml version="1.0"?>
<WORKER_COUNT>
        <RECOMMENDED>0</RECOMMENDED>
        <MAX>1</MAX></WORKER_COUNT>

Update recommended &  max value based on cpu count.

Here I updated recommended value as 8 and max value as 64 and saved the file.

Once the changes are made, fs_clone went smoothly.

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...

 

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.