Just wondering if your company restarts Windchill on a set schedule or just when problems start occurring?
We usually restart Windchill when it becomes sluggish or comes up with the creo workspace repetitive warnings such as "no connection can be found, do you want to work offline".
We usually only restart when some type of maintenance is required - either a critical patch set is installed or some property needs to be changed. I'd say this happens on average about once a month.
WC 10.2 M030 / MS SQL 2012 / Windows Server 2012
In an idea situation Windchill rarely needs to be restarted, but it can also depends on the OS on which it is running too, or other factors. Windows systems occasionally get updates that require server restarts, thus requiring Windchill restarts too. It isn't so much that there is a "correct" or "expected" frequency, but rather what is optimal for your installation.
Other factors can also influence the frequency of restart too, such as backup strategy. I have worked with customers that range from only doing restarts as necessary for maintenance updates or code changes, to a weekly cold backup done on Saturdays requiring WC to be down for the DB/LDAP dump, to performing restarts every night at midnight, with Windchill down for a few hours each night for daily cold DB/LDAP dumps.
I'm interested in your comment in that you see "no connection can be found" warnings repeatedly in Creo. My company provides Windchill maintenance and monitoring services, and we'd be happy to provide an assessment to get to the root of this issue or other issues you are experiencing. If you are interested, please send me an e-mail at firstname.lastname@example.org.
We shutdown every night with a script. The script shuts down the windchill related services, backs up a few critical files, cleans out some cache files and restarts Windchill. Overall the process takes ~10 minutes.
We implemented this procedure at the advice of our VAR/Consultant and I have to say, we have seen very few Windchill issues, and the performance is pretty stellar.
We do the same as described by Marc.
We also restart Windchill every night to align some attribute (selectable from a drop down list) shared with our ERP (which is master for this attributes).
We do maintenance monthly. But I do not think this is going to solve your problem of no connection can be found. We had a similar issue. What version of Creo are you using?
We also shutdown Windchill every night. We do it so we can make a cold-backup. We dont want Windchill running when doing the backup.
We only restart in case of updating the software - so maybe once in 2 months. Making a Backup can be done within oracle without shutting down Windchill.
Shutting Windchill down also has the risk that someone is working within Windchill and things get messed up. I can't see any reason why it should be safer to shut
If you have problems like " "no connection can be found, do you want to work offline"." you definetly should contact the PTC support to sort this out.
Unfortunately we did not have much help from PTC. It appears to be a response issue between the server and client. We put sniffers at the server and just before the client. If I can dig up more information I collected, I'll let you know. It was a while ago we experienced this issue.
You need to check this with PTC technical support. May be you have network issues between your client and server, this you can check with your network team, if you have one.
We restart the WIndchill, Oracle and publishing engine every morning at 5:00AM.
I do an Oracle dump at 9:00PM and IT does system backups starting at 10:00PM.
While the daily restarts may not be necessary, the systems give us no performance issues during the day.
I have worked at a site where the hardware was not sized properly and we rebooted 3 times a day on some days. My first upgrade there was to a more powerful server for Windchill. The users noticed the difference right away.
When I got here, the servers were marginal, so we ordered new hardware before going to Windchill 10. I moved the Oracle database over to a new server over Christmas and the users also noticed that Windchill queries were faster. The whole system got even faster when we put 10.0 on the new hardware.