Oracle OWB introduces series 1 introduction and use process

Oracle OWB introduces series 1 introduction and use process

OWB, Oracle Warehouse Builder, is a tool for oracle to implement data warehouses. To put it bluntly, it is to clean and convert data from many other databases and load it into a data Warehouse, so what owb does is this function.

Since the data is loaded from the source database to the data warehouse, you must connect to the source database and the target database. Therefore, owb provides the concept of "LOCATION, it is actually the database connection information, including the database server address, user name and password.

After the location is set up, the next step is to create a database module. owb claims to support most databases and also includes flat files. Therefore, common databases are listed below the database on the menu. We select the corresponding database, click Create, such as the new oracle module. This database module has two concepts: source data. For this, we only need to import the objects we need in the source database, such as tables or views. The other is the target database module. The database module includes table, ing, latitude, cube, and other information. Create a table under the target database module and deploy the table to the target database (that is, the table structure is automatically created in the target database ), create a ing file corresponding to the table. The ing file describes how the table is loaded from the source database to the table. At this point, we have learned how to migrate data from the source database to the target database. We need to put forward two points. First, the source database can be a variety of different databases, and the target database must be an oracle database, in addition, the oracle database must have owb-related functions, and the target database user must have owb-related roles.

We already know how to migrate data from the source database to the target database after completing the preceding steps. However, as a complete system, these steps are not enough. Sometimes there is a sequence between loading two tables, for example, you must first load table A and then load table B data according to Table A. Therefore, the owb client provides the owf function, namely, oracle workflow and process flow, this function is similar to the flow chart we often draw. We draw this chart based on the interface provided by owb, then the ing file will be executed in the desired order. Another point is that sometimes these ing files need to be executed on a regular basis, and we cannot assign a few people to manually execute them on a daily basis. Therefore, owb also provides the scheduled execution function, the configuration is flexible and convenient.

To sum up, owb's process is to create a table first, then create a ing for the table, create a corresponding process flow after creating n tables and their corresponding ing, and then create a plan, finally, deploy the ing and execute the ing according to the plan and the process flow. After that, the owb client can be separately installed on a machine. When starting, you only need to connect the client to the server with the owb server. In this way, multiple clients can be connected to one server for work. The core of owb is the ing function, which enables data to be loaded from the source database to the target database according to its own ideas.