Finding diffs between actual and expected schema contents?

RE: Finding diffs between actual and expected schema contents?

Thenmozhi Mohanakrishnan — Tue, 23 Aug 2022 02:10:37 GMT

The database schema does not map to the structure expected by the following datastores: [null]. No DDL files exist to update the datastore schema..

In my case, I was getting the same above error when I missed to push a CDT object, but included that CDTs entity in the DataStore. So was able to fix it by adding the missing CDT.

RE: Finding diffs between actual and expected schema contents?

josep — Tue, 08 Aug 2017 09:51:29 GMT

I am glad you solved the issue, add this verification to your checklist, so the next time you don't spend too much time on it.

RE: Finding diffs between actual and expected schema contents?

bruceh0001 — Mon, 07 Aug 2017 19:53:11 GMT

Hi Abhinav/Jose,

Both of you had the right ideas, it was a combination of a missing synonym and a missing grant on the synonym for a sequence. Our privilege separation requires synonyms for the schema access to work right, and one of those grants was missing. Thanks to you both for the pointers in the right direction, much appreciated!

RE: Finding diffs between actual and expected schema contents?

abhinavg712 — Mon, 07 Aug 2017 16:42:27 GMT

Extra DDL changes does not matter as long as they are not used in data store mappings.

Can you share the inspection logs please for data store package.

RE: Finding diffs between actual and expected schema contents?

bruceh0001 — Mon, 07 Aug 2017 16:11:38 GMT

Unfortunately not, still getting errors after the DDL scripts were run because we're still missing something. I assume any "extra" stuff will be fine as long as we're not missing a table/column/grant that we need, is that correct?

RE: Finding diffs between actual and expected schema contents?

abhinavg712 — Mon, 07 Aug 2017 16:09:47 GMT

So, the issue has been resolved ?

RE: Finding diffs between actual and expected schema contents?

bruceh0001 — Mon, 07 Aug 2017 14:44:11 GMT

Thanks Abhinav. That's actually part of the issue I'm facing. One of my QA engineers ran a bad DDL script and then ran another over top of it, which put us in a bit of a pickle w.r.t. the current state of the database. Wanted to reply quickly to verify that this step was indeed completed, and in this case actually caused the issue.

RE: Finding diffs between actual and expected schema contents?

bruceh0001 — Mon, 07 Aug 2017 14:42:34 GMT

Hi Jose,

I'll check the grants. The DB diffs I've run so far are showing the structure itself is the same as the source DB that the changes came from.

Dumb question (speaking from ignorance again). If I import using the force_import flag, then verify the datastore, would that tell me what I'm missing? Any irreversible risks with this approach?

RE: Finding diffs between actual and expected schema contents?

abhinavg712 — Sat, 05 Aug 2017 16:17:16 GMT

Before deploying your Appian packages containing Datastores, can you makes sure the Target Database is updated with respective DDL changes, if not, please run the DDL before inspecting the Datastores containing package.

Datastores being exported from source system has updated data mapping resulted in the error being seen on target system.

RE: Finding diffs between actual and expected schema contents?

josep — Sat, 05 Aug 2017 00:12:23 GMT

Hi Bruce,

Depending on the database you are using you can have different options to compare, for the tags it seems like you have oracle, then you can use SQL Developer to compare the surce and target and see the structure difference:
SQL Developer > MEnu:Tools > option database Diff

- Sounds like you have run the "Verify and publish" in the datasrore?
- Not always is the structure,, take a look at the "Grants" (security )

Best Regards
Jose Perez