Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Problems with Oracle NT

Problems with Oracle NT

From: Todd Storch <todd.storch_at_wang.com>
Date: 1997/03/03
Message-ID: <01bc2828$44f28a80$100f7c96@tgs75984>#1/1

I just finished configuring Oracle Server 7.3.2.2 on NT Server 4.0 Service Pack 1 with Oracle Names Server. Here are some of the problems I had. Please let me know if you have any solutions or if you have had the same problem(s).

-The account dbsnmp and associated data objects are created with the script
CATSNMP.SQL.. The account is created with the password dbsnmp. Oracle support says that the password must be remain as dbsnmp or must be hard coded in the snmp.ora file. This seems to be a security problem. Oracle support also claims that this account must be in the system tablespace otherwise the agent will lock up.

-When using network manager to create the the topology.ora file the node
names are created with a domain attached. The file must be edited to remove the domain names. I found this out from the oracle support notice 2064129.4

-The lsnrctl dbsnmp_start, dbsnmp_stop, and dbsnmp_status have no
significance with NT.

-When the agent is installed with oracle names the client requires the
tnsnames.ora file to find the address of the agent. If the tnsnames.ora file does not exist then the client daemon can not communicate with the agent.

-When the topology file is created with network manager the names server is
not added to the file. This prevents enterprise manager from seeing the names server. The names server can be added manually or with the topology editor utility.

-When using enterprise manager do not press the advanced button from the
export screen. A fatal VOC.EXE error occurs. This only happen when creating a job. The export advanced dialog screen works fine when using the Data Manager.

-When creating the names database with network manager the names server
password entry writes junk data to the password even when left blank. This forces the namesctl program to require a password when stopping the names server. To work around this problem use a password instead of leaving it blank. Then uses the SET PASSWORD password in the namesctl utility.

Todd Storch
Wang HealthCare
todd.storch_at_wang.com Received on Mon Mar 03 1997 - 00:00:00 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US