We're running 6.5.1 and not having this issue.

Also FYI - Upgrade from 6.5.1 to 6.5.3 would not be as painful as the
one you just went through.   From 5.1 to 6.0 there was a major change in
the way things were done.   We upgraded from 6.0 to 6.5 with no real
issues.

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of smehta
Sent: Wednesday, January 07, 2009 12:09 PM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] nbu 6.5.1 lifecycle policy issue



David McMullin wrote:
> Regarding the error you are getting - you might want to open a trouble
ticket with Symantec. 
> 
> For the error: 
> "Caught CORBA SystemException from SSmgrOperations: system exception,
ID 'IDL:omg.org/CORBA/NO_PERMISSION:1.0' 
> OMG minor code (0), described as '*unknown description*', completed =
NO" 
> 
> <![if !supportLists]>1. <![endif]>There are several binary updates
available ( I have rev 6 of nbpem ) 
> <![if !supportLists]>2. <![endif]>Check your daemons (on unix)
nbstserv has a tendency to core dump/stop and cause these errors. 
> <![if !supportLists]>3. <![endif]>Be aware you can overload the
database! 
> 
> I had set up a script that would deactivate all my SLP: 
> for i in `/usr/openv/netbackup/bin/admincmd/nbstl -L | grep -i name |
cut -c38-` 
> do 
> echo "Now deactivating "$i 
> /usr/openv/netbackup/bin/admincmd/nbstlutil inactive -lifecycle $i 
> done 
> 
> and I found that you can overload the database with too many changes,
and cause this type issue as well. 
> 
> Hope one of these helps you! 
> 
> BTW - symantec has recommended to me that I should go to 6.5.3! 
> 
> "I put the nbpem rev 6 (ETRACK 1448343)on our ftp site for you. " 
> "The significant changes in here for your environment are timer
conflict corrections that can impact correct rescheduling of due dates
and recognition of schedule changes. We still urge you to upgrade to
6.5.3 as soon as possible, for several other SLP issues are resolved in
that release. "


Thanks for the update. I did open a call with Symantec and they came
back with the same solution. Upgrade to 6.5.3.  However, we just
completed the upgrade to 6.5.1. from 5.1 and have all the clients at
6.5.1. Upgrade was painful and so don't want to change to 6.5.3..

Might end up sticking with old vault.

+----------------------------------------------------------------------
|This was sent by s.mehta AT ieee DOT org via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential 
information and is for the sole use of the intended recipient(s). If you are 
not the intended recipient, any disclosure, copying, distribution, or use of 
the contents of this information is prohibited and may be unlawful. If you have 
received this electronic transmission in error, please reply immediately to the 
sender that you have received the message in error, and delete it. Thank you.
----------------------------------

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu