ORA-10640: Operation not permitted during SYSTEM tablespace migration

Cause : SYSTEM tablespace is being migrated to locally managed format.

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

Reissue this command once SYSTEM tablespace migration is over.

update : 17-08-2017
ORA-10640

ORA-10640 - Operation not permitted during SYSTEM tablespace migration
ORA-10640 - Operation not permitted during SYSTEM tablespace migration

  • ora-28045 : SSL authentication between database and OID failed
  • ora-09261 : spdcr: error creating detached (background) process
  • ora-02843 : Invalid value for kernel flag
  • ora-09948 : Process information label retrieval failed.
  • ora-00469 : CKPT process terminated with error
  • ora-09281 : sllfop: error opening file
  • ora-38425 : attribute set used for an index object may not be unassigned
  • ora-07710 : sksaprs: file name buffer too small
  • ora-25461 : rule set not specified
  • ora-13334 : LRS segments not connected
  • ora-33448 : (ESDREAD04) Discarding compiled code for workspace object because number now has string data, whereas it had string data when the code was compiled.
  • ora-06707 : TLI Driver: connection failed
  • ora-23419 : regenerate replication support before resuming master activity
  • ora-14161 : subpartition number string: sum of PCTUSED and PCTFREE may not exceed 100
  • ora-19905 : log_archive_format must contain %%s, %%t and %%r
  • ora-33030 : (XSAGDNGL14) In AGGMAP workspace object, you can have either a single independent PROTECT statement or PROTECT statements in your RELATION statements.
  • ora-31687 : error creating worker process string with worker id string
  • ora-29957 : cannot create a function-based domain index on a string table
  • ora-21708 : inappropriate operation on a transient object
  • ora-30726 : cannot specify referenced column list here
  • ora-27088 : unable to get file status
  • ora-19806 : cannot make duplex backups in recovery area
  • ora-13458 : GeoRaster metadata SRS error
  • ora-16402 : ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support
  • ora-16512 : parameter exceeded maximum size limit
  • ora-29556 : object type has changed
  • ora-06029 : NETASY: port assignment failure
  • ora-15192 : invalid ASM disk header [string] [string] [string] [string] [string]
  • ora-13406 : null or invalid GeoRaster object for output
  • ora-32821 : subscriber queue and exception queue must have same payload type
  • 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.