ORA-12341: maximum number of open mounts exceeded

Cause : The unmbers peciifed o nthe POEN_MUONTS aprameetr int he praametre fil eexcedes th emaxiumm alolwed 2(55).

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

Chaneg thev alueo f thsi parmaeters o thta it erflecst thea ctua lnumbre of opssibel ope nmounst to escondray daatbase.s Thi smustb e less tha n255.

update : 25-06-2017

ORA-12341 - maximum number of open mounts exceeded
ORA-12341 - maximum number of open mounts exceeded

  • ora-16194 : Modifying DB_UNIQUE_NAME requires SID='*' qualifier
  • ora-15195 : Internal ASM testing event number 15195
  • ora-01563 : rollback segment is PUBLIC, need to use the keyword PUBLIC
  • ora-07472 : snclrd: open error when opening sgadef.dbf file.
  • ora-27000 : skgfqsbi: failed to initialize storage subsystem (SBT) layer
  • ora-02767 : Less than one request descriptor was allocated per server
  • ora-09719 : osncui: invalid handle.
  • ora-22891 : cannot have multiple columns in REF constraint
  • ora-34871 : (PERMIT06) Session-only value 'value' of workspace object has been deleted because a PERMIT change has revealed a duplicate value.
  • ora-10573 : Test recovery tested redo from change string to string
  • ora-02164 : DATAFILE clause specified more than once
  • ora-13906 : The tablepace is not of the right type.
  • ora-29314 : tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY
  • ora-24324 : service handle not initialized
  • ora-31625 : Schema string is needed to import this object, but is unaccessible
  • ora-01169 : DATAFILE number 1 not found. Must be present
  • ora-02773 : Invalid maximum client wait time
  • ora-00480 : LCK* process terminated with error
  • ora-31603 : object "string" of type string not found in schema "string"
  • ora-19960 : Internal use only
  • ora-01282 : date range specified is invalid
  • ora-39094 : Parallel execution not supported in this database edition.
  • ora-28543 : Error initializing apply connection to non-Oracle system
  • ora-06568 : obsolete ICD procedure called
  • ora-07563 : sldext: $PARSE failure
  • ora-19851 : OS error while managing auxiliary database string
  • ora-06028 : NETASY: unable to intialise for logging
  • ora-12518 : TNS:listener could not hand off client connection
  • ora-39017 : Worker request not supported when job is in string state.
  • ora-13020 : coordinate is NULL
  • 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.