Missing indexses in DB02

Hi ,
    When i am monitoring the system thru DB02 i m getting missing secondary indexses.....can anyone tell me why they actually come? how severe can they for the system? how can i adjust them?
The name of the indexes are
/BIC/FITC_MDP-020
/BIC/FITC_MDP-030
/BIC/FITC_MDP-040
/BIC/FITC_MDP-050
/BIC/FITC_MDP-060
/BIC/FITC_MDP-070
and as a matter of fact i have run abap report
SAP_INFOCUBE_INDEXES_REPAIR
though running it has repaired some indexes but not the one i want.plz suggest
siddharth
regards
Message was edited by:
        Siddharth Sharma

Hello Siddharth,
First, you have to check and search for the index already exists or not :
Through OS level :-
(sqlplus under sapr3 user)
select index_name, owner, num_rows from dba_indexes
where index_name = '          ' ;
you can rather ALTER or REBUILD it using
alter index sapr3." ~0" rebuild ;
Regards,
Jafer

Similar Messages

  • Missing indexes in db02

    Hello,
    Checking DB02 i've found a list of missing primary indexes. I know that i can use SE14 to adjust the indexes but i found some decumentation that says that i should first check if double index for the primary index exist and elimenate them.
    Please Advice.
    David.

    hi David,
    oss note 157918
    BW: DB02 shows "missing indexes"  
    Symptom
    DB02 shows indexes of a fact table to be missing. Such indexes have names that start with prefixes /BI0/F or /BIC/F (BW 1.2, BW 2.x) or /BI0/E or /BIC/E (BW 2.x only).
    Additional key words
    Business Information Warehouse, InfoCube, Fact Table, Bitmap Indexes, Oracle, DB02, Unique Index
    Cause and prerequisites
    For BW 1.2, this only applies to Oracle-based systems. For BW 2.x, this might apply to any DB-platform.
    BW 1.2 and BW 2.x take advantage of certain DB-specific features which are not supported by the data dictionary of R/3 4.0, 4.5 or 4.6 base systems. Prominent examples are bitmap indexes on fact tables (Oracle-based BW systems), partitioned/fragmented indexes, nologging and parallel index building facilities etc. Such features are used in BW by triggering native SQL statements which bypass the data dictionary.
    While all these features improve performance of the BW system, there are, however, some other transactions that are also affected when the data dictionary is bypassed. Amongst these is DB02. It sometimes claims that certain indexes of infocube fact tables are missing while direct checks on the database level show that those indexes are not missing at all or substituted by equivalent indexes. The latter might happen in BW 2.x where the primary index on fact tables might be replaced by a non-unique index or simply skipped as it is not required. Therefore you can usually ignore those messages. Obviously, we are currently working on removing such inconsistent information. If you want to be sure on the indexing then check the solution section of this note.
    Solution
    For BW 1.2A systems (Oracle only):
    You have to ask your local DBA to check the state of the indexes directly by looking at the USER_INDEXES table on the Oracle database.
    For BW 1.2B systems (Oracle only):
    There are two alternatives to check the secondary indexes of infocube and aggregate cubes fact tables:
               (1) Go to the Admin Workbench. Go to the infocube. Click the right mouse button and choose "InfoCube Performance". This leads you to a screen that shows the state of those indexes via traffic light semantics. There are also buttons to repair inconsitent states of the indexes.
               (2) Use transaction RSRV. Go to the tabstrip "Database". Choose the item "Indices of an InfoCube and its aggregates" and insert the (technical) infocube name (e.g. 0BWTC_C01) in the input box at the bottom of the screen. Press F8 ("Analysis") and wait until a red, yellow or green light appears beside "Indices of an InfoCube and its aggregates", i.e. in the "Result" column. Then press F6 ("Results") in order to see a detailed report on the index situation of that cube.
               (3) Go to SE37 and do a "single test" for the function module RSDU_CHECK_SECONDARY_INDEXES. Use the infocube's technical name (e.g. 0BWTC_C01) as the input parameter and 'X' for both, the I_COMPLETE_CHECK and I_WITH_AGGREGATES, parameters. Press F8 to run the module. Only the C_T_INDEX output parameter is relevant. It shows a list of indexes. Check the TYPE and STATUS columns. These should show 'BITMAP' and 'VALID' respectively.
    For BW 2.0A systems (all DB-platforms):
    For checking secondary indexes on individual infocubes the following methods can be applied, similar to the BW 1.2B solution:
               (1) Go to the Admin Workbench. Go to the infocube. Click the right mouse button and choose "Manage". Choose the tabstrip "Performance". This leads you to a screen that shows the state of those indexes via traffic light semantics. There are also buttons to repair inconsitent states of the (secondary) indexes.
               (2) same as (2) for BW 1.2B.
               (3) Go to SE37 and do a "single test" for the function module RSDU_INFOCUBE_INDEXES_CHECK. Use the infocube's technical name (e.g. 0BWTC_C01) as the input parameter, leave the I_FACTTAB initial, use 'X' for both, the I_COMPLETE_CHECK and I_WITH_AGGREGATES, parameters and use 'U' in the I_DOUBLE_FACTTAB parameter. Press F8 to run the module. Only the C_T_INDEX output parameter is relevant. It shows a list of indexes. Check the TYPE_CHECK, UNIQUE_CHECK, PARTITIONED_CHECK and STATUS_CHECK columns. These should show 'G' (= "green" = ok) respectively.
    If your BW 2.0A system is on patch level 11 Make DB02 consistent by running the report SAP_UPDATE_DBDIFF (via SE38), go to DB02 and press the "Refresh" button in order to synchronise the information in DB02 with the DBDIFF table. This should provide you with a consistent view.
    For BW 2.0B and BW 2.1C systems (all DB-platforms):
    DB02 should work consistently in BW 2.0B / BW 2.1C  with infocubes created in 2.0B / BW 2.1C. If you wish, you can still use the BW 2.0A approach. For infocubes that were created in BW 2.0A or BW 1.2 you need to adjust the index setup (on the facttables) by running the report SAP_INFOCUBE_INDEXES_REPAIR. The latter is available from BW 2.0B patch 3 onwards. It should be run in a background process as it might take a while to run through.
    You also might want to run the report SAP_UPDATE_DBDIFF once in order to update the table DBDIFF that lists database objects whose data dictionary setting do not correspond to the actual setup and that should therefore be omitted in DB02 checks.
    Source code corrections

  • Missing Index in DB02

    Hi,
    When I go to DB02->Diagnostics->Missing Tables and Indexes in our ECC6 system.
    I see some missing primary and secondry indexes there.I also see option " Create on Db" there.
    Please suggest should I create such indexes by option "Create in Db" and also suggest how SAP find out such missing indexes in Database,,, Does CheckkDB or Update stats provide this information to SAP.
    Please confirm.
    Regards,
    Shivam

    >
    Shivam Mittal wrote:
    > Hi,
    >
    > When I go to DB02->Diagnostics->Missing Tables and Indexes in our ECC6 system.
    >
    > I see some missing primary and secondry indexes there.I also see option " Create on Db" there.
    >
    > Please suggest should I create such indexes by option "Create in Db" and also suggest how SAP find out such missing indexes in Database,,, Does CheckkDB or Update stats provide this information to SAP.
    >
    > Please confirm.
    >
    > Regards,
    >
    > Shivam
    Yes you can create them on DB.
    SAP doesnt find out that information until and unless then login into ur system through saprouter.
    Regards,
    Nirmal.K

  • Missing tables in DB02

    Hi Gurus,
    In DB02 / Diagnostics displays that following tables are missing:
    - ORA_COCKPIT_HELPER
    - SFHOT
    - T77TNM_IFPROPS
    - YINFTOOL
    I found some sap notes how to solve the issue, but was not able to.
    1. What are these tables.
    2. Do I need them, if NOT which tables can be deleted, and how exactly
    3. Required tables ho can I create them
    Pl. give exact instructions
    - ZZCON_TEMP            (Tried to delete in SE14 / SE11) could not delete.
    Pl. advse how to solve the issue, thanks for your help in advance.
    sahmad

    Transaction DB02 reports a data inconsistency between the database and the ABAP Dictionary:
    1) ORA_COCKPIT_HELPER: Read note Note 1374746 - DBA Cockpit: Temporary table ORA_COCKPIT_HELPER it says how to create the missing table ORA_COCKPIT_HELPER
    Goto your SQL prompt and the commmand as per note
    SQL>create global temporary table ora_cockpit_helper as
        select * from ( <p_sql_stmt_text> ) where 1=0
    It was just not get created for SAP dictionary. Simple create it....
    2) SFHOT: is defined in the ABAP Dictionary as a cluster table and was accidentally created in the database in a previous release. Check that the table is correctly defined in R/3.  To do this, you can activate the table in transaction SE11. If this can be done without any errors, the table can be deleted from the database. Use database tools to do this. Read how to go for it from SAPnote :33814
    3)T77TNM_IFPROPS: The customizing table T77TNM_IFPROPS only exists in release 4.70 as stated in note 1130425; hence during an upgrade from this release, you might notice that the table and the runtime objects exist without the DDIC reference. Follow as "Note 1396592 - Table T77TNM_IFPROPS - Upgrade discrepancies" says ...
    No idea about your fourth table....
    all the best !

  • Can not create missing index

    Dear all,
    This is about a  BW 3.5 system running Oracle 10.2.0.2 on Solaris 10
    After an online database reorganisation, I receive these messages in db13
    BR0970W Database administration alert - level: ERROR, type: MISSING_INDEX, object: (table) SAPR3./BI0/F0BWTC_C02
    BR0970W Database administration alert - level: ERROR, type: MISSING_INDEX, object: (table) SAPR3./BI0/F0BWTC_C05
    According to the logs, the tables above have been reorganised successfully.
    I see the missing indexes in db02 under Missing Indexes:
    Secondary indexes               13 
        /BI0/F0BWTC_C02-070            
        /BI0/F0BWTC_C02-060            
        /BI0/F0BWTC_C02-050            
        /BI0/F0BWTC_C02-040            
        /BI0/F0BWTC_C02-020            
        /BI0/F0BWTC_C02-010            
        /BI0/F0BWTC_C05-070            
        /BI0/F0BWTC_C05-060            
        /BI0/F0BWTC_C05-050            
        /BI0/F0BWTC_C05-040            
        /BI0/F0BWTC_C05-020            
        /BI0/F0BWTC_C05-010            
        /BIC/FZ_CPLN_00-900            
    If I try to select one and click on create in db, I get a short dump
    Runtime Error          RAISE_EXCEPTION                                                
    Date and Time          23.08.2007 11:12:13                                                                               
    ShrtText                                                                               
    Exception condition "STORAGE_NOT_DETERMINATED" raised.                                                                               
    What happened?                                                                       
         The current ABAP/4 program encountered an unexpected                             
         situation.                                                                               
    What can you do?                                                                     
         Print out the error message (using the "Print" function)                         
         and make a note of the actions and input that caused the                         
         error.                                                                               
    To resolve the problem, contact your SAP system administrator.                   
         You can use transaction ST22 (ABAP Dump Analysis) to view and administer         
          termination messages, especially those beyond their normal deletion             
         date.                                                                               
    is especially useful if you want to keep a particular message.                                                                               
    Error analysis                                                                       
         A RAISE statement in the program "SAPLSDB2" raised the exception                 
         condition "STORAGE_NOT_DETERMINATED".                                            
         Since the exception was not intercepted by a superior program                    
         in the hierarchy, processing was terminated.                                                                               
    173   else.                                                                      
    174      storage_source_hierarchy-dbr = 'X'.                                     
    175   endif.                                                                     
    176   storage_source_hierarchy-cmt = 'X'.                                        
    177   storage_source_hierarchy-cmp = 'X'.                                        
    178   if dbtabname ne space and dbtabname ne tabname.                            
    179     perform shdupg_get_index_storage tables storpar                          
    180             using dbsys prid tabname indexname storage_source_hierarchy      
    181                   dbindex_of_origtable dbprimindex_of_origtable              
    182             changing rc.                                                     
    183   else.                                                                      
    184     call function 'DB_STORAGE_GET'                                           
    185          exporting                                                           
    186               dbsys                = dbsys                                   
    187               prid                 = prid                                    
    188               tabname              = tabname                                 
    189               indexname            = indexname                               
    190               dbindex              = realname                                
    191               dbrefindex           = name_of_primidx                         
    192               source_hierarchy     = storage_source_hierarchy                
    193          tables                                                              
    194               storpar              = storpar                                 
    195          exceptions                                                          
    196               mapping_error        = 1                                       
    197               db_error             = 2                                       
    198               uncomplete_parameter = 3                                       
    199               others               = 4.                                      
    200     rc = sy-subrc.                                                           
    201   endif.                                                                     
    202   if rc ne 0.                                                                
    >>>>     raise storage_not_determinated.                                          
    204   endif.                                                                
    205                                                                         
    206 * Progamm generieren                                                    
    207   perform db_get_progname using 'SDB2F' dbsys changing sdb2fdbs.        
    208   refresh statements.                                                   
    209   perform gen_create_index in program (sdb2fdbs)                        
    210           tables ddfldnames storpar loc_stmt                            
    211           using  tabname indexname realname unique dbsys rc.            
    212   if rc <> 0.                                                           
    213 *KUGL-protocol-270694                                                   
    214     perform stdo_sam1                                                   
    215        using prid max_severity msgid '122' realname.                    
    216     raise program_not_generated.                                        
    217   endif.                                                                
    218   statements[] = loc_stmt[].                                            
    219                                                                         
    220   perform create_index_finish tables loc_stmt                           
    221                           using  tabname realname dbsys no_exec  rc.    
    222  if rc <> 0. raise program_not_generated. endif.                        
    Any ideas?
    Many thanks
    Andreas

    Hi,
    Please check following note:
    Note 703304.
    You may have to import correction against your release.
    Regards,
    Payal Patel

  • Missing index problem

    Hi Gurus!
    I have a critical problem to solve.
    I have a table without data which is inconsistent because it doesn't have the primary index. When i see missing indexes at DB02, the system tells me that the index is created, but when i go to SE14 and select the primary index, it says the index does not exists on the database and the only option that is active is the one to create the index. If I try to create the index, i get an error saying: there is already a  an object named 'zmed_distr~0' ( my index name ).
    Can anybody help me?
    Thank you in advance.

    the tsystem does'nt create the index and give me this log:
    Request: Create Index ZMED_DISTR-0 (FORM05/11.12.07/19:06)                                                                        
    Process: BLADE04_0                                                                               
    sql:                                                                               
    ALTER TABLE [ZMED_DISTR]                                                                               
    ADD CONSTRAINT [ZMED_DISTR~0]                                                                               
    PRIMARY KEY CLUSTERED                                                                               
    ( [MANDT] ,                                                                               
    [ZUONR] ,                                                                               
    [GJAHR] ,                                                                               
    [KUNNR] ,                                                                               
    [ESTAB] ,                                                                               
    [TXT20] ,                                                                               
    [REPS] )                                                                               
    There is already an object named 'ZMED_DISTR~0' in the database.Could                                                             
    not create constraint. See previous errors.                                                                               
    DDL time(___1): .........3 milliseconds                                                                               
    The SQL statement was not executed                                                                               
    Index   could not be created completely in the database                                                                           
    Index ZMED_DISTR-0 could not be created                                                                               
    Request for ZMED_DISTR could not be executed

  • Reoccuring missing secondary indexes in BI systems

    Hi Gurus,
    I'm been experiencing the problem of missing secondary indexes for some time, and I would like to get to the bottom of this problem.
    These are a few of the missing indexes (from DB02):-
    /BIC/F100294-900
    /BIC/F100365-900
    /BIC/F100366-900
    /BIC/F100368-900
    /BIC/F100369-900
    /BIC/F100386-900
    /BIC/FZCFIGRLP-900
    /BIC/FZCGLECRD-900
    /BIC/FZCGLECRD2-900
    /BIC/FZCGLECRD3-900
    TSP03-1
    TSP03L-A
    Any idea what could be causing this???
    And how do I solve this problem??? And how can I prevent these from reoccuring again???
    Thanks.
    Cheers,
    KeatSeong

    I see missing indexes on DB02 as well and ran SAP_INFOCUBE_INDEXES_REPAIR and I just have a couple more questions that I think is relevant to this chain:
    1) It repaired some fact indexes like /BIC/F* and dimension indexes like /BIC/D* but in the report showed as follows for those cubes:
    0  ZPP_C008     :          0  secondary indexes repaired.
    2) I had some other dimension indexes like /BIC/D* that did not get repaired and I'm wondering why. See 4) below for how I repaired those.
    3) I ran RSRV and these missing indexes like /BIC/D* do not show up as being an issue
    4) When I run RSDU_INFOCUBE_INDEXES_REPAIR on that missing index like /BIC/D* I get E_REPAIRED = 0 and system error: RSDU_INFOCUBE_INDEXES_REPA_ORA but when I refresh DB02 the index is gone. When I go to RSDU_INFOCUBE_INDEXES_REPA_ORA and run it I got e_reparied - 11
    Thanks for all your help.
    Mike
    Edited by: Michael Hill on May 26, 2010 6:49 PM

  • Problem about Indexes missing in the database

    Dear all,
    We found a missing index in DB02 view of our sap system.
    This missing index is a Secondary index,
    and its name is S509-VAB.
    We tried to create it in DB, but got below error log as below:
    Index S509~VAB could not be set up in the database
    Message no. DI 006
    Diagnosis
    It was not possible to create the index in the database.
    This could be caused by the fact that an index with the same name exists in the database, but it is unknown to the ABAP/4 Dictionary. Activating the index in the ABAP/4 Dictionary is possible, but it is not possible to create it in the database.
    Procedure
    For more information about the cause of the error, analyze the SQL error messages in this log.
    Our question is How to Activate the index in the ABAP/4 Dictionary?
    Anyone experienced,
    Please kindly give advice.
    Regards,
    Allen

    Hi Allen,
    S509 is an information structure table. Data is populated into it post we do some necessary cutomizing and is mainly used for reporting purpose. I do not know what reports you are generating out of this. Hence difficult to say whether you can ignore this missing index or not.
    I would suggest you to do the following
    In se14, type the table name S509.
    Go to indexes tab. Look for the list of indexes defined.
    Select the index name VAB ( Which is missing in your case ).
    1) check the status of this index ? Does it says "exists in database"
    2) If point 1 is not valid then , select the option create in database button and create the index in the database.
    Regards,
    Deepak Kori

  • Missing Index for /BI0/A*

    My system has missing Indexes for
    /BI0/ABP_ID40-0
    /BI0/ABP_REL40-0
    /BI0/AFORM_DS140-0
    /BI0/AGN_CONV40-0
    /BI0/APERS_BOD40-0
    /BI0/APERS_VAR40-0
    /BI0/APERS_WTE40-0
    /BI0/ATCA_DS0140-0
    /BI0/ATCA_DS0240-0
    /BI0/ATCA_DS0340-0
    /BI0/ATCA_DS0440-0
    /BI0/ATCA_DS0540-0
    /BIC/AEFIO99AT40-0
    I ran a a program SAP_INFOCUBE_INDEXES_REPAIR which fixed my secondary Indexes. But the primary indexes doesn't work.
    What can I do to resolve this issue
    Regards
    Naziem Mahomed

    Hi,
    these looks like active tables of ODS/DSOs...
    You position you cursor on the missing object in DB02 and hit the create in DB button; better choose in background.
    Note that they will remain showing missing in DB02 until statistics are refreshed...
    After the background jobs are completed hit the dsplay definition button; you will be lead to the SE14 screen for this IDX; it should say that the index exists in the DB;
    Tomorrow your DB02 screen should be updated...
    hope this helps...
    Olivier.

  • ST04 and DB02

    Hi
    I am learning SAP BASIS
    I am not understanding, what  can i monitor in Transaction ST02 and DB02, and If any problem observed in these transactions, What is the solution?
    Plz kindly give me the solution

    In the intial screen of ST02 we can monitor Roll area, Paging area , extended memory and Heap memory.
    The roll area is a memory area with a set (configurable) size that belongs to a work process. It is located in the heap of the virtual address space of the work process.
    Extended memory is the mail part of memory management system.You can assign the extended memory from a common space to any work process.(We commonly do it when we work with pointers in ABAP).
    If a dialog work process has used up the roll area assigned to it and the extended memory, private memory is assigned to the work process. The work process goes into PRIV mode (private).
    Missing indexes may occur if you ignore an error message when creating a table or if an index is deleted.You can find the missing indexes in DB02 just by clicking on the missing index area.

  • How do I a full database impoert?

    Could somebody help me?
    I have a database (OraEE 8.1.6 WinNT), SID=DB01 and I have a full export database dump, it was made like this:
    EXP system/<pw> file=MY.DMP full=Y
    I would like to make a same database in an other instance (SID=DB02).
    I have started the new empty DB02 (there are not exist all table space than these were in the DB01), but I don't know how to use the IMP.EXE.
    I have tried it like this:
    IMP system/<pw> file=MY.DMP full=Y
    If I run it than some user and schema are missing from the DB02 database.
    How can I make an exactly same copy from the originan database?
    Thank you very mutch.
    Regards
    Viktor
    null

    The above solution is correct. Along with this you also need grant for the user EXP_FULL_DATABASE and IMP_FULL_DATABASE. If not you grant using the following syntax.
    grant EXP_FULL_DATABASE to <user-name>
    grant IMP_FULL_DATABASE to <user-name>
    Best of luck

  • What exactly does 'Activate and Adjust Database" mean?

    In SE14, if I put a table or index name in I get the button options to creat/delete/and Activate and Adjust Database.  What does that last one mean?  If I have an existing index does it reorg it? Does it just rematch the SAP internals to the Oracle database?
    Thanks
    Vince

    Hi,
    For an Index in SE14-->Activate & Adjust database is nothing but rebuilding of Index. if you see any missing indexes in DB02 then you can rebuild those using this option.
    This is specially helpful when your Index size becomes larger than table(more than table size).  You can free some space by monitoring large size index whose size is greater than & rebuild then using SE14-->Activate & Adjust with database.
    In case of table this option is risky as it may result in data loss
    Hope this helps.
    Thanks,
    Sushil

  • Checklist for setting up BI QA box

    Hi Gurus,
    Can you please provide me the checklist for the BI QA/Prod box.
    We are in the process of building our QA and Prod. box.
    Thanks,
    SAPIAN

    Hi,
    As for the case
    There is a Preupgrade phase wherein u need to follow the points listed below.
    1.Activate all requests in the ODS and Data targets.
    2. All Transfer and Update Rules should be activated
    3.     All Info Cubes should be activated
    4.     Master data consistency [Execute report RSDMD_CHECKPRG_ALL]
    5.     Transport requests [Release transport requests and repairs. No request should be in Modifiable version.]
    6.     Deactivate all Process chains
    7.     Remove unnecessary BW temporary database objects
    8.     Delta Queue should be Empty
    9.     Validate the missing indices in DB02
    10.     Check Info-Objects Status.[RSRV: extensive check]
    11.     Check the status of all support packages (via transaction SPAM)
    12. Determine strategy for downtime minimized or resource minimized
    13.Using the SAP BW Analysis Tool (transaction RSRV), perform extensive tests on all important SAP BW Objects; ensure their correctness prior to the upgrade.
    14. Report ANALYZE_RSZ_TABLE to find double entries in SE38
    We have the PREPARE PHASE next.
    Followed by post upgrade activities.
    Hope it helps.
    Regards
    Govind.

  • Index is Missing in DB02

    Dear All,
    I just check in DB02 that there is one secondary Index is missing on Production server.
    Database object for VBAK is inconsistent: (Secondary indexes)  
    Indexes: Inconsistent with DDIC source  
    ABAP Dictionary Database
    Index does not exist Index *IDX$$_6E360001*
      AUFNR
      MANDT
    Please tell me ....
    is it automatically created?
    now.... how can i create this indexe with SE11 or SE14 or some other way?
    Regards,
    Diya

    Hello Diya,
    If you really need to create index then Please go through the Note 334224 - Important notes for creating indexes.
    http://sap.ittoolbox.com/groups/technical-functional/sap-basis/how-to-create-index-in-abap-dictionary-in-sap-1089196
    However, I am not sure whether 'creating' a new index is the solution of the problem mentioned by you initially (What I mean is, creating the index is not the solution 'everytime' for this kind of message in DB02)
    Thanks

  • DB02 = Missing Tables and Indexes = Unknown objects in ABAP Dictionary = DB views

    Hi SAP Gurus,
    on our SAP NetWeaver 7.x BW (based on AIX/Oracle) I find via transaction DB02 (path = Diagnostics => Missing Tables and Indexes) under "Unknown objects in ABAP Dictionary" under DB views a BW object /BI0/.....
    When I make a double click on the object, I am getting the popup window "Display not possible for this object":
    How can I identify the object and clarify with the BW application expert, if needed, how to resolve this object?
    I searched already via RSA1 for the object, but I wasn't able to find anything so far ...
    Thanks for your help and ideas.
    Best regards
    Carlos

    Hello Carlos
    The database view in question is a temporary database object created during a query execution.
    Please read this SAP note 449891 - Temporary database objects in BW 3.x to understand what that view is all about and impact if those views are removed.
    The SAP notes 449891 and 1139396 suggests to run the report SAP_DROP_TMPTABLES to drop these temporary objects. Whether the objects are still required or not is a question to be put across to the BW team. If the temporary objects are removed when they are used by a query, then the query will fail.
    Have a nice day
    RB

Maybe you are looking for