11.07.2015 Views

Banner Student / Release Guide / 7.3.2

Banner Student / Release Guide / 7.3.2

Banner Student / Release Guide / 7.3.2

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Section 4 Problem ResolutionsOverallcurriculum existed. The trigger calculates the new priority and fills in default valuesfrom SORLCDF.The source of the maximum priority has been changed and now comes fromSOTLCUR instead of SORLCUR. The issue is that SORLCUR is only updated aftera commit, because the actual database delete occurs in the ON-INSERT trigger, whichis executed at commit. The SOTLCUR temporary table provides a pre-commit lookat current and active curriculum rows.SOQOLIB,SRAQUIK,SRARECR,SAAQUIK,SAAADMS,SGASTDN,SFAREGS,SHADEGR(#1-10EC07)Description: If a student had an existing curriculum on a current SGASTDN record,and SAAQUIK was used to change the curriculum, using the Clear Record functionin the Curriculum block removed the existing SGATSDN curriculum, leaving onlythe curriculum that had been entered on SAAQUIK.Impact: Users had to use the Insert Record function to create a new record and notthe Clear Record function.Resolution: Triggers have been modified in the SORLCUR and SORLCUR_LITEblocks to correct this.APIssokb%, sokd%(#1-QA6PU)Description: The dynamic update statements executed by the DML packages do notfully use bind variables for all runtime values. This causes extra hard parsing of newcursors at runtime and affects system performance by increasing parsing overhead,cached cursors, and latch contention. This level of latch contention was notanticipated when the DML update architecture was first designed, and the bestmethod to correct the situation is being researched. It is not recommended thatinstitutions use the session setting CURSOR_SHARING= FORCE in the meantime, asthis appears to create other performance behavior that is difficult to diagnose. Thisissue occurs across <strong>Banner</strong> products, including Self-Service products.Impact: Processes that use the APIs may experience slow performance.Resolution: The affected objects were passed through a conversion process tochange the DML p_update procedure to use an explicit update rather than adynamic update. The objects are:• sokb_admissions1.sql• sokb_app_decision1.sql• sokb_catlg_intpart1.sql• sokb_course_reg1.sql• sokb_enr_ver_pay1.sql• sokb_enr_ver_serve1.sql• sokb_enrollment1.sql• sokb_faculty1.sql• sokb_filedelimiter1.sql• sokb_filetestscore1.sqlFebruary 2007 <strong>Student</strong> <strong>Release</strong> <strong>7.3.2</strong>Confidential <strong>Release</strong> <strong>Guide</strong> 127

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!