IBM Support

[Db2] db2diag -A <path> might print error EXDEV in db2diag.log.

Troubleshooting


Problem

The db2diag -A (archive) command with directory name option might print an error in db2diag.log like as following.
2020-08-12-07.31.17.644493+540 I2330E1265            LEVEL: Error (OS)
PID     : 879402               TID : 140602969769352 PROC : db2diag
INSTANCE: db2inst1             NODE : 000
HOSTNAME: db2server.example.com
FUNCTION: DB2 Common, OSSe, ossFileRename, probe:20
MESSAGE : ECF=0x90000034=-1879048140=ECF_FILE_REMOTE_SYSTEM_NOT_ACTIVE
          File is on a remote system and the link to that system is not active
CALLED  : OS, -, rename                           OSERR: EXDEV (18)
DATA #1 : String, 41 bytes
/home/db2inst1/sqllib/db2dump/DIAG0000/db2diag.log
DATA #2 : String, 42 bytes
/archive_data/diaglog/db2diag.log_2022-11-10-12.31.17

Cause

db2diag command tries rename() first, then copy the db2diag.log file only when rename fails.
That is, the error is recorded only if the target directory is located in the different file system than original db2diag.log.

Environment

Db2 for Linux and Unix platforms.

Resolving The Problem

Users can choose one of the following ways to bypass the error.
a) Specify the target directory in the same file system as original db2diag.log.
b) Do not specify the target directory. Copy the archived files after the archive processing.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"ARM Category":[{"code":"a8m500000008PlfAAE","label":"DB2 Tools-\u003Edb2diag.log"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"All Versions"}]

Document Information

Modified date:
12 November 2022

UID

ibm16839049

Page Feedback