Question
CYBG
GB
Last activity: 30 Sep 2016 11:17 EDT
Purpose of index tablespaces created during PRPC installation
I recently received an email from our new DBA who assisted with a PRPC installation. He noticed that the PRPC tables and indexes created through the auto-produced oracledate.sql script create tablespaces for both tables and indexes, yet when the indexes are created they are created in the "table" tablespace. The "index" tablespace remains unused.
Is this simply an oversight in the code that produces the oracledate.sql script, or is there some other reason the index tablespaces are created (and not used)?
Many thanks,
Mike.
Pegasystems Inc.
AU
Ideally its better to separate the tables and index tablespaces for various reasons that are advocated by the DBA.
- Run-time performance
- Reporting/monitoring
- Manageability etc.
I dont remember inputing the tablespce names while creating the PRPC schema. It would have been good if that option is provided while installation.
Having said that, it is up to the DBA to alter the scripts to separate index and tables into separate tablespaces.
Accepted Solution
CYBG
GB
I agree, Krishna, and our DBA is happy to make those kinds of changes. I was just curious if Pega had an underlying reason for designing the installation scripts in the way they did, or whether the Index Tablespaces were something that was considered but never fully implemented.
Many thanks for your input!