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-06-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-26668 : STREAMS process string exists
  • ora-01862 : the numeric value does not match the length of the format item
  • ora-35021 : (QFCHECK08) The EIF file definition of workspace object has some partitions that are not present in the existing Analytic Workspace object.
  • ora-04081 : trigger 'string' already exists
  • ora-00279 : change string generated at string needed for thread string
  • ora-00079 : variable string not found
  • ora-30341 : dropped level has references
  • ora-14020 : this physical attribute may not be specified for a table partition
  • ora-39600 : Queue keys needs to be a suffix of cluster key.
  • ora-00264 : no recovery required
  • ora-26696 : no streams data dictionary for object with number string and version number string from source database string
  • ora-25000 : invalid use of bind variable in trigger WHEN clause
  • ora-13918 : Updating system alert with reason_id string failed; previous alert not found
  • ora-26724 : only SYS is allowed to set the Capture or Apply user to SYS.
  • ora-32409 : materialized view log on "string"."string" already excludes new values
  • ora-14070 : option may be specified only for partitioned indices or with REBUILD
  • ora-36181 : A VARIABLE cannot have both the $AGGREGATE_FROM and $AGGREGATE_FROMVAR properties applied to it.
  • ora-02879 : sou2o: Could not gain access to protected memory
  • ora-25275 : Test support for buffered queues
  • ora-06736 : TLI Driver: server not running
  • ora-29365 : parameters string and string cannot both be set
  • ora-30046 : Undo tablespace string not found in control file.
  • ora-16747 : logical standby database guard could not be turned on
  • ora-13197 : element string.string.string is out of range
  • ora-16058 : standby database instance is not mounted
  • ora-32307 : must use FROM ONLY clause when referencing an object table
  • ora-01043 : user side memory corruption [string], [string], [string], [string]
  • ora-29835 : ODCIGETINTERFACES routine does not return required interface(s)
  • ora-06430 : ssaio: Seals do not match
  • ora-26725 : cannot downgrade apply handlers
  • 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.