Versions Compared

Version Old Version 12 New Version Current
Changes made by

DevaDarshini.S

DevaDarshini.S

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Expand
titleI am not able to view the log-on screen for Canvas Studio or the ModelHouse application

There could be several reasons for this issue. Some of those are:

  • Ensure that all the Canvas schema scripts have been executed successfully. The scripts are dependent on the credentials given in the ‘config.txt’ file.
  • Connect to each Canvas schema (MODEL, EXPERT, and WIZARD) in the Oracle SQL Developer and check if you are able to view the tables.
  • Ensure the correct schema name and password, port number, and Oracle SID are specified in the respective app/web server configuration. Such configurations in Tomcat server are in the 'server.xml' that is located in the Tomcat folder, e.g. D:\Canvas\apache-tomcat-7.0.67\conf\server.xml.

    server.xml file configuration

  • Stop and restart the Tomcat server and check if you are able to connect to Canvas applications.

...

Expand
titleWhat to do when multiple notifications are sent instead of one?

Multiple emails get triggered even though only one entry in the table (OD_PENDING_MAIL) from where CT picks up records to be sent as email. In such cases refer these kind of errors found in the SystemOut.log (WebSphere log).

  • WTRN0006W: Transaction {0} has timed out after {1} seconds

    For example:

    Code Block
    languagepowershell
     WTRN0006W: Transaction 00000188D7CBD648000000455D953708CCA97D4013E3EDB45FD179E3597A7D478393378300000188D7CBD648000000455D953708CCA97D4013E3EDB45FD179E3597A7D478393378300000001 has timed out after 120 seconds

    Solution: Increase the total transaction lifetime timeout and maximum translation timeout in seconds. These settings can be updated through the WebSphere Application Server console, using Servers > Server Types > WebSphere application servers > server_name > [Container Settings] Container Services > Transaction Service

  • WTRN0037W: The transaction service encountered an error on an xa_recover operation. The resource was com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl@1f5b7ee3. The error code was XAER_RMERR.

    Solution:
    Run the following commands as user SYS:
    Code Block
    languagepowershell
    grant select on pending_trans$ to <user>;
grant select on dba_2pc_pending to <user>;
grant select on dba_pending_transactions to <user>;
grant execute on dbms_system to <user>;  //If using Oracle 10.2.0.3 or lower JDBC driver
grant execute on dbms_xa to <user>; //If using Oracle 10.2.0.4 or higher JDBC driver

    In the above commands, <user> is the username configured in the Oracle datasource's authentication alias.

    Reference link : https://www.ibm.com/support/pages/exception-occurs-during-recovery-oracle-database-transactions

...