FAQ: Why does ArcSDE service for Oracle fail to start?


Why does ArcSDE service for Oracle fail to start?


There are a number of reasons why the service may not start. View the list below to verify that the following criteria have been met. If additional help is needed, refer to the "ArcSDE Installation Guide" and the help topic Troubleshooting the ArcSDE service. For ArcSDE 9.1 or lower releases, consult the "Managing ArcSDE Services" or "Managing ArcSDE Application Servers" book.

· The RDBMS server must be up and running.

· The software must be installed in a certified environment.

· The RDBMS SDE user account must exist with appropriate permissions.

· The RDBMS SDE user must have created the ArcSDE geodatabase schema.

· The ArcSDE home directory must exist and the system PATH variable must be updated to reflect its location - in particular, the \bin and \lib directories under SDEHOME.

· The correct ORACLE_SID must be defined in $SDEHOME/etc/dbinit.sde for UNIX and Linux operating systems.

· The SDE service name and port number must be in the services.sde file found in the etc directory of SDEHOME, and the entry must be uncommented. Additionally, on Windows operating systems (OS), the SDE service name and port number must be in the Windows services file.

· The service name and port number in the OS services file must exactly match that found in the SDEHOME/etc/services.sde file.

· The following additional permissions must have been granted:

GRANT EXECUTE ON dbms_pipe TO public;
GRANT EXECUTE ON dbms_lock TO public;

See article 35408 for an alternative to this.
<a href='http://support.esri.com/en/knowledgebase/techarticles/detail/35408' target='_blank'>FAQ: Can the execute privilege be removed from public on Oracle packages?</a>

· For ArcSDE releases prior to 9.1, an ArcSdeServer license must be available for checkout from a license server accessible through the network. For ArcSDE releases 9.1 or higher, the geodatabase must have been authorized with a valid license file.

· On Windows, check the Application Log of the Event Viewer. The Event Viewer provides diagnostic information that may help explain ArcSDE startup problems.

If the above conditions are satisfied and the service still does not start, do as follows:

· Check the sde.errlog, the giomgr.log, and the sdelic.log for more detailed information as to why the ArcSDE service may have failed.

· Check the Oracle alert files for any error messages that may be related to the problem.

· For Windows, make sure the ArcSDE service was created correctly by running the 'sdeservice -o list -i <instance>' command. Check the SDEHOME variable, License_Server, data source, and status parameters. The Windows user who starts the ArcSDE service must be in either the Windows administrator or power user group.

· If the service was not correctly created, create a new service with 'sdeservice -o create'.
On Windows, try to start the server using the Services panel. If it fails, try using 'sdemon -o start -i <instance>'.

· For Windows, if the service will not start, use 'sdeservice -o delete' to remove the service, reboot the machine, and create the service again with 'sdeservice -o create'.

· Check that there are not duplicate ports in the operating system services file.

· Use the information collected above and refer to the following references for specific information on common startup problems.

� The "ArcSDE for Oracle Installation Guide", which is included on the ArcSDE installation media.

� The book "Managing ArcSDE services" or "Managing ArcSDE Application Servers", Chapter 6, "Trouble Shooting the ArcSDE Service"; PDF files are on the ArcSDE 9.1 or lower installation media (and installed on Windows operating systems).

Troubleshooting the ArcSDE service.

� The ArcSDE Administration Command Reference, which is included with the ArcSDE installation.