English

Error: Unable to save edits. Logfile not found [SDE.DEFAULT]

Error Message

While editing data stored in an ArcSDE for Oracle geodatabase the following error is received when saving edits:

"Unable to save edits.
Logfile not found[SDE.DEFAULT]".

Cause

This error can occur when the ArcSDE geodatabase is stored in Oracle and session pooled logfile tables are being used.
An example of this configuration is shown below:

ALLOWSESSIONLOGFILE TRUE
LOGFILEPOOLSIZE 20

Solution or Workaround

For most Oracle DBMS geodatabases, shared ArcSDE logfiles is recommended and is the default setting. If session logfiles is a requirement due to workflow or other restrictions, then using the session temp logfiles is another option.
Using the sdeconfig -o alter command, the parameters associated with configuring ArcSDE logfiles can be adjusted.

  1. To configure shared logfiles:

    Code:
    sdeconfig -o alter -v MAXSTANDALONELOGS=0 -i <service> -s <server_name> -D <database> -u <DB_User_name> -p <DB_User_password> -N -q
    sdeconfig -o alter -v ALLOWSESSIONLOGFILE=FALSE -i <service> -s <server_name> -D <database> -u <DB_User_name> -p <DB_User_password> -N -q

  2. To configure session temp logfiles:

    Code:
    sdeconfig -o alter -v LOGFILEPOOLSIZE=20 -i <service> -s <server_name> -D <database> -u <DB_User_name> -p <DB_User_password> -N -q
    sdeconfig -o alter -v ALLOWSESSIONLOGFILE=TRUE -i <service> -s <server_name> -D <database> -u <DB_User_name> -p <DB_User_password> -N -q


    Note:
    The LOGFILEPOOLSIZE parameter can be adjusted according to the number of connections for best performance.

Related Information