Two database connections are required to successfully produce degree audits through the Connector via uAchieve:
Keep the following points in mind to minimize degree audit troubleshooting when setting up database access and installing the Connector:
|
This section is important when the database user used by the uAchieve server is different than the schema owner of the uachieve tables. If the database user used by the uAchieve server is the same as the database owner of the uAchieve tables, the points in this section aren't necessary.
When the database user used by the uAchieve server is different than the schema owner of the uachieve tables, the database user for the uAchieve server must have the following minimum access (synonyms and privileges):
Select privilege on the following uAchieve tables:
CHART_CATEGORIES COM CRS_CONVERT DPROG DPROG_REQ GMASTER MASTREF MASTREF_ADDRESS MASTREF_SEG REPEAT REQ_MAIN REQ_TEXT REQ_XY STRING STRING_CRSE SUB_REQ SUB_REQ_AR SUB_REQ_TEXT STU_ACADREC TCA_MASTER TCA_RULE TCA_SOURCE TCA_TARGET |
Some schools want to prevent the Connector from accessing the audit data contained in the JOB_QUEUE_xxx tables used by their existing uAchieve Server.
The alternatives below assume this initial setup, prior to performing the isolation steps:
The following sections show the two alternatives.
This isolation requires three database users and is the most secure.
Coming soon!
This isolation only requires two database users. It is slightly less secure than the above 3 Database User alternative.
It is accomplished with the following tasks: