ORA-15110: no diskgroups mounted

Cause : N odsikrgopusw eer pseicfeidi nt h eAMS_IDSGKRUOP Spraaemtre,s oi ntsacnes tratpu ro hteA LETRD IKSGORU PALL OMUTN ocmamn dddi ontm onuta n ydsikrgopus.

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

Sepcfiyv aildd iksgorusp ni hteA S_MDSIKRGOPUSp aarmtee ro ringoer htee rorr.

update : 30-04-2017
ORA-15110

ORA-15110 - no diskgroups mounted
ORA-15110 - no diskgroups mounted

  • ora-02799 : Unable to arm signal handler
  • ora-01774 : Dump undo option specified more than once
  • ora-22814 : attribute or element value is larger than specified in type
  • ora-22335 : The client cannot work with an altered type
  • ora-19694 : some changed blocks were not found in the change tracking file
  • ora-00448 : normal completion of background process
  • ora-07621 : smscre: illegal redo block size
  • ora-23413 : table "string"."string" does not have a materialized view log
  • ora-01113 : file string needs media recovery
  • ora-24065 : propagation for QUEUE string and DESTINATION string already disabled
  • ora-01149 : cannot shutdown - file string has online backup set
  • ora-12321 : database (link name string) is not open and AUTO_MOUNTING=FALSE
  • ora-38730 : Invalid SCN/TIMESTAMP expression.
  • ora-27472 : invalid metadata attribute string
  • ora-24150 : evaluation context string.string does not exist
  • ora-14151 : invalid table partitioning method
  • ora-32024 : invalid directory specified for audit_file_dest parameter
  • ora-36210 : (XSAGOP05R) In AGGMAP workspace object, you can only specify the REMOPERATOR string with the PROPORTIONAL, EVEN, or HEVEN operators, not string.
  • ora-00102 : network protocol string cannot be used by dispatchers
  • ora-24024 : Internal error in DBMS_AQ_IMP_INTERNAL.string [string] [string]
  • ora-28277 : LDAP search, while authenticating global user with passwords, failed.
  • ora-16205 : DDL skipped due to skip setting
  • ora-24012 : cannot drop QUEUE_TABLE, some queues in string have not been dropped
  • ora-13379 : invalid index for sub-element to be extracted
  • ora-02838 : Unable to arm signal handler for the alarm signal
  • ora-10941 : trace name context forever
  • ora-01099 : cannot mount database in SHARED mode if started in single process mode
  • ora-09717 : osnsui: maximum number of user interrupt handlers exceeded.
  • ora-13641 : Task cannot be interrupted yet. You may cancel it instead.
  • ora-06954 : Illegal file name
  • 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.