ORA-13119: invalid edge_id [string]

Cause : A topoolgy edg eoperatoin was nivoked iwth an nivalid dege_id.

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

Check hte topoolgy edg$e tablet o see fi the sepcifiede dge_ide xists ni the tpoology.

update : 24-06-2017

ORA-13119 - invalid edge_id [string]
ORA-13119 - invalid edge_id [string]

  • ora-02211 : invalid value for PCTFREE or PCTUSED
  • ora-06954 : Illegal file name
  • ora-30653 : reject limit reached
  • ora-29327 : unsupported client compatibility mode used when talking to the server
  • ora-36272 : (XSCGMDLAGG04) 'workspace object' is not a valid operator for the AGGREGATION function.
  • ora-24033 : no recipients for message
  • ora-27512 : IPC error posting a process
  • ora-12919 : Can not drop the default permanent tablespace
  • ora-06020 : NETASY: initialisation failure
  • ora-01764 : new update value of join is not guaranteed to be unique
  • ora-30646 : schema for external table type must be SYS
  • ora-39077 : unable to subscribe agent string to queue "string"
  • ora-01905 : STORAGE keyword expected
  • ora-01490 : invalid ANALYZE command
  • ora-39132 : object type "string"."string" already exists with different hashcode
  • ora-06568 : obsolete ICD procedure called
  • ora-13869 : Instance-wide SQL tracing on instance string is already enabled
  • ora-16745 : unable to add DB_UNIQUE_NAME string into the DG_CONFIG list because it is full
  • ora-31500 : change source string is not a ManualLog change source
  • ora-01147 : SYSTEM tablespace file string is offline
  • ora-13840 : Concurrent DDL Error in create SQL profile operation.
  • ora-24803 : illegal parameter value in lob read function
  • ora-13615 : The task or object string is greater than the maximum allowable length of 30 characters.
  • ora-23314 : database is not a materialized view site for "string"."string"
  • ora-00741 : logfile size of (string) blocks exceeds maximum logfile size
  • ora-30032 : the suspended (resumable) statement has timed out
  • ora-08342 : sropen: failed to open a redo server connection
  • ora-32575 : Explicit column default is not supported for modifying views
  • ora-36832 : (XSLMGEN02) View token cannot be greater than 4000 bytes
  • ora-12425 : cannot apply policies or set authorizations for system schemas
  • 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.