on 04-04-2011 10:04 AM
Hi,
In the process Chain, getting error "Dump: ABAP/4 processor: DBIF_RSQL_SQL_ERROR" on DTP execution.
I repair that for 2-3 times even also getting same error.
How it will be solve?
Regards,
Balaram
Edited by: Balaramtripathy on Apr 4, 2011 2:35 PM
HI,
This is due to the unavailability of space in the parameter for the shared memory or due to parallel processes. Check the details in ST22 and if it is due to space issue, check with the DB team.
Thanks,
Rajesh.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Thanks to all for valuable ans.
I had gone through DB02OLD, and find the table space PSAPTEMP used 0% only.
What should I do now?
Regards,
Balaram
Edited by: Balaramtripathy on Apr 5, 2011 2:22 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Have you tried to repeat the load by delering the index ?
In my last post I asked you that whether you are loading a cube or not...
Anyways, Select that table space and click on table and indexes..........check the tables ...if any PSA tables are there which has huge data....delete those PSA data...
Also check with some Basis people.....
Regards,
Debjani....
Hi,
ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP"
=> your tablesspace TEMP is to small.
How many GB you have definied for this tablespace?
How many data you want to process? Can you create packages?
Sven
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I m getting all theses in st22
Short text
SQL error in the database when accessing a table.
How to correct the error
Database error text........: "ORA-01652: unable to extend temp segment by 128
in tablespace PSAPTEMP"
Internal call code.........: "[RSQL/FTCH//BIC/B0000115000 ]"
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_SEMANTIC_PACKETIZER=CP" or "CL_RSODSO_SEMANTIC_PACKETIZER=CM002"
"FETCH_PACKAGE"
Information on where terminated
Termination occurred in the ABAP program "CL_RSODSO_SEMANTIC_PACKETIZER=CP" -
in "FETCH_PACKAGE".
The main program was "RSBATCH_EXECUTE_PROZESS ".
In the source code you have the termination point in line 79
of the (Include) program "CL_RSODSO_SEMANTIC_PACKETIZER=CM002".
The program "CL_RSODSO_SEMANTIC_PACKETIZER=CP" was started as a background job.
Job Name....... "BIDTPR_55801_1"
Job Initiator.. "BW_USER"
Job Number..... 13480200
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "FETCH_PACKAGE" "(METHOD)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "CL_RSODSO_SEMANTIC_PACKETIZER=CP "; its source
code begins in line
2 of the (Include program "CL_RSODSO_SEMANTIC_PACKETIZER=CM002 ".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi..
This is a deadlock issue..
If you are loading a cube....then drop the index and then repeat the load....once the load get completed then recreate the index....
Check the SAP Note :631668
If you are loading the ODS....then contact the Basis Team and ask them to recreate the bitmap index......
Regards,
Debjani.......
Hi
This can be a tablespace issue. Please check the tablespace available in DB02. or You can ask basis to check this. and can get more space allocated.
Once this is done, delete the failed DTP request from from target and repeat the DTP in process chain.
This should complete the job.
Hope it helps you.
Hi...
Are you loading a cube ? What is the full error ?
Is it a deadlock issue?
If the Exception is "CX_SY_OPEN_SQL_DB", then it is a deadlock issue..for that ....
If you are loading a cube..........then drop the index before loading...............then do the loading.........again recreate the index after loading....
If still the load is failing...then you may running out of spaces....then you have to increase the table space...for this contact some Basis person...
Regards,
Debjani....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please let us know the short dump which you get . It would display the line in which short dump is caused. Do analyse this dump with Basis team as well.
Regards
Venky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
DBIF_RSQL_SQL_ERROR is not the exact error message. read the complete short dump in ST22.
-> tablespace?
-> deadlock?
-> missing table?
-> missing field?
Sven
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.