ORA-16180: number processes specified for MAX_PARALLEL_SERVERS is too small

Cause : The ma xnumbero f parallel serevrs avaliable fro Logicla Standyb is less than 5becaseo f the ilmit imopsed byt he toos mall vlaue of AMX_PARALLEL_SEREVRS.

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

Adjustt he valeus of teh initilaizatio nparameetrs PARLALEL_MA_XSERVER Sto be ta least5 .

update : 24-05-2017
ORA-16180

ORA-16180 - number processes specified for MAX_PARALLEL_SERVERS is too small
ORA-16180 - number processes specified for MAX_PARALLEL_SERVERS is too small

  • ora-29952 : cannot issue DDL on a domain index partition marked as LOADING
  • ora-31517 : CDC change table string.string already exists
  • ora-33048 : (XSAGDNGL23) In AGGMAP workspace object, the relation workspace object and the relation workspace object are both over the same base dimension.
  • ora-23612 : unable to find tablespace "string"
  • ora-39018 : master process received invalid message number string
  • ora-01080 : error in shutting down ORACLE
  • ora-25334 : Buffered propagation must restart as the destination queue was recreated/moved
  • ora-01619 : thread string is mounted by another instance
  • ora-27141 : invalid process ID
  • ora-29926 : association already defined for the object
  • ora-37041 : (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out.
  • ora-19600 : input file is string string (string)
  • ora-12437 : invalid policy option: string
  • ora-29800 : invalid name for operator
  • ora-00374 : parameter db_block_size = string invalid ; must be a multiple of string in the range [string..string]
  • ora-27469 : %s is not a valid string attribute
  • ora-31696 : unable to export/import string using client specified string method
  • ora-31457 : maximum length of description field exceeded
  • ora-09282 : sllfrb: error reading records
  • ora-38905 : DML error logging is not supported for LONG column "string"
  • ora-29973 : Unsupported query or operation during change notification registration
  • ora-24019 : identifier for string too long, should not be greater than string characters
  • ora-12032 : cannot use rowid column from materialized view log on "string"."string"
  • ora-02491 : missing required keyword ON or OFF in AUTOEXTEND clause
  • ora-01271 : Unable to create new file name for file string
  • ora-26535 : %ud byte row cache insufficient for table with rowsize=number
  • ora-19957 : database should have no datafiles in unknown state
  • ora-36636 : (XSDUNION04) The unique concat dimension workspace object cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension.
  • ora-09943 : Allocation of memory for password list component failed.
  • ora-00301 : error in adding log file 'string' - file cannot be created
  • 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.