Re: Interesting OEM issue

Jarad,

How have you configured the target machine? Make sure the listener is configured correctly and you can make a sqlnet connection to the database. Start the agent on the target agentctl -start (lsnrctl dbsnmp_start for 8i and ) and discover the node from OEM. If the node can be discovered automatically then all should be OK. If not then it should give the reason why. If after this you cannot open the target from OEM you may have some listener configuration problem on the target(perhaps not using correct DNS name).

If you make any changes to the listener then shut down the agent and delete the config files it generated in $ORACLE_HOME/network/agent and $ORACLE_HOME/network/admin then start the agent again. The agent creates the config files when it is first started.

The first one is always the hardest but OEM works fine on Linux.

"Jared" <jared_at_hwai.com> wrote in message news:480f610.0205011306.16a1574b_at_posting.google.com...
> Hi, all
>
> I am running OEM 9.0.1.0.0 on a Linux box. It appeared to install
> properly. When I run it standalone it works fine; when I sign on to
> the repository (9.0.1, on the same machine) I created and try to
> access a database I get an ORA 12645.
>
> I have compared sqlnet.ora files between the console box and an
> instance I manually configured (and can manage when I start the
> console standalone), and they are identical. This is weird. Has
> anyone seen this and if so, what was the problem (and fix)?
>
> TIA -
>
> Regards,
> jh
Received on Thu May 02 2002 - 04:56:24 CDT