ORACLE APPLICATIONS ARCHIVES

Topicwise collection of
Postings on Mail Lists
ON
UPGRADATION & MIGRATION OF ORAAPPS



11 or 11i - Query 3

From: McClung, Ed D. [mailto:EDMCCLUNG@ESCOCORP.com]
Sent: Wednesday, 20 October 1999 07:00
To: Multiple recipients of list
Subject: 10.7SC NCA Release 11 Release 11i ???

We are currently on 10.7SC, our company really wants to be on Release 11i but Oracle keeps postponing Order management and CRM applications, the last is Q2 of 2000 and of course we cannot do business without these modules plus by experience you never want to be the first. Also in the consideration is that we have a lot of custom code to convert and test, plus how many upgrades can we ask our user world to be involved in, so our dilemma is: stay with 10.7SC since the maintenance has been extended, then to 11i when stable
or upgrade to NCA then to 11i when stable
or upgrade to 11.3 then 11i when stable
Any help, comments or experience would be much appreciated, thanks in advance,,,

Ed McClung
Database Administrator
ESCO Corporation
(503) 778-6275
(503) 778-6754 (Fax)
(503) 599-4813(pager)


Date: Wed, 20 Oct 1999 09:21:20 +1300
From: Mark Healey MHealey@swichtec.co.nz
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: 10.7SC NCA Release 11 Release 11i ???

You are not alone in your dilemma, we are in exactly the same situation. We have decided to wait until 11i, it would appear that from a users point of view 11, although it offers some further functionality does not give you any performance gains and is not a lot more presentable than the outdated look of 10.7sc. There is apparently very little functional difference between 11 and 11i so we have opted to put 11 on a test box and thrash it about until 11i is available. Would be keen to keep in touch with yourself to compare notes

Mark Healey
Swichtec Power Systems
New Zealand



7.3.3. to 7.3.4 with 10.7 Applications

Date: Thu, 28 Oct 1999 12:43:25 GMT
From: "Jennifer volkers" jennifervolkers@hotmail.com
To: OraApps-L@cpa.qc.ca
Subject: Upgrading from 7.3.3 to 7.3.4 with 10.7 Applications (Character and SC)

I would like to thank all of you for responding to my previous question. Right now i am planning to upgrade my database from 7.3.3 to 7.3.4 for ORACLE Applications 10.7 (SC and Charac). My questions are:

1. What are the potential pitfalls i can expect during this upgrade?

2. Can some one share their experience in this upgrade?

thanks a lot!
Jenny


Date: Thu, 28 Oct 1999 09:18:41 -0700
From: Andy Rivenes arivenes@llnl.gov
To: oraapps-l@cpa.qc.ca
Subject: Re: Upgrading from 7.3.3 to 7.3.4 with 10.7 Applications

The number one thing is to follow the Oracle Applications Interoperability Patch instructions for the 7.3.4 upgrade and put on the latest certified 7.3.4 patch set for your platform.

Other things to consider are init.ora changes between releases, environment setups to point to the new ORACLE_HOME, performing the actual database upgrade properly (e.g. orainst and any additional cat... scripts), and verifying object status before and after (e.g. one of the steps is to recompile packages and procedures - adadmin).

Of course testing and a dry run are always advised, but the upgrade is pretty simple from a technical standpoint.

Good luck.
Andy Rivenes
arivenes@llnl.gov


Date: Fri, 29 Oct 1999 14:00:45 -0600
From: tom prado-irwin tprado-irwin@Quark.Com
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: Upgrading from 7.3.3 to 7.3.4 with 10.7 Applications

Jennifer-

We had a problem with 7.3.4.0 (known bug# 570945) that caused the db to crash when running adadmin compile apps schema. I believe the fix is in 7.3.4.1 - we went straight to 7.3.4.4 with a patch from Oracle and that solved the problem.



10.7 SC and NCA

From: Chang Shirley [mailto:chang.shirley@bcg.com]
Sent: Wednesday, November 03, 1999 1:36 PM
To: Multiple recipients of list
Subject: 10.7 SC and NCA

We are in the process of moving from P16.1 SC to NCA.

I would appreciate if you can provide information for the following questions:
1) What's your NCA server configuration ? - In terms of CPU,memory for how many concurrent users

2) If you have converted from 10SC to NCA, did you do it at once ? Oracle does not support 10SC and NCA running in parallel against the same database server. But how to you do overnight switch of large number of users ? We have about 200 users.

3) We are switching from Citrix to NCA as middle tier - if you have switched from the same environment, what's your experience with Citrix vs. NCA. Is NCA more reliable ? Is the performance better or worse ? How does NCA server handle database server connections when a client PC does not respond ?

4) Has anyone supported multiple languages on a single NCA server ?

Shirley Chang
Boston Consulting Group, Inc.
Global Services, Information Technology
phone: +1 617 973 1214 ~ fax: +1 617 973 1399
e-mail: chang.shirley@bcg.com


From: Kathy Largay
Sent: Wednesday, November 03, 1999 2:37 PM
To: Multiple recipients of list
Subject: RE: 10.7 SC and NCA

We also moved from Citrix to NCA. In reference to #3, NCA seems more stable, and the users like the presentation much better. However, we have had to replace several PCs (for heads-down data entry folks) due to poor performance -- they really need high-end machines -- and this has solved their performance problems.

Two things that take a lot of time: 1.It appears that when someone doesn't end their connection correctly, the session continues on the NCA server, and I find myself deleting sessions on a regular basis (rebooting the server nightly helps this problem somewhat); 2.There are particular screens that seem to cause a session to eat up all available CPU on the NCA server, and everything crawls (for everyone) until we identify and end the 'rogue' process(this is very difficult -- sometimes it's a guess). We appear to have this problem with some FA screens (we also have OFU).

So I guess we find that the NCA servers need more babysitting than the Citrix servers did, but users, on the whole, are pleased.


Date: Wed, 3 Nov 1999 16:59:59 -0500
From: Chang Shirley chang.shirley@bcg.com
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: 10.7 SC and NCA

Thanks for the quick response.
Please let me know :
1) what are the patches that you applied on the database and NCA servers to support NCA.
2) what is your NCA hardware configuration, how many concurrent users that you support on this NCA server.
3) which FA forms would cause performance problem, did you get any patch from Oracle to resolve the problem ?

The following is some information that I obtained from Oracle on NCA server for session disconnect, may be you are already on the version of forms runtime (please let me know) :

Forms Server Heartbeat

_____

The Problem

Customers have been finding that on NT, if a Forms Server session is initiated and the client for any reason goes down, the f50web32.exe process remains in memory until it is manually killed via the Task Manager.

The Fix, Server

A time-bomb has been placed in the server which will cause it to exit after a default span of 15 minutes assuming no messages have been received from the client within that timeframe. As soon as a message is received, the time-bomb resets itself to 15 minutes and starts ticking again.

The Fix, Client

Given that users occasionally may spend more than 15 minutes away from their machines, a heartbeat thread has been installed in the client that sends a simple message every 2 minutes, thereby resetting the server-side time-bomb. If, of course, the client goes down, the bomb will tick away to zero, and the f50web32 process will quietly exit.

The Interface

You cannot turn off the heartbeat feature. It is always running on both the server and client sides. You can however vary the length of time it takes for the server process to exit. On NT:

* Create a new registry entry under HKEY_LOCAL_MACHINE\\SOFTWARE\\ORACLE as a DWORD value.
* Name it FORMS50_TIMEOUT. (FORMS45_TIMEOUT, FORMS60_TIMEOUT for 1.6, 6.0 respectively)
* Give it an integer value representing the length of time in minutes until timeout between 3 and 1440 (1 Day) inclusive.

On Solaris:

* Create an environment variable FORMS50_TIMEOUT. (FORMS45_TIMEOUT, FORMS60_TIMEOUT for 1.6, 6.0 respectively)
* Give it an integer value representing the length of time in minutes until timeout between 3 and 1440 (1 Day) inclusive.

Availability

Developer 1.6: Forms 4.5.9.10.0 patch.
Developer 1.6.1: Forms 4.5.10.8.0 patch and later.
Developer 2.0: Forms 5.0.5.6.0 patch and later.
Developer 2.1 Forms 5.0.6.9.0 patch and later.
Developer 6.0 and beyond - all base releases.

NOTE: The heartbeat implementation is available for all platforms for 1.6.1. For 2.0 and higher it is currently NT only, although porting to other platforms is planned.

Shirley Chang
Boston Consulting Group, Inc.
Global Services, Information Technology
phone: +1 617 973 1214 ~ fax: +1 617 973 1399
e-mail: chang.shirley@bcg.com