Skip to Content
Jun 26, 2012 at 10:28 AM

Getting error-SQL Error: ORA-01089: immediate shutdown in progress - no operations are permitted while index genetation of a cube


Recently we had upgraded our BW system from 7.0 to 7.3 and converted the 3.x flow in 7.0 flow. After that we are getting Dump daily During Index Generation for one Process chain but when we manually repeat that(In process chain itself) in morning its works fine. For other every thing is working fine.

Please help to resolve this issue

System Detail

SAP Release..... 730

SAP Basis Level. 0007

Operating system..... "AIX"

Release.............. "6.1"

Database type..... "ORACLE"


ERROR Statement


SQL Error: ORA-01089: immediate shutdown in progress - no ope rations are permitted

Message no. DBMAN257


The database system registered an SQL error. As available, the error number and a description are included in the short text. Possible causes for SQL

errors include:

1. Overflow of database objects such as buffers, temporary tablespaces, rollback segments or data containers/tablespaces.

->These problems can generally be eliminated by system administrators.

2. Missing generated database objects such as tables or views based on inconsistent or inactive InfoCubes or InfoObjects. Examples of this include the

view of the fact table for an InfoCube or the attribute SID table (X/Y table) of a characteristic.

-> These problems can generally be eliminated by a BW administrator.

3. SQL requests with incorrect content.

-> Problems of this type are generally programming errors.


Contact your system administrator.

Procedure for System Administration

If there is no error description, look for one in the reference from the database producer.

Decide on the correct category for the SQL error and check if it can be eliminated. Generally the error can also be found in the syslog (transaction sm21).

From there, transactions sm51 and sm50, the developer's trace log of the work process can be determined and the erroneous statement can be viewed

in the log. This procedure is described in SAP Note 568768.



Error .jpg (221.1 kB)