Actually, the principles for Netview are different.
When using Netview, you need to create the name of the rim object differently,
try "netview@jupiter" and it should work, not just the keyword netview alone. I
assume your tnsnames.ora file has been correctly configured ??
The reason why the user id etc was blank before may have been due to the
correctly named rim object not being found.
wrimtest -l may test correctly if you don't use this format, but Netview comms
won't work.
Mark
Vladimir Petr <petr@DATASYS.CZ> on 30/09/99 06:55:40
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L@UCSBVM.ucsb.edu>
To: NV-L@UCSBVM.ucsb.edu
cc:
Subject Re: Configuration of RIM object - take 2
:
John,
I will add a few comments. I have never used RIM with NetView but I have
with TEC and Inventory. The principles are the same.
John Grover wrote:
> I'd like to reassert the question asked by Wenlong Wang last week
> concerning problems we are having connecting Netview to our Oracle
> database. I will excerpt pertinent segments of his mail.
>
> > We created the TME 10 NetView Database in the database server and used
> > the following command to create the RIM object:
> >
> > wcrtrim -v Oracle -h jupiter.caps.maine.edu -d UMSB -u jupiter -H
> > /usr/OV/oracle/product -s saturn_tcp_UMSB netview
> >
> > note: /usr/OV/oracle/product is in
> > jupiter.caps.maine.edu side
>
Have you tried to run SQL*Plus session as that user? Have you connected
successfully? Really, it does not matter what the user name is provided the
desired schema for the user has been created in the database. Running
wgetrim will just tell you what you have entered. There is no connection
being created to the instance to verify all is correct. To test if the RIM
attributes are correct, either run SQL*Plus session under the environment
equal to them (set $ORACLE_SID, $ORACLE_HOME, $TWO_TASK environment
variables and run the session under that user). Or use
wrimtest -l <RIM_name>.
If the session opens, everything's fine. Otherwise, it will tell you more
about the reason why it could not connect.
>
> Ken Garst suggests that the -u jupiter should be -u netview as evidenced
> by the wgetrim output seen below:
>
> >
> > This command was successful. By using 'wgetrim netview', we got:
> >
> > RIM Host: jupiter.caps.maine.edu
> > RDBMS User: jupiter
> > RDBMS Vendor: Oracle
> > Database ID: UMSB
> > Database Home: /usr/OV/oracle/product
> > Server ID: saturn_tcp_UMSB
> > Instance Home:
>
> However, our RDBMS user is indeed jupiter, so I'm not sure changing to
> -u netview will help, will it? Of concern and confusion to us are the 2
> parameters supplied for Database Home and Server ID. Is Database Home
> where the rdbms resides or where the oracle tree (clients only) on the
> local machine is? And what (in Oracle-speak) is desired for Server ID.
> We have specified the service name used in the tnsnames.ora file to
> connect Oracle clients to the rdbms.
The database home ($ORACLE_HOME) is the directoy where the Oracle software
was installed on the RIM host (the RIM host client is used to connect to the
instance). This env. variable is set during the software install and does
not depend on whether it is only a client or a server or both - there is
always this variable. Surely, it need not be the same as the server
$ORACLE_HOME if the RIM host is not the server box.
Server ID ($TWO_TASK) is the name of the listener service on the server. You
will find this name in $ORACLE_HOME/network/admin/tnsnames.ora on the RIM
host and on the server box (it *must* be there). Usually, the name contains
the domain "world", e.g. frodo.world (you must use domain when the RIM host
sits on AIX). Check the files for the name.
>
>
> Finally, when we attempt to connect using nvColTabl, amongst the errors
> is these lines:
>
> > Could not open database
> >
> > Unable to open database with DB type = RIM, login ID = , Server name =
> > netview@jupiter.
>
> I have trouble correlating the information in the error message with
> that from wgetrim output above and I'm perplexed that the login ID
> appears to be NULL.
>
> I'm getting the feeling our error is easily corrected, but I can't see
> what I need to do differently. Any help would be very much appreciated.
Now, I would try to successfully connect through the client from the RIM
host or through wrimtest. For the former, set the env. variables mentioned
above and run a session for your RIM user.
HTH,
Best regards,
Vladimir.
>
>
> -John
>
> --
> ---------------------------------+--------------------------------------
> John Grover | Operations Manager,
> UNET, Technology Services | Senior Technical Support Specialist
> University of Maine System | JGrover@Maine.edu
> Computing Center | phone: (207) 581-3510
> Orono, ME 04469 | fax: (207) 581-3531
======================================================================
This email message has been swept by MIMEsweeper.
|