Tuning the Oracle Forms client (F45RUN32) for Better Performance
Tuning the Oracle Forms client (F45RUN32) for Better Performance Tuning the Oracle Forms client (F45RUN32) for Better Performance
Citrix states in their article: CTX725040
CTX725040 - Tuning the Oracle Forms client (F45RUN32) for Better Performance
This document was published at: http://support.citrix.com/kb/entry.jspa?externalID=CTX725040
Document ID: CTX725040, Created on: Jun 30, 2000, Updated: Apr 23, 2003
Products: Citrix WinFrame 1.8
Loading Oracle Forms may improve by following these steps:
The below registry location is for WinFrame 1.x.
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
1. Find the Registry key HKEY_LOCAL_MACHINESOFTWARE CitrixCompatibility ApplicationsF45RUN32:
2. Add the following settings:
FirstCountMsgQPeeksSleepBadApp=0x1
Flags=0x8
MsgQBadAppSleepTimeInMillisec=0
NthCountMsgQPeeksSleepBadApp=0x1
Note: For the proper Terminal Server 4.0 registry locations, see Q186628 and Q198060. Some applications that perform normally on WinFrame 1.x and Windows NT 4.0, Terminal Server Edition consume 100% of the CPU resources under Windows 2000 with Terminal Services. Microsoft removed the "bad app" detection from Windows 2000. Check with Microsoft for hotfixes for specific applications on Windows 2000. Therefore, the above registry keys for WinFrame and Terminal Server Edition are not valid in Windows 2000.
TroubleShooting Tips when Running Reports with Forms 4.5
1. Does the issue happen with all users including administrators? If so, this could indicate a rights, n:orantreports45temp, or profile issue.
2. Does the issue happen on the console and/or with a RDP desktop session? This could indicate an application performance issue.Can I run Forms on NT Terminal Server Edition (or Citrix Winframe)? Answer: No. We do not support Forms deployed in this kind of configuration.
3. Can the issue be isolated to a printer driver?
4. Do newer versions of Oracle Forms exhibit the same problem?
5. The 4.5 Oracle Forms client had 16-bit and 32-bit versions, the 32-bit version of the client is preferred.
6. If the report is running from the client, then the form may be too large for the client buffer. Configure the client to run the report on the UNIX box instead of the Terminal Server.
User login
Who's new
- maczugaher
- locksgydff
- isotheces
- ahundredyears7
- Jacomijntjefu