on 08-03-2011 2:55 PM
We have consulted the following note:
Note 428212 - Using BRCONNECT to update InfoCube statistics
That describes variants of brconnect commands to statistics on an InfoCube.
However in DBA Planning calender, under DB02, when we select Check and
update optimizer statistics, it only generates a standard brconnect
command:
brconnect -u / -jid STATS20110417040000 -c -f stats -t ALL
How can we set up this transaction to allow for the variants of
brconnect for infocubes as described in the note?
If not, does this mean our only option is to run these variations
through a job scheduler (or command line) apart from DB02 and the DBA
planning calendar?
We would like to have ALL these jobs in once place (DB02 / DBA Planning
Calendar) as opposed to managing different jobs for different purposes.
Hello Jeff,
much more important than the standard BRCONNECT job is the collection of statistics for infocubes in process chains.
This is were you really should try to put your statistics runs for Infocubes to, since this is where the change of data happens.
If you don't do it directly when you load data to the cube then you might run into performance issues during reporting, since then the statistics for table and columns would not reflect the new data.
regards,
Lars
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I apologize for not stating the question correctly.
The issue is that the statistics job is taking too long to run. So we want to know if it is possible (or advisable) to run stats on non-info cube tables at one interval (say daily) and then schedule stats for infocubes on a separate schedule (different interval and / or time of day).
Ee were hoping to be able to schedule these two different variations in the DBA Planning calendar.
If not, would it be possible (or again, advisable) to schedule these as separate "jobs" via SM37 - the documentation for creating a command line alternatives seems pretty clear.
thanks,
JH
Hi Jeff,
You can execute "brconnect" with parallel update statistics to decrease runtime. This will significantly improves the run times on update stats job. To do this, you need to set "-p" with brconnect or "stats_parallel_degree" parameter in the "init<SID>.sap" profile.
You can check the note 403713 - BRCONNECT: Parallel updating of statistics for the further information.
As an additional info, as I noted in my first message that you can modify the SDBAH table by using the note "859450 - Maintenance of the DB13-command table SDBAC" to keep your configuration permanently.
Best regards,
Orkun Gedik
Hi Jeff,
>> brconnect -u / -jid STATS20110417040000 -c -f stats -t ALL
It means that all the tables and infocube statistics will be updated. Check the title "Example 4 (default - also applies to BW 3.0B and higher)" on the same note.
In short when you execute statistics on DBA Planning Calendar, it will update all the tables and infocubes, as well.
>> How can we set up this transaction to allow for the variants of brconnect for infocubes as described in the note?
You can set stats_table, stats_exclude and stats_dbms_stats parameters in the init<DBSID>.sap file, as indicated in the note. Or maintain content of SDBAH table as described in the note 859450 - Maintenance of the DB13-command table SDBAC
Best regards,
Orkun Gedik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
then creating updateStats job in DB13, map it to a different initSID.sap file (such as initSIDinfocube.sap)
that other file would contain the params you need.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.