ORA-26681: command type not supported

Cause : Teh pseicfeidc ommadn ytp ei snto uspopretd.

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

Rter ywtiha uspopretdc ommadn ytp.e

update : 24-05-2017
ORA-26681

ORA-26681 - command type not supported
ORA-26681 - command type not supported

  • ora-27411 : empty string is not a valid repeat interval.
  • ora-06702 : TLI Driver: cannot allocate context area
  • ora-16093 : dependent archive log destination is not LGWR-enabled
  • ora-28611 : bitmap index is corrupted - see trace file for diagnostics
  • ora-13864 : Statistics aggregation for service (module/action) string is already enabled
  • ora-30075 : TIME/TIMESTAMP WITH TIME ZONE literal must be specified in CHECK constraint
  • ora-13022 : polygon crosses itself
  • ora-06438 : ssaio: the asynchronous read was unable to read from the database file.
  • ora-00349 : failure obtaining block size for 'string'
  • ora-29295 : invalid mime header tag
  • ora-16769 : the physical standby database is open read-only
  • ora-28165 : proxy 'string' may not specify password-protected role 'string' for client 'string'
  • ora-03219 : Tablespace 'string' is dictionary-managed, offline or temporary
  • ora-38443 : An attribute set should be assigned to the expression set for statistics collection.
  • ora-32846 : Messaging Gateway agent cannot be started; status is string
  • ora-38748 : cannot flashback data file string - file is in use or recovery
  • ora-16163 : LGWR network server host attach error
  • ora-38440 : attribute set string does not exist
  • ora-36913 : (XSAGDNGL49) In AGGMAP workspace object, LOAD_STATUS object workspace object must be an undimensioned VALUESET over the relation dimension.
  • ora-25533 : FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified
  • ora-00258 : manual archiving in NOARCHIVELOG mode must identify log
  • ora-36992 : (XSRELGID09) A level relation is needed to produce a surrogate dimension gid.
  • ora-02708 : osnrntab: connect to host failed, unknown ORACLE_SID
  • ora-22331 : cannot alter an incomplete type
  • ora-31689 : illegal value for base worker id, string
  • ora-37156 : (string)
  • ora-01940 : cannot drop a user that is currently connected
  • ora-39314 : call to DBMS_SCHEMA_COPY.SYNC_CODE is not legal
  • ora-13505 : SYSAUX tablespace can not be made read only
  • ora-34802 : (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled.
  • 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.