This is the most common error while performing the SAP system copy running on DB2 database.
Sample Error:
ERROR 2020-10-13 17:58:57.336 (root/sapinst) id=syslib.process.childApplication.notAccessed errno=FSL-04008
Unable to access application /db2/db2<sid>/sqllib/adm/db2set. A file or directory in the path name does not exist.
ERROR 2020-10-13 17:58:57.348 (root/sapinst) id=modlib.jslib.caughtException errno=MUT-03025
Caught ::ESyException in module call: At line 1121 file /bas/749_REL/bc_749_REL/src/ins/SAPINST/impl/src/syslib/process/syuxctask.cpp
Call stack:
CThrThread.cpp: 85: CThrThread::threadFunction()
CSiServiceSet.cpp: 63: CSiServiceSet::executeService()
CSiStepExecute.cpp: 915: CSiStepExecute::execute()
EJSController.cpp: 187: EJSControllerImpl::executeScript()
JSExtension.hpp: 1136: CallFunctionBase::call()
iaxxcprocess.cpp: 120: iastring CIaOsProcessConnect::callMemberFunction(iastring const& name, args_t const& args)
iaxxcprocess.cpp: 1346: iastring CIaOsProcessConnect::start(args_t const& _args)
iaxxbprocess.cpp: 416: CIaOsProcess::start_impl()
syuxctask.cpp: 1090: CSyTaskImpl::start(bool)
Unable to access application /db2/db2<sid>/sqllib/adm/db2set. A file or directory in the path name does not exist.
.
ERROR 2020-10-13 17:58:59.534 (root/sapinst) id=controller.stepExecuted errno=FCO-00011
The step UpdateDB2Registry with step key |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_CreateDB|ind|ind|ind|ind|createdb|0|NW_DB6_DB|ind|ind|ind|ind|db6|0|NW_DB6_UpdateDb2Registry|ind|ind|ind|ind|NW_DB6_UpdateDb2Registry|0|UpdateDB2Registry was executed with status ERROR (Last error reported by the step: Unable to access application /db2/db2<sid>/sqllib/adm/db2set. A file or directory in the path name does not exist).
Cause:
SAP Note 2883517 explains the cause of this issue.
Following this note, you can find if you can see the cause of the issue by using the below command on unix servers
Go to the log directory of the SAP DB instance system copy, example for SAP ECC EHP6
cd /tmp/sapinst_instdir/BS2011/ERP606/LM/COPY/DB6/SYSTEM/DISTRIBUTED/AS-ABAP/DB.
grep "Skipdb2icrt" *
If it returns the result, it means this note is valid for your issue.
How to Resolve?
Though SAP Note 2883517 mentions that you can find the command in one of the log files of the SAP installation, however I could not find it in that log file so I compared it with one of the similar installation of other system.
You will need to create the database instance manually with below command, if possible check the installation logs for other successful system in sapinst_dev.log file
./db2icrt -s ESE -a SERVER_ENCRYPT -u db2<sid> db2<sid>
This will create the sqllib and other db2 related directories in the /db2/db2<sid> directory.
Once completed, retry the installation