Skip to Content
0
Former Member
Dec 05, 2006 at 05:52 AM

ODS Acitvation Problem..

43 Views

Hi Experts:

Following is the ABAP dump, while ODS data activation error in BI 7.0...Please help.

Runtime Errors DBIF_RSQL_SQL_ERROR

Except. CX_SY_OPEN_SQL_DB

Date and Time 04.12.2006 22:02:29

Short text

SQL error in the database when accessing a table.

What can you do?

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

How to correct the error

Database error text........: "ORA-12801: error signaled in parallel query

server P007#ORA-00018: maximum number of sessions exceeded"

Internal call code.........: "[RSQL/FTCH//BIC/AZFIGLO1040 ]"

Please check the entries in the system log (Transaction SM21).

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"

"CL_RSODSO_ACTIVATE_REQUESTS===CP" or "CL_RSODSO_ACTIVATE_REQUESTS===CM00D"

"ACTIVATE_DATA_FROM_QUEUE"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

The exception must either be prevented, caught within proedure

"ACTIVATE_DATA_FROM_QUEUE" "(METHOD)", or its possible occurrence must be

declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

Thanks,

RR