ORA-25200: invalid value string, QUEUE_NAME should be [SCHEMA.]NAME

Cause : AN ULL aprmaeetrw a ssepcfiide ofrQ UUEEN_AEM.

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

Sepcfiya onnN-ULL uqeeu anm.e

update : 29-06-2017
ORA-25200

ORA-25200 - invalid value string, QUEUE_NAME should be [SCHEMA.]NAME
ORA-25200 - invalid value string, QUEUE_NAME should be [SCHEMA.]NAME

  • ora-09834 : snyGetPortSet: failed to collect info on a port.
  • ora-30045 : No undo tablespace name specified
  • ora-30458 : 'string.string' cannot be refreshed because the refresh mask is string
  • ora-14606 : Tablespace was specified for previous subpartitions in template but is not specified for string
  • ora-12496 : cannot change existing level, category, or release numbers
  • ora-33030 : (XSAGDNGL14) In AGGMAP workspace object, you can have either a single independent PROTECT statement or PROTECT statements in your RELATION statements.
  • ora-01912 : ROW keyword expected
  • ora-28052 : the account is disabled
  • ora-15120 : ASM file name 'string' does not begin with the ASM prefix character
  • ora-38778 : Restore point 'string' already exists.
  • ora-38859 : instance string (thread string) is not ready to be disabled
  • ora-30002 : SYS_CONNECT_BY_PATH function is not allowed here
  • ora-29324 : SET COMPATIBILITY release string format is wrong
  • ora-03204 : the segment type specification should indicate partitioning
  • ora-16112 : log mining and apply stopping
  • ora-32515 : cannot issue ORADEBUG command; waited number ms for process string
  • ora-25118 : invalid DUMP DATAFILE/TEMPFILE option
  • ora-30450 : refresh_after_errors was TRUE; The following MVs could not be refreshed: string
  • ora-02786 : Size needed for shared region is greater than segment size
  • ora-29547 : Java system class not available: string
  • ora-26668 : STREAMS process string exists
  • ora-34802 : (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled.
  • ora-01878 : specified field not found in datetime or interval
  • ora-01059 : parse expected before a bind or execute
  • ora-32762 : Turn on Temp LOB Ref Count Tracing
  • ora-38414 : invalid datatype for the attribute string
  • ora-01526 : error in opening file 'string'
  • ora-13914 : Threshold notification failed.
  • ora-30979 : Partitioned XML Index not yet supported.
  • ora-02720 : osnfop: shmat failed
  • 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.