Mariadb - Vibe 4.0.8.3 on SLES15SP5 - new installation

I had problems with Vibe 4.0.8.3 on a sles12sp5 server after an Sles update (java error)
I decided to reinstall Vibe based on a SLES15SP5 server and also installed tk-32bit, tcl-32bit and libstdc++6-32bit.
I preselected MariaDB as the database because it is recommended according to the documentation.

The installation of Vibe 4.0.8.3 went fine and I have to run the scripts to create the database.
Here I only find scripts for MSSQL, Oracle, Mysql and Postgres, but not for MariaDB.
Who can help me?
Thanks for your support

Parents
  • 0

    i use the original installation documentation for vibe4.0.8 and there are many false command when using sles15sp5!

    we can only hope, that the documentation for cominb version vibe 4.0.9 will be refreshed !!!

    the installation is not easy, libs must be loaded manually, database must be choiced manually, conf files and other must be edited, database must be created, propertie-files edited, and then tables created

    Are we in 2024 with artificel intelligence or what is false?

Reply
  • 0

    i use the original installation documentation for vibe4.0.8 and there are many false command when using sles15sp5!

    we can only hope, that the documentation for cominb version vibe 4.0.9 will be refreshed !!!

    the installation is not easy, libs must be loaded manually, database must be choiced manually, conf files and other must be edited, database must be created, propertie-files edited, and then tables created

    Are we in 2024 with artificel intelligence or what is false?

Children
  • 0   in reply to 

    Claude, you are working with a product which has not been refreshed for years. Unfortunately! One of its children has a new makeup and a lot more support. Filr. In the background they are very similar.

    That's the reason why Vibe specialist know the Filr frame in a very good way. 

    Sometimes I feel that Vibe is Cindarella - and we wait for the good fairy ...


    Use "Verified Answers" if your problem/issue has been solved!