Optim™ is a Windows application and has the following requirements.
On HP-UX PA-RISC architectures, Oracle versions 9i and later provide both 64-bit and 32-bit libraries. The directory for the 32-bit library must be on the 32-bit shared library path (SHLIB_PATH). Optim supports the HP-UX Itanium architecture in 32-bit emulation mode only.
On Solaris SPARC, Oracle versions 10g and later provide both 64-bit and 32-bit libraries. The directory for the 32-bit library needs to be on the shared library load path (LD_LIBRARY_PATH). Optim does not support the Solaris x86 architecture.
You must manually edit the Optim environment setup script rt/rtsetenv, and change the RTORACLELIB environment variable definition in that file based on your Oracle environment. The shell file rt/rtsetenv contains comments describing how to make the necessary changes.
Optim requires certain hardware equipment and memory. See the detailed system requirements document on the IBM support site for information about your version of the Optim solutions.
Physical memory (RAM) requirements depend on the version of Windows you have installed (refer to the system requirements for your Windows version). The actual memory required for acceptable performance will depend on the number of Optim components that are open (for example, dialogs, Optim Server, ODBC server), as well as the number of open tables, the number of rows being read, and the size of their column data. It will also depend on the memory demands of all other applications and services active on the system. In all cases, it will be greater than the minimum amount of memory suggested by the Windows system requirements.
Since Windows is a virtual memory operating system, it can access more memory than actual physical memory. It does this by writing pages (sections of memory) that are not currently referenced to a “page file” on disk. When a page is referenced that is not in memory, Windows loads it back into physical memory. To do this, it must make room for the page by “swapping” it with another page, which in turn is written to the page file. Therefore, the more physical RAM a workstation has, the less swapping needs to be done and performance improves greatly.
The amount of virtual memory (page file space) required will depend on the memory usage of all applications, services, and processes that are running. Having a small amount of physical memory (RAM) means a slower system since time is spent swapping to and from a page file. However, having an insufficient amount of disk space allocated for virtual memory can cause one or more applications or even Windows itself to hang or terminate, sometimes with disastrous results.
For the 2000 and XP versions of Windows, the disk drives and amount of disk space reserved for the paging file (virtual memory) can be limited by user settings that can affect stability. You can view or change this value. Go to System Properties, Advanced tab, Performance Settings button, Advanced tab.