Finding diffs between actual and expected schema contents?

bruceh0001 over 7 years ago

I'm still new to Appian, so I apologize if I get some of the terminology incorrect.

I am seeing deployment errors in the deploymentautomation.log:

2017-08-04 14:24:17,577 [main] INFO com.appiancorp.ps.plugins.automatedimport.remote.DeployUtils - Status: Failed. Current step: Inspecting Application. Error message: Error occured during inspection. The database schema does not map to the structure expected by the following datastores: [33995, 3072, 3079]. No DDL files exist to update the datastore schema.

I work in an environment with privilege separation between model.publisher and the database users, so I cannot include the DDL files in the import package, and instead must run the scripts separately. In this case, however, the database schema either contains something it shouldn't, or is missing something it needs, but the error message above isn't very helpful. Does anyone know of another log file I can look at, or a debug option I can turn on to see more detail?

None of the logs in the "logs" folder seemed to be of any help. Thanks in advance for any pointers.

Discussion posts and replies are publicly visible

Top Replies

bruceh0001 over 7 years ago in reply to abhinavg712 +1

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…

0 josep over 7 years ago

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 abhinavg712
Certified Lead Developer
over 7 years ago

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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 bruceh0001 over 7 years ago

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?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 bruceh0001 over 7 years ago in reply to abhinavg712

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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 abhinavg712
Certified Lead Developer
over 7 years ago in reply to bruceh0001

So, the issue has been resolved ?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 bruceh0001 over 7 years ago in reply to abhinavg712

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?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 abhinavg712
Certified Lead Developer
over 7 years ago in reply to bruceh0001

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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 bruceh0001 over 7 years ago in reply to abhinavg712

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!
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel
0 josep over 7 years ago in reply to bruceh0001

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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

0 Thenmozhi Mohanakrishnan

Certified Senior Developer

over 2 years ago

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.