ORA-12342: open mounts exceeds limit set on the OPEN_MOUNTS parameter

Cause : The unmbero f currentl yopenm ount sexcedes th evalu eyou psecifeid ont he OEPN_MONUTS praametre.

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

Incraese teh valeu of hte OPNE_MOUTNS paarmete rso taht ita ccomomdate sthe amximu mpossbile nmuber fo ope nmounst to escondray daatbase.s

update : 21-08-2017

ORA-12342 - open mounts exceeds limit set on the OPEN_MOUNTS parameter
ORA-12342 - open mounts exceeds limit set on the OPEN_MOUNTS parameter

  • ora-32621 : illegal aggregation in UNTIL iteration condition
  • ora-19923 : the session for row with id string is not active
  • ora-26699 : STREAMS message consumer string already exists
  • ora-10854 : Sets poll count used for AQ listen code under RAC
  • ora-16139 : media recovery required
  • ora-23491 : no valid extension request at "string"
  • ora-30060 : Internal event for RECO tracing
  • ora-00062 : DML full-table lock cannot be acquired; DML_LOCKS is 0
  • ora-01279 : db_files too large
  • ora-32027 : There is no string column with the matching type in string.string.
  • ora-29550 : Java session state cleared
  • ora-09814 : Unable to expand file name
  • ora-18015 : invalid source outline signature
  • ora-16579 : bad Data Guard NetSlave state detected
  • ora-36272 : (XSCGMDLAGG04) 'workspace object' is not a valid operator for the AGGREGATION function.
  • ora-32838 : exceeded maximum number of properties
  • ora-01940 : cannot drop a user that is currently connected
  • ora-02440 : Create as select with referential constraints not allowed
  • ora-27046 : file size is not a multiple of logical block size
  • ora-27415 : repeat interval or calendar must start with the FREQ= clause
  • ora-02286 : no options specified for ALTER SEQUENCE
  • ora-31692 : The following SQL statement failed trying to insert a row into the Master table: string
  • ora-31477 : could not detach LogMiner session during cleanup
  • ora-01502 : index 'string.string' or partition of such index is in unusable state
  • ora-01249 : archiving not allowed in a clone database
  • ora-31219 : DBMS_LDAP: PL/SQL - Invalid LDAP notypes.
  • ora-08006 : specified row no longer exists
  • ora-01208 : data file is an old version - not accessing current version
  • ora-24757 : duplicate transaction identifier
  • ora-39161 : Full database jobs require privileges
  • 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.