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)

Oracle EBS 12.1.3 - Database Upgrade from 11.1.0.7 to 11.2.0.4

Steps in the following metalink documents should be followed to do the database upgrade from 11.1.0.7 to 11.2.0.4.

Interoperability Notes EBS 12.0 and 12.1 with Database 11gR2 (Doc ID 1058763.1)
Complete Checklist to Upgrade the Database to 11gR2 using DBUA (Doc ID 870814.1)

Issue Resolution for ORA-00020: maximum number of processes (%s) exceeded

select resource_name, current_utilization, max_utilization, limit_value

from v$resource_limit 

where resource_name in ('sessions', 'processes');

When ORA-00020: maximum number of processes (%s) exceeded occurred in a database and also you are NOT able to connect to the database as sys even to increase the processes parameter.
In that scenario following will work to resolve the same.

1. Instead of logging to the database via sys user as sqlplus / as sysdba you can use the following command.
sqlplus -prelim "/ as sysdba"

2.  Then you can shutdown the database using shutdown abort
SQL> shutdown abort

3. Then connect to the database via sys user as follows.
sqlplus / as sysdba

4. Then mount the database and increase the processes parameter as required.
SQL> startup mount

5. Then open the database.
SQL> alter database open

Oracle EBS R12: Creating New Branch on New Bank Errors with ORA-06508: Issue Resolution

Oracle Payables – Version: 12.1.1 and later   [Release: 12.1 and later ]
Information in this document applies to any platform.
ARHRELTS.pls 120.2
ARHRELTB.pls 120.4
ARH2RGVB.pls
ARH2RGVS.pls
HZ_RELATIONSHIPS_PKG
HZ_REGISTRY_VALIDATE_V2PUB

In Payables, when trying to save a new bank branch on a newly created bank, users are getting the following online error message:The following SQL error occurred: ORA-06508: PL/SQL: could not find program unit being called.


Payables Manager > Setup: Payment Banks and Bank Branches
Bank Branches Tab > Create
Enter Bank Name, Number and Country
Branch Options > Create New Branch
Enter Branch Name and Branch Type
Click on Save and Next or Finish

The following SQL error appears

ORA-06508: PL/SQL: could not find program unit being called.
Log shows that HZ_RELATIONSHIPS_PKG is the missing program.

Solution

1. Execute HZ_RELATIONSHIPS_PKG to create the database package

       SQL>@ARHRELTS.pls
       SQL>@ARHRELTB.pls

2. Compile HZ_REGISTRY_VALIDATE_V2PUB

     Alter package APPS.HZ_REGISTRY_VALIDATE_V2PUB compile;
     Alter package APPS.HZ_REGISTRY_VALIDATE_V2PUB compile body;

3. Retest the issue.

Reference

R12: Creating New Branch on New Bank Errors with ORA-06508: PL/SQL: Could Not Find Program Unit Being Called; HZ_RELATIONSHIPS_PKG (Doc ID 1291931.1)

Oracle EBS R12 Concurrent Managers Issue Resolution - Execute adrelink

Problem Description -
"Scheduler/Prereleaser Manager" is showing status "System Hold, Fix Manager before resetting counters".

Problem Solution -
To implement the solution, please execute the following steps:

1. Stop all middle tier services including the concurrent managers.
Please make sure that no FNDLIBR, FNDSM, or any dead process is
running.

2. Stop the database.

3. Start the database.

4. Go to cd $FND_TOP/bin
$ adrelink.sh force=y link_debug=y "fnd FNDLIBR"
$ adrelink.sh force=y link_debug=y "fnd FNDFS"
$ adrelink.sh force=y link_debug=y "fnd FNDCRM"
$ adrelink.sh force=y link_debug=y "fnd FNDSM"

5. Run the CMCLEAN.SQL script from the referenced note below (don't forget to commit).
Note 134007.1 CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables

6. Execute the following SQL:
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where
CONCURRENT_QUEUE_NAME like 'FNDSM%';

7. Start the middle tier services including your concurrent manager.

8. Retest the issue.