Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Change DBSNMP password 1

Status
Not open for further replies.

williey

Technical User
Jan 21, 2004
242
I had just changed the DBSNMP password and the snmp_rw.ora is updated. But I still get the NMS-00205 error message in the dbsnmp.log file.

This is on Oracle 9i. Any ideas?

------------------------------------------
There are 10 kinds of people in this world. One that understands binary and the other one that does not.
 
Checking Metalink, I see that there is a known bug in which this error can happen if you change the dbsnmp password to something that is exactly eight characters long. If that's your situation, I suggest you try changing the password again, this time using a slightly longer or shorter password.

This bug is supposed to be fixed in the 9.2.0.8 patch set, so another alternative is to install the patch set, assuming it's available for your platform.
 
I had change 6 instances and not all of them are 8 characters long. Does the password in the snmp_rw.ora file needs to be encrpyted? I entered clear text in the file. Secondly, we did not renew the Oracle license. I do not have access to Metalink anymore. Changing the password back to default is not possible due to audit.


Code:
SNMP.CONNECT.TEST.NAME = "dbsnmp"
SNMP.CONNECT.TEST.PASSWORD = "*****"

------------------------------------------
There are 10 kinds of people in this world. One that understands binary and the other one that does not.
 
If those snmp.connect entries are exactly the same as in your snmp_rw.ora file, you probably are just experiencing the finicky syntax requirements of the entries in this file. You should remove the spaces on either side of the equal sign. Also, (at least on some platforms), the "snmp.connect.{SID}.password" has to be in lower case, not upper case as you have it. Finally the SID, which you have as "TEST", needs to exactly match the corresponding entry in the "snmp.visibleservices" line in snmp_ro.ora.

If you get things set up right in snmp_rw.ora, the password should automatically get encrypted when you change it on the database. You should see a line in snmp_rw.ora that looks similar to

snmp.connect.{SID}.encryptedpassword="xxxx"

Make sure you shut down the agent before making these changes. I doubt that the agent could gracefully handle a password change if it's up and running at the time.
 
Got it to work now. Removing the spaces before and after the "=" and using lower case fixed the problem.

I thought following the example in the snmp_rw.ora file is the safe way to got. I guess not. Thanks for your help!


------------------------------------------
There are 10 kinds of people in this world. One that understands binary and the other one that does not.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top