No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


The Startup Script Startsybaseserver errors leads database process fails to start.

Publication Date:  2012-07-25 Views:  61 Downloads:  0
Issue Description
N2000 BMS Version:: V200R011C03B036SPC003

Watchman Version::V200R007C50B113CP0015

For the N2000 BMS high availability (HA) system, the N2000 processes can be properly started and stopped by the Watchman on the standby server. After the N2000 processes are stopped by the Watchman on the active server, however, they fail to be started again on the active server.

Alarm Information
Because the Watchman fails to start the database process and other processes for a long time, an alarm indicating a process abnormality is reported on the Watchman.  
Handling Process
1. When the Watchman client starts processes, the database process is not started. Therefore, check whether the database is faulty. Navigate to the /opt/sybase/ASE-12_5/install folder and run the following command to manually start the Sybase:
#./startserver -f ./RUN_N2000DBServer &
After the command is used, the returned information indicates that the N2000DBServer database is successfully started. Then, run the ps-ef|grepSybase command to view the sybase process, but the sybase process cannot be found and the database_server process is grayed out on the Watchman client, which indicates that the process is not started.
2. Because the database process is not started, the installation of the N2000 BMS software is not checked.
3. Manually start the database and the database is successfully started. After running the ps command, you cannot view the sybase process. This is normal because all N2000 processes are stopped by the Watchman client previously. Even though the database is manually started later, since the Watchman has a higher priority in process control, the Watchman stops the database process again. As a result, the sybase process cannot be viewed even when you run the ps command.
4. Since the Watchman fails to start the database process, the script of the Watchman for starting the database must has errors.
5. The Watchman client uses a script of starting the database to start the sybase process. The script is startsybaseserver in the /opt/watchman/server/script/ directory and the script is saved to this directory when the N2000 UMS software is installed. To check whether the script has errors, manually run the script in this way: Navigate to the /opt/watchman/server/script/ directory and run the following command:
root@N2000Primary # ./startsybaseserver &
The returned information is as follows:
root@N2000Primary # Sun Microsystems Inc. SunOS 5.8 Generic Patch February
couldn’t push module ’ip’, No such device or address
sh: /opt/sybase/ASE-12_0/install/: cannot execute
Start database server failed!
The returned information indicates that the database fails to be started.
6. Since the Watchman can properly start and stop the database and the N2000 processes on the standby server, compare the script file on the active server with the script file on the standby server and the following differences are found:
Active server (abnormal)
StartSybaseServer "$1"
Standby server (normal)
StartSybaseServer "$1"
In the preceding information, the two scripts differ in the second line which defines the environment variable, and the environment variable for the active server is incorrect. Then, overwrite the script file on the active server with the script of the standby server, restart the background process of the Watchman, and start the N2000 processes on the Watchman client. As a result, all the processes are successfully started
Root Cause
1. The database is faulty.
2. The N2000 BMS is improperly installed.
3. The Watchman is improperly installed. 

To understand the mechanism of the N2000 BMS HA system, the principle of starting the processes, and the dependency between the processes, is very important for troubleshooting.
Besides, the problem occurs probably because relevant files are not uninstalled when the N2000 BMS software is re-installed previously. Therefore, you are advised to follow the guide to delete the relevant files, database, and volumes when uninstalling the N2000 BMS software.