Moving from OPS to Standby database?

We have a mission critical 8.1.6 database built on two RS6000/H50's, configured for OPS, meaning of course, raw devices.

I've been given the task to re-architect this database and prepare it for eventual implementation of stand-by (which will be done by another DBA). Which means my big task is to convert it from using raw devices to JFS.

Reviewing the space allocation within the database, I'm seeing a mix of LMT's and dictionary, with some tablespaces being overallocated. So, while performing the conversion, I'd also like to rebuild the tablespaces to standardize on LMT's and also to free up more disk by downsizing the overallocated tablespaces.

On top of all this, there may be a requirement to change the characterset from WE8ISO8859P1 to UTF8, which would mean a database rebuild.

I'm unsure as to best way to accomplish the move from raw to JFS while rebuilding the tablespaces, with or without the UTF8 requirement.

Any advice, ideas?

Thanks,
Jeff Thomas
thomasje_at_tce.com Received on Fri Jan 12 2001 - 08:22:53 CST