Hi Jee,

you are correct - the index backup is actually a process running on the NW 
server after the client data backup, but only for server-initiated backups. 
What i kept in mind was that if the problem appears, it is obviously happening 
at the transition phase from the data backup to the index backup or in other 
words: when the client backup has finished and it returns control to the NW 
server to take over.

If you run a manual (client-initiated) backup (for example, a cron-based 
backup) there is no index backup in the end. Consequently, there is no 
transition and the problem will just be prevented. 

Yes, in fact, NW media index = NW media database. Old NW terminology - sorry.

I agree that EMC could often produce more informative messages but an ORA 
message is actually not generated by NW.

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER