Hi Sajith, Thanks for the response.What is the max and suggested value that can be set for ShiftsInFuture in this case of long time horizon. If I understand correctly , does default value ‘0’ means no shifts in future? Please advise. Regards,Jithesh
Hi Lee,I meant how the old data time would be impacted with the timezone change. If there will be no change to the time that will be good and expected.Regards,Jithesh
Hi Hushan, You are right. This fixed the issue and I was able to complete the upgrade.Thanks for the quick help. Regards,Jithesh
Hi Hushan, There was no 170 folder in C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\ Only 110 was there and it didnt have SQLCMD file. I have copied the folder 170\Tools\Binn from my local system to the customer server along with the SQLCMD file and also added the env variable with the path C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\BinnIt didnt work.. Installation errors with the same message. Regards,Jithesh
Hi Hushan,We tried this already but still gives same error. Regards,Jithesh
Hi Hasara, TNS_ADMIN entry and TNS configuration not added correctly in the env variables which was the cause of the issue. That is updated and issue is fixed. Thanks for your time and response. Regards,Jithesh
Hi Hasara, We have the FSM client 6.5 still working without it upgraded to 6.9 even though FSM DB is on 6.9So I assume there should be no problem with tnsnames.ora However we are checking that again with the DBAs and will revert.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
