Hmmm... If you are using DataGuard, you need EE, don't you? I'm pretty sure that DG has never been available with SE, although that *might* have changed with 11g. (I am pretty sure that looked when 11g was announced and I don't * recall* seeing any changes to DG licensing rules. That doesn't mean they weren't there, though.) Now, while it is true that you don't *have* to license EE by CPU, you *do*have to license a *minumum* of 25 named users per CPU (with EE, that is), which means *at least* the 50% of the cost of CPU licenses. There's one other little matter. Last time I checked, you were required to license your DG standby database with the *same licensing metric* as you have for the primary. That is, if you use CPU licensing for the primary database, you must use CPU licensing for the standby. Of course, nothing * requires* you to have the same number of CPUs for the standby -- unless you want to do something lavish, like load-testing or performance testing. Bottom line: standby databases are generally far from free. Or -- in most cases -- cheap. On Mon, Mar 17, 2008 at 8:51 AM, dbvision@xxxxxxxxxxxx < dbvision@xxxxxxxxxxxx> wrote: > And where was it said > or implied it wasn't licensed? > What it doesn't have to be is a > full-on EE, CPU-based licence. > > > On Mon Mar 17 20:03 , "Bradd Piontek" sent: > > >Am I missing something? Whether you are using dataguard or not, you need > to > license the test database. > > > > > >On Mon, Mar 17, 2008 at 3:55 AM, LS Cheng <exriscer@xxxxxxxxx> wrote: > > > >I am not sure how Mirrorview license works but with DG you pay per > instance per > CPU so it gets damn expensive..... > > > > > >-- > >LSC > > > > -- > //www.freelists.org/webpage/oracle-l > > > -- Cheers, -- Mark Brinsmead Senior DBA, The Pythian Group http://www.pythian.com/blogs