You are on page 1of 2

Document 946564.1

Copyright (c) 2018, Oracle. All rights reserved.

Error "1070020 Out of disk space. Cannot create a new [Index] file. [adIndNewFile] aborted" and Info
"1008108 Essbase Internal Logic Error [7333]" (Doc ID 946564.1)

In this Document



Hyperion Essbase - Version and later

Information in this document applies to any platform.
***Checked for relevance on 20-May-2014***


While running a calculation or restructure the application crashes with an xcp log.

The exception log (log0000#.xcp) shows the following:

Assertion Failure - id=7333 condition='((!( dbp )->bFatalError))'

- line xxxx in file kernel/indbtree.c
- arguments [0] [0] [0] [0]
Fatal Error Occurrence.


Assertion Failure - id=7333 condition='((!( dbp )->bFatalError))'

- line <number> in file kernel/objind.c
- arguments [0] [0] [0] [0]

From the stack:

(11) 0xc00000000b430de0 adIndReadFreeBlks + 0x1c0 at kernel/objind.c:805 [/cluster/hypprd/app/Hyperion/AnalyticServices

The application log may show one or all of the following:

Warning(1019004) Unable to write information to file [e:\Hyperion\AnalyticServices\APP\xxx_xx \xxx_xxx\ess00001.ind], errno is

Error(1070020) Out of disk space. Cannot create a new [Index] file. [adIndNewFile] aborted
Info(1008108) Essbase Internal Logic Error [7333]
Info(1008108) Essbase Internal Logic Error [7303]


There are multiple potential reasons for this problem:

Disk Space may be low.

When the compression setting has been set to none, the data on the disk is stored uncompressed which can lead to the creation of
many .pag files, causing low disk space.
The settings do not match the limits of the OS.
The Database (Index) is corrupted.


1 de 2 10/04/2018 12:20 p. m.
Document 946564.1

Note that Essbase needs at least as much free space for a calculation as the database is in size.
Therefore "low on disk space" may still mean that there are several Gigabytes of free space.

To resolve the problem:

1. Make sure that problematic application is completely stopped. (check process Manager/open Processes for ESSSVR processes).
2. Rename the file
3. Try to re-start the application.

If that is not successful, please try the following:

1. Stop all applications and stop the Essbase Service.

2. Check on the file system. Remove any temporary files that may be in the Essbase database directory.
Temporary files have the extensions .INN, .PAN, .OTN, .ESN, .TCU.
3. Replace dbname.db file with dbname.dbb file in the database directory.
4. Replace file with appname.apb file in the application directory.
5. Restart Essbase Service.
6. Try to load the application.

If the above does not work, then restore the specific application and its databases from a working backup. If you do not have a working
backup, restore by doing the following:

1. Delete these files:

2. Restart the database.
3. Clear the data in the database.

4. Reload from data or export files that you created before the corruption.

Run a validation after it is restored to ensure integrity.

Didn't find what you are looking for?

2 de 2 10/04/2018 12:20 p. m.