milly
6:55 pm on January 14, 2010 |
Answers: 1
Tags: database (51), error (67), k
ora-, memory (16), ora (7), oracle (136), pool (3), server (37), startup (27) 
Loading ...Resolving Oracle ORA-12853 error in Windows Server Environment during startup
I was getting the following ORA- error:
SQL> startup
ORA-12853: insufficient memory for PX buffers: current 0K, max needed 144K
ORA-04031: unable to allocate 21616 bytes of shared memory ("large pool","unknown object","large pool","PX msg pool")
Resolving Oracle ORA-32690: Hash Table Infrastructure Ran out of MemoryResolving Oracle Database ORA-12638 Error in WindowsResolving ORA-12518: TNS:listener Could Not Hand off Client Connection Error
Resolving Oracle “ORA-00942: table or view does not exist ” ErrorTroubleshooting and Resolving “ORA-00904: string: invalid identifier” Error
milly 6:55 pm on January 14, 2010
After some troubleshooting, I discovered that my SGA_TARGET parameter is causing the issue. Initially I set SGA as:
However, Oracle did not take the value and threw ORA-12853
After some troubleshooting, I changed the value to 12000M and Oracle starts up without issues.
Therefore, if you encounter ORA-12853 error, try to adjust your SGA_TARGET parameter.