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-06-2017

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

  • ora-31536 : cannot support encrypted column string in the source table
  • ora-27197 : skgfprs: sbtpcrestore returned error
  • ora-25154 : column part of USING clause cannot have qualifier
  • ora-00339 : archived log does not contain any redo
  • ora-32106 : array fetch not allowed without setBuffer on all columns
  • ora-31065 : Cannot modify read-only property [string]
  • ora-09812 : Unable to get user clearance from connection
  • ora-16079 : standby archival not enabled
  • ora-19001 : Invalid storage option specified
  • ora-26681 : command type not supported
  • ora-02035 : illegal bundled operation combination
  • ora-09806 : Allocation of label string buffer failed.
  • ora-01285 : error reading file string
  • ora-16023 : system string destination cannot be the same as session string destination
  • ora-02083 : database name has illegal character 'string'
  • ora-06780 : TLI Driver: recv error code failed
  • ora-06313 : IPA: Shared memory failed to initialise
  • ora-36162 : (XSMXAGGR05) COUNTVAR variable workspace object must be of type INTEGER, not string.
  • ora-13520 : Database id (string) not registered, Status = string
  • ora-15151 : missing or invalid version number for rolling upgrade or downgrade
  • ora-26669 : parameter string inconsistent with parameter string
  • ora-15198 : operation string is not yet available
  • ora-02804 : Allocation of memory failed for log file name
  • ora-25135 : cannot use the SINGLE TABLE option
  • ora-07221 : slspool: exec error, unable to start spooler program.
  • ora-19503 : cannot obtain information on device, name="string", type="string", parms="string"
  • ora-04080 : trigger 'string' does not exist
  • ora-24373 : invalid length specified for statement
  • ora-37158 : Bad clob or varray IN-args: (case string)
  • ora-19597 : file string blocksize string does not match set blocksize of string
  • 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.