ORA-27193: sbtinfo2 did not return volume label

Cause : sbtinfo2 did not return the volume label information for the backup file that was just created.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

This is an internal error in the media management product. Contact the media management vendor.

update : 27-04-2017
ORA-27193

ORA-27193 - sbtinfo2 did not return volume label
ORA-27193 - sbtinfo2 did not return volume label

  • ora-25327 : Array size is invalid
  • ora-00373 : online log version string incompatible with ORACLE version string
  • ora-25270 : sender info does not match with the actual sender of the message
  • ora-14262 : new subpartition name must differ from the old subpartition name
  • ora-16650 : command incompatible when Fast-Start Failover is enabled
  • ora-02156 : invalid TEMPORARY tablespace identifier
  • ora-01641 : tablespace 'string' is not online - cannot add data file
  • ora-01152 : file string was not restored from a sufficiently old backup
  • ora-07265 : sppst: semop error, unable to increment semaphore.
  • ora-13709 : Required parameter "string" must be set before execution.
  • ora-30044 : 'Retention' can only specified for undo tablespace
  • ora-36835 : (XSLMGEN05) Dimension string.string!string hierarchy string level string is missing a COLUMNNAME property value
  • ora-31015 : Attempted to insert entry without name
  • ora-14154 : only one of STORE IN or clause may be specified
  • ora-16628 : the broker protection mode is inconsistent with the database setting
  • ora-01180 : can not create datafile 1
  • ora-33454 : (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.
  • ora-40285 : label not in the model
  • ora-30459 : 'string.string' cannot be refreshed because the refresh method is NONE
  • ora-09711 : orasrv: archmon already connected.
  • ora-13142 : invalid PROXIMITY window definition
  • ora-06525 : Length Mismatch for CHAR or RAW data
  • ora-02171 : invalid value for MAXLOGHISTORY
  • ora-02185 : a token other than WORK follows COMMIT
  • ora-01658 : unable to create INITIAL extent for segment in tablespace string
  • ora-30493 : The percentile value should be a number between 0 and 1.
  • ora-12802 : parallel query server lost contact with coordinator
  • ora-16531 : unable to post message
  • ora-12622 : TNS:event notifications are not homogeneous
  • ora-04094 : table string.string is constraining, trigger may not modify it
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.