Dear Experts,
I had a problem when applying archive log through SQLPLUS by command "recover database using backup control file until cancel".
Usually 1 archive log just need 10s, now 1 archive log need 3 minutes. It's pretty long.
Before applying archive log, I found warning message on alertSID.log when I executed startup mount:
WARNING: -------------------------------
WARNING: oradism not set up correctly.
Dynamic ISM can not be locked. Please
setup oradism, or unset sga_max_size.
[diagnostic 0, 8, 303]
Here is the parameter on spfile and initSID.ora:
sga_max_size : 30GB
pga_aggregate_target: 6GB
db_cache_size Size: 27GB
I tried to reduce the parameters became:
sga_max_size : 4.3GB
pga_aggregate_target: 3GB
db_cache_size Size: 2GB
And the performance for apply archive log back to normal which is 10s per archive log.
Just curious here, why the parameters must be reduced before applying archive log?
Whether the OS reject the parameters? I found on the internet, this is a solaris bug like memory locking, is it true?
Thank You
Edy