...

• When the account is created, a password is established for the account.
  Please record these credentials in the local development password safe.
• The credential is not used by any applications--the use of GRANTS ensures the WRITER schema has all the proxy access it needs: select, insert, update, delete.
  Make it as long, complicated, and obtuse as you like (not really--Oracle limits credentials to 30 bytes). We'll only cut and past it the few times we need it.

...

create user geodp### identified by "stored-secret-30-bytes" profile long_password;
alter user geodp###
default tablespace labwaregeodesc
temporary tablespace temp
quota unlimited on labwaregeodesc
quota unlimited on labwareidxgeodescidx
;

grant create session to geodp###;
grant create sequence to geodp###;
grant create table to geodp###;
grant create trigger to geodp###;

Historical Note

During initial development, these roles, privileges, and storage configurations were applied.

• Note that the above are sufficient for operational use.
• Note that storage is moved to dedicated tablespaces (geodesc, geodescidx) for operational use.

1. Granted Roles:
   1. Connect
2. System Privileges:
   1. Advisor
   2. Alter session
   3. Create Credential
   4. Create Database Link
   5. Create Job
   6. Create Procedure
   7. Create Public Synonym
   8. Create Sequence
   9. Create Session
   10. Create Synonym
   11. Create Table
   12. Create Trigger
   13. Create Type
   14. Create View
   15. Create Any Procedure
   16. Debug Connect Session
   17. Drop Public Synonym
   18. Select Any Dictionary
   19. Select Any Table
3. Quotas
   1. LABWARE
   2. LABWAREIDX
   3. USERS |  31457280 | K

2. Clone Database from Existing Project

...

1. Open the table properties in the source connection.
2. Click the SQL tab.
3. Scroll to the bottom of the SQL worksheet.
4. Copy the grant SQL commands.
   Only the grants for WRITER, GUEST, PUBLIC need to be copied. All others are unnecessary.
   Copy grant statements from destination connection
5. Paste these commands into the worksheet in the destination connection.
6. Modify all source schema names to destination schema name.
   

7. Execute and commit the grant SQL commands.
   This is the set that must be repeated for each table in the GEODP### schema.

   Code Block

   -- Add required Grants to Tables in New Project Schema GRANT SELECT, INSERT, UPDATE, DELETE ON "NEW-PROJ-SCHEMA"."TABLE_NAME" TO "WRITER"; GRANT SELECT ON "NEW-PROJ-SCHEMA"."TABLE_NAME" TO "GUEST"; GRANT SELECT ON "NEW-PROJ-SCHEMA"."TABLE_NAME" TO PUBLIC; -- Example for the specific table P_CAPTURE_FILES in schema GEODPTST123 GRANT SELECT, INSERT, UPDATE, DELETE ON "GEODPTST123"."P_CAPTURE_FILES" TO "WRITER"; GRANT SELECT ON "GEODPTST123"."P_CAPTURE_FILES" TO "GUEST"; GRANT SELECT ON " GEODPTST123"." P_CAPTURE_FILES " TO PUBLIC;

   At this point the new project should be ready for use by GEODESC applications.

4. Register the new project in table GEODCAT.PROJECTS

...