Apps DBA Workshop

 Implementing a Disaster Recovery (DR) strategy for Oracle E-Business Suite (EBS) between on-premises and Oracle Cloud Infrastructure (OCI) involves carefully planning data replication, failover, and recovery to ensure business continuity. Below are best practices to help you build a robust, secure, and cost-effective DR architecture. Oracle E-Business Suite DR Best Practices (On-Prem to OCI) 1. Architect a DR Topology Based on Business Needs Active-Passive (Cold or Warm DR) : EBS runs on-prem; OCI is the failover site. Cold Standby : Cost-effective; environment is spun up only during failover. Warm Standby : EBS application tier is always available, but database is synchronized. 2. Use Oracle Data Guard for Database Synchronization Oracle Data Guard (Physical Standby) is the recommended method to replicate the EBS database to OCI. Enables real-time or near-real-time replication of the on-prem DB to OCI. Supports Fast-Start Failover and Snapshot Standby f...

Oracle Solaris and IBM AIX are both enterprise-grade Unix operating systems that have long histories in mission-critical environments. However, their future is increasingly uncertain as the IT industry shifts toward cloud-native, Linux-based, and containerized solutions. Oracle Solaris has seen limited development in recent years, with Oracle focusing more on its cloud offerings, leading many to question its long-term viability. Similarly, IBM AIX, while still actively supported, is increasingly viewed as a legacy system as IBM emphasizes Linux, particularly Red Hat Enterprise Linux, for modernization and hybrid cloud strategies. Despite continued use in sectors like finance and government, where stability and long-term support are crucial, both Solaris and AIX face declining adoption and a shrinking talent pool, suggesting that their roles in enterprise IT will continue to diminish in the coming years. Migrating an Oracle E-Business Suite (EBS) database from Solaris to Linux involves ...

In one of the customer environment while performing the Oracle EBS R12.2.0 Base install it failed with the following error message. RW-50010: Error: - script has returned an error: 1 RW-50004: Error code received when running external process. Check log file for details. Running Database Install Driver for VIS instance RMAN Log file Phase 3 Rename Database Executing command: sh -c "ORACLE_SID=ORCLVIS;export ORACLE_SID;ORACLE_HOME=/u01/oracle/VIS/12.1.0;export ORACLE_HOME; /u01/oracle/VIS/12.1.0/bin/rman target / nocatalog @/u01/oracle/VIS/12.1.0/appsutil/out/VIS_ebsapps/restore-rac3.rman > /u01/oracle/VIS/12.1.0/appsutil/out/VIS_ebsapps/restore-rac3.log" Unable to rename database RW-50010: Error: - script has returned an error: 1 RW-50004: Error code received when running external process. Check log file for details. Running Database Install Driver for VIS instance [root@ebsapps lib]# cat /u01/oracle/VIS/12.1.0/appsutil/out/VIS_ebsapps/restore-rac3.log Recovery Mana...