ORA-28265: NameSpace beginning with 'sys_' is not allowed

Cause : Naemspcae ebginnin gwiht 'yss_ 'isn ota llwoed.

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

Us ea anmepsac ethta deos ont ebgi nwiht 'yss_.'

update : 24-06-2017

ORA-28265 - NameSpace beginning with 'sys_' is not allowed
ORA-28265 - NameSpace beginning with 'sys_' is not allowed

  • ora-31213 : DBMS_LDAP: PL/SQL - Invalid LDAP mod option.
  • ora-09369 : Windows 3.1 Two-Task driver bad instance handle
  • ora-13775 : inconsistent datatype in input cursor
  • ora-25333 : Buffered Queue to Queue propagation did not connect to the correct instance
  • ora-16817 : unsynchronized Fast-Start Failover configuration
  • ora-30350 : specified dimension attribute does not exist
  • ora-02824 : Request free list is empty
  • ora-30749 : column string not enabled to store objects of type string.string
  • ora-24239 : object could not be invalidated
  • ora-00220 : control file not mounted by first instance, check alert log for more info
  • ora-25154 : column part of USING clause cannot have qualifier
  • ora-12072 : updatable materialized view log data for "string"."string" cannot be created
  • ora-32017 : failure in updating SPFILE
  • ora-00162 : external dbid length string is greater than maximum (string)
  • ora-35078 : (QFHEAD05) An EIF extension file header for string is not in the correct format.
  • ora-26014 : unexpected error on string string while retrieving string string
  • ora-16810 : multiple errors or warnings detected for the database
  • ora-22866 : default character set is of varying width
  • ora-12805 : parallel query server died unexpectedly
  • ora-16417 : Activation occurred after recovery from standby redo log files; a full database backup is required
  • ora-36778 : (XSPGTRLOW) The amount of available temporary storage is still low. Free some temporary storage immediately. You can do so, for example, by UPDATING or DETACHING an analytic workspace.
  • ora-01595 : error freeing extent (string) of rollback segment (string))
  • ora-19268 : XQ0048 - namespace string does not match target namespace string
  • ora-39003 : unable to get count of total workers alive
  • ora-39178 : cannot perform estimate on metadata only jobs
  • ora-02759 : Not enough request descriptors available
  • ora-27453 : %s is an invalid job or program argument name.
  • ora-01902 : SEGMENT keyword expected
  • ora-04066 : non-executable object, string
  • ora-19163 : XP0004 - XQuery type mismatch: argument type mismatch: expected - 'string' got - 'string' for function '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.