However I do work with databases on a daily basis and that means I need to be aware of licensing 'things'. Often I get access to accounts with privileges for various dictionary views. And there are some views and tables which can only be queried after supplying large amounts of folding paper to your friendly Oracle reseller.
That's one of my dislikes about Oracle. I'd be much happier if those views and packages which require the diagnostic, tuning or whatever packs were secured by some additional role to make them EXTREMELY obvious.
And development and test databases are another thing. It's all very well pretending things can be covered by OTN licences, but some things aren't. Throwing up another database for testing isn't necessarily covered by your existing licences. And what about that readonly standby ? Or that one on the VMWare server ?
Anyway, I've got my diary booked in for Mogens Nørgaard talking to us Sydneysiders about the joys of Oracle licensing in just under two weeks. If you've got any questions you want to pose (apart from why are they so bleeding expensive), add a comment.
I'd like to know more about Amazon Oracle pay-by-the-hour, due in the next couple of months, but I think we'll all have to wait for that.
2 comments:
And DBAs / Consultants who install "everything" (a "default install") and don't care to check if someone had started creating Partitioned Tables !
And DBAs who run scripts that they shouldn't be running.
And DBAs who advise management that a DG standby does not need to be licenced.
Hemant
I'd hope DBAs have a good idea of what the licenses are on the databases for which they are responsible.
It would be nice in MOS to have a screen indicating what you are licensed for, and a corresponding screen in Enterprise Manager indicating what you are running.
The other 'faultline' are the managers of the DBAs (up to CEOs/CIOs) who instruct the DBA to install or run stuff for which the firm isn't licensed. Puts the DBA in a VERY difficult spot.
Post a Comment