Not all ASP Clients are Oracle 19c
This is an FYI to anyone that is installed, has upgraded to Oracle 19c, and anticipates taking over any plans from any other firms that utilize Relius Administration as their recordkeeping platform and are FIS ASP clients.
We were in this predicament last month when we were scheduled to receive RAX files from an existing ASP client for us to import because we were taking over their plans. We verified that we were utilizing the same version of Relius Administration as the ASP firm, but we were receiving immediate schema errors when we attempted to Import their RAX files.
Come to find out, even though we were on the same version of Relius Administration, we were not on the same version of Oracle. We had upgraded to 19c (as enforced by FIS), however, ironically, the ASP client was still on Oracle 12.
In order to get the RAX imports to work we had to have on hand at least one workstation that was running an Oracle12 desktop client, and the imports could only be done via that one workstation.
So, notice to anyone that is installed (or technically is even ASP, but FIS has upgraded you to 19c) and are planning to take over any plans from another Relius Administration recordkeeping company, you not only need to verify that you are on the same version of Relius Administration, you need to make sure that you are both utilizing the same (or schema-compatible) version of Oracle.
The reverse would likely fail as well. It may not be a problem between 11g and 12c, but 19c and 12c or 11g would most likely fail. We identified the problem was the schema around all fields that were VARCHAR2 fields (even though the fields were VARCHAR2 in both databases they're apparently non-compatible between the older and later versions of Oracle).