Archives of the TeradataForum

Message Posted: Tue, 22 Apr 2014 @ 21:43:10 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Antonio,

I just started another packdisk at 15:32PM in Eastern time using crontab. Then I opened cnsterm 1 and it shows that packdisk has started as you see below. As you see the log file (CNSRUN_140422-15:32.output) has been generated and packdisk has started. When I ran packdisk this morning I expected to see the log file size grow with the output of packdisk information as we see in ViewPoint at the end of the job. I wanted to check the log file to verify that packdisk indeed ran. Do you expect log information in the log file when packdisk runs ok? How do you verify if packdisk runs successfully? Through cnsterm?

Thank you for all your help.

     CDEV_1-2:~ # crontab -e
     crontab: installing new crontab
     CDEV_1-2:~ # pwd
     /root
     CDEV_1-2:~ # cd..
     CDEV_1-2:/ # cd /var/opt/teradata/bteqdba
     CDEV_1-2:/var/opt/teradata/bteqdba # ls
     CNSRUN_140422-10:00.output  TAREAS_DBA.log
     CNSRUN_140422-15:32.output  packdisk
     MDCOMP670CDEV_1-2:/var/opt/teradata/bteqdba # cnsterm 1
     Attempting to connect to CNS...Completed.
     Hello

     Average Free Cylinders Across All AMPs in the Current Scope:   79%

     * Reported in units of Large Cylinders
       (A Large Cylinder is 6 times the size of a small cylinder)

     Ferret  ==>
     packdisk fsp=10

     Note: For table(s) within scope that have specified FSPs,
     that FSP will take precedence.
     Tue Apr 22, 2014  15:32:11 : Packdisk will be started
                                On all AMP vprocs
             Do you wish to continue based upon this scope?? (Y/N)
     y

     Tue Apr 22, 2014  15:32:11 : Packdisk has been started
                                On all AMP vprocs

         SCRIPT MODE is Enabled.
         ABORT command will not be allowed
         INQ  command will not be allowed

James Park
Database Specialist

	<Prev	Next>		<<First	<Prev	Next>	Last>>