ORA-19999: skip_row procedure was called

Cause : The skip_row procedure was called which raises this error

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

Skip_row should only be called within a trigger or a procedure called by a trigger.

update : 22-07-2017

ORA-19999 - skip_row procedure was called
ORA-19999 - skip_row procedure was called

  • ora-01092 : ORACLE instance terminated. Disconnection forced
  • ora-12157 : TNS:internal network communication error
  • ora-39030 : invalid file type string
  • ora-12720 : operation requires database is in EXCLUSIVE mode
  • ora-09873 : TASDEF_OPEN: open error when opening tasdef@.dbf file.
  • ora-30691 : failed to allocate system resources while registering a TCP/IP connection for data traffic detection
  • ora-28651 : Primary index on IOTs can not be marked unusable
  • ora-01506 : missing or illegal database name
  • ora-13233 : failed to create sequence number [string] for R-tree
  • ora-28526 : invalid describe information returned to Heterogeneous Services
  • ora-38755 : Flashback is already turned on for this tablespace.
  • ora-13345 : a compound polygon geometry has fewer than five coordinates
  • ora-00351 : recover-to time invalid
  • ora-39046 : Metadata remap string has already been specified.
  • ora-07628 : smsfre: sga not mapped
  • ora-27032 : failed to obtain file size limit
  • ora-34183 : (MXCHGDCL22) Partition number already exists.
  • ora-13706 : Invalid value "string" specified for parameter "string" in "string" analysis mode.
  • ora-02822 : Invalid block offset
  • ora-31510 : name uses reserved prefix CDC$
  • ora-19240 : XP0020 - context item must be node in an axis expression
  • ora-30051 : VERSIONS clause not allowed here
  • ora-07759 : slemtr: invalid destination
  • ora-32814 : propagation schedule string does not exist
  • ora-34177 : (MXCHGDCL19) number cannot be deleted because one or more partitioned variables instantiate it.
  • ora-02732 : osnrnf: cannot find a matching database alias
  • ora-26685 : cannot apply transactions from multiple sources
  • ora-36641 : (XSDUNION20) The concat dimension must be defined as UNIQUE because base dimension workspace object contains custom member values.
  • ora-12057 : materialized view "string"."string" is INVALID and must complete refresh
  • ora-00107 : failed to connect to ORACLE listener process
  • 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.