Re: Need a different Toad for RAC?

We have seperate installer toad for oeacle rac that comes with different
license key.

Manju
On Feb 23, 2013 2:04 AM, "SCHROEDER, NATHAN E (AG/1000)" <
[email protected]> wrote:

> **
>
>
>  One of our databases just got migrated to a RAC platform. As we’re
> working with it and finding out new things, one of my teammates wrote:
>
> I’m hoping the issue with <xxx> is resolved… I guess we’ll see tomorrow.
> There was another session on the second node on the database that had a
> lock but I couldn’t see that session since I was on node 1.  <Name> said to
> see sessions in TOAD session browser across nodes I will need Toad for
> RAC.  Nate I know you are a TOAD beta user… have you ever used Toad for
> RAC?  Do you know if our current licenses cover it?
>
> I looked up the Toad white paper “Toad Says RAC ‘Em Up!” to try to see
> what *Toad DBA Suite for Oracle **–** RAC Edition* would bring to the
> party. So far as I can tell, it would provide a number of cool additional
> capabilities in the Spotlight tool; but it shouldn’t be needed for what my
> friend needed, namely the ability to see all object locks from any node in
> the Toad session browser.
>
> Is that correct? Should we expect the base Toad session browser to be able
> to show information about sessions on all nodes of the RAC? Or do we need a
> different Toad for that?
>
> Nate Schroeder
> Data Tech Lead - US Row Crops IT Data Management Team
> Monsanto Company
> 800 N. Lindbergh Blvd. G3WB - Saint Louis, MO - 63167
> 314-694-2592
>
>
> This e-mail message may contain privileged and/or confidential
> information, and is intended to be received only by persons entitled
> to receive such information. If you have received this e-mail in error,
> please notify the sender immediately. Please delete it and
> all attachments from any servers, hard drives or any other media. Other
> use of this e-mail by you is strictly prohibited.
>
> All e-mails and attachments sent and received are subject to monitoring,
> reading and archival by Monsanto, including its
> subsidiaries. The recipient of this e-mail is solely responsible for
> checking for the presence of "Viruses" or other "Malware".
> Monsanto, along with its subsidiaries, accepts no liability for any damage
> caused by any such code transmitted by or accompanying
> this e-mail or any attachment.
>
>
> The information contained in this email may be subject to the export
> control laws and regulations of the United States, potentially
> including but not limited to the Export Administration Regulations (EAR)
> and sanctions regulations issued by the U.S. Department of
> Treasury, Office of Foreign Asset Controls (OFAC).  As a recipient of this
> information you are obligated to comply with all
> applicable U.S. export laws and regulations.
>  
>