Hello friends,
I need help, because the Oracle 12.1.0.2.0 can not do an RMAN backup anymore. This came suddenly during productive operation. A day before it worked without any problems. Here is the total error description:
Recovery Manager: Release 12.1.0.2.0 - Production on Tue Jan 31 09:09:33 2017
Copyright (c) 1982, 2016, Oracle and/or its affiliates. All rights reserved.
RMAN>
RMAN> connect target *
connected to target database: P02 (DBID=2018208075)
using target database control file instead of recovery catalog
RMAN> **end-of-file**
RMAN>
host command complete
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11>
allocated channel: sbt_1
channel sbt_1: SID=1374 device type=SBT_TAPE
channel sbt_1: Veritas NetBackup for Oracle - Release 7.7.3 (44)
allocated channel: sbt_2
channel sbt_2: SID=1057 device type=SBT_TAPE
channel sbt_2: Veritas NetBackup for Oracle - Release 7.7.3 (44)
allocated channel: sbt_3
channel sbt_3: SID=1846 device type=SBT_TAPE
channel sbt_3: Veritas NetBackup for Oracle - Release 7.7.3 (44)
Starting backup at 2017-01-31 09:10:02
channel sbt_1: starting archived log backup set
channel sbt_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=20368 RECID=19449 STAMP=934668055
channel sbt_1: starting piece 1 at 2017-01-31 09:10:03
channel sbt_2: starting archived log backup set
channel sbt_2: specifying archived log(s) in backup set
input archived log thread=1 sequence=20366 RECID=19447 STAMP=934666116
channel sbt_2: starting piece 1 at 2017-01-31 09:10:03
channel sbt_3: starting archived log backup set
channel sbt_3: specifying archived log(s) in backup set
input archived log thread=1 sequence=20361 RECID=19442 STAMP=934662469
channel sbt_3: starting piece 1 at 2017-01-31 09:10:03
RMAN-03009: failure of backup command on sbt_1 channel at 01/31/2017 09:10:10
ORA-19506: failed to create sequential file, name="P02_aevbmpfl.20928_1", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: non RMAN, but media manager or vendor specific failure, error text:
VxBSAValidateFeatureId: Failed with error:
Server Status: cannot connect on socket
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 01/31/2017 09:10:17
ORA-19506: failed to create sequential file, name="P02_aevbmpfl.20929_1", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: non RMAN, but media manager or vendor specific failure, error text:
VxBSAValidateFeatureId: Failed with error:
Server Status: cannot connect on socket
channel sbt_2 disabled, job failed on it will be run on another channel
released channel: sbt_1
released channel: sbt_2
released channel: sbt_3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on sbt_3 channel at 01/31/2017 09:10:24
ORA-19506: failed to create sequential file, name="P02_aevbmpfl.20930_1", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: non RMAN, but media manager or vendor specific failure, error text:
VxBSAValidateFeatureId: Failed with error:
Server Status: cannot connect on socket
RMAN>
specification does not match any backup in the repository
RMAN>
Recovery Manager complete.
------------------------------------------------------------------------------------
Any idea?
Why is RMAN not able to get a socket anymore?
At the same time an "sqlplus / as sysdba" does not work anymore. Only DB connects with user+PW still work so the application is running.
We have the error since we upgrated to Oracle 12 last September. We have this phenomena about every 14 days. When we restart the DB, everything is normal again.
best regards,
Claudia Geissler