ORA-19732: incorrect number of datafiles for tablespace string

Cause : d by a user editing the export file.

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

Use the correct export file and retry the operation.

update : 25-04-2017
ORA-19732

ORA-19732 - incorrect number of datafiles for tablespace string
ORA-19732 - incorrect number of datafiles for tablespace string

  • ora-01631 : max # extents (string) reached in table string.string
  • ora-22923 : amount of data specified in streaming LOB write is 0
  • ora-15204 : database version string is incompatible with diskgroup string
  • ora-27468 : "string.string" is locked by another process
  • ora-12549 : TNS:operating system resource quota exceeded
  • ora-14606 : Tablespace was specified for previous subpartitions in template but is not specified for string
  • ora-28666 : option not allowed for an index on UROWID column(s)
  • ora-12492 : DBLOW cannot be changed
  • ora-25136 : this cluster can contain only one table
  • ora-23363 : mismatch of mview base table "string" at master and mview site
  • ora-02801 : Operations timed out
  • ora-24144 : rules engine internal error, arguments: [string], [string]
  • ora-16009 : remote archive log destination must be a STANDBY database
  • ora-24030 : Only one of rule or rule-set must be specified
  • ora-01145 : offline immediate disallowed unless media recovery enabled
  • ora-02153 : invalid VALUES password string
  • ora-30755 : error during expansion of view hierarchy
  • ora-00404 : Convert file not found: 'string'
  • ora-39071 : Value for string is badly formed.
  • ora-27214 : skgfrsfe: file search failed
  • ora-01233 : file string is read only - cannot recover using backup control file
  • ora-19613 : datafile string not found in backup set
  • ora-09875 : TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file.
  • ora-14018 : partition bound list contains too few elements
  • ora-39314 : call to DBMS_SCHEMA_COPY.SYNC_CODE is not legal
  • ora-28020 : IDENTIFIED GLOBALLY already specified
  • ora-16237 : SGA specified for Logical Standby is too small
  • ora-01558 : out of transaction ID's in rollback segment string
  • ora-27302 : failure occurred at: string
  • ora-25100 : TABLESPACE option can only be used with ALTER INDEX REBUILD
  • 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.