Error on Export after Export/Import

[Stefaney-MP]

Hi,

sorry to bother you again, but we are experiencing a weird error: We have a model, which is exported to a freshly initialized DB - successfully. When the model is closed and imported again, the import finishes successfully as well. BUT: If anything gets changed (might be just a comment), and another export is performed, we receive a couple of errors:

There seems to be something wrong with the model, after trying to export the model again I'm stuck - even save-as doesn't work any more, no file gets written. If i don't perform the DB-actions, save-as works as usual - the file gets written. It seems, that the failed DB-export even breaks the usual save-function.

How can i determine which part of the model is invalid (if that's the case at all.....) - and how to fix this issue?

DatabasePlugin.log

[herve91]

Hi,

The error message indicates that you've got connections (a connection is an arrow in a view) which lost their target which, of course, should never happen.

I did the same test as you:

1. initialise new empty database
2. open model from archimate file
3. export model to empty database
4. close model
5. import model from database
6. update some components
7. export updates to database

I do not experience any error in my model DatabasePlugin.log

I will continue to conduct tests to understand what could happen.

[Stefaney-MP]

Hi,

I don't think, that our problem necessarily has something to do with the plugin – I can exactly pinpoint the version, where things started to go wrong. But I have no idea, which relation causes the error, so the fix is almost impossible. I could offer to send you the problematic archimate-File (and the version prior to that) via PM, if this is possible.

Kind Regards, Stefan Ey

[herve91]

yes, sure. It will helps a lot.

My email is herve.jouin (at) gmail.com

I can sign a non disclosure agreement if you wish. I already did it for some companies.

[herve91]

Just release version 4.9.0.beta. You should not experience the error message anymore.

Could you please check ?

[Stefaney-MP]

I tried installing the beta; there is however an additional error when connecting to the DB (missing left parenthesis):

The logfile is unfortunately of little help:

DatabasePlugin.log

[Stefaney-MP]

Prior to the error i'm asked to upgrade the DB - which i acknowledged

[herve91]

You are right. I just released a fix even if I did not change the plugin numbering.

Unfortunately, as the plugin cannot rollback after a table creation, your database has been left in an "in between" situation that is not handled by the plugin. Therfore, you need to manually delete the two following tables in your database: PROFILES and PROFILES_IN_MODEL.

Once those two tables are deleted, the plugin will be able to upgrade the database from version 4.9.0.alpha to 4.9.0.beta.

Please do not hesitate to drop me a line should you require assistance to drop those 2 tables.

[Stefaney-MP]

I dropped both tables; now the DB has the following tables:

BENDPOINTS DATABASE_VERSION ELEMENTS ELEMENTS_IN_MODEL FEATURES FOLDERS FOLDERS_IN_MODEL IMAGES METADATA MODELS PROPERTIES RELATIONSHIPS RELATIONSHIPS_IN_MODEL VIEWS VIEWS_CONNECTIONS VIEWS_CONNECTIONS_IN_VIEW VIEWS_IN_MODEL VIEWS_OBJECTS VIEWS_OBJECTS_IN_VIEW

When trying to import I'm prompted to upgrade the Database again - If i choose "Yes" the same error (left parenthesis missing) occurs and the 2 tables are present again.

Just to be precise: i also receive the error when upgrading from 4.8.2 to 4.9.alpha - so right now we are stuck with 4.8.2

But there is good news too: this time i get a decent logfile, so the error is visible: ALTER TABLE ARCHI.elements ADD ( profile VARCHAR ) doesn't work with oracle, since the length of the profile-column has to be specified e.g. ALTER TABLE ARCHI.elements ADD ( profile VARCHAR(100) )

DatabasePlugin.log

[herve91]

Yes indeed, that's what I corrected yesterday. Please download the plugin again (even if I did not update its version) and install this new one in Archi.

Then accept the upgrade process and it will succeed.

[Stefaney-MP]

Thanks for the update; the upgrade now works perfectly. Something however still seems to be wrong, since the import doesn't finish; I'm stuck - might be after importing folders:

It seems, that the plugin isn't doing anything any more, there is no active statement at the DB-level. The last recorded DB-statement was

SELECT DISTINCT element_id, parent_folder_id, version, class, name, TYPE, TO_CHAR (documentation) AS documentation, profile, created_on, properties, features, checksum FROM ARCHI.elements_in_model JOIN ARCHI.elements ON elements.id = element_id AND version = (SELECT MAX (version) FROM ARCHI.elements WHERE id = element_id) WHERE model_id = :1 AND model_version = :2 GROUP BY element_id, parent_folder_id, version, class, name, TYPE, TO_CHAR (documentation), profile, created_on, properties, features, checksum

The DB-Log doesn't provide any clues - it seems, that the DB is not the reason for the issue.

[Uploading DatabasePlugin.log…]()

My steps were:

• Plugin 4.8.2: Export model to DB
• Uninstall 4.8.2
• Install 4.9.0 current beta
• Migrate DB
• Import model

[herve91]

Weird ... I do not experience the same behaviour.

I can't retreive your log file. Can you upload it again please ?

[Stefaney-MP]

Sure

DatabasePlugin.log

[herve91]

Unfortunately, I can't do anything with your logfile as you didn't switch the plugin log to trace mode.

Anyway, I received your model by email and export it and imported it back from my Oracle database without any issue. What puzzles me, it that the behaviour you describe let me think of a lock on the elements table. Even if my plugin creates a transaction when it exports a model, it does not create locks on tables. When it exports a model, it blocks other users to export to the same model at the same time, but does not block imports.

To ensure the lock is not caused by my plugin, please quit Archi, run it again and retry your import.

If your issue is not fixed, you may check if you have another process connected to the database. You may also check in the database itself if there is a lock on the elements table. Do you know how to do it or do you need assistance ?

[Stefaney-MP]

Sorry for my last error-report; there has been a version-mismatch: i was using plugin 4.9 with archi 4.8.1; when i "upgrade" to archi 4.9 everything - especially the import - works the way it should.

Thanks again for your support - from my point of view this issue/bug is resolved!

[herve91]

No prob. I prefer it that way :)