Question

2
Replies
157
Views
Victor Uriel Camas (VictorU)
Corner Banca

Corner Banca
CH
VictorU Member since 2012 6 posts
Corner Banca
Posted: January 24, 2017
Last activity: January 25, 2017
Posted: 24 Jan 2017 3:33 EST
Last activity: 25 Jan 2017 21:03 EST
Closed

Database tuning (1.5 TB DB)

Good morning everybody,

soon our Pega database, running Oracle version 12.1, will probably reach 1.5 TB.

We wonder if we can improve its manageability, and we have some questions for you:

  1. are there some PDFs or documents related to Best Practices or Recommendation in case of very large Pega's Oracle databases (1 TB or more)? 
  2. Is anybody managing an Oracle DB so large? If so, are you following additional guidelines?
  3. does anybody think that it is correct to have some tables (and some of their indexes) in the range of 100 - 200 GB, which are not partitioned?
  4. Is it correct that we have just one tablespace (whose 50 datafiles will sum up almost 1.5 TB) which contains all together : tables, indexes, BLOBS?
  5. Can anybody confirm if the following BLOB's parameters (either for performance or for storage utilization ) : "IN ROW", "NOCACHE", "CHUNK 8192" (this one is probably ignored), no PCTVERSION, no RETENTION are correct?

Also, we are concerned about BLOB data. There are 4 tables, which are clones of PC_WORK where we store our service cases/interactions specific for each application, whose BLOB segments (all using new SECUREFILE option) will be 100 GB soon.

I would really appreciate if I could get some inputs on these questions to improve the performance of our DB and the space management.

Thank you very much,

Víctor

Data Integration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.