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)?
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.