BIA indexes for Multiprovider

Hello All,
Can we create BIA indexes for a multiprovider.
My current data flow is that, i have a Infocube and based on that i have multiprovider not a big flow.
what does it make difference in creating on Infocubes and multiprovider?
I know that multiprovider does not holds the data physically, but just to understand can we implement this.?
I am currently working on SAP BI 7.3 version.
Regards,
Siva

hey Siva,
You cannot create BIA Indexes on a multiprovider.
     - a multiprovider does not contain any physical data (like you stated).
     - a multiprovider can have all kinds of underllying infoproviders to it, this means DSOs as well. We do not create indexes on a multiprovider.
     - even if your multiprovider consist only of cubes, it never holds the data physically. Everytime you run a query, it fetches from the underlying cubes. Thus, no sense of making indexes on a multiprovider when the reading has to be done from the cube itself.
Thanks,
Sheen

Similar Messages

ABAP to set "Switched on/off BIA indexes for queries" flag?

Hi everyone,
Does anyone know if the "Switch on/off BIA Indexes for Queries" can be set for a specific cube by a delivered ABAP?
Here's my scenario. We go live with BIA next Monday 9/22. I've indexed our cubes in production BIA this past weekend and they're rolled up nightly. Until the go-live, I've manually set the "Switched Off for Queries" flag via RSDDBIAMON > BI Accelerator > Index Settings > Switch on/off BIA Indexes for Queries".
However, one indexed cube is deleted fully every night by the flag in the full load infopackage. In testing, I saw that the BIA fact table index was fully deleted when the E and F tables of the cube were truncated, and then reindexed when the full package is loaded and rolled up. This is all ok.
The issue is that after the delete, load and rollup, the "Switched Off for Queries" flag is not set. I have had to manually reset to off in the morning. This won't be an issue (hopefully) once we go live, but it does seem like a bug and I'll likely submit a customer message. I would think the delete, index and rollup process should not change the status of this flag.
Does anyone know if that flag can be programatically set?
Thanks for any advice,
Doug

Thanks, Vitaliy!
I think you're exactly right. Its seems to be a bug in processing of just this specific type of index reprocessing, e.g. dropping and reindexing. The indexing process properly retains INA status on the other delta indexed cubes.
I'm barely ABAP OO literate, but do understand enough to find, review and test the class and method code. Thanks for finding it!
Also, I reviewed table RSDDTREXDIR and it is correct/current. It does spawn another question, though. The field ITYPE (Type of BIA Index) is consistently ICB exept for 2 cubes/indexes, which are typed as PA2 and PA9. When I check possible values on the domain, RSDDTREX_TAGGR_TYPE, it only lists ICB and ICF (Infocube - flat).
Any idea what types PA2 and PA9 are, and why these 2 cubes would be different? From my perspective, they're basic infocubes, same as all the others.
Thanks again,
Doug

Error when creating BIA INDEX FOR CUBE

Hi
I am trying to create BIA index for a cube and I am getting error
"An error occurred. Choose "Continue" to start again from the beginning" in the second step. Could any body explain what this error mean and How to correct it.
and when I press BIA Moniter tab I am getting following message.
An error occurred. Choose "Continue" to start again from the beginning
"BIA Monitor Is Called for First Time
The RFC destination for the BI accelerator is not yet specified in the
system. Without the relevant entry in RSADMINA, the BIA monitor cannot
be executed. Do you want to enter the RFC destination now?"
Thanks in Advance
Sarath
Edited by: sarath kumar on Aug 21, 2008 9:42 AM

Hi,
Is there any way i can check bi accelerator installed or not for our bi server.I contacted basis team but they do not have any idea regarding this. but I heard from my ex colleage it is installed. and Reports from one cube is running very fast compared to recently created cube.
Thanks
Sarath

Transport error failure with return code 12 for BIA indexed Cube

Hello,
I was trying to transport few cubes from the Dev to the QA system. However, the transport failed repeatedly with return code 12. I noticed that the version of Cubes in the target system had BIA indexes loaded on it. So, I deleted those indexes and re-transported the cubes.To my surprise, the transport went fine without the BIA indexes. This now opens up a new avenue for discussion of dropping and recreating BIA indexes for those cubes that needs to be transported.
Any thoughts on this new aspect before. Has anyone faced similar problems. I want to know your experiences before we can take this issue to SAP.
Thanks,
Rishi

Rishi/Vitaly/Marc,
How do you transport cubes with BIA indexes.
Do you drop/recreate the BIA index before the transport.
In my case, the transport kicked off adjustment job exactly as described in [Note 1012008|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1012008]
Indexes looks fine once this jobs completes successfully. The transport does not fail.
Is this approach fine.
I see that most of the customers drop/recreate indexes before transporting cubes.
Can I run into data consistency issues with this approach?
Input required.
Thanks,
Saurabh

Error in creating BIA index after SPS upgrade

Hi BIA experts,
we got issues in BIA after our BI SPS upgrade (current level SPS18):
when wir try to create new BIA index for a cube (normal basic cube), we got error RSD_TREX121 (index type ICB). This issue occurs since we completed SPS18 upgrade.
Any help and feedback are highly appreciated!!!
Regards,
Sally

Hi Sally,
"BIA index has type ICB" is not an error message. It just indicates that the index type has been initialized or changed. Can you describe the symptoms more clearly or provide more details of the job and/or application log?
Regards,
Marc
SAP NetWeaver RIG

Attribute Change Run aborted with an error :Not all data indexed for index

Hi,
I have an issue where the master data Attribute Change Run aborted with an error pointing to the BWA:
Attribute Change Run aborted with an error :Not all data indexed for index
we tried to load only 0 data into it,the error still occured.

Detail message is following:
not all data was indexed for index 'GBP_BIC:XYCH_098('0' for '114')
creation of The BIA INDEX for infocube 'YBC_SD015' terminated while filling

BIA INdexes : URGENT

Hello
I am maintaining the BIA Indexes for my cubes and when i say continue i am getting this error message
Restart master index server
I got this error message yesterday as well and I did restart the mater index server through the BIA Index Monitor tab...but today when creating for the other cubes it is giving this error.
Is it like when we are creating BIA Indexes we have to start the master index server for each cube..
Please can someone suggest
thanks

Hello,
Are you executing multiple BIA Indexes in parallel, if so there may be a lock created which may cause this error.
From the below OSS
Two or more InfoCubes are indexed simultaneously in the BI accelerator (BIA). One of the processes terminates because the indexing of a master data table by one of the other processes has not been completed yet.
You can restart the process without problems.
See these
SAP Note 981054 BIA indexing: Termination due to locked master data
Thanks
Chandran

Deleting the BIA Indexes

<Moderator Message: Search before posting>
Hi,
Can you explain how to delete BIA Indexes for a particular infocube?
Thanks,
Manohar
Edited by: Siegfried Szameitat on May 5, 2009 1:13 PM

Hi,
See if these notes are of help.
SAP Note 926609 - BIA index and metadata changes
SAP Note 917803 - Estimating the memory consumption of a BIA index
1012008 - BI accelerator index after activating the InfoCube
There may be few related notes attached to these notes.
check them also.
Hope this helps.
Thanks,
JituK

BIA Index Loading into Mmeory (for SAP) ....

Hello all,
I went to www.sdn.sap.com and chose Business Intelligence from the left menu.
In the BI Knowledge Center (Right side), I chose BI Accelerator, which is under Key Topics section.
Then I opened a document "SAP Business Intelligence Accelerator (PDF 154 KB)".
Go to the section "SAP BI Accelerator at Work", which is at page# 5. The third point says like this -
BI accelerator indexes are loaded into memory where the query is processed. In memory, joins and aggregations are done at run time. Loading of indexes into memory happens automatically at first query request, or it can be set for preloading whenever new data is loaded.
I had an understanding that it will be loaded into memory only when query was first executed. But this says it can be set for preloading as well wherever new data loaded.
My question is that where this setting can be done for preloading?
It says that preloading option is available whenever new data loaded so does that mean that it can only be set for rollup of BIA Index and for initial load, it will still load data into memory when the query is first executed.
I would appreciate if somebody has knowledge of this as it is new technology.
Others, who has a knowledge can also answer.
Your help will be greatly appreciated.
Thank you to everybody in advance.
Sume

Hi,
I found it.
It is an option on BIA Index Property button in the wizard. It appears only after the initial load is done. There is check box for to keep the BIA Index in main store. I thin it is only applicable to Roll-up.
Thank you.
Sume

Prerequisites for an Infocube to crete BIA indexes

Hi experts,
I am very new to BIA. I have just loaded some data into a Cube and I want to create and fill BIA indexes. But before that I doubt whether we need to do any must-be-done activities such as roll up or compressing that particular request. Please guide me step by step approach to create BIA indexes starting from the load to the cube has been done. Thanks.

Hi,
I would like to ad that though technically there are no pre-requisits for an InfoCube to create BWA indexes, from a business side there is. This is assuming being on BW 7.x is not considered as a pre-req.
1. In a BW only enviroment modeling is not very critical as space and selection are both ceheap and manual.
2. Move to BWA and sudeenly space is a very expensive commodity, not only at the time of ourchase but also on an annual basis. In such an environment if re-modelign can reduce the Cube footprint by 30 to 60% then that company has to spend 30-60% less on blades and annual maintenence costs. Or fit 30-60% more cubes into the BWA. This one seems to be a no-brainer.
3. A lot of time we run our queries from Multiproviders and go ahead and index all the Cubes. The in some cases user says that the query response is still the same. When we dive deeper we discover that the query, or Muptiprovider, is dependent on a reporting DSO. Well this reporting DOS must now either be converted to an InfoCube or one built on top for leveraging the BWA. This is a common 1st time mistake with some BWA installations - lessons get learnt quite rapidly
But just at a high level these is a lot of business reasons to reshape the Cubes prior to BWA, or create 'RightModeled" Cubes on top of reporting DSO's. Companies will save manyfolds more in this process and enhance prformances that the cost for deployign this solution. - It's all automated now..

Error while deleting from BIA index

HI EXPERTS GETTING BELOW ERROR PLZ GIVE CLARITY ON THIS:
1.A communication error occured, with the TREX TcpIp
2.Error while deleting from BIA index; reconstruction required
THANKS &REGARDS,
rAMESH,

Dear Ramesh,
Please check the connection with BIA. Please ask the Basis team to check the BW to BIA connection if they maintain it.
YOu can go to rsddbiamon2 and check BIA connection availibility for more details.
If that is right please try redoing the step at which you faced error and it should help.
Please close the question if you have got the answer or solved it.
Regards,
Den

Effect of Cube Compression on BIA index's

What effect does cube compression have on a BIA index?
Also does SAP recommend rebuilding indexes on some periodic basis and also can we automate index deletes and rebuild processes for a specific cube using the standard process chain variants or programs?
Thank you

Compression: DB statistics and DB indexes for the InfoCubes are less relevant once you use the BI Accelerator.
In the standard case, you could even completely forgo these processes. But please note the following aspects:
Compression is still necessary for inventory InfoCubes, for InfoCubes with a significant number of cancellation requests (i.e. high compression rate), and for InfoCubes with a high number of partitions in the F-table. Note that compression requires DB statistics and DB indexes (P-index).
DB statistics and DB indexes are not used for reporting on BIA-enabled InfoCubes. However for roll-up and change run, we recommend the P-index (package) on the F-fact table.
Furthermore: up-to-date DB statistics and (some) DB indexes are necessary in the following cases:
a)data mart (for mass data extraction, BIA is not used)
b)real-time InfoProvider (with most-recent queries)
Note also that you need compressed and indexed InfoCubes with up-to-date statistics whenever you switch off the BI accelerator index.
Hope it Helps
Chetan
@CP..

How to delete BIA indexes - manually via program?

Dear all
We are currently facing the issue where our BIA indexes are growing at a tremendous rate, due to our use of Full Load and Delete Overlapping Requests activities. Checks shows that our fact indexes are 6999% above the Fact tables and growing by day.
As per suggestion from the SAP Best Practice, we should be deleting and rebuilding the BIA indexes on a regular basis (we plan to do this everytime the loading completes). However, the SAP Best Practice only mention the program to initially activate and fill the BIA indexes (RSDDTREX_BIA_ACTIVATE_FILL), and fail to mention a program to delete the BIA indexes automatically.
Since we are scheduling this activity, is there a program for us to delete the BIA indexes? We will subsequently rebuild it using the RSDDTREX_BIA_ACTIVATE_FILL program.
We don't mind function module as well, as we will create a wrapper program around it.
Thanks for the advise
Chris

Hi,
See if these notes are of help.
SAP Note 926609 - BIA index and metadata changes
SAP Note 917803 - Estimating the memory consumption of a BIA index
1012008 - BI accelerator index after activating the InfoCube
There may be few related notes attached to these notes.
check them also.
Hope this helps.
Thanks,
JituK

BIA Index creation error due to invalid characters

Hi All,
While creating BIA index on an Infocube the index creation process fails with the following message.
Index for table '/BIC/SSPSEGTXT' is being processed
A character set conversion is not possible.
Parallel indexing process terminated (Task: '4')
Turns out this field is a text field and has characters such as * and + in the description,which is causing this problem.
How do I proceed with the index creation.
Options I have are:
a) Get rid of this field.. Impossible since there are a few queries that require this information.
b) Run the Database scan tool RSI18N_Search to eliminate foreign characters ....but this does not work for me.
Can anyone suggest some other option or a resolution to this problem. Or If anyone has prior experience of working with the program RSI18N_Search please let me know.
Regards
VK

Venkat, Andres,
You can try several things here;
1) This is pretty ugly but in case you need a quick way around. Create another cube w/o that char, load all the data to that cube from the first cube, and start sending daily deltas to both cubes. Of course put the second cube to BWA
2) Delete the master data! When you try deleting the master data (a particular record or records that you identified), mostly you will find out that it's used in a transactional data(in ODS or Cube) therefore it will not allow you to delete those records, unless you delete the records from the cubes first, then try it again. OR you might be lucky that it's not stored in anycube and it will delete it right away!
The right way is the second option, however when you delete data from cubes, ods, it will lock the cube + invalidate aggregates if you have + BWA indexes etc. You need to recreate them again. So try doing it in non-business hours or in your maintenance window.
Cheers
Tansu

Initiate and Fill BIA Index Step Fails in Process Chain

HI!
       In our weekend scenario for a cube, we refresh the data in a cube. What we do is, we delete BIA indexes before the data refresh in the cube, load the data, recreate the indexes using "Initialize and Fill BIA" step.
Last run the filling process failed and in the log it showed this message:
Lock for table 'table name'. Job will be restarted again later
We have it for many tables and at the end of the log:
FILLING_FAILED >CHECK LOG!!!!!
Please any advice in this?
Thanks,
Ghassan Matar

HI!
    After the investigation, we found that the root cause of the lock is the ODS Activation. We have two ODS's activation jobs running at the same time we were initialize and fill BIA indexes. We tested that in Staging and it causes the lock as well.
We implemented the Note 1223239 by setting the following parameters:
WRITEINDEX =        180
WAITTIME =            60
This weekend, the ODS Activation step ended before the BIA Initialize and Fill step by 4 minutes. The step created the indexes for the cube tables but it didn't continue to fill any index and it failed.
The Log is here.
NEW INDEX: /BI0/SVTYPE                                                                                RSD_TREX        100          S
NEW INDEX: /BI0/SSALESORG                                                                                RSD_TREX        100          S
NEW INDEX: /BIC/SZREGION                                                                                RSD_TREX        100          S
Event RSPROCESS with parameter 4L1CWG1AC7C479GIO3Z5A5GPH successfully triggered      RSMPC         090          S
Job finished                                                                                00           517          S
Also, after implementing the note: 1223239 with the parameters above, THE ODS Activation step was running in parallel with BIA Initalize and Fill step. the lock occured and after the completion of ODS Activation step all the locked tables get unlocked and filled properly except for 5 tables. It seems to me like kind of dead lock between these 5 tables. they take all the remaining time of the step and at the end BIA Initalize and Fill fails.
If you will notice in our log, it is only 5 tables remaining and they are repeated every minute. At the end, the step failed.
03:59:26 Lock for table '/BIC/SSEGRULE'. Job will be restarted again later
03:59:26 Lock for table '/BIC/SNPM_YEAR'. Job will be restarted again later
03:59:26 Lock for table '/BIC/SNPM_ENDYR'. Job will be restarted again later
03:59:26 Lock for table '/BIC/SNPMPERCNT'. Job will be restarted again later
03:59:26 Lock for table '/BIC/SDOMRULE'. Job will be restarted again later
04:00:26 Lock for table '/BIC/SSEGRULE'. Job will be restarted again later
04:00:26 Lock for table '/BIC/SNPM_YEAR'. Job will be restarted again later
04:00:26 Lock for table '/BIC/SNPM_ENDYR'. Job will be restarted again later
04:00:26 Lock for table '/BIC/SNPMPERCNT'. Job will be restarted again later
04:00:26 Lock for table '/BIC/SDOMRULE'. Job will be restarted again later
04:01:26 Lock for table '/BIC/SSEGRULE'. Job will be restarted again later
04:01:26 Lock for table '/BIC/SNPM_YEAR'. Job will be restarted again later
04:01:26 Lock for table '/BIC/SNPM_ENDYR'. Job will be restarted again later
04:01:26 Lock for table '/BIC/SNPMPERCNT'. Job will be restarted again later
04:01:26 Lock for table '/BIC/SDOMRULE'. Job will be restarted again later
04:01:26 FILLING_FAILED >CHECK LOG!!!!!
04:01:27 Entire chain now has status 'R'
04:01:28 Process ABAP Program, variant Rebuild BIA Indexes - Daily Inventory - End of Pro has status Undefined (instance )
Please advise.
Thanks,
Ghassan Matar

BIA indexes for Multiprovider

Similar Messages

Maybe you are looking for