ORA-13404: invalid ultCoordinate parameter

Cause : The ultCoordinate array parameter had the wrong length or contained an invalid value.

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

Check the documentation, and make sure the ultCoordinate parameter is correct.

update : 24-09-2017
ORA-13404

ORA-13404 - invalid ultCoordinate parameter
ORA-13404 - invalid ultCoordinate parameter

  • ora-31519 : CDC subscription string already exists
  • ora-09954 : scgcc: unexpected return status to callback of lock close
  • ora-39149 : cannot link privileged user to non-privileged user
  • ora-36951 : (XSFCAST28) The ALLOCLAST parameter cannot be set to YES unless PERIODICITY specifies more than one cycle.
  • ora-16139 : media recovery required
  • ora-24431 : Statement does not exist in the cache
  • ora-09809 : Unable to get user's group ID from connection
  • ora-16725 : the phase supplied to resource guard is invalid
  • ora-31102 : Already locked in exclusive mode. Cannot add lock.
  • ora-27156 : request for process information failed
  • ora-07549 : sftopn: $OPEN failure
  • ora-14516 : subpartition corrupt. all rows do not fall within subpartition bounds
  • ora-10573 : Test recovery tested redo from change string to string
  • ora-12016 : materialized view does not include all primary key columns
  • ora-19240 : XP0020 - context item must be node in an axis expression
  • ora-00485 : DIAG process terminated with error string
  • ora-12540 : TNS:internal limit restriction exceeded
  • ora-14159 : duplicate subpartition name
  • ora-06544 : PL/SQL: internal error, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  • ora-00383 : DEFAULT cache for blocksize string cannot be reduced to zero
  • ora-08446 : syntax error in SYNCHRONIZED clause in mask options
  • ora-36872 : (XSTFDSC02) Column type specifier cannot be used when the table function data type is specified.
  • ora-15045 : ASM file name 'string' is not in reference form
  • ora-13407 : invalid storage parameter
  • ora-01282 : date range specified is invalid
  • ora-29936 : NULL association is allowed only with a column or an index
  • ora-32002 : cannot create SPFILE already being used by the instance
  • ora-15095 : reached maximum ASM file size (string GB)
  • ora-32131 : bind data type cannot be changed
  • ora-24400 : error occured while creating connections in the pool
  • 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.