STEP 4: Clone checking

Data d'actualització: 02/09/2011 10:46:16

Share with Facebook   Share with Delicious Share with GoogleShare with Meneame Share with Myspace Share with Digg Mail

ID: 25898
Category: Computer science RSS Computer science
Clasification Unesco: Technological sciences
Description: Finally, we compare rows from the table that was been modified while source DB2 was clonned. Josep Vidal - System Programmer. For more questions you can reach me at: .
Labels: Online DB2 Z/OS Cloning clone subsystem LPAR
Resolution:  1024 x 1024  unknown
Score: Sense puntuacio (puntuar).
License CC: No asignada
Visits: 246

No comments
related videos

12.- Instalación zlinux. Conexión al zlinux

Después de hacer IPL, procederemos a logarnos en la debian s/390 tanto por consola como via ssh.

DB2 HA & DR. Part III

Cluster DB2 Activo/Activo con pureScale

STEP 3: Restart Target DB2

Finally, we RESTART TARGET DB2 and it's stopped databases.

11.- Instalacion zlinux. Finalización de la instalacion

Una vez finalizada la instalación procedemos a parar el ramdisk de instalación para posteriormente hacer IPL del volumen sobre el que hemos instalado la debian para la arquitectura s390.

STEP 2.2: Change Catalog STOGROUPs HLQ:

So, now we got both systems up and runing, but TARGET DB2 storage groups point to source HLQ. So we have to update TARGET DB2 catalog to point to new HLQ. To do this we use REXX code to select all storage groups and generate DDL to: 1.- Alter all depenent tablespaces and indexspaces to a temporal storage group -> SYSADM.TEMP.CHTSSGT 2.- Drop all storage groups -> SYSADM.TEMP.DROPSTO 3.- Create all storage groups with new HLQ (VCAT) -> SYSADM.TEMP.CREASTO 4.- Alter all depenent tablespaces and indexspaces to their original storages groups -> SYSADM.TEMP.CHTSSGO The JCLs that automates all this stuff are RENSTOGC (generates DDL to change STOGROUP VCAT) and ALTSTOG (executes it)