Deploy Oracle E-Business Suite 12.2.13 from OCI Marketplace: Step-by-Step Guide
Deploying Oracle E-Business Suite 12.2.13 from OCI Marketplace — Step by Step Guide
Prerequisites:
System Requirements
- An OCI tenancy with sufficient service limits for VM.Standard3.Flex or BM.Standard3.64 shapes
- A Compartment with IAM policies permitting Marketplace subscriptions
- Valid Oracle EBS licences (the listing is BYOL — Bring Your Own License)
- OCI CLI installed and configured with a valid API key profile (or use OCI Cloud Shell)
- Basic familiarity with OCI Networking concepts (VCN, Subnets, Security Lists, NSGs)
Environment used in this article
- EBS 12.2.13 · Oracle Database 19c EE · Oracle Linux 8 (UEK R7)
- WebLogic 12.2.1.4 · JDK 8u391 · OCI CLI 3.43.x
- Region: uk-london-1 · Shape: VM.Standard3.Flex (16 OCPU / 256 GB)
1. Architecture Overview:
Before touching the OCI console or CLI, understand what the Marketplace image deploys. A standard single-node EBS on OCI deployment places the EBS node in a private subnet, fronted by an OCI Load Balancer in the public subnet, with a Bastion host for SSH access, block volumes for the application and database filesystems, and Object Storage for RMAN backups.
The Marketplace image provisions everything inside the EBS Node. Your responsibility is the surrounding OCI infrastructure: VCN, subnets, security lists / NSGs, load balancer, and the storage volumes attached at launch time.
2. Provision the Network Infrastructure:
Create the VCN and required subnets before launching the Marketplace image. The image installer expects to land in a private subnet with internet outbound via NAT Gateway for patching, and it expects the standard EBS ports to be permitted on the security list.
# Set your compartment OCID and region bash#export COMPARTMENT_ID="ocid1.compartment.oc1..aaaaaaaaxxxxxxxxxxx" bash#export REGION="uk-london-1" # 1. Create the VCN bash#oci network vcn create --compartment-id "${COMPARTMENT_ID}" --cidr-block "10.0.0.0/16" --display-name "ebs-vcn" --dns-label "ebsvcn" --region "${REGION}" # 2. Create the public subnet (Load Balancer + Bastion) bash#oci network subnet create --compartment-id "${COMPARTMENT_ID}" --vcn-id "${VCN_ID}" --cidr-block "10.0.1.0/24" --display-name "ebs-public-subnet" --dns-label "ebspublic" # 3. Create the private subnet (EBS node) bash#oci network subnet create --compartment-id "${COMPARTMENT_ID}" --vcn-id "${VCN_ID}" --cidr-block "10.0.2.0/24" --display-name "ebs-private-subnet" --dns-label "ebsprivate" --prohibit-public-ip-on-vnic true # 4. Create Internet Gateway (public) and NAT Gateway (private outbound) bash#oci network internet-gateway create --compartment-id "${COMPARTMENT_ID}" --vcn-id "${VCN_ID}" --display-name "ebs-igw" --is-enabled true bash#oci network nat-gateway create --compartment-id "${COMPARTMENT_ID}" --vcn-id "${VCN_ID}" --display-name "ebs-natgw"
Configure the security list for the private subnet to allow the standard EBS ports — web entry (4443/8000), Forms, database listener (1521), WebLogic managed servers (7201–7202), and SSH only from the Bastion subnet:
# Update private subnet security list with EBS ingress rules bash#oci network security-list update --security-list-id "${PRV_SECLIST_ID}" --ingress-security-rules '[ {"source":"10.0.1.0/24","protocol":"6","tcpOptions":{"destinationPortRange":{"min":4443,"max":4443}},"description":"EBS HTTPS web entry from LB"}, {"source":"10.0.1.0/24","protocol":"6","tcpOptions":{"destinationPortRange":{"min":8000,"max":8000}},"description":"EBS HTTP web entry from LB"}, {"source":"10.0.2.0/24","protocol":"6","tcpOptions":{"destinationPortRange":{"min":1521,"max":1521}},"description":"DB listener (intra-subnet)"}, {"source":"10.0.1.0/24","protocol":"6","tcpOptions":{"destinationPortRange":{"min":7201,"max":7202}},"description":"WebLogic managed servers"}, {"source":"10.0.1.0/24","protocol":"6","tcpOptions":{"destinationPortRange":{"min":22,"max":22}},"description":"SSH from Bastion"}, {"source":"10.0.0.0/16","protocol":"1","icmpOptions":{"type":3,"code":4},"description":"ICMP Path MTU"} ]' --force
3. Subscribing to the Marketplace Listing:
The Oracle E-Business Suite listing on OCI Marketplace is a BYOL (Bring Your Own License) listing — you must hold valid Oracle EBS licences. The subscription step associates the Marketplace image with your tenancy. In the OCI Console, navigate to Marketplace → All Applications and search for "Oracle E-Business Suite":
The same can be done fully from the CLI. First locate the listing and its latest package version:
# Search for Oracle EBS listings in the Marketplace bash#oci marketplace listing list --name "Oracle E-Business Suite" --compartment-id "${COMPARTMENT_ID}" --query 'data[*].{Name:name, ID:id, Publisher:publisher.name}' --output table +----------------------------------------------------+--------------------------------------+-----------+ | Name | ID | Publisher | +----------------------------------------------------+--------------------------------------+-----------+ | Oracle E-Business Suite 12.2.13 - BYOL | ocid1.appcataloglisting.oc1..aaaaxxxx | Oracle | | Oracle E-Business Suite Demo Install 12.2 | ocid1.appcataloglisting.oc1..aaaayyyy | Oracle | +----------------------------------------------------+--------------------------------------+-----------+ # Store the listing ID and get the latest package version bash#export LISTING_ID="ocid1.appcataloglisting.oc1..aaaaxxxx" bash#oci marketplace listing-package list --listing-id "${LISTING_ID}" --compartment-id "${COMPARTMENT_ID}" --query 'data[*].{"Version":"package-version","Type":"package-type"}' --output table +----------------+----------+ | Version | Type | +----------------+----------+ | 12.2.13.0.0 | IMAGE | | 12.2.12.0.0 | IMAGE | +----------------+----------+
Accept the Marketplace Terms of Use — this is mandatory before the image can be launched:
bash#export PKG_VERSION="12.2.13.0.0" # Get the agreement OCID for this listing + version bash#AGREEMENT_ID=$(oci marketplace listing-package-agreement list --listing-id "${LISTING_ID}" --package-version "${PKG_VERSION}" --compartment-id "${COMPARTMENT_ID}" --query 'data[0].id' --raw-output) # Accept terms bash#oci marketplace accepted-agreement create --compartment-id "${COMPARTMENT_ID}" --listing-id "${LISTING_ID}" --pac
4. Compute Shape and Storage Sizing:
Choosing the right compute shape is the most consequential pre-launch decision. EBS is memory-intensive — undersizing the node causes Java heap pressure on the application tier and buffer cache pressure on the database tier.
| OCI Shape | OCPUs | Memory | Suitable For | Status |
|---|---|---|---|---|
| VM.Standard3.Flex (8/128) | 8 | 128 GB | Sandbox / Demo / Small Production | ✓ Recommended |
| VM.Standard3.Flex (16/256) | 16 | 256 GB | Mid-size Production (50–200 users) | ✓ Recommended |
| VM.Standard3.Flex (32/512) | 32 | 512 GB | Large Production (200–500 users) | ✓ Recommended |
| BM.Standard3.64 | 64 | 1024 GB | Enterprise (500+ users, RAC candidate) | ✓ Enterprise |
| VM.Optimized3.Flex | 8–18 | up to 256 GB | High-frequency compute workloads | Optional |
| VM.Standard.E4.Flex | 8–64 | up to 1024 GB | Cost-optimised alternative | ⚠ Validate perf |
Storage volume layout
| Mount Point | Recommended Size | VPUs/GB | Content |
|---|---|---|---|
| /u01 | 200–300 GB | 20 (Balanced) | EBS Application filesystem (APPL_TOP, OA Framework, Concurrent Mgr) |
| /u02 | 500 GB – 2 TB | 30–50 (High) | Oracle Database files (datafiles, redo logs, control files) |
| /u03 | 200 GB | 20 | Staging area — patches, EBS technology stack files |
| /u04 | 200–500 GB | 10 (Low) | RMAN backup staging before export to Object Storage |
| Boot volume | 100 GB minimum | — | OS + /tmp — extend from the default at launch time |
# Get Availability Domain bash#export AD=$(oci iam availability-domain list --compartment-id "${COMPARTMENT_ID}" --query 'data[0].name' --raw-output) Using AD: bFuS:UK-LONDON-1-AD-1 # Create /u01 — EBS Application (200 GB, Balanced) bash#U01_ID=$(oci bv volume create --compartment-id "${COMPARTMENT_ID}" --availability-domain "${AD}" --display-name "ebs-u01-apptier" --size-in-gbs 200 --vpus-per-gb 20 --query 'data.id' --raw-output) # Create /u02 — Oracle DB files (800 GB, High Performance) bash#U02_ID=$(oci bv volume create --compartment-id "${COMPARTMENT_ID}" --availability-domain "${AD}" --display-name "ebs-u02-dbfiles" --size-in-gbs 800 --vpus-per-gb 30 --query 'data.id' --raw-output) # Create /u03 — Staging (200 GB, Balanced) bash#U03_ID=$(oci bv volume create --compartment-id "${COMPARTMENT_ID}" --availability-domain "${AD}" --display-name "ebs-u03-staging" --size-in-gbs 200 --vpus-per-gb 20 --query 'data.id' --raw-output)
5. Launching the EBS Instance:
With networking and volumes in place, launch the Marketplace image. Retrieve the image OCID from the Marketplace package, generate an SSH key pair, and launch the instance into the private subnet:
# Retrieve the image OCID from the Marketplace package bash#IMAGE_ID=$(oci marketplace listing-package get --listing-id "${LISTING_ID}" --package-version "${PKG_VERSION}" --compartment-id "${COMPARTMENT_ID}" --query 'data."app-catalog-listing-resource-version"."listing-resource-id"' --raw-output) Image OCID: ocid1.image.oc1..aaaaaaaaebs1213xxxxxxxxxxxxxxxxxxxxxxxxxx # Generate SSH key pair bash#ssh-keygen -t rsa -b 4096 -C "ebs-oci-deploy" -f ~/.ssh/ebs_oci_rsa -N "" # Launch EBS instance from the Marketplace image bash#INSTANCE_ID=$(oci compute instance launch \ --compartment-id "${COMPARTMENT_ID}" \ --availability-domain "${AD}" \ --display-name "ebs-app-db-01" \ --image-id "${IMAGE_ID}" \ --subnet-id "${PRV_SUBNET_ID}" \ --shape "VM.Standard3.Flex" \ --shape-config '{"ocpus": 16, "memoryInGBs": 256}' \ --boot-volume-size-in-gbs 100 \ --ssh-authorized-keys-file ~/.ssh/ebs_oci_rsa.pub \ --assign-public-ip false \ --hostname-label "ebsappdb01" \ --freeform-tags '{"env":"production","app":"oracle-ebs","version":"12.2.13"}' \ --query 'data.id' --raw-output) # Wait for instance to reach RUNNING state bash#oci compute instance get --instance-id "${INSTANCE_ID}" --query 'data."lifecycle-state"' --raw-output PROVISIONING PROVISIONING RUNNING
⚠ Important — attach volumes BEFORE the EBS installer runs. The Marketplace image triggers the EBS installer automatically on first boot. The installer expects /u01, /u02, and /u03 to be available. Attach your block volumes within 2–3 minutes of instance launch, or the installer will use the boot volume's space and you will need to re-run the install.
# Attach u01, u02, u03 (paravirtualized) bash#for VOLUME_ID in "${U01_ID}" "${U02_ID}" "${U03_ID}"; do oci compute volume-attachment attach --type "paravirtualized" --instance-id "${INSTANCE_ID}" --volume-id "${VOLUME_ID}" --is-shareable false & done; wait # Confirm attachments bash#oci compute volume-attachment list --compartment-id "${COMPARTMENT_ID}" --instance-id "${INSTANCE_ID}" --query 'data[*].{"State":"lifecycle-state","Device":"device"}' --output table +----------+---------------------------+ | State | Device | +----------+---------------------------+ | ATTACHED | /dev/oracleoci/oraclevdb | | ATTACHED | /dev/oracleoci/oraclevdc | | ATTACHED | /dev/oracleoci/oraclevdd | +----------+---------------------------+
6. Post-Launch: Configure the EBS Instance:
SSH into the instance via your Bastion host, then format and mount the block volumes, and set the Oracle environment before the final configuration step.
# SSH in via Bastion and become root [local]$ ssh -J opc@<bastion-public-ip> opc@10.0.2.10 -i ~/.ssh/ebs_oci_rsa [opc@ebsappdb01 ~]$ sudo -i # List attached block devices [root@ebsappdb01 ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 100G 0 disk └─sda1 8:1 0 100G 0 part / sdb 8:16 0 200G 0 disk ← /u01 sdc 8:32 0 800G 0 disk ← /u02 sdd 8:48 0 200G 0 disk ← /u03 # Format with xfs (Oracle-recommended for EBS on OL8), create mount points, mount [root@ebsappdb01 ~]# mkfs.xfs -L u01 /dev/sdb; mkfs.xfs -L u02 /dev/sdc; mkfs.xfs -L u03 /dev/sdd [root@ebsappdb01 ~]# mkdir -p /u01 /u02 /u03 [root@ebsappdb01 ~]# mount /dev/sdb /u01; mount /dev/sdc /u02; mount /dev/sdd /u03 # Persist across reboots [root@ebsappdb01 ~]# cat >> /etc/fstab << 'FSTAB' LABEL=u01 /u01 xfs defaults,_netdev,noatime 0 0 LABEL=u02 /u02 xfs defaults,_netdev,noatime 0 0 LABEL=u03 /u03 xfs defaults,_netdev,noatime 0 0 FSTAB [root@ebsappdb01 ~]# df -hT | grep "^/dev/sd[b-d]" /dev/sdb xfs 200G 1.3G 199G 1% /u01 /dev/sdc xfs 800G 1.3G 799G 1% /u02 /dev/sdd xfs 200G 1.3G 199G 1% /u03
Set ownership and the Oracle environment variables for the oracle OS user (already created by the Marketplace image):
[root@ebsappdb01 ~]# id oracle uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba),54323(oper) [root@ebsappdb01 ~]# chown oracle:oinstall /u01 /u02 /u03 [root@ebsappdb01 ~]# chmod 775 /u01 /u02 /u03 [root@ebsappdb01 ~]# su - oracle [oracle@ebsappdb01 ~]$ cat >> ~/.bash_profile << 'PROFILE' # Oracle EBS Environment export ORACLE_BASE=/u01/app/oracle export ORACLE_HOME=/u01/app/oracle/product/19c/db_1 export ORACLE_SID=EBSDB export TWO_TASK=EBSDB export EBS_APPS_HOME=/u01/oracle/EBSDB/fs1/EBSapps/appl export NLS_LANG=AMERICAN_AMERICA.AL32UTF8 export NLS_DATE_FORMAT="DD-MON-RRRR HH24:MI:SS" export PATH=$ORACLE_HOME/bin:$EBS_APPS_HOME/ad/bin:$PATH export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH PROFILE [oracle@ebsappdb01 ~]$ source ~/.bash_profile
7. Running the EBS Installer (Rapid Install Wizard):
The Marketplace image includes the Oracle EBS Rapid Install Wizard (RIW). On first boot it auto-runs with a default parameter file. For production, interrupt auto-start and run the wizard manually with your site-specific parameters.
# Check installer status and view the parameter file used by the image [oracle@ebsappdb01 ~]$ ps -ef | grep rapidwiz | grep -v grep [oracle@ebsappdb01 ~]$ tail -f /u01/install/APPS/rapidwiz/log/installDB.log [oracle@ebsappdb01 ~]$ cat /u01/install/APPS/rapidwiz/conf/install.txt ===== EBS Rapid Install Configuration ===== s_base_dir = /u01/oracle/EBSDB s_dbSid = EBSDB s_hostname = ebsappdb01.ebsprivate.ebsvcn.oraclevcn.com s_dbhost = ebsappdb01.ebsprivate.ebsvcn.oraclevcn.com s_appsuser = APPS s_webentryurlprotocol = https s_active_webport = 4443 s_login_page = OA_HTML/AppsLogin s_charset = AL32UTF8 s_install_type = SingleNode # Run installer in express mode (unattended) — takes 30–90 minutes depending on shape [oracle@ebsappdb01 ~]$ cd /u01/install/APPS/rapidwiz [oracle@ebsappdb01 rapidwiz]$ ./rapidwiz -express -techStackOnly no -paramfile ./conf/install.txt # Monitor install progress in a separate session [oracle@ebsappdb01 ~]$ tail -100f /u01/install/APPS/rapidwiz/log/installDB.log AutoConfig is running... [INSTE8 ADM 2601] Starting Oracle 19c database creation Creating database EBSDB... Creating datafiles in /u02/oradata/EBSDB/ [INSTE8 ADM 2603] Database creation completed successfully [INSTE8 ADM 3001] Starting EBS schema creation (APPS, SYSTEM, ...) Loading EBS seed data... Running post-install scripts... [INSTE8 ADM 9000] EBS installation completed successfully Total install time: 47 minutes 22 seconds
8. Starting and Verifying EBS Services:
After the installer completes, start the EBS application and database services and run a health check to confirm the environment is operational.
# Source the EBS run edition environment (fs1 or fs2) [oracle@ebsappdb01 ~]$ source /u01/oracle/EBSDB/fs1/EBSapps/appl/APPSEBSDB_ebsappdb01.env # Start the database [oracle@ebsappdb01 ~]$ sqlplus / as sysdba <<SQL startup; exit; SQL # Start the EBS application services (WebLogic, OAF, Forms, Concurrent Mgr) [oracle@ebsappdb01 ~]$ $ADMIN_SCRIPTS_HOME/adstrtal.sh apps/${APPS_PASSWORD} You are running adstrtal.sh version 120.20.12020000.13 Starting Oracle Application Database Listener... [ OK ] Starting Oracle DB (EBSDB)... [ OK ] Starting Oracle Web Listener... [ OK ] Starting Oracle Forms Server... [ OK ] Starting Oracle Reports Server... [ OK ] Starting Concurrent Processing Managers... [ OK ] Starting Oracle WebLogic Managed Servers... [ OK ] All services started successfully. # Verify database is open [oracle@ebsappdb01 ~]$ sqlplus -S / as sysdba <<SQL SELECT instance_name, status, database_status FROM v$instance; exit; SQL INSTANCE_NAME STATUS DATABASE_STATUS -------------- ----------- --------------- EBSDB OPEN ACTIVE # Check EBS application server ports [oracle@ebsappdb01 ~]$ ss -tlnp | grep -E "4443|8000|7201|7202|1521" LISTEN 0 128 0.0.0.0:1521 users:(("tnslsnr",pid=2341,fd=9)) LISTEN 0 128 0.0.0.0:8000 users:(("httpd",pid=3102,fd=4)) LISTEN 0 128 0.0.0.0:4443 users:(("httpd",pid=3102,fd=6)) LISTEN 0 128 0.0.0.0:7201 users:(("java",pid=4210,fd=42)) LISTEN 0 128 0.0.0.0:7202 users:(("java",pid=4210,fd=44))
9. Configuring OCI Load Balancer for EBS:
Expose EBS through an OCI Load Balancer in the public subnet. This provides TLS termination, health checking, and session persistence — all required for production EBS access.
# Get the private IP of the EBS instance bash#EBS_PRIVATE_IP=$(oci compute instance list-vnics --instance-id "${INSTANCE_ID}" --query 'data[0]."private-ip"' --raw-output) EBS private IP: 10.0.2.10 # Create Load Balancer in the public subnet bash#LB_ID=$(oci lb load-balancer create --compartment-id "${COMPARTMENT_ID}" --display-name "ebs-lb" --shape-name "flexible" --shape-details '{"minimumBandwidthInMbps":100,"maximumBandwidthInMbps":1000}' --subnet-ids '["'"${PUB_SUBNET_ID}"'"]' --is-private false --wait-for-state ACTIVE --query 'data.id' --raw-output) # Create backend set with IP_HASH policy + session persistence (required for EBS) bash#oci lb backend-set create --load-balancer-id "${LB_ID}" --name "ebs-backend-set" --policy "IP_HASH" --health-checker '{"protocol":"HTTP","port":8000,"urlPath":"/OA_HTML/AppsLogin","returnCode":200,"intervalInMillis":10000,"timeoutInMillis":3000,"retries":3}' --session-persistence-configuration '{"cookieName":"EBS_SESSION","disableFallback":false}' # Add EBS node as a backend (EBS web entry port 4443) bash#oci lb backend create --load-balancer-id "${LB_ID}" --backend-set-name "ebs-backend-set" --ip-address "${EBS_PRIVATE_IP}" --port 4443 --weight 1 # Create HTTPS listener (public :443 → EBS :4443) bash#oci lb listener create --load-balancer-id "${LB_ID}" --name "ebs-https-listener" --default-backend-set-name "ebs-backend-set" --port 443 --protocol "HTTP" # Get the LB public IP bash#oci lb load-balancer get --load-balancer-id "${LB_ID}" --query 'data."ip-addresses"[0]."ip-address"' --raw-output 132.145.xxx.xxx
10. Post-Deployment Checklist:
Before handing the environment over to users or beginning data migration, complete this verification checklist:
- ✅ EBS login page accessible via Load Balancer public IP on port 443
- ✅ Oracle DB EBSDB instance status is OPEN in v$instance
- ✅ Concurrent Processing Manager is running (adcmctl.sh status)
- ✅ All block volumes mounted, in /etc/fstab with _netdev, and writable by oracle user
- ✅ RMAN baseline backup completed to Object Storage bucket
- ✅ OCI Vault secrets created for APPS, SYSTEM, and applsyspub passwords
- ✅ Oracle Alert Log reviewed for ORA- errors post startup
- ✅ EBS AutoConfig run with production hostname and URL
- ✅ Load Balancer health check returning HTTP 200 on /OA_HTML/AppsLogin
- ✅ Bastion host configured with time-limited session policies
- ✅ OCI Monitoring alarms set for CPU, memory, and disk thresholds
# Run AutoConfig after DNS / hostname update — Application Tier then DB Tier [oracle@ebsappdb01 ~]$ $ADMIN_SCRIPTS_HOME/adautocfg.sh apps/${APPS_PASSWORD} [oracle@ebsappdb01 ~]$ $ORACLE_HOME/appsutil/scripts/EBSDB_ebsappdb01/adautocfg.sh # Verify web entry point settings in the context file [oracle@ebsappdb01 ~]$ grep -iE "s_webentryurlprotocol|s_webentryhost" $CONTEXT_FILE <oa_var name="s_webentryurlprotocol" value="https"/> <oa_var name="s_webentryhost" value="ebs.yourdomain.com"/> # Confirm the login page responds — HTTP 200 bash#curl -sk -o /dev/null -w "%{http_code} — %{time_total}s\n" "https://132.145.xxx.xxx/OA_HTML/AppsLogin" 200 — 0.412s ← EBS login page responding normally
Change all default passwords immediately. The Marketplace image ships with default passwords for the APPS schema, SYSTEM, applsyspub, and the oracle OS user. Change them all before any data migration or user access. Store secrets in OCI Vault — never in shell scripts or environment files on the filesystem.
Conclusion:
The OCI Marketplace image turns what used to be a multi-day EBS installation into an afternoon's work: subscribe to the listing, land the instance in a private subnet with block volumes attached before the installer fires, let the Rapid Install Wizard build the database and application tiers, and front everything with an OCI Load Balancer doing TLS termination, health checks, and session persistence. Layering in Object Storage-based RMAN backups, OCI Vault for secrets, and OCI Monitoring alarms turns this from a one-time setup into an operationally sound production platform.
Common mistakes to avoid: launching before accepting the Marketplace Terms of Use, attaching block volumes after the auto-installer has already started (it will consume the boot volume), placing the EBS node in a public subnet, skipping the _netdev flag in /etc/fstab (volumes fail to mount on reboot), leaving default APPS/SYSTEM passwords in place, forgetting to re-run AutoConfig after the hostname or web entry URL changes, and exposing ports 1521/4443 directly to the internet instead of via the Load Balancer.
References & Documentation:
- Oracle E-Business Suite on OCI Marketplace — cloudmarketplace.oracle.com
- Deploy Oracle EBS on OCI — Reference Architecture — docs.oracle.com/en/solutions/deploy-ebs-on-oci
- Oracle EBS Rapid Install Wizard (RIW) Guide — docs.oracle.com
- OCI Marketplace Documentation — docs.cloud.oracle.com
- My Oracle Support Note 2517025.1 — EBS on OCI: Known Issues and Best Practices
- My Oracle Support Note 1506931.1 — EBS 12.2: Minimum Technical Requirements
Syed Zaheer
Service Delivery Director · Techvisions · Cloud, AI & Managed Infrastructure
Syed Zaheer is Service Delivery Director at Techvisions, author, speaker, and technology enthusiast with deep expertise in the Oracle landscape covering databases, middleware, Applications, AI and cloud infrastructure. He actively contributes to the Oracle community through technical articles, conference presentations, and knowledge-sharing initiatives, helping organizations modernize and optimize their enterprise technology platforms.
Comments