Move CMOD 9.5 to new windows server, remote db not changing

[Shannan]

We moved our small CMOD system to a new windows 2012 server (from 2008).  The archive DB is on a remote system and did not move.  Installed same version of CMOD to new server, copied all arstmp, arscache, arsload…. folders to new server.  Had issue with retr folder copying from arscache folder though - link files that wouldn't copy.  Configured new instance on new server, using same settings as old system.  Am able to view all reports ok - reports are stored in cache and tsm.  But now having issues loading new reports (error 88) but not able to get additional information on why failing.  Can anyone talk about steps for moving CMOD 9.5?  Or do you have any ideas what to check on the loads failing?  Tried enabling tracing, but trace file doesn't have anything more than the header.   We moved it years ago with the same process but no issues, (not sure when retr folder came to be and if that's the cause of my load issue or not)

[jsquizz]

Whats the exact error message you are getting in the system log 88 message?

What's the other error message associated with the 88, assuming it's probably storage related..?

[Shannan]

Thank you!  I was able to find the issue with my 88 - a new AG with the remotedb needs special handling (db2 db on remote host) and existing AG item was hitting an issue with the cache value having been cleared out.  So now am getting things to load successfully. (Yay!)   

Do you know about the link items in the arscache retr folder?  Will it cause any future issues not having those link items or is there a way to recreate them or such? I asked IBM about them and they said there wasn't any documentation about moving CMOD from one server to another and they couldn't answer the question about the retr folder items?? 

[Justin Derrick]

To understand what went wrong in your cache, start here...

https://odug.tv/ODUG-TC-2019-CMOD-Cache.mp4

... then pop back and ask any questions you might have.

-JD.

[Shannan]

Thank you for sharing that link!  Very beneficial!  So, we have a pretty small OD system, and all reports are being stored in both cache and TSM when loaded.  I've never run the expire of cache items - largely because I haven't had too (since pretty small).  In the presentation, it says that Windows is just using the text files in the retr folder but it looks like I have 'link' objects now too so did Windows add that?  Would I be able to zip the retr folder and get those link objects to move (ie like the tar for unix)?  During our move to the new server, the cache folders are all named the same as on the previous server so no name changes, etc...  The only thing I have seen a problem viewing have been old system log details which isn't a huge issue, but thinking that's because of these link objects?  I did not know about the cache verify option, so will look at that too.  Just want to make sure I don't find other issues later due to the 'link' objects not copying successfully - this would explain why when we upgraded/moved CMOD last time, we didn't have issues copying (ie the link objects are a newer thing for windows)

[Shannan]

think I have the copy for the .symlink items in windows xcopy /b /i . After watching your video, I could see that the links must have been added during the last upgrade - so pre-that, we have the text files and then the links.  So I just need to copy my links to add to my other cache items.  Thank you for the help in understanding how the links were used in unix/etc - that helped me understand what I needed for windows! 

[Justin Derrick]

I'm delighted to see that Alessandro's presentation helped. 

-JD.