I am using command rollforward db ABCD to end of logs overflow log path ('/db2backup/logs') to apply DB2 archived logs to my staging database. My staging database is in rollforward pending state.

Execution of command is fine when instance user have write permission on path /db2backup/log and execution of command is creating an empty directory structure as NODE0000/LOGSTREAM0000/LOGSTREAM0000/. I want to prevent any write access on path and still want to use same location for log apply.

Please let me know if it's possible to prevent creation of directory structure NODE0000/LOGSTREAM0000/LOGSTREAM0000/ during execution of "rollforward db ABCD to end of logs overflow log path ('/db2backup/logs')".

  • Not sure I understand your requirements, can you elaborate on why you don't want db2 to create the necessary log structure? – Lennart Dec 23 '18 at 11:19
  • The archive logs are available on a shared location and I can only read the logs and due storage I/O problem I can't copy these logs to some other location. So, I am looking for a way through which rollforward command can read the logs but directory structure will be created in some other location – hemant gairola Dec 23 '18 at 12:12
  • Are logfiles from remote server mounted in /db2backup/log? – Lennart Dec 23 '18 at 12:25
  • Yes, the location is remote and mounted at /db2backup/logs – hemant gairola Dec 23 '18 at 12:37
  • Problem is that db2 expects a certain structure below the overflow log path. Can you create that structure and mount there? – Lennart Dec 23 '18 at 12:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.