Siebel Analytics Server Administration Guide > Creating and Administering the Physical Layer in a Repository > Process of Creating the Physical Layer From Relational Data Sources >

Importing a Physical Schema From Relational Data Sources

This topic is part of the Process of Creating the Physical Layer From Relational Data Sources.

You can import physical schema for supported data source types. This task is part of Process of Creating the Physical Layer From Relational Data Sources.

When you can use importing to create the physical schema, you need to select one of the following two import options and the appropriate connection type:

• Import. Available in Offline and Online modes. Use this option when you have all database connections set up on your machine. You can use the following connection types with the Import option:
  • Most physical schema imports are performed using an ODBC connection type.
  • Native database gateways for schema import are supported for only DB2 (using DB2 CLI or DB2 CLI Unicode) and XML connection types. For more information about importing XML data using the Siebel Analytics Server XML gateway, see Siebel Analytics Server XML Gateway Example.
• Import through Server. Available in Online mode. Use this option when you want to use the Analytics Server connections to import schema. This feature allows an administrator to use the DSN's of the Siebel Analytics Server machine to import physical schema information. Connectivity software and duplicate DSN's do not have to reside on the administrator's machine and the Siebel Analytics Server machine. You can use the following connection types with the Import option:
  • Available connection types are ODBC, DB2 CLI, DB2 CLI (Unicode), and XML.
  • When it is running on a Unix platform, the Analytics Server does not support importing schema using an ODBC connection type.

NOTE:  The Import from Repository menu option allows you import metadata objects from another repository. You can use this to import objects from all three metadata layers. For more information, see Importing from Another Repository.

You can use a table mask to limit (filter) the list of tables that appear in the Import dialog box. When you have one or more specific tables that you want to import, using a table mask helps locate the tables.

To import a physical schema from an ODBC connection type

1. In the Administration Tool, select File > Import or Import through Server.
2. In the Select Data Source dialog box, perform the following steps:
   1. From the Connection Type drop-down list, select the correct type.

      NOTE:  It is recommended that you use ODBC 3.5 or DB2 CLI Unicode for importing schema with International characters such as Japanese table and column names.

   2. In the DSN list, select a data source from which to import the schema.

      When you import through the Analytics Server, the DSN entries are on the Analytics Server, not on the local machine.

   3. Click OK.
3. If a logon screen appears, type a valid user ID and password for the data source, and then click OK.

   The administrator must supply the user name and password for the data source. If you are performing an import on the administrator's machine, the user name will be obtained from the machine's DSN configuration.

4. In the Import dialog box, select the check boxes for the types of objects that you want to import. For example, Tables, Keys, and Foreign Keys.

   Some objects check boxes are automatically selected. These default selections depend on your data source.

5. To use a table mask, type a table mask such as F%, and then click the highest level database folder.

   Tables that meet the filter criteria appear.

6. Select the tables and columns you want to import.
7. After you select all the objects you want to import, click Import or drag and drop the objects into the Physical layer.