Run the Catalog Build Utility
To run the catalog build utility
1. Log in as the Gateway System Administrator. For UNIX and Windows, this is the 'ingres' user ID.
2. Ensure the environment is set correctly for the gateway and for the host DBMS (that is, ensure that you can access the host DBMS as the Gateway Installation Owner and that the host DBMS user has the appropriate access permissions in the target DBMS).
3. If this is an existing installation, ensure that no users are currently using the gateway.
4. A gateway alias must be defined to access the target DBMS. If the gateway alias entry does not contain the password for the Gateway Catalog Owner username/password, provide the information in the command line, or you will be prompted for this information. For additional information about defining a gateway alias, see
Gateway Catalog Setup.
5. Run the gateway catalog build utility for the appropriate database. Utility names appear in the previously mentioned table.
6. A prompt appears for the name of the gateway alias. Enter the gateway alias entry previously defined to access the target DBMS.
7. A prompt appears for the DBA name used to qualify unqualified objects. Enter the name of the schema that contains shared objects (tables, views, etc.). When a user accesses an object that is not owned by the user, the gateway prefixes the DBA name to the object's name so that the user may access the object. This value can be changed in CBF/VCBF with the "load_table_qualifier" parameter (see
Configuration Parameter Descriptions).
Note: This entry is not the owner of the system catalogs. See the load_table_qualifier parameter in the Configuration Parameter Descriptions section and the Microsoft SQL Server Considerations section for additional information.
Note: A prompt appears for the Ingres user's host DBMS password. Enter the password of the Gateway Catalog Owner, which is currently the host DBMS password for the Ingres user.
8. Oracle only: The Oracle catalog build utility, iigwcatora, prompts for the number mapping mechanism to use. If you are unsure, choose the default. The default Oracle Number mapping mechanism is OpenSQL (Option 1). See
Developing Portable Applications for more information about the Oracle number mapping mechanism.
9. A prompt appears for the money mapping mechanism to use. Before choosing a mapping other than the default of Float (Option 1), be sure you understand the implications. It is best to use the default value, unless full support of the money data type is required. Selecting a mapping other than the default will result in some existing data appearing as money when that may not be the intent. See additional details in the Gateway Catalog Parameters table.
Important! Because of continuing enhancements to the gateway, existing gateway catalogs must be re-created using the Gateway Catalog Utility provided with the release. The use of upgraded catalogs with earlier releases of Enterprise Access is not supported.