sfa-siard / SiardGui

SIARD Suite - SiardGui
Other
17 stars 3 forks source link

error extracting metadata from Oracle #28

Open gillianh1 opened 2 years ago

gillianh1 commented 2 years ago

I am trying to extract metadata from a single table on an oracle database using SIARD software (version 2.1.134). We setup a new user with access to one table. The connection works. However unfortunately the database has some underlying permissions granted to public which cannot be removed. This results in the user having some additional access to some objects by default which cannot be removed.

The following error appearing "Database download failed ( java.i.o.IO.Exception: Only one view with the same name allowed per schema!)! Partial download is completed"

The output from the gui when trying to download shows multiple entries for an object type “Routine”

This corresponds to objects in the database object_type=type and type body

Even though there is only one grant to the "type" and "type body" object to the public role it is listed 22 times in the output in gui before failure.

Can you advise if it is possible to resolve this issue?

Thanks

mburri commented 2 years ago

Hi @gillianh1 Thank you for your bug report - this seems to be quite a special case.

Is it possible for you to provide a sample database that we could use to reproduce this issue?

Have they tried exporting the whole database or is that not an option?

gillianh1 commented 2 years ago

I don't have a sample database that I could provide at the moment unfortunately. Do you have an Oracle database that you have extracted from previously? Maybe issue could be reproduced by creating one table and one object of object_type=type?

Not tried exporting the whole database using SIARD as we are unable to get a simple case using one object working.

mburri commented 2 years ago

I just thought that the issue could be caused by the special setup with this dedicated user...

Maybe issue could be reproduced by creating one table and one object of object_type=type?

We will try your suggestion and see if this reproduces the issue.

JacCGeo commented 3 weeks ago

Is there any update on this error? I'm still encountering the same issue, even after creating a special user for this case and granting them select rights to a single table.