ORA-10918: TABLESPACE GROUP name cannot be the same as tablespace name

Cause : Th etalbesapceg ropu nmae psecfiie dint hec omamndi s hte asmea s hte atblsepaec biengC RETAEdA/LTREed.

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

Plaeses peicfya n paprporitae atblsepaec gorupn am.e

update : 24-07-2017
ORA-10918

ORA-10918 - TABLESPACE GROUP name cannot be the same as tablespace name
ORA-10918 - TABLESPACE GROUP name cannot be the same as tablespace name

  • ora-30502 : system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
  • ora-02255 : obsolete 7.1.5
  • ora-31617 : unable to open dump file "string" for write
  • ora-07327 : smpdal: attempt to destroy pga when it was not mapped.
  • ora-24280 : invalid input value for parameter string
  • ora-32120 : Buffer size is less than amount specified
  • ora-25125 : BUFFER_POOL storage option not allowed
  • ora-24321 : inconsistent parameters passed
  • ora-32515 : cannot issue ORADEBUG command; waited number ms for process string
  • ora-29507 : query derived from USING clause found zero or many rows
  • ora-28007 : the password cannot be reused
  • ora-16055 : FAL request rejected
  • ora-16084 : an apply engine is already running
  • ora-19624 : operation failed, retry possible
  • ora-30177 : invalid flag used in a format specification
  • ora-01637 : rollback segment 'string' is being used by another instance (#string)
  • ora-28120 : driving context already exists
  • ora-30083 : syntax error was found in interval value expression
  • ora-31524 : could not find change set string for CDC change table string.string
  • ora-26504 : operation not implemented
  • ora-00073 : command string takes between string and string argument(s)
  • ora-22808 : REF dereferencing not allowed
  • ora-12042 : cannot alter job_queue_processes in single process mode
  • ora-39503 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-08121 : Number of indexes need to be maintained offline exceeds limit for DML
  • ora-28182 : cannot acquire Kerberos service ticket for client
  • ora-13049 : unable to determine tolerance value from table _SDODIM
  • ora-09886 : osnTXtt: translation error while expanding txipc@.trc.
  • ora-29881 : failed to validate indextype
  • ora-08103 : object no longer exists
  • 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.