Thank you very much for the valuable pieces of information! Here the points I've noted from your posts, in order to help others that may search for the same topic.
The original question: I'm looking for some DB2 specific recommendations regarding User Catalogs, specially if there are any rules of thumb as a start point for defining the infrastructure for DB2 (like each member has its own catalog or something like that). Here the answers: - Frequently ICF catalogs are shared by many users / applications. It is unusual for a DB2 install today to include the allocation of a new user catalog. - Software, DB2 objects, and backups (Copies, logs etc) should not share the same HLQ - Make sure the storage management team know about the numbers and volitility of each type of dataset use - Sometimes it can be a good thing for the aliases (or vcatnames) used in multiple DB2 subsystems to be in separate ICF usercats. Then each subsystem can be granted update access only to the ICF usercat that has the aliases for it. - You're less likely to have an outage putting different components of a single DB2 sub-system into different ICF catalogues. Do your job as a DBA and let the Storage Admins do theirs. - Chapter 4.1.7 from redbook "Data Sharing in a Nutshell" (http://www.redbooks.ibm.com/redbooks/pdfs/sg247322.pdf) has some recommendations about User Catalogs. - Page 140 from redbook "DB2 9 for z/OS and Storage Management" (http://www.redbooks.ibm.com/redbooks/pdfs/sg247823.pdf) has similar recommendations. - If you intend to use SYSTEM BACKUP there are special recommendations regarding what objects should be put in each user catalog. - One should caution against a profusion of UCATs; it can lead to all sorts of recriminations when doing "business continuity" testing (Disaster recovery.) Suggestion: 4 UCATs; testing, production, pre-production testing and DB2. - In a small DB2 shop , one user catalog can support more subsystems ( PROD,TEST,DEVL) . Isolation of production is also a best practice. Depending on the number of archives logs that you produce and keep cataloged, they will consume space , size the catalog appropriately to avoid extents. - DB2 treats the whole group in a data sharing system as a logical entity, so different user catalogs for data sharing members won't work. And here the source: DB2-L Avram Friedman, Debora Gresham, Ted MacNEIL, Cathy Taddei, Cuneyt Goksu, Marcel Harleman IBM-Main Rick Fochtman, Ed Finnell, Kevin Clark, Wayne Driscoll ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
