db2mt run load fail

[shkang-kr]

Hello,
Please check my work and review what I need to check further.
db2mt run setupdb worked fine, but db2mt run load fails and I am doubting it has authentification issue here and what I can try further.
I'm trying to migrate to RDS for Db2 and working on remote db2 client node.

db2inst1@ip-xxxxxxxx :~/db2mtdir/logs/current$ cat setupdb.log
==================================================== setupdb Starting ====================================================
[2024-04-19.07:15:31] INFO: Command successful: mkdir -p /home/db2inst1/db2mtdir/landing/current
[2024-04-19.07:15:32] INFO: Command successful: db2 connect to rdstpcc user "xxxxxx" password "xxxxxx"
[2024-04-19.07:15:33] INFO: Command successful: db2 -vf /home/db2inst1/db2mtdir/landing/current/uncatalog_alias.clp
[2024-04-19.07:15:33] INFO: Command successful: db2 -vf /home/db2inst1/db2mtdir/landing/current/catalog_alias.clp
[2024-04-19.07:15:33] INFO: Command successful: /home/db2inst1/db2mt s3 download --source db2mtdir/ddl/db2look_tables.ddl --target /home/db2inst1/db2mtdir/landing/current
[2024-04-19.07:15:33] INFO: Command successful: /home/db2inst1/db2mt s3 download --source db2mtdir/ddl/db2look_stats_profile.ddl --target /home/db2inst1/db2mtdir/landing/current
[2024-04-19.07:15:33] INFO: Command successful: db2 connect to rdstpcc user "xxxxxx" password "xxxxxx"
[2024-04-19.07:15:36] INFO: Command successful: db2 -td@ -vf /home/db2inst1/db2mtdir/landing/current/db2look_tables.ddl
[2024-04-19.07:15:36] INFO: Command successful: db2 -td@ -vf /home/db2inst1/db2mtdir/landing/current/db2look_stats_profile.ddl
=================================================== setupdb Completed ====================================================

db2inst1@ip-12-0-3-xx:~/db2mtdir/logs/current$ db2 list storage access
SQL1027N The node directory cannot be found.

db2inst1@ip-12-0-3-xx:~/db2mtdir/logs/current$ db2 -vf /home/db2inst1/db2mtdir/landing/current/catalog_alias.clp
call sysibmadm.storage_access_alias.catalog('db2mts3alias','s3','s3.us-east-1.amazonaws.com','myaccesskey,'access-secretkey','backup-20240224t',NULL,'U','admin')

Return Status = 0

db2inst1@ip-12-0-3-xx:~/db2mtdir/logs/current$ db2 list storage access
SQL1027N The node directory cannot be found.

db2inst1@ip-12-0-3-xx:~/db2mtdir/logs/current$ db2 "backup db rdstpcc to DB2REMOTE://backup-20240224t/db2mtdir/export"
SQL30082N Security processing failed with reason "3" ("PASSWORD MISSING").

db2inst1@ip-12-0-3-xx:~/db2mtdir/logs/current$ db2 "backup db rdstpcc to DB2REMOTE://backup-20240224t/db2mtdir/export"SQL30082N Security processing failed with reason "3" ("PASSWORD MISSING").SQL30082N Security processing failed with reason "3" ("PASSWORD MISSING").
-bash: syntax error near unexpected token `('

db2inst1@ip-12-0-3-xx:/db2mtdir/logs/current$ cat /home/db2inst1/db2mtdir/landing/current/catalog_alias.clp
call sysibmadm.storage_access_alias.catalog('db2mts3alias','s3','s3.us-east-1.amazonaws.com','mykey','mysecretkey','backup-20240224t',NULL,'U','admin')
db2inst1@ip-12-0-3-xx:/db2mtdir/logs/current$

db2inst1@ip-12-0-3-xx:~/db2mtdir/logs/current$ db2 get dbm cfg|grep -i key
SSL server keydb file (SSL_SVR_KEYDB) = /rdsdbdata/db/keystore/server.p12
SSL server stash file (SSL_SVR_STASH) = /rdsdbdata/db/keystore/server.sth
SSL client keydb file (SSL_CLNT_KEYDB) =
Keystore type (KEYSTORE_TYPE) = PKCS12
Keystore location (KEYSTORE_LOCATION) = /rdsdbdata/db/local_keystore/db2pwdstore.p12

[eunicechung]

Hello,

I don't see any load errors from the logs above. I'm assuming the steps listed are what you've attempted to debug the load issue. Those steps won't work for the following reasons:

• The catalog alias is meant to be run against the target RDS for DB2 system, so it won't show up when listing storage access which is listing from the local client.
• Db2 backup can only be run directly on the local server, it will not work from a remote client.
• The backup command itself db2 "backup db rdstpcc to DB2REMOTE://backup-20240224t/db2mtdir/export" is missing the alias. The correct syntax should be something like DB2REMOTE://(alias)/(bucket)/

Now, back to the original load problem that you're encountering. In the logs directory (e.g. ~/db2mtdir/logs/current), load_thread<#>_failed.lst will list the tables that have failed. There will be a corresponding log file (load_thread<#>.log) that shows the exact db2 load command for that table and the error that it is failing on. Once you have found the error, Db2 info center should have details on the failure and action that can be taken to fix it.

[shkang-kr]

The root cause of the issue has been identified as a network problem