Syed Saad Ali
Syed Saad Ali

Oracle ACE Pro

Oracle Solution Architect

Oracle E-Business Suite

Oracle Cloud Infrastructure

Oracle Fusion Middleware

Oracle Database Administration

Oracle Weblogic Administration

Syed Saad Ali
Syed Saad Ali

Oracle ACE Pro

Oracle Solution Architect

Oracle E-Business Suite

Oracle Cloud Infrastructure

Oracle Fusion Middleware

Oracle Database Administration

Oracle Weblogic Administration

AppsDBA CV Download CV Contact Me

Home

About Me

Technically-sophisticated professional with extensive experience in updating server security, executing routine back-ups, and designing and implementing tests of the system to address issues with accessing data

  • Adept at leading the planning, designing, developing, testing, and deploying efficient solutions within Oracle EBS system, in order to satisfy strategic, financial, and operations needs of the organization.
  • Skilled in planning and managing successful projects, mitigating risks, controlling costs, and directing project teams. Instrumental in monitoring routine maintenance of system, implementing the ERP systems, and approving budget.
  • Proven success in analyzing business processes/process re-engineering and recommending solutions. Deft at establishing IT service continuity management strategies, disaster recovery plans and associated test procedures of each critical functional area of the organization.
  • Age: 36
  • Residence: Pakistan
  • Freelance: Available
  • Address: Karachi, PAKISTAN
My Services
Oracle E-Business Suite Upgrade
Oracle E-Business Suite Migration
Oracle Database Upgrade or Migrate
Oracle Maximum Availability Architecture
Performance Evaluation
Pricing
Hire Me On Upwork
$ 35 Hour
  • Database Administration
  • Oracle E-Business Suite Administration
  • Configuration, Administration, Cloning, Patching, Migrating, Support, Maintenance, Monitoring, tuning and capacity planning, User Management, Backup/Recovery Management
Order Now
Hire Me on Fiverr
$ 35 Hour
  • Database Administration
  • Oracle E-Business Suite Administration
  • Configuration, Administration, Cloning, Patching, Migrating, Support, Maintenance, Monitoring, tuning and capacity planning, User Management, Backup/Recovery Management
Order Now
Hire Team
$ 40 Hour
  • Database Administration
  • Oracle E-Business Suite Administration
  • Configuration, Administration, Cloning, Patching, Migrating, Support, Maintenance, Monitoring, tuning and capacity planning, User Management, Backup/Recovery Management
Order Now

Resume

Resume
Experience
Senior Apps DBA
2022- Present
Senior Apps DBA
Computer & Systems Engineering Company
My role includes infrastructure support, capacity planning, installation, configuration, database design, and migration, up gradation, performance monitoring, security,  database backups, data recovery plan, and procedures including application server administration
Lead Infrastructure Consultant
2020-2021
Lead Infrastructure Consultant
ITANZ Group
Managed Oracle cloud infrastructure, compute, storage, networking, connectivity, and edge service, database management, analytics, integration, and Oracle weblogic clustering environment over Oracle Cloud IAAS.  Collaborated with the Oracle corporation staff for offering technical support to diagnose and troubleshoot common problems.
Professional Freelancer
2020 - 2022
Professional Freelancer
Upwork Inc.
Collaborated with Clients for the Task Related to Oracle Database, Oracle E-Business Suite, Oracle Cloud Infrastructure, Oracle Weblogic
Assistant Director (Databases)
2015-2020
Assistant Director (Databases)
Pakistan Civil Aviation Authority
Managed ERP for implementing the structures effectively, while limiting the resources consumed in the planning process. Improved IT/business processes and investigations to resolve the user’s issues as well as offered user’s training to help the user in operating the system in efficient way.
Education
Newports Institute Of Communication & Economics
2008 - 2011
Newports Institute Of Communication & Economics
Pakistan

Newports Institute Of Communication & Economics offers a B.S. in Computer Science.

Certificate
Oracle University
2013
Oracle University
USA

Oracle E-Business Suite R12 Financials Certified Expert  Consultant, PAYABLES 

Certificate
Oracle University
2014
Oracle University
USA

Oracle E-Business Suite R12 Applications Database Administrator Certified Professional 

Certificate
Oracle University
2011
Oracle University
USA

Oracle Database 11g Administrator Certified Professional 

Certificate
Skills
Oracle Expertise
  • Oracle Databases
  • Oracle E-Business Suite
  • Oracle Weblogic
  • Oracle Cloud Infrastructure
  • Oracle Database Appliances
Languages
  • English
System
  • Linux
    90%
  • Microsoft
    75%
  • SOLARIS
    65%
  • AIX
    60%
Knowledge
  • Installation/Configuration
  • Capacity Planning
  • Data Recovery Plan
  • Oracle Database Migration and Upgrade
  • Oracle ERP Migration and Upgrade
  • Linux and Windows management
  • Performance Evaluation

Blog
December 24, 2024 FMW 12.2.1.4 Installation for OAM
Oracle Access Manager

Oracle Fusion Middleware 12.2.1.4 Introduction

  1. What is Oracle Fusion Middleware 12.2.1.4?

Oracle Fusion Middleware 12.2.1.4 is a set of software tools and services that help businesses build and run applications. It acts as a bridge between different systems, making it easier to connect, manage, and secure enterprise applications whether they are in the cloud, on-premises, or both.

  1. What Does It Do?

  • Develop Applications: Provides tools to create modern web, mobile, and enterprise applications.
  • Integrate Systems: Connects different software and systems so they work together.
  • Manage Content: Organizes documents and web portals for easy collaboration.
  • Analyze Data: Includes tools to generate reports and make data-driven decisions.
  • Secure Access: Manages user logins and permissions to protect sensitive information.

  1. Key Components

  • Oracle WebLogic Server: The foundation for running applications reliably and efficiently.
  • Oracle SOA Suite: Helps combine services (like APIs) into workflows for seamless integration.
  • Oracle WebCenter: Used to manage digital content and create user-friendly portals.
  • Oracle Identity Management: Ensures secure user authentication and authorization.
  • Oracle Business Intelligence (BI): Provides dashboards and reports for analyzing business performance.

  1. Why Use It?

  • Flexibility: It works in hybrid environments, combining cloud and on-premises systems.
  • Scalability: Handles small applications to large, complex enterprise systems.
  • Efficiency: Speeds up application development and deployment.
  • Enhanced Security: Centralized tools protect apps and user data.
  • Improved Integration: Makes different systems work as one unified solution.

  1. Benefits for Businesses

  • Reduces complexity by centralizing tools and systems.
  • Increases productivity by automating workflows and simplifying integration.
  • Provides actionable insights to make better decisions.
  • Ensures systems remain secure and compliant.

Summary

Oracle Fusion Middleware 12.2.1.4 is a comprehensive platform designed to help businesses build, integrate, and secure applications while enabling advanced collaboration, analytics, and scalability. It’s ideal for organizations managing diverse IT systems in a hybrid environment.

Oracle Documentation To Be Used for FMW,OID,ODIP 12.2.1.4

Ø Oracle Identity & Access Management Certification Matrix  Oracle Fusion Middleware 12.2.1.4 Certification Matrix

Ø Install Oracle Fusion Middleware Infrastructure Oracle Fusion Middleware 12.2.1.4

Ø Installing and Configuring the Oracle Access Management Software ORACLE ACCESS MANGER 12.2.1.4

FMW Infrastructure Installation

1  Create OAM Operating System User

[root@oamserver ~]# useradd -g oinstall -G dba -d /home/oammgr -m -s /bin/bash oammgr

[root@oamserver ~]# passwd oammgr

Changing password for user oammgr.

New password:

Retype new password:

passwd: all authentication tokens updated successfully.

[root@oamserver ~]#

[root@oamserver u02]# chown -R oammgr:oinstall /u02

2. Untar the JDK

[oammgr@oamserver u02]$ tar -xvzf jdk-8u361-linux-x64.tar.gz
[oammgr@oamserver ~]$ cd /u02/jdk1.8.0_361/bin

 

3. Unzip the FMW12.2.1.4

[oammgr@oamserver fmw_infrastructure]$ ll
total 1597388
-rwxrwxrwx. 1 oammgr oinstall 1635717400 Nov 17 22:35 V998828-01.zip
 
[oammgr@oamserver fmw_infrastructure]$ unzip -qo V998828-01.zip
[oammgr@oamserver fmw_infrastructure]$ ll
total 3195068
-r-xr-xr-x. 1 oammgr oinstall 1636007590 Sep 13  2019 fmw_12.2.1.4.0_infrastructure.jar 
-rw-r–r–. 1 oammgr oinstall      10185 Sep 16  2019 fmw_12214_readme.html
-rwxrwxrwx. 1 oammgr oinstall 1635717400 Nov 17 22:35 V998828-01.zip

4. Running Installer FMW12.2.1.4

The 12c installation starts with the common infrastructure which contains Weblogic, the RCU, and other common components.

Start the installation with the command ‘java -jar fmw_12.2.1.4.0_infrastructure.jar for version 12.2.1.4.

[oammgr@oamserver ~]$ cd /u02/jdk1.8.0_361/bin/
[oammgr@oamserver bin]$ export DISPLAY=192.168.1.123:0.0
[oammgr@oamserver bin]$ ./java -jar /u02/fmw_infrastructure/fmw_12.2.1.4.0_infrastructure.jar

Click Next

  • Click Skip Auto Updates
  • Click Next

  • On this step, set the value for ORACLE_HOME, which is to be the location of core installed files.
  • Click Next

  • For the next step leave the ‘FUSION MIDDLEWARE INFRASTRUCTURE‘ selected.
  • Click Next

  • Click Next

  • Verify the settings on the Installation Summary screen.  
  • To change entries, Click BACK on the pertinent screen.
  • Once satisfied with the settings, click the INSTALL button to begin the installation.

  • Installation Started

  • Click Next

  • Click Finish
December 23, 2024 Oracle Database 19c Installation For OAM
Oracle Access Manager

Oracle Database 19c Installation on OEL 8.10

Operating System Setup

1. For Automatic Setup of Operating System Packages and Parameters, Run the following command with Root user

[root@oidserver ~]# dnf install -y oracle-database-preinstall-19c

If you are using RHEL8 or CentOS8, you can pick up the RPM from the OL8 repository and install it. It will pull the dependencies from your normal repositories.

curl -o oracle-database-preinstall-19c-1.0-2.el8.x86_64.rpm https://yum.oracle.com/repo/OracleLinux/OL8/appstream/x86_64/getPackage/oracle-database-preinstall-19c-1.0-2.el8.x86_64.rpm

dnf -y localinstall oracle-database-preinstall-19c-1.0-2.el8.x86_64.rpm

2. Set the password for the “oracle” user.

[root@oamserver ~]# passwd oracle

3. Set secure Linux to permissive by editing the “/etc/selinux/config” file, making sure the SELINUX flag is set as follows.

SELINUX=permissive

4. Once the change is complete, restart the server or run the following command.

[root@oamserver ~]# setenforce Permissive

5. Once the change is complete, restart the server or run the following command.

If you have the Linux firewall enabled, you will need to disable or configure it. To disable it, do the following.

# systemctl stop firewalld
# systemctl disable firewalld

6. Create the directories in which the Oracle software will be installed.

[root@oamserver ~]# mkdir -p /u01/app/oracle/product/19.0.0/dbhome_1
[root@oamserver ~]# chown -R oracle:oinstall /u01/app
[root@oamserver ~]# chmod -R 775 /u01

7. Create an Environment Variable file for the Oracle Database on the Oracle User Home Directory

[oracle@oamserver ~]$ vi setEnv.sh

# Oracle Settings
export TMP=/tmp
export TMPDIR=$TMP

export ORACLE_HOSTNAME=oidserver.com
export ORACLE_UNQNAME=OAMDB
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/19.0.0/dbhome_1
export ORA_INVENTORY=/u01/app/oraInventory
export ORACLE_SID=OAMDB
export DATA_DIR=/u01/oradata

export PATH=/usr/sbin:/usr/local/bin:$PATH
export PATH=$ORACLE_HOME/bin:$PATH

export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
export CLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib
[oracle@oidserver ~]$

8. Unzip Software Binaries

Copy the Downloaded Database 19c Zip (V982063-01.zip) file on the /u01/app/oracle/product/19.0.0/dbhome_1 Directory

[oracle@oamserver ~]$ cd /u01/app/oracle/product/19.0.0/dbhome_1
[oracle@oamserver dbhome_1]$ unzip -oq V982063-01.zip

Running Database Installer

[oracle@oamserver dbhome_1]$ export DISPLAY=192.168.1.124:0.0
[oracle@oamserver dbhome_1]$ export CV_ASSUME_DISTID=OEL7.8

[oracle@oamserver dbhome_1]$ ./runInstaller
Launching Oracle Database Setup Wizard…

The response file for this session can be found at:
 /u01/app/oracle/product/19.0.0/dbhome_1/install/response/db_2024-11-30_10-01-36PM.rsp

You can find the log of this install session at:
 /u01/app/oraInventory/logs/InstallActions2024-11-30_10-01-36PM/installActions2024-11-30_10-01-36PM.log

Select Single Instance Database Installation

Click Next
Select Enterprise Edition

Click Next
Confirm Oracle Base Location

Click Next
Select Database Administration Groups

Click Next
Click Next
Click Install
Installation Started
Run the Script with Root User

[root@oidserver ~]# /u01/app/oracle/product/19.0.0/dbhome_1/root.sh

Click OK
Click Close

Database Creation through DBCA
[oracle@oamserver ~]$ . ./setEnv.sh

[oracle@oamserver ~]$ dbca
Select Advanced Configuration

Click Next
Select Oracle Single Instance database

Select Template Name General Purpose or TransactionProcessing

Click Next
Enter Global Database name and SID

Uncheck Option Create as Container database

Click Next
Click Next
Click Next
Click Next
Click Next
Click Next
Click Next
We used the Same Password for all Administrative accounts.

Click Next
Click Next
Verify the settings on the Installation Summary screen.

To change entries, Click BACK to the pertinent screen.

Once satisfied with the settings, click the Finish button to begin the installation.
Database Creation Started
Click Close

Alter Database Parameters
SQL> alter system set open_cursors=800 scope=both;
SQL> alter system set processes=1000 scope=spfile;
SQL> alter system set sessions=1000 scope=spfile;

Hope you found this document informative and gained valuable insights.
December 17, 2024 Step by Step Installing and Configuring OID 12.2.1.4
Oracle Internet Directory

Step-by-Step Guide: Installing and Configuring Oracle Internet Directory 12.2.1.4

 

INTRODUCTION Oracle Internet Directory(OID)

 

What is OID?

Oracle Internet Directory (OID) is a scalable LDAP-based directory service that acts like a centralized address book for businesses. It stores and manages user identities, application data, and system information securely in one place, simplifying operations for enterprises.

 

What Can It Do?

  • Centralized Storage: Keeps all user and system data in one secure, easily accessible location.
  • LDAP Support: Fully compliant with LDAP v3 standards, ensuring compatibility with many systems.
  • Integration-Friendly: Works seamlessly with Oracle software (e.g., Oracle Fusion Middleware, Oracle E-Business Suite) and third-party tools like Active Directory.
  • Handles Large Data Volumes: Manages millions of records without compromising speed or performance.
  • Secure and Reliable: Offers encryption, access controls, and high availability with replication and clustering.

How It Works

  • Directory Information Tree (DIT): Organizes data like a family tree, making it easy to locate users or systems.
  • Oracle Directory Server: Processes user requests, such as logins or data updates.
  • Synchronization: Oracle Directory Integration Platform (ODIP) ensures data is always up-to-date across systems.
  • Single Sign-On (SSO): Simplifies logins by letting users access multiple systems with one set of credentials.
  • Streamlined Identity Management: Centralizes user accounts and permissions, reducing administrative burden.
  • Enhanced Security: Protects sensitive information with strict controls and encrypted connections.
  • Enterprise Integration: Allows smooth interaction with both Oracle and non-Oracle tools.

 

Summary

Oracle Internet Directory is a powerful, secure, and efficient solution for businesses that need to manage large amounts of user and system data. It’s particularly beneficial for companies using Oracle products, helping them streamline operations, boost security, and ensure smooth system performance.

INTRODUCTION Oracle Directory Integration Platform(ODIP)

 

What is ODIP?

ODIP is a component of Oracle Internet Directory (OID) that ensures smooth data synchronization between OID and other directories, databases, or applications. It helps keep user information consistent and up-to-date across different systems.

Key Features

  • Data Synchronization: Automatically syncs data like user profiles, passwords, and group memberships between systems.
  • Two-Way Integration: Supports both import (pulling data into OID) and export (pushing data from OID to other systems).
  • Support for Multiple Directories: Works with other directories, such as Microsoft Active Directory or Sun Directory.
  • Flexible Configuration: Allows customization of synchronization rules based on organizational needs.

How ODIP Works

  • Connectors: Prebuilt or custom connectors link OID to other directories or databases.
  • Synchronization Profiles: Define rules for what data should be synced, how often, and in which direction.
  • Real-Time Updates: Ensures changes made in one system are reflected instantly or on schedule in others.

Use Cases

  • User Onboarding/Offboarding: Automatically propagates changes in user accounts to all connected systems.
  • Password Sync: Keeps passwords synchronized across multiple directories for seamless login.
  • Hybrid Environments: Bridges on-premise and cloud systems, ensuring data consistency.

Summary

Oracle Directory Integration Platform (ODIP) is essential for organizations that need to synchronize identity data across multiple systems, ensuring data consistency, automation, and streamlined identity management. It complements OID by connecting it with the broader IT ecosystem.

Benefits of OID and ODIP Together:

  • Centralized Management: OID acts as a single source of truth for user and system data.
  • Data Consistency: ODIP keeps all connected systems synchronized.
  • Enhanced Security: Unified control over access and data policies.
  • Automation: Reduces manual effort in managing user data.
  • Seamless Integration: Bridges diverse systems for smooth operations.

Summary:

OID simplifies identity management by centralizing data, while ODIP ensures data consistency across systems. Together, they enable secure, efficient, and automated identity and directory management for modern enterprises.

 

Prerequisites and Environment Setup

Before diving into the installation process, ensure that your environment meets the necessary prerequisites.

Environment Resources

Below is a summary of the resources used in this setup:

Hardware Resources
Component Details
Virtualization VirtualBox
RAM 10 GB
Hard Drive 100 GB
CPU 4 vCPU

 

Software Resources
Component Version/Details
Operating System Oracle Enterprise Linux 8.10
Oracle Database Oracle Database 19c
Fusion Middleware (FMW) 12.2.1.4
Oracle Internet Directory 12.2.1.4

 

Action Plan for The Installation:

The installation process will be divided into the following parts, as illustrated below. Each part will be thoroughly explored and discussed in detail as presented below.

Step 1: Install Oracle Database 19c

Oracle Internet Directory requires a backend database to store its metadata. Oracle Database 19c is a recommended choice.

Key Steps:

  • Download and install the Oracle Database software.
  • Create a database instance to host the OID schema.
  • Ensure the database is running before proceeding to subsequent steps.

For detailed instructions, refer to Oracle Database 19c Installation for OID.

 

Step 2: Install Fusion Middleware 12.2.1.4

Oracle Fusion Middleware is required for the OID installation.

Key Steps:

  • Download the Fusion Middleware Infrastructure 12.2.1.4 installer.
  • Use the Oracle Universal Installer (OUI) to install the software.
  • Validate the installation with the rcu utility.

For details, visit FMW 12.2.1.4 Installation for Oracle Internet Directory(OID).

 

Step 3: Install Oracle Internet Directory

Once Fusion Middleware is installed, the next step is to install OID.

Key Steps:

  • Use the Oracle Universal Installer to install the OID binaries.
  • Ensure the proper directory structure is created.

Refer to Oracle Internet Directory 12.2.1.4 Installation for detailed steps.

 

Step 4: Configure WebLogic Domain for OID

The Oracle WebLogic Server domain is a crucial component that manages OID services.

Key Steps:

  • Create a new WebLogic domain for OID.
  • Configure the domain using the WebLogic Configuration Wizard.
  • Start the WebLogic Admin Server.

Detailed instructions are available in Configure Weblogic Domain for OID 12.2.1.4.

 

Step 5: Configure Oracle Internet Directory

The final step is to configure and initialize OID.

Key Steps:

  • Test and verify the configuration using OID tools.
  • Integrate with external applications as required.

Follow Configure Oracle Internet Directory(OID) 12.2.1.4 for the full guide.

 

Final Verification and Testing

After completing the above steps, perform the following checks to ensure the installation and configuration are successful:

  1. Verify that all services (OID and WebLogic) are up and running.
  2. Use ldapbind and ldapsearch commands to test the OID service.
  3. Check the WebLogic Admin Console for server health.

Conclusion

Installing and configuring Oracle Internet Directory 12.2.1.4 involves multiple interconnected steps. Following this comprehensive guide can streamline the process and ensure a successful deployment. For additional details on each task, refer to the linked individual posts.

 

 

If you encounter any issues or have further questions, feel free to contact on Below: Linkedin 🔗  SyedSaadAli

 

 

 
December 16, 2024 Step By Step Upgrading Oracle EBS to R12.2.14
APPS DBA

Step By Step Upgrading Oracle EBS to R12.2.14

This post will offer comprehensive guidance on upgrading Oracle EBS Release R12.2.x to R12.2.14. 

Step 1: Upgrade Oracle Database
This Part covers the upgrade process of Oracle Apps R12.2.x Database from 12c to 19c, followed by a verification process to ensure a successful upgrade. if you are currently on that database version or earlier, you should now upgrade to Oracle Database 19c before proceeding with next steps. To upgrade your database, follow the process documented in Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c, My Oracle Support Knowledge Document 2552181.1  Use the Following Links below if you want to Upgrade the Database to 19c Important Notes on Upgrading to Oracle Database 19c:

  • As part of upgrading your Oracle E-Business Suite to Oracle Database 19c, your database will undergo a conversion to a multitenant architecture. This means it will consist of a Container Database (CDB) with a single Pluggable Database. Please note that only multitenant architecture databases are supported for Oracle E-Business Suite when using Oracle Database 19c.
  • During the upgrade process, you will also need to migrate directories that are defined for PL/SQL File I/O to database directory objects. This requirement arises from the de support of the UTL_FILE_DIR database initialization parameter in Oracle Database 19c.
  • Oracle Database Release Update 19.3, as well as Release Updates 19.5 and later, have been certified for compatibility.
  • If the products you have implemented do not support 19c, it is advised not to proceed with the database upgrade.

 

Database Upgrade Part 1 Link:   Oracle EBS Database Upgrade from 12c to 19c Part-1

Database Upgrade Part 2 Link:  Oracle EBS Database Upgrade from 12c to 19c Part-2

 

Step 2: Apply Latest AD and TXK Delta Release Update Packs
A) (ETCC) EBS Technology Codelevel Checker Use the Below given link to Download the latest ETCC Patch and Identifying and applying the required Database and Middleware Technology Patches Link    Apply ETCC(OCT-2024) Patches   B) Oracle Official Document for AD-TXK  Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)  Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2, and follow the instructions to apply the required codelevel of AD and TXK for your system. The Oracle E-Business Suite Applications DBA and Technology Stack release update packs R12.AD.C.Delta.16 and R12.TXK.C.Delta.16 include a set of structural changes that modernize the EBS database architecture, including a schema named EBS_SYSTEM.   C) Link to Apply AD-TXK Link Apply AD TXK 16

 

Step 3 Apply Oracle E-Business Suite 12.2.14 Release Update Pack

Having applied the latest available AD and TXK RUPs and having also performed the necessary pre-update steps mentioned in the above sections, you can now proceed withapplying the Oracle E-Business Suite 12.2.14 Release Update Pack

a)  Source the run edition applications environment.
[oracle@ebs12214 ~]$ . ./EBSapps.env E-Business Suite Environment Information —————————————- RUN File System : /u01/oracle/PROD/fs2/EBSapps/appl PATCH File System : /u01/oracle/PROD/fs1/EBSapps/appl Non-Editioned File System : /u01/oracle/PROD/fs_ne DB Host: ebs12214.com Service/SID: PROD E-Business Suite Environment Setting ———————————— – Enter [R/r] for sourcing Run File System Environment file, or – Enter [P/p] for sourcing Patch File System Environment file, or – Enter anything else to exit Please choose the environment file you wish to source [R/P]:R Sourcing the RUN File System …

b) Unzip and Staging the Patch 36026788

[oracle@ebs12214 ~]$ cd /u01/Patches/12214_upgrade [oracle@ebs12214 12214_upgrade]$ unzip -o ‘*.zip’ [oracle@ebs12214 12214_upgrade]$ cp -pr 36026788 $PATCH_TOP

c) Start an Online Patching Cycle
[oracle@ebs12214 ~]$ adop phase=prepare Enter the APPS password: Enter the EBS_SYSTEM password: Enter the WLSADMIN password: Validating credentials. Warning: WebLogic Admin Server is not running. Trying to start Admin Server. You are running adadminsrvctl.sh version 120.10.12020000.11 Starting WLS Admin Server… Refer /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/logs/appl/admin/log/adadminsrvctl.txt for details AdminServer logs are located at /u01/oracle/PROD/fs2/FMW_Home/user_projects/domains/EBS_domain/servers/AdminServer/logs adadminsrvctl.sh: exiting with status 0 adadminsrvctl.sh: check the logfile /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/logs/appl/admin/log/adadminsrvctl.txt for more information … Initializing. Run Edition context : /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch edition context: /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch file system free space: 149.84 GB Validating system setup. Node registry is valid. Checking for existing adop sessions. No pending session exists. Starting new adop session. =========================================================================== ADOP (C.Delta.16) Session ID: 15 Node: ebs12214 Phase: prepare Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241209_200033/adop.log =========================================================================== Validating configuration on node: [ebs12214]. Verifying data dictionary. Validating system is ready to prepare. Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241209_200033/prepare/ebs12214 Detecting configuration changes. Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241209_200033/prepare/ebs12214/adConfigChanges.log The log file is /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241209_200033/prepare/ebs12214/adConfigChanges.log Configuration change detected. File system configuration changes were detected. Checking AD-TXK codelevel. AD-TXK codelevel has not changed. Checking for pending cleanup actions. Running cleanup as it was not run in previous patching cycle. Processing cleanup actions in parallel. Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241209_200033/prepare/ebs12214/log/cleanup.log Generating report of queued DDL actions. Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241209_200033/prepare/ebs12214/adzdallddls.out Running cleanup in STANDARD mode. Log: @ADZDSHOWLOG.sql “2024/12/09 20:06:39” [ERROR] [CLEANUP 1:1 ddl_id=26909] ORA-01432: public synonym to be dropped does not exist SQL: drop public synonym WF_ALL_JOBS force Validating database is ready to prepare. Starting Apps listener. adalnctl.sh version 120.3.12020000.4 Checking for FNDFS executable. Starting listener process APPS_PROD. adalnctl.sh: exiting with status 0 adalnctl.sh: check the logfile /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/logs/appl/admin/log/adalnctl.txt for more information … Submitting ADZDPATCH concurrent program. Saving database logs from previous session. Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241209_200033/prepare/ebs12214/adzdshowlog_cleanup.out Creating database patch edition. Log: @ADZDSHOWLOG.sql “2024/12/09 20:06:47” preparing the seed tables needed for autoconfig execution. Synchronizing patch filesystem with run filesystem. Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241209_200033/prepare/ebs12214 Stopping node manager. You are running adnodemgrctl.sh version 120.11.12020000.12The Node Manager is already shutdown NodeManager log is located at /u01/oracle/PROD/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1 adnodemgrctl.sh: exiting with status 2 The prepare phase completed successfully. adop exiting with status = 0 (Success)

 

d)  Apply Oracle E-Business Suite Release 12.2.14 Patch 36026788.
[oracle@ebs12214 ~]$ adop phase=apply patches=36026788 wait_on_failed_job=yes workers=4 flags=autoskip Enter the APPS password: Enter the EBS_SYSTEM password: Enter the WLSADMIN password: Validating credentials. Initializing. Run Edition context : /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch edition context: /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch file system free space: 129.40 GB Validating system setup. Patch file system free space: 129.40 GB Validating system setup. Node registry is valid. Checking for existing adop sessions. Continuing with existing session [Session ID: 15]. =========================================================================== ADOP (C.Delta.16) Session ID: 15 Node: ebs12214 Phase: apply Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241209_205240/adop.log =========================================================================== Applying patch 36026788. Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241209_205240/apply/ebs12214/36026788/log/u36026788.log [WARNING] Some patching actions failed and were skipped [WARNING] Refer to the autoskip logfile for the list of skipped jobs [WARNING] Logfile: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241209_205240/apply/ebs12214/36026788/log/autoskip.log Generating post apply reports. Generating log report. Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241209_205240/apply/ebs12214/adzdshowlog.out The apply phase completed successfully. adop exiting with status = 0 (Success)

e) Complete the Patching Cycle (Finalize, Cutover, FSclone)

i) Run Finalize

[oracle@ebs12214 ~]$ adop phase=finalize Enter the APPS password: Enter the EBS_SYSTEM password: Enter the WLSADMIN password: Validating credentials. Initializing. Run Edition context : /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch edition context: /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch file system free space: 120.50 GB Validating system setup. Node registry is valid. Checking for existing adop sessions. Continuing with existing session [Session ID: 15]. Session Id : 15 Prepare phase status : COMPLETED Apply phase status : ATLEAST ONE PATCH IS ALREADY APPLIED Cutover phase status : NOT COMPLETED Abort phase status : NOT COMPLETED Session status : FAILED =========================================================================== ADOP (C.Delta.16) Session ID: 15 Node: ebs12214 Phase: finalize Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241210_033617/adop.log =========================================================================== Verifying data dictionary. Running finalize phase database actions. Log: @ADZDSHOWLOG.sql “2024/12/10 03:36:57” Generating log report. Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241210_033617/finalize/ebs12214/adzdshowlog.out The finalize phase completed successfully. adop exiting with status = 0 (Success) [oracle@ebs12214 ~]$

ii) Run Cutover

[oracle@ebs12214 ~]$ adop phase=cutover Enter the APPS password: Enter the EBS_SYSTEM password: Enter the WLSADMIN password: Validating credentials. Initializing. Run Edition context : /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch edition context: /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch file system free space: 120.47 GB Validating system setup. Node registry is valid. Checking for existing adop sessions. Continuing with existing session [Session ID: 15]. =========================================================================== ADOP (C.Delta.16) Session ID: 15 Node: ebs12214 Phase: cutover Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241210_034304/adop.log =========================================================================== Validating configuration on node: [ebs12214]. Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241210_034304/cutover/validate/ebs12214 Checking if finalize required. Finalize phase is not required Submitting request for Internal Concurrent Manager shutdown. You are running adcmctl.sh version 120.19.12020000.7 Shutting down concurrent managers for PROD … ORACLE Password: Submitted request 512325 for CONCURRENT FND SHUTDOWN adcmctl.sh: exiting with status 0 ============================== ************************* ============================================= Calling /u01/oracle/PROD/fs1/EBSapps/comn/util/jdk32/jre/bin/java … Flipping snapshots in run and patch editions. Performing file system cutover. Checking if file system cutover completed. Starting run edition Admin Server. Starting application tier services. Waiting for middle tier services to start on all available nodes. Generating post-cutover reports. Generating log report. Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241210_034304/cutover/ebs12214/adzdshowlog.out The cutover phase completed successfully. adop exiting with status = 0 (Success)

iii) Open New Terminal And Source Environment
[oracle@ebs12214 ~]$ . ./EBSapps.env run E-Business Suite Environment Information —————————————- RUN File System : /u01/oracle/PROD/fs1/EBSapps/appl PATCH File System : /u01/oracle/PROD/fs2/EBSapps/appl Non-Editioned File System : /u01/oracle/PROD/fs_ne DB Host: ebs12214.com Service/SID: PROD Sourcing the RUN File System …

 

iv) Run FS Clone to Synchronized File System
[oracle@ebs12214 ~]$ adop phase=fs_clone Enter the APPS password: Enter the EBS_SYSTEM password: Enter the WLSADMIN password: Validating credentials. Warning: WebLogic Admin Server is not running. Trying to start Admin Server. You are running adadminsrvctl.sh version 120.10.12020000.11 Starting WLS Admin Server… Refer /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/logs/appl/admin/log/adadminsrvctl.txt for details AdminServer logs are located at /u01/oracle/PROD/fs1/FMW_Home/user_projects/domains/EBS_domain/servers/AdminServer/logs adadminsrvctl.sh: exiting with status 0 adadminsrvctl.sh: check the logfile /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/logs/appl/admin/log/adadminsrvctl.txt for more information … Initializing. Run Edition context : /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch edition context: /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch file system free space: 120.04 GB Validating system setup. Node registry is valid. Checking for existing adop sessions. No pending session exists. Starting new adop session. =========================================================================== ADOP (C.Delta.16) Session ID: 16 Node: ebs12214 Phase: fs_clone Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/16/20241210_140253/adop.log =========================================================================== ======================= ********************** ========================= Stopping node manager. You are running adnodemgrctl.sh version 120.11.12020000.12 The Node Manager is already shutdown NodeManager log is located at /u01/oracle/PROD/fs2/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1 adnodemgrctl.sh: exiting with status 2 adnodemgrctl.sh: check the logfile /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/logs/appl/admin/log/adnodemgrctl.txt for more information … Generating log report. Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/16/20241210_140253/fs_clone/ebs12214/adzdshowlog.out The fs_clone phase completed successfully. adop exiting with status = 0 (Success) [oracle@ebs12214 ~]$

 

   

Step 4 Post Upgrade Steps

i) Apply Oracle E-Business Suite Release 12.2.14 Online Help

Using adop hotpatch mode on the run file system, apply Oracle E-Business Suite Release 12.2.14 Online Help Patch 36026775.

Source Run Environment [oracle@ebs12214 ~]$ . ./EBSapps.env run   E-Business Suite Environment Information   —————————————-   RUN File System           : /u01/oracle/PROD/fs1/EBSapps/appl   PATCH File System         : /u01/oracle/PROD/fs2/EBSapps/appl   Non-Editioned File System : /u01/oracle/PROD/fs_ne DB Host: ebs12214.com  Service/SID: PROD   Sourcing the RUN File System … Unzip Downloaded Patch  [oracle@ebs12214 ~]$ cd /u01/Patches/12214_upgrade/ [oracle@ebs12214 12214_upgrade]$ unzip -qo p36026775_R12_GENERIC.zip [oracle@ebs12214 12214_upgrade]$ cp -pr  36026775/ $PATCH_TOP Apply Patch [oracle@ebs12214 ~]$ adop phase=apply patches=36026775 hotpatch=yes Enter the APPS password: Enter the EBS_SYSTEM password: Enter the WLSADMIN password: Validating credentials. Initializing.     Run Edition context  : /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml     Patch edition context: /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml     Patch file system free space: 119.93 GB Validating system setup.     Node registry is valid. Checking for existing adop sessions.     Application tier services are down.     No pending session exists.     Starting new adop session. =========================================================================== ADOP (C.Delta.16) Session ID: 17 Node: ebs12214 Phase: apply Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_170137/adop.log =========================================================================== Applying patch 36026775.     Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_170137/apply/ebs12214/36026775/log/u36026775.log Running finalize actions for the patches being applied.     Log: @ADZDSHOWLOG.sql “2024/12/10 17:32:36” Running cutover actions for the patches being applied.     Creating workers to process cutover DDL in parallel     Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_170137/apply/ebs12214/log/cutover.log     Loading JAR files into database.     Loading JAR files into database     No JAR files found to load     Performing database cutover in Quick mode Generating post apply reports. Generating log report.     Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_170137/apply/ebs12214/adzdshowlog.out The apply phase completed successfully. adop exiting with status = 0 (Success) [oracle@ebs12214 ~]$

ii) Apply Oracle Application Framework Patch

After you have installed the Oracle E-Business Suite 12.2.14 Release Update Pack, Oracle recommends that you apply the following critical patch as mentioned in Oracle E-Business Suite Release 12.2 Upgrade Considerations for OAF-based Applications and Oracle CRM Technology Foundation (Doc ID 1927975.1) OAF: Patch 36470037:R12.FWK.C Oracle Application Framework (FWK) Release Post-12.2.14 Consolidated Patch

Source Run Environment [oracle@ebs12214 ~]$ . ./EBSapps.env run E-Business Suite Environment Information —————————————- RUN File System : /u01/oracle/PROD/fs1/EBSapps/appl PATCH File System : /u01/oracle/PROD/fs2/EBSapps/appl Non-Editioned File System : /u01/oracle/PROD/fs_ne DB Host: ebs12214.com Service/SID: PROD Sourcing the RUN File System … Unzip Downloaded Patch  [oracle@ebs12214 ~]$ cd /u01/Patches/12214_upgrade/ [oracle@ebs12214 12214_upgrade]$ unzip -qo p36470037_R12.FWK.C_R12_GENERIC.zip [oracle@ebs12214 12214_upgrade]$ cp -pr 36470037/ $PATCH_TOP Apply Patch  [oracle@ebs12214 ~]$ adop phase=apply apply_mode=downtime patches=36470037 Enter the APPS password: Enter the EBS_SYSTEM password: Enter the WLSADMIN password: Validating credentials. Initializing. Run Edition context : /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch edition context: /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch file system free space: 119.59 GB Validating system setup. Node registry is valid. Checking for existing adop sessions. Application tier services are down. Continuing with the existing session [Session ID: 17]. =========================================================================== ADOP (C.Delta.16) Session ID: 17 Node: ebs12214 Phase: apply Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_175351/adop.log =========================================================================== Applying patch 36470037. Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_175351/apply/ebs12214/36470037/log/u36470037.log Running finalize actions for the patches being applied. Log: @ADZDSHOWLOG.sql “2024/12/10 17:55:11” Running cutover actions for the patches being applied. Creating workers to process cutover DDL in parallel Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_175351/apply/ebs12214/log/cutover.log Loading JAR files into database. Loading JAR files into database No JAR files found to load Performing database cutover in Quick mode Generating post apply reports. Generating log report. Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_175351/apply/ebs12214/adzdshowlog.out The apply phase completed successfully. adop exiting with status = 0 (Success) [oracle@ebs12214 ~]$

iii) Implement Java Runtime Environtment (Optional)

[edsanimate_start entry_animation_type= “pulse” entry_delay= “0.5” entry_duration= “0.5” entry_timing= “linear” exit_animation_type= “” exit_delay= “” exit_duration= “” exit_timing= “” animation_repeat= “1” keep= “yes” animate_on= “load” scroll_offset= “” custom_css_class= “”]Note: If you dont want to Enable JWS or is Already enabled, Skip this Section.[edsanimate_end]

What is Java Web Start?

  • Java Web Start (JWS) is a technology that allows for the deployment of Java-based applications to the client desktop, independent of the user’s browser.
  •  Users can launch a Java application by simply clicking a link on a web page, which leads to a Java Network Launch Protocol (JNLP) file.
  •  The JNLP file instructs the Java Web Start software to download, cache, and run the application, eliminating the need for additional installation procedures.
  •  Java Web Start is included as part of the Java Runtime Environment (JRE) software, so users don’t need to install it separately or perform any additional tasks.
  •  There is an architectural comparison between Java Plug-in and Java Web Start, which can be understood through the following diagrams showcasing the differences in the client (desktop) tier.

If you wish to enable JWS, you can refer to the provided document titled ‘Using Java Web Start with Oracle E-Business Suite (Doc ID 2188898.1)’.  However, please note that if your environment is on version 12.2.10 or below, the steps outlined in the document are applicable. In our specific case, as we have already upgraded our application to version 12.2.14, all the necessary patches to enable JWS have been included in the upgrade patch. Therefore, we only need to follow the subsequent process described in this section to enable JWS.

Update Context File to Enable JWS

Open the Application Context file in VI Editor as shown below As you Can see out forms launch method is set to browser, we need to change it to jws [oracle@ebs12214 ~]$ echo $CONTEXT_FILE /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml   [oracle@ebs12214 ~]$ grep s_forms_launch_method $CONTEXT_FILE          <config_option type=”techstack” oa_var=”s_forms_launch_method”>browser</config_option> [oracle@ebs12214 ~]$ vi $CONTEXT_FILE After Changing the Parameter of s_forms_launch_method Parameter to jws , Save and Close the Context File [oracle@ebs12214 ~]$ grep s_forms_launch_method $CONTEXT_FILE          <config_option type=”techstack” oa_var=”s_forms_launch_method”>jws</config_option>

Run Autoconfig on Application Tier

[oracle@ebs12214 ~]$ sh $ADMIN_SCRIPTS_HOME/adautocfg.sh

Regenerate JAR Files through ADADMIN Utility

[oracle@ebs12214 ~]$ adadmin

iv) Run ECPUC for Applying Critical Update Patches

For detail EBS Critical Patch Update Checker (ECPUC) application follow the Link below Step by Step Guide to apply EBS Latest CPU OCT-2024 through EBS Critical Patch Update Checker (ECPUC) Oracle E-Business Suite Release 12.2 Critical Patch Update Availability Document (October 2024) (Doc ID 3037725.1)

Source Run Environment

[oracle@ebs12214 ~]$ . ./EBSapps.env run E-Business Suite Environment Information —————————————- RUN File System : /u01/oracle/PROD/fs1/EBSapps/appl PATCH File System : /u01/oracle/PROD/fs2/EBSapps/appl Non-Editioned File System : /u01/oracle/PROD/fs_ne DB Host: ebs12214.com Service/SID: PROD Sourcing the RUN File System … Run ecpuc.sql [oracle@ebs12214 ~]$ cd ecpuc/ [oracle@ebs12214 ecpuc]$ sqlplus apps/apps SQL*Plus: Release 10.1.0.5.0 – Production on Tue Dec 10 17:04:43 2024 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production SQL> @ECPUC.sql Start Time: 10-12-2024 17:04:47 **************************************************************************** E-Business Suite Critical Patch Update Checker (ECPUC) ECPUC.sql may be run on any EBS 12.2 environment to identify missing patches that are in the latest EBS CPU. You can download the latest version of ECPUC via Patch 35583866. Refer to the README.txt in Patch 35583866 for instructions for running ECPUC and information regarding the generated ECPUC.lst report. The checker generates the report ECPUC_YYYY-MM-DD_HH24-MI.lst that lists recommended EBS CPU patches and security fixes for your environment per Table 1 ‘CPU Patches for Oracle E-Business Suite’ and Table 2 ‘Additional Patches Required’ documented in the quarterly EBS CPU MOS Note. Each quarterly EBS CPU MOS Note ID is unique. Refer to My Oracle Support (MOS) Knowledge Document 2484000.1, ‘Identifying the Latest Critical Patch Update for Oracle E-Business Suite Release 12′ which includes a link to the current EBS CPU MOS document. ****************************************************************************

Applying Patch 1 of ECPUC Result 37078895

Source Run Environment

[oracle@ebs12214 ~]$ . ./EBSapps.env run E-Business Suite Environment Information —————————————- RUN File System : /u01/oracle/PROD/fs1/EBSapps/appl PATCH File System : /u01/oracle/PROD/fs2/EBSapps/appl Non-Editioned File System : /u01/oracle/PROD/fs_ne DB Host: ebs12214.com Service/SID: PROD Sourcing the RUN File System …

Unzip Patch

[oracle@ebs12214 ~]$ cd /u01/Patches/12214_upgrade/ [oracle@ebs12214 12214_upgrade]$ unzip -qo p37078895_R12.ATG_PF.C_R12_GENERIC.zip [oracle@ebs12214 12214_upgrade]$ cp -pr 37078895/ $PATCH_TOP

Apply Patch

[oracle@ebs12214 ~]$ adop phase=apply apply_mode=downtime patches=37078895 Enter the APPS password: Enter the EBS_SYSTEM password: Enter the WLSADMIN password: Validating credentials. Initializing. Run Edition context : /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch edition context: /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch file system free space: 119.58 GB Validating system setup. Node registry is valid. Checking for existing adop sessions. Application tier services are down. Continuing with the existing session [Session ID: 17]. =========================================================================== ADOP (C.Delta.16) Session ID: 17 Node: ebs12214 Phase: apply Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_180435/adop.log =========================================================================== Applying patch 37078895. Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_180435/apply/ebs12214/37078895/log/u37078895.log Running finalize actions for the patches being applied. Log: @ADZDSHOWLOG.sql “2024/12/10 18:05:56” Running cutover actions for the patches being applied. Creating workers to process cutover DDL in parallel Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_180435/apply/ebs12214/log/cutover.log Loading JAR files into database. Loading JAR files into database No JAR files found to load Performing database cutover in Quick mode Generating post apply reports. Generating log report. Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_180435/apply/ebs12214/adzdshowlog.out The apply phase completed successfully. adop exiting with status = 0 (Success) [oracle@ebs12214 ~]$

Applying Patch 2 of ECPUC Result 37068559

Source Run Environment

[oracle@ebs12214 ~]$ . ./EBSapps.env run E-Business Suite Environment Information —————————————- RUN File System : /u01/oracle/PROD/fs1/EBSapps/appl PATCH File System : /u01/oracle/PROD/fs2/EBSapps/appl Non-Editioned File System : /u01/oracle/PROD/fs_ne DB Host: ebs12214.com Service/SID: PROD Sourcing the RUN File System …

Unzip Patch

[oracle@ebs12214 ~]$ cd /u01/Patches/12214_upgrade/ [oracle@ebs12214 12214_upgrade]$ unzip -qo p37068559_R12.GMD.C_R12_GENERIC.zip [oracle@ebs12214 12214_upgrade]$ cp -pr 37068559/ $PATCH_TOP

Apply Patch

[oracle@ebs12214 ~]$ adop phase=apply apply_mode=downtime patches=37068559 Enter the APPS password: Enter the EBS_SYSTEM password: Enter the WLSADMIN password: Validating credentials. Initializing. Run Edition context : /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch edition context: /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch file system free space: 119.58 GB Validating system setup. Node registry is valid. Checking for existing adop sessions. Application tier services are down. Continuing with the existing session [Session ID: 17]. =========================================================================== ADOP (C.Delta.16) Session ID: 17 Node: ebs12214 Phase: apply Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_181022/adop.log =========================================================================== Applying patch 37068559. Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_181022/apply/ebs12214/37068559/log/u37068559.log Running finalize actions for the patches being applied. Log: @ADZDSHOWLOG.sql “2024/12/10 18:12:20” Running cutover actions for the patches being applied. Creating workers to process cutover DDL in parallel Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_181022/apply/ebs12214/log/cutover.log Loading JAR files into database. Loading JAR files into database No JAR files found to load Performing database cutover in Quick mode Generating post apply reports. Generating log report. Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_181022/apply/ebs12214/adzdshowlog.out The apply phase completed successfully. adop exiting with status = 0 (Success) [oracle@ebs12214 ~]$

v) Run ECPUC Again after Applying Critical Update Patches

Source Run Environment

[oracle@ebs12214 ~]$ . ./EBSapps.env run E-Business Suite Environment Information —————————————- RUN File System : /u01/oracle/PROD/fs1/EBSapps/appl PATCH File System : /u01/oracle/PROD/fs2/EBSapps/appl Non-Editioned File System : /u01/oracle/PROD/fs_ne DB Host: ebs12214.com Service/SID: PROD Sourcing the RUN File System … Run ecpuc.sql [oracle@ebs12214 ~]$ cd ecpuc/ [oracle@ebs12214 ecpuc]$ sqlplus apps/apps SQL*Plus: Release 10.1.0.5.0 – Production on Tue Dec 10 17:04:43 2024 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production SQL> @ECPUC.sql Start Time: 10-12-2024 17:04:47 **************************************************************************** E-Business Suite Critical Patch Update Checker (ECPUC) ECPUC.sql may be run on any EBS 12.2 environment to identify missing patches that are in the latest EBS CPU. You can download the latest version of ECPUC via Patch 35583866. Refer to the README.txt in Patch 35583866 for instructions for running ECPUC and information regarding the generated ECPUC.lst report. The checker generates the report ECPUC_YYYY-MM-DD_HH24-MI.lst that lists recommended EBS CPU patches and security fixes for your environment per Table 1 ‘CPU Patches for Oracle E-Business Suite’ and Table 2 ‘Additional Patches Required’ documented in the quarterly EBS CPU MOS Note. Each quarterly EBS CPU MOS Note ID is unique. Refer to My Oracle Support (MOS) Knowledge Document 2484000.1, ‘Identifying the Latest Critical Patch Update for Oracle E-Business Suite Release 12′ which includes a link to the current EBS CPU MOS document. ****************************************************************************

 vi) Run FS Clone to Synchronized File System

[oracle@ebs12214 ~]$ adop phase=fs_clone Enter the APPS password: Enter the EBS_SYSTEM password: Enter the WLSADMIN password: Validating credentials. Initializing. Run Edition context : /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch edition context: /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch file system free space: 119.57 GB Validating system setup. Node registry is valid. Checking for existing adop sessions. No pending session exists. Starting new adop session. =========================================================================== ADOP (C.Delta.16) Session ID: 18 Node: ebs12214 Phase: fs_clone Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/18/20241210_192155/adop.log =========================================================================== Validating configuration on node: [ebs12214]. =========================== ******************************* =================================== Blocking managed server ports. Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/18/20241210_192155/fs_clone/ebs12214/txkCloneAcquirePort.log Performing CLONE steps. Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/18/20241210_192155/fs_clone/ebs12214 Beginning application tier FSCloneStage – Tue Dec 10 19:26:27 2024 Target System Instance Top set to /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214 Report file located at /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/temp/portpool.lst The new APPL_TOP context file has been created : /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml contextfile=/u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Completed FSCloneApply… Tue Dec 10 20:35:49 2024 Resetting FARM name… runDomainName: EBS_domain patchDomainName: EBS_domain targets_xml_loc: /u01/oracle/PROD/fs2/FMW_Home/user_projects/domains/EBS_domain/sysman/state/targets.xml Patch domain is not updated, no need to reset FARM name. Releasing managed server ports. Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/18/20241210_192155/fs_clone/ebs12214/txkCloneAcquirePort.log Synchronizing snapshots. Stopping services on patch file system. Stopping admin server. You are running adadminsrvctl.sh version 120.10.12020000.11 Stopping WLS Admin Server… Refer /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/logs/appl/admin/log/adadminsrvctl.txt for details AdminServer logs are located at /u01/oracle/PROD/fs2/FMW_Home/user_projects/domains/EBS_domain/servers/AdminServer/logs adadminsrvctl.sh: exiting with status 0 Stopping node manager. You are running adnodemgrctl.sh version 120.11.12020000.12 The Node Manager is already shutdown NodeManager log is located at /u01/oracle/PROD/fs2/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1 adnodemgrctl.sh: exiting with status 2 adnodemgrctl.sh: check the logfile /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/logs/appl/admin/log/adnodemgrctl.txt for more information … Generating log report. Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/18/20241210_192155/fs_clone/ebs12214/adzdshowlog.out The fs_clone phase completed successfully. adop exiting with status = 0 (Success) [oracle@ebs12214 ~]$

 

Step 5 Starting and Verifying Application 12.2.14

Start Application Services
Source Run Environment [oracle@ebs12214 ~]$ . ./EBSapps.env run E-Business Suite Environment Information —————————————- RUN File System : /u01/oracle/PROD/fs1/EBSapps/appl PATCH File System : /u01/oracle/PROD/fs2/EBSapps/appl Non-Editioned File System : /u01/oracle/PROD/fs_ne DB Host: ebs12214.com Service/SID: PROD Sourcing the RUN File System … Start Application Services [oracle@ebs12214 ~]$ cd $ADMIN_SCRIPTS_HOME [oracle@ebs12214 scripts]$ ./adstrtal.sh apps/apps You are running adstrtal.sh version 120.24.12020000.11 Enter the WebLogic Server password: The logfile for this session is located at /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/logs/appl/admin/log/adstrtal.log Executing service control script: **************************************************** All enabled services for this node are started. adstrtal.sh: Exiting with status 0 adstrtal.sh: check the logfile /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/logs/appl/admin/log/adstrtal.log for more information …

 

Verifying Application

Login Console

  • Expand System Administrator Responsibility.

  •  Click Define Profile Options to Open Forms Interface.

You can See and Verify the Following Application and Database Version

Application Version: 12.2.14
December 14, 2024 Configure Oracle Internet Directory(OID) 12.2.1.4
Oracle Internet Directory

Configure Oracle Internet Directory(OID) 12.2.1.4

 

Note: Before proceeding with this installation section, ensure you have completed the prerequisite tasks outlined below. Refer to the provided links for detailed guidance.

 

Step 1: Install and Configure Oracle Database for Oracle Internet Directory Please refer to the following blog for detailed guidance.

Link 🔗  Oracle Database 19c Installation for OID

 

 

Step 2: Install Oracle Fusion Middleware 12c Detailed instructions can be found in the following blog.

Link 🔗FMW 12.2.1.4 Installation for Oracle Internet Directory(OID)

 

Step 3: Install Oracle Internet Directory 12.2.1.4 Detailed instructions can be found in the following blog.

Link 🔗Configure Weblogic Domain for OID 12.2.1.4

 

 

Step 4:Configure Oracle Internet Directory(OID) 12.2.1.4 Detailed instructions are in the following blog.

Link 🔗Configure OID 12.2.1.4

 

 

Starting the Environment For OID Configuration

Connect with the OID Operating System User to check the Profile Option set for the OID Environment.

[oidmgr@oidserver ~]$ cat .bash_profile

# .bash_profile

# Get the aliases and functions if [ -f ~/.bashrc ];

then . ~/.bashrc fi

# User specific environment and startup programs

export MW_HOME=/u02/app/oracle/Middleware/Oracle_Home

export ORACLE_COMMON_HOME=$MW_HOME/oracle_common

export ORACLE_HOME=$MW_HOME/oid

export WL_HOME=$MW_HOME/wlserver

export JAVA_HOME=/u02/jdk1.8.0_361/

export DOMAIN_HOME=$MW_HOME/user_projects/domains/base_domain

 

Next we will untar the JDK

[oidmgr@oidserver u02]$ tar -xvzf jdk-8u361-linux-x64.tar.gz

[oidmgr@oidserver ~]$ cd /u02/jdk1.8.0_361/bin

1. Start the Administration Server and Node Manager

[oidmgr@oidserver ~]$ . ./oid_env.env [oidmgr@oidserver ~]$ cd $DOMAIN_HOME/bin

[oidmgr@oidserver bin]$ nohup ./startWebLogic.sh & [1] 6503

Check the nohup.out to check and make sure the Admin Server Process in Running Mode

[oidmgr@oidserver bin]$ tail -20 nohup.out

[oidmgr@oidserver ~]$ cd $DOMAIN_HOME/bin

[oidmgr@oidserver bin]$ nohup ./startNodeManager.sh &

[2] 7630

Check the nohup.out to check and make sure the Node Manager Process in Running Mode

[oidmgr@oidserver bin]$ tail -20 nohup.out

2. Initial Oracle Internet Directory(OID) Setup

Connect with Weblogic Scripting Tool for initial setup up of OID Instance

[oidmgr@oidserver bin]$ cd $ORACLE_HOME/oracle_common/common/bin

[oidmgr@oidserver bin]$ ./wlst.sh

WARNING: This is a deprecated script. Please invoke the wlst.sh script under oracle_common/common/bin. Initializing WebLogic Scripting Tool (WLST) … Welcome to WebLogic Server Administration Scripting Shell Type help() for help on available commands

wls:/offline> connect (‘weblogic’,’oracle123′,’t3://oidserver.com:7001′)

wls:/base_domain/serverConfig/> oid_setup(orcladminPassword=’oracle123′, odsPassword=’oracle123′, realmDN=’dc=us,dc=oracle,dc=com’)

This will start the oid instance automatically

3. Starting Managed Server (wls_ods1)

[oidmgr@oidserver bin]$ cd $DOMAIN_HOME/bin

[oidmgr@oidserver bin]$ ./startManagedWebLogic.sh wls_ods1

When prompted for username/password to Boot Weblogic
Wait for the process of Managed Server being started and status shows RUNNING

4. Access Weblogic Console

Login the Weblogic Console to check the Status

http://oidserver.com:7001/console/login/LoginForm.jsp

 
Check the Server Status As you can see our wls_ods1 Manage Server is running.

5. Access Oracle Directory Service Manager(ODSM) Console
Open the ODSM Console For Creating Login Connection http://oidserver.com:7001/odsm/faces/odsm.jspx
Click Connect to a directory Now Click Create a New Connection

Fill the Connection information as Below

•Directory Type: OID

•Name: oid1 (We can give any name )

•Server: oidserver.com

•Port : 3060

•Username: cn=orcladmin

•Password: Oracle_123
Logged in  Page of ODSM

6. Access Enterprise Manager(EM) Console

Access WebLogic Server EM Console

http://oidserver.com:7001/em

 
Note:We Faced issue while logging into EM Console, it was continuously trying to reload the page and in the end, it ends up with Error.jsp Download the Following 2 Patches and Copy the downloaded patches on /home/oidmgr/* directory and Unzip Patch Patch 33903365 Patch 30613425

Environment should be down for apply this patch

Unzip the Download Patches [oidmgr@oidserver ~]$ cd /home/oidmgr/30613424/ [oidmgr@oidserver 30613424]$ unzip p30613424_122140_Generic.zip [oidmgr@oidserver ~]$ cd /home/oidmgr/33903365/ [oidmgr@oidserver 33903365]$ unzip p33903365_122140_Generic.zip Set the Environment for Patching [oidmgr@oidserver ~]$ export ORACLE_HOME=/u02/app/oracle/Middleware/Oracle_Home [oidmgr@oidserver ~]$ export PATH=$ORACLE_HOME/OPatch:$PATH [oidmgr@oidserver ~]$ opatch version OPatch Version: 13.9.4.2.1 OPatch succeeded. Validate the OUI inventory with the following commands: [oidmgr@oidserver ~]$ opatch lsinventory -jre $ORACLE_HOME/oracle_common/jdk/jre Applying Patch 30613424 [oidmgr@oidserver ~]$ cd 30613424/30613424 [oidmgr@oidserver 30613424]$ opatch apply Applying Patch 33903365 [oidmgr@oidserver 30613424]$ cd /home/oidmgr/33903365/33903365 [oidmgr@oidserver 33903365]$ opatch apply

Now Again Try to Login EM Console

Access WebLogic Server EM Console as http://oidserver.com:7001/em
After login Click the Highlighted Icon to Expand Target Navigation  
You can see Adminserver and Manage_Server(wls_ods1)

 

CONFIGURING Directory Integration Platform(DIP) 12.2.1.4 FOR OID

Adding Cipher Suites Configured for Oracle Internet Directory into ODIP

[oidmgr@oidserver ~]$ . ./oid_env.env [oidmgr@oidserver ~]$ cd $JAVA_HOME/jre/lib/security [oidmgr@oidserver security]$ vi java.security

Change the following given below in java.security From:

jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL

TO:

jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, NULL
From the Target Navigation pane in EM, expand the domain. From the domain home page, select the Managed Server (wls_ods1).
From the WebLogic Server menu, choose System MBean Browser.

Expand Configuration MBeans in the MBean navigation tree and then select bea > Server.

Expand the Server node and then expand the Managed Server node (wls_ods1).

From the Managed Server node, expand SSL and then select the Managed Server MBEAN.

The Configuration MBEAN page is displayed. Select Attributes tab and then select CipherSuites
 Click on Lock & Edit screen before doing the changes
Attribute: Ciphersuites page is displayed. Click Add and then add the ciphers

TLS_DH_anon_WITH_AES_128_GCM_SHA256 TLS_DH_anon_WITH_3DES_EDE_CBC_SHA SSL_DH_anon_WITH_3DES_EDE_CBC_SHA

Click Apply.

Click Activate Changes in the Change Center

Security Features in Oracle Directory Integration Platform

Documentation: Security Features in DIP

 

 

Configuring Oracle Directory Integration Platform for Oracle Internet Directory SSL No Authentication Mode
  1. Ensure that the Oracle WebLogic Administration Server and Oracle Directory Integration Platform managed server is running.
  2. Run the manageDIPServerConfig utility to update the Oracle Directory Integration Platform SSL configuration to use the Oracle Internet Directory SSL No Authentication Mode

Note: Make sure before executing manageDIPServerConfig Utility you update your WL_HOME  Location [oidmgr@oidserver ~]$ . ./oid_env.env

[oidmgr@oidserver ~]$ cd $ORACLE_HOME/bin

[oidmgr@oidserver bin]$ $ORACLE_HOME/bin/manageDIPServerConfig set -attribute sslmode -val 1 -h oidserver.com -p 7005 -D “weblogic”

[Weblogic user password] Connection parameters initialized. Connecting at oidserver.com:7005, with userid “weblogic”.. Connected successfully.

The attribute sslmode is successfully changed to value 1.

[oidmgr@oidserver bin]$

Configuring Oracle Directory Integration Platform for Oracle Internet Directory

Set the WL_HOME and ORACLE_HOME environment variables for Oracle Directory Integration Platform

Run the dipConfigurator setup (<ORACLE_HOME>/bin) command on the command line. Note: You must create a dbconfigfile named as db.properties file with mentioned parameters under $ORACLE_HOME/bin You must set the WL_HOME and ORACLE_HOME environment variables before executing the dipStatus and dipConfigurator commands [oidmgr@oidserver ~]$ . ./oid_env.env

[oidmgr@oidserver ~]$ cd $ORACLE_HOME

[oidmgr@oidserver Oracle_Home]$ cd bin

[oidmgr@oidserver bin]$ vi db.properties DRIVER_NAME:oracle.jdbc.OracleDriver DRIVER_TYPE:thin DB_HOST:oidserver.com DB_PORT:1521 DB_SID:OIDDB DB_SERVICENAME:OIDDB

Running dipConfigurator

[oidmgr@oidserver bin]$./dipConfigurator setup -wlshost oidserver.com -wlsport 7001 -wlsuser weblogic -ldaphost oidserver.com -ldapport 3131 -ldapuser “cn=orcladmin” -isldapssl true -dbconfigfile db.properties

Enter password to contact WebLogic Server:

Enter password to contact LDAP Server :

Enter password to connect OID DB :

DIP Configuration completed

 

/u02/app/oracle/Middleware/Oracle_Home/ldap/log/dipConfig.log

Verifying Oracle Directory Integration Platform
[oidmgr@oidserver bin]$ ./dipStatus -h oidserver.com -p 7005 -D weblogic [Weblogic user password] Connection parameters initialized. Connecting at oidserver.com:7005, with userid “weblogic”.. Connected successfully. ODIP Application is active at this host and port. [oidmgr@oidserver bin]$

 

 

 

If you encounter any issues or have further questions, feel free to contact on Below: Linkedin 🔗  SyedSaadAli

 
December 13, 2024 Configure Weblogic Domain for OID 12.2.1.4
Oracle Identity Management

Configure Weblogic Domain for OID 12.2.1.4

 

Note: Before proceeding with this installation section, ensure you have completed the prerequisite tasks outlined below. Refer to the provided links for detailed guidance.

 

Step 1: Install and Configure Oracle Database for Oracle Internet Directory Please refer to the following blog for detailed guidance.

Link 🔗  Oracle Database 19c Installation for OID

 

 

Step 2: Install Oracle Fusion Middleware 12c Detailed instructions can be found in the following blog.

Link 🔗FMW 12.2.1.4 Installation for Oracle Internet Directory(OID)

 

Step 3: Install Oracle Internet Directory 12.2.1.4 Detailed instructions can be found in the following blog.

Link 🔗Configure Weblogic Domain for OID 12.2.1.4

 

 

Configuring the Weblogic Domain

 

  • To configure the Weblogic Domain, execute the script ‘$ORACLE_HOME/oracle_common/common/bin/config.sh‘.   
  • On the first screen choose to CREATE A NEW DOMAIN and select the location for the domain creation. 
  • Oracle recommends separating the core Applications (Oracle Home) from the Configuration, so in this case we are storing the target Domain under the <PATH_TO_DOMAIN> directory.
  • [oidmgr@oidserver ~]$ cd $ORACLE_HOME/oracle_common/common/bin
  • [oidmgr@oidserver bin]$ ./config.sh

Enter the Domain Location
Selecting this template automatically selects the following as dependencies:

  • Oracle Internet Directory (Collocated) -12.2.1.3.0 [oid]
  • Oracle Directory Services Manager -12.2.1.3.0 [oid]
  • Oracle JRF -12.2.1.3.0 [oracle_common]
  • WebLogic Coherence Cluster Extension -12.2.1.3.0 [wlserver]
  • Oracle Enterprise Manager – 12.2.1.3.0 [em]
Enter the Application Location
Enter Weblogic Credentials Click Next
Select Domain Mode Production Select JDK Environment Click Next
Enter the Connection Details Highlighted Click Get RCU Configuration Click Next
Select All Component Schema Click Next
Click Next
Select the following:

  • Administration Server
  • Node Manager
  • Topology

Click Next
Click Next
Enter Weblogic Credentials Click Next
Add JRF-MAN-SVR from Server Groups Click Next
Click Next
Click Next
Click Next
Click Next
Click Unix Machine TAB
Add oidhost1 in Unix Machine  Note: Remove the entry from Machine tab. Click Next
Add Servers To the Machine Click Next
Click Next
Click Next
Click Create
Configuration Started
Click Next
Click Finish

Create OID Environment file

[oidmgr@oidserver ~]$ vi oid_env.env export ORACLE_COMMON_HOME=$ORACLE_HOME/oracle_common export ORACLE_HOME=/u02/app/oracle/Middleware/Oracle_Home export WL_HOME=$ORACLE_HOME/wlserver export JAVA_HOME=/u02/jdk1.8.0_361/ export DOMAIN_HOME=$ORACLE_HOME/user_projects/domains/oid_domain

Enabling Weblogic Startup without password

Enter the following parameter given below $DOMAIN_HOME/bin definition to enable reading boot.properties file for starting the Weblogic without Password [oidmgr@oidserver ~]$ cd $DOMAIN_HOME/bin [oidmgr@oidserver bin]$ vi setDomainEnv.sh JAVA_OPTIONS=”${JAVA_OPTIONS} -Dweblogic.system.BootIdentityFile=${DOMAIN_HOME}/security/boot.properties” export JAVA_OPTIONS

Create boot.properties file
[oidmgr@oidserver ~]$ cd /u02/app/oracle/Middleware/Oracle_Home/user_projects/domains/oid_domain/security [oidmgr@oidserver security]$ vi boot.properties
Also Create a folder named security in $DOMAIN_HOME/servers/AdminServer and cp the boot.properties file

The StopWebLogic.sh Command Fails With “No valid username/password or userConfigFile/userKeyFile provided” When boot.properties is Not Present. (Doc ID 2683299.1) The stopWebLogic.cmd Errors with “No valid username/password or userConfigFile/userKeyFile provided” (Doc ID 2633650.1)

[oammgr@oamserver security]$ mkdir -p $DOMAIN_HOME/servers/AdminServer/security [oammgr@oamserver security]$ cp boot.properties $DOMAIN_HOME/servers/AdminServer/security

 

Start Node Manager and the Admin Server

 In new shells start the Node Manager and the Admin Server with the commands ‘$DOMAIN_HOME/bin/startNodeManager.sh‘ and ‘$DOMAIN_HOME/bin/startWebLogic.sh‘ respectively.

[oidmgr@oidserver ~]$ . ./oid_env.env [oidmgr@oidserver ~]$ cd $DOMAIN_HOME/bin [oidmgr@oidserver bin]$ nohup ./startNodeManager.sh & [1] 11841 [oidmgr@oidserver bin]$ nohup: ignoring input and appending output to ‘nohup.out’ [oidmgr@oidserver bin]$ nohup ./startWebLogic.sh & [2] 12402 [oidmgr@oidserver bin]$ nohup: ignoring input and appending output to ‘nohup.out’

Login Weblogic Console
http://oidserver.com:7001/console Enter Username and Password
Weblogic Console Home Page

 

 

 

If you encounter any issues or have further questions, feel free to contact on Below: Linkedin 🔗  SyedSaadAli

 

 

 

 

 

Contact

Get in Touch
  • Address: Karachi, PAKISTAN
  • Email: askme@SyedSaadAli.com
  • Phone: +92-300-026-5668
  • Freelance: Available
Contact Form

    All Rights Reserved