Ha, progress has been made.
Unfortunately, one step forward, two backwards. Oracle appears now to be having
a laugh!
I've managed to get the case sensitivity to work by using a parameter file, as
suggested by Kim Berg Hansen, as follows:
TOID_NOVALIDATA=(
'"TypeNameWithCamelCase"'
)
Where that's a leading single quote, a double quote, the case sensitive name,
closing double and closing single quote. Easy stuff!
This correctly leads to the message during the import that:
... skipping TOID validation on type USER.TypeNameWithCamelCase
So imp has finally recognised that I have a TOID to ignore. (and by the way, if
you specify the user name as part of the parameter file, you get errors that
the TOID with the same name as the user, not the full name of the type, has not
been found in the import file. Sigh.)
Unfortunately, after ignoring said TOID, imp barfs with the same old errors:
IMP-00061: Warning: Object type "USER"."TypeNameWithCamelCase" already exists
with a different identifier.
IMP-00063: Warning: Skipping table "USER"."TABLENAME" because object type
"USER"."TypeNameWithCamelCase" cannot be created or has a different identifier
I am about ready to go ape, now. 23 hours to test Oracle's workarounds and each
one fails. When it finally gets around to recognising the case sensitive type
names, it says "I'm ignoring this TOID" but then proceeds to throw the same
errors where it looks obvious that it hasn't ignored the TOID in question.
I could rant. (But it won't help.)
Stay tuned! More insanity later ;-)
(It was never this hard on Unix!)
Cheers,
Norm.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
