AMGDB Version Cutting

Before you can proceed to cut a new version of AMGDB,

• your personal account must be in the products group on both fncdug1 and fncduh1
• your personal account must have a privilege to store file in the MISCOMP CVS area
• all necessary files are created on fncduh1 and checked into the miscomp cvs area
• /miscomp/amgdb needs to be created on both fncdug1 and fncduh1 if it does not exist

Unless you undeclare the product first, you only need to do UPS Declare once regardless how many times the procedure was repeated.

The product and version below should be replaced by the prodcut name and version number that you are cutting, e.g. amgdb v1_0

General Concurrent Version System (CVS) Version Cutting

• Logon to fncduh1, enter
• newgrp products
• setup miscompcvs
• kinit
• setenv AMGDB_DIR /miscomp/amgdb/version
• cd /miscomp/cvscutting
• cvscut amgdb version SunOS+5 none amgdb_int.table test | tee anylogfilename
  

  Note : During the execution of cvscut statement, you may receive the error similar to the following
      ERROR: Error in call to mkdir: Permission denied
      ERROR: Unable to open file /local/ups/db/amgdb/test.chain.
      ERROR: Error in call to mkdir: Permission denied
      ERROR: Unable to open file /local/ups/db/amgdb/v1_0.version.
  
  If you do, you need to manually enter
      ups declare -t -r /miscomp/amgdb/version -f SunOS+5 -m amgdb_int.table
      -M /miscomp/amgdb/version/ups -z /fnal/ups/db amgdb version

• cd /miscomp/amgdb/version
• tar cvf $HOME/product_version.tar *
• logon to fncdug1, enter
• newgrp products
• kinit
• cd /miscomp/amgdb
• mkdir version              (do this only if the directory does not exist)
• cd version
• ftp fncduh1 4021         (to copy the tar file)
• tar xvf product_version.tar
• ups declare -r /miscomp/amgdb/version -f SunOS+5 -m amgdb_int.table
  -M /miscomp/amgdb/version/ups -z /fnal/ups/db amgdb versiont
• ups declare -t -z /fnal/ups/db amgdb versiont
• ups list -val amgdb -t

Integration Database Conversion

• Logon to fncdug1, enter
• newgrp products
• kinit
• (optional)
  ups declare -t -r /miscomp/amgdb/version -f SunOS+5 -m amgdb_int.table
  -M /miscomp/amgdb/version/ups amgdb version
  
• ups list -t amgdb versiont
• setup -t amgdb
• cd $AMGDB_DIR
• setenv TWO_TASK int1
• echo $ORACLE_SID $TWO_TASK         (to make sure the result is   int1)
• make convert version=version user=alignadm/int_password
| tee amgdb_int_version.log
• setup developer
• make all ORAUSER=alignadm/int_password | tee amgdb_int_frm_version.log
• cd /miscomp/amgdb
• rm test         (do this only when the symbolic link is predefined for test)
• ln -s version test

Now, you can perform the test on the specific version that you have just cut.

Production Database Conversion

Before you start the production database conversion, you should schedule database shutdown for version cutting and make a backup copy of database.

• logon to fncdug1, enter
• newgrp products
• kinit
• ups declare -r /miscomp/amgdb/version -f SunOS+5 -m amgdb_prod.table
  -M /miscomp/amgdb/version/ups -z /fnal/ups/db amgdb version
• setup amgdb version
• cd $AMGDB_DIR
• setenv TWO_TASK misprod1
• echo $ORACLE_SID $TWO_TASK         (to make sure the result is   misprod1)
• make convert version=version user=alignadm/prod_password | tee amgdb_prd_version.log
• setup developer
• make all ORAUSER=alignadm/prod_password | tee amgdb_prd_frm_version.log
• ups declare -c amgdb version -z /fnal/ups/db
• ups list -va amgdb
• cd /miscomp/amgdb
• rm current         (do this only when symbolic link is predefined for current)
• ln -s version current

last modified 23 May 2007     Comments or Questions? AMG	Security, Privacy, Legal