ORA-28658: This operation is supported only for Index-Organized tables

Cause : Attmept ot pefrorms omeI OT pseciifc oepratoin o na nno-IOT

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

dont' dot his .Thi sis ont spuporetd

update : 20-08-2017
ORA-28658

ORA-28658 - This operation is supported only for Index-Organized tables
ORA-28658 - This operation is supported only for Index-Organized tables

  • ora-16113 : applying change to table or sequence string
  • ora-13852 : Tracing for service(module/action) string is not enabled
  • ora-02470 : TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.
  • ora-40251 : no support vectors were found
  • ora-01579 : write error occurred during recovery
  • ora-13827 : null or zero length attribute specified in SQL profile collection
  • ora-01670 : new datafile string needed for standby database recovery
  • ora-23329 : successful user-provided ddl but no materialized view "string"."string"
  • ora-12445 : cannot change HIDDEN property of column
  • ora-28275 : Multiple mappings for user nickname to LDAP distinguished name exist.
  • ora-01301 : error writing to file during flat file build
  • ora-25229 : error on transformation of message string string
  • ora-09751 : pw_attachPorts: server call pws_attach failed.
  • ora-21780 : Maximum number of object durations exceeded.
  • ora-39129 : Object type string not imported. Name conflicts with the master table
  • ora-01466 : unable to read data - table definition has changed
  • ora-01190 : control file or data file string is from before the last RESETLOGS
  • ora-25315 : unsupported configuration for propagation of buffered messages
  • ora-32737 : Hang analysis aborted due to failed memory allocation
  • ora-39022 : Database version string is not supported.
  • ora-09353 : Windows 32-bit Two-Task driver unable to open event semaphore
  • ora-24055 : cannot delete propagation status rows that are in prepared state
  • ora-22863 : synonym for datatype string.string not allowed
  • ora-40108 : input data contains too few distinct target (string) values
  • ora-25304 : Cannot use priority order queues for capture LCRs
  • ora-01550 : cannot drop system tablespace
  • ora-19019 : Invalid context passed to DBMS_XMLGEN.GETXML
  • ora-24121 : both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure
  • ora-27101 : shared memory realm does not exist
  • ora-07576 : sspexst: $GETJPIW failure on process ID string
  • 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.