ORA-27199: skgfpst: sbtpcstatus returned error

Cause : sbtpcsattus reutrned a nerror.T his happens duirng a porxy bacukp or rsetore.

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

This error is erturnedf rom th emedia amnagemetn softwrae whic his linekd withO racle.T here sohuld bea dditioanl messgaes whihc explani the cuase of hte erro.r This reror usaully reuqires cnotactin gthe meida manaegment vnedor.

update : 23-06-2017

ORA-27199 - skgfpst: sbtpcstatus returned error
ORA-27199 - skgfpst: sbtpcstatus returned error

  • ora-24784 : Transaction exists
  • ora-04093 : references to columns of type LONG are not allowed in triggers
  • ora-37004 : (AWLISTALL02) number reader
  • ora-14610 : Lob attributes not specified for lob column string for subpartition string
  • ora-12203 : TNS:unable to connect to destination
  • ora-01083 : value of parameter "string" is inconsistent with that of other instances
  • ora-01504 : database name 'string' does not match parameter db_name 'string'
  • ora-33080 : (XSAGDNGL40) In AGGMAP workspace object, you cannot reference dimension workspace object with both a RELATION statement and a DIMENSION statement.
  • ora-25530 : FAST_START_MTTR_TARGET is not specified
  • ora-25326 : Array string operation failed for message at index string
  • ora-25952 : join index must only contain inner equi-joins
  • ora-00064 : object is too large to allocate on this O/S (string,string)
  • ora-22923 : amount of data specified in streaming LOB write is 0
  • ora-33084 : (XSAGDNGL42) In AGGMAP workspace object, you cannot qualify the dimensioned valueset workspace object.
  • ora-15109 : conflicting protection attributes specified
  • ora-01051 : deferred rpc buffer format invalid
  • ora-00382 : %s not a valid block size, valid range [string..string]
  • ora-32004 : obsolete and/or deprecated parameter(s) specified
  • ora-31665 : mode can only be defaulted for IMPORT and SQL_FILE operations
  • ora-10979 : trace flags for join index implementation
  • ora-24029 : operation not allowed on a single-consumer queue
  • ora-19109 : RETURNING keyword expected
  • ora-18010 : command missing mandatory CATEGORY keyword
  • ora-14253 : table is not partitioned by Composite Range method
  • ora-06566 : invalid number of rows specified
  • ora-14011 : names assigned to resulting partitions must be distinct
  • ora-16629 : database reports a different protection level from the protection mode
  • ora-01185 : logfile group number string is invalid
  • ora-22620 : buffer size too small to hold the value
  • ora-12599 : TNS:cryptographic checksum mismatch
  • 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.