RE: Step down - EE to SE
From: Hand, Michael T <HANDM_at_polaroid.com>
Date: Fri, 17 Oct 2008 11:11:28 -0400
Message-ID: <0B43A9298955E14183B7AFAD4A11FC21052AC6CA@USHQEXVS.polanet.polaroid.com>
Date: Fri, 17 Oct 2008 11:11:28 -0400
Message-ID: <0B43A9298955E14183B7AFAD4A11FC21052AC6CA@USHQEXVS.polanet.polaroid.com>
Guillermo,
I don't see how a schema level exp/imp will help. I.E. In an EE database, userA creates a procedure which calls dbms_sqltune. If userA is exported, and imported into a SE database, the procedure will be imported and still function but will now be in violation of the SE license.
Now, I can't say how likely I am to find this kind of scenario, nor how stringent Oracle would be if they discovered this at a customer's site, but I'd rather error on the side of compliance.
Mike Hand
From: Bort, Guillermo [mailto:guillermo.bort_at_eds.com] Sent: Friday, October 17, 2008 10:39 AM To: Hand, Michael T; Allen, Brandon; oracle-l Subject: RE: Step down - EE to SE How about export/import at schema level? Guillermo Alan Bort DBA / DBA Main Team EDS, an HP company
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Oct 17 2008 - 10:11:28 CDT