Banner Connection Issues

November 01, 2019 2:41 p.m.
Multiple applications that connect to the Banner production database
Location: 
Multiple Locations
Status: 
Open
Resolved alert: 
10/17/2019 3:30 pm

Intermittent Banner issues occurred on October 16th at approximately 3:30 – 4:10 P.M., October 17th  at approximately 8:50 – 10:05 A.M., and October 18th for about 2 minutes (8:56-8:58 A.M.).  New connections could not be established against Banner PROD.  However, existing sessions were unaffected.

Initial symptoms: 

New connections could not be established against Banner PROD.  This manifested in jobs failing in AppWorx and jobsub.  Users were getting “service invocation errors” when attempting to connect to AppNav and/or an Admin Page.  eVA crashed as well.

Duration: 
10/17/2019 10:10 am - 10/17/2019 3:30 pm
Impact to Mason: 

New connections could not be established against Banner PROD.  This manifested in jobs failing in AppWorx and jobsub.  Users were getting “service invocation errors” when attempting to connect to AppNav and/or an Admin Page.  eVA crashed as well.

Affected Services: 
Banner Admin
ROOT CAUSE ANALYSIS
Cause: 

Error messages indicate 1 or 4 possible issues:

  • Network issues
  • Server memory
  • Database memory
  • Not enough user processes allowed on the server

There were no network issues at the time.  Network issues would have also impacted existing session but that was not occurring.

Resolution: 

Monitoring tools indicated that additional CPU could help.

The following changes were made:

  • Server memory was increased by 16G
  • Four additional CPU were added to the server
  • 2000 user processes added for the Oracle user
  • Database memory was increase by 5G
  • Maximum processes allowed within the database increased from 1500 to 3000.
Prevention: 

Monitoring.

STATISTICS