Technical Blog Post
75 ways to demystify DB2 #58: Techtip : SQL5099 RC 9 while updating logpath or mirror logpath
On Windows, updating logpath or mirror logpath with path pointing to a mapped drive letter for a network drive may return SQL5099 RC 9.
C:\Program Files\IBM\SQLLIB\BIN>db2 update db cfg for sample using mirrorlogpath "U:\pmrs\03298.082.000"
SQL5099N The value "U:\pmrs\03298.082.000" indicated by the database configuration parameter "MIRRORLOGPATH" is not valid, reason code "9".
Here U:\pmrs\ is mapped driver letter for my network drive:
You can find more information about SQL5099 here.
RC 9 indicates:
9 The path cannot be accessed.
DB2 is not able to access the path, because it is not able to decipher the drive letter.
Drive letter mapping on Windows is not visible in all processes running on the box, this can lead to the error SQL5099N RC9.
Instead of using drive letter, one can use UNC path and overcome this error. If you still run into problems with this the access rights to the network path need to be reviewed.
Here is a good Microsoft article explaining this.
In my example, I changed the drive letter to UNC path and it worked:
C:\Program Files\IBM\SQLLIB\BIN>db2 update db cfg for sample using mirrorlogpath "\\xyz.abc.com\tlbgsa\projects\d\dbtpmrs\pmrs\03298.082.000"
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
SQL1363W One or more of the parameters submitted for immediate modification were not changed dynamically. For these configuration parameters, the
database must be shutdown and reactivated before the configuration parameter changes become effective.
Please let me know if you have any questions on this.