ORA-08006: specified row no longer exists " while compression

[former_member214274]

Hi All,

I am getting ORA-08006 error while compressing a cube.

This cube has active aggregates.

The messages are like below:

@5B@    Aggregation of InfoCube 100031 to request 2872   @35@

@5B@    statistic data written    @35@

@5B@    Zero elimination switched on    @35@

@5B@    Requirements check compelted: ok    @35@

@5B@    enqueue set: 100031    @35@

@5B@    compond index checked on table: /BIC/E100031    @35@

@5B@    enqueue released: 100031    @35@

@5C@    ORA-08006: specified row no longer exists    @35@

@5C@    ORA-08006: specified row no longer exists    @35@

@5B@    Collapse terminated: Data target CUBE01, from  to 2872    @35@

However, after repeating the step, the PC runs fine with no errors.

Let me know what can be done to remove this recurring error.

Thanks

[RamanKorrapati · Accepted solution]

Hi,

This might be db backend issue.

please check with your DB/oracle team.

Error belongs to oracle.

Try to activate your target and later try to compress data.

Thanks

[former_member214274 · Accepted solution]

Hi Raman,

Yes, it is a db backend issue, but why only for this cube and aggregate?

Activating target is too risky as it is one of the SLA cubes and may need to take approval for that.

[colm_boyle]

Hi Akanksha,

in a previous instance of this error in an SAP customer incident I saw the following text... Please run it by your BASIS guys...

"Indeed, this '08006' referenced code is a SQLState error code which

correspond to a connection failure. This mean that for some reason

the connection to the database has been lost and make the current SQL

query to fail."

and further down...

"Thus, could you please check if something can make the network

to be slow down at this time? Please try to monitor your network,

firewall, database and so on to make sure there is nothing that can

cause a connection lost."

I hope this helps. Please also keep an eye out for ORA00600 which corresponds to a locking error, if the row was locked, which is common in Oracle, due to BITMAP Indexing, you will have to run your loads when there is no activity on the infoprovider in question.

This particular error is nto reported to SAP very often, I only found the one incident above, so the above reason may not be the cause. Anyway it's a start,

thanks,

Colm

[former_member214274]

Hi Colm,

Thanks for your reference found for SAP incident.

However, there is no network/firewall or database issue while the chain is running.

The variant collectively compresses 3-4 cubes and we get this error only for this one cube.

There is no locking issue also.

I suspect there is some problem with the cube aggregates.

Anyhow I have mailed our Basis team to look into the same.

[former_member186053]

Hi Akanksha,

Please give your BW version,support pack and oracle database details.

Try to see the dump log in ST22 and give the details.

Thanks,

Vengal.

[former_member214274]

Hi Vengal,

There are no dumps in the system while this error occurred.

SAP BW version is 7.0 with highest support pack as SAPKW70026.

The Database is Oracle with release 10.2.0.4.0.

Thanks