This topic provides
guidance for replacing missing secured data folders, secured library
objects, and secured table objects.
Note: Some of the resolutions in
this section use the REPAIR statement, most of which is a preproduction
feature in the current release. These
resolutions should be used only under advice and direction from SAS
Technical Support.
As an alternative to using the REPAIR statement, you can create a
new physical library, bind that library to metadata, and use the SAS
COPY procedure to copy your data into the new library.
See REPAIR Statement.
Issue: A secured data folder is missing.
Resolution:
Use one of the following
approaches:
-
Use the metadata promotion tools
to import the folder (and its contents) from an existing package.
See Promotion Tools Overview in SAS Intelligence Platform: System Administration Guide.
-
Re-create the folder in SAS Management
Console. On the
Folders tab, navigate to
the appropriate location (under a repository’s
/System/Secured
Libraries
branch), right-click, and select
NewFolder.
-
Issue: A secured library object is missing.
Resolution:
Use one of the following
approaches:
-
-
Use the REPAIR
statement of the AUTHLIB
procedure, with the ADD action and the METADATA option. This approach should be used only under
advice and direction from SAS Technical Support.
-
Issue: A secured table object is missing.
Resolution:
Use one of the following
approaches:
-
Use the metadata promotion tools to import the
secured table object’s parent library from an existing package. The import overwrites the current secured
library object and its child objects, and it re-creates any missing secured table
objects.
See Promotion Tools Overview in SAS Intelligence Platform: System Administration Guide.
-
Use the REPAIR statement of the AUTHLIB procedure, with the ADD action, the METADATA
option, and TABLESONLY=YES. This approach should
be used only under advice and direction from SAS Technical Support.
-