Latest Denodo community answered questions 2025-01-15T16:28:00Z 2025-01-15T16:28:00Z

For the last denodo patch (denodo-v80-update-20240926.1) in the downloads section Denodo Platform / Denodo Solution Manager â?? Virtual DataPort, Scheduler, Data Catalog and Solution Manager 8.0 20240926.1 Given that the title above says also **Denodo Solution Manager**, in this case, are we going to use same jar file for solution manager, Virtual DataPort, Scheduler, Data Catalog and Denodo platform? In older versions there are two diferent files one for solution manager and other file for Denodo Platform, Virtual DataPort, Scheduler and Data Catalog. applying it as below commands? ./jre/bin/java -jar /opt/denodo-v80-update-20240927/denodo-v80-update-202409272200.jar /opt/denodo -câ?¯ Thanks in advance for your answer Denodo community

2025-01-15T16:28:00Z 2025-01-13T22:31:14Z 2025-01-13T22:31:14Z

I would like to make some archived Salesforce data available for reporting purposes. When I look at the endpoints types available in OWN, it only lists Azure Blob, MySQL, S3 Bucket, and Snowflake. Has anyone successfully connected to OWN? Any help is appreciated. Thanks!

2025-01-13T22:31:14Z 2025-01-08T07:42:19Z 2025-01-08T07:42:19Z

Dear Denodo Support Team, I need assistance in obtaining a list of remote tables in our Denodo environment. I have tried various stored procedures and VQL queries without success. Could you please provide the correct method to list all remote tables? Thank you for your help. Best regards, Ievgenii (Denodo 8, 20240306.1)

2025-01-08T07:42:19Z 2025-01-03T09:08:06Z 2025-01-03T09:08:06Z

I enabled the cache and pointed the DataSource to PostgreSQL. However, now when I try to switch to another database or disable the cache, an error message occurs. The message is as follows: > 61079486 [DNI(7920)-XXX.XXX.XX.XX-739] ERROR 2025-01-03T09:04:22.869 com.denodo.vdb.interpreter.execution.VCSDiscardAction [] - Error discarding local changes for /databases/admin/datasources/jdbc/vdpcachedatasource out: An error has occurred while discarding local changes on '/databases/admin/datasources/jdbc/vdpcachedatasource' : com.denodo.vdb.catalog.datasource.LoadDataSourceException: Error loading jdbc data source 'b42e08f6-3dc6-4427-a81f-759fd709d04d'. > com.denodo.vcs.exception.VCSException: com.denodo.vdb.catalog.datasource.LoadDataSourceException: Error loading jdbc data source 'b42e08f6-3dc6-4427-a81f-759fd709d04d'. > at com.denodo.vdb.interpreter.execution.VCSDiscardAction.doDiscardDataSourceRenaming(VCSDiscardAction.java:1116) ~[denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.interpreter.execution.VCSDiscardAction.discardDataSourcesRenaming(VCSDiscardAction.java:979) ~[denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.interpreter.execution.VCSDiscardAction.doDiscardRenamings(VCSDiscardAction.java:904) ~[denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.interpreter.execution.VCSDiscardAction.doDiscardElement(VCSDiscardAction.java:1906) ~[denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.interpreter.execution.VCSDiscardAction.doDiscard(VCSDiscardAction.java:1642) [denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.interpreter.execution.VCSDiscardAction.doExec(VCSDiscardAction.java:311) [denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.interpreter.execution.VCSAction.exec(VCSAction.java:76) [denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.interpreter.execution.Action.run(Action.java:505) [denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.interpreter.execution.processor.VDBActionProcessor.runAction(VDBActionProcessor.java:1741) [denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.interpreter.execution.processor.VDBActionProcessor.process(VDBActionProcessor.java:1360) [denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.interpreter.execution.processor.VDBActionProcessor.preProcess(VDBActionProcessor.java:805) [denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.interpreter.execution.Action.start(Action.java:622) [denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.interpreter.execution.ExecutionEngine.execute(ExecutionEngine.java:346) [denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.interpreter.execution.ExecutionEngine.execute(ExecutionEngine.java:236) [denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.interpreter.execution.ExecutionEngine.execute(ExecutionEngine.java:226) [denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.vdbinterface.server.QueryExecutorImpl.doExecuteStatement(QueryExecutorImpl.java:422) [denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.vdbinterface.server.QueryExecutorImpl.executeStatement(QueryExecutorImpl.java:403) [denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.vdbinterface.server.QueryExecutorImpl.executeStatement(QueryExecutorImpl.java:432) [denodo-vdp-server.jar:9.1.0] > at jdk.internal.reflect.GeneratedMethodAccessor242.invoke(Unknown Source) ~[?:?] > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] > at java.base/java.lang.reflect.Method.invoke(Method.java:568) ~[?:?] > at com.denodo.internal.o.a.r.server.ObjectRef.invoke(ObjectRef.java:110) [denodo-asyncrmi.jar:9.1.0] > at com.denodo.internal.o.a.r.netty.RMIServerHandler.dispatch(RMIServerHandler.java:198) [denodo-asyncrmi.jar:9.1.0] > at com.denodo.internal.o.a.r.netty.RMIServerHandler.channelRead(RMIServerHandler.java:82) [denodo-asyncrmi.jar:9.1.0] > at com.denodo.internal.i.n.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444) [denodo-asyncrmi.jar:9.1.0] > at com.denodo.internal.i.n.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:61) [denodo-asyncrmi.jar:9.1.0] > at com.denodo.internal.i.n.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:425) [denodo-asyncrmi.jar:9.1.0] > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?] > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?] > at com.denodo.internal.i.n.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [denodo-asyncrmi.jar:9.1.0] > at java.base/java.lang.Thread.run(Thread.java:840) [?:?] > Caused by: com.denodo.vdb.catalog.datasource.LoadDataSourceException: Error loading jdbc data source 'b42e08f6-3dc6-4427-a81f-759fd709d04d'. > at com.denodo.vdb.catalog.Catalog.findDataSourceById(Catalog.java:1839) ~[denodo-vdp-server.jar:9.1.0] > at com.denodo.vdb.interpreter.execution.VCSDiscardAction.doDiscardDataSourceRenaming(VCSDiscardAction.java:1100) ~[denodo-vdp-server.jar:9.1.0] > ... 30 more

2025-01-03T09:08:06Z 2025-01-03T05:13:24Z 2025-01-03T05:13:24Z

Referring to the blogs https://www.denodo.com/en/partner/data-sentinel & https://www.denododatafest.com/session/actionable-data-classification-data-sentinel-and-denodo-platform, the first step is, Data sentinel connecting to data sources and classifying them as sensitive/PII elements and then this information is fed to Denodo. Later an mapping exercise is perfromed and with the tags the data is protected using masking techniques. Instead of Data sentinel connecting to individual data sources, can it be connected to Denodo to read the data and classify them ? If its achievable, then the mapping of the sensitive information coming from Data sentinel against the Denodo views will also be seamless. Please advise. Thanks, Sandeep.N

2025-01-03T05:13:24Z 2025-01-02T05:57:14Z 2025-01-02T05:57:14Z

Date(Last_day(Date_trunc('month', date.column.name)-1)) Can you help me change above code as per denodo standards, I tried but faced problems

2025-01-02T05:57:14Z 2024-12-24T09:23:11Z 2024-12-24T09:23:11Z

How Can I know the number of hits of specified API and accounts that hits this API

2024-12-24T09:23:11Z 2024-12-24T08:06:45Z 2024-12-24T08:06:45Z

Hi Team, I need to connect an SFTP server to Denodo, which contains an Excel file. I have the host, username, and password details. I was able to connect to the server using FileZilla with just the username and password. The file URL is: sftp://sftptest.efwnow.com:22/ClaimsReport.xlsx However, when I try to establish the connection in Denodo, I encounter the following error: "Unable to establish connection: java.net.ConnectException: Connection timed out: connect" Could you please assist?

2024-12-24T08:06:45Z 2024-12-23T20:03:20Z 2024-12-23T20:03:20Z

Hi, I got the following error messages when calling custom function from oracle databse in PowerBI Desktop by using direct query option. I'm using DenodoODBC drive Unicode(x64). Please advise. Query: select i.AWD_ITEM_NUMBER_FORMATTED, i.AWD_ITEM_OBLIGATED_AMOUNT, i.AWD_ITEM_OPTION_LINE, i.AWD_ITEM_DOCKEY as AWD_ITEM_DOCKEY, i.AWD_ITEM_VERKEY as AWD_ITEM_VERKEY, XXA99_DM_GETOPTIONDISPLAYVALUE(i.AWD_ITEM_DOCKEY,i.AWD_ITEM_DOCKEY,i.AWD_ITEM_OPTION_LINE) "Option" from awd_item i where 1 = 1 Error: DataSource.Error: ODBC: ERROR [HY000] ERROR: Function 'xxa99_dm_getoptiondisplayvalue' with arity 3 not found java.sql.SQLException: Function 'xxa99_dm_getoptiondisplayvalue' with arity 3 not found; Error while executing the query Details: DataSourceKind=Odbc DataSourcePath=dsn=Denodo_p2pfsnd OdbcErrors=[Table]

2024-12-23T20:03:20Z 2024-12-19T06:45:22Z 2024-12-19T06:45:22Z

Hello everyone, I would like to reproduce the behavior of an old API according to the following case: Before displaying the final result, I'd like a previous SQL query to confirm access to the data. Currently, an HTTP 500 error is returned by the API explaining why this data should not be displayed to the end user. I'm having trouble finding documentation on how to raise an exception in VQL. Which leads me to ask: wouldn't such an exception raising in Denodo be bad practice? And should I propose another approach to providing this data? Thanks in advance for your feedback

2024-12-19T06:45:22Z