Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Object remain after uninstall #693

Closed
j-sieben opened this Issue Jun 6, 2018 · 8 comments

Comments

Projects
None yet
2 participants
@j-sieben
Copy link

j-sieben commented Jun 6, 2018

Hi,
the following object seem to be missing in the uninstall script:
-- Types
UT_COMPOUND_DATA_VALUE, UT_HAVE_COUNT

-- Packages
UT_COMPOUND_DATA_HELPER, UT_COVERAGE_BLOCK, UT_COVERAGE_HELPER_BLOCK, UT_COVERAGE_HELPER_PROFILER, UT_COVERAGE_PROFILER

-- Tables
DBMSPCC_BLOCKS, DBMSPCC_RUNS, DBMSPCC_UNITS

It would be nice if the install script would check for execute grants on DBMS_CRYPTO and DBMS_LOCK upfront to avoid having to uninstall, grant the privs and reinstall again.

Thanks for the outstanding work though!

Best regards,

Jürgen

@j-sieben j-sieben closed this Jun 6, 2018

@j-sieben j-sieben reopened this Jun 6, 2018

@jgebal

This comment has been minimized.

Copy link
Member

jgebal commented Jun 6, 2018

Hi
Good idea with the check - definitely worth adding.

@jgebal

This comment has been minimized.

Copy link
Member

jgebal commented Jun 6, 2018

I've just fixed the uninstall to remove all objects and its now in develop branch.
What version you were using?

@j-sieben

This comment has been minimized.

Copy link
Author

j-sieben commented Jun 6, 2018

Hi jgebal,

thanks for the ultimately fast fix! I just downloaded the latest version some minutes ago and found this issue when trying to install in different users. I first installed into a user but then decided to create a new user for utPLSQL and grant access to the initial user, so this when these issues popped up.

@jgebal

This comment has been minimized.

Copy link
Member

jgebal commented Jun 6, 2018

You probably wouldn't encounter issues if you would use provided create user script.
https://github.com/utPLSQL/utPLSQL/blob/develop/docs/userguide/install.md#manual-installation-procedure

@j-sieben

This comment has been minimized.

Copy link
Author

j-sieben commented Jun 6, 2018

Yes, I saw that later on. But I first wanted to install utPLSQL in an already existing user, which I later found to be a bad idea. Basically, you're right.

@jgebal

This comment has been minimized.

Copy link
Member

jgebal commented Jun 12, 2018

One issue with checking grants.
Install can be ran as SYSDBA user or as any user (when not using headless install).
Depending on who is running we need to check different data dictionary tables DBA_TAB_PRIVS or USER_TAB_PRIVS.
The reason is that user performing the install doesn't really have to have access to DBA views.

@j-sieben

This comment has been minimized.

Copy link
Author

j-sieben commented Jun 13, 2018

@jgebal

This comment has been minimized.

Copy link
Member

jgebal commented Jul 8, 2018

Actually it should be:

  • ALL_TAB_PRIVS when installing into current (connected) user schema
  • DBA_TAB_PRIVS when installing as SYSDBA into another user schema

jgebal added a commit that referenced this issue Jul 9, 2018

Resolves #693
Added scripts to validate privileges before install.

@jgebal jgebal closed this in #705 Jul 9, 2018

@jgebal jgebal added this to the 3.1.2 milestone Jul 18, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.