ORA-13622: invalid recommendation annotation

Cause : Teh sue rattepmtde ot amr kar eocmemnadtoinu sniga ni navldi nantoaito.n aVldi nantoaito natcinosa r eACCETP,R EEJC Tadn GINROE.

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

Crorcett h eatcino nadr ertyt h eoeprtaino.

update : 20-07-2017
ORA-13622

ORA-13622 - invalid recommendation annotation
ORA-13622 - invalid recommendation annotation

  • ora-01908 : EXISTS keyword expected
  • ora-13428 : invalid modelCoordinateLocation
  • ora-39114 : Dump files are not supported for network jobs.
  • ora-03254 : unable to execute the sql in read only database
  • ora-00345 : redo log write error block string count string
  • ora-39141 : dump file "string" is a duplicate of dump file "string"
  • ora-23314 : database is not a materialized view site for "string"."string"
  • ora-02473 : Error while evaluating the cluster's hash expression.
  • ora-22285 : non-existent directory or file for string operation
  • ora-01719 : outer join operator (+) not allowed in operand of OR or IN
  • ora-39777 : data saves are not allowed when loading lob columns
  • ora-12856 : cannot run parallel query on a loopback connection
  • ora-24771 : cannot detach, prepare or forget a local transaction
  • ora-39764 : specified stream is not in the specified direct path context
  • ora-01999 : password file cannot be updated in SHARED mode
  • ora-12321 : database (link name string) is not open and AUTO_MOUNTING=FALSE
  • ora-19575 : expected string blocks in file string, found string
  • ora-00151 : invalid transaction ID
  • ora-37037 : (XSMLTDCL03) You cannot RENAME objects in analytic workspace string because it is attached in MULTI mode.
  • ora-01216 : thread string is expected to be disabled after CREATE CONTROLFILE
  • ora-25208 : RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE
  • ora-30079 : cannot alter database timezone when database has TIMESTAMP WITH LOCAL TIME ZONE columns
  • ora-27002 : function called with invalid device structure
  • ora-28012 : Manual commit not allowed here
  • ora-38754 : FLASHBACK DATABASE not started; required redo log is not available
  • ora-38767 : flashback retention target parameter mismatch
  • ora-25427 : cannot downgrade database links after database link data dictionary has been upgraded
  • ora-12200 : TNS:could not allocate memory
  • ora-01308 : initialization parameter utl_file_dir is not set
  • ora-25153 : Temporary Tablespace is Empty
  • 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.