When i'm trying to delete the DSO Request i'm getting this error msg "SQL error in the database when accessing a table" Actually my DSO Having more than 28 lacs recrods.how to slove this error???
Deleting the corresponding line from table RSICCONT just removed the BW internal reference to it.
Now, BW cannot handle this request any more.
A way better solution would have been to post the actual SQL error you got.
Given the current information in this thread, there is no way to tell, what went wrong and why.
I'm really surprised to see that we find recommendations in this forum based on ... nothing. No error number, no clear identified cause of the issue. And still you move on and delete some data in your system...
To come out of this situation now, you may either check if you can get rid of the data via SQL (totally unsupported of course!) or you simply drop and rebuild the whole DSO.
Actually i'm having more than 28 lacs recrods in ecc 2lis_13_vdkon data Source.i deleted the DTP and recreated and when i execute the DTP i got following Error msg
"The database returned a value containing an error"
Message no. RS_EXCEPTION000
And also i have checked DB04 it shows 3 errors and warnings
Warnings:::
1. TABLESPACE_FULL:Tablespace: PSAPSR3, value: 100.00% (> 95%) # Tablespace fulL
2.LOG_BUFFER::::Value: 14489600 (>< 4096,512 KB) # Size of redo log buffer in bytes
3.OPTIMIZER_INDEX_COST_ADJ :::Value: 20 (set in parameter file) # Optimizer index cost adjustement
Errors:
1.MISSING_STATISTICS:::Table: SAPSR3./BIC/B0000479000 # Table or index has no optimIZER STATISTICS
2.01653:::::Time: 2011-08-29 13.00.08, line: ORA-1653: unable to extend table SAPSR3.BALDAT by 128 in tablespace PSAPSR3
Time: 2011-08-29 13.00.08, line: ORA-1653: unable to extend table SAPSR3.BALDAT by 128 in tablespace PSAPSR3
3.01688::::::Time: 2011-08-26 17.16.15, line: ORA-1688: unable to extend table SAPSR3./BIC/B0000197000 partition /BIC/B00001970000000000002 b
Time: 2011-08-26 17.16.15, line: ORA-1688: unable to extend table SAPSR3./BIC/B0000197000 partition /BIC/B00001970000000000002 b
> Actually i'm having more than 28 lacs recrods in ecc 2lis_13_vdkon data Source.i deleted the DTP and recreated and when i execute the DTP i got following Error msg
> "The database returned a value containing an error"
> Message no. RS_EXCEPTION000
Hi again,
ok, if you get these kinds of error, you should always check the system log (transaction SM21) and if necessary also the workprocess developer trace file (ST11) to get more detailed information about the error.
> And also i have checked DB04 it shows 3 errors and warnings
> 2.LOG_BUFFER::::Value: 14489600 (>< 4096,512 KB) # Size of redo log buffer in bytes
> 3.OPTIMIZER_INDEX_COST_ADJ :::Value: 20 (set in parameter file) # Optimizer index cost adjustement
These warnings are something completely different.
They are the result of a regularly performed database system health check (db_check function of brconnect).
This check just compares the IS situation against a defined set of SHOULD BE rules and prints out warnings if they don't match.
For example the warning about the parameters LOG_BUFFER and OPTIMIZER_INDEX_COST_ADJ are not valid for your BW on Oracle 10g!
Make sure to read and work through notes
483856 Description of the alerts for Oracle database monitoring
435290 Description of BRCONNECT 6.10 DB check conditions
403704 BRCONNECT - Enhanced functions for Oracle DBA (<< this note also contains scripts to reset the check conditions to the SAP defaults for the current database releases).
to get the warnings correct and to understand them properly.
> Errors:
> 1.MISSING_STATISTICS:::Table: SAPSR3./BIC/B0000479000 # Table or index has no optimIZER STATISTICS
This may be a temporary effect, e.g. when the table/partition had just been created and statistics had not yet been collected.
Should this reoccur for the same table in the next run of the DBCHECK this might be worth to follow up.
> 2.01653:::::Time: 2011-08-29 13.00.08, line: ORA-1653: unable to extend table SAPSR3.BALDAT by 128 in tablespace PSAPSR3
> Time: 2011-08-29 13.00.08, line: ORA-1653: unable to extend table SAPSR3.BALDAT by 128 in tablespace PSAPSR3
>
> 3.01688::::::Time: 2011-08-26 17.16.15, line: ORA-1688: unable to extend table SAPSR3./BIC/B0000197000 partition /BIC/B00001970000000000002 b
> Time: 2011-08-26 17.16.15, line: ORA-1688: unable to extend table SAPSR3./BIC/B0000197000 partition /BIC/B00001970000000000002 b
Now, these are the actual problems: the storage space in tablespace PSAPSR3 has run out.
You need to either add some space or release/free up some storage in this tablespace.
If I'd were in your place I would especially check, why table BALDAT (application log) got so big and try to get it smaller again.
See notes
1616768 BALDAT and BALHDR application log tables are very large
195157 Application log: Deletion of logs
706478 Preventing Basis tables from increasing considerably on this.
If you now say: wait a minute! this is a BW question but you keep referring me to BASIS notes, then it's because, this really is a BASIS issue. The database storage has completely been allocated and new storage requests are currently denied.
It may due to database extents reached upto maximum allotted size. Try to extend further. once the space for the extents allocated your problem will be solved I guess.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.