ORA-24067: exceeded maximum number of subscribers for queue APPLSYS.FND_CP_GSM_OPP_AQ

ORA-24067: exceeded maximum number of subscribers for queue APPLSYS.FND_CP_GSM_OPP_AQ

ORA-06512: at "APPS.FND_CP_OPP_IPC", line 346

ISSUE:XML reports  complete in warning

Solution:

select count(*) from applsys.FND_CP_GSM_OPP_AQTBL;

create table applsys.FND_CP_GSM_OPP_AQTBL_bkp2 as select * from applsys.FND_CP_GSM_OPP_AQTBL;

exec dbms_aqadm.purge_queue_table('FND_CP_GSM_OPP_AQTBL', null, null);

select count(*) from applsys.FND_CP_GSM_OPP_AQTBL ;

sqlplus username/passwd @$FND_TOP/patch/115/sql/afopp002.sql

exec fnd_cp_opp_ipc.remove_all_subscribers();

SEVERE: [FATAL] servername: servername.

11.2.0.3 Runinstaller failed to execute on OEL6.5 64bit

Error:-

SEVERE: [FATAL] mangalyan.bangalore.bedford.local: mangalyan.test.com
Refer associated stacktrace #oracle.install.commons.util.exception.DefaultErrorAdvisor:37
INFO: Advice is ABORT
SEVERE: Unconditional Exit
INFO: Adding ExitStatus FAILURE to the exit status set
INFO: Finding the most appropriate exit status for the current application
INFO: Exit Status is -1
INFO: Shutdown Oracle Database 11g Release 2 Installer

Solution:
 Check the below detail

hostname
uname -a
cat /etc/hosts
ifconfig

After correcting the issue i am able to execute.

PRVE-0426 : The size of in-memory file system mounted

Starting check for /dev/shm mounted as temporary file system ...

ERROR:

PRVE-0426 : The size of in-memory file system mounted as /dev/shm is "998" megabytes which is less than the required size of "2048" megabytes on node ""
PRVE-0426 : The size of in-memory file system mounted as /dev/shm is "998" megabytes which is less than the required size of "2048" megabytes on node ""

Check for /dev/shm mounted as temporary file system failed

Fix:-

[root@rac2 ~]# mount -o remount,size=2G /dev/shm
[root@rac2 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda3              26G   12G   13G  50% /
/dev/sda1              99M   46M   49M  49% /boot
tmpfs                 2.0G     0  2.0G   0% /dev/shm

The size of in-memory file system mounted at /dev/shm is "2048" megabytes which does not match the size in /etc/fstab as "0" megabytes

Error:-


Starting check for /dev/shm mounted as temporary file system ...

WARNING:

The size of in-memory file system mounted at /dev/shm is "2048" megabytes which does not match the size in /etc/fstab as "0" megabytes
The size of in-memory file system mounted at /dev/shm is "2048" megabytes which does not match the size in /etc/fstab as "0" megabytes

Check for /dev/shm mounted as temporary file system passed

Open /etc/fstab using vi or any text editor :-

Locate the line of /dev/shm and use the tmpfs size option to specify your expected size,

tmpfs      /dev/shm      tmpfs   defaults,size=2g   0   0


The /etc/fstab content format is documented in man fstab and the tmpfs filesystem options can be found in man mount

change effective immediately, run this remount command :

mount -o remount /dev/shm

iscsiadm: Login failed to authenticate with target

Error:-

iscsiadm: >    TargetPortalGroupTag=1
iscsiadm: login response status 0201
iscsiadm: Login failed to authenticate with target
iscsiadm: discovery login to 192.168.88.17 rejected: initiator error (02/01), non-retryable, giving up
iscsiadm: disconnecting conn 0xb23010, fd 3
iscsiadm: Could not perform SendTargets discovery.

Solution:-

Change below values on node 1 and node 2(not in SAN)/etc/iscsi/iscsid.conf

discovery.sendtargets.auth.authmethod = CHAP
discovery.sendtargets.auth.username = muthu

discovery.sendtargets.auth.password = Yourpassword
node.session.auth.authmethod = CHAP
node.session.auth.username = muthu

node.session.auth.password = Yourpassword

Step by Step Oracle E-Business Suite Upgrade from R12.2.3 to R12.2.4

Follow the below mentioned steps in sequential order to upgrade from Oracle E-Business Suite Release 12.2.3 to 12.2.4

Section 4: Apply the Latest AD and TXK Delta Release Update Packs

Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)

Section 2: Apply Required Technology Patches

Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1)

Section 3: Apply the R12.AD.C.Delta.5 and R12.TXK.C.Delta.5 Release Update Packs

If you are...	Follow this path...
Upgrading to Oracle E-Business Suite Release 12.2 from Release 11i, 12.0, or 12.1	Path A
Installing a new Oracle E-Business Suite system	Path A
Already using Oracle E-Business Suite Release 12.2 (below AD/TXK R12.AD.C.Delta.5 and R12.TXK.Delta.5 codelevel)	Path B

3.1 Path A - Upgrade and New Installation Customers

1.  Source the run edition environment file.

$ . <EBS_ROOT>/EBSapps.env run

2.  Apply the latest Application Tier Technology patches on the run file system.

3. Start up only the Weblogic AdminServer service on the run edition application tier file system.

$ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

4. Unzip patches and run adgrants.

1. Download and unzip the following patches:
• Patch 18283295:R12.AD.C.Delta.5
• Patch 14845118:R12.AD.C (Windows only)
• Patch 19164901:R12.AD.C (Windows only)
• Patch 18288881:R12.TXK.C.Delta.5
• Patch 18886213:R12.TXK.C
• Patch 19259764:R12.FND.C

Note: You should also download and unzip any applicable patches from Section 4: Apply Additional Critical Patches.

2. Follow the instructions in the patch readme of Patch 18283295:R12.AD.C.Delta.5, to execute adgrants.

5. Apply Patch 18283295:R12.AD.C.Delta.5 (plus additional critical patches) in hotpatch mode on the run edition application tier file system. Windows users also need to merge and apply two additional patches, as shown.

UNIX:

$ adop phase=apply patches=18283295 hotpatch=yes

6. Apply Patch 18288881:R12.TXK.C.Delta.5 merged with Patch 18886213:R12.TXK.C (plus additional critical patches) in hotpatch mode on the run edition application tier file system:

$ adop phase=apply patches=18288881,18886213 hotpatch=yes merge=yes

8.Complete the online patching cycle by running the following commands in the order

$ . <EBS_ROOT>/EBSapps.env run
$ adop phase=finalize
$ adop phase=cutover
$ . <EBS_ROOT>/EBSapps.env run
$ adop phase=cleanup

9.Synchronize the file systems (conditional)

• If you are ultimately going to apply the Oracle E-Business Suite 12.2.2 Release Update Pack, you must now synchronize the file systems by running the following command:

$ adop phase=fs_clone

6.2 Path B - Existing Customers (Release 12.2.2 or Release 12.2.3) upgrading to Oracle E-Business Suite 12.2.4 Release Update Pack

    Source the run edition applications environment.

    UNIX:

    $ . <INSTALL_BASE>/EBSapps.env run

    Windows:

    C:\><INSTALL_BASE>\EBSapps.cmd run

    Start an online patching cycle.

    $ adop phase=prepare

    Apply Oracle E-Business Suite Release 12.2.4 Patch 17919161.

    UNIX:

    $ adop phase=apply patches=17919161

  

    Complete the online patching cycle by running the following commands in the order shown.

    UNIX:

    $ adop phase=finalize

    $ adop phase=cutover

    $ . <INSTALL_BASE>/EBSapps.env run

    $ adop phase=cleanup

  

    Synchronize file systems

    Synchronize the file systems using the command shown below. This action will copy the new run edition code and configuration to the other file system, to help the next online patching cycle complete faster.

    $ adop phase=fs_clone

Section 7: Post-Update Steps

1.Apply Oracle E-Business Suite Release 12.2.4 Online Help

Apply Oracle E-Business Suite Release 12.2.4 Online Help Patch 17919162 merged with Patch 19290141 using adop hotpatch mode on the run file system.

$ adop phase=apply patches=17919162,19290141 hotpatch=yes merge=yes

2.Grant flexfield value set access to specific users (required)

Register new products (conditional)

The new products below (added in Release 12.2.4) are not automatically registered in your system. If you intend to use new products, register them using License Manager. For instructions, refer to Oracle E-Business Suite Maintenance Guide, Release 12.2 (Part No. E22954).

Product Short Name       Product Name

yms        Oracle Yard Management

cmi         Oracle In-memory Cost Management

Perform Product-Specific Steps (conditional) :-

Customer Relationship Management tasks:

    Run the "Update Time Structure" concurrent program.

    Run the "Update Time Structure" concurrent program, if it was not executed after opening the latest General Ledger period.

    Verify whether this concurrent program was already executed by running the following query in APPS user.

    SELECT COUNT(*)

    FROM OZF_TIME_DAY

    WHERE TRUNC(SYSDATE) BETWEEN START_DATE AND END_DATE;

    If the query returns 1, the concurrent program was already executed; there is no need to execute it again. If the query returns 0, execute the concurrent program. Suggested parameters are:

        FROM DATE: 1-JAN-1997 0:0:0

        TO DATE: (the last date previously defined in General Ledger)

        All Level : Y

    It is recommended to schedule this program to run at regular intervals whenever new GL periods are opened. If not executed, YEAR_ID column in table OZF_FUNDS_UTILIZED_ALL_B will not be populated.

Navigate to Oracle Trade management Administrator responsibility --> view  --> request  --> Submit a new request  --> click ok --> enter concurrent program name (Update Time Structure)  --> enter below parameter --> click submit.

 

References

• 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 Release 12.2.4 Readme (Doc ID 1617458.1)