memory windows

[Andrew_80]

Has anyone ever use memory windows in 32 Bit Application ?

I specifically trying to find out if using memory windows with SAP 3.1i have any issues at all ?

Also if it can be used with HP-UX11i

It is an old technology but it is the only way to overcome the memory limitation problem.

Any advise will be greatly appreciated

[James A. Donovan]

We used to use it before we upgrade the Oracle databases to 64-bit. It's actually very simple to implement as you don't need to change anything in the Oracle binaries.

Just create a file called /etc/services.window and place the SIDs of your databases in there like so;


$ cat services.window
#
# File: /etc/services.window
# @(#)B.11.11_LR
#
# The format of this file is name followed by a space/tab followed by
# a unique user key. A memory window application uses the
# getmemwindow(1M) command to extract the user key and then passes that
# key to the setmemwindow(1M) command. Using the same key places
# those applications in the same memory window.
#
# For example:
#
# winid=getmemwindow database1
# setmemwindow -i $winid startup_script arg1 arg2 arg3.
#
QA11i 10
ERPCRP2 30
DEV11i 40


Since we were running 8.1.7.4 databases, we did run into an issue with PMON trying to automatically register with the listener over port 1521. You may need to set the LOCAL_LISTENER attribute in your listener.ora file(s). Take a look at Metalink article 235562.1

http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=235562.1

[Patrick Wallek]

We are using memory windows with our Oracle database as well without any problems. We are still on HP-UX 11.0.

Memory Windows should still work the same on 11i as far as I know.

One thing you will need to be sure you do is set the kernel parameter max_mem_window to the number of memory windows you will need. Note that this will require the kernel to be regenerated and the system rebooted.