Skip to content

Bugfix/non sysdba install #660

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

Merged
merged 10 commits into from
May 12, 2018
Merged

Bugfix/non sysdba install #660

merged 10 commits into from
May 12, 2018

Conversation

pocelka
Copy link

@pocelka pocelka commented May 4, 2018

Implements fix when installing utPLSQL manually:

  • dba creates user
  • dba / ut3 owner / ut3 user install rest of the framework manaully

Fixes #658

Peter Ocelka added 5 commits May 4, 2018 17:39
…ot dropped. Then when new version is installed manually without user creation, this script failed as table already exists in the schema.
…rformed also with new user creation; Added purge for UT_OUTPUT_BUFFER_TMP$ to drop also overflow segment table
@jgebal
Copy link
Member

jgebal commented May 4, 2018

Would it make sense to split the public synonyms and grants too?


Example invocation:
```bash
cd source
sqlplus admin/admins_password@database @create_synonyms_and_grants_for_user.sql ut3 hr
sqlplus admin/admins_password@database @create_user_grants.sql ut3 hr
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That can be executed using the utplsql v3 owner, so if you don't have admin user access you can still install.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thats true. It depends on what you will imagine behind "admin user". I will change the description in docs. It can be sysdba as well as ut3 user. It really depends on the who is executing the script.

@pocelka
Copy link
Author

pocelka commented May 4, 2018

Regarding public synonyms.

create_synonyms_and_grants_for_public.sql is excuted only when you install with headless script (dba running it). It doesn't make sense to me right now to change it, however it is possible.

Then we should think about the installation process in general. Because if you would want to run the synonyms script as ut3 user, than ut3 user would need grant create public synonym; which can be a problem for some DBAs.

Maybe some conditional logic could be present in the scripts to decide; i.e.

  • create user would contain question if public synonyms should be created? They can be created even if objects dont exists.
  • then installation itself would contain just core scripts and grants

@jgebal jgebal added this to the 3.1.2 milestone May 12, 2018
@jgebal jgebal merged commit 61066a9 into utPLSQL:develop May 12, 2018
@pocelka pocelka deleted the bugfix/non_sysdba_install branch May 14, 2018 06:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

non-sysdba installation
3 participants