The following error
messages might appear when you run the
Export SAS Package wizard,
the
Import SAS Package wizard, or the batch
import or export tool:
Solutions for Error Messages
Out of memory error occurred during the import
(or export) process.
This message indicates
that an out of memory error occurred on the client machine. The error
could occur if you export or import a large number of sizable objects,
such as information maps or SAS Data Integration Studio jobs. If this
error occurs, you can take either of the following actions:
-
Instead of exporting all of your
objects at the same time, perform multiple exports that include a
smaller number of objects.
-
Increase the amount of memory that
is allocated to the import or export process. For instructions, see
Ensure Adequate Memory.
ERROR - Failure exporting metadata from source
repository. Reason: org.omg.CORBA.NO_MEMORY: Insufficient memory
This message, or a similar
message, appears if an out-of-memory error occurs on the metadata
server machine. Solutions might include the following:
-
Check the memory settings on the
server machine and adjust them as necessary.
-
Use the Analyze and Repair Metadata
utility in SAS Management Console to clean up orphaned metadata. Then
use the
Reorganize
Repositories option
of the metadata server backup facility to reclaim unused disk space
left from deleted metadata objects.
-
Instead of exporting all of your
objects at the same time, perform multiple exports that include a
smaller number of objects.
The export process has failed. No X11 DISPLAY
variable was set, but this program performed an operation which requires
it. For more information, view the export log file:
filename
This error could occur
if you submit a batch import or export job on a UNIX machine for which
the DISPLAY variable has not been set. To resolve the error, set the
DISPLAY variable by entering a command such as the following:
export
DISPLAY=
machine-name
This error can occur
if you try to import a package file whose contents were updated after
the package was created. For example, if you open a package file,
save any of the files in the package (for example, the export log),
and then save the package file, then the package becomes corrupted
and cannot be imported.
To resolve the error,
perform the export again to re-create the package.
The following resources could not be found in
the package file or on the target server. Objects dependent on these
resources may not function properly after the import process.
This message means that
the objects that you are importing depend on objects that are not
present on the target metadata server.
You will need to import
the resources that objects depend on, unless those resources already
exist in the target environment. For example, in order for a report
to function properly, you must import the information map that the
report depends on, as well as any stored processes that are associated
with the report.
Destination folder has invalid or missing content
mapping; cannot import reports.
Content mapping, which
is set up during the installation and configuration process, establishes
the location of the XML (.srx) files that define reports. The location
must be a path on the SAS Content Server. If this message appears
when you try to run the import wizard, click
OK to
close the message box and click
Cancel. Then
follow these steps to check content mapping on the target metadata
server:
-
Right-click the appropriate
folder in the SAS Folders tree, and click
Properties.
Generally, content mapping is specified in the root folder (
SAS
Folders).
-
Open the
Content
Mapping tab, and make any necessary changes. When you
specify the location on the SAS Content Server, you must enter the
user ID and password for the SAS Trusted User (sastrust) in the appropriate
fields. Then start the import again.
Could not import "
filename.sas"
in "
path"
on application server "
server name".
Reason: Insufficient authorization to access
path.
This message appears
in the error log at the end of the import process. It means that the
user who ran the import does not have Write permission for the specified
directory in the file system of the target machine. Grant the user
Write permission to the directory, and run the import again.
Libname
library
name is not assigned.
This message could appear
in the error log if you try to export physical tables along with DBMS
table objects while you are logged on as an unrestricted user. Unrestricted
users (for example, sasadm) cannot access the servers that are necessary
to export physical DBMS tables. Log on as a different user, and start
the export process again.