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 : 29-05-2017

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

  • ora-25333 : Buffered Queue to Queue propagation did not connect to the correct instance
  • ora-13362 : disjoint sub-element in a compound polygon
  • ora-00289 : suggestion : string
  • ora-30102 : 'string' is not in the legal range for 'string'
  • ora-35587 : (SQLOUT20) The nesting of table functions and SQL commands has exceeded the maximum of number levels.
  • ora-00225 : expected size string of control file differs from actual size string
  • ora-23498 : repgroups specified must have the same masters
  • ora-30453 : summary contains AVG without corresponding COUNT
  • ora-31216 : DBMS_LDAP: PL/SQL - Invalid LDAP rdn.
  • ora-01927 : cannot REVOKE privileges you did not grant
  • ora-12902 : default temporary tablespace must be SYSTEM or of TEMPORARY type
  • ora-30085 : syntax error was found in overlaps predicate
  • ora-02167 : LOGFILE clause specified more than once
  • ora-31602 : parameter string value "string" in function string inconsistent with string
  • ora-01623 : log string is current log for instance string (thread string) - cannot drop
  • ora-36672 : (XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only have a single partition dimension.
  • ora-31449 : invalid value for change_set_name
  • ora-16778 : redo transport error for one or more databases
  • ora-19768 : USING clause only valid with ENABLE CHANGE TRACKING
  • ora-38794 : Flashback target time not in current incarnation
  • ora-19565 : BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices
  • ora-02030 : can only select from fixed tables/views
  • ora-29348 : You must specify the datafiles to be plugged in
  • ora-38770 : FLASHBACK DATABASE failed during recovery.
  • ora-39045 : invalid metadata remap name string
  • ora-38903 : DML error logging is not supported for abstract column "string"
  • ora-33304 : (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.
  • ora-14129 : INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
  • ora-39016 : Operation not supported when job is in string state.
  • ora-02427 : create view failed
  • 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.