SGA_TARGET Has To Be 1GB To Start Up A Database On SPARC-T3 Server With 128 Virtual CPUs
Last updated on MARCH 14, 2013
Applies to:Oracle Database - Standard Edition - Version 22.214.171.124 and later
Information in this document applies to any platform.
Customer is trying to migrate 50 databases from an old Solaris server UltraSPARC-IIIi to a new SPARC-T3 server with 128 for the CPU_COUNT.
The database on the old server requires 300MB SGA_TARGET to startup. On the new server the same database requires 1GB to startup, otherwise they get an Ora-4031 error.
There is only 32GB memory on the new server, which means they can not host 50 databases.
CPU information on the old server:
The physical processor has 1 virtual processor (0)
UltraSPARC-IIIi (portid 0 impl 0x16 ver 0x34 clock 1592 MHz)
The physical processor has 1 virtual processor (1)
UltraSPARC-IIIi (portid 1 impl 0x16 ver 0x34 clock 1592 MHz)
The physical processor has 1 virtual processor (2)
UltraSPARC-IIIi (portid 2 impl 0x16 ver 0x34 clock 1592 MHz)
The physical processor has 1 virtual processor (3)
UltraSPARC-IIIi (portid 3 impl 0x16 ver 0x34 clock 1592 MHz)
CPU information on the new server:
The physical processor has 128 virtual processors (0-127)
SPARC-T3 (chipid 0, clock 1649 MHz)
The workaround described on Note 815426.1 does work. Customer can set the database not to use ASMM, but it still needs a very large shared pool (580M) to start up the database. Settings as follows:
The total SGA size used by the database is over 1.2G:
Fixed Size 2168040 bytes
Variable Size 734006040 bytes
Database Buffers 536870912 bytes
Redo Buffers 9297920 bytes
Customer has also applied patch for Bug 8316255 which did not resolve the issue.
Moved to a new server with a different number of CPU's and Threads per core.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms