We have been shutting down app and web tiers whenever doing maintenance on the
database or database servers. But your question made me wonder as to the
specifics as to why we have been since it was just something the app team has
always asked for. Here is the response from our PS Admin:
"Short Answer: Best Practices.
Long Answer: Appliciation Server processes can get hung. Although they have
a recycle time, my experience has been that errant processes can cuase Abends.
The Batch Server runs scheduled jobs and when interrupted in the middle
of a job it goes to Error. Sometimes, its gets stuck in "Processing" state.
This problem has 2 ramifications. We only allow 8 jobs to run in parallel, so
we're now reduced to 7. Also, it commonly locks up all future jobs of the
same type. For Example, nVison reports or PeopleSoft Query. To resolve, this
problem we have to delete INSTANCE ID /PROCESS ID records from 5 tables.
They mentioned Integration Broker, we don't really have the Integration
Broker working directly with the database. Either the Application Server or
Batch Server makes the calls directly with Active Directory.
My other comment, it gives me an excuse to clear the Cache on web, app
and batch which improves performance and its necessary for some Code changes."
Thanks,
Steve Givens
Lead Database Administrator
First National Bank
Omaha, NE 68197
sgivens@xxxxxxxx
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Hubler, Daniel
Sent: Monday, January 22, 2018 8:46 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: [External] Database patching for Peoplesoft applications
<<<This question is Peoplesoft specific.>>>
Looking for comments/anecdotes about database patching with Peoplesoft
applications.
We run HCM, CRM & ELM on AIX hosts (for all tiers).
Our database is Oracle.
Some of this is Oracle-RAC.
When you are applying DATABASE patches do you shut down your APPLICATION
software also?
Our experience seems to be that leaving the application software up is
O.K........for the most part.
Integration Broker has problems with this; it will end up hung. Everything
else seems to restart/reconnect OK.
I opened a case with Oracle/Peoplesoft support, looking for an official
position.
The "official" recommendation is to stop the application software, before
patching your database.
But...........this recommendation is not written down anywhere; the analyst
says such a document does not exist.
Want to hear form others regarding how they handle this.
--
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.freelists.org_webpage_oracle-2Dl&d=DwIFAg&c=LkAXfnqL6_MvrMPL5JzdE3Ild0DUTpmjbCJvMv5_TcQ&r=p64P693r52tzs7tJCmFvOg&m=GhAdolgPFQx8J5dxDkOhhVeuFMdLKWP9ZO9tMHwr67s&s=kt4KuLI-rbLuoI6zSXUlsvyXc_9j22gXHbS5gpU270c&e=
--
//www.freelists.org/webpage/oracle-l
