Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • SQL_PROFILE – I explaination Oracle
  • tblwopk.sql /* Find Tables Without PK */ Oracle
  • remove archfiles only when it is applied to DR rm_archfiles.sh Linux/Unix
  • create PLAN_TABLE command. Oracle
  • Add new columns in dataframe Python/PySpark
  • Nice Article about semaphores and init.ora Processes parameter relations Linux/Unix
  • chk_space_SID.ksh Linux/Unix
  • secure crt settings Linux/Unix
  • Important Script Method for tuning Oracle
  • nfs mount command Linux/Unix
  • Wait Based Tuning Step by step with SQL statement Oracle
  • Pending Distributed Transations Oracle
  • Temporary tablespace explaination Oracle
  • grep multuple patterns Linux/Unix
  • Resolving RMAN Hung Jobs 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

  • Virtual Indexes in Oracle Oracle
  • Finding locked objects Oracle
  • Find all users who have DML privileges Oracle
  • 10g oem configuration Oracle
  • crtgr.sql /* For creating trigger from data dictionary */ Oracle
  • Rename Oracle Instance Name 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 (395)
  • PHP/MYSQL/Wordpress (10)
  • POSTGRESQL (1)
  • Power-BI (0)
  • Python/PySpark (7)
  • RAC (17)
  • rman-dataguard (26)
  • shell (150)
  • SQL scripts (343)
  • SQL Server (6)
  • Uncategorized (0)
  • Videos (0)

Recent Posts

  • prepfiles.sh for step by step generating pending statistics files10-Mar-2026
  • 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

Archives

  • 2026
  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • Disbaling DBA_SCHEDULER_JOBS Oracle
  • Identical Dblink Issue… Oracle
  • Removing first line Linux/Unix
  • create database link syntax Oracle
  • PLSQL Table Syntax 1 Oracle
  • How to know Number of CPUs on Sun Box Linux/Unix
  • secure crt settings Linux/Unix
  • SQL_PLAN.sql for checking real execution plan Oracle

Copyright © 2026 pvmehta.com.

Powered by PressBook News WordPress theme