Investigating Why it Happened
The below sections give some advice on how to overcome various issues within the ServiceOptimizer instance. In all cases, if you are unable to make progress then a call should be raised with the ServiceScheduling support team (see ServicePower Support). Please ensure that you include all necessary evidence - Evidence required for ServiceScheduling Support covers this in more detail.
Why won't my system start up?
Logged error | Problem | Processes potentially affected | Solution | |||
---|---|---|---|---|---|---|
System Monitor | API Agent | Gantt Router | FRU | |||
spsysmon fails to start the system | If the system monitor failed to completely shutdown after the last startup, then the first thing it will do is attempt to tidy up and complete the shutdown process. | ![]() | This is correct behaviour, and not a cause for concern. Once the shutdown process has completed simply restart the system and it should startup normally | |||
spsysmon still fails to start the system | If the system still fails to startup then it may need help clearing down the system | ![]() | Instead of running spsysmon with the –s parameter use the –c parameter as described in System Monitor 1. Then try starting the system again as normal. | |||
Database error in log | The first thing the system monitor tries to do is connect to the database. If it cannot do this then it will not start up. Other server processes also need to connect to the database, so their logfiles may also show errors, but in general these would not prevent the system from starting. | ![]() | Speak with the system administrator and/or DBA to regain connection to the database. | |||
Missing Mandatory parameter | A parameter in SP083_System_Parameters is not set up, which the process requires to be present before starting. | ![]() | ![]() | ![]() | ![]() | This will often happen if the ServiceOptimizer software has been upgraded but DBInstall has not been run. With any upgrade, no matter how small, DBinstall must always be run (see Install Guide) |
Port number in use | The port numbers that are being used are held in the database. SQL for finding the ports in use is given below - look for the entries for the appropriate component | ![]() | ![]() | Ensure the ports allocated are not in use elsewhere.
| ||
Invalid user logged | The username that the API Agent uses to connect to other processes (such as authenticating to an FRU) does not exist. There is an sp083_system_parameters value that holds the username that the API agent uses to connect to the FRU processes. to give the user id that is needed. NB. A default is set up, but this value may be changed if required. | ![]() | It is advisable that this user is made very distinct, and easily recognizable, for its purpose. Also it should be set up as one that is not available for general update via the ServiceManager user maintenance screens (see ServiceManager AdminGuide) | |||
Travel matrix error logged | The travel matrix is not set up correctly. See Travel Time Estimates. The value of the travel_matrix parameter will give the file name (including extension) and the full path to the travel matrix .tm2 file. SQL to find where the Travel Matrix is expected to be found is given below | ![]() | ![]() | Verify that the travel matrix full path and name matches the relevant database entry. If they do not, either the DB should be updated or the travel matrix file moved.
| ||
Other error logged | Possibly some data has been corrupted in the database. | ![]() | ![]() | ![]() | ![]() | The error message in the log file will usually indicate an oracle error or complain about invalid data. At this point, contact SERVICEPower support and include the log file in the communication (see Contacting ServicePower Support) |
Why has my API call failed?
Has an end user reported that an API has appeared not to work?
Does a component crash point at there being a issue with an API?
All systems that interface with ServiceOptimizer will use the standard APIs. The information that is passed through to ServiceOptimizer can be seen in the APIAgent log file. Reading Log files covers how to analyse these logfiles to ascertain what might have happened.
Why have I run out of space?
Are all the regular tidy processes working correctly
Do these need reviewing?