To solve this error, you will need to consider a manual procedure to reconfigure the BizagiAdmon user by deleting it and creating it again with the scripts provided within your newer Bizagi version. To do this, carry out the following steps:
1. Delete the current definition for the BizagiAdmon user in your Oracle instance:
Recall that in order to do drop a user, you will need to previously ensure that it is not currently connected and having active sessions.
For instance, you may employ this script to check for active sessions:
SELECT s.sid, s.serial#, s.username
FROM gv$session s
JOIN gv$process p ON p.addr = s.paddr AND p.inst_id = s.inst_id
WHERE s.type != 'BACKGROUND' and s.username = 'BizagiAdmon';
2. Create the user again by running the script provided within the newer Bizagi installation.
This script is found at Bizagi Studio installation path (by default at C:\Program Files\Bizagi\Bizagi Studio\ProjectModel\Database\ConfigureInstanceForBizAgi-11g.basql).
To create this user, explicitly define the relevant parameters for the BizagiAdmon configuration (such as paths or the password):
Notice that the path set for the indexes tablespace is the same base path in which the BizagiLobs tablespace will be stored.
Note that you should run this script with a user with enough rights (e.g., the sys user). Once this is set, ensure that running this script is successful:
And similarly, you may verify that the user has been created:
In addition to the above, you may also evaluate if you wish to migrate LOB type fields into the BizagiLobs tablespace by means of a manual procedure (by default this new tablespace is not configured in upgraded projects), in order to benefit from splitting the data tablespace (provided that this helps your specific project).
If you wish to migrate LOBs to the BizagiLobs tablespace, you will need to execute the following stored procedure:
Make sure you execute the stored procedure by connecting with the user schema of your Bizagi project, once you have ensured that there are no active connections (this task to be scheduled at non-working hours, as recommended in the above Before you start section).
Verify that the execution of the stored procedure is successful: