I had asked Oracle to put TAR to sleep. They, however, closed it. Also, I doubt this is worth the time on my part to persue. The workaround of using the 9.2 DB to hold the DB works quite well and is available. It also separates our data from Oracle's data, which is also a good reason to keep in separate DBs. Evidently the current Oracle Portal release is not going to let us do what I wanted anyway.
Here are a couple exerts from the TAR:
"
22-OCT-04 17:51:07 GMT
RESPONSE:
===========
The problem could be due to the binary being from the portal database. Since you are using this binary, there are most likely issues re
lated to that. 9015, which is the version of the export utility that is being u
sed, is specific to Portal as we do not have an actual database release of that
version. This is why I sent you these articles.
Regards,
...
22-OCT-04 19:43:09 GMT
Let me know if the articles help at all. If not, you may have to use the 920x binary but I don't believe you can import back into the 9015 Portal database wit
h that. I believe that the articles go through the steps on getting the exports
and also importing.
Regards,
...
31-OCT-04 01:51:18 GMT
New info : I read through the articles. Don't see anything that would tell us
how to do what we need to do there.
Charlie

10/30/04
...
11-NOV-04 17:42:12 GMT
CUSTOMER CONTACT:
======================
Hello Charlie,
I apologize for the late response to this issue. I have tried to find any issues related to this and unfortunately we do not have any filed other than the normal issues related to running CATEXP, which we have already addressed. I was reviewing the details of the SR and I see that the 920x instance is running 9201 base...is this correct? If so, would you be able to apply the 9205 patchset, run CATPATCH.SQL in migrate mode, CATEXP.SQL and then try the export again. I am not sure if this is a problem with the combination of 9015 and 9201. Let me know if you can do this.
Thanks,
..."
Sincerely,
Charlie

1/4/05