Ok, I am attempting to clarify the required use of the RESIZE command, when you have a UNIVERSE or a UNIDATA DB attached to Cache. Traditional UNIVERSE / UNIDATA databases 'require' that hashed files be re-sized according to historic use, to prevent file overflow (aka. performance issues). It is not clear if that requirement is fully eliminated by attaching one of these databases to Cache. It is clear that, if you do not allocate 'enough' space on Cache for the database 'as a whole', that is a problem. But, Cache space allocation for the database 'as a whole' seems to be separate and distinct from the need to properly size hashed files, on an attached UNIVERSE or UNIDATA database.
Can anyone clarify this requirement, and, specify the 'why' to that answer?