DISK SPACE CHECK BUG
Article ID: 125596
Updated On:
Products
CA Spectrum
Issue/Introduction
During an upgrade to 10.3 on a CA Spectrum installation, the Post Upgrade step to convert the DDMDB to InnoDB is incorrectly calculating the available disk space, before starting the conversion. We have more than enough space, however the "convert_current_myisam_to_innodb.pl" script, incorrectly says there was not enough space to migrate a 5Gb Event table.
Environment
Spectrum 10.3
Resolution
This is fixed in 10.3.1 and 10.3 BMP 01
Symptom: If disk name is larger than normal, it results in a failure as the wrong information is parsed.
Resolution: Used "df -P" command instead of "df" command to avoid line breaks.
(DE388021, 01205923 )
It can be worked in 10.3 by replacing the following line in the "convert_current_myisam_to_innodb.pl" script
$FREE_DISK_SPACE = df $SPECROOT | awk '{print \$4}'| tail -1; #size in KB
with
$FREE_DISK_SPACE = df -P $SPECROOT | awk '{print \$4}'| tail -1; #size in KB
Symptom: If disk name is larger than normal, it results in a failure as the wrong information is parsed.
Resolution: Used "df -P" command instead of "df" command to avoid line breaks.
(DE388021, 01205923 )
It can be worked in 10.3 by replacing the following line in the "convert_current_myisam_to_innodb.pl" script
$FREE_DISK_SPACE = df $SPECROOT | awk '{print \$4}'| tail -1; #size in KB
with
$FREE_DISK_SPACE = df -P $SPECROOT | awk '{print \$4}'| tail -1; #size in KB
Feedback
Yes
No
Powered by
