Note: This SAS Note applies to SAS Financial Management 5.3 and earlier releases.

If you are experiencing slow query performance or OutOfMemory errors in SAS Financial Management, check the memory arguments (MEM_ARGS) in the start-up settings for your SASManagedServer and your SASODCSServer (SAS Financial Management release 4.x) or your SASServer3/SASServer4 (release 5.x).

Initially, the MEM_ARGS might be set to one of the following:

• -Xms512m -Xmx512m
• -Xms860m -Xmx860m

This setting tells the Oracle WebLogic Server to allocate a minimum and a maximum of 512 (or 860) MB of memory for the Java Virtual Machine (JVM) heap size.

Check Memory Settings

Since you have the ability to start your WebLogic servers as a Windows service from the WebLogic Server Administration Console or manually, it is important to confirm the memory arguments that are defined for each method of starting the servers, because these settings might differ.

Checking the Windows registry entries is the definitive way to determine the memory settings for the most recent time the WebLogic servers were started:

1. On the mid-tier server, select Start ► Run and enter REGEDIT to access the Registry Editor.


2. Navigate the registry tree as follows:
   
   • For SAS Financial Management 4.x: HKEY_LOCAL_MACHINE ► SYSTEM ► CurrentControlSet ► Services ► beasvc SASSolutions_XServer_Lev1 (where X = 'SASManaged' or 'SASODCS') ► Parameters.
     In the right pane, double-click the command line item and verify the -Xms and -Xmx settings from the Value data field for both the SASManagedServer and the SASODCSServer.
     Note: It might be easier to verify the settings if you copy of the entire contents of the Value data field to a text editor.
   
   
   • For SAS Financial Management 5.x: HKEY_LOCAL_MACHINE ► SYSTEM ► CurrentControlSet ► Services ► SASDomain_SASServerX (where X = a number from 1 to 5) ► Parameters.
     In the right pane, double-click the command line item and verify the -Xms and -Xmx settings from the Value data field for all five of the WebLogic servers.
     Note: It might be easier to verify the settings if you copy of the entire contents of the Value data field to a text editor.

Maximize Memory Settings

If you are working with large models and/or queries, you will likely want to maximize the memory arguments, particularly for SASServer4/SASODCSServer and (to a somewhat lesser extent) for SASServer3/SASManagedServer.

For an installation on a 32-bit operating system, the minimum server memory (RAM) requirement is 4 GB RAM, so you can increase these settings to a maximum of 1280m. This increase applies to both -Xms and -Xmx on the SAS Managed Server and the SAS ODCS Server (primarily for SAS Financial Management release 4.x).

For a 64-bit operating system installation, the amount of memory you can allocate to each server is a function of the total memory (RAM) available on the physical server and what resources are consumed by other processes that run on that same machine:

• For SAS Financial Management 4.x:
  To increase the MEM_ARGS settings, edit the following files:
  • If starting as a Windows service, edit the installSASManagedService.cmd and installODCSService.cmd files.
  • If starting interactively, edit the startManagedWebLogic.cmd and startODCSWebLogic.cmd; files.
  The default location for these files on the middle tier machine is your-drive:\bea\user_projects\domains\SASSolutions.
• For SAS Financial Management 5.x:
  
  • To increase the MEM_ARGS settings, edit the SASServer3 and SASServer4 Start Arguments in the WebLogic Server Administration Console. The default URL to access the WebLogic Server Administration Console on the middle tier machine is: http://servername:7501/console. The default logon credentials are:
    • User name: weblogic
    • Password: AdminAdmin1
    Note: The credentials might be different for your site.
  • Make any necessary changes to -Xms and -Xmx settings for each application server and save the files.

  Implement New Memory Settings

  For both SAS Financial Management 4.x AND SAS Financial Management 5.x:
  If you make changes to the memory settings for the WebLogic servers and your WebLogic servers are started interactively (either via a start-up script or via the WebLogic Server Administration Console), you must execute the command files in order to restart your servers and have the new memory settings take effect.

For both SAS Financial Management 4.x AND SAS Financial Management 5.x:
If you make changes to the memory settings for the WebLogic servers and your WebLogic servers are started as a Windows service, you must uninstall and reinstall the service. To accomplish this, complete these steps:


1. Be sure that your SASManagedServer/SASServer3 and SASODCSServer/SASServer4 have been stopped.
   To do so, navigate to your Windows Services window and stop the services in this order:
   For SAS Financial Management 4.x:
   
   • beasvcSASSolutions_SASManagedServer
   • beasvcSASSolutions_SASODCSServer
   
   For SAS Financial Management 5.x:
   
   • SASDomain SASServer4
   • SASDomain SASServer3


2. Open a command prompt.


3. Navigate to the following path:
   
   • For SAS Financial Management release 4.x, your-drive:\bea\user_projects\domains\SASSolutions
   • For SAS Financial Management release 5.x, your-drive:\bea\wlserver_10.3\server\bin
   This path assumes that your installSASManagedService.cmd and installODCSService.cmd files (for SAS Financial Management release 4.x) or installSvc.cmd file (for SAS Financial Management release 5.x) are installed in this directory. If not, modify the path accordingly.


4. If no changes were made to the installODCSService.cmd file, skip to step 8.
   If changes were made to your installODCSService.cmd file, you must uninstall and reinstall the service.
   To uninstall the service, enter the following at the command prompt:
   UninstallODCSService.cmd


5. Once the service has been uninstalled, you see a message similar to:
   beasvc SASSolutions_SASODCSServer removed.
   The window returns to a command prompt.
   Return to your Windows Services window. Select Action ► Refresh and ensure that beasvcSASSolutions_SASODCSServer no longer appears in the list of available services.


6. You now must reinstall the service by entering the following at the command prompt:
   InstallODCSService.cmd


7. Once the service has been reinstalled, you see a message similar to:
   beasvc SASSolutions_SASODCSServer installed
   The window returns to a command prompt.
   Return to your Windows Services window. Select Action ► Refresh and ensure that your beasvcSASSolutions_SASODCSServer now appears in the list of available services.


8. If no changes were made to the installSASManagedService.cmd file, skip to step 12.
   If changes were made to the installSASManagedService.cmd file, you must uninstall and reinstall the service.
   To uninstall the service, first perform steps 1 - 3, above.
   Next, enter the following at the command prompt:
   UninstallSASManagedServerService.cmd


9. Once the service has been uninstalled, you see a message similar to:
   beasvc SASSolutions_SASManagedServer removed
   The window returns to a command prompt.
   Return to your Windows Services window. Select Action ► Refresh and ensure that beasvcSASSolutions_SASManagedServer no longer appears in the list of available services.


10. You now must reinstall the service. To reinstall the service, enter the following at the command prompt:
    InstallSASManagedService.cmd


11. Once the service has been reinstalled, you see a message similar to:
    beasvc SASSolutions_SASManagedServer installed
    The window returns to a command prompt.
    Return to your Windows Services window. Select Action ► Refresh and ensure that beasvcSASSolutions_SASManagedServer now appears in the list of available services.


12. You should now be able to restart both the SAS^® ODCS Server and the SAS^® Managed Server and continue working with SAS Financial Management.
    To do so, navigate to your Windows Services window and start the services in this order:
    
    • beasvcSASSolutions_SASODCSServer
    • beasvcSASSolutions_SASManagedServer




Operating System and Release Information

Product Family	Product	System	SAS Release
			Reported	Fixed*
SAS System	SAS Financial Management	Microsoft Windows 2000 Datacenter Server
		Microsoft Windows 2000 Server
		Microsoft Windows 2000 Professional
		Microsoft Windows Server 2003 Datacenter Edition
		Microsoft Windows Server 2003 Enterprise Edition
		Microsoft Windows Server 2003 Standard Edition
		Microsoft Windows XP Professional
		64-bit Enabled AIX
		64-bit Enabled Solaris
		Microsoft Windows 2000 Advanced Server

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.