When you update metadata for a table using either a client application (for example, SAS^® Management Console) or PROC METALIB, the metadata might not be updated. When this problem occurs, the SAS log shows either a Read-access violation or a segmentation violation, depending on your operating environment. In Microsoft Windows environments, you receive a Read-access violation. In UNIX and Linux environments, you receive a segmentation violation.

In SAS Management Console, you receive the violation when you do the following:

1. Right-click the database management server (DBMS) table and select Update Metadata.
2. In the dialog box that appears, you click Yes when it asks whether you want to continue.

After you click Yes, another dialog box then appears with a message similar to the following:

Clicking Yes in this dialog box opens the SAS log where you can see the full error, as shown below. (This is the same error that you receive in Base SAS^® software when you run PROC METALIB code to update the metadata.)

The problem occurs when all of the following are true:

• Many options are defined in a LIBNAME statement such that the statement has a total of more than 256 characters.
• One of the options in the LIBNAME statement is of the form option-name="string=value" (for example, QUERY_BAND="ClientUser=user-ID;").
• A macro-variable reference is part of the LIBNAME statement definition.

Here is an example of such a LIBNAME statement:

To work around this problem, you either need to reduce the number of options that are defined for the library in the LIBNAME statement or remove the macro-variable reference.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for Base SAS 9.4_M3 is available at: