Sga_target set more than 100G a bug encountered Ora-00064:object is too large

Host memory 256g,sga_target ready to set to 160G,DBCA when creating a database Ora-00064:object is too large to allocate on this O/S (1,15429280)

Directly using the DBCA default parameters to build the library, again using the command to modify, error is still. After checking, the reference document database startup can fail with the ORA-00064 Errors with the huge sga_target of over 40Gig (document ID 886312.1), that is, with the SGA Gra Nule Size Correlation, set _ksmg_granule_size=33554432 to resolve this issue.

Part of the document:

CauseThe cause of this problem have been identified inbug:5051962, which has been closed as not-a-bug. It is caused by the granule size needed for the new SGA size to being different than the one currently in use by the instance At the time of the ALTER SYSTEM SET sga_target command is run.SolutionThis is expected Behaviour:the granule size was set based on the size of the SGA. If you set a SGA parameter (such as Sga_target) to a value which exceeds the value of the granule size it was calulcated At instance startup, then you must set the _ksmg_granule_size instance parameter as well to choose a larger granule size. As this parameter isn't dynamically changeable, an instance restart is required.

The following table, shows granule sizes for specific SGA sizes and releases of Oracle:

SGA Size	10g granule Size	11g granule Size	11g granule Size With fix 8813366 installed
<= 1GB	4MB	4MB	4MB
1gb-4gb	16MB	16MB	16MB
4gb-8gb	16MB	64MB	16MB
8gb-16gb	16MB	64MB	32MB
16gb-32gb	16MB	256MB	64MB
32gb-64gb	16MB	256MB	128MB
64gb-128gb	16MB	512MB	256MB
128gb-256gb	16MB	512MB	512MB
> 256GB	16MB	512MB	512MB

See also document:947152.1For details on the granule size and its impact.

The following SQL statement can be used to check the actual granule a size in use by the instance:
SQL> select bytes from v$sgainfo where name like ‘Granule Size‘;
so-in order-implement the solution for the issue at hand, either:

1. Set Sga_target to a value less than or equal to the previous one, or:
2. Set _ksmg_granule_size to a higher value (the value of the is set to 32MB). When using a text parameter file, add the following parameter:
   _ksmg_granule_size=33554432
   When using a server parameter file, issue:
   alter system set "_ksmg_granule_size"=33554432 scope=spfile;
   In either case, restart the instance for the changes-take effect.

Sga_target Setting a bug that is larger than 100G Ora-00064:object is too large