Learn & Share

How to delete orphan but active records on source and instance table in Omnihealthdata. The records were deleted at source but the load to onramp was missed for delete batch. Is there other way I could delete these records from _s(source) and instance tables? Is a manual SQL delete a right way to go with or would it cause any future issues?

I’m using RDM 14.2 (soon to be upgraded to 14.5) and I need to build an API endpoint to accept incoming data.I have an integration input and will use an RDM Importer step to import the data into my table.My table has a generated id as a primary key and I need to provide the generated id as a response back to the incoming API call.But the RDM Importer step stops there. It doesn’t tell me the id. How do I then get the id back? I could make an RDM Extended Reader step in the plan, but I cannot guarantee the Reader step is executed after the Importer step, because the Importer step doesn’t have an out endpoint, it only has an err endpoint. And if I query the data before the insert is committed then I will end up with nothing to provide. Any ideas? (I believe the new RDM REST API functionality is read only so that won’t be relevant here?)

We are on version 14.2 and trying to create a connection to Microsoft OneDrive, so we can export some data from RDM to it. We are planning to write the data using onPublish plan.We see that Ataccama ONE supports Onedrive in the ONE webapp (https://support.ataccama.com/home/docs/aip/14.2.0/user-guides/one-web-application-user-guide/knowledge-catalog/data-catalog/working-with-data-sources/microsoft-onedrive-storage-connection)But I cannot find a corresponding connection type in ONE Desktop. In here One drive is not an option: How can we set this up please?

 Hello everyone!In the new version of Ataccama 14.5, how is the configuration done for regular scanning of data schemas to detect the appearance of new tables: metadata import? I need to regularly automatically import tables based on a specific schema that are not in the Catalog Item.I will be very grateful for your help🤗Thank you!

I got 2 questionsFirst: how can I replicate my DQ rules from one environment to another ? (example: from dev to QA)Second: how can I make the rules automatically replicate to new records on a table ? Like if I have a table with 500 rows and I add 50 more rows, I need to re apply the rules to all the table, instead I wanna make it in an incremental way so only my new records would need to have the rules applied.

how to be ataccama data integration(migration) to azure cloud?

My requirement is to get all the RDM tables in Ataccama to Snowflake or to amazon S3.Could anyone please let me know how to do that.

Hi Team, Can anyone please help me with below Information on MDM licensing?Is Ataccama MDM licensing model based on number of records that we load form various sources (unconsolidated) or based based on unique profiles in MDM (Consolidated) Apart from number of records, are there other aspects that affects licensing price like the domain that I want to master (Customer/Product/Location etc.), the number of API calls, the number of batch jobs that execute per day, total volume required to host source records + history + merge history etc. ? Any other factor that is required to calculate MDM licensing cost? 

We had a internal discussion, but ended up not being 100% sure. So here's the question.When we run DQE on a CI, where are the rules evaluated? Does the DPE get the full data (possibly with filters on the MP?) and the run the rules evaluation IN the DPE. Or does the DPE create a SQL-like statement and does the source DB return the results?As we also run on Hadoop with DPE on Hadoop. Is this the same.

Hi community,I am looking for a bit more clarity about Term Suggestions Synchronization. In the Documentation Portal I read that the synchronization is only relevant after a database restore or ‘by importing any initial content (default, demo, etc.)’.For me it is not clear what is meant with this initial content. Importing a catalog item for the first time, or? Does anyone know?Kind regards,Albert

The performance of one of the subject is bad. This what is happening.A new or existing records loaded and it runs matching against 1000 records (one master and 999 slaves) because they are similar and have same master_id 123. So if we think of overall if 500 records are loaded during an incremental load and each have similar conditions, its ending up touching 500000 records and taking several hours. IS there a way to make the record only try to match against the Master record? or other ways to improve the performance? Please suggest. Thank you.

Hi Team ,Can anyone please help me setup my MDM environment locally .Please help me with the plugins and folder structure .Regards,Kundan 

One of the most common data sources that our users connect to are relational databases, e.g. Oracle, MSSQL, PostgreSQL, etc. For those sources, we usually recommend using JDBC drivers to connect, and use JDBC Reader and JDBC Writer steps to work with the data.But for big data sources, e.g. Databricks, within the Ataccama ONE Desktop environment there are a few different steps available. Ever wondered which one you should choose? Hive Reader and Writer:Hive Reader and Writers are the simplest to configure, but also offer the least options. You will need to specify the exact database, table and column names you want to read from / write to. For the Reader step you can provide some simple where clause in the Filter. Spark SQL Reader:For more complex SQL queries, you can use the Spark SQL Reader. This is not limited to where clauses, but also joins, aggregates etc. Spark Reader and Writer:For even more complex operations, you can use the Spark Reader and Writer steps. They are more complex

Ataccama detail document on what all can be done related to snowflake like can we pull tags from snowflake connect to snowflake console from Ataccama?is there any blog or document available on the same. Any limitation related to that

What is the difference between ataccama one desktop and ataccama ONE? 

Hi we are trying to connect to a AS400 source using JT400 jdbc driver for a customer and keep getting "Unable to initialize pool" is there any specific configuration we are missing in DPE? If anyone has done a similar connection in the past then please do share some inputs. Will be highly appreciated.

I have a use case to use the JDBC writer step to write some data into a MS SQL db.I will need to use the Before and After script feature. (Truncate the table in the before script, then I need to call a stored proc in the after script).And in the after script, I need to construct that based on some value that I calculate in the plan. So it is different every time I run the plan, but I need to keep it consistent.Does this after script support some parameterisation? I have a feeling it won’t but wanted to double check.

Hi Team,I need to upgrade my ataccama 13.8 to new latest one…. request you to please provide upgrade version download path or URL's. As I am facing some issue on current repository-  ";Cannot instantiate class: com.ataccama.dqc.jms.sqs.SQSInitialContextFactory”

I am working on template project for MDM and i am not able to run the pgsql script in it and i did followed the steps mentioned in this  MDM Example Project - Ataccama ONE Gen2 Platform Latest Kindly let me know if you have any solution for this.   

When working with Reference Data table there may be a business requirement to control what kind of values can be input into a given attribute which are checked whenever a user creates or edits records within the RDM application. There are two kinds of validations:  The first kind are called Instantaneous validations. These conditions, e.g., regular expressions or string size are checked automatically when you enter an attribute value. When the input value fails to meet these condition, an INVALID message appears next to the attribute field. The second kind are called Online validations. These are more complex conditions, which are triggered by clicking Validate in the Create detail/Edit detail dialogue or upon closing them. Such validations are performed by DQC plans (using, e.g., phone number or address lookups) or SQL queries in RDM. When the input value fails to meet these condition, a Warning message appears next to the attribute field.Records which do not satisfy online conditions