The uninstallation procedure is described below.
Note
If performing operation with WebAdmin, back up the following file before uninstallation.
Instances will not be recognized by WebAdmin even if Symfoware Server is reinstalled after uninstallation.
If performing operation with WebAdmin after reinstalling Symfoware Server, replace the following backed up file after installation.
installFolder\gui\data\gui-instanceBy replacing the above file in the installation folder after installation, the instance will be recognized by WebAdmin, and the recognized instance will be set to automatically start and stop.
To disable the automatic start and stop setting for an instance, select the service for the applicable instance in the Windows services window, and in [Startup Type], select [Manual].
If a PL/extJava environment has been built, delete the domain. Refer to "Setting up and Operating PL/extJava" in the Operation Guide for details.
If using database multiplexing mode, refer to "Uninstalling in Database Multiplexing Mode in the Symfoware Server Cluster Operation Guide before performing the uninstallation.
See
Refer to the Installation and Setup Guide for Client when uninstalling the Symfoware Server client feature.
1. Stop applications and the client program
Before starting the uninstallation, stop the following:
Applications that use the product
pgAdmin
2. Stop all instances
Stop all instances that are using the product to be uninstalled.
In the [Monitor] window, click [Stop].
Use the following procedure to stop a service:
Display the [Services] window.
In Windows, select [Administrative Tools], and then click [Services].
Stop the service
Select the instance name that you wish to stop from the services list, and click [Stop Service]. If you stop a service while applications and commands are running, Symfoware Server will force those applications and commands to close and will stop normally.
You can also stop a service by specifying the service name in the net stop command or sc stop command.
3. Stop WebAdmin
If you are using WebAdmin, stop WebAdmin.
Refer to "E.1.3 Stopping the Web Server Feature of WebAdmin" for details.
4. Unregister Windows services
Perform this step if the instance was created with the initdb command.
Unregister the instance registered in Windows services.
Use the unregister mode of the pg_ctl command to specify the registered service name and unregister the instance from Windows services.
The following is an example showing execution of this command for the registered service name "inst1".
> pg_ctl unregister -N "inst1"
Note
You should unregister services before uninstalling Symfoware Server. If you uninstall Symfoware Server while services are running, several files will remain after the uninstallation.
If you have carried out the uninstallation without unregistering services beforehand, use the server command sc delete to unregister the services.
5. Delete registrations related to the event log
If you are outputting to the event log, a DLL registration mentioned in "4.2.5 Preparing for Output to the Event Log" has been performed.
To prevent unnecessary issues from occurring, you should delete this registration. Refer to "Server Administration", "Registering Event Log on Windows" in the PostgreSQL Documentation for details.
The following is an example showing deletion of the DLL registration for a 64-bit product under the default event source name.
regsvr32 /u "c:\Program Files\Fujitsu\symfoserver64\lib\pgevent.dll"
DLL registration is performed so that you can output messages corresponding to the event source name assigned by the user, allowing you to identify messages output to the event log by instance.
Since it is necessary to delete the DLL registration for each instance, delete the DLL registration by event source name.
The following is an example showing deletion of the DLL of a 64-bit product registered under the event source name "Symfoware Server inst1".
regsvr32 /u /i:"Symfoware Server inst1" "c:\Program Files\Fujitsu\symfoserver64\lib\pgevent.dll"
Note that this step is not required if the instance was created with WebAdmin.
If the instances you created using this package have been set to output error logs to the event log, use the DLL path name that you took note of previously as explained in "4.2.5 Preparing for Output to the Event Log" to reregister the default event source name.
Note
Ensure to delete DLLs before the uninstallation. If you perform the uninstallation without doing so, you may not be able to delete the DLLs at a later time.
6. Start the command prompt
In Windows, right-click [Command Prompt] and then select [Run as administrator].
If using Windows Server(R) 2003, click the icon.
Execute the command below.
The installation directory may remain after uninstallation. If it is not required, delete it.
> installFolder\suninst.batX: Drive on which the product is installed
Note
In Windows(R)7, Windows Server(R) 2008 or Windows Server(R) 2008 R2, an empty folder may remain in the [Start] menu after uninstallation. In Windows, select [All Programs], right-click the following, and then click [Delete]:
Symfoware Server Client (Open Interface) (32-bit) V12.1.0
Symfoware Server Client (Open Interface) (64-bit) V12.1.0
Uninstaller results will be output to the log file.
xxyz is the number part when the version is Vxx.y.z.
pathName:%TEMP%\SymfowareOpen_SV_64_xxyz.logpathName:%TEMP%\SymfowareOpen_SV_32_xxyz.logThe following return values are output:
Return value | Description |
|---|---|
0 | Uninstallation was successful. |
64 | Failed to install because "Uninstall (middleware)" is running. |
74 | Failed to write product information (updating registry). |
79 | Failed to read product information (viewing registry). |
83 | Failed to delete the information from FJQSS. |
129 | Unsupported operating system. |
144 | Not executed with administrator privileges. |
251 | An error occurred when running a system function. |
255 | An internal inconsistency occurred. |