ORA-01695: error converting rollback segment string to version 8.0.2

Cause : Version8 .0.1 daatbase ma ynot hav eshutdow ncleanly

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

May hav eto reloda the 8..01 databsae and suhtdown celanly

update : 23-08-2017
ORA-01695

ORA-01695 - error converting rollback segment string to version 8.0.2
ORA-01695 - error converting rollback segment string to version 8.0.2

  • ora-16170 : Terminal recovery may have left the database in an inconsistent state
  • ora-01694 : max # extents (string) reached in lob segment string.string partition string
  • ora-38725 : specified name "string" does not match actual "string"
  • ora-30396 : rewrite equivalence procedures require the COMPATIBLE parameter to be string or greater
  • ora-38907 : DML error logging is not supported for FILE column "string"
  • ora-30946 : XML Schema Evolution warning: temporary tables not cleaned up
  • ora-38950 : Source platform string not cross platform compliant
  • ora-39502 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-04004 : MINVALUE must be less than MAXVALUE
  • ora-38905 : DML error logging is not supported for LONG column "string"
  • ora-22851 : invalid CHUNK LOB storage option value
  • ora-24271 : translation type must be either T, S or M
  • ora-00203 : using the wrong control files
  • ora-07613 : $GETJPIW failed in retrieving the user's process label
  • ora-06814 : TLI Driver: the SPX device file could not be opened
  • ora-25351 : transaction is currently in use
  • ora-14004 : missing PARTITION keyword
  • ora-00041 : active time limit exceeded - session terminated
  • ora-24354 : number fetched too large to fit in COBOL display type buffer.
  • ora-06736 : TLI Driver: server not running
  • ora-23440 : incorrect public template value
  • ora-29293 : A stream error occurred during compression or uncompression.
  • ora-16226 : DDL skipped due to lack of support
  • ora-16233 : The table string.string is unsupported now
  • ora-01038 : cannot write database file version string with ORACLE version string
  • ora-19729 : File string is not the initial version of the plugged in datafile
  • ora-07585 : spdcr: $PARSE failure
  • ora-00042 : Unknown Service name string
  • ora-38622 : Decision Tree not enough memory, requires at least stringKB
  • ora-13630 : The task string contains execution results and cannot be executed.
  • 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.