cancel
Showing results for 
Search instead for 
Did you mean: 

Rollup fails with "SQL Error 12801"

anil_babu13
Participant
0 Kudos

Dear All,

One of our process chain is being failed regularly these days at rollup step, error message is as below.

SQL Error: 12801

Message no. DBMAN257

Diagnosis

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.

Procedure

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.

When we repeat the step in a min again, it gets successful.

Did anyone face these type issue ? if so can you please give us some hints on how to avoid such failures.

Rollup is being done for less number of records only (less than 10k) and rollup is for aggregates (not for BWA) and we are facing this issue after moving to cloud.

Thanks

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member600441
Participant
0 Kudos

Hi Anil,

Please go through below blog which explains how to resolve the issue.
https://blogs.sap.com/2011/02/27/bwdb-support-101-get-to-know-your-failing-sql-statement/

You might need to check with Basis team for right configuration. Verify the parallel job execution setting in RSBATCH t-code. Select relevant process in this case it should be Roll-up Process etc. and try to collect the trace log during job execution to troubleshoot the issue.

Use RSRV tcode - analysis and repair BW objects.

Hope following above step you will be able to resolve the issue.

Regards,
Pradeep Jaiswar