Hi Joachim..
Thanks for that .. interesting that google found the SAP notes, but not the IBM notes...
I was suspecting that the change was intentional.
In this case, the error message and specially the "User Response" action for SQL5099N rc2 needs a DRASTIC improvement.
the ibm technote says that the user is prompted to specify the correct path.. that's a LIE . the user has no idea on what's happening and how it can be fixed. Either the error message txts, and neither the user response for that error says anything about using the NEWLOGPATH clause in the restore command.
db2 "? SQL5099N"
SQL5099N The value "<value>" indicated by the database configuration
parameter "<parameter>" is not valid, reason code "<reason-code>".
Explanation:
The value of the named parameter is not valid for one of the following
reasons:
...
2
The path does not exist.
...
User response:
Resubmit the command with a valid value for the named parameter.
sqlcode: -5099
User response is a generic one, and should have specific sections for each reason code and possible scenarios, like several other errors details text has ...
For rc 2, and if user is performing a Restore, and IMAGELOGPATH is invalid, resubmit the restore command by using the NEWLOGPATH clause pointing to a valid path for the restored active logs.
Please IBM...
Thanks again Joachim!
------------------------------
Samuel Pizarro
------------------------------
Original Message:
Sent: Mon February 24, 2025 01:37 AM
From: Joachim Müller
Subject: db2 11.5.8 SQL5099N error when Restoring db to a new server
Hello Samuel,
This information from IBM beginning with Db2 11.5.6 is in the SAP Note you mentioned:
Restore returns SQL 5099N database configuration parameter "IMAGELOGPATH" is not valid, reason code "2".
Best regards,
Joachim
------------------------------
Joachim Müller
Original Message:
Sent: Fri February 21, 2025 10:35 PM
From: Samuel Pizarro
Subject: db2 11.5.8 SQL5099N error when Restoring db to a new server
I've managed to overcome this by specifying the NEWLOGPATH clause, and pointing to a valid path at the target system.
I've done hundreds of restores like this before, and I never had to specify NEWLOGPATH for this kind of restore.. if the cfg path that is saved within the image does not exist.. why not just use the defaul path for the log files and move on !?
IBM ??
Regards
------------------------------
Samuel Pizarro
Original Message:
Sent: Fri February 21, 2025 10:14 PM
From: Samuel Pizarro
Subject: db2 11.5.8 SQL5099N error when Restoring db to a new server
Db2 11.5.8 on Windows
Restoring an online bkp into a new server which has different filesystems settings. (redirect restore) on storage group etc ....
Fails with following:
restore db noxgr from D:\backup , D:\backup, D:\backup TAKEN AT 202502 on G: dbpath on G:\ INTO NOXGR replace existing parallelism 6SQL5099N The value "L:\db2ActiveLogs\DB2\NOXGR\" indicated by the databaseconfiguration parameter "IMAGELOGPATH" is not valid, reason code "2".SQLSTATE=08004
Yes, that is the original logpath that only exists at the original server.
Why does it requires this path to exist? it makes no sense !
I've tried also to use LOGTARGET clause at the restore comand, pointing to a valid existing path, but no luck , same error.
I'm stuck !
Also, Found this trhead in SAP site saying exactly the same .. but I am not a SAP customer, and can't see the information.
3193409 - Db2 LUW: Redirected restore errors with SQL5099N for IMAGELOGPATH | SAP Knowledge Base Article
IBM need help !!
------------------------------
Samuel Pizarro
------------------------------