Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • Example of How To Resize the Online Redo Logfiles Note:1035935.6 Oracle
  • Multiple listeners Oracle
  • eplan9i.sql Oracle
  • usnsql.sql Displays information about UNDO segments with sql statements Oracle
  • Formatter Explain plan Output 1 Oracle
  • DBMS_PROFILER for tuning PLSQL programs. Oracle
  • Important Script Method for tuning Oracle
  • restarting network in linux Linux/Unix
  • to see when crontab is changed. Linux/Unix
  • database trigger failing Oracle
  • moving lob object to other tablespace lob_mvmt.sql Oracle
  • cif crons Linux/Unix
  • create trigger syntax Oracle
  • scripts to take listener.log backup Linux/Unix
  • Follwoing korn shell is used to move files from source folder to destination folder and gzip it in destination folder. mv_iotto.ksh 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

  • My Minimum Tuning Programs Oracle
  • Identical Dblink Issue… Oracle
  • USE_NL and INDEX hints example Oracle
  • oracle Dba site Oracle
  • Renaming Global Name GLOBAL_NAME Oracle
  • Roles and Stored Procs II 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
  • CPU speed on Linux Linux/Unix
  • create PLAN_TABLE command. Oracle
  • Clean up Oracle
  • Adding Datafile on Primary Server and Impact on Standby Server Oracle
  • standard Monitoring – 1 Oracle
  • v$backup.status information Oracle
  • find the files that are 1 day old. Linux/Unix
  • Changing default shell Linux/Unix

Copyright © 2026 pvmehta.com.

Powered by PressBook News WordPress theme