ORA-12200: TNS:could not allocate memory

Cause : Out of memory on machine.

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

Reconfigure machine to have more storage or run fewer applications while the Interchange is running.

update : 23-08-2017

ORA-12200 - TNS:could not allocate memory
ORA-12200 - TNS:could not allocate memory

  • ora-09957 : Unable to send termination request to IMON
  • ora-26501 : RepAPI operation failure
  • ora-16006 : audit_trail destination incompatible with database open mode
  • ora-16780 : a database has exhausted its archived redo log storage quota
  • ora-17622 : failed to deregister the memory with Oracle Disk Manager library
  • ora-13774 : insufficient privileges to select data from the workload repository
  • ora-02298 : cannot validate (string.string) - parent keys not found
  • ora-12521 : TNS:listener does not currently know of instance requested in connect descriptor
  • ora-29932 : the type being dropped is a statistics type
  • ora-25440 : invalid table alias: string
  • ora-16814 : incorrect redo transport setting for AlternateLocation for standby database
  • ora-36267 : (XSCGMDLAGG09) workspace object has no dimensions, so it cannot have a qualified data reference.
  • ora-09790 : sllfcf: unable to close file.
  • ora-09767 : osnmfs: bad return code from msg_send.
  • ora-28332 : cannot have more than one password for the encryption key
  • ora-21608 : duration is invalid for this function
  • ora-31197 : Error in processing file string
  • ora-19372 : invalid update condition
  • ora-31640 : unable to open dump file "string" for read
  • ora-02778 : Name given for the log directory is invalid
  • ora-36841 : (XSLMGEN11) Dimension string.string!string was not found
  • ora-14154 : only one of STORE IN or clause may be specified
  • ora-23465 : flavor already includes column string of "string"."string"
  • ora-22955 : The cardinality parameter is not within the allowed limits
  • ora-19589 : %s is not a snapshot or backup control file
  • ora-13051 : failed to initialize spatial object
  • ora-01549 : tablespace not empty, use INCLUDING CONTENTS option
  • ora-39216 : object type "string"."string" hashcode mismatch
  • ora-30743 : "string" is not an object view
  • ora-07201 : slhom: oracle_home variable not set in environment.
  • 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.