Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • age_alert.ksh aging out alert.log Linux/Unix
  • ipcs -l Linux/Unix
  • fkwoindex.sql /* Find FK without Index */ Oracle
  • Another export with Query Oracle
  • Python class import from different folders Python/PySpark
  • create database link syntax Oracle
  • How to analyze statspack or AWR report. Oracle
  • export import with parameter file. Oracle
  • sesswait.sql Oracle
  • compile_inv.sql Oracle
  • Adding addidional hard drive and attach it to a linux box. Linux/Unix
  • shutdown linux Linux/Unix
  • To see how much time or progress of long transaction Oracle
  • Unix command for system configuration Linux/Unix
  • Index Range Scan 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

  • CPU Core related projections AWS
  • runon_allpdbs_show_conname.sh Oracle
  • Rollback force for distributed transactions Oracle
  • EXTPROC Oracle
  • pvm_metric.sql for gathering report from vmstat tables Oracle
  • Temporary Tablespace Information and restriction. 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 (403)
  • PHP/MYSQL/Wordpress (10)
  • POSTGRESQL (1)
  • Power-BI (0)
  • Python/PySpark (7)
  • RAC (18)
  • rman-dataguard (26)
  • shell (150)
  • SQL scripts (350)
  • SQL Server (6)
  • Uncategorized (5)
  • Videos (0)

Recent Posts

  • 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.sql23-Apr-2026
  • Running PDB on single node in RAC09-Apr-2026
  • find_arc.sql09-Apr-2026
  • pvm_pre_change.sql08-Apr-2026
  • find_encr_wallet.sql08-Apr-2026
  • find_pdbs.sql08-Apr-2026

Archives

  • 2026
  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • Very clear article about oracle dataguard Oracle
  • restarting network in linux Linux/Unix
  • tblwopk.sql /* Find Tables Without PK */ Oracle
  • v$event_name Oracle
  • Oracle Identifiers Oracle
  • currwaitobj.sql SQl_ID and SQL statement you can get from currwaitobj.sql Oracle
  • Find long Running Transaction Linux/Unix
  • create trigger syntax Oracle

Copyright © 2026 pvmehta.com.

Powered by PressBook News WordPress theme