ADOP fails with ORA-12516: TNS:listener could not find available handler with matching protocol stack

No comments
While running ADOP I saw below error in adconfig log file.

Error:

ORA-12516: TNS:listener could not find available handler with matching protocol stack

CAUSE;

 This is an issue with the number of database process/sessions. 

SOLUTION:

We can check utilization of processes and session.

 SQL>  select resource_name, current_utilization, max_utilization from v$resource_limit where resource_name in ('processes','sessions');

RESOURCE_NAME                  CURRENT_UTILIZATION MAX_UTILIZATION
------------------------------ ------------------- ---------------
processes                                      478             500
sessions                                       499             540


We can bounce the database, and increase the number of processes/sessions . Re-run the patch application.


Reference: adop fails with "ORA-12516: TNS:listener could not find available handler with matching protocol stack" (Doc ID 2105049.1)

No comments :

Post a Comment

How to check/configure Oracle Apps EBS and ASCP(APS) integration

No comments
In this post we are going to see the  steps that are needed to validate/configure the EBS and ASCP instance integration. This Setup changes might be  required after cloning and setting up new APS destination and EBS source.


Source EBS: DEBS

Destination APS : DAPS

Steps:


1) Create DBapps and public schema of both source and destination instance.


On Source Instance DEBS create DB link with name 
DAPS connecting to DAPS instance. DB link should be present in both public and APPS schema.

On Destination Instance DAPS create DB link with name 
DEBS connecting to DEBS instance. DB link should be present in both public and APPS schema.


2. Log in to the Target (ASCP) System and choose “Advanced Planning Administrator”.
Navigate to Admin --> Instances. The Application Instances window appears.
Insert record for the Source (ERP) system as follows:
Instance Code : Give a new name for the Instance Code (uniquely identified).
Instance Type : Select “Discrete” (consult Functional Consultant).
Version : 11i (default, for 11i E Business Suite).
From Source to APS : Database Link created on the Source System for Target System Database.
From APS to Source : Database Link created on the Target System for Source System Database.
Check “Enable Flag”, “Allow ATP” and “Allow Release”.

You can verify the values from below table on APS side

select * from MSC_APPS_INSTANCES.

3) On EBS source set Below profile value as DB link name pointing to APS instance.


MRP:ATP Database Link = DAPS



4)  On EBS side check below table/view should be having correct value.


select * from MRP_AP_APPS_INSTANCES_ALL;

In case multiple rows are available in the above query, then update
MRP_AP_APPS_INSTANCES_ALL.ALLOW_ATP_FLAG = 1 for only the one correct instance we want to use for ATP.
For all other rows update it as 2.

In case no rows are present in the table the we can insert.


 insert into mrp.MRP_AP_APPS_INSTANCES_ALL values (1,46523506,'27-SEP-18','FUN','DEBS','DAPS',-1,'27-SEP-18',1396,'30-APR-08',104,6269,'HR',2,2,2,14,13,14,13,12,11,NULL,13,14,14,14,14,14,NULL,NULL,NULL,NULL,0,NULL,0,NULL,NULL,NULL,NULL,NULL,NULL,1,1,NULL,2,'x.SEGMENT1',2,NULL,NULL,'C');


There might be various other steps than need to worked upon by you functional or technical consultant. 

No comments :

Post a Comment

Oracle Apps R12-->REP-0004: Warning: Unable to open user preference file

No comments
If we are getting Error while running reports.

Error:

REP-0004: Warning: Unable to open user preference file

Solution:

Make sure the file prefs.ora is located in your "home" directory  If it is not, change the directory or filename as appropriate.

Copy $ORACLE_HOME/tools/admin/prefs.ora to $HOME

If error is not solved after copy the prefs.ora also then you have to check privileges.

After changing privileges bounce application services.

No comments :

Post a Comment