Is This Content Helpful?
We're glad to know this article was helpful.
If SDEVERBOSE is turned on when the ArcSDE command sdesetup runs, the application will display errors on the console as it looks for pre-existing tables, sequences, and packages. These errors are also trapped and handled by the program; they are not fatal. However, the messages are numerous and might be misleading in that it may seem sdesetup failed, when in fact, it ran correctly.
Below are some examples of errors that may display:
"SDE_Oracle Error: 942
ORA-00942: table or view does not exist"
"SDE_Oracle Error: 2289
ORA-02289: sequence does not exist"
.SDE_Oracle Error: 6550
ORA-06550: line 1, column 27:
PLS-00201: identifier 'SDE.SDE_UTIL' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored"
The 'set SDEVERBOSE=1' option is set in the $SDEHOME/etc/dbinit file on the ArcSDE server. This line signals the ArcSDE server to write non-fatal error messages to the $SDEHOME/etc/sde.errlog and to the console that would normally not be issued. This option is generally used for debugging.
This article is specific to sdesetup. The errors cited above are safe to ignore. If errors are encountered in a production environment, contact ESRI Support Services.
Refer to the ArcSDE Developer Help ArcSDE Administrator Command References for proper usage of the sdesetup command.