I am confused by your question:
Are you having other problems that do not relate to DWH? if not, I’m not sure why you’re doubting your choice in regards to the FQDN hostname you provided.
As for your DWH issue, after correcting the values in /opt/kaltura/dwh/.kettle/kettle.properties, specifically:
78 # the DWH DB settinge
79 DbHostName = localhost
80 DbPort = 3306
81 DbUser = etl
82 DbPassword =
84 # the Read DWH connection
85 DbReadHostName = localhost
86 DbReadPort = 3306
87 DbReadUser = etl
88 DbReadPassword =
90 # the operational Db settings
91 OpDbHostName = localhost
92 OpDbPort = 3306
93 OpDbUser = etl
94 OpDbPassword =
96 # operational DB with write priviledge (for exporting plays/views)
97 OpWritableDbHostName = localhost
98 OpWritableDbPort = 3306
99 OpWritableDbUser = etl
100 OpWritableDbPassword =
and in /opt/kaltura/app/configurations/db.ini:
dwh.adapter = mysql
dwh.connection.classname = KalturaPDO
dwh.connection.phptype = mysql
dwh.connection.database = kalturadw
dwh.connection.hostspec = localhost
dwh.connection.port = 3306
dwh.connection.user = kaltura
dwh.connection.dsn = "mysql:host=localhost;port=3306;dbname=kalturadw;"
And reloading Apache, are you able to connect to the kalturadw DB using these credentials?
Note that you should not touch other MySQL DSN directives in this file, since, if I understood you correctly, the connection to the operational MySQL DB was fine and the only problem was with the DWH [Analytics].
If that is not so, please reiterate.