Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • Temporary Tablespace Information and restriction. Oracle
  • longtx.sql with the flag whether session is blocking any DML locks or not. Oracle
  • Find All internal Parameters Oracle
  • get_aix_vmstat.ksh Oracle
  • crontab syntax Linux/Unix
  • Find execution plan from dba_hist_sql_plan for a specific SQL_ID and PLAN_HASH_VALUE fplan.sql Oracle
  • SAN Linux/Unix
  • Monitor Long Running Job Oracle
  • How To Transfer Passwords Between Databases (ref note: 199582.1) Oracle
  • Gather Stats manually using DBMS_STATS after disabling DBMS_SCHEDULER jobs as previous entry Oracle
  • Search and replace editor command in vi Linux/Unix
  • Search and replace pattern Linux/Unix
  • MYSQL for Oracle DBA MYSQL
  • Oracle vs MYSQL Architecture differences (For DBAs) MYSQL
  • SQL Tracker by SID sqltrackerbysid.sql 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

  • Building Our Own Namespaces with “Create Context” Oracle
  • alter database backup controlfile to trace Oracle
  • PLSQL Table Syntax 2 Oracle
  • 751131.1 New Article Error 2819 While Requesting a Systemstate Dump Oracle
  • How to specify 2 arch location to avoid any kind of DB hanging. Oracle
  • plan10g.sql 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 (393)
  • PHP/MYSQL/Wordpress (10)
  • POSTGRESQL (1)
  • Power-BI (0)
  • Python/PySpark (7)
  • RAC (17)
  • rman-dataguard (26)
  • shell (149)
  • SQL scripts (342)
  • SQL Server (6)
  • Uncategorized (0)
  • Videos (0)

Recent Posts

  • 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
  • Oracle vs MYSQL Architecture differences (For DBAs)24-Jul-2025

Archives

  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • lck.sql Oracle
  • Goldengate document from Porus Oracle
  • Good notes for shared pool Oracle
  • DB Console Mainenance. Oracle
  • TRUNCATE Privs Oracle
  • create trigger syntax Oracle
  • Adding or Dropping Online Redo Log Files When Physical Standby in place Oracle
  • Important Script Method for tuning Oracle

Copyright © 2026 pvmehta.com.

Powered by PressBook News WordPress theme