ORA-10647: Tablespace other than SYSTEM, string, string not found in read only mode

Cause : WehnS YTSE Mtbalsepcaei sb enigm irgaetd ,tbalsepcae sohte rtahnt h etrhe esohudl eb LATREe dt oraedo nyl.

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

Atle rteh atbelsapc esattsu ot era dolnya n drter ymgirtaino.

update : 28-04-2017

ORA-10647 - Tablespace other than SYSTEM, string, string not found in read only mode
ORA-10647 - Tablespace other than SYSTEM, string, string not found in read only mode

  • ora-02223 : invalid OPTIMAL storage option value
  • ora-12701 : CREATE DATABASE character set is not known
  • ora-36270 : (XSCGMDLAGG03) The parameter list for the AGGREGATION function includes duplicate values.
  • ora-31083 : error while creating SQL type "string"."string"
  • ora-16040 : standby destination archive log file is locked
  • ora-30956 : invalid option for XML Index
  • ora-01353 : existing Logminer session
  • ora-38602 : FI invalid input cursor
  • ora-01652 : unable to extend temp segment by string in tablespace string
  • ora-19666 : cannot do incremental restore of the control file
  • ora-24374 : define not done before fetch or execute and fetch
  • ora-13029 : Invalid SRID in the SDO_GEOMETRY object
  • ora-01881 : timezone region id number is invalid
  • ora-26723 : user "string" requires the role "string"
  • ora-10583 : Can not recovery file string renamed as missing during test recovery
  • ora-16582 : could not edit instance specific property
  • ora-28104 : input value for string is not valid
  • ora-30678 : too many open connections
  • ora-19372 : invalid update condition
  • ora-02281 : duplicate or conflicting CACHE/NOCACHE specifications
  • ora-36179 : (XSNOAGM) No AGGMAP was specified for VARIABLE workspace object.
  • ora-07845 : sllfcl: LIB$FREE_VM failue
  • ora-31513 : unsupported column type specified in change table
  • ora-25143 : default storage clause is not compatible with allocation policy
  • ora-16087 : graceful switchover requires standby or current control file
  • ora-14025 : PARTITION may not be specified for a materialized view or a materialized view log
  • ora-13190 : recursive SQL fetch failed
  • ora-08323 : scnmin: close of bias lock failed
  • ora-01194 : file string needs more recovery to be consistent
  • ora-26736 : Data Pump error
  • 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.