Re: tnsManager Vs OID
Date: Mon, 26 Oct 2009 15:07:53 -0500
OID has been positioned as an industrial strength LDAP server. The pitch has been that because the data is stored in an Oracle database, all the basic advantages of Oracle apply (i.e. scalability, HA, recoverability, advanced replication capabilities, etc...) For example, a couple of my co-workers worked on a project where two OID thingies (not sure what to call them - containers maybe?) were created on separate RAC databases with two way replication between them. One was primary for users in the western half of the US, the other was primary for the rest. If I remember correctly, they had physical standbys hanging off of them as well. This was intended to be an enterprise wide mechanism for authenticating to all the companies apps. So availability was very important to say the least. I'm not saying other solutions couldn't match these kinds of capabilities, but that's how Oracle positioned it.
In addition, Oracle has bought a whole slew of companies with products in the identity management space and has been attempting to merge them into a cohesive product for the past couple of years. If the acquisition of Sun goes through, they will have yet another strong offering in that space to consider.
On Oct 25, 2009, at 2:52 AM, ~Jeff~ wrote:
> tnsManager just uses a tnsnames.ora file , no database required.
> Its a shame Oracle didn't make OID so elegantly simple!
> 2009/10/25 sundar mahadevan <sundarmahadevan82_at_gmail.com>
> From Alan's reply, Am I correct in understanding that OID requires an
> oracle database for names resolution. But with respect to tnsManager,
> I do not think it requires a database.
> On Fri, Oct 23, 2009 at 7:28 PM, Guillermo Alan Bort
> <cicciuxdba_at_gmail.com> wrote:
> > Plus you get the basic memory footprint of an Oracle Database... I
> > reckon you will need much memory... but at least 200MB...
> > cheers.
> > Alan Bort
> > Oracle Certified Professional