I am installing TRIRIGA 3.5.0/10.5.0 on my local machine with WebLogic and Oracle 12c. But I am getting the following error:
[java] Connecting to system@jdbc:oracle:thin:@localhost:1521:orcl
[java] Exception encountered! java.sql.SQLException: ORA-65048: error encountered when processing the current DDL statement in pluggable database PDBORCL
[java] ORA-00959: tablespace 'TRIDATA_DATA' does not exist...
Installing to a pluggable database (PDB) or container database (CDB) is not supported in TRIRIGA 3.5.0. To resolve this, you will need to use the 3.5.2 platform installer or higher. Here is the 3.5.2 release note:
Installation: The installation of TRIRIGA Platform now supports connecting to Oracle via Service Name. This will allow you to use a RAC URL, or PDB installations. The installer will prompt for connecting via the older SID, or the Service Name as a section choice. (Tri-213951)
[Admin: This post is related to the 07.07.16 post and 01.26.16 post about getting an Oracle 12c error during install.]
I have been trying to do an object migration (OM) import, but I am getting a validation error on one of the navigation collections contained in the OM package. It is not an error I have seen before, so I wondered if anyone could tell me what it meant? And how I can resolve it?
Which TRIRIGA Platform version are you using? I know we fixed an issue related to OM packages in our TRIRIGA 3.5.2 release, where certain navigation items were not exporting correctly, which may be related to you having problems importing the object. The following is the text from the TRIRIGA 3.5.2 release notes:
“Resolved object migration issues where Navigation Items may not export correctly if the Dynamic Label check box was selected and the Dynamic Label Query was not selected on the Navigation Item definition. (Tri-250723)”
[Admin: This post is related to the 05.19.16 post about inconsistent OM validation results. To see other related posts, use the Object Migration tag.]
We are currently planning our 3.5.2 upgrade, and I noticed in the 3.5.2 release notes that the “Reverse Association” flag is being deprecated in a future release. I’m assuming that the legacy queries which used this flag have been or are being changed and included in the application upgrades.
Is it possible that a list of these queries is published so that those of us who are not currently taking application upgrades can make the fixes manually? Or is there a way that we can easily query which queries are currently using this flag?
Here’s an SQL you can run to see which queries are using this flag. Note that while it will be fine to uncheck the “Reverse Association” flag for the vast majority of these queries, there may be some where this flag was intended and a larger redesign of the functionality is needed. I know I’ve purposefully used it once in the last ten years, but that was more to understand how it worked exactly and haven’t used it since…
Starting with the TRIRIGA 3.5.0 platform release, the Object Migration tool’s “Full Package” create mode was removed from the Object Migration tool. But with TRIRIGA 3.5.2, the new “Full Metadata Package” was added in its place.
From the 3.5.2 Release Notes
- Release Notes > Object Migration: The Create Mode field in Object Migration now contains a Full Metadata Package option. With this option, the export package contains all objects from the entire TRIRIGA system, except for most record data. The record data for Classifications is included in the package. However, any record data that is associated to the classifications is not included. This option replaces the Full Package option available in earlier releases.
From the 3.5.2 Knowledge Center
- New features > Create Full Metadata Package export option: You can create an export package that contains all objects from the entire system, except for most record data. The record data for Classifications is included in the package. However, any record data that is associated to the classifications is not included. This menu replaces the Full Package option of earlier versions.
- Creating an export package: To create a package that contains all objects, select Full Metadata Package. The package will contain all objects from the entire system, except for most record data. The record data for Classifications is included in the package. However, any record data that is associated to the classifications is not included.
Where is the information regarding IBM TRIRIGA Application Platform 3.5.2 and IBM TRIRIGA 10.5.2 features, installation, and more?
[Admin: This post is related to the 06.13.16 post about finding 3.5.1 and 10.5.1 information, the 12.11.15 post about finding 3.5.0 and 10.5.0 information, and the 10.01.15 post about finding 3.4.2 and 10.4.2 information. To see other related posts, search “where is the latest“ or “where can you find“.]
[Updated 06.04.18 to reflect current URLs]
IBM TRIRIGA hosts a public beta for review and evaluation of our upcoming releases. You can access the site here. There is a very simple registration application that you must fill out, in order to gain access. That registration application can be found here (username: beta, password: signup).
We also have a public Slack channel to which you can request access, where you can engage development of new and upcoming features, as well as gain early previews of release notes and support matrices.
The IBM TRIRIGA beta is going to be refreshed to start our 3.5.3/10.5.3 beta on December 29th, and will be available again by January 3rd. During the refresh, the beta server will be unavailable. All previous user accounts will be removed, and registration will be required again to create new accounts and access the beta.
You can also request a demo of our IBM TRIRIGA SaaS or “Cloud” version. You can access the site here.
[Admin: A similar message is also posted in the TRIRIGA Around the World Facebook group. This post is related to the 11.13.15 post about IBM TRIRIGA SaaS in the Cloud Shop.]