Upgrading from IBM 8.6 to IBM BAW 18.0.0.1 - Disk is crucial

I saw this: -

...

[08/10/18 11:54:56:571 BST] 00000001 BPMConfig     E com.ibm.bpm.config.BPMConfig main ADMA5002E: Application binaries cannot be saved in /opt/ibm/WebSphere/AppServer/profiles/Dmgr01/wstemp/anonymous1538995571224/workspace/cells/PCCell1/applications/navigatorEAR_AppCluster.ear/navigatorEAR_AppCluster.ear: org.eclipse.jst.j2ee.commonarchivecore.internal.exception.SaveFailureException: navigator.war

                                 com.ibm.bpm.config.util.ConfigException: ADMA5002E: Application binaries cannot be saved in /opt/ibm/WebSphere/AppServer/profiles/Dmgr01/wstemp/anonymous1538995571224/workspace/cells/PCCell1/applications/navigatorEAR_AppCluster.ear/navigatorEAR_AppCluster.ear: org.eclipse.jst.j2ee.commonarchivecore.internal.exception.SaveFailureException: navigator.war
        at com.ibm.bpm.config.util.jmx.AppManagementNotificationListener.appEventReceived(AppManagementNotificationListener.java:117)
        at com.ibm.ws.management.application.SchedulerImpl.propagateTaskEvent(SchedulerImpl.java:245)
        at com.ibm.ws.management.application.task.BackupAppTask.install(BackupAppTask.java:195)
        at com.ibm.ws.management.application.task.BackupAppTask.performTask(BackupAppTask.java:92)
        at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:315)
        at java.lang.Thread.run(Thread.java:811)
…

whilst upgrading from IBM Business Process Manager 8.6 CF2013.03 to IBM Business Automation Workflow 18.0.01, as per this: -

Upgrading profiles from IBM Business Process Manager Version 8.6.x to IBM Business Automation Workflow V18.0.0.1

Something made me think that it MIGHT be disk-space related, given the exception.

Checking free disk space: -

df -kmh

Filesystem             Size  Used Avail Use% Mounted on
/dev/mapper/rhel-root   48G   44G  3.8G  93% /
devtmpfs               3.8G     0  3.8G   0% /dev
tmpfs                  3.9G   60K  3.9G   1% /dev/shm
tmpfs                  3.9G   12M  3.8G   1% /run
tmpfs                  3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/sda1              497M  210M  288M  43% /boot
tmpfs                  781M     0  781M   0% /run/user/1004
vmhgfs-fuse            477G  405G   73G  85% /mnt
tmpfs                  781M     0  781M   0% /run/user/0

kinda reinforced that suspicion.

So I checked the logs further: -

fgrep -R device /opt/ibm/WebSphere/AppServer/profiles/Dmgr01/logs

and found: -=

...
/opt/ibm/WebSphere/AppServer/profiles/Dmgr01/logs/DBUpgrade_Mon-Oct-08-11.40.36-BST-2018_0.log:INSERT INTO SYNCCONFIGURATION ( ID, ATTRIBUTES ) VALUES ('com.ibm.ecm.sync.WebAppListener.deviceCleanupInitialDelay', 'name=Initial deplay for the database clean up task;descr=Initial deplay for the database clean up task (in days);attributes=1')
/opt/ibm/WebSphere/AppServer/profiles/Dmgr01/logs/DBUpgrade_Mon-Oct-08-11.40.36-BST-2018_0.log:INSERT INTO SYNCCONFIGURATION ( ID, ATTRIBUTES ) VALUES ('com.ibm.ecm.sync.WebAppListener.deviceCleanupPeriod', 'name=Device clean up cycle time;descr=Device clean up cycle time (in days);attributes=7')
/opt/ibm/WebSphere/AppServer/profiles/Dmgr01/logs/DBUpgrade_Mon-Oct-08-11.40.36-BST-2018_0.log:INSERT INTO SYNCCONFIGURATION ( ID, ATTRIBUTES ) VALUES ('com.ibm.ecm.sync.tools.cleanup.CleanupTask.deviceExpiration','name=Device expiration;descr=device expiration (in days);attributes=90')
/opt/ibm/WebSphere/AppServer/profiles/Dmgr01/logs/ffdc_20181008-114610/ffdc.1987123897687396422.txt:Caused by: java.io.IOException: No space left on device
/opt/ibm/WebSphere/AppServer/profiles/Dmgr01/logs/ffdc_20181008-114610/ffdc.1987123897687396422.txt:   java.lang.Throwable::detailMessage:No space left on device
...

which kinda confirmed things.

Off to add more disk ……