Error during extraction through InfoSource: 0CO_OM_OPA_1

[Former Member]

Currently we are extracting the data from SAP R/3 System into BW System through InfoSource 0CO_OM_OPA_1 (Orders: Costs and allocations)which is a part of the process chain. But we are getting the error as follows:

-

---

Idocs missing: No selection information arrived from the source s

Diagnosis

Background processing has not been completed in the source system. A short dump has most probably been logged in the source system.

System response

No selection information arrived from the source s

Procedure

Look for the short dump belonging to your data request in the short dump overview in the source system. Be sure of the correct date and time in the selection screen.

You can get the short dump list using the Wizard or from the monitor detail screen via the path "Environment -> Short dump -> Source system".

-

---

We have also checked the short dump in R/3 Production System, we are geeting following error details:

Runtime Error DBIF_RSQL_SQL_ERROR

Exception CX_SY_OPEN_SQL_DB

An SQL error occurred when accessing a table.

-

---

Error analysis

-

---

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was

neither

caught nor passed along using a RAISING clause, in the procedure

"REOM_OM_READ_COSP_DATA" "(FUNCTION)"

.

Since the caller of the procedure could not have expected this exception

to occur, the running program was terminated.

The reason for the exception is:

-

---

How to correct the error

-

---

The exception must either be prevented, caught within the procedure

"REOM_OM_READ_COSP_DATA"

"(FUNCTION)", or declared in the procedure's RAISING clause.

To prevent the exception, note the following:

Database error text........: "ORA-01652: unable to extend temp segment by 2560

in tablespace PSAPTEMP"

Internal call code.........: "[RSQL/FTCH/COSP ]"

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

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

-

---

"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC

"SAPLREOM " or "LREOMU08 "

"REOM_OM_READ_COSP_DATA"

-

---

After this we have also extend temp segment by 2560

in tablespace PSAPTEMP" and after that we have loaded the data manually but we are getting same eror, how to solve this problem. So, please help us to slove this problem.

RAJESH GIRIBUWA

[Former Member]

Hi Rajesh,

This is PSA table space issue. Due to lack of space in PSA while extracting the data from SAP ECC side the above error will occur.

Go to DB02 -> Table Spaces-> Current Sizes-> check table space 'PSAPBWP' -> Used(%).

If Used(%) > 98 then clean up the PSA table space before go for SAP extraction.

To clean up table space, Create a process chain with a variant for delete PSA requests and include all PSA requests then choose the period from 'Older than' radio button and schedule.

Always run this process chain if table space exceeds 98%.

Hope your question has been answered.

**Award points if you satisfy with this solution**

Thanks,

Prabhakar

[Former Member]

Hi Rajesh,

Just increase the Table space for PSAPTEMP. Inform your basis about this. You can see the size of the table space in DB02.

Hope this helps.

Cheers!

Bhuvana.

[Former Member]

Look for the Change Log DATA and PSA DATA . you may delete the unwanted PSA Data and the Change Log DATA to increase the Table Space . That will resolve the issue of the DBIF SQL error

[Former Member]

Hi,

it seems that was a lack of space table problem.

This DBIF_RSQL_SQL_ERROR comes due to lack of table space .. If you package didn't finish yet, please execute ST22 and SM21 and look for errors and dumps.

U can catch the error in ur program. this error occurs whenever database access exceeds some limit & the error is fired.

This should point you to the DB issue... frequently a table space issue.

Also take a look on the note :590370

check oss note

840552

Symptom

On BW tables that belong to an InfoCube, statistics are calculated (COMPUTE) instead of estimated with the set percentage (ESTIMATE). This results in high runtimes.

Other terms

InfoCube, database, Oracle statistics

Reason and Prerequisites

In the Oracle-specific RSDU_ANALYZE_TABLE_ORA BW function, in some situations an estimation is made as to how many records are in the table to be analyzed. A SELECT in the USER_TABLES table is specifically used for this. If there is no value there now, 0 is returned and a COMPUTE is carried out. COMPUTE is considerably fasterer than ESTIMATE on small tables (under 10000 approximately).

However, if the table is too big and if the statistics were deleted by a brconnect run that ran shortly beforehand, the above situation of long runtimes mentioned above can occur.

Solution

BW 3.0B

Import Support Package 27 or 3.0B (BW3.0B Patch 27 or SAPKW30B27) into your BW system. The Support Package will become available oncenote 723258 with the short text, "SAPBWNews BW3.0B Support Package 27", which describes this Support Package in more detail, is released for customers.

BW 3.10 Content

Import Support Package 21 for 3.10 (BW3.10 Patch 21 or SAPKW31021 ) into your BW system. The Support Package will become available once <Z1>note 723263 with the short text, "SAPBWNews BW3.1 Content SP 21", which describes this Support Package in more detail, is released for customers.

BW 3.50

Import Support Package 13 for 3.5 (BW3.50 Patch 13 or SAPKW35013) into your BW system. The Support Package will become available oncenote 783254 with the short text, "SAPBWNews BW SP12 NetWeaver'04 Stack 13", which describes this Support Package in more detail, is released for customers.

In urgent cases, you can use the correction instructions.

To provide information in advance, the notes mentioned may already be made available before the Support Packages are released. However, the short text in this case will still contain the words "Preliminary version".

/message/1599520#1599520 [original link is broken]

-Shreya

[Former Member]

Hi Rajesh,

Please co-ordinate with BASIS person in your team.

Also, provide him with the OSS note that I gave you and suggest him to import the support package 21 for 3.10(bw 3.10 patch 21).

The BASIS person will be aware of what needs to be done in this regard. It will be nice if you give these informations to him.

Hope this helps...

Thanks,

Raj

[Former Member]

Hi Rajesh,

try to speak to your Basis / database guy it is the problem related to table space most probably table space mentioend below -

<b>unable to extend temp segment by 2560 in tablespace PSAPTEMP</b>

hope it helps

regards

Vikash

[Former Member]

Hi rajesh,

This is basically a tablespace issue.

pls check for OSS notes: 840552

You might need to import support package depending on your version .

Please let me know the version you are using, I shall try to let you know about the support package.

Thanks,

Raj

[Former Member]

Dear Raj,

The Sytem status is as follows:

S/W Comp Rele Level High Supp Description

-

---

SAP_BASIS 620 0044 SAPKB62044 SAP Basis Component

SAP_ABA 620 0044 SAPKA62044 Cross-Application Component

SAP_BW 310 0018 SAPKW31018 Business Information Warehouse

PI_BASIS 2003_1_620 0006 SAPKIPYH56 PI_BASIS 2003_1_620 : Add-On Delta Upgra

BI_CONT 330 0000 - Business Intelligence Content

ST-A/PI 01E_BCO 620 0000 - Servicetools for other App./Basis 620

ST-PI 003C_620 0002 SAPKITLPR2 SAP Solution Tools Plug-In

Please tell which support package we should install.

Kind regards

RAJESH GIRIBUWA

[Former Member]

Hi Rajesh,

Try to extract data in smaller parts by giving selection conditions in your infopackage.

Bye

Dinesh