ORA-22863: synonym for datatype string.string not allowed

Cause : A ysnoynm psecfiictaio nfo ra adtaytpei s ont uspproted

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

don otu set hes ynnoymf ort hed attaype

update : 19-08-2017
ORA-22863

ORA-22863 - synonym for datatype string.string not allowed
ORA-22863 - synonym for datatype string.string not allowed

  • ora-04011 : sequence string must range between string and string
  • ora-25298 : Only immediage visibility mode supported for buffered message enqueue or dequeue
  • ora-29390 : some resource plans are not part of any top-plan
  • ora-24051 : cannot propagate object type payloads that have a REF attribute
  • ora-29864 : analyzing domain indexes marked LOADING/FAILED not supported
  • ora-14176 : this attribute may not be specified for a hash partition
  • ora-31698 : Error stack buffer size must be specified and must be greater than 0.
  • ora-29375 : sum of values string for level string, plan string exceeds string
  • ora-01106 : database must be closed before dismounting
  • ora-12051 : ON COMMIT attribute is incompatible with other options
  • ora-13237 : internal error during R-tree concurrent updates: [string]
  • ora-38447 : Type required for the embedded ADT attribute "string" is missing
  • ora-19704 : file name exceeds maximum length of string
  • ora-16222 : automatic Logical Standby retry of last action
  • ora-39213 : Metadata processing is not available
  • ora-12406 : unauthorized SQL statement for policy string
  • ora-02397 : exceeded PRIVATE_SGA limit, you are being logged off
  • ora-08498 : Warning: picture mask 'string' overrides picture mask option 'USAGE IS string' to 'USAGE IS DISPLAY'
  • ora-22864 : cannot ALTER or DROP LOB indexes
  • ora-07581 : spstp: cannot derive SID from unexpected process name
  • ora-32407 : cannot exclude new values when materialized view log includes new values
  • ora-13867 : Database-wide SQL tracing is already enabled
  • ora-13283 : failure to get new geometry object for conversion in place
  • ora-38784 : Cannot create restore point 'string'.
  • ora-01984 : invalid auditing option for procedures/packages/functions
  • ora-16745 : unable to add DB_UNIQUE_NAME string into the DG_CONFIG list because it is full
  • ora-31516 : CDC change set string already exists
  • ora-38950 : Source platform string not cross platform compliant
  • ora-01943 : IDENTIFIED BY already specified
  • ora-12170 : TNS:Connect timeout occurred
  • 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.