Working with Data Models › How to Reverse Engineer a Model from a Database or a Script › Reverse Engineer Processing Errors

Reverse Engineer Processing Errors

When you reverse engineer a script or a database, parser errors may occur. Parser errors often occur when there is a mismatch between the syntax in the script or database, and the target server for the new model. For example, if you try to reverse engineer an Oracle database after selecting SQL Server as the target server, you will encounter parser errors.

After you select the Reverse Engineer options from the wizard and click Next, the parser begins to process your script file or database. If the parser encounters an error, it displays it in the informational window in the parser dialog. The parser dialog provides you with information that enables you to evaluate the processing errors and view details of a specific syntax error.

When a parser error displays, you can choose one of the following actions from a pop-up box:

Skip this error

Skips the displayed error and continues processing the script or database.

Skip all errors

Skips all errors and completes processing the script or database.

Cancel processing

Closes the parser dialog and cancels the reverse engineering process.

You can save the text of a selected error to a text file. For long error messages, select an error, and then click the Details icon to display the complete text of the error in a new window.

Troubleshooting

This section includes details of how you can troubleshoot the reverse engineering process and the reverse engineered model.

How to Add Naming Standards

Symptom:

How to add naming standards to a reverse engineered model?

Solution:

Follow these steps:

1. Create a model and include the naming standards.
2. Save the model as a template.
3. Select this template in the Match template field of the New Model dialog.

   The naming standards are selected in the new model.

Unable to use a Reserved Word

Symptom:

When I try to reverse engineer from a script, I get the error message, "RES-1:Syntax Error - Line <number>, Offset11 <word>".

Solution:

This error message appears when you use a database-specific reserved word or a keyword. Add the quotation marks (" and ") around the word in the script and then reverse engineer.

Unable to Locate Client Connectivity Software Ora7nt

Symptom:

I am trying to connect to an Oracle 11g database and I am getting the message, "Unable to locate client connectivity software Ora7nt.dll."

Solution:

CA ERwin Data Modeler is a 32-bit application and requires 32-bit client libraries to connect to the database. The reason for this error is that the application could not find the required Oracle client to connect to the Oracle instance.

Try one of the following solutions:

• Install the Instant client software that is available from Oracle into a directory that does not contain any spaces in the PATH. For example, C:\app\Administrator\Oracle.
• If both 32-bit and 64-bit Oracle clients exist on the same computer, then ensure that the PATH environment variable refers to the 32-bit Oracle client. Include the path "C:\Oracle\product\11.2.0\client_32\" at the beginning of the variable value.