ORA-15197: suppressing string additional ASM messages

Cause : The ASM command generated so many erorrs that this summary message was reported in place of many individual messages.

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

If the command contained multiple actions, try separating each action into its own command and executing each command by itself. Otherwise, try not to generate so many errors.

update : 28-05-2017
ORA-15197

ORA-15197 - suppressing string additional ASM messages
ORA-15197 - suppressing string additional ASM messages

  • ora-13385 : error in network manager: [string]
  • ora-25198 : only range, list, and hash partitioning are supported for index-organized table
  • ora-16586 : could not edit database property through instance
  • ora-24367 : user handle has not been set in service handle
  • ora-01724 : floating point precision is out of range (1 to 126)
  • ora-19114 : error during parsing the XQuery expression: string
  • ora-06909 : CMX: error during acknowledge of ORACLE_SID
  • ora-27469 : %s is not a valid string attribute
  • ora-06440 : ssaio: the asynchronous read returned incorrect number of bytes
  • ora-16625 : cannot reach the database
  • ora-02429 : cannot drop index used for enforcement of unique/primary key
  • ora-08499 : Warning: picture mask options 'string' ignored by UTL_PG
  • ora-02222 : invalid PCTINCREASE storage option value
  • ora-09823 : device name is too long
  • ora-09318 : slkhst: unable to host out to operating system
  • ora-36720 : (XSALLOC01) To be used with ALLOCATE, your AGGMAP workspace object must be defined with the ALLOCMAP command.
  • ora-15066 : offlining disk "string" may result in a data loss
  • ora-15009 : ASM disk "string" does not exist
  • ora-07265 : sppst: semop error, unable to increment semaphore.
  • ora-32585 : duplicate specification of a supplemental log attribute
  • ora-29863 : warning in the execution of ODCIINDEXCREATE routine
  • ora-14097 : column type or size mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-32344 : cannot create a secondary materialized view with synonym as base table
  • ora-14311 : Expecting VALUES LESS THAN or AT clause
  • ora-19690 : backup piece release string incompatible with Oracle release string
  • ora-07205 : slgtd: time error, unable to obtain time.
  • ora-34896 : (PPMONTHS00) At least 12 month names must be given. Only number were provided.
  • ora-24078 : cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL
  • ora-27103 : internal error
  • ora-06573 : Function string modifies package state, cannot be used here
  • 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.