myblog

Certificates expire, weekends don’t. This post shows how we eliminated manual renewals by scripting the entire path— CertifyTheWeb → OpenSSL → OCI CLI —including temporary Port 80 open/close , issuer auto-detect (R10–R13) , PFX export , and a clean push to OCI Certificates . The result: fewer outages, faster audits, and a repeatable pipeline your ops team can trust. Goal: Fully automate Let's Encrypt renewals on Windows and update OCI Certificates programmatically. Pattern: CertifyTheWeb renews → OpenSSL extracts keys/chain → OCI CLI updates the certificate resource. Security: Temporarily open Port 80 only for ACME HTTP-01, then auto-close. Outcome: Zero-click rotation, audit-friendly logs, and consistent results. Architecture at a Glance Please find the attached script here. https://drive.google.com/file/d/1ojvDTS3zemaxuEAv8by7R-r4ruDgfSma/view?usp=drive_link Flow 1. CertifyTheWeb renews via ACME HTTP-01. 2. Script opens Port 80 on the OCI Security List (short window). 3. Export n...

  Introduction Many legacy enterprise systems still operate on aging infrastructure and unsupported platforms. In this scenario, the production Oracle E-Business Suite (EBS) 11.5.10.2 and Oracle Database 11.2.0.4 Enterprise Edition are hosted together on a single physical on-premises server running Oracle Linux 5.11 (64-bit). While this setup has supported critical business operations, it presents challenges such as hardware limitations, lack of vendor support, and upgrade constraints. As a first step toward modernization, the entire environment is being migrated “as-is” to Oracle Cloud Infrastructure (OCI), using a custom Oracle Compute VM with Oracle Linux 5.11. This approach enables a seamless lift-and-shift migration with minimal downtime and no immediate application changes. ⚠️ Important to note: Although Oracle Linux 5.11 is out of support, moving to OCI provides the customer with flexibility and safety to later upgrade the OS and application stack at their own pace. We stron...

Oracle's Exadata Cloud Service (ExaCS) in Oracle Cloud Infrastructure (OCI) has undergone changes in database version support, specifically for older versions like Oracle Database 11g, 12c and 19c non-container database. These versions are no longer visible or available for provisioning new databases in the OCI console for Exadata Cloud Service. In Oracle Database 19c, CDB (Container Database) architecture is the default and recommended configuration. However, Oracle still allows creating non-CDB 19c databases under certain conditions for backwards compatibility, though this is not recommended. Since Oracle recommends transitioning to CDB, and non-CDB architecture is officially desupported starting with Oracle 21c, if you still need to create a non-CDB in Oracle 19c on Exadata Cloud Service (ExaCS), you can follow these steps manually. Oracle does not recommend creating non-CDBs for any new applications. If you need to use a non-CDB, you may need to do so through manual steps as ...