Administration Utility Error

[User35489]

Good Day Guys,

When i tried to run the command SDELAYER
SDELAYER -O DESCRIBE_LONG
it throughs an error

"
[sde@LinuxServer etc]$ sdelayer -o describe_long

Error: SDE not running on server (-101).
Error: Cannot get configuration information
"

Where my service is up and running. I tried restarting the ArcSDE service, it did not worked out...

My Environment: Oracle 11.2.0.3, RHEL6, ArcSDE 10.1(SP1)

Please look into this issue...

Thanks
-Abdullah Saleh

[VinceAngelo]

There's probably been two or three times in the past eighteen years where I really
wanted to run an unadorned "describe_long", but for the most part, you never
want to do that.

ALL command line utilities (may they rest in peace) take *lots* of arguments, the
most important of which are the connection parameters (-s / -i / -D / -u / -p).
All table commands require a "-t".  All layer commands require a "-l". The exact
syntax can be discovered by running the command without any arguments.

In reality, it gets even more interesting, because the connection parameters are
mostly optional, and they have environment variable equivalents.

If, after setting SDEUSER and SDEPASSWORD, and using a -l constraint, you
discover that the instance is not running on the default port on the local host,
you will also need to use or set the server and/or instance parameters.

- V

[User35489]

Vince thanks for your input..
While trying to find a workaround, i found the below command worked instead..

sdelayer -o describe_long -i 5151 -l LayerName,Column -u sde -s ServerName

I found the below link to find a workaround...
http://forums.arcgis.com/threads/2309-A-problem-seemed-silly-cannot-connect-to-SDE-service
Thanks to "Yu De"


-AS

[VinceAngelo]

I can't think of a single reason why that command should ever be run as user SDE.
The SDE user should be reserved for ArcSDE instance administration.  The SDE
user should not ever own spatial data (treat it like a restricted admin account).

- V

[User35489]

I can't think of a single reason why that command should ever be run as user SDE.
The SDE user should be reserved for ArcSDE instance administration.  The SDE
user should not ever own spatial data (treat it like a restricted admin account).

- V

I too agree with you, Vince...
Actually the command is run by the SDE User, but the layer is owned by another user. It was just to show the example. Actual command looks like this

$ sdelayer -o describe_long -i 5151 -l LayerOwner.LayerName,ColumnName -u sde -s ServerName

Thanks for your inputs.
Regards
-AS

[VinceAngelo]

Best practice is to forget the SDE user exists.  It should not be used to get layer
properties -- That's the job of the table owner or a browse user to whom SELECT
access has been granted.  If you use the SDE user casually, there will be a moment
when you regret it; hopefully it won't involve a complete database restore to fix.

- V