HAPPY NEW YEAR 2021

For Any queries, please mail us at support@funoracleapps.com

How to use Patch wizard in Oracle EBS Environment for Analysing the Patch Impact

No comments

How to use Patch wizard in Oracle EBS Environment for Analysing the Patch Impact

I am using R12.1.3 environment for demonstration.

When we have to run Patch Wizard first time in EBS, we have followed the below steps to run Patch Wizard without an internet connection to generate the latest EBS Patch Recommendation Analysis or to analyze any EBS patch(es) against your current EBS Application.

If you want to get the latest Oracle E-Business Suite patch recommendations:
Download the Patch Information Bundle (InfoBundle) on to a system that has Internet access.

The InfoBundle can be downloaded from the following locations:

or

From Patch Wizard > Preferences, set up a staging directory if not already done so.



Make sure the Patch Wizard can read from and write to the staging directory. The InfoBundle Zip file must be copied to a system that can access the Patch Wizard staging directory. If the staging directory is on a local disk, it must be copied to the system where you run Patch Wizard. If the staging directory is on a shared (network) disk, it can be copied to any system with access to the shared disk.

For example Patch Wizard runs in the concurrent tier and is usually owned by SYSADMIN, so ensure SYSADMIN can access the staging directory from the concurrent tier
 
Copy the InfoBundle Zip file to the staging directory(/tmp in my case).

Go to Patch Wizard > Recommend/Analyze Patches.

Select Create Recommendation, choose any Patch Filters, and click OK.

NOTE: if you are using a version of Patch Wizard later than Release 12.0.4, Patch Wizard will use the latest InfoBundle that exists in the staging directory, so make sure to update this InfoBundle file regularly.




NOTE: if you are using a version of Patch Wizard earlier than Release 12.0.2, like 11.5.10.2 then you must also check Upload patch information bundle before analyzing patches, to include the current InfoBundle file found in the staging directory.





NOTE: if you are using a version of Patch Wizard earlier than Release 12.0.2, like 11.5.10.2 you can optionally upload the latest InfoBundle file to Patch Wizard by clicking the Upload patch information bundle (no analysis) button, and clicking OK.




The patch info upload will take time to complete the job for the first time.

Once the Patch info is uploaded then we can run the patch wizard to analyze the patches.

1) Create a staging directory where the patches will be kept.
I am using /tmp location.

[applmgr@ebs122 sf_Downloads 03:26 PM]$cd /tmp
[applmgr@ebs122 tmp 03:38 PM]$mkdir nonad ad 




Make sure the Patch Wizard can read from and write to the staging directory. The patch Zip files must be copied to a system that can access the Patch Wizard staging directory. If the staging directory is on a local disk, it must be copied to the system where you run Patch Wizard. If the staging directory is on a shared (network) disk, it can be copied to any system with access to the shared disk.


2) Copy the downloaded patch Zip file(s) to the Patch Wizard staging directory.

In Oracle E-Business Suite 12.1.2 Release Update Pack (RUP2) and higher, all the AD product patches must be placed in the <staging  directory>/ad directory, and all the non-AD patches must be placed in the <staging directory>/nonad directory.

3) Go to Patch Wizard > Recommend/Analyze Patches.

Select Analyze Specific Patches.



4) When the patch analysis is complete, the analysis report appears on the Patch Wizard page. Click the Details icon to view the detailed report.


Reference:
741129.1


If you like please follow and comment

No comments :

Post a Comment

The Server is not able to service this request: [Socket:000445]Connection rejected, filter blocked Socket, weblogic.security.net.FilterException: [Security:090220]rule 2

No comments

The Server is not able to service this request: [Socket:000445]Connection rejected, filter blocked Socket, weblogic.security.net.FilterException: [Security:090220]rule 2

Error:

Weblogic server is starting but giving the below error while accessing the URL.

The Server is not able to service this request: [Socket:000445]Connection rejected, filter blocked Socket, weblogic.security.net.FilterException: [Security:090220]rule 2



Cause:

The error I encountered is due to WebLogic offers a concept called “connection filter“.  Connection filters provide network layer access control and allow the server(s) to block unwanted communication based on different criteria. 

Solution:


Take backup of config.xml

[applmgr@ebsupgrade config]$ cp -ip config.xml config.xml_bkp
Edit the file and open the connection part in config.xml file



In the above config.xml file, you can see that it is blocking the connection for 0.0.0.0/0 which means connections from all public IP

Change deny to allow.



<connection-filter>oracle.apps.ad.tools.configuration.wls.filter.EBSConnectionFilterImpl</connection-filter>
    <connection-filter-rule>ebsupgrade.lab * * allow</connection-filter-rule>
    <connection-filter-rule>0.0.0.0/0 * * allow</connection-filter-rule>
    <connection-logger-enabled>true</connection-logger-enabled>

Restart Application Services and try again. It will work.

If you like please follow and comment

No comments :

Post a Comment

EBS|Oracle Apps Road Map and Support Information

No comments

EBS|Oracle Apps Road Map and Support Information


Hi Guys, This is just an information blog that I am sharing as per my understanding. 

A few of  the important points are:

1) Premier support till at least 2031 for EBS  all 12.2


2) Every next version of R12.2.X which is released gets 10 yrs premier support. Let's say if R12.2.15 is released in Mar 2022 so it will get the next 10-year premier support. If a new version is released in Jul 2022 then it will be having the next 10 years of support from the release date. So it is termed as rolling support. Not to negate point 1st, all support for 12.2 will be at least 2031.

3) R12.1 premier support will end in Dec 2021.




4) Beyond Dec 2021 R12.1.3 will get an Advanced Customer Services Contract which will have a price structure.


5) Both EBS R12.1.3 and R12.2. is certified with 19c Database.





6) EBS web-based application pages are now rendered to work on tablets as well apart from laptop/desktops.

7) Forms will still be there in the future for EBS.

8)  No new EBS version like R13 or anything will be released. All developments will be on R12.2 versions only and it will keep getting updated like R12.2.10, R12.11 etc...

9) Lot of developments still going on and will keep coming regularly. 

Hope this information would be helpful for many DBA's. Long Way to go for Oracle Apps DBA.

The data is collected from Oracle and Sangam 20 webinars.



If you like please follow and comment

No comments :

Post a Comment

AutoConfig Components and Tools in Oracle Apps

No comments

AutoConfig Components and Tools in Oracle Apps








AutoConfig is a tool that supports automated configuration of an Oracle E-Business Suite Release 12 instance. All the information required for configuring an Applications instance is collected into two local repositories, called the Applications context file and the database context file.  

When AutoConfig runs on the application tier, it uses information from the Applications context file to generate all configuration files and update database profiles. When AutoConfig runs on the database tier, it uses information from the database context file to generate all configuration files used on the database tier. 


Benefits  


  • Configuration Support: AutoConfig configures the APPL_TOP, the ORACLE_HOMEs, and the supporting technology stack.  

Configuration Management:  centralizes the configuration and re-configuration of an Application instance. 

Configuration Delivery and Patching: The uptake of new technology is simplified, as new configurations and configuration changes can be provided in the form of a patch. 

AutoConfig Components 


Component 

Description 

Applications context File 

An XML repository located in the INST_TOP that contains information specific to the APPL_TOP. 

Database context File 

An XML repository located in the RDBMS ORACLE_HOME that contains information specific to that database tier. 

AutoConfig template files 

Files containing named tags that are replaced with instance-specific information from the appropriate context ("instantiation"). 

AutoConfig driver files 

Every Oracle E-Business Suite product maintains a driver file used by AutoConfig. The driver file lists the AutoConfig file templates and their destination locations. 

AutoConfig scripts 

A set of scripts that provide a simplified interface to the AutoConfig APIs. 

 

The Applications Release 12 application tier is AutoConfig-enabled, and has an Applications context file stored in the INST_TOP as $INST_TOP/appl/admin/<CONTEXT_NAME>.xml. The Applications Release 12 database tier created via Rapid Install is also AutoConfig-enabled, and has a database context file stored in the RDBMS ORACLE_HOME as <RDBMS ORACLE_HOME>/appsutil/<CONTEXT_NAME>.xml. When a change is made to any of the context files or any of the template files, the AutoConfig utility updates the Applications Release 12 configuration. 

 

 

AutoConfig Tools 


Script 

Location 

Utility 

adautocfg.sh 

On Applications Tier: 
<INST_TOP>/admin/scripts  
 
On Database Tier: 
<RDBMS_ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME> 

This script is used for running AutoConfig. 

adchkcfg.sh 

On Applications Tier: 
<AD_TOP>/bin 
 
On Database Tier: 
<RDBMS_ORACLE_HOME>/appsutil/bin 

This script may be run before running AutoConfig to review the changes on running AutoConfig. This will generate a report showing the differences between the existing configuration and what the configuration would be after running AutoConfig. 

GenCtxInfRep.pl 

On Applications Tier: 
<FND_TOP/patch/115/bin 
 
On Database Tier: 
<RDBMS_ORACLE_HOME>/appsutil/bin 

This script can be used to find out detailed information about context variables and the templates in which they are used, given all or part of a context variable name as a keyword. 

adtmplreport.sh 

On Applications Tier: 
<AD_TOP>/bin 
 
On Database Tier: 
<RDBMS_ORACLE_HOME>/appsutil/bin 

This script can be used to gather information regarding the location of the AutoConfig templates, provided the location of the instantiated files and vice versa. 

admkappsutil.pl 

On Applications Tier: 
<AD_TOP>/bin 

This script is used while applying patches to the database tier. Running this script generates appsutil.zip which may be copied over to the database tier to migrate the patch to the database tier. 

 


Reference:


If you like please follow and comment

No comments :

Post a Comment