Solution: BI Issues after Account Rename

Posted on Updated on

Occasionally, when a Fusion user account is renamed, there is a sync issue that prevents the end-user accessing BI. Sometimes the data gets back in-sync within an hour or so, however sometimes the issue persists.

People get married or divorced and change their surname, or may have a name change for several other perfectly legitimate reasons. So renaming user accounts is an occasional but necessary part of most customer’s business-as-usual function – the only reason it might not be needed is if users log on with their employee id, or similar.

If the user has previously accessed BI using their old account name, after the rename they may either get an ‘Error 500–Internal Server Error’ or may be told ‘You are not currently signed in to the Oracle BI Server’, or may just receive blank output while trying to view BI content.

Previously, the solution was to raise an SR with Oracle and the issue would be resolved, however now Oracle have made available a handy self-service utility so we can sort the issue ourselves. Here’s how it works:

1) Locate the URL for the pod

This will be something like:
https://abcd.fa.em2.oraclecloud.com

2) Create the input file

This will be <old username>;<new username> with one pair per line. e.g.
user1;user10
user2;user20

Save this as a .txt file. Other than the extension the filename isn’t important.

3) Download the rename tool

It can be found here.

Unzip the archive and locate ‘RenameAccts.jar’.

If your version of Java is old (pre-1.8 you may hit issues here).

4) Execute the rename tool

Double click RenameAccts.jar and click OK at the first dialogue.

Fill out the fields in the Rename Accounts Details screen. It’s pretty self explanatory:

For the URL just use the fully qualified domain name from step #1, not anything after the domain.

Once you click Submit it’ll prompt you for a file. Select the one you prepared in step #2.

It’ll then take a little while to process. At least 10 seconds, maybe more depending up how many rows are in the file.

5) Checking the logs

Once it’s done it’ll say that it’s completed, however this does not mean it was successful. You need to check the logs.

Browse to the same directory that the RenameAccts.jar file resides and look for two log files.

RenameAccounts.out – contains details of successful updates e.g.

User :PrevUser is renamed to user: NewUser

RenameAccountsErrors.out – contains details of unsuccessful updates e.g.

Error while renaming user :PrevUser to : NewUser
Account not found. Please see the server log to find more detail regarding exact cause of the failure.

Tip: it does not appear as though the username is case sensitive in the update.

Tip: Oracle also include a PDF walkthrough of this process at this link.

Tip: If the rename has already happened and you cannot remember what the username used to be, then query FND_SESSIONS to locate the username as it was.