Steps to Change Oracle Weblogic Server Node Manager & Administration User Password

The option to set the Oracle WebLogic Server Administration User password to a
non-default value is available during Oracle E-Business Suite installation. This section
describes the procedure to use (on the run file system) if you need to change the
password at a later time.

The EBS WebLogic Domain uses Node Manager to control the Administration Server
and the managed servers. For the EBS WebLogic Domain, the Node Manager and
WebLogic Server Administration User passwords must be same, otherwise the AD
control scripts will not work properly.

Important: 

If you need to change the Administration User password, you must change the Node Manager password first, If you do not do this, the WebLogic Server configuration change will not be detected and the next online patching cycle may fail.

The instructions that follow should be performed on the run file system. The password

change will be automatically propagated to the patch file system during the next adop

prepare phase or fs_clone operation.

1.Shut down all application tier services except the Admin Server.

On the primary node, run the command:

$ <ADMIN_SCRIPTS_HOME>/adstpall.sh -skipNM -skipAdmin

2. Change the Oracle WebLogic Server Node Manager and Administration User passwords by performing the following steps on weblogic console

Changing the Oracle WebLogic Server Node Manager Password

-Login to weblogic to server console: 


 

- Login using the current weblogic admin username and  password.

- Click on the lock and edit button

- Click on Domain link
- Click on Security TAB

   

- Click on "Advanced" Tab

- Provide the new node manager  password which you want to configure for weblogic admin user

- Click on "save"

 

- Verify settings updated successfully and then click on "Activate changes"

- Verify all changes has been activated successfully.

Changing the Oracle WebLogic Server Administration User Password

- Click on "Security Realms"

- Click on "myrealm"

-  select "users and groups" and select weblogic User:

 

- Provide same password as we have provided above for node manager.

- Make sure the settings has been updated successfully.

- take  backup of the following files:

$FMW_HOME/user_projects/domains/EBS_domain_PROD/servers/AdminServer/security/boot.properties

$FMW_HOME/user_projects/domains/EBS_domain_PROD/servers/oafm_server1/security/boot.properties

$FMW_HOME/user_projects/domains/EBS_domain_PROD/servers/forms-c4ws_server1/security/boot.properties

$FMW_HOME/user_projects/domains/EBS_domain_PROD/servers/forms_server1/security/boot.properties

$FMW_HOME/user_projects/domains/EBS_domain_PROD/servers/oacore_server1/security/boot.properties

After this we need to edit the following configuration file "boot.properties" for all managed and admin server  using text editor and update the password field with the above configured password ( new password).

password={AES}ATsg8vMdZRg1pDofFsrAiPUfqtDqyNarOKaBkqDtbqs\=

username={AES}ni/ohZITMmwRT8ft1wdc5dGr2sO+qlA5S0JwZVQrzEc\=

After editing all the above mentioned files we need to restart the application services using adstpall.sh and adstrtal.sh scripts. Above files password will be automatically encrypted during the start of the application services.

    
After restarting of services make sure all application services are started successfully. Verify that you are able to access weblogic server console and access ERP application.

3. Start all services, using the command:

$ <ADMIN_SCRIPTS_HOME>/adstrtal.sh

Custom Application in Oracle EBS R12.2

Creating a Custom Application in Oracle E-Business Suite Release 12.2 (Doc ID 1577707.1)

Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2 (Doc ID 1577661.1)

Oracle EBS 12.2.4 application tier autoconfig fails after database upgrade from 11.2.0.3 to 11.2.0.4

Problem

Oracle EBS 12,2,4 application tier autoconfig fails with following error.

WARNING: [AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution.  Errors are grouped by directory and phase.
The report format is:
      <filename>  <phase>  <return code where appropriate>

  [PROFILE PHASE]
  AutoConfig could not successfully execute the following scripts:
    Directory: /u01/CRP/fs1/inst/apps/CRP_oracle/admin/install
      jtfictx.sh              INSTE8_PRF         1

AutoConfig is exiting with status 1

Cause

DECLARE
*
ERROR at line 1:
ORA-20000: Oracle Text error:
DRG-50857: oracle error in drixmd.GetIndexRec
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at "CTXSYS.DRUE", line 160
ORA-06512: at "CTXSYS.CTX_DDL", line 948
ORA-06512: at "CTXSYS.AD_CTX_DDL", line 336
ORA-06512: at line 96



Solution
connect /as sysdba

ALTER SESSION SET CURRENT_SCHEMA=SYS;
grant select on SYS.DBA_PROCEDURES to ctxsys;

ALTER SESSION SET CURRENT_SCHEMA=CTXSYS;
SET PAGESIZE 0
SELECT 'Calling ctx/admin/driacc.plb on ' || SYSTIMESTAMP FROM dual;
SET PAGESIZE 10

@@?/ctx/admin/driacc.plb;

@$ORACLE_HOME/rdbms/admin/utlrp.sql

set serveroutput on
execute sys.validate_context;

select comp_name, status, substr(version,1,10) as version from dba_registry where comp_id = 'CONTEXT';

Reference
 Can Not Validate CTXSYS.DRIACC Package (Doc ID 1906873.1)

Oracle EBS R12 JSP Compilation Issue Resolution

Modify the value of "s_apctimeout" to -1 in the apps tier $CONTEXT_FILE which means indefinite wait.

Then Execute the autoconfig on application tier.

Then recompile the JSP again.

EBS R12.2 ADOP Patching & Issues

ADOP Patching Cycle

# Prepare for patching:
$ adop phase=prepare

# Apply patches:
$ adop phase=apply patches=<patch number>

# Finalize patch application:
$ adop phase=finalize

# Perform cutover:
$ adop phase=cutover

$ . <EBS_ROOT>/EBSapps.env run

These steps are performed post-cutover.
$ perl <AD_TOP>/bin/admkappsutil.pl

This will create the appsutil.zip file in <INST_TOP>/admin/out.

On the database tier, as the oracle user:

Copy or ftp the appsutil.zip file to the RDBMS_ORACLE_HOME, 

then run the following commands:

$ cd <RDBMS_ORACLE_HOME>
$ unzip -o appsutil.zip

Run AutoConfig on the database tier.

Run AutoConfig on the run file system of each application tier node.

Start the application tier services. 

# Perform cleanup:
$ adop phase=cleanup

$ adop phase=fs_clone 

ADOP Important queries 

select ADOP_SESSION_ID,PREPARE_STATUS,APPLY_STATUS,
FINALIZE_STATUS,CUTOVER_STATUS,CLEANUP_STATUS,
ABORT_STATUS,STATUS,ABANDON_FLAG,NODE_NAME 
from AD_ADOP_SESSIONS order by ADOP_SESSION_ID;

Note: STATUS
N - Not Applied In the current node but applied in other nodes
R - Patch Application is going on.
H - Patch failed in the middle. (Hard Failure)
F - Patch failed in the middle but user tried to skip some failures.
S - Patch Application succeeded after skipping the failed jobs.
Y - Patch Application succeeded.
C - Reserved for clone and config_clone. Indicates clone completed 

select ADOP_SESSION_ID, BUG_NUMBER, STATUS, 
APPLIED_FILE_SYSTEM_BASE, PATCH_FILE_SYSTEM_BASE, 
ADPATCH_OPTIONS, NODE_NAME, END_DATE, CLONE_STATUS
from ad_adop_session_patches
order by end_date desc; 

ADOP Patching Issues

Issue :

Error while running command: adop phase=prepare

ERROR at line 1:

ORA-20008: No Concurrent Manager is defined that can run concurrent program

ADZDPATCH

ORA-6512: at "APPS.AD_ZD_ADOP", line 240

Solution:

FNDLOAD
 apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct 
$AD_TOP/patch/115/import/US/adzdpatch.ldt - CUSTOM_MODE=FORCE 

Oracle EBS Important Profile Options

ICX: Limit Time
Determines the maximum number of hours a user can be logged on per session.

ICX:Session Timeout
Determines the length of time (in minutes) of inactivity in a user's form session before the session is disabled.

"ICX: Limit Time" is used to control the total time a session can be logged in, regardless of what activity is being done.
It is always assigned to higher value than "ICX: Session Timeout".

Configure Oracle EBS R12 with RAC

Using Oracle 12c Release 1 Real Application Clusters with Oracle E-Business Suite Release 12 (Doc ID 1490850.1)
Using Oracle Real Application Clusters 11g Release 2 with Oracle E-Business Suite Release 12 (Doc ID 823587.1)

Oracle EBS 12.2.3 Installation

Oracle E-Business Suite Release 12.2: Technical Planning, Getting Started, and Go-Live Checklist (Doc ID 1585857.1)
Oracle E-Business Suite Release 12.2.3 Readme (Doc ID 1586214.1 )
Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1)
Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)
Oracle E-Business Suite 12.2 Patching Technology Components Guide (Doc ID 1355068.1)

Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID 1320300.1)
Oracle E-Business Suite Release 12.2 Technology Stack Documentation Roadmap (Doc ID 1934915.1)
Oracle E-Business Suite Technology Stack and Applications DBA Release Notes for Release 12.2.3 (Doc ID 1606170.1)
Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1)
Oracle EBusiness Suite Installation and Upgrade Notes Release 12 (12.2) for Linux x8664
(Doc ID 1330701.1)

Oracle EBS R12 DB Tier Cloning Issue Resolution

Oracle EBS R12 DB Tier Cloning was NOT successful. But Database was mounted. Then following can be attempted to recover and startup the database.

1. Try to open the database using resetlogs option.

SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/u01/TEST/db/apps_st/data/system01.dbf'


2. If similar error comes like above, Shutdown immediate     

SQL> Shutdown immediate

3. Remark the parameter in initTEST.ora:  

 UNDO_MANAGEMENT=AUTO
 UNDO_TABLESPACE=APPS_UNDOTS

4. Add the parameter in initTEST.ora :         

    UNDO_MANAGEMENT=MANUAL
    _ALLOW_RESETLOGS_CORRUPTION = TRUE
    _ALLOW_ERROR_SIMULATION = TRUE

5. Startup database with Manual undo management.using new initTEST.ora      

sqlplus '/as sysdba'

SQL> startup mount pfile=initTEST.ora

SQL> recover database using backup controlfile until cancel;

SQL> alter database open resetlogs;

6. Create new UNDO Tablespace  

SQL> Create UNDO tablespace NEW_UNDOTS datafile '/u01/TEST/db/apps_st/data/undo01.dbf' size 2048M;

7. Take offline the OLD Undo Tablespace :  
 
SQL> alter tablespace APPS_UNDOTS offline;

8. Take online the NEW Undo Tablespace :  

SQL> alter tablespace NEW_UNDOTS online;

9. Shutdown the database :      

SQL> shutdown immediate;

10. Edit the initTEST.ora :  

    + Remark the parameter :

    UNDO_MANAGEMENT=MANUAL
    _ALLOW_RESETLOGS_CORRUPTION = TRUE
    _ALLOW_ERROR_SIMULATION = TRUE

    + Add and edit the parameter :

    UNDO_MANAGEMENT=AUTO
    UNDO_TABLESPACE=NEW_UNDOTS 

11. Startup the database :

SQL> startup

12. Set the  default Undo tablespace as NEW_UNDOS

SQL> alter system set undo_tablespace=NEW_UNDOTS;

13. Then we can drop the OLD Undo tablespace :   

SQL> drop tablespace APPS_UNDOTS including contents and datafiles;

14. Also reuse the existing TEMP tablespace tempfiles or create a new TEMP tablespace.

Open Database failed - DATAFILE NEEDS MORE RECOVERY TO BE CONSISTENT ORA-1194 ORA-1547 ORA-1110 (Doc ID 1528788.1)