ORA-16246: User initiated abort apply successfully completed

Cause : SQL Apply was stopped using the abort option.

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

No action necessary, this informational statement is provided to record the event for diagnostic purposes.

update : 26-06-2017
ORA-16246

ORA-16246 - User initiated abort apply successfully completed
ORA-16246 - User initiated abort apply successfully completed

  • ora-07845 : sllfcl: LIB$FREE_VM failue
  • ora-32515 : cannot issue ORADEBUG command; waited number ms for process string
  • ora-02285 : duplicate START WITH specifications
  • ora-12013 : updatable materialized views must be simple enough to do fast refresh
  • ora-16093 : dependent archive log destination is not LGWR-enabled
  • ora-06809 : TLI Driver: could not clear the IPX ethernet SAP at init
  • ora-23533 : object "string"."string" can not be cached
  • ora-30390 : the source statement is not equivalent to the destination statement
  • ora-07475 : slsget: cannot get vm statistics.
  • ora-13196 : failed to compute supercell for element string.string.string
  • ora-06547 : RETURNING clause must be used with INSERT, UPDATE, or DELETE statements
  • ora-09808 : Could not obtain user clearance.
  • ora-24020 : Internal error in DBMS_AQ_IMPORT_INTERNAL, string
  • ora-14313 : Value string does not exist in partition string
  • ora-30067 : Internal Event to turn on nested debugging info
  • ora-01521 : error in adding data files
  • ora-13366 : invalid combination of interior exterior rings
  • ora-31679 : Table data object string has long columns, and longs can not be loaded/unloaded using a network link
  • ora-39017 : Worker request not supported when job is in string state.
  • ora-31472 : Importing Change Data Capture version string.string is too new
  • ora-00284 : recovery session still in progress
  • ora-13200 : internal error [string] in spatial indexing.
  • ora-38954 : Cross platform transport is not supported between source platform identifier string and target platform identifier string
  • ora-19636 : archivelog thread string sequence string already included
  • ora-10918 : TABLESPACE GROUP name cannot be the same as tablespace name
  • ora-02424 : potential circular view references or unknown referenced tables
  • ora-19563 : %s header validation failed for file string
  • ora-28510 : heterogeneous database link initialization failed
  • ora-01245 : offline file string will be lost if RESETLOGS is done
  • ora-36378 : (XSAGTHRWEIGHT) While running AGGREGATE with multiple threads, the weight variable workspace object specified by your ARGS variable workspace object must exist in the same analytic workspace as your AGGMAP workspace object.
  • 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.