tag:blogger.com,1999:blog-7650953985627040991.post8433332786500969662..comments2024-02-14T05:30:55.538-05:00Comments on Cameron's Blog For Essbase Hackers: The Compleat Idiot's Guide to PBCS, No. 17 -- License ComplianceCameron Lackpourhttp://www.blogger.com/profile/07701786303677521318noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7650953985627040991.post-11680202609335488222016-10-25T09:10:01.541-04:002016-10-25T09:10:01.541-04:00Richard,
What I don't understand is *why* Ora...Richard,<br /><br />What I don't understand is *why* Oralce allows anyone to create an application he doesn't have access to? Surely if Contracts can identify who's in violation of a license, the logon id can be prevented from doing The Wrong Thing. Why make it possible at all?<br /><br />Regards,<br /><br />Cameron LackpourCameron Lackpourhttps://www.blogger.com/profile/07701786303677521318noreply@blogger.comtag:blogger.com,1999:blog-7650953985627040991.post-7916444178158276012016-10-25T02:57:51.637-04:002016-10-25T02:57:51.637-04:00What I found annoying is that when managing the PO...What I found annoying is that when managing the POD, Oracle have called it planning regardless of the licence type you have. So I have two PODs both called planning even though one is FCCS and one is PBCS. Would have been easier to have a licence type match the provisioning rather than showing everyne that your paying such as difference only for the pre-developed IP, and allowing them Indiana Jones style to "choose poorly".<br /><br />Richard Philipsonhttps://www.blogger.com/profile/14829290828826557867noreply@blogger.com