Home » RDBMS Server » Enterprise Manager » suddenly get VNI-2015 problems under LINUX
suddenly get VNI-2015 problems under LINUX [message #215440] Mon, 22 January 2007 05:25 Go to next message
wgkott
Messages: 2
Registered: January 2007
Junior Member
Hello,

I run a OMS 9.2.06 on SUSE SLES Linux 9.3 to managing several
nodes. Version of the operating system and database are the same of all client nodes.
Job-scheduling works fine for more than fifteen month.
I'm able to add new, delete, or copy jobs. Every thing works fine.

Then one node (with two instances) run unsynchronously and the scheduled jobs planned in the past instead of future.
I delete all Jobs of this node. If I would transfer new jobs to this node I suddenly get the VNI-2015 error.

actual status/actions...
- preferred credentials are correct.
- I use user root for this node
- permission of ORACLE_HOME/bin/dbsnmp are set -rwsr-s--x root dba dbsnmp
- I restarted database, listener, agent several times
- I delete the service.ora, *.q, *.inp, *.jou-Files, bsnmp.ver,snmp_ro.ora,snmp_rw.ora, dbsnmp.log ,dbsnmp.nohup, nmiconf.log
- there are no Jobs in the DBA_JOBS-View of both instances
- DNS works fine (map and reverse map)
- OMS is able to discover the node
- the agent is pingable
- no firewall on all systems (Ports open 7771 -7776 on OMS)
- no changes made

Please help.

best regards
Thorsten
Re: suddenly get VNI-2015 problems under LINUX [message #215497 is a reply to message #215440] Mon, 22 January 2007 09:53 Go to previous messageGo to next message
tahpush
Messages: 961
Registered: August 2006
Location: Stockholm/Sweden
Senior Member

Have you looked at metalink note 2062600.102 ?

ls -al dbsnmp

[Updated on: Mon, 22 January 2007 09:53]

Report message to a moderator

Re: suddenly get VNI-2015 problems under LINUX [message #215595 is a reply to message #215497] Tue, 23 January 2007 01:00 Go to previous message
wgkott
Messages: 2
Registered: January 2007
Junior Member
Yes I read it.
The s-bit is set by root.
But this is exactly my problem. It worked for a long time and
suddenly fail without any changes on the node.
Are there other possibilities to specify what goes wrong?
Like getting trace files, logging the certification?

br
Thorsten
Previous Topic: Where is oem on a solaris box?
Next Topic: Enterprise Manager 9i for Sun Solaris
Goto Forum:
  


Current Time: Thu Dec 08 12:38:50 CST 2016

Total time taken to generate the page: 0.14406 seconds