Am I missing something simple here?
No. Verified the import of data to Other Users schema worked in 4.2 and 17.2, but broke (regressed) in 17.3.
Test case (using 17.3.1):
1. Connect as HR
2. Export DDL for HR.DEPARTMENTS, but first uncheck Show Schema checkbox.
3. Export data for HR.DEPARTMENTS in csv format.
4. Connect as SCOTT, run the DDL file in the worksheet, then grant all on DEPARTMENTS to HR.
5. Optional: disconnect the SCOTT connection in the navigator tree.
6. Under the HR connection in the navigator tree, open nodes for Other Users > SCOTT > DEPARTMENTS
7. Right-click on DEPARTMENTS, select Import Data... and import the csv file.
Expanding all nodes in the Data Import Wizard page, we see...
But after clicking Finish, the import fails with...
So it seems the import is using the schema of the current connection (the destination connection), not the schema of the destination table as shown in the wizard's summary page. Please open an SR with MOS if possible.
Even though your error is
ORA-00942: table or view does not exist
while mine is
ORA-00001: unique constraint (HR.DEPT_ID_PK) violated
that is just consistent with the fact that I have the same table in both HR and SCOTT, while I imagine your current connection does not contain a table of the same name as the destination table.
I am trying to put in an SR on MOS, but I'm getting a negative circular reference during login.
When first entering the site it asks me to associate my account with an SI. To get the SI I need to ask request it from my CUA. To get my CUA I need to be signed in all the way (so I can go into Settings to find them).
Don't know if this link is still current, but this is the advice I found (of course, I have no experience opening SRs)...
and here is info on a more recent (the most recent?) MOS release...
Support Identifiers Unavailable or Missing When Creating an SR
An SI is unavailable, missing, or grayed out when creating a technical SR. To resolve this issue:
- Ensure you have selected the correct tab (Hardware or Software).
- If you are a customer or partner opening an SR against an SI which does not have the support provider selected and you see the following question, you must select No:
Are you creating this Service Request on behalf of an end customer?
- Software customers must select a product before selecting the SI.
And since SQL Developer always ships with Oracle RDBMS, the database is product you need to select.
LOL. Yep... this was the advice I was trying to follow. It seems like at one point you could log in and navigate through some things (like Settings under My Account). Now they want you to put in the SI before you can navigate through your account, so you can't look up your CUA.
Can't fully log in without the SI from the CUA and can't get the CUA because you aren't fully signed in.
I'm part of a sizable organization, so to "manually" find my CUA is going to take some time.
I updated my prior post. See if the new advice makes a difference...
Thanks, but I am still getting same thing. Can't fully log in without the SI from the CUA and can't get the CUA because I'm not fully signed in.
Someone didn't think this one through.
In any event, the developer is aware of this discussion. Hope you are able to get the SR logged.
Update: the developer logged the bug and fixed this regression for the 17.4 quarterly release.