ORA-02068: following severe error from stringstring

Cause : A sever eerror (idsconnec,t fatal rOacle erorr) recevied fromt he indiacted datbaase lin.k See following error text.

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

Contactt he remoet systema dministartor.

update : 28-07-2017
ORA-02068

ORA-02068 - following severe error from stringstring
ORA-02068 - following severe error from stringstring

  • ora-12712 : new character set must be a superset of old character set
  • ora-01033 : ORACLE initialization or shutdown in progress
  • ora-36164 : (XSMXAGGR07) When using the COUNTVAR clause, the number of variables to be aggregated (number) must match the number of COUNTVAR variables (number).
  • ora-14020 : this physical attribute may not be specified for a table partition
  • ora-29257 : host string unknown
  • ora-28504 : ROWID not found in ROWID cache for heterogeneous database link
  • ora-12927 : RETENTION option already specified
  • ora-22345 : recompile type string.string before attempting this operation
  • ora-07445 : exception encountered: core dump [string] [string] [string] [string] [string] [string]
  • ora-14134 : indexes cannot use both DESC and REVERSE
  • ora-02827 : Invalid file number
  • ora-07449 : sc: usnewlock failed.
  • ora-32700 : error occurred in DIAG Group Service
  • ora-00025 : failed to allocate string
  • ora-24146 : rule string.string already exists
  • ora-10372 : parallel query server kill event proc
  • ora-29848 : error occurred in the execution of ODCIINDEXMERGEPARTITION routine
  • ora-01685 : max # extents (string) reached in index string.string partition string
  • ora-13757 : "SQL Tuning Set" "string" owned by user "string" is active.
  • ora-31191 : Resource string is already checked out
  • ora-01286 : start interval required
  • ora-27548 : Unable to unprepare IPC buffer
  • ora-36722 : (XSALLOC02) In AGGMAP workspace object, you specified an NA or ZERO sourceval but supplied formula workspace object as your source for ALLOCATE.
  • ora-09856 : smpalo: vm_allocate error while allocating pga.
  • ora-02769 : Setting of handler for SIGTERM failed
  • ora-16107 : all log data from primary has been processed
  • ora-16590 : Data Guard configuration does not contain a primary database
  • ora-10948 : trace name context forever
  • ora-16822 : new primary database not yet ready for standby database reinstatement
  • ora-38432 : EVALUATE operator only allowed on an expression column
  • 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.