Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • Consolidated Reference List Of Notes For Migration / Upgrade Service Requests -ID 762540.1 Oracle
  • Histogram information Oracle
  • Drop database in Oracle 10g Oracle
  • Search and replace pattern Linux/Unix
  • useful dg links Oracle
  • oracle tips… from http://www.bijoos.com/oracle/douknow.htm Oracle
  • reset Sequence Oracle
  • Processes parameter and its dependencies on OS kernel parameters Linux/Unix
  • Privileges Required to Create Procedures and Functions that uses objects from other schema. Oracle
  • How to connect to Oracle Database with Wallet with Python. Oracle
  • get_aix_vmstat.ksh Oracle
  • Goog notes on X$ tables Oracle
  • get_vmstat_solaris Oracle
  • When to rebuld B-tree index Oracle
  • Shuffle an array PHP/MYSQL/Wordpress

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

  • ORA-8031 issue and solution if it is occuring due to truncate. Oracle
  • Updated LCK.SQL file. Oracle
  • When error comes for temporary tablespace with version <= 9i Oracle
  • v$backup.status information Oracle
  • dbms_job.submit example Oracle
  • Find average Row Length and other table size calculation. metalink notes Oracle

Leave a Reply Cancel reply

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

Categories

  • Ansible (0)
  • AWS (2)
  • Azure (1)
  • Linux/Unix (149)
  • MYSQL (5)
  • Oracle (393)
  • PHP/MYSQL/Wordpress (10)
  • POSTGRESQL (0)
  • 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

  • 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
  • V$INSTANCE of Oracle in MYSQL24-Jul-2025
  • Day to day MYSQL DBA operations (Compared with Oracle DBA)24-Jul-2025

Archives

  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • Recovering lost SYS password Oracle
  • Shuffle an array PHP/MYSQL/Wordpress
  • Implementing Listener Security Oracle
  • standard Monitoring – 1 Oracle
  • Absolute file number and relative file number Oracle
  • Virtual Indexes in Oracle Oracle
  • Drop all SPM baselines for SQL handle Oracle
  • To find all disk io ( EMC as well as local) Linux/Unix

Copyright © 2025 pvmehta.com.

Powered by PressBook News WordPress theme