this post discusses in brief, what the etl implementation for a data vault might look like.
short excerpt on existing issues i’m finding, and incosistencies in the omb/owb product.
omb/owb data vault link code generated from a couple simple inputs.
a brief description comparing design time effort in owb (oracle warehouse builder) and informatica powercenter.
how would you like to take: a) a source model, b) target model, c) cross-reference (source-to-target) spread-sheet, push it in to a service, and automatically generate target etl loading code? i’ve got a service i’m working on that does just that. i hope it’s available soon. for now, here’s some preliminary information & an example […]
in case you’re following me for this, you’ve noticed that what i must be doing is generating etl code… well, you’re absolutely correct. i’m using patterns in the data vault, patterns in source system models, and patterns in code generation to generate etl code for owb. in this case, it’s omb script (tcl script) that […]
i recently setup owb for 11g r2 right after installing oracle 11g. it’s fairly smooth to do, but there are some quirks along the way, enough to drive you batty. so i thought i’d share a few hints and techniques here… (more…)
this is a look into tidbits of implementation for structures in omb/owb code.