ORA-10700: Alter access violation exception handler

Cause : Use this event to control what the VMS exception handler does when it encounters an access violation.

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

Level: >=10 Suspend current process on access violation *** SET THIS EVENT ONLY UNDER THE SUPERVISION OF ORACLE DEVELOPMENT ***

update : 26-05-2017
ORA-10700

ORA-10700 - Alter access violation exception handler
ORA-10700 - Alter access violation exception handler

  • ora-10657 : Lob column to be shrunk does not exist
  • ora-14608 : Tablespace was specified for the previous lob segments of column string in template but is not specified for string
  • ora-22277 : cannot use two different locators to modify the same LOB
  • ora-39053 : parameter or attribute string must be defined for a string job
  • ora-38741 : Formatted blocks value string is not valid.
  • ora-23542 : dependent object "string"."string" already registered
  • ora-12234 : TNS:Redirect to destination
  • ora-29549 : class string.string has changed, Java session state cleared
  • ora-12160 : TNS:internal error: Bad error number
  • ora-07287 : sksagdi: unsupported device for log archiving.
  • ora-30021 : Operation not allowed on undo tablespace
  • ora-13521 : Unregister operation on local Database id (string) not allowed
  • ora-02726 : osnpop: access error on oracle executable
  • ora-35276 : (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [ USING aggmap ]
  • ora-15013 : diskgroup "string" is already mounted
  • ora-31076 : required attribute "string" not specified
  • ora-23610 : internal dbms_streams_tablespaces error: [string] [string] [string] [string]
  • ora-36276 : (XSCGMDLAGG06) The current operator does not need a weight variable.
  • ora-26008 : Invalid syntax or bind variable in SQL string for column string. string
  • ora-38407 : The ADT associated with the attribute set already exists.
  • ora-25314 : a commit-time queue table cannot be migrated to 8.0
  • ora-06781 : TLI Driver: error reading negotation string
  • ora-15072 : command requires at least string failure groups, discovered only string
  • ora-02818 : Less than the number of blocks requested was read in
  • ora-00306 : limit of string instances in this database
  • ora-07595 : sppid: $GETJPIW failure
  • ora-12510 : TNS:database temporarily lacks resources to handle the request
  • ora-30454 : summary contains STDDEV without corresponding SUM & COUNT
  • ora-14007 : missing LESS keyword
  • ora-22851 : invalid CHUNK LOB storage option value
  • 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.