ORA-27151: buffer not large enough to hold process ID string

Cause : internal error

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

contact Oracle Support

update : 26-04-2017

ORA-27151 - buffer not large enough to hold process ID string
ORA-27151 - buffer not large enough to hold process ID string

  • ora-12718 : operation requires connection as SYS
  • ora-15122 : ASM file name 'string' contains an invalid file number
  • ora-01196 : file string is inconsistent due to a failed media recovery session
  • ora-14405 : partitioned index contains partitions in a different tablespace
  • ora-14644 : table is not subpartitioned by Hash method
  • ora-29660 : Unable to find the class defined in the EXTERNAL NAME clause
  • ora-10561 : block type 'string', data object# string
  • ora-06037 : NETDNT: connect failed, node unreachable
  • ora-01956 : invalid command when OS_ROLES are being used
  • ora-00100 : no data found
  • ora-39706 : schema 'string' not found
  • ora-00345 : redo log write error block string count string
  • ora-37173 : null dimension source data
  • ora-19951 : cannot modify control file until DBNEWID is completed
  • ora-01697 : control file is for a clone database
  • ora-38795 : warning: FLASHBACK succeeded but OPEN RESETLOGS would get error below
  • ora-02700 : osnoraenv: error translating ORACLE_SID
  • ora-29851 : cannot build a domain index on more than one column
  • ora-09809 : Unable to get user's group ID from connection
  • ora-32831 : timed out trying to acquire administration lock
  • ora-07280 : slsget: unable to get process information.
  • ora-01138 : database must either be open in this instance or not at all
  • ora-09851 : soacon: Archmon unable to lock named pipe.
  • ora-14616 : table is not subpartitioned by List method
  • ora-10646 : Too many recursive extensions during SYSTEM tablespace migration
  • ora-37133 : (XSCCOMP08) You cannot write into an aggregated VARIABLE dimensioned by a COMPRESSED COMPOSITE. Use the CLEAR AGGREGATES command to reenable write access.
  • ora-16013 : log string sequence# string does not need archiving
  • ora-16761 : resource guard could not stop SQL Apply
  • ora-01674 : data file string is an old incarnation rather than current file
  • ora-22852 : invalid PCTVERSION LOB storage option value
  • 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.