cancel
Showing results for 
Search instead for 
Did you mean: 

Oracle issue on BO4.2 installation

leguen
Explorer
0 Kudos
163

Hello,

We have the following issue on BO BI4.2SP8 cluster installation when we are trying to join the existing CMS repository :

Error<br>An error has occurred.<br><br>Database access error. Reason ORA-00928: mot-cl? SELECT absent. (FWB 00090)<br><br>The system cannot verify the database logon information.<br>
Would you like to correct it
  • We already have a node on a first server which is running perfectly.
  • This first node runs on RedHat RHEL 7.6 x86_64. Database is Oracle 19. The oracle password is not complex.
  • The second servers runs on the same version of RedHat. Oracle client is installed. We can connect to the database via sqlplus.
  • If we try to register this installation step with another schema of the same database the installer doesn't return any error. (we didn't proceed because we are wanting to extend the existing CMS repository).
  • The schema was already used by an old BO version. It contains the following tables :
TABLE_NAME<br>CMS_ALIASES6<br>CMS_ALIASES7<br>CMS_CCFRONTIER6<br>CMS_CCFRONTIER7<br>CMS_FRONTIER6<br>CMS_FRONTIER7<br>CMS_IDNUMBERS6<br>CMS_IDNUMBERS7<br>CMS_INFOOBJECTS6<br>CMS_INFOOBJECTS7<br>CMS_LOCKS6<br>CMS_LOCKS7<br>CMS_RELATIONS6<br>CMS_RELATIONS7<br>CMS_ROOTFRONTIER6<br>CMS_ROOTFRONTIER7<br>CMS_SESSIONS7

Thanks a lot if you have any idea to help us.

Accepted Solutions (0)

Answers (1)

Answers (1)

leguen
Explorer
0 Kudos

Hello

We have resolved our issue !!!

We don't know why but our oracle schema didn't contain the table CMS_VERSIONINFO.

So oracle was using an other table stocked on an other very old schema...

We just manually create CMS_VERSIONINFO and fill it with 2 values (7 and 14.0.0) and now installation process run well...