As an update to CheckPoint’s Blog on May 10th on the subject of Oracle’s EPM 184.108.40.206.900 release, we are posting our latest findings. The testing, and subsequent results are from our lab environment using simple test applications. The results may or may not be indicative of what we would expect to find in a “real-world” example. Your mileage may vary!
Oracle Data Integrator (ODI) offers many benefits to users extracting, loading, and transforming data in their data intelligence systems. It offers a practical GUI to the user so that they can effectively manage this data. A small setback, however, appears during troubleshooting: mismatched timestamps.
A challenge that is commonly overlooked when upgrading EPM is keeping your upgraded application in sync with your Legacy application after the initial upgrade, prior to go-live. The challenge comes from the requirement to continue day-to-day operations in the Legacy environment during the upgrade project time line. At some point, the Legacy application must be "upgraded." The upgraded application then becomes a snapshot, or a "Point in Time" of the Legacy application; any changes made in the Legacy environment beyond that point must be accounted for in some form or fashion in the new, or upgraded environment and application.
When working with a client reporting frequent slowdowns in copying of data between schemas, we asked the DBAs to investigate, as well as the UNIX team. Both teams reported that the individual database servers were performing fine, with plenty of resources available to them. However, after a number of conference calls, we overheard one of the team members say their HOST server was at or near 100% CPU usage and had been for some time. As the host was an Exadata 3 server, we had not anticipated we would be subject to shortages of system resources. Unfortunately, without visibility on the host server, we had to rely on reports from the teams maintaining the individual instances. Without us asking specifically for a screenshot of the host server’s performance statistics, we would not have been able to certify the issue was with the database server after all. As always, trust, but verify.
Oracle bundles an installer for WebLogic with their Oracle EPM suite of products, that ‘phones home’ to Oracle for more information. Many of us deal with clients who have firewalls that may block all attempts to communicate from the installation server to Oracle.com or other outside Internet addresses. In these cases, the installer for Oracle EPM informs us of the communication error and asks us to provide proxy information for the installer to communicate with Oracle.com. Refusal to grant the proxy information results in another nag screen after which we can move on with our installation.