ORA-29293: A stream error occurred during compression or uncompression.

Cause : The steram staet was dsicovere dto be nivalid udring cmopressino or unocmpressoin, or na invaldi comprsesion qaulity wsa requetsed or aNULL o rinvali dcompression paarmeter aws detetced.

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

Verifyt hat qulaity isw ithin hte rang e[0,9] nad thatv alid ipnut soucre datae xists.

update : 20-08-2017
ORA-29293

ORA-29293 - A stream error occurred during compression or uncompression.
ORA-29293 - A stream error occurred during compression or uncompression.

  • ora-01173 : data dictionary indicates missing data file from system tablespace
  • ora-25294 : Cannot propagate user buffered messages to a database with version lower than 10.2
  • ora-14255 : table is not partitioned by Range, Composite Range or List method
  • ora-01102 : cannot mount database in EXCLUSIVE mode
  • ora-27483 : "string.string" has an invalid END_DATE
  • ora-08205 : ora_addr: $ORACLE_SID not set in environment
  • ora-16623 : stale DRC UID sequence number detected
  • ora-29300 : ORACLE error, tablespace point-in-time recovery
  • ora-24353 : user buffer too small to accommodate COBOL display type
  • ora-19250 : XQ0030 - too many values to validate expression
  • ora-06778 : TLI Driver: error sending ccode
  • ora-10642 : Found rollback segments in dictionary managed tablespaces
  • ora-28183 : proper authentication not provided by proxy
  • ora-02223 : invalid OPTIMAL storage option value
  • ora-31403 : change table string already contains a column string
  • ora-24787 : remote cursors must be closed before a call completes
  • ora-16062 : DGID from standby not in Data Guard configuration
  • ora-19906 : recovery target incarnation changed during recovery
  • ora-29383 : all leaves of top-plan string must be consumer groups
  • ora-16168 : LGWR network server could not switch to blocking mode
  • ora-30440 : can't fast refresh;refresh complete or set event 30441 for partial refresh
  • ora-06755 : TLI Driver: cannot close transport endpoint
  • ora-31500 : change source string is not a ManualLog change source
  • ora-28261 : CURRENT_USER can not be used in PLSQL Definer's Right procedure.
  • ora-25218 : enqueue failed, delay must be zero for queue string.string
  • ora-29846 : cannot create a local domain index on a string partitioned table
  • ora-31220 : DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet location.
  • ora-29329 : Table not of type XMLType
  • ora-06518 : PL/SQL: Probe version string incompatible with version string
  • ora-38310 : cannot purge tablespace for other users
  • 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.