You can translate the question and the replies:

Our Denodo server are down after configuring external database

we have configured external metadata on one of our server, after restart the server is not starting up, and facing below error, error : 53303 [DNI(2)-XXX.XXX.XX.XX-4] ERROR 2023-05-18T14:36:18.371 com.denodo.vdb.interpreter.execution.ListResourcesAction [] - Error executing list resources com.denodo.vdb.catalog.resource.exception.ResourceException: Error loading resource versions by type 'essbase,jar,jdbc,jdbc_other,generic,kerberos,library,sapjco,vault' at com.denodo.vdb.catalog.resource.MetaResource.a3(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] at com.denodo.vdb.catalog.resource.MetaResource.findMetaResourcesByTypes(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] at com.denodo.vdb.catalog.Catalog.findMetaResourcesByTypes(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] at com.denodo.vdb.interpreter.execution.ListResourcesAction.findAllResources(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] at com.denodo.vdb.interpreter.execution.ListResourcesAction.exec(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] at com.denodo.vdb.interpreter.execution.Action.run(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] at com.denodo.vdb.interpreter.execution.processor.VDBActionProcessor.f3(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] at com.denodo.vdb.interpreter.execution.processor.VDBActionProcessor.a3(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] at com.denodo.vdb.interpreter.execution.processor.VDBActionProcessor.d3(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] at com.denodo.vdb.interpreter.execution.processor.VDBActionProcessor.a3(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] at com.denodo.vdb.interpreter.execution.Action.start(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] at com.denodo.vdb.interpreter.execution.ExecutionEngine.execute(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] at com.denodo.vdb.interpreter.execution.ExecutionEngine.execute(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] at com.denodo.vdb.interpreter.execution.ExecutionEngine.execute(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] can some one help
user
18-05-2023 14:06:49 -0400
code

3 Answers

Greetings, The captured errors suggest that the server has failed in loading the required resources particularly the types specified (e.g., jdbc,generic,Kerberos …etc.). Possible causes could be related to lack of necessary permissions to access the external database(e.g., user account in the database does not hold enough privileges), connectivity, and compatibility issue (e.g., type and version of the database) or incorrect configuration of the external database. Therefore, you could perform the following checks: * Verify and implement necessary permissions needed to access the external database (necessary permissions are listed [here](https://community.denodo.com/docs/html/browse/8.0/en/vdp/administration/server_configuration/storing_catalog_on_external_database/storing_catalog_on_external_database#how-to-configure-virtual-dataport-to-store-the-metadata-on-an-external-database)). * Check and test connectivity between the server and the external database. * Review the configuration of the external database. Refer to the following [instructions](https://community.denodo.com/docs/html/browse/8.0/en/vdp/administration/server_configuration/storing_catalog_on_external_database/storing_catalog_on_external_database#how-to-configure-virtual-dataport-to-store-the-metadata-on-an-external-database). If you are setting-up an external database for the solution manager, then please refer to the following [documentation](https://community.denodo.com/docs/html/browse/latest/en/solution_manager/administration/configuration/database_configuration/database_configuration). If the issue persists, contact Denodo support for further assistance and troubleshooting. Hope this helps !
Denodo Team
21-05-2023 23:04:57 -0400
code
we have done all according to the document, still facing the same issue. and it hass necessary permissions and its not on SM, its VDP external DB configuration. logs : Error executing list resources com.denodo.vdb.catalog.resource.exception.ResourceException: Error loading resource versions by type 'essbase,jar,jdbc,jdbc_other,generic,kerberos,library,sapjco,vault' Caused by: com.denodo.vdb.catalog.storage.StorageInternalException: Unexpected error accessing metadata while loading/storing objects: 'Invalid column name 'resourcetype'.' at com.denodo.vdb.catalog.storage.JDBCStorageManager.loadAllRemovedMetaResourceSinceEpoch(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] ... 9 more Caused by: com.denodo.vdb.exception.ExternalException: Received exception with message 'Invalid column name 'resourcetype'.' at com.denodo.vdb.catalog.storage.JDBCStorageManager.loadAllRemovedMetaResourceSinceEpoch(Unknown Source) ~[denodo-vdp-server.jar:8.0.6] ... 9 more
user
23-05-2023 05:20:53 -0400
Hello, Could you check the following error messages "Received exception with message 'Invalid column name 'resourcetype'." And Unexpected error accessing metadata while loading/storing objects: 'Invalid column name 'resourcetype'. This is an indication that you are trying to query a column that does not exist in a table, or it is not being recognized. (e.g. misspelled column name , non-existent table). Other possible reasons would be that this is caused by Denodo platform inability to process the metadata table created in the target database(e.g., table is corrupted) Or a network error that prevents the platform from communicating with the database in question. To get better look on the errors produced, I would modify the Virtual DataPort log level as “Debug’’ or “Trace” in <DENODO_HOME>/conf/vdp/log4j2 , execute the metadata export or reconfigure the external database and check for the possible causes in the vdp.log file in <DENODO_HOME>/logs/vdp. Alternatively, you could invoke the [LogController](https://community.denodo.com/docs/html/browse/latest/en/vdp/vql/stored_procedures/predefined_stored_procedures/logcontroller#logcontroller) stored procedure with appropriate log category such as “com.denodo.vdb.catalog.storage” or “com.denodo.vdb.catalog.resource”. If changing the logging level to Debug doesn't bring up anything obvious, I would advise you to raise a support case, so further investigation can be done to resolve the issue. Remember to change the log level back to "Error" when you've solved the issue to prevent performance problems from excessive logging. Hope this helps !
Denodo Team
29-05-2023 06:59:32 -0400
code
You must sign in to add an answer. If you do not have an account, you can register here