You can find information about some common known graphical user interface (GUI) issues that might help you resolve them.
|The SnapManager web start GUI displays the incorrect version.||After downgrading SnapManager from a later version to an earlier version when you launch the web start GUI, the later version of the SnapManager web start GUI is launched.||You must also clear the
cache by performing the following steps:
|When you restart the GUI and try to check the backups for a certain profile, you see only the names of the profiles.||SnapManager does not display any information about a profile until you open it.||Perform the following steps:
Note: You only need to authenticate the profile once as long as the credentials are valid and remain in the cache.
|The GUI installation on Windows succeeds, but with errors.||
The user account used to install the GUI does not have enough permissions to set up the icons and shortcuts for all the users. The user account does not have permissions to modify the C:\Documents and Settings\All Users directory.
|When you open the first repository in the GUI, an error message similar to the following is displayed: The Profile name XXXX clashes with previously loaded repository.||Identically named profiles cannot exist in a repository. Also, you can open only one repository at a time.||Reference the conflicting profiles from two different operating system (OS) users or rename the profile by issuing an SQL statement for the repository: UPDATE SMO_33_PROFILE SET NAME = 'NEW_NAME' WHERE NAME = 'OLD_NAME'|
|An error message similar to the following is displayed: SMO-01092: Unable to initialize repository repo1@ does not exist:repo1 SMO-11006: Cannot resolve host does not exist||The repository is inaccessible, perhaps because it no longer exists. The GUI initializes the list of repositories from the credentials file.||The error message asks if you would like to remove this repository so that no attempt is made to load it in the future. If you do not need to access this repository, click Delete to remove it from the GUI view. This removes the reference to the repository in the credentials file and the GUI does not attempt to load the repository again.|
|SnapManager takes a longer time to load the database tree structure and results in a timeout error message being displayed on the SnapManager GUI.||When you try to perform a partial backup operation from the SnapManager GUI, SnapManager tries to load the credentials for all the profiles, and if there are any invalid entries, SnapManager tries to validate the entry and this results in a timeout error message being displayed.||Delete the credentials of the unused host, repository, and profile by using the credential delete command from the SnapManager command-line interface (CLI).|
|The custom scripts for the preprocessing or postprocessing activity to occur before or after the backup, restore, or clone operations, are not visible from the SnapManager GUI.||When you add custom scripts in the custom backup, restore, or clone script location after you start the respective wizard, the custom scripts are not displayed under the Available Scripts list.||Restart the SnapManager host server and then open the SnapManager GUI.|
|You cannot use the clone specification XML file created in SnapManager (3.1 or earlier) for the clone operation.||From SnapManager 3.2 for Oracle, the task specification section (task-specification) is provided as a separate task specification XML file.|| If you are using SnapManager 3.2 for Oracle, you must remove the task specification section from the clone specification XML or create a new clone specification XML file.
SnapManager 3.3 or later does not support the clone specification XML file created in SnapManager 3.2 or earlier releases.
|SnapManager operation on the GUI does not proceed after you have cleared user credentials by using the smo credential clear command from the SnapManager CLI or by clicking from the SnapManager GUI.||The credentials set for the repositories, hosts, and profiles are cleared. SnapManager verifies user credentials before starting any operation.
When user credentials are invalid, SnapManager fails to authenticate. When a host or a profile is deleted from the repository, the user credentials are still available in the cache. These unnecessary credential entries slow down the SnapManager operations from the GUI.
|Restart the SnapManager GUI depending on how
the cache is cleared.
Note:Set the credentials that you have given for the repository, profile host, and profile. From the SnapManager GUI, if there is no repository mapped under the Repositories tree, perform the following steps:
|You cannot open the SnapManager GUI by using Java Web Start GUI due to weaker Secure Sockets Layer (SSL) cipher strength of the browser.||SnapManager does not support SSL ciphers weaker than 128 bits.||Upgrade the browser version and check the cipher strength.|