Patch 9233832 - Setting _MAX_LUBA_STACK on logical standby not working
Hi,
we are applying Windows networking patch 31 (Patch # 9233832) on our production logical standby database
As per the read me instructions of the patch
"On Windows platforms, the _MAX_LUBA_STACK Logical standby parameter may need to be adjusted to a smaller value to reduce virtual memory usage per-process. The default is 8000000. This value should be inversely proportional to the number of apply processes applying large transactions. [For e.g. start with 4million and adjust as needed if continue to run into out-of-memory errors.]
Set SQL apply parameter as follows using SQL*Plus:
SQL> alter database stop logical standby apply;
SQL> exec dbms_logstdby.apply_set('_MAX_LUBA_STACK', 4000000);"
we are applying Windows networking patch 31 (Patch # 9233832) on our production logical standby database
As per the read me instructions of the patch
"On Windows platforms, the _MAX_LUBA_STACK Logical standby parameter may need to be adjusted to a smaller value to reduce virtual memory usage per-process. The default is 8000000. This value should be inversely proportional to the number of apply processes applying large transactions. [For e.g. start with 4million and adjust as needed if continue to run into out-of-memory errors.]
Set SQL apply parameter as follows using SQL*Plus:
SQL> alter database stop logical standby apply;
SQL> exec dbms_logstdby.apply_set('_MAX_LUBA_STACK', 4000000);"
0