Troubleshooting: Why can't I save my stored item?

Symptoms: When a stored display is created, a row is added to the MM_Stored_Displays table. However the stored display doesn't appear in the dropdown menu in ArcMap. This issue may also appear when using the Copy Design tool. After copying a design, features are not associated with the new design. This is because the stored display associated with the copied design cannot be saved.

Problem: The problem may be in the MAXBLOBSIZE and MAXBUFSIZE parameters in SDE. The MAXBLOBSIZE SDE setting restricts the amount of the data you can save to that field. The MAXBUFSIZE SDE setting restricts the amount of data that can be transferred. Both settings default to 65K when SDE is installed, but may be increased up to 2GB (maximum) if the field is an Oracle field type Long Raw and up to 4GB (maximum) if the field is an Oracle field type Blob.

Solution: Increase the MAXBLOBSIZE and MAXBUFSIZE parameters in the database. There are two ways to modify these values, depending on your ArcSDE version.

ArcSDE 8.3 and earlier: Increase the MAXBLOBSIZE and MAXBUFSIZE parameters in your giomgr.defs file (which is located in SDEHOME\etc). Below is an example of the portion of giomgr.defs that should be modified.

   MAXBLOBSIZE      10000000    # Maximum BLOB size allowed for storage
        MAXBUFSIZE       10000000    # Maximum BUF size allowed for transfer

After you've made changes to this file, you must "import" the new parameters into your Oracle server table with the following command. Adjust for your SDE service, server name, and SDE password.

sdeconfig -o import -f full_path_and_file_name_of_giomgr.defs -i sde_service -s server_name -u sde -p sde_password

ArcSDE 9.0 and later: In a DOS command window, use the SDE line command "sdeconfig." Schneider Electric recommends setting the MAXBLOBSIZE parameter to 10Mb-20Mb. The example below shows how a user might increase the MAXBUFSIZE parameter to 1Mb. Adjust for your SDE service, server name, and SDE password.

  sdeconfig -o alter -v MAXBLOBSIZE=20000000 -i sde_service -s server_name -u sde -p sde_password
        sdeconfig -o alter -v MAXBUFSIZE=1000000 -i sde_service -s server_name -u sde -p sde_password
        

There are also settings in Oracle that may cause size errors when saving to system tables. You can set a maximum number of extents either on a table in Oracle or on a tablespace. The tablespace may just simply have run out of space. These space settings should be checked by a DBA in Oracle prior to making the above modification.

QR code for this page

Was this helpful?