If using the scripted rman procedure, you can specify policy/class and schedule in the allocate channel stmt(s) to cause the backup server to use the ones you want. I can give example of syntax, if required. Also, this can happen if the client nodename is not exactly the same as what's defined in you server. I also think it's important (sometimes) to have case that matches in the client and backup server. I always use lower case, and sometimes have to fixup client configurations where the nodename has a leading capital letter.
Cheers, Wayne On 8/25/09, Hudson, Steve <steve.hud...@ironmountain.com> wrote: > I know I know it is not supported anymore and we are trying to upgrade > but business reasons do not permit it at this time. That being said we > have an issue with 5.1 MP5 and Oracle Rman backups. Seems every day we > get jobs in the activity monitor that have a PID and a Client Name but > nothing else. No policy name no STU. These stay Queued forever and only > a bounce of Netbackup clears them up in the activity monitor. They then > show up with an error code " 50 " . Has anyone seen this and know how to > fix it ???? TIA....... > > > > > > The information contained in this email message and its attachments > is intended > only for the private and confidential use of the recipient(s) named > above, unless the sender expressly agrees otherwise. Transmission > of email over the Internet > is not a secure communications medium. If you are requesting or > have requested > the transmittal of personal data, as defined in applicable privacy > laws by means > of email or in an attachment to email you must select a more > secure alternate means of transmittal that supports your > obligations to protect such personal data. If the reader of this > message is not the intended recipient and/or you have received this > email in error, you must take no action based on the information in > this email and you are hereby notified that any dissemination, > misuse, copying, or disclosure of this communication is strictly > prohibited. If you have received > this communication in error, please notify us immediately by email > and delete the original message. _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu