Troubleshooting
If the following errors are encounter when using Dynamic Import, note the explanation and resolution to correct the problem.
Troubleshooting:
When I run Dynamic Import I get an error message about the application not being able to locate the custom/utils.pm file in @INC—for example:
Can't locate custom/utils.pm in @INC (@INC contains: /
pdm/encaps/adapters /pdm/clients/clientapi/orb/perllib/
PCMPlugin /pdm/clients/clientapi/orb/perllib /pdm/encaps
/etc/xyvision/common/perl/lib/5.6.0/sun4-solaris /etc/
xyvision/common/perl/lib/5.6.0 /etc/xyvision/common/
perl/lib/site_perl/5.6.0/sun4-solaris /etc/xyvision/
common/perl/lib/site_perl/5.6.0 /etc/xyvision/common/
perl/lib/site_perl .) at digui.pl line 36.
BEGIN failed--compilation aborted at digui.pl line 36.
Explanation:The utils.pm file was not found in the Contenta_home/di/custom directory. This step may have been missed during installation.
Resolution:
Copy utils.pm and CustomCallbacks.pm from the Contenta_home/di to ..encaps/di/custom.
Troubleshooting:
Dynamic Import was interrupted during the import process and I tried to restart using the drivefile.xml file when I resumed the import process but DI started the import over from the top level instead of the point of failure.
Explanation:
When Dynamic Import was interrupted it may not have exited properly and you may have a stale Contenta user session hanging that is causing the problem.
Resolution:
Use pcmsessions tool with the -clear and -user switches to clear the user session(s) that failed. Refer to Contenta Sessions Command of the Contenta System Administration Guide for a list and description of the pcmsessions switches and the syntax for the command.
Troubleshooting:
Whenever I try to import a large file, the import fails.
Explanation:
This may be due to insufficient memory resources.
Resolution:
Try increasing the memory on the system where you are executing the import or use another system with more memory.
Troubleshooting:
The Dynamic Import output log (GUI log report) reported the following error:
Error (-10) Cannot open /pdm/encaps/di/sgmlFiles/
allwell.xml (SliceDTD)</state>
<exit id="s3" status="-10">Exiting</exit>
And the following was reported in the ../di/encaps/errs
file:
Error (-10) Cannot open /pdm/encaps/di/sgmlFiles/
allwell.xml (SliceDTD)
Exiting
Explanation:
The file you specified in the Source field of the Dynamic Import application does not exist in the directory path specified. Whenever you see an error containing a path and/or filename follow the steps below.
Resolution:
Check that the directory path or filename was entered properly (that there are no typing errors).
Go to the directory path specified and make certain the file exists in that path.
UNIX: Check case—UNIX paths and filenames are case-sensitive.
Windows: Check the file properties and make certain that the file is not Read Only.