Skip to main content
SnapManager Oracle

Troubleshooting SnapManager


You can find information about some of the most common issues that might occur and how you can resolve them.

The following table describes common issues and possible solutions:

Issue-driven question Possible solution

Are the target database and listener running?

Run the lsnrctl status command. Ensure that the database instance is registered with the listener.

Is the storage visible?

Run the snapdrive storage show -all command.

Is the storage writable?

Edit a file in the mountpoint that you just created. Use the touch filename command. If the file is created, then your storage is writable. You must ensure that the storage is writable by the user that SnapManager runs as (for example, as root on UNIX).

Is the SnapManager server running?

Run smo_server status and try to start the server by using the smo_server start command.

Before you can use the graphical user interface (GUI) or the command-line interface (CLI) to initiate SnapManager commands related to profiles, the server must be running. You can create or update repositories without starting the server, but to execute all other SnapManager operations, the server must be running.

To start the SnapManager server, enter the following command: smo_server start.

Are all the components required to run SnapManager set up correctly?

Run the smo system verify command to verify that SnapDrive is set up correctly.

Do you have the correct version of SnapManager?

Use the smo version command to check the SnapManager version.

Have you looked at the SnapManager log files to determine if the error messages can help isolate the issue?

SnapManager records all log entries into one set of rotating log files. The log files are found at /var/log/smo.

The log files are found at C:\program_files\NetApp\SnapManager for Oracle\logs.

It might also be helpful to look at the logs in the following location:


Each operation log is written to its own log file of the form smo_of_date_time.log.

If you have archive logs stored on a storage system that is not running Data ONTAP, have you excluded them from consideration for backup with SnapManager?

The smo.config file enables you to exclude certain archive log files. For UNIX, the files are at the following location: /opt/NetApp/smo/properties/smo.config

Use the format mentioned in the file to exclude the local archive logs. For additional information, see the “Setting configuration properties” topic.

You can also exclude the archive log destinations while creating a backup from the SnapManager CLI. For additional information, see the “Creating database backups” topic.

You can also exclude the archive log destinations while creating a backup from the SnapManager GUI.

Do you have a FlexClone license if you are using SnapManager with NFS databases?

A FlexClone license is required to take full advantage of SnapManager with NFS databases. SnapManager uses the FlexClone feature to accomplish these tasks:

  • Mount backups of NFS databases

  • Verify backups of NFS databases

  • Clone NFS databases

  • Register backups of NFS databases with RMAN (if using RMAN)

Were you unable to connect to the repository?

If connecting to a repository fails, run the lsnrctl status command on the repository database and check the active service names. When SnapManager connects to the repository database, it uses the service name of the database. Depending on how the listener is setup, this might be the short service name or the fully qualified service name. When SnapManager connects to a database for a backup, restore, or other operation, it uses the host name and the SID. If the repository does not initialize correctly because it is currently unreachable, you receive an error message asking whether you want to remove the repository. You can remove the repository from your current view so that you can perform operations on other repositories.

Also, check whether the repository instance is running by running the ps -eaf

grepinstance - name command.

Can system resolve the host name?

Check whether the specified host name is on a different subnet. If you receive an error message that SnapManager cannot resolve the host name, then add the host name in the host file.Add the host name to the file located at /etc/hosts: hostname IP address

Is SnapDrive running?

Check whether the SnapDrive daemon is running: -snapdrived status

If the daemon is not running, a message appears indicating that there is a connection error.

Which storage systems are configured to be accessed with SnapDrive?

Run the command: -snapdrive config list

How can SnapManager GUI performance be improved?

  • Ensure that you have valid user credentials for the repository, profile host, and profile.

    If your credential is invalid, then clear the user credentials for the repository, profile host, and profile. Reset the same user credentials that you set before for the repository, profile host, and profile. For additional information about setting the user credentials again, see “Setting credentials after clearing credential cache”.

  • Close the unused profiles.

    If the number of profiles that you have opened is more, the SnapManager GUI performance slows down.

  • Check whether you enabled Open On Startup in the User Preferences window under the Admin menu, from the SnapManager GUI.

    If this is enabled, then the user configuration (user.config) file available at /root/.netapp/smo/3.3.0/gui/state is displayed as openOnStartup=PROFILE.

    Because Open On Startup is enabled, you must check for recently opened profiles from the SnapManager GUI, using lastOpenProfiles in the user configuration (user.config) file: lastOpenProfiles=PROFILE1,PROFILE2,PROFILE3,…​

    You can delete the profile names listed and always keep a minimum number of profiles as open.

  • The protected profile takes more time to refresh than the profile that is not protected.

    The protected profile is refreshed at a time interval, based on the value specified in the protectionStatusRefreshRate parameter of the user configuration (user.config) file.

    You can increase the value from the default value (300 seconds) so that the protected profiles are refreshed only after specified time interval.

  • Before installing the new version of SnapManager on the UNIX-based environment, delete the SnapManager client-side entries available at the following location:


SnapManager GUI takes more time to refresh when there are multiple SnapManager operations started and running simultaneously in the background. When you right-click the backup (that is already deleted but still gets displayed in the SnapManager GUI), the backup options for that backup are not enabled in the Backup or Clone window.

You need to wait until the SnapManager GUI gets refreshed, and then check for the backup status.

What would you do when the Oracle database is not set in English?

SnapManager operations might fail if the language for an Oracle database is not set to English. Set the language of the Oracle database to English:

  1. Add the following under the initial comments in /etc/init.d/smo_server

    • NLS_LANG=American_America

    • export NLS_LANG

  2. Restart the SnapManager server using the following command: smo_server restart

Note If the login scripts such as .bash_profile, .bashrc, and .cshrc for the Oracle user is set to NLS_LANG, you must edit the script to not overwrite NLS_LANG.

What would you do when the backup scheduling operation fails if the repository database points to more than one IP and each IP has a different host name?

  1. Stop the SnapManager server.

  2. Delete the schedule files in the repository directory from the hosts where you want to trigger the backup schedule.

    The schedule file names can be in the following formats:

    • repository#repo_username#repository_database_name#repository_host#repo_port

    • repository-repo_usernamerepository_database_name-repository_host-repo_port Note: You must ensure that you delete the schedule file in the format that matches the repository details.

  3. Restart the SnapManager server.

  4. Open other profiles under the same repository from the SnapManager GUI to ensure that you do not miss any schedule information of those profiles.

What would you do when the SnapManager operation fails with credential file lock error?

SnapManager locks the credential file before updating, and unlocks it after updating.When multiple operations run simultaneously, one of the operations might lock the credential file to update it. If another operation tries to access the locked credential file at the same time, the operation fails with the file lock error.

Configure the following parameters in the smo.config file depending on the frequency of simultaneous operations:

  • fileLock.retryInterval = 100 milliseconds

  • fileLock.timeout = 5000 milliseconds

Note The values assigned to the parameters must be in milliseconds.

What would you do when the backup verify operation's intermediate status shows failed in the Monitor tab even though the backup verify operation is still running?

The error message is logged in the sm_gui.log file. You must look in the log file to determine the new values for the operation.heartbeatInterval and operation.heartbeatThreshold parameters which will resolve this issue.

  1. Add the following parameters in the smo.config file:

    • operation.heartbeatInterval = 5000

    • operation.heartbeatThreshold = 5000 The default value assigned by SnapManager is 5000.

  2. Assign the new values to these parameters.

    Note The values assigned to the parameters must be in milliseconds.
  3. Restart the SnapManager server and perform the operation again.

What to do when you encounter a heap-space issue?

When you encounter a heap-space issue during SnapManager for Oracle operations, you must perform the following steps:

  1. Navigate to the SnapManager for Oracle installation directory.

  2. Open the launchjava file from the installationdirectory/bin/launchjava path.

  3. Increase the value of the java -Xmx160m Java heap-space parameter.

    For example, you can increase the default value of 160m to 200m.

    Note If you have increased the value of the Java heap-space parameter in the earlier versions of SnapManager for Oracle, you should retain that value.

What would you do if you cannot use the protected backups to restore or clone?

This issue is observed if you were using SnapManager 3.3.1 with clustered Data ONTAP and have upgraded to SnapManager 3.4. The backups were protected using post-scripts in SnapManager 3.3.1. From SnapManager 3.4, the backups are protected using either SnapManager_cDOT_Mirror or SnapManager_cDOT_Vault policies which are selected while creating a profile.After upgrading to SnapManager 3.4, you might still be using the old profiles and thus backups are protected using backup scripts, but you cannot use them for restore or cloning using SnapManager.

You must update the profile and select either SnapManager_cDOT_Mirror or SnapManager_cDOT_Vault policy and delete the post-script that was used for data protection in SnapManager 3.3.1.

What would you do if scheduled backups are not getting protected (SnapVault)?