Switching Keys 

Use

If you suspect that unauthorized parties know the key that you have been using, change it.

...

Procedure

...

       1.      Create a new file with the new key.

       2.      Change the profile parameter so that it points to the new key file. (For systems with multiple application servers, you must do this for all servers.)

       3.      Start transaction SECSTORE and choose Global key changed.

       4.      Enter the previous key in the input field, and choose Execute.

Result

The result list shows the successfully migrated entries and the entries that are not to be migrated, which were already created with the new key.

If entries remain in the error status Incorrect global key for the secure storage, these entries were created with a key other than the entered old key.

If you specify an incorrect key in transaction SECSTORE; it does not do any damage. If the database contains entries that were created with multiple versions of the key, you can migrate these in stages, by entering all of the used keys in turn and performing the migration in each case.