ORA-27205: skgfpcn: sbtpccancel returned error

Cause : sbtpccancel returned an error. This happens during a proxy restore.

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 : 28-04-2017
ORA-27205

ORA-27205 - skgfpcn: sbtpccancel returned error
ORA-27205 - skgfpcn: sbtpccancel returned error

  • ora-25444 : invalid ROWID: string for table alias: string
  • ora-14618 : cannot drop the last value of subpartition
  • ora-01917 : user or role 'string' does not exist
  • ora-24776 : cannot start a new transaction
  • ora-19229 : XP0009 - schema import not supported
  • ora-32059 : deadlock detected on mapping structures
  • ora-12083 : must use DROP MATERIALIZED VIEW to drop "string"."string"
  • ora-25314 : a commit-time queue table cannot be migrated to 8.0
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • ora-30345 : circular dimension hierarchy
  • ora-30749 : column string not enabled to store objects of type string.string
  • ora-19700 : device type exceeds maximum length of string
  • ora-06518 : PL/SQL: Probe version string incompatible with version string
  • ora-16533 : inconsistent Data Guard broker state
  • ora-16783 : instance string not open for read and write access
  • ora-16095 : Dependent destination removal for inactivation
  • ora-19038 : Invalid opertions on query context
  • ora-26687 : no instantiation SCN provided for "string"."string" in source database "string"
  • ora-19200 : Invalid column specification
  • ora-13116 : [string]_FACE$ table does not exist
  • ora-31440 : change set string is empty and cannot be advanced
  • ora-30489 : Cannot have more than one rollup/cube expression list
  • ora-13386 : commit/rollback operation error: [string]
  • ora-19204 : Non-scalar value 'string' is marked as XML attribute
  • ora-02215 : duplicate tablespace name clause
  • ora-30060 : Internal event for RECO tracing
  • ora-15080 : synchronous I/O operation to a disk failed
  • ora-12720 : operation requires database is in EXCLUSIVE mode
  • ora-38504 : this operator not allowed with the configured attribute set
  • ora-36833 : (XSLMGEN03) View token cannot be blank
  • 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.