In the course of applying a CPU patch to Oracle, OPatch throws an error 130 and exits. This is in conjunction with attemptiing to get beyond the Oracle Configuration Management section of OPatch.
Oracle Configuration Manager (OCM) is a program being promoted by Oracle that allows Oracle to store certain information regarding a database. It requires a metalink ID and Oracle CSI, both of which Symantec does not provide to customers as Symantec is responsible for providing its customers with Oracle support with their Data Loss Prevention product. By not declining OCM appropriately, OPatch will wait for a valid username and CSI to connect to Oracle, and will throw a 130 if null or invalid.
If during the Oracle install, anything comes up prompting you to provide Oracle with information such as the CSI, you are to opt out. Oracle may ask if you agree to the license statement (for, it turns out, OCM), and if you say “yes”, you are on the path to installing OCM. Symantec DLP customers are advised to NOT agree to the license to avoid getting the Opatch 130 error.