Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

%IPM_Repo_Filesystem.Cache is out of sync and causing errors - how to clear out and start fresh #596

Open
chi-leadnorth opened this issue Oct 24, 2024 · 11 comments
Assignees
Labels
bug Something isn't working customer

Comments

@chi-leadnorth
Copy link

Version: zpm-0.9.0-beta
On a new install of IPM and attempting first module installation.

Getting this error upon zpm repo call:
ERROR! SQLCODE: -106 Message: Delete row from table '%IPM_Repo_Filesystem.Cache' with %rowid1' failed, row with this id was not found.

Also getting it when attempting to delete the repo.
In the backend, it appears the repo was recorded in:
%IPM_Repo_Filesystem.Definition and %IPM_Repo.Definition without corresponding row in %IPM_Repo_Filesystem.Cache.
The foreign key constraints prevent me from cleaning the Definitions to try to clear the error.

How can I clear these tables to start anew?

@isc-tleavitt
Copy link
Contributor

@chi-leadnorth thank you so much for trying it out and letting us know you hit this. To clarify, did you previously have IPM 0.7.x running on the instance? What's the specific zpm repo call you're using?

@isc-shuliu can you look into this as a top priority?

@chi-leadnorth
Copy link
Author

I did not have IPM 0.7.x. I encountered an error regarding the LoadStream call when trying to install IPM 0.7.x. Attempted beta on a lark and saw that it worked, so I moved forward with that. Trying to "downshift" back to loading 0.7.x but system is fighting me on that.

More insight -- I see that the backend globals for %IPM_Repo_Filesystem.Cache are populating, but from SQL, selecting from the table shows no rows, but does throw this error: [SQLCODE: <-350>:]

[%msg: <Unexpected error executing SqlCompute code for field 'Version_Postrelease': %0AmBk1+18^%sqlcq.DPTNS.cls14.1 *Prerelease>]

@chi-leadnorth
Copy link
Author

@chi-leadnorth thank you so much for trying it out and letting us know you hit this. To clarify, did you previously have IPM 0.7.x running on the instance? What's the specific zpm repo call you're using?

zpm "repo -name DPTRepo2024 -snapshots 1 -fs -depth 2 -path /share/LN/DPT_2024"

@isc-shuliu
Copy link
Collaborator

Hi @chi-leadnorth, can you also share with us your IRIS version info?

Write $ZV

@chi-leadnorth
Copy link
Author

Hi @chi-leadnorth, can you also share with us your IRIS version info?

Write $ZV

IRIS for UNIX (Red Hat Enterprise Linux 8 for x86-64) 2023.1.2 (Build 450_0_23376U) Wed Apr 24 2024 00:00:42 EDT

@chi-leadnorth
Copy link
Author

Also - in case this helps -- the module I am trying to install is an early release - the HL7 Data Profiling Tool. In case the pre-release status is what is causing the issue on the Sql compute

@isc-shuliu
Copy link
Collaborator

Also - in case this helps -- the module I am trying to install is an early release - the HL7 Data Profiling Tool. In case the pre-release status is what is causing the issue on the Sql compute

That's likely related to the problem. Can you share with me the version string of the module you're installing? I'm trying to reproduce the error but haven't had any luck so far.

@isc-shuliu
Copy link
Collaborator

Actually I just reproduced it :) Looking into the cause now

@isc-shuliu
Copy link
Collaborator

Just identified the bug and implemented the fix in #599

@isc-shuliu isc-shuliu moved this from To Do to In Progress in v0.9.0 release blockers Oct 25, 2024
@isc-shuliu isc-shuliu moved this from In Progress to Done in v0.9.0 release blockers Oct 25, 2024
@isc-shuliu
Copy link
Collaborator

@chi-leadnorth We have a new IPM v0.9.0-beta.27 release published. Can you try to reload the associated xml file, restart your iris instance, and see if you can remove all repos using zpm "repo -delete-all"?

@chi-leadnorth
Copy link
Author

The new release resolved the issue. Thank you kindly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working customer
Projects
Development

Successfully merging a pull request may close this issue.

3 participants