DBIF_RSQL_SQL_ERROR with CX_SY_OPEN_SQL_DB exception

[Former Member]

Hi All,

I'm connecting to SAP system through procxy mechanism.

Some of the messages has struc in DM with SYSFAIL error status in SMQ2.

Can I restart the message in all the situations of SYSFAIL?

here this SYSFAIL with fiollowing description.

-

---

Termination occurred in the ABAP program "CL_PROXY_STYLESHEET_UTILS=====CP"

in "GET_TRANSFORMATION_VERSION".

The main program was "SAPMSSY1 ".

In the source code you have the termination point in line 4

of the (Include) program "CL_PROXY_STYLESHEET_UTILS=====CM006".

The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

procedure "GET_TRANSFORMATION_VERSION" "(METHOD)", but it was neither handle

locally nor declared

in the RAISING clause of its signature.

The procedure is in program "CL_PROXY_STYLESHEET_UTILS=====CP "; its source

code begins in line

1 of the (Include program "CL_PROXY_STYLESHEET_UTILS=====CM006 ".

-

---

Could any one suggesr how to overcome this problems in future?

Thanks,

srini

[aashish_sinha · Accepted solution]

hi Srini,

After smq2, go deep inside to the blocked queue, after double clicking all the way you will se the message as u see in sxmb moni, please check inside that wat is the error and then post it here.

And ya you can restart the SYSFAIL messages.

regards

Aashish Sinha

PS : reward points if helpful

[aashish_sinha · Accepted solution]

HI,

i guess u need to set the parameter abap\buffersize in instance profile

Check out these notes for your error.

Note 480710 - Profile parameters for table buffers,

Note 8778 - Overflow in the table, single record, and CUA buffers

Note 983566 - RZ10: Buffer size for ABAP programs in basic maintenance

regards

Aashish Sinha

PS : reward points if helpful

[GabrielSagaya]

The error shows that there might be a table space problem in your database.

Please consult your basis administrator to increase the table space.

Also please post further details of the error.

[Former Member]

Hi Selvam,

Requested Basis administrator , he is given following analysis but how can I avoid this situation in future.

Issue was the result of a database lock time-out (3600 Seconds - 1 hour). Root cause a contention issue with another application / batch, etc.......

At the DB level we set this time-out to ensure one application/agent cannot wait indefinitely to access the database object.

Thanks,

srini

[aashish_sinha]

Hi,

u need to set the parameter abap\buffersize in instance profile.

Regards

Aashish Sinha

PS : reward points if helpful