ORA-27191: sbtinfo2 returned error

Cause : sbtinfo2 returned an error. This happens while retrieving backup file information from the media manager's catalog.

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

This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

update : 27-04-2017

ORA-27191 - sbtinfo2 returned error
ORA-27191 - sbtinfo2 returned error

  • ora-32583 : query passed to table function has wrong number of elements in select list
  • ora-32822 : subscriber string is marked for removal
  • ora-09317 : szprv: insufficient privileges
  • ora-00081 : address range [string, string) is not readable
  • ora-24393 : invalid mode for creating connection pool
  • ora-07256 : sptrap: cannot set up signal handler to catch exceptions.
  • ora-16133 : Datafile string has incorrect terminal recovery stamp.
  • ora-01168 : physical block size string does not match size string of other members
  • ora-38466 : user does not have privileges to CREATE/MODIFY expressions
  • ora-12025 : materialized view log on "string"."string" already has primary keys
  • ora-01564 : rollback segment is not PUBLIC
  • ora-32121 : Source FILE is null
  • ora-10706 : Print out information about global enqueue manipulation
  • ora-30017 : segment 'string' is not supported in string Undo Management mode
  • ora-01911 : CONTENTS keyword expected
  • ora-28358 : improper set key syntax
  • ora-33005 : (XSAGDIMBREAK) Invalid breakout for dimension workspace object.
  • ora-12687 : Credentials expired.
  • ora-01938 : IDENTIFIED BY must be specified for CREATE USER
  • ora-19603 : cannot backup or copy active file with KEEP .. UNRECOVERABLE option
  • ora-38746 : error occurred while restoring data block (file# string, block# string)
  • ora-16644 : apply instance not available
  • ora-13291 : conversion error between the specified unit and standard unit
  • ora-16220 : no failed transaction found
  • ora-12556 : TNS:no caller
  • ora-00369 : Current log of thread string not useable and other log being cleared
  • ora-30930 : NOCYCLE keyword is required with CONNECT_BY_ISCYCLE pseudocolumn
  • ora-28006 : conflicting values for parameters string and string
  • ora-01613 : instance string (thread string) only has string logs - at least 2 logs required to enable.
  • ora-28338 : cannot encrypt indexed column(s) with salt
  • 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.