Skip Headers

Oracle TopLink Developer's Guide 10g Release 3 (10.1.3) B13593-01 |
| Home | Solution Area | Contents | Index

Previous | Next |

# XML Schema Errors (700 – 706)

This section lists TopLink Workbench XML schema errors.

701: A database table can only have one IDENTITY column defined.
  Cause: You defined more than one identity column for this table.
  Action: On the database table's Columns tab, leave only one identity (Identity) column. See "Working With Column Properties".

702: A size is required for the column [column].
  Cause: You did not specify any size for this column. The default size is 0.
  Action: On the database table's Columns tab, specify the size (Size) for the column (field). See "Working With Column Properties".

703: The reference [table reference] does not have any field pairs.
  Cause: You added a reference for a table, but the reference does not include a key pair.
  Action: On the database table's References tab, specify source and target field pairs for the table reference. See "Creating Table References".

704: A key pair has not been completely specified for a reference.
  Cause: A reference table is missing a complete key pair (source and target fields).
  Action: You must specify a foreign key reference for the database table. On the database table's References tab, add a complete key pair. "Creating Table References".

705: A development login has not been specified.
  Cause: You created a relational TopLink Workbench project, but did not specify a development login.
  Action: On the Database property sheet, select a Development Login from the available defined logins, or add a new login. See "Configuring Development and Deployment Logins".

706: A deployment login has not been specified.
  Cause: You created a relational TopLink Workbench project, but did not specify a deployment login.
  Action: On the Database property sheet, select a Deployment Login from the available defined logins, or add a new login. See "Configuring Development and Deployment Logins".