Not only would you have to add the new user but you have to do the following:
- Ensure the new user has the same Privileges as the old user
- Ensure the new user has the same Security access to business areas as the old user
- Change the owner of any workbooks from the old user to the new user
- Change the users involved in shared workbooks
- Consider what to do with scheduled workbooks and the results of scheduled workbooks
The first two you should be able to do yourself within the Discoverer Admin tool.
The third one will need an update script on the EUL5_DOCUMENTS table.In this table is a field called DOC_EU_ID. This is the field that determines the owner of the workbook. You would need to update this field with the EU_ID from the EUL5_EUL_USERS table for the new user.
The fourth item will need an update script on the EUL5_ACCESS_PRIVS table. This table contains metadata about which workbooks have been shared with other users. If you have never shared a workbook you will have a much easier time. However, if you have shared workbooks you will also need to update this table to change the shared_with user, the owning user and the last updated by user.
In EUL5_ACCESS_PRIVS the field AP_TYPE contains GD for a shared document and the following fields are key:
- AP_EU_ID - this is the ID of the user with whom a workbook has been shared
- AP_CREATED_BY - this is the uername, not the ID, of the user that owns the workbook
- AP_UPDATED_BY - this is the username, not the ID, of the user that last updated the sharing - always the same as AP_CREATED_BY
The fifth item on my list is scheduled workbooks. If you have any of these I would recommend canceling the old schedules and setting them up again. Trying to do updates to existing schedules would be a nightmare.
Warning: be very careful when making any SQL updates to EUL5 tables as doing so could mess up your EUL and invalidate your system. Just because I am telling you the names of the fields and tables does not mean I am sanctioning updating them. I have worked with Discoverer for 20 years and I know what I can and cannot update. I always take backups so that I can restore afterwards. I am also aware that I cannot ask Oracle Support to help me out if I mess things up so - be very, very careful. This is not for the feint of heart or novice administrator. I strongly recommend taking a backup of any table you are going to update, just in case, and then do any updates in a test environment first when no users are accessing the system. In other words don't jump right in and start making changes to your production EUL before you are certain what you intend doing will not break the integrity of the system.
Hope this helps