Unable to Activate DSO 0PY_PP_C1

[Former Member]

I seem to be unable to activate DSO 0PY_PP_C1 after I have uploaded data. I get an ABAP dump with the header DBIF_RSQL_SQL_ERROR. The ABAP Dump data in ST22 states "ORA-12801: error signaled in parallel query server P000#ORA-00018: maximum number of sessions exceeded".

Anybody got any ideas?

Thanks

[Former Member · Accepted solution]

This is a Table Space issue.

Check Transaction DB02> Performance>Locks wait and Deadlock Option. Here u will find the deadlock situation for this Activation Process,

OR

Check in St22 the tables of this ODS for which Activation is going on . In this ST22 u will get the table for which there is a space issue.

contact with ur Basis Team to increase the size of this table. once this is done it will allow u to activate.

Assign Points if this helps u.

Thanks,

Nagesh

Edited by: Nagesh Mule on Jan 28, 2008 3:04 PM

[Former Member · Accepted solution]

In DB02 under performace I dont have a Locks wait and Deadlock Option. I have wait event analysis and in that I have Lock Monitor. Is there any difference between versions as we are using BI7.

[Former Member · Accepted solution]

Hello!

No, the interface is different in appearance but functions in the same manner. If you are uncomfortable with the interface, you may use DB02OLD instead... This ought to bring you to the 3.5 version DB02.

Regards,

P.

[Former Member · Accepted solution]

You can even check in ST22.

Search for ur ODS table name, u will get in that dump. Read the whole content u will understand that it is because the size of the table is not sufficient hence it is not able to activate.

If this is confirmed by u...... no need to check in DB02.

Just inform this issue to ur Basis Team about the table space issue. they will resolve this.....

Assign points if this helps u......

Thanks,

Nagesh

[Former Member]

OSS Note 541538 should help you to fix this issue:

- ORA-00018: maximum number of sessions exceeded

With large-scale parallel processing, the SESSIONS limit may be reached and the error described above may occur. In this case, increase the SESSIONS parameter sufficiently.

Hope it helps,

Andreu

[Former Member]

How do you increase the sessions parameter?