I'm confused. You write that that your dbinit.sde has ORACLE_SID and that the service starts
and then stops (which is the expected result -- Use LOCAL as the variable), and that sdemon
and sdeservice report the service up and running -- which is it?
Application server connects are made to the ArcSDE host, not the Oracle host. Even if you're
running locally, an enabled firewall may block connection when you refer by the local IP.
You really should use robust passwords for administrative database users (and try to avoid
publishing them on the Internet). I try to avoid connecting as the SDE user, and never use
SYSTEM to connect via ArcSDE. Best practice is to create at least one tablespace to store
data and create one or more database users to own spatial data (with default tablespace
to (one of) the new tablespace(s)). I usually create a "read-mostly" user, which is granted
only SELECT access (via a "browse" role) to the spatial tables, and use that to connect
for mapping applications.
- V