Re: GLOBAL_NAMES parameter for streams
Date: Sat, 24 May 2008 20:31:47 -0500
GLOBAL_NAMES=TRUE is a requirement in the documentation and I had the same concerns as you did when I implemented Streams, so I opened a SR regarding this. The bottom line is it's not necessary, but as you say, you may run into a support issue. For me there was no way around setting it to FALSE (way too many db links named wrong for TRUE) so I just had to go with it and never ran into an issue (like Krish).
On Sat, May 24, 2008 at 1:31 AM, <krish.hariharan_at_quasardb.com> wrote:
> I wasn't aware of the requirement that this has to be true. I am running
> streams or testing it with it false but with the db links matching the
> target database's global name. I cannot set global_names to true as there
> are other links in the database that do not conform.
> If the duty manager stated that, then I would ask for a metalink or Oracle
> Documentation reference that states that (I would be interested in your
> discovery as well). BTW, in my case the set up works just fine, which I
> guess is not the point of this email.