Hello, We have successfully done an upgrade from Appian 7.7 to 16.1 and hav

Adel Ammari over 9 years ago

Hello,
We have successfully done an upgrade from Appian 7.7 to 16.1 and have applied the latest Hotfix Package B. But we are facing these error messages which we are not able to resolve or get around. Below are further stuff we noticed:

- All engines are OKAY.
- Database started.
- Search Server Started.
- When starting jboss, no errors except for "10:42:08,591 ERROR [stderr] (Spring executor 3) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found", which can be ignored i guess.
- We are able to login normally to Appian as well, except that some connections to some records is broken (when using the "feed" view) but works normal (when using the new "list" view).
- But soon after we click on tasks or records, we get a huge block of errors which we are not able to solve.

Furthermore, we noticed that whenever we save any query rule or datastore, inst...

LogsAndScreenshot.zip

Discussion posts and replies are publicly visible

0 Adel Ammari over 9 years ago

Hello Khalil, thank you for your answer, but no, we neither get this error or startup nor when we run a certain query. Jboss starts normally and Appian is behaving normally, without anyone using Appian, a couple of minutes later we start seeing CLOB errors, which keep showing up every couple of minutes as per the screenshot below. Keep in mind that there are no users using the system whatsoever, so i think this is related to something within the upgraded product.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tom Ryan
Appian Employee
over 9 years ago

Do you have any validation queries configured for your datasources (in appian-ds.xml for JBoss)?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Adel Ammari over 9 years ago

Nope, we only have the below [db connection URL has been omitted]
<?xml version="1.0" encoding="UTF-8"?>
<datasources
xmlns:xsi="www.w3.org/.../XMLSchema-instance"
xsi:noNamespaceSchemaLocation="www.jboss.org/.../datasources_1_0.xsd">
<xa-datasource
jndi-name="jdbc/OracleDSPrimary"
pool-name="OracleDS"
use-java-context="false">
<xa-datasource-property name="URL">jdbc:oracle:thin:@*****.************.*****:****:*****</xa-datasource-property>
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
<driver>oracle.jdbc</driver>
<security>
<security-domain>ds-name-appian1</security-domain>
</security>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
<xa-pool>
<min-pool-size>5</min-pool-size>
<max-pool-size>100</max-pool-size>
</xa-pool>
<timeout>
<blocking-timeout-millis>5000</blocking-timeout-millis>
<idle-timeout-minutes>5</idle-timeout-minutes>
</timeout>
</xa-datasource>
</datasources>
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tom Ryan
Appian Employee
over 9 years ago

In that case, can you confirm that you are using either the appropriate driver version as listed here: forum.appian.com/.../System_Requirements.html or a more recent version?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Adel Ammari over 9 years ago

Thanks for pointing that out, we had not replaced the driver when we did the upgrade, i just replaced it now with the latest one as its the one which works with JDK 8, lets see how things go now.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Adel Ammari over 9 years ago

Hello, even after having the latest driver, we still get the CLOB messages!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tom Ryan
Appian Employee
over 9 years ago

After some further research it seems this error:

ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00932: inconsistent datatypes: expected - got CLOB

is related to an internal query used for populating a Sites metric log forum.appian.com/.../Logging.html. I expect this log will be blank but otherwise no impact, so you can disregard the error. Otherwise you can hide it by turning off the JDBC Exception Reporter logger, but this could obscure other relevant errors.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Adel Ammari over 9 years ago

I see, as long as its safe to disregard, we will just do so. Thank you so much for your awesome explanation and drill down of the problem(s). Kudos
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel