Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • Logic to chech # of parameters command line parameters Linux/Unix
  • scripts to take listener.log backup Linux/Unix
  • sbind.sql Find Bind variable from sql_id sqlid Oracle
  • Unix command for system configuration Linux/Unix
  • TOP-N Sql to find Nth max or Top N rows Oracle
  • Some useful Unix Commands Linux/Unix
  • Find_stale_dr.sql finding stale physical DR.. Oracle
  • MYSQL for Oracle DBA MYSQL
  • Mutating Table Error while using database trigger Oracle
  • Test Case for Inserting Multiple (2.3 Million rows in 26 Seconds) Oracle
  • setting prompt display with .profile Linux/Unix
  • Renaming Oracle Instance Name Oracle
  • Distributed Transaction Troubleshooting. Oracle
  • Linux CPU info. Linux/Unix
  • grep multuple patterns Linux/Unix

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

  • findinfo.sql (SQL for getting CPU and Active session info) Oracle
  • UNderstand and eliminate Latch contention. Oracle
  • V$transaction notes for finding XID composition. Oracle
  • Good Doc 28-JUN-2006 Oracle
  • Ports used by Oracle Software Oracle
  • column level grant syntax Oracle

Leave a Reply Cancel reply

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

Categories

  • Ansible (0)
  • AWS (2)
  • Azure (1)
  • Django (0)
  • GIT (1)
  • Linux/Unix (149)
  • MYSQL (5)
  • Oracle (394)
  • PHP/MYSQL/Wordpress (10)
  • POSTGRESQL (1)
  • Power-BI (0)
  • Python/PySpark (7)
  • RAC (17)
  • rman-dataguard (26)
  • shell (149)
  • SQL scripts (343)
  • SQL Server (6)
  • Uncategorized (0)
  • Videos (0)

Recent Posts

  • tracksqltime.sql05-Mar-2026
  • Complete Git Tutorial for Beginners25-Dec-2025
  • Postgres DB user and OS user.25-Dec-2025
  • Trace a SQL session from another session using ORADEBUG30-Sep-2025
  • SQL Server Vs Oracle Architecture difference25-Jul-2025
  • SQL Server: How to see historical transactions25-Jul-2025
  • SQL Server: How to see current transactions or requests25-Jul-2025
  • T-SQL Vs PL/SQL Syntax25-Jul-2025
  • Check SQL Server edition25-Jul-2025
  • Checking SQL Server Version25-Jul-2025

Archives

  • 2026
  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • Find all users who have DML privileges Oracle
  • To find all disk io ( EMC as well as local) Linux/Unix
  • Postgres DB user and OS user. POSTGRESQL
  • Btee and Bitmap Plans in Oracle 9i and higher Oracle
  • ENQ: KO – FAST OBJECT CHECKPOINT tips Oracle
  • upload.html PHP/MYSQL/Wordpress
  • Good Site for Oracle Internals Oracle
  • Renaming the column name Oracle

Copyright © 2026 pvmehta.com.

Powered by PressBook News WordPress theme