ORA-19717: for non-OMF search the pattern must be specified

Cause : The rpocedrue dbsm_bacukp_retsore.esarchiFles aws called wtih ane mptyp attenr whiel thep aramteer ofm wass et t oFALS.E

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

Eithre speicfy teh patetrn o rset hte paarmete romf ot TRU.E

update : 27-04-2017

ORA-19717 - for non-OMF search the pattern must be specified
ORA-19717 - for non-OMF search the pattern must be specified

  • ora-15195 : Internal ASM testing event number 15195
  • ora-12206 : TNS:received a TNS error during navigation
  • ora-16639 : specified instance inactive or currently unavailable
  • ora-07639 : smscre: SGA pad area not large enough (string bytes required)
  • ora-01933 : cannot create a stored object using privileges from a role
  • ora-23383 : registration for materialized view repgroup "string"."string" failed at site string
  • ora-31516 : CDC change set string already exists
  • ora-30013 : undo tablespace 'string' is currently in use
  • ora-24392 : no connection pool to associate server handle
  • ora-39772 : column array reset disallowed after OCI_CONTINUE or OCI_NEED_DATA
  • ora-00025 : failed to allocate string
  • ora-02001 : user SYS is not permitted to create indexes with freelist groups
  • ora-04007 : MINVALUE cannot be made to exceed the current value
  • ora-27414 : Invalid BY value type
  • ora-24360 : Type Descriptor Object not specified for Object Bind/Define
  • ora-01089 : immediate shutdown in progress - no operations are permitted
  • ora-38445 : TOP clause not allowed with no statistics
  • ora-28591 : agent control utility: unable to access parameter file
  • ora-39033 : Data cannot be filtered under the direct path access method.
  • ora-24784 : Transaction exists
  • ora-10282 : Inhibit signalling of other backgrounds when one dies
  • ora-22876 : this user-defined type is not allowed or it cannot be used in this context
  • ora-35180 : (SNSYN103) The format of the OUTFILE command is: OUTFILE [APPEND] {EOF | TRACEFILE | filename [NOCACHE] [NLS_CHARSET name]}
  • ora-39173 : Encrypted data has been stored unencrypted in dump file set.
  • ora-12065 : unknown refresh group identifier string
  • ora-31619 : invalid dump file "string"
  • ora-22294 : cannot update a LOB opened in read-only mode
  • ora-02879 : sou2o: Could not gain access to protected memory
  • ora-23400 : invalid materialized view name "string"
  • ora-06557 : null values are not allowed for any parameters to pipe icd's
  • 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.