Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • get_vmstat.ksh for Solaris Oracle
  • Jai Shree Ram Linux/Unix
  • Sending email with file attachment. Linux/Unix
  • get_vmstat.ksh Linux/Unix
  • How to Make Trace Files Created by Oracle Readable by All Users ? Oracle
  • shr1.sql for MTS or Shared server configuration Oracle
  • Rman Notes -1 Oracle
  • Load testing on Oracle 19C RAC with HammerDB Oracle
  • prepfiles.sh for step by step generating pending statistics files Oracle
  • Oracle Connections expire_time and firewall Oracle
  • Oracle 11g Environment Setup Oracle
  • How to find pinned objects from shared pool. (pinned via dbms_shared_pool.keep) Oracle
  • kill all processes from specific user in solaris. Linux/Unix
  • crtgr.sql /* For creating trigger from data dictionary */ Oracle
  • sqlnet.ora paramters Oracle

ORA-00064: object is too large to allocate on this O/S during startup

Posted on 25-Jun-2008 By Admin No Comments on ORA-00064: object is too large to allocate on this O/S during startup

(1) When you attempt to set the ‘Processes’ parameter to high value (for example> 14000), the instance startup fails with

ORA-00064: object is too large to allocate on this O/S ORA-00064: object is too large to allocate on this O / S.

Solution:

Change PROCESSES parameter.

or

The workaround to bypass this limit is to set the hidden parameter _ksmg_granule_size to 32M or reduce the value of processes parameter.

Example (using spfile): Example (using spfile):

SQL> alter system set “_ksmg_granule_size”=32M scope=spfile;

Another reason:

The initialization parameter DB_BLOCK_SIZE is set to a value that calls for more contiguous space than can be allocated on the operating system being used.

Action: Reduce the value of DB_BLOCK_SIZE so that the requested contiguous space is within the capacity of the operating system.

Another reason:

ORA-00064 error is possibly encountered on database startup when the parameter

OPEN_LINKS_PER_INSTNACE set to over 400 OPEN_LINKS_PER_INSTNACE set to over 400.

Oracle, SQL scripts

Post navigation

Previous Post: standard Monitoring – 1
Next Post: how to find VIP from ifconfig

Related Posts

  • sbind.sql Find Bind variable from sql_id sqlid Oracle
  • V$transaction notes for finding XID composition. Oracle
  • How to choose Driver table in SQL statement Oracle
  • Benefits and Usage of RMAN with Standby Databases Oracle
  • TABLE SIZING WITH DB_BLOCK ARCHITECTURE Reference : Metalink note : 10640.1 Oracle
  • Pending Distributed Transations Oracle

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Categories

  • AMC10 (0)
  • Ansible (0)
  • AWS (2)
  • Azure (1)
  • Django (0)
  • GIT (1)
  • Linux/Unix (150)
  • MYSQL (5)
  • Oracle (403)
  • PHP/MYSQL/Wordpress (10)
  • POSTGRESQL (1)
  • Power-BI (0)
  • Python/PySpark (7)
  • RAC (18)
  • rman-dataguard (26)
  • shell (151)
  • SQL scripts (349)
  • SQL Server (6)
  • Uncategorized (9)
  • Videos (0)

Recent Posts

  • Tutornet.US — Source of excellent learning14-Oct-2026
  • OCI Infrastructure Patching14-Oct-2026
  • Free API credits for AI models14-Oct-2026
  • AMC1020-Sep-2026
  • Key Management in Oracle: The Core Issue: Missing Master Key12-May-2026
  • SAT Mathematics 10 questions and answer at the end.30-Apr-2026
  • top 10 AI news today30-Apr-2026
  • runon_allpdbs_show_conname.sh23-Apr-2026
  • runon_allcdbs_find_pdbs.sh23-Apr-2026
  • Running PDB on single node in RAC09-Apr-2026

Archives

  • 2026
  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • sid_wise_sql.sql Further explaination Oracle
  • TRUNCATE Privs Oracle
  • Useful Solaris Commands on 28-SEP-2005 Linux/Unix
  • Oracle Material from OTN Oracle
  • rm_backup_arch_file.ksh Linux/Unix
  • ORA-1841 Error Connecting to Upgraded Database After Set PASSWORD_LIFE_TIME Oracle
  • Some useful Unix Commands Linux/Unix
  • oracle 11g RAC on vmware Oracle

Copyright © 2026 pvmehta.com.

Powered by PressBook News WordPress theme