ORA-25135: cannot use the SINGLE TABLE option

Cause : The SINGLE TABLE option is only valid for hash clusters.

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

Do not specify the SINGLE TABLE option.

update : 22-08-2017
ORA-25135

ORA-25135 - cannot use the SINGLE TABLE option
ORA-25135 - cannot use the SINGLE TABLE option

  • ora-12602 : TNS: Connection Pooling limit reached
  • ora-00750 : database has been previously mounted and dismounted
  • ora-07265 : sppst: semop error, unable to increment semaphore.
  • ora-02098 : error parsing index-table reference (:I)
  • ora-04007 : MINVALUE cannot be made to exceed the current value
  • ora-25195 : invalid option for index on an index-organized table
  • ora-22953 : Cardinality of the input to powermultiset exceeds maximum allowed
  • ora-23308 : object string.string does not exist or is invalid
  • ora-39785 : SQL expressions returning ADT objects are not allowed in direct path
  • ora-09281 : sllfop: error opening file
  • ora-23372 : type string in table string is unsupported
  • ora-29856 : error occurred in the execution of ODCIINDEXDROP routine
  • ora-12225 : TNS:destination host unreachable
  • ora-13193 : failed to allocate space for geometry
  • ora-24901 : handles belonging to different environments passed into an OCI call
  • ora-13767 : End snapshot ID must be greater than or equal to begin snapsho ID.
  • ora-02844 : Invalid value for the leave open flag
  • ora-01175 : data dictionary has more than the string files allowed by the instance
  • ora-10266 : Trace OSD stack usage
  • ora-16256 : Failure to complete standby redo logfile archival after failover
  • ora-31407 : end_date must be greater than the begin_date
  • ora-13517 : Baseline (id = string) does not exist
  • ora-03130 : the buffer for the next piece to be fetched is required
  • ora-02765 : Invalid maximum number of servers
  • ora-30335 : JOIN KEY clause references a level not in this hierarchy
  • ora-12463 : undefined group string for policy string
  • ora-31478 : could not detach LogMiner session after change set advance
  • ora-31092 : invalid SQL name "string"
  • ora-33282 : (DBERR11) Cannot wait for analytic workspace string to become available since doing so would cause a deadlock.
  • ora-03213 : Invalid Lob Segment Name for DBMS_SPACE package
  • 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.