ORA-19870: error reading backup piece string

Cause : This error should be followed by other errors indicating the cause of the problem.

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

See other errors actions. Do not use message 19871; it is used by RMAN client for testing previous resync time when using backup/standby control file.

update : 25-09-2017

ORA-19870 - error reading backup piece string
ORA-19870 - error reading backup piece string

  • ora-30386 : invalid SQL statement for DECLARE_REWRITE_EQUIVALENCE
  • ora-12031 : cannot use primary key columns from materialized view log on "string"."string"
  • ora-34489 : (MXMAINT06) You cannot maintain workspace object because it is a SURROGATE.
  • ora-31228 : DBMS_LDAP: invalid MOD_ARRAY
  • ora-01920 : user name 'string' conflicts with another user or role name
  • ora-28110 : policy function or package string.string has error
  • ora-26010 : Column string in table string is NOT NULL and is not being loaded
  • ora-30506 : system triggers cannot be based on tables or views
  • ora-28267 : Invalid NameSpace Value
  • ora-12636 : Packet send failed
  • ora-13778 : no new name or owner specified for "SQL Tuning Set"
  • ora-29879 : cannot create multiple domain indexes on a column list using same indextype
  • ora-36850 : (XSLMGEN20) View token string is not correct
  • ora-07441 : function address must be aligned on string byte boundary
  • ora-01106 : database must be closed before dismounting
  • ora-26711 : remote table does not contain a primary key constraint
  • ora-25462 : evaluation context not specified
  • ora-27034 : maximum length of ORACLE_SID exceeded
  • ora-01882 : timezone region string not found
  • ora-10640 : Operation not permitted during SYSTEM tablespace migration
  • ora-02831 : Segment deallocation failed - empty segment list
  • ora-16759 : resource guard unable to start SQL Apply with initial SCN
  • ora-14052 : partition-extended table name syntax is disallowed in this context
  • ora-06781 : TLI Driver: error reading negotation string
  • ora-31011 : XML parsing failed
  • ora-19637 : backupPieceCreate requires file name when using DISK device
  • ora-40262 : NMF: number of features not between [1, string]
  • ora-16023 : system string destination cannot be the same as session string destination
  • ora-13436 : GeoRaster metadata dimensionSize error
  • ora-02159 : installed DLM does not support releasable locking mode
  • 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.