Z Archived: Foundation CM
  1. Z Archived: Foundation CM
  2. KULCFG-284

make it so we can use the USERS tablespace and TEMP temp tablespace for our kul*** schemas

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: KFS
    • Labels:
      None

      Description

      currently i have these comments in kuluser_maint_pk (the package we use to purge (i.e. drop/create) schemas in oracle for the daily updates, cause we're set up to use per schema tablespaces and TEMP02

      – FOR NOW THIS NEEDS TO BE CHANGED TO TEMP02 FOR THE KUALI FOUNDATION DAILY UPDATE PROCESS
      TemporaryTablespace CONSTANT VARCHAR2(30) := 'TEMP';
      PrimaryTablespace CONSTANT VARCHAR2(30) := 'USERS';
      – FOR NOW THIS NEEDS TO BE CHANGED TO TRUE FOR THE KUALI FOUNDATION DAILY UPDATE PROCESS

        Issue Links

          Activity

          Farooq Sadiq (Inactive) made changes -
          Field Original Value New Value
          Assignee Brian McGough [ bmcgough ] Farooq Sadiq [ fsadiq ]
          Casey Boettcher (Inactive) made changes -
          Link This issue is related to KULRICE-2764 [ KULRICE-2764 ]
          Hide
          Casey Boettcher (Inactive) added a comment -

          Putting aside the larger issue of the sustainability, documentation and fragility of kul-cfg-envs, I don't see why we couldn't alter the create_user function to take a tablespace name as a third parameter and default to something sane if one isn't provided.

          Also, from what I've been able to glean, all of the existing RICE-related schemas use KUALI_USERS as a tablespace. What are the pros and cons of establishing a one-to-one relationship between tablespaces and schemas?

          Show
          Casey Boettcher (Inactive) added a comment - Putting aside the larger issue of the sustainability, documentation and fragility of kul-cfg-envs, I don't see why we couldn't alter the create_user function to take a tablespace name as a third parameter and default to something sane if one isn't provided. Also, from what I've been able to glean, all of the existing RICE-related schemas use KUALI_USERS as a tablespace. What are the pros and cons of establishing a one-to-one relationship between tablespaces and schemas?
          Hide
          Ailish Byrne added a comment -

          this was a decision by the cms last year. we have to use a special version of the kul maint pk function. we would like to keep our default config as simple as possible. the db import/export is not intended to be used for live production implementations where dbas might want to get fancier.

          Show
          Ailish Byrne added a comment - this was a decision by the cms last year. we have to use a special version of the kul maint pk function. we would like to keep our default config as simple as possible. the db import/export is not intended to be used for live production implementations where dbas might want to get fancier.
          Farooq Sadiq (Inactive) made changes -
          Component/s Foundation [ 13091 ]
          Component/s Automated Environment Updates [ 10661 ]
          Farooq Sadiq (Inactive) made changes -
          Priority Critical [ 2 ] Minor [ 4 ]
          Hide
          Farooq Sadiq (Inactive) added a comment -

          For me separate tablespaces makes management easier. I am not a DBA so I have asked the UofA DBAs to see what they recommend in regards to tablespace usage.
          I have put it on the agenda for the KTI on Wednesday.

          Show
          Farooq Sadiq (Inactive) added a comment - For me separate tablespaces makes management easier. I am not a DBA so I have asked the UofA DBAs to see what they recommend in regards to tablespace usage. I have put it on the agenda for the KTI on Wednesday.
          Farooq Sadiq (Inactive) made changes -
          Component/s KFS [ 13092 ]
          Component/s Foundation [ 13091 ]
          Hide
          Farooq Sadiq (Inactive) added a comment -

          Discussed at the Kuali Technical Integration (KTI) on Mar 31, 2010. Resolved to close ticket with no change to package.

          UseUserNameForTablespace CONSTANT is set to TRUE on esdbk02 package and we would like to continue to use a tablespace per SCHEMA.

          Show
          Farooq Sadiq (Inactive) added a comment - Discussed at the Kuali Technical Integration (KTI) on Mar 31, 2010. Resolved to close ticket with no change to package. UseUserNameForTablespace CONSTANT is set to TRUE on esdbk02 package and we would like to continue to use a tablespace per SCHEMA.
          Farooq Sadiq (Inactive) made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              Farooq Sadiq (Inactive)
              Reporter:
              Ailish Byrne
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel