The oks2coral is permanently running in the initial partition. When a new run is started, the oks2coral_mk_tmp_file.sh script merges used oks configuration files into single schema and data files and puts them into directory defined by the OKS2CORAL_TMP_DIR config parameter. The oks2coral binary is running in the initial partition and periodically scans this directory looking for new .data.xm files. When new file is found, it tries to archive it and in case of success removes the data file and corresponding schema one. If found file is bad (e.g. cannot be loaded, cannot find corresponding partition object), the oks2coral ignores it in future scans. If a file cannot be archived because of the RDBMS / CORAL problems (timeouts, quota, wrong OKS schema in HEAD version), the oks2coral will try to archive it again with low frequency (once per several tens of minutes); it may succeed in future if one fixes the problem without restarting the oks2coral.