Unfortunately, installing OBIEE on 64 bit Redhat Linux 5.5 is neither simple or straightforward. It is a complex multistep process. Here are the high level steps on how to install it.
Script to find all generations Of an object’s children. Children. Grandchildren. Great-Grandchildren. Great-Great-Grandchildren. Etc.
Very Useful Scripts To Find Oracle Object Dependencies; Parents, and Children.
Fabulous to determine:
– The order of operations to create objects. Parents first. Then children.
– The impact of dropping a view, package, procedure.
– Causes of object invalidation such as another invalid object.
– ALL the tables that a package is accessing.
– Whether a package, function or procedure calls another prodecure.
– Obscure issues, such as references to variables in packages.
Another bizarre database design is to split up a table vertically. In other words, to have duplicate tables!
MUCK: Massively Unified Code-Key, Generic Three Table Data Models cause lots of problems: Awful performance, Pivots, Require multiple inline views, data type Issues, really complex inserts, increased people time, cost, and create a Cobol system. Just say no!
There was a functional dependency, violating 2NF. The first field, determined the second field. This of course should have been moved into another table, but it wasn’t.
Creating a LOB for every customer record, whether it was used or not, caused some serious problems.
A 1:1 relationship was split into two tables. Now a table join was required for almost every query. Querying on a single table would take 10 to 15 seconds. After joining to the second table to get a few more fields, the response time slowed down to about 45 to 60 seconds! About 4 times as long.
Here is an Oracle script to find the tables that don’t have any foreign keys.
Tables that are neither a parent table, or a child table.
Another Database Design Mistake to Avoid is the Redundant Foreign Key.