search cancel

Best practices for Performing Database Saves.


Article ID: 41354


Updated On:


CA eHealth



Best Practices for Performing Database Saves


eHealth 6.2.2 onwards
Applies to all Operating Systems.


When performing a database save, follow these guidelines:

- Always perform backups using the eHealth database save commands to make sure that you can easily restore the saved database.
- Do not use Oracle tools or other third-party software to back up database files. Doing so can corrupt the database.
- Make sure that the locations to which you are saving the database have sufficient disk space for the backup. If you specify multiple locations, eHealth splits the backup data equally over the locations that you specify. It does not consider available disk space.
- Do not save the database to an NFS-mounted disk or mapped drive. eHealth does not support database saves to NFS-mounted disks or mapped drives.
- On Windows systems, do not include accented characters in pathnames or file names. If you use accented characters, the load utility cannot identify the location and cannot load the database.
- Do not use the UNIX tape archive (tar) utility on files that are larger than 2 GB. For larger files, you must split the saved files and tar the resulting smaller files.


Additional Information:

1. To do the save from the command line: save DB
    Enter the nhSaveDb command in a form similar to the following:

    nhSaveDb -ascii -p <path_to_save_tdb_directory>

2. To load the ASCII save on destination server(new server):

    nhLoadDb -p <path_of_saved_tdb_directory>
But before loading the ascii save, you need to stop the ehealth server (nhServer Stop)


Release: LHDEVC99000-6.3-eHealth-Live Health Upgrade Elements