Oracle E-Business Suite with Oracle Autonomous Database on Dedicated Exadata Infrastructure

Oracle E-Business Suite with Oracle Autonomous Database on Dedicated Exadata Infrastructure Oracle Autonomous Database on Dedicated Exadata Infrastructure is certified for use with Oracle E-Business Suite (EBS) Release 12.2. Customers who use Oracle Autonomous Database can expect to benefit from increased system availability as well as automation of tasks such as provisioning, patching, and tuning. This initial limited availability certification includes procedures for several key tasks, starting with migration of an existing EBS environment to Oracle Cloud Infrastructure (OCI) and Oracle Autonomous Database. Further procedures are provided for subsequent backup and restore, cloning, and patching of the migrated EBS environment. If you would like to learn more about the limited availability program for Oracle E-Business Suite with Oracle Autonomous Database, contact the EBS on Autonomous Database Program Office at ebs-adb-info_ww@oracle.com.

How to Change Profile Option Value Without Forms? (Doc ID 943710.1)

 

APPLIES TO:

Oracle Application Object Library - Version 11.5.10.0 to 12.2.10 [Release 11.5 to 12.2]
Information in this document applies to any platform.

GOAL

How to update a Profile Option using SQL (if Forms login is not possible)?

SOLUTION

Please use the API:  FND_PROFILE
The package FND_PROFILE  can be found in file AFPFPROS.pls

 

Note: FND_PROFILE is not public interface.  Use of this API is considered a customization and should be tested in a test environment.

FND_PROFILE.SAVE - sets the value of a profile option permanently to the database,
at any level. This routine can be used at runtime or during patching.
This routine will not actually commit the changes; the caller must commit.
The levels are: 'SITE', 'APPL', 'RESP', or 'USER'.

Examples of use:

FND_PROFILE.SAVE('P_NAME', 'P_VAL', 'SITE');
FND_PROFILE.SAVE('P_NAME', 'P_VAL', 'APPL', 321532);
FND_PROFILE.SAVE('P_NAME', 'P_VAL', 'RESP', 321532, 345234);
FND_PROFILE.SAVE('P_NAME', 'P_VAL', 'USER', 123321);

returns: TRUE if successful, FALSE if failure.


To update a Profile Option value at Site level, you need to run the SQL Script below:

Declare
value Boolean;
Begin
value := fnd_profile.save('APPS_DATABASE_ID','<new_value>','SITE');
End;

Example:

===========
Sample Code
===========
DECLARE
stat boolean;
BEGIN
dbms_output.disable;
dbms_output.enable(100000);
stat := FND_PROFILE.SAVE('GUEST_USER_PWD', 'GUEST/ORACLE', 'SITE');
IF stat THEN
    dbms_output.put_line( 'Stat = TRUE - profile updated' );
ELSE
    dbms_output.put_line( 'Stat = FALSE - profile NOT updated' );
END IF;
commit;
END;
===============
End of Sample Code
===============

Description of the FND_PROFILE.SAVE function parameters:

Function SAVE(
X_NAME in varchar2,             /* Profile name you are setting */
X_VALUE in varchar2,            /* Profile value you are setting */
X_LEVEL_NAME in varchar2,       /* Level that you're setting at:
                                   'SITE','APPL','RESP','USER', etc. */
X_LEVEL_VALUE in varchar2 default NULL,
                                /* Level value that you are setting at,
                                   e.g. user id for 'USER' level.
                                   X_LEVEL_VALUE is not used at site level. */
X_LEVEL_VALUE_APP_ID in varchar2 default NULL,
                                /* Used for 'RESP' and 'SERVRESP' level;
                                   Resp Application_Id. */
X_LEVEL_VALUE2 in varchar2 default NULL
                                /* 2nd Level value that you are setting at.
                                   This is for the 'SERVRESP' hierarchy. */
) return boolean;

 

 

Reference: https://docs.oracle.com/cd/E26401_01/doc.122/e20927.pdf

FND_CONCURRENT_QUEUE Control Code Meaning

 In the FND_CONCURRENT_QUEUE table we have a column named control_code.

To get the details of the code present in the column we can use below script.

SQL> select lookup_code,meaning from apps.fnd_lookups where lookup_type = 'CP_CONTROL_CODE' order by lookup_code;

LOOKUP_CODE    MEANING
----------                    ------------------------------
A                               Activating
B                               Activated
D                               Deactivating
E                               Deactivated
H                               System Hold, Fix Manager before resetting counters
N                               Target node/queue unavailable
O                               Suspending concurrent manager
P                                Suspended
Q                               Resuming concurrent manager
R                               Restarting
T                               Terminating
U                               Updating environment information
V                               Verifying
X                               Terminated

adop fs_clone failure

adop fs_clone failure

Validating credentials.

Initializing.

    Run Edition context  : /ascprd/app/applmgr/IRASCPRD_R122/fs1/inst/apps/IRASCPRD_Admin_host/appl/admin/IRASCPRD_Admin_host.xml

    Patch edition context: /ascprd/app/applmgr/IRASCPRD_R122/fs2/inst/apps/IRASCPRD_Admin_host/appl/admin/IRASCPRD_Admin_host.xml

    Patch file system free space: 696.66 GB

Validating system setup.

    [UNEXPECTED]Invalid worker Count: 0

    [UNEXPECTED]Error validating worker count

[STATEMENT] Please run adopscanlog utility, using the command

"adopscanlog -latest=yes"

to get the list of the log files along with snippet of the error message corresponding to each log file.

adop exiting with status = 2 (Fail)

Fix : Run with one worker

$ adop phase=fs_clone worker=1

Solution worked for others

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.

How to choose the number of workers for adop or adpatch

 How to choose the number of workers:

For less than 32 cores set:

• parallel_max_servers = 2 x number of CPU cores
• AD Parallel workers – start with 1.5 x number of CPU cores. Possibly increase to 2 x number of CPU cores
• job_queue_processes = 2 x number of CPU cores

For 32 cores and above, start with:

• parallel_max_servers = 1.5 x number of CPU cores
• AD Parallel workers = between 1.0 and and 1.5 x number of CPU cores
• job_queue_processes = 1.5 x number of CPU cores

EBS 12.2.9 RUP Patch 28840850 Hung with Error "aiosp2() Error: failure in usdspn() Contents of error buffer are: usdsop cannot create a new process" (Doc ID 2878394.1)