Retail Pro 9 Performance Optimizations

Performance Tips:

Operating System:

Routine defrag ?

Should be scheduled to occur once a week using either Windows Defrag utility or another proven third party application such as MyDefrag.

  1. Stop the Oracle services
  2. Suspend scheduled activities such as ECM.
  3. Proceed with the defrag using the program?s conventions for scheduling.
  4. Restart the Oracle services

Extreme defrag ?

This is typically done as a one time ?fix? to a system that has had a database growing in place for some time. Usually defrag tools cannot defragment the large files this procedure addresses that problem.

  1. Fully backup the database using the TTK. To a separate physical hard drive.
  2. Confirm the backup is good by doing a test restore to a system.
  3. Stop the Oracle services
  4. Suspend scheduled activities
  5. Delete the DBF files in the \Oracle\Oradata\RPROods folder. Do not perform this step unless you have a confirmed good backup as described in step 2.
  6. Proceed with the defrag using the program?s conventions until completed
  7. Restore the DBF files from the backup made in step two. This will cause the files to be completely re written block by block (provided they were backed up to a different physical hard drive).
  8. Login and confirm functionality

Server Optimizations ?

  • Set server to allocate processor for background services.
  1. Open Start>ControlPanel>System>Advanced>Performance>Advanced>
  2. under Processor Scheduling select ?Background services?

General Optimizations -

  • Turn off unnecessary user interface visual effects.
  1. Open Start>ControlPanel>System>Advanced>Performance>Visual Effects>
  2. select the ?Adjust for best performance? option
  • Review and turn off any unnecessary services.
  1. Go into Start>Run>services.msc
  2. Review the running services and turn off an disable any un needed services (confer with the local IT admin for proper guidance)

Oracle (database)

Pre-size Database Files ?

In circumstances where you know the database is going to grow significantly, for instance if you are converting a large customer from 9i to 11g, you should increase the size of the USERS##.DBF, INDX##.DBF and the UNDOTBS##.DBF by at least 1.5 times the size of the old database ahead of time.

Archive and Redo separation -

There is a nominal speed advantage to storing the redo and archive log files on different physical drives. The reason is that the archive logs are archived versions of used redo logs. Copying files from one drive to another is quicker then copying from one folder to another on the same drive. It is a safer practice to keep your archive files on a separate drive in case you have a database failure.

To change the location of the archive log files you can manually adjust the INIT.ORA file using the instructions below:

  • Create the destination folder that you are going to store archive logs in.
  • Using Windows explorer browse to [drive]:\Oracle\admin\RproODS\pfile
  • Make a copy the INIT.ORA file that is that folder before editing it.
  • Locate this string in the INIT.ORA file log_archive_dest= and change the path to the one you want.

EXAMPLE log_archive_dest=E:\archives

  • Restart the RPROODS service.

Once the service has been restarted the new setting will be applied and archives will go to the new location.

NOTE: The logs that have been created up to that point will NOT be moved as a result of changing this setting in the INIT.ORA. You must move the existing Archive log files manually through Windows explorer to the new location.

Memory Target Adjustment -

Oracle memory allocation can be manually adjusted in order to optimize the amount of RAM made available to Oracle on the system. To learn how to adjust the amount of memory that Oracle has at its disposal for processing review the following KB Articles

32bit OS-

64bit OS-

Re-index -

Reordering and consolidating the database indices via the TechToolkit will allow them to perform more efficiently. To re ?index use the instructions below and perform it at least 1 time a week.

  • Launch the TechToolkit.exe and browse Use Techtoolkit.exe Data Maintenance > Reindexing > Start.

NOTE this task can be scheduled. Review the command line parameters documentation for details on how to do that. This document is available on the documentation portalĀ

Keyword: ?command line?

Tuning (FULL)-

Tuning optimizes the way that Oracle accesses information in the database. It uses a ?cost value? to determine the best way to access data. This cost value becomes out of date as the information in the database changes or grow. It is important to tune after every re-index, large data import and as a regular maintenance task at least 1 time weekly using the TechToolkit. Below are the instructions on how to do this manually in the TechToolkit.

  • Techtoolkit.exe (Data Maintenance > Tuning > Start). Perform tuning regularly, at least

NOTE this task can be scheduled. Review the command line parameters documentation for details on how to do that. This document is available on the documentation portalĀ

Keyword: ?command line?


Tuning should always be run after Re index

More Performance Tuning Resources

There are more performance optimization tips for 9 series in the V9_System_Performance_maintenance.PDF which is available on the documentation portal.

Keyword ?performance?

Published on Mar 18, 2014 in Database, Performance


Find Another Article