z/OS Security Server RACF System Programmer's Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Procedure for the primary database

z/OS Security Server RACF System Programmer's Guide
SA23-2287-00

  1. Ensure that the backup database is active (RVARY LIST, followed, if necessary, by RVARY ACTIVE).
  2. Issue RVARY SWITCH. The original primary is now an inactive backup.
  3. Copy the current primary database (the original backup) using IRRUT200, or IRRUT400 with LOCKINPUT.

    Uncatalog the current backup database (the original primary). Ensure that the newly-created database that you want to use as the new primary database has been cataloged, and ensure that it has the same name as the original primary database. This must be done on all systems that share the RACF® database.

  4. Issue RVARY ACTIVE for the new primary database (the current backup).
  5. If you used IRRUT400 with LOCKINPUT in step 3, run IRRUT400 with UNLOCKINPUT to unlock your current primary (the original backup).
  6. Issue RVARY SWITCH (this inactivates the original backup).
  7. Issue RVARY ACTIVE for the original backup.
Note: After an RVARY SWITCH when your backup is inactive, your primary and backup databases might become out of synch. If this is a concern to you, the safest approach is to use IRRUT400 with LOCKINPUT to perform the copy. But note that even in this scenario, a window exists between steps 6 and 7 where your databases might become out of synch. The recommended scenario is to use IRRUT200 to do the copy at a time when no profiles are being updated in your RACF database. This gives you the fastest copy performance.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014