Don't know if this will help. But, it looks like an RMAN error. Here is some information I was able to find.
Additional information: 7012 -- Indicates Invalid argument(s) to sbtopen 962 indicates a Command-line interpreter error. But, I don't see any explanation for the error. https://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmtroub.htm#BRADV89877 [image: OCIO-logo-Transparent.png] <https://ocio.iowa.gov/> Lynn Hall Information Technology Specialist IV Platform Services Office of the Chief Information Officer 200 E Grand Ave | Des Moines, IA 50309 - Mailing mobile 515-669-4325 ocio.iowa.gov [image: social media icons_Twitter cir.png] <https://twitter.com/IowaOCIO>[image: social media icons_LinkedIn cir.png] <https://www.linkedin.com/company/state-of-iowa> On Thu, Dec 17, 2020 at 10:09 AM Loon, Eric van (ITOP NS) - KLM < eric-van.l...@klm.com> wrote: > Hi guys, > > I'm having a real issue on one of our SAP servers. We upgraded the TDP for > SAP (Oracle) client from 7.1.3 to 8.1.11 along with the API client (from > 7.1.8 to 8.1.11). Now when we start a full backup, it fails with the > following error in the log: > > RMAN-03009: failure of backup command on sbt_1 channel at 12/17/2020 > 16:58:37 > ORA-19506: failed to create sequential file, name="P11_bffjgyso.142533_1", > parms="" > ORA-27007: failed to open file > Additional information: 7012 > Additional information: 962 > ORA-19511: non RMAN, but media manager or vendor specific failure, error > text: > SBT error = 7012, errno = 0, sbtopen: internal error - invalid > argument(s) > channel sbt_1 disabled, job failed on it will be run on another channel > RMAN-03009: failure of backup command on sbt_2 channel at 12/17/2020 > 16:58:37 > ORA-19506: failed to create sequential file, name="P11_bffjgyso.142534_1", > parms="" > ORA-27007: failed to open file > Additional information: 7012 > Additional information: 962 > > I opened a PMR at IBM and they asked me to enable tracing for both the API > and the TDP client, but both trace files are not created during a backup > attempt, so my guess is that the error occurs before the TDP client is even > used. > I tried everything, like reinstalling the 7.1.3 TDP client, switching back > to the old server, nothing helps and the SAP people are getting nervous > because of their archivelog space. Does anybody have any idea what else I > can try? > Thanks for any help in advance. > > Kind regards, > Eric van Loon > Air France/KLM Storage & Backup > ******************************************************** > For information, services and offers, please visit our web site: > http://www.klm.com. This e-mail and any attachment may contain > confidential and privileged material intended for the addressee only. If > you are not the addressee, you are notified that no part of the e-mail or > any attachment may be disclosed, copied or distributed, and that any other > action related to this e-mail or attachment is strictly prohibited, and may > be unlawful. If you have received this e-mail by error, please notify the > sender immediately by return e-mail, and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its > employees shall not be liable for the incorrect or incomplete transmission > of this e-mail or any attachments, nor responsible for any delay in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch > Airlines) is registered in Amstelveen, The Netherlands, with registered > number 33014286 > ******************************************************** >
