ORA-27030: skgfwrt: sbtwrite2 returned error

Cause : sbtwrite2 returned an error. This happens while writing a backup file during a backup operation.

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 : 23-04-2017
ORA-27030

ORA-27030 - skgfwrt: sbtwrite2 returned error
ORA-27030 - skgfwrt: sbtwrite2 returned error

  • ora-06042 : NETDNT: message receive failure
  • ora-22863 : synonym for datatype string.string not allowed
  • ora-24780 : cannot recover a transaction while in an existing transaction
  • ora-13364 : layer dimensionality does not match geometry dimensions
  • ora-28579 : network error during callback from external procedure agent
  • ora-35019 : (QFCHECK07) The Analytic Workspace and EIF file definitions of workspace object have different partition dimensions.
  • ora-02228 : duplicate SIZE specification
  • ora-22605 : FDO handle [string] is not initialized
  • ora-28654 : table and partition not overflow compatible
  • ora-36260 : (XSAGHIERPART00) Aggregating from partition %J to partition %J over hierarchy workspace object creates an increase in sparsity.
  • ora-09708 : soacon: failed to bind socket to port.
  • ora-27366 : job "string.string" is not running
  • ora-19034 : Type not supported during schema generation
  • ora-28334 : column is already encrypted
  • ora-06954 : Illegal file name
  • ora-32643 : invalid use of window function in MODEL rule
  • ora-25226 : dequeue failed, queue string.string is not enabled for dequeue
  • ora-16566 : unsupported document type
  • ora-07704 : error in archive text: need ':' after device name
  • ora-27211 : Failed to load Media Management Library
  • ora-26048 : Scoped REF column has wrong table name.
  • ora-03276 : duplicate ALLOCATE EXTENT option specification
  • ora-23600 : cannot create PROPAGATION, string already exists
  • ora-31010 : XML element index string exceeds maximum insertion index string
  • ora-30183 : invalid field width specifier
  • ora-04010 : the number of values to CACHE must be greater than 1
  • ora-30500 : database open triggers and server error triggers cannot have BEFORE type
  • ora-31608 : specified object of type string not found
  • ora-14631 : the partition bounds do not match the subpartition bounds of the partition
  • ora-12609 : TNS: Receive timeout occurred
  • 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.