1.2K Messages
DB2 z/os Catalog Ingestion
I would be interested if anyone has been successful ingesting using the DB2 for z/os into Collibra for just one database. We haven’t been able to figure out how to ingest by database. We’ve tried using specialRegisters, but haven’t yet been successful. The database property ($database) in the connection string points to the sub-system, not a particular database. Our databases are using the same schema name, so we can’t just sync by schema without getting metadata from multiple databases.
This is the connection string: jdbc:db2://$host:$port/$database
arthurburkhardt
1.2K Messages
4 years ago
Can’t you use the “Tables excluded from registration” option?
https://productresources.collibra.com/docs/cloud-user/2020.11/#Catalog/RegisterDataSource/ta_register-data-source-own-driver.htm?Highlight=exclude
If you have 5000 tables in the same schema, you probably have some logic/prefix to identify tables per “database”.
Identify the minimum set of prefixes, and add them here, like so:
“TA*”, “TC*”, etc.
0
0
Former User
1.2K Messages
4 years ago
Unfortunately that wouldn’t help much, as each database/application uses the same naming convention. We have multiple databases/applications that use the same schema. First, we want one application per Collibra domain. Second, we wouldn’t be able to put together an exclusion list that would identify just one application.
2
0
laurenzhiller
36 Messages
4 years ago
Hi @cxlarsen.larsen,
did you find a solution for ingesting metadata by database in the meanwhile? We are facing exactly the same problem for z/OS in the moment.
1
0