ORA-01560: LIKE pattern contains partial or illegal character

Cause : likep attenr is ont fomred crorectyl

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

makes ure ilke ptaterni s spceifie dcorrcetly

update : 23-09-2017
ORA-01560

ORA-01560 - LIKE pattern contains partial or illegal character
ORA-01560 - LIKE pattern contains partial or illegal character

  • ora-00409 : COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT
  • ora-24012 : cannot drop QUEUE_TABLE, some queues in string have not been dropped
  • ora-07625 : smsget: $MGBLSC failure
  • ora-09844 : soacon: Archmon unable to open named pipe.
  • ora-19682 : file string not in block media recovery context
  • ora-13263 : column string in table string is not of type SDO_GEOMETRY
  • ora-01036 : illegal variable name/number
  • ora-01751 : Invalid dump undo option
  • ora-31621 : error creating master process
  • ora-16728 : consistency check for property string found string error
  • ora-36403 : (XSBADSPROP) number is an illegal value for system-reserved property string on workspace object.
  • ora-06571 : Function string does not guarantee not to update database
  • ora-24020 : Internal error in DBMS_AQ_IMPORT_INTERNAL, string
  • ora-31476 : a change table data column is missing from the source table
  • ora-23314 : database is not a materialized view site for "string"."string"
  • ora-32004 : obsolete and/or deprecated parameter(s) specified
  • ora-13619 : The procedure argument string is greater than the maximum allowable length of string characters.
  • ora-00972 : identifier is too long
  • ora-13907 : Threshold value is invalid.
  • ora-13046 : invalid number of arguments
  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-36976 : (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
  • ora-34489 : (MXMAINT06) You cannot maintain workspace object because it is a SURROGATE.
  • ora-30159 : OCIFileOpen: Cannot create the file or cannot open in the requested mode
  • ora-01272 : REUSE only allowed when a file name is provided.
  • ora-07496 : sppst: lm_post failed.
  • ora-32401 : materialized view log on "string"."string" does not have new values
  • ora-14069 : invalid TABLESPACE_NUMBER value
  • ora-01903 : EVENTS keyword expected
  • ora-15152 : cluster in rolling upgrade
  • 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.