It is complaining that the path z:\db2backups\archive_logs\OPNACT does not exist.

Verify that Z: is mounted, and the full path exists with correct permissions, before any database activates...

Hello Mor,

Thanks, .... I made a mistake in the path.......

Z:\Db2backups\DB2IIC>db2 "UPDATE DB CFG FOR OPNACT USING logarchmeth1 disk:z:\db2backups\DB2IIC\archive_logs\OPNACT"
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.

So for now the next step is get the config. as we used it on the old DB2 environment ( Windows 2008 R2 with DB2 10.1 FP2 ) to
write archive logs to a a server share directly.

Z:\Db2backups\DB2IIC>net use \\scvbus\db2backups
The command completed successfully.

Z:\Db2backups\DB2IIC>set | find "USERNAME"
USERNAME=db2iic

So we are running the DB2 instance onder the local user DB2IIC, the same user also exists locally on the scvbus server.

I can open shares from within the explorer view without entering any credentials but setting the LOGARCHMETH1 to this
location doesn't work anymore? We were able to configure it like this in the old setup.

Does this have something to do with Windows 2012 R2?

Thanks.

Cheers, Marco

Z:\Db2backups\DB2IIC>db2 "UPDATE DB CFG FOR OPNACT USING logarchmeth1 disk:\\scvbus\db2backups\DB2IIC\archive_logs\OPNACT"

SQL5099N The value "\\scvbus\db2backups\DB2IIC\archive_logs\OPNACT" indicated
by the database configuration parameter "LOGARCHMETH1" is not valid, reason code "2". SQLSTATE=08004

db2diag.log

2016-02-26-14.31.13.231000+060 I55617902F515 LEVEL: Error
PID : 4336 TID : 3912 PROC : db2syscs.exe
INSTANCE: DB2IIC NODE : 000 DB :
APPHDL : 0-3032 APPID: *LOCAL.DB2IIC.160209140231
AUTHID : DB2IIC HOSTNAME: DB2
EDUID : 3912 EDUNAME: db2agent (instance) 0
FUNCTION: DB2 UDB, config/install, sqlfVerifyLogArchMeth, probe:1220
MESSAGE : Error -5099 updating db cfg parm LOGARCHMETH1.

2016-02-26-14.31.13.231000+060 I55618419F683 LEVEL: Error
PID : 4336 TID : 3912 PROC : db2syscs.exe
INSTANCE: DB2IIC NODE : 000 DB :
APPHDL : 0-3032 APPID: *LOCAL.DB2IIC.160209140231
AUTHID : DB2IIC HOSTNAME: DB2
EDUID : 3912 EDUNAME: db2agent (instance) 0
FUNCTION: DB2 UDB, config/install, sqlfUpdateDbCfg, probe:70
MESSAGE : ZRC=0xFFFFEC15=-5099
SQL5099N The value "" indicated by the database configuration
parameter "" is not valid, reason code "".

DATA #1 : String, 41 bytes
Error updating per-member DB config, rc =

2016-02-26-14.31.13.231000+060 I55619104F1624 LEVEL: Error
PID : 4336 TID : 3912 PROC : db2syscs.exe
INSTANCE: DB2IIC NODE : 000 DB :
APPHDL : 0-3032 APPID: *LOCAL.DB2IIC.160209140231
AUTHID : DB2IIC HOSTNAME: DB2
EDUID : 3912 EDUNAME: db2agent (instance) 0
FUNCTION: DB2 UDB, config/install, sqlfUpdateDbCfg, probe:71
DATA #1 : <preformatted>
each_param->token: 822
each_param->ptrvalue: disk:\\scvbus\db2backups\DB2IIC\archive_logs\OPNACT
each_param->flags: 0
CALLSTCK:
[0] 0x00007FFF0C64132B pdLogPrintf + 0x3FB
[1] 0x00007FFEE724F1E8 sqlfUpdateDbCfg + 0x2C18
[2] 0x00007FFEE724C4B9 sqlfDispatchDbCfgUpdate + 0x69
[3] 0x00007FFEEC1A59C7 sqlfudb_backend + 0x2B7
[4] 0x00007FFEEC18F06C sqlesrvr + 0x9FC

Same reason code 2: the new UNC path either does not exist or is not found bu the logon-account used by the DB2-instance.

Fix that first.

If the UNC path exists and the localuser acting as the "Log on As" for your DB2-instance can create files (from remote) on it and delete files and write files on it then DB2 should be happy (as long as you verify that the services.msc shows that your DB2-instance has '"Log on As" with a correct value).

If that fails with the same error, try running the DB2-instance account with a domain account (where both of the Windows servers are either in the same domain, or have appropriate trusts) and that domain-account can create/read/write/delete files on the UNC path.