Yeah, you are right,
that cman.ora is sqlnet.ora
my cman.ora is:
cman=(address=(protocol=tcp)(host=ops001.corp.abc.com)(port=1630))
cman_rules=
(rule_list=
(rule=(src=ops002.corp.abc.com)(dst=ops001.corp.abc.com)(srv=TARGETDB.C
ORP.ABC.COM)(act=accept)))
Good at least cman.ora does not need on client.
I think I will give it another try with CMCTL...
In article <9stqo3$9ve$1_at_cronkite.cc.uga.edu>, Jeff <jeff_at_work.com> wrote:
>In article <5f8af180.0111131806.267f72fe_at_posting.google.com>, dominica_l_at_yahoo.com (Dominica Leung) wrote:
>
>>My question is ?
>>Is there any daemon, I need to turn ON
>>for the CMAN-server side???
>
>Yes. CMCTL is the control utility that you need to do so.
>
>
>>Also, what should be the cman.ora look like in ops002,the client
>>side, I am assuming that file should NOT exist at all.
>
>What you had listed as cman.ora on 001 was actually sqlnet.ora. You should
>read the online documentation (go search Oracle's web site for "configuring
>connection manager" or "cman.ora") for the proper cman.ora setup. You are
>correct in that cman.ora does not belong on the client side.
Received on Wed Nov 14 2001 - 18:39:49 CST
