When an OCXO wakes up after a long sleep, it can take a month or more to work the kinks out. The rather ugly phase jumps in the original file could be exactly that. During this initial period you'll also see aging that's so fast it will affect your measurements. Many high-quality OCXOs state that aging can only be measured after 30, 60, even 90 days of continuous operation. Now add in the fact that it's a used unit from China that was probably picked up by a big crane, dropped 5 or 10 meters into a bin, had other big, heavy things dropped on it, maybe shipped overseas in an open bin, and maybe removed from the board by heating the board and banging it on a table. I'd be rather shaky too, if I endured that! I'm amazed that these things work at all, never mind often work quite well! Time will tell whether the crystal will ever settle down properly.
Did you notice the last part of the data that gives a nice straight line? If you delete everything but that part, you'll find that the resulting ADev graph goes down into the low e-12 range! That's looking very nice! Both the frequency and phase plots are clean. The drift shown on the frequency page is -5e-9 which is decent. Hopefully, it will drop further as the unit runs. Maybe this oscillator survived the recycling process intact.
11.68 MHz is completely wrong. An OCXO should never be more than a few KHz off-frequency even if it's stone cold. Use a scope to check the waveform and make sure that there isn't something terribly wrong. For example, if the output is CMOS/TTL and the counter is set to DC triggering at zero volts you'll get some very strange results. An internal fault in the oscillator that results in an extremely low output level could also cause gross errors because the counter is trying to dig through noise to find the signal. I've seen that once or twice.
You mentioned that the frequency doesn't move far enough as the unit warms up. Does that unit have EFC capability? If so, you might need to hook it up to a pot to get the frequency correct. If the unit is old, it may have drifted far enough off frequency that it can't be corrected. I have cracked open a few oscillators to modify them to bring them back on-frequency. It's a lot of work unless it's a really, really good oscillator or just as a learning exercise. If an off-frequency oscillator has really good ADev, it's still useful as a reference to compare other oscillators to. The frequency error isn't important there. In fact, there are other ways to measure ADev that require an off-frequency oscillator. Another interesting fact is that if the frequency starts high and drops as the unit warms up, it's probably an AT-cut crystal. If it starts low and rises, it's probably an SC-cut crystal. There are other crystal cuts, but those two are by far the most common.
Here's a TimeLab hint for you. While you're in the middle of a data run, you can't edit the data. But you can save the .TIM file without affecting the data collection. Now you can reload the .TIM file without affecting the data collection. Now you can edit the saved data as much as you want. If you're doing a long data run, it's not a bad idea to save the .TIM file occasionally in case Murphy sticks his nose in where you don't want it!
Ed