Since you are an Off-Cloud customer you will follow the same set of steps that you did to create your current External Archive Destination in the remote Oracle Server.

For Example:

1) Create a new schema (database) in your remote Oracle server
1.a) For Example archive25
1.b) You can set the same Owner as your current archive database

2) Login to Governance as the Admin

3) Go to Data Administration -> Maintenance -> Archive Destination
3.a) Press the New Archive Destination Link
3.a.1) Provide the necessary information (I would utilize a display Name that is helpful)
NOTE: Do not set it as the Current Achive Destination yet
3.b) Press the Test Connection to confirm the information
3.c) Press Save

4) When you are ready to utilize this new Archive database as the "Current" one, enable it. That is it, you have rotated your archive destination.

Once you have completed this step, you can never again write to the "old/prior" archive destination. When the archive destination is set as the "current", the 1st step the system will do is truncate all tables to ensure the database is empty. Therefore, one can never point back to a prior Archive database.

NOTE: This is similar to the behavior when one disables Archiving. The "Current" archive destination will have all of the tables truncated. There is a warning in the UI when one goes to disable archiving that outlines the necessary.

Sincerely,
Steven Williams
Principal Enterprise Architect
OpenText Cybersecurity

What is the business goal with keeping the archives and rotating?    

I'll suggest that if you have a conversation about compliance with the business and get an idea for what reporting artifacts you need as evidence of your governance process, you might not need to keep archives of the IG data around.

--Jim

Hello Steven,

thank you very much for your quick response!

The current archive destination was created by default during the application installation. We are not using a real "external" archive destination, yet. So far I am here:

CREATE USER [username] IDENTIFIED BY [password]
GRANT CREATE SESSION TO [username] WITH ADMIN OPTION
GRANT CREATE TABLE TO [username]
ALTER USER [username] quota unlimited on users
GRANT CREATE VIEW, CREATE PROCEDURE, CREATE SEQUENCE TO [username]

For Oracle, user equals schema, so I created a new user. Where I do not know how to proceed is on the rights on the tables of other schemas. I naturally want to avoid giving too many rights to the user. Is there a documentation or a list of statements that is needed to be executed to get the new schema and user ready?

Thank you and best regards,

Bernhard