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 : 25-06-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-01505 : error in adding log files
  • ora-28221 : REPLACE not specified
  • ora-13048 : recursive SQL fetch error
  • ora-24335 : cannot support more than 1000 columns
  • ora-01781 : UNRECOVERABLE cannot be specified without AS SELECT
  • ora-31006 : Path name segment length string exceeds maximum length string
  • ora-01309 : invalid session
  • ora-26527 : local store callback init phase failed for 'string.string'
  • ora-22600 : encountered 8.0.2 (Beta) VARRAY data that cannot be processed
  • ora-39168 : Object path string was not found.
  • ora-30646 : schema for external table type must be SYS
  • ora-32036 : unsupported case for inlining of query name in WITH clause
  • ora-01264 : Unable to create string file name
  • ora-04069 : cannot drop or replace a library with table dependents
  • ora-06449 : The list IO or the sysvendor is not installed.
  • ora-25470 : duplicate attribute value for variable: string
  • ora-39311 : call to DBMS_SCHEMA_COPY.CLONE_RECOVERY is not legal
  • ora-09801 : Unable to get user ID from connection
  • ora-07607 : szaud: $SNDOPR failure
  • ora-21522 : attempted to use an invalid connection in OCI (object mode only)
  • ora-31094 : incompatible SQL type "string" for attribute or element "string"
  • ora-38906 : insert into DML Error Logging table "string" failed
  • ora-36904 : (XSAGDNGL44) In AGGMAP workspace object, RELATION workspace object occurs after a dynamic model. The dynamic model must be the last calculation within the AGGMAP.
  • ora-07494 : scgcm: unexpected error.
  • ora-09926 : Unable to set effective privilege set of the server
  • ora-16403 : shutdown in progress - remote connection is not permitted
  • ora-15010 : name is already used by an existing ASM disk
  • ora-32831 : timed out trying to acquire administration lock
  • ora-28043 : invalid bind credentials for DB-OID connection
  • ora-07454 : queue timeout, string second(s), exceeded
  • 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.