Output Post Processor (OPP) in Oracle Applications R12 and 11i
OPP runs as a service that can be managed through Oracle Applications Manager (OAM) from the System Activity page (Navigation: Applications Dashboard > Applications
Service (from the dropdown list) > Go).
How to Increase the number of Output Post Processors?
1.Log on to Applications with “System Administrator” responsibility.
2.Navigate to Concurrent -> Manager -> Define.
3. Query for the “Output Post Processor” service.
4. Click on “Work Shifts” and increase the number of processes
How to get OPP manager log file location?
$APPLCSF/log/<SID>/FNDOPP####.txt OR
1,System Administrator > Concurrent > Manager > Administer
2,Search for ‘Output Post Processor’
3,Click the ‘Processes’ button .
4, Click the Manager Log button. This will open the ‘OPP’
Upload the OPP log file.
In some cases, Output Post Processor is not starting up and it shows Actual and Target are showing different values when we query for Output Post Processor.
The log files show no error message. In this case, apply the following possible solution for starting the OPP.
1. Shut down the internal manager by using adcmctl.sh stop apps/apps
2. Make sure there are no FNDLIBR processes running:
$ ps -ef| grep FNDLIBR OR ps -ef|grep applprod|grep FNDLIBR
3. If there is any FNDLIBR process please kill it $ kill -9 pid
4. Run cmclean.sql script
5. Restart the internal manager by using adcmctl.sh start apps/apps
or How to kill and start Output Post Processor (OPP) Background:
This article explains how to kill OPP and restart the same
Solution:
1,System Administator > Concurrent > Manager > Administer
2,Query “Output Post Processor” -> Processes button
Get the sytem id of “Output Post Processor”
3,ps -ef|grep [system id]
4,kill -9 [system id] in Unix
5,System Administator > Concurrent > Manager > Administer
6,Query “Output Post Processor” -> Restart button
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Apps password change routine in Release 12.2 E-Business Suite changed a little bit. We have now extra options to change password, as well as some manual steps after changing the password using FNDCPASS.
Whether you use FNDCPASS or AFPASSWD to change the APPLSYS/APPS password, you must also perform some additional steps. This is because in R12.2, the old AOL/J connection pooling is replaced with Weblogic Connection Pool ( JDBC Data source ). Currently this procedure is not yet automated. It would be good, if this can be automated using some WLS scripting.
Important: These steps must be carried out on the run file system.
Shut down the application tier services using the $INST_TOP/admin/scripts/adstpall.sh script.
Change the APPLSYS password, as described for the utility you are using.
Start Admin Server using the $INST_TOP/admin/scripts/adadminsrvctl.sh script. Do not start any other application tier services.
Change the “apps” password in WLS Data source as follows:
Log in to WLS Administration Console.
Click Lock & Edit in Change Center.
In the Domain Structure tree, expand Services, then select Data Sources.
On the “Summary of JDBC Data Sources” page, select EBSDataSource.
On the “Settings for EBSDataSource” page, select the Connection Pool tab.
Enter the new password in the “Password” field.
Enter the new password in the “Confirm Password” field.
Click Save.
Click Activate Changes in Change Center.
Start all the application tier services using the $INST_TOP/admin/scripts/adstrtal.sh script.
Verify the WLS Datastore changes as follows:
Log in to WLS Administration Console.
In the Domain Structure tree, expand Services, then select Data Sources.
On the “Summary of JDBC Data Sources” page, select EBSDataSource.
On the “Settings for EBSDataSource” page, select Monitoring > Testing.
Select “oacore_server1“.
Click Test Data Source
Look for the message “Test of EBSDataSource on server oacore_server1 was successful“.
Important: Steps 4, 5 and 6 are only applicable when changing the APPLSYS password. They are not applicable when changing passwords for product schemas or the SYSTEM schema.
In the next prepare phase after the password change, adop will invoke EBS Domain Configuration to ensure that the WLS data source on the patch file system will be synchronized with the new APPS password.
Below i face an error when i was running adop session.
When i was running adop phase=cleanup i was hit with the below error
[applmgr@r122 ~]$ adop phase=cleanup
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Please wait. Validating credentials…
RUN file system context file: /u01/oracle/PROD/fs2/inst/apps/PROD_r122/appl/admin/PROD_r122.xml
PATCH file system context file: /u01/oracle/PROD/fs1/inst/apps/PROD_r122/appl/admin/PROD_r122.xml
************* Start of session *************
version: 12.2.0
started at: Wed May 24 2021 03:34:53
APPL_TOP is set to /u01/oracle/PROD/fs2/EBSapps/appl
[STATEMENT] Using 4 workers (Default: 4, Recommended maximum limit: 62)
Cleanup is not done in earlier session
[START 2021/05/24 03:35:27] adzdoptl.pl run
ADOP Session ID: 4
Phase: cleanup
Log file: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/4/adop_20210524_033421.log
[START 2021/05/24 03:35:48] cleanup phase
[EVENT] [START 2021/05/24 03:35:52] Performing Cleanup steps
[EVENT] [START 2021/05/24 03:35:57] Running CLEANUP ddls in ddl handler table
Calling: adpatch options=hotpatch,nocompiledb interactive=no console=no workers=4 restart=no abandon=yes defaultsfile=/u01/oracle/PROD/fs2/EBSapps/appl/admin/PROD/adalldefaults.txt patchtop=/u01/oracle/PROD/fs2/EBSapps/appl/ad/12.0.0/patch/115/driver logfile=cleanup.log driver=ucleanup.drv
ADPATCH Log directory: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/4/cleanup_20210524_033421/PROD_r122/log
[EVENT] [END 2021/05/24 03:39:43] Running CLEANUP ddls in ddl handler table
[EVENT] Cleaning up ABORT DDL from DDL Handler Table
[START 2021/05/24 03:39:54] Generating All DDL Report
[EVENT] Report: /u01/oracle/PROD/fs2/EBSapps/appl/ad/12.0.0/sql/ADZDALLDDLS.sql
[EVENT] Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/4/cleanup_20210524_033421/PROD_r122/adzdallddls_20210524_033957.out
[END 2021/05/24 03:39:58] Generating All DDL Report [EVENT] Calling cleanup in QUICK mode [WARNING] Cleanup may take a while. Please wait. [ERROR] Failed to execute sql statement : declare result varchar2(10); begin ad_zd.cleanup(‘QUICK’); exception when others then raise_application_error(-20001,’Error while calling ad_zd.cleanup’ || sqlerrm); end; [ERROR] SQLPLUS error: buffer=
SQL*Plus: Release 10.1.0.5.0 – Production on Wed May 24 03:40:01 2021
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> SQL> Connected.
SQL> declare ERROR at line 1: ORA-20001: Error while calling ad_zd.cleanupORA-01555: snapshot too old: rollback segment number 2 with name “_SYSSMU2_735814084$” too small
ORA-06512: at line 7
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[UNEXPECTED]Error occurred while calling cleanup plsql API
[UNEXPECTED]Cleanup phase completed with errors/warnings. Please check logfiles
Log file: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/4/adop_20210524_033421.log
adop exiting with status = 1 (Fail)
[applmgr@r122 ~]$
To overcome this issue.I have extended the undotablespace using below:
SQL> select TABLESPACE_NAME,FILE_NAME from dba_data_files where TABLESPACE_NAME like ‘APPS_UNDOTS1’;
TABLESPACE_NAME FILE_NAME
APPS_UNDOTS1 /u01/oracle/PROD/data/undo01.dbf
SQL> ALTER DATABASE DATAFILE ‘/u01/oracle/PROD/data/undo01.dbf’ RESIZE 10240M;
Database altered.
SQL>
Then again i executed the adop phase=cleanup
applmgr@r122 ~]$ adop phase=cleanup
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Please wait. Validating credentials…
RUN file system context file: /u01/oracle/PROD/fs2/inst/apps/PROD_r122/appl/admi
n/PROD_r122.xml
PATCH file system context file: /u01/oracle/PROD/fs1/inst/apps/PROD_r122/appl/ad
min/PROD_r122.xml
************* Start of session *************
version: 12.2.0
started at: Fri Feb 28 2021 04:11:18
APPL_TOP is set to /u01/oracle/PROD/fs2/EBSapps/appl
[STATEMENT] Using 4 workers (Default: 4, Recommended maximum limit: 59)
Cleanup is not done in earlier session
[START 2021/02/28 04:11:45] adzdoptl.pl run
ADOP Session ID: 4
Phase: cleanup
Log file: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/4/adop_20210228_041049.log
[START 2021/02/28 04:12:03] cleanup phase
[EVENT] [START 2021/02/28 04:12:06] Performing Cleanup steps
[EVENT] [START 2021/02/28 04:12:11] Running CLEANUP ddls in ddl handler table
Calling: adpatch options=hotpatch,nocompiledb interactive=no console=no workers=4 restart=no abandon=yes defaultsfile=/u01/oracle/PROD/fs2/EBSapps/appl/admin/PROD/adalldefaults.txt patchtop=/u01/oracle/PROD/fs2/EBSapps/appl/ad/12.0.0/patch/115/driver logfile=cleanup.log driver=ucleanup.drv
ADPATCH Log directory: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/4/cleanup_20210228_041049/PROD_r122/log
[EVENT] [END 2021/02/28 04:13:26] Running CLEANUP ddls in ddl handler table
[EVENT] Cleaning up ABORT DDL from DDL Handler Table
[START 2021/02/28 04:13:32] Generating All DDL Report
[EVENT] Report: /u01/oracle/PROD/fs2/EBSapps/appl/ad/12.0.0/sql/ADZDALLDDLS.sql
[EVENT] Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/4/cleanup_20210228_041049/PROD_r122/adzdallddls_20210228_041335.out
[END 2021/02/28 04:13:36] Generating All DDL Report
[EVENT] Calling cleanup in QUICK mode
[WARNING] Cleanup may take a while. Please wait.
[EVENT] [END 2021/02/28 04:57:56] Performing Cleanup steps
[END 2021/02/28 04:58:05] cleanup phase
[START 2021/02/28 04:58:11] Generating AD_ZD_LOGS Report
[EVENT] Report: /u01/oracle/PROD/fs2/EBSapps/appl/ad/12.0.0/sql/ADZDSHOWLOG.sql
[EVENT] Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/4/cleanup_20210228_041049/PROD_r122/adzdshowlog.out
[END 2021/02/28 04:58:24] Generating AD_ZD_LOGS Report
[END 2021/02/28 04:58:25] adzdoptl.pl run
adop phase=cleanup – Completed Successfully
Log file: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/4/adop_20210228_041049.log
adop exiting with status = 0 (Success)
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Oracle E-Business Suite Installation (EBS 12.2.0).
Now i am going to install Oracle E-Business Suite Installation (EBS),For this I have already created an instance in my cloud account.
I have created an instance in the following specificaions as mentioned below,
OS Version: Oracle Linux 7.9
Shape: VM Standard E 2.4, 4 core CPU and 32 GB Memory.(depends of the CPU, our EBS installation software running time is decided)
Instance name: ANDHRA
Once the instance is created we can proceed with the installation procedures.
Then connect with putty login connect as root user.
Better install the software using Vnc ,it is more advantage because while we are installing the software if any power outage occurs it doesn’t disturbs the installation.
if you are going to use vnc install the following packages,
Stop the firewall using the below command systemctl stop firewall.
Then set the selinux parameter as permissive which is in the vi /etc/selinux/config location.
After that you have to reset the system using init 6 or setenforce 0
Add the following set of lines to the files.
vi /etc/sysctl.conf
vi /etc/security/limits.conf
Next add the groups and users,here i am adding oracle and applmgr users to the newly created dba group.
set the passwords for the oracle and applmgr user.
Examine the locations of ora inventory and change the mod and group of orainst.loc
Create the below mentioned directories that is needed to install the software.
Add and attach the block volumes(here i am adding block volume size of 700GB) after attaching the block volume,view the block volume details and click ISCSI commands and information,once you click that there will be the informations for connecting and disconnecting.
Do the partition for the newly added block volume.Simply just attaching the block volume will not be partitioned.
Download the ebs software version that we are going to install as wget file.And move the file to the EBS directory in the /u01/stage mountpoint where we are going to unzip the software.
Run the given pre install,
yum install oracle-ebs-server-R12-preinstall --------------------------it is for ebs.
yum install oracle-database-server-12cR2-preinstall ------------------it is for database.
unlink /usr/lib/libXtst.so.6 and link libXtst.so.6.1 with /usr/lib.it is important because it is helpful to load the frontend page.
we are going to create the stage area,then specify the directory which contains the zipped installation media.
Move the downloaded software (ie. wget.sh file) to the stage area location to perform installation.
Here starts the rapid installation process.
In this choose Install Oracle E-business Suite Release 12.2.0
Here provides you a option to receive security updates via My Oracle Support if you want enable the check Box and provide the mail Email ID.
in this window it opts for configuration choice either we can create a new configuration or Load the saved configuration.
Here we can see Global System Settings leave it by default as it is don’t change any values in this window.
Now only we are going to configure the Database Node Configuration,set up those parameters such as database sid,database host name,db operating system.
choose the Licensing Type , suite Licensing or Component Licensing.I have choosen suite licensing.
It shows the License Additional Products,don’t do any change,click Next.
In this choose country out of the available regions which is displayed.
select the character set by specifying the language you are going to use.I choose the language as American_English – US.
Next we have to configure the Primary Applications Node Configuration,such as setting the primary host name,operating system,Apps OS User,Apps OS Group,Apps Base Dir,Apps Instance Dir
Provide the Application User Information such as WLS Admin User,Password and proceed further for Installation.
Continue with the Node Information.Database node,primary apps node information should be given here.
Rapid Install Wizard is performing the system checks,once it is fine we can move further.
It shows the list of pre-install tests if and only it satisfies all the condition we can go with the installation process.For us the instance passed all of the pre-install tests.
we are set with the process,installation is in progress it takes some time to install the software.
Depending upon the CPU core that we have specified in the instance creation the installation time may differ.
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8
Oracle E-Business Suite Installation (EBS 12.2.0).
Now i am going to install Oracle E-Business Suite Installation (EBS),For this I have already created an instance in my cloud account.
I have created an instance in the following specificaions as mentioned below,
OS Version: Oracle Linux 7.9
Shape: VM Standard E 2.4, 4 core CPU and 32 GB Memory.(depends of the CPU, our EBS installation software running time is decided)
Instance name: ANDHRA
Once the instance is created we can proceed with the installation procedures.
Then connect with putty login connect as root user.
Better install the software using Vnc ,it is more advantage because while we are installing the software if any power outage occurs it doesn’t disturbs the installation.
if you are going to use vnc install the following packages,
Stop the firewall using the below command systemctl stop firewall.
Then set the selinux parameter as permissive which is in the vi /etc/selinux/config location.
After that you have to reset the system using init 6 or setenforce 0
Add the following set of lines to the files.
vi /etc/sysctl.conf
vi /etc/security/limits.conf
Next add the groups and users,here i am adding oracle and applmgr users to the newly created dba group.
set the passwords for the oracle and applmgr user.
Examine the locations of ora inventory and change the mod and group of orainst.loc
Create the below mentioned directories that is needed to install the software.
Add and attach the block volumes(here i am adding block volume size of 700GB) after attaching the block volume,view the block volume details and click ISCSI commands and information,once you click that there will be the informations for connecting and disconnecting.
Do the partition for the newly added block volume.Simply just attaching the block volume will not be partitioned.
Download the ebs software version that we are going to install as wget file.And move the file to the EBS directory in the /u01/stage mountpoint where we are going to unzip the software.
Run the given pre install,
yum install oracle-ebs-server-R12-preinstall --------------------------it is for ebs.
yum install oracle-database-server-12cR2-preinstall ------------------it is for database.
unlink /usr/lib/libXtst.so.6 and link libXtst.so.6.1 with /usr/lib.it is important because it is helpful to load the frontend page.
we are going to create the stage area,then specify the directory which contains the zipped installation media.
Move the downloaded software (ie. wget.sh file) to the stage area location to perform installation.
Here starts the rapid installation process.
In this choose Install Oracle E-business Suite Release 12.2.0
Here provides you a option to receive security updates via My Oracle Support if you want enable the check Box and provide the mail Email ID.
in this window it opts for configuration choice either we can create a new configuration or Load the saved configuration.
Here we can see Global System Settings leave it by default as it is don’t change any values in this window.
Now only we are going to configure the Database Node Configuration,set up those parameters such as database sid,database host name,db operating system.
choose the Licensing Type , suite Licensing or Component Licensing.I have choosen suite licensing.
It shows the License Additional Products,don’t do any change,click Next.
In this choose country out of the available regions which is displayed.
select the character set by specifying the language you are going to use.I choose the language as American_English – US.
Next we have to configure the Primary Applications Node Configuration,such as setting the primary host name,operating system,Apps OS User,Apps OS Group,Apps Base Dir,Apps Instance Dir
Provide the Application User Information such as WLS Admin User,Password and proceed further for Installation.
Continue with the Node Information.Database node,primary apps node information should be given here.
Rapid Install Wizard is performing the system checks,once it is fine we can move further.
It shows the list of pre-install tests if and only it satisfies all the condition we can go with the installation process.For us the instance passed all of the pre-install tests.
we are set with the process,installation is in progress it takes some time to install the software.
Depending upon the CPU core that we have specified in the instance creation the installation time may differ.
Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8
