Hi @Dilshani ,

looking at the error it seems that one of the objects that IAM is trying to create already exists in the database. Was the database cloned from another database? Any chance there is another MT instance connecting to the same database? You can see if there is a another MT instance connecting to the database by querying v$session and checking the IP addresses of the database session to see if there is anything connecting from an IP address different from your new MT instance.

Cheers

This was investigated through a case and R&D provided following steps to drop and recreate IFSIAMSYS schema.

Please note that this was a fresh installation coming from an upgrade, so there were no customer specific IAM configurations in the environment. 

1. Run DROP USER ifsiamsys on db. This should drop the existing IFSIAMSYS schema.

2. Then run the prepare DB step again. This will recreate IFSIAMSYS.

3. After that you can login as Application Owner and run following query.

   SELECT *
   FROM dba_objects
   WHERE owner = 'IFSIAMSYS'
   AND object_type = 'TABLE';

   The result of this query should not contain any objects as schema objects are not created yet.
    
4. Restart ifsapp-iam pod and during the start up the IFSIAMSYS schema objects should be created properly.

Thank you @Sajith D for your support.

Thank you Charith. I tested this one and it fixed the issue.

Hi Charith,

We are having similar case upon completion of upgrade from old version of IFS to IFS Cloud 23R1. But when IFSADMIN attempted to login to IFS Cloud, after user authentication the application could not be loaded with the following error message. Similarly when we check the Pods, IFSAPP-CONNECT only running ½ instead of 2/2.

Do you mean, the corrective action is to do prepare DB like before we do the upgrade process after dropping IFSIAMSYS user? Then we just need to restart IFSAPP-IAM, then it should solve the probelm?

Thanks,

Sutoto