Create an Oracle database for the UDDI Registry
Perform this task if you want to use Oracle as the database store for your UDDI Registry data. You need only do this once for each UDDI registry, as part of Setting up and deploying a UDDI Registry.
Overview
Note: Only V9i1 and Oracle 10g2
Before you begin
Note that this task will create two new schemas, ibmudi30 and ibmuds30. You will be unable to complete this task if you already have existing schemas of those names.
The steps below use a number of variables for which we need to enter appropriate values. You should decide the values that you will use before you start. The variables used, and suggested values are:
- <OracleUserID>
- is the Oracle userid to be used to create the database.
- <OraclePassword>
- is the password for the Oracle userid.
Procedure
- Run the following commands:
- sqlplus <OracleUserID>/<OraclePassword> @ uddi30crt_10_prereq_oracle.sql
- sqlplus <OracleUserID>/<OraclePassword> @ uddi30crt_20_tables_generic.sql
- Complete one of the two following actions depending on your level of Oracle:
- For V10g and later
sqlplus <OracleUserID>/<OraclePassword> @ uddi30crt_25_tables_oracle.sql- For Oracle 9i
sqlplus <OracleUserID>/<OraclePassword> @ uddi30crt_25_tables_oracle_pre10g.sql
- sqlplus <OracleUserID>/<OraclePassword> @ uddi30crt_30_constraints_generic.sql
- sqlplus <OracleUserID>/<OraclePassword> @ uddi30crt_35_constraints_oracle.sql
- sqlplus <OracleUserID>/<OraclePassword> @ uddi30crt_40_views_generic.sql
- sqlplus <OracleUserID>/<OraclePassword> @ uddi30crt_45_views_oracle.sql
- sqlplus <OracleUserID>/<OraclePassword> @ uddi30crt_50_triggers_oracle.sql
- sqlplus <OracleUserID>/<OraclePassword> @ uddi30crt_60_insert_initial_static_data.sql
- This last command should only be run if you want the database to be used as a default UDDI node.
sqlplus <OracleUserID>/<OraclePassword> @ uddi30crt_70_insert_default_database_indicator.sql
What to do next
Continue with setting up and deploying your UDDI Registry node.
Related Tasks
Creating a DB2 database for the UDDI Registry
Creating a Cloudscape database for the UDDI Registry
- Restrictions:
- discoveryURL (Business) maximum 4000 bytes, UDDI specification 4096 characters; accessPoint (bindingTemplate) maximum 4000 bytes, UDDI Specification 4096 characters; instanceParms (tModelInstanceInfo) maximum 4000 bytes, UDDI specification 8192 characters; overviewURL (tModelInstanceInfo) maximum 4000 bytes, UDDI specification 4096 characters; Digital Signature maximum 4000 bytes.
- Restrictions:
- discoveryURL (Business) maximum 4000 bytes, UDDI specification 4096 characters.