I am encountering an error while deploying a model in a new Semarchy instance. I have attached an image of the error message for your reference.
Could you please assist me in resolving this issue?
Your help would be greatly appreciated.
Best regards,
Dounia BOUZOUBAA
Best Answer
A
Alexia SIMOND
said
over 1 year ago
Hello,
Even though this topic was solved over on ticket, I still wanted to provide some investigation leads here for other customers that might face the same behavior.
So, to recontextualize things, when deploying a model there is an error regarding duplicates on the function Levenshtein.
In order to make sense of the root cause, it is important to retrace your steps to have a clear view on the context after which you are encountering the issue. Because, for example, this is something that can be encountered either after a refresh, upgrade or any other action that previously required to do a schema backup. Resulting in 2 schemas on the same database having the Levenshtein function present, creating a dependency for your system.
Restarting tomcat with a cache clearing can also help to avoid any inconsistencies left from in-memory kept elements:
Stop the tomcat on all instances
Delete the folder semarchy under webapps/
Delete the folder Catalina under work/
Delete all logs under logs/
Start tomcat
If after doing so, you are still facing the issue, please run a check consistency and analyze the resulting pde logs. You can do this by:
Open the Application Builder
Menu: <Username> -> Error Log
Click the Menu Icon
Select Check Consistency
Note: Please delete the contents of the PDE Log first. Then export and send the log to the support team.
Finally, check your search_path to make sure that it matches what is recommended in our documentation.
I hope this will help.
But if someone's still facing issues after those steps, please open a ticket to the support team for further analysis (by mentioning the steps already taken and the associated results).
Thank you
1 Comment
A
Alexia SIMOND
said
over 1 year ago
Answer
Hello,
Even though this topic was solved over on ticket, I still wanted to provide some investigation leads here for other customers that might face the same behavior.
So, to recontextualize things, when deploying a model there is an error regarding duplicates on the function Levenshtein.
In order to make sense of the root cause, it is important to retrace your steps to have a clear view on the context after which you are encountering the issue. Because, for example, this is something that can be encountered either after a refresh, upgrade or any other action that previously required to do a schema backup. Resulting in 2 schemas on the same database having the Levenshtein function present, creating a dependency for your system.
Restarting tomcat with a cache clearing can also help to avoid any inconsistencies left from in-memory kept elements:
Stop the tomcat on all instances
Delete the folder semarchy under webapps/
Delete the folder Catalina under work/
Delete all logs under logs/
Start tomcat
If after doing so, you are still facing the issue, please run a check consistency and analyze the resulting pde logs. You can do this by:
Open the Application Builder
Menu: <Username> -> Error Log
Click the Menu Icon
Select Check Consistency
Note: Please delete the contents of the PDE Log first. Then export and send the log to the support team.
Finally, check your search_path to make sure that it matches what is recommended in our documentation.
I hope this will help.
But if someone's still facing issues after those steps, please open a ticket to the support team for further analysis (by mentioning the steps already taken and the associated results).
Dounia BOUZOUBAA
Hello,
I am encountering an error while deploying a model in a new Semarchy instance. I have attached an image of the error message for your reference.
Could you please assist me in resolving this issue?
Your help would be greatly appreciated.
Best regards,
Dounia BOUZOUBAA
Hello,
Even though this topic was solved over on ticket, I still wanted to provide some investigation leads here for other customers that might face the same behavior.
Note: Please delete the contents of the PDE Log first. Then export and send the log to the support team.
I hope this will help.
But if someone's still facing issues after those steps, please open a ticket to the support team for further analysis (by mentioning the steps already taken and the associated results).
Thank you
Alexia SIMOND
Hello,
Even though this topic was solved over on ticket, I still wanted to provide some investigation leads here for other customers that might face the same behavior.
Note: Please delete the contents of the PDE Log first. Then export and send the log to the support team.
I hope this will help.
But if someone's still facing issues after those steps, please open a ticket to the support team for further analysis (by mentioning the steps already taken and the associated results).
Thank you
-
Extend a model with new entities or attributes
-
Data types in xDM
-
Effective date on entities
-
Search using wild cards
-
Export a model from production and import on a development environment
-
"Allow Delete" vs "Allow Removal" privileges
-
LOV label in Named Query
-
Select location on a map and save coordinates
-
Is there a way to set up a master-detail relationship on browse mode?
-
Choose Either a Stepper or A Workflow Based on The User Privileges
See all 346 topics