HP Structured Records Management Solution Tutorial, August 2011

HP Structured Records Management Solution Tutorial 59
Runtime issues
Solution Upload the data to a different database.
Archive files not loaded into HP TRIM
Symptom Your cartridge successfully ran, and the XML files were generated, but the files
were not loaded into HP TRIM.
Cause In order for your archive files to be loaded into HP TRIM, the business flow must
successfully call the HP TRIM Loader to ingest the files into HP TRIM. If the
loader is not called or fails for some reason, the files are not ingested into HP
TRIM.
Solution • Ensure that your business flow includes a Groovy script that calls the HP
TRIM Loader.
• Ensure that your HP TRIM Enabler Pack configuration is correct. You may
need to consult with your DBA or HP Support.
TIP If necessary, use the Launch SRMS Loader tool to launch the loader
manually.
Insufficient capacity error in HP TRIM
Symptom HP TRIM displays the following error message when attempting to load your
archive data file:
Document store operation failed – the Document Store has
insufficient capacity
Cause When you archive a large amount of data from database to file, the archive data
files generated by HP Database Archiving can become quite large. HP TRIM
stores documents in the file system and therefore you must have enough free
space in that file system to accommodate the archive data files.
Solution Be conscious of the potential size of your archive date files and ensure that you
have sufficient free space in your HP TRIM file system. If necessary, do the
following before trying to load the data files:
• Clear some space on the HP TRIM file system.
• Create a new HP TRIM document store on a file system that has sufficient
space.
Loaded files do not match originals
Symptom When HP TRIM performs a validation of the archived files, you receive a
message stating that some hashes did not match originals.
Cause The problem could be either of the following:
• MD5 files were not generated by HP Database Archiving.
• The files changed between the time you generated them and the time they
were loaded into HP TRIM.