Bugfix/non sysdba install#660
Conversation
…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
|
Would it make sense to split the public synonyms and grants too? |
| ```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 |
There was a problem hiding this comment.
That can be executed using the utplsql v3 owner, so if you don't have admin user access you can still install.
There was a problem hiding this comment.
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.
|
Regarding public synonyms.
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 Maybe some conditional logic could be present in the scripts to decide; i.e.
|
3 participants
Implements fix when installing utPLSQL manually:
Fixes #658