Using dbms_stats

Hi ,
I tried to ran the following dbms_stats for a new table
declare
begin
dbms_stats.gather_table_stats(ownname => xx, tabname => 'TESTING_BT' ,
options => 'GATHER AUTO', method_opt => 'for all columns size repeat',
estimate_percent => dbms_stats.auto_sample_size ,cascade => TRUE ) ;
end;
and it gave me the error :
ORA-06550: line 5, column 40:
PLS-00302: component 'AUTO_SAMPLE_SIZE' must be declared
ORA-06550: line 3, column 1:
PL/SQL: Statement ignored
ques :
1) i thought it will auto gather 5 - 20% of the existing records as per what i read ?
2) does it mean i need to update the "SAMPLE_SIZE" column with some values from the user_tables that has table_name = 'TESTIGN_BT' ?
3) if i really need to do pt 2 then the value is in terms of no of records or a percentage will do ?
kindly advise
tks & rdgs

First off all in 9.2 release options parameter is not proper for gather_table_stats.
It is onlyproper for gather_schema_stats or gather_databas_stats. So your statment
should look like this.
begin
dbms_stats.gather_table_stats(ownname => 'mob', tabname => 'T1' ,
method_opt => 'for all columns size repeat',
estimate_percent => dbms_stats.auto_sample_size ,cascade => TRUE ) ;
end;
There are several bugs in 9.2 about SAMPLE_SIZEcolumn is user_tables. You can
refer to "WHEN USING DBMS_STATS.AUTO_SAMPLE_SIZE NUM_ROWS=SAMPLE_SIZE"
Note:302802.1
Best Regards
Krystian Zieja / mob

Similar Messages

  • Confusion using dbms_stat package

    Hi,
    I am using oracle 10G. I am quite confusied between analyze comman and dbms_stat package. In 9i we can use the analyze command to generate the execution plan if the optimizer select the CHOOSE base. But in oracle 10G this is obsolete, instead of that we can use the three parameter values viz, ALL_ROWS, FIRST_ROWS and FIRTS_N_ROWS. In oracle documentation it is written that whenever we user the value ALL_ROWS then the oracle server automatically selects the COST based optimizer.
    So My question is that what is the use of using dbms_stat package if the plan is automatically generated by setting the value ALL_ROWS in the parameter OPTIMIZER_MODE.
    Please reply ASAP.
    Thanks
    SS

    > I am quite confusied
    It would seem so. This is the wrong forum for your subject matter. What makes you think that DBMS_STATS have anything to do with object orientated programming, object relational design and advance (user) defined data types in Oracle?
    > Please reply ASAP.
    We are volunteers doing answers for free here.
    Urgent asap answers are supplied by Oracle Support when you file a Service Request with them. So try http://metalink.oracle.com for your asap answer.

  • What are the database resources when collecting stats using dbms_stats

    Hello,
    We have tables that contain stale stats and would want to collect stats using dbms_stats with estiamte of 30%. What are the database resources that would be consummed when dbms_stats is used on a table? Also, would the table be locked during dbms_stats? Thank you.

    1) I'm not sure what resources you're talking about. Obviously, gathering statistics requires I/O since you've got to read lots of data from the table. It requires CPU particularly if you are gathering histograms. It requires RAM to the extent that you'll be doing sorts in PGA and to the extent that you'll be putting blocks in the buffer cache (and thus causing other blocks to age out), etc. Depending on whether you immediately invalidate query plans, you may force other sessions to start doing a lot more hard parsing as well.
    2) You cannot do DDL on a table while you are gathering statistics, but you can do DML. You would generally not want to gather statistics while an application is active.
    Justin

  • Where are stats that are gathered using dbms_stats stored?

    where are stats that are gathered using dbms_stats stored?

    http://docs.oracle.com/cd/E11882_01/server.112/e16638/stats.htm#PFGRF94765

  • Regarding gathering statastics using dbms_stats

    Hi,
    BANNER
    Oracle8i Enterprise Edition Release 8.1.7.0.0 - 64bit Production
    PL/SQL Release 8.1.7.0.0 - Production
    CORE 8.1.7.0.0 Production
    TNS for Solaris: Version 8.1.7.0.0 - Production
    NLSRTL Version 3.4.1.0.0 - Production
    i would like generate statastics of tables using dbms_stats and i have lot of users in the database but i would like to generate statastics of "asap" user object(tables and indexes)i am using following syntax by connecting database as asap user :
    sql>connect asap/asap;
    sql>exec DBMS_STATS.GATHER_TABLE_STATS(NULL,'ITEM_T',CASCADE=>TRUE,METHOD_OPT=>'FOR ALL COLUMNS SIZE 254',
    ESTIMATE_PERCENT=>10,DEGREE=>4);
    is this statement is correct do anybody share valuable inputs since first time generating statastics in this database(new joinee)
    Regards
    Prakash

    Hi Prakash ,
    if i want gather statastics of asap schema how i need to connect database is as asap user or sys user OR both the cases are okIn general, I would carefully test the dbms_stats and the resulting new plans BEFORE doing anything in production! Lots may change!
    Oracle recommends only re-analyzing when you have had enough data changes that it will effect your SQL execution plans.
    Is there a reason for your desire to re-analyze? Have you identified sub-optimal SQL as a result of bad stats?
    The addage "If it ain't broke, don't fix it" applies here.
    Andy Holsworth recommends taking aa "deep" sample (perhaps more than 10% if you have the time), including histograms, and keep the stats as-is, only re-analyzing when required.
    Withour SKEWONLY, you will need to manually add your histograms, by identifying skewed column distributions and correlating them to historical SQL. I have some notes on manual histogram detection here:
    http://articles.techrepublic.com.com/5100-10878_11-5091017.html
    We have the term "Monday Morning Mayhem" to describe databases where the DBA blindly re-analyzes stats on Sunday, only to find that the execution plans change dramatically.
    Just make sure to test it throughly in both TEST and QA instances before changing production!

  • Error while using DBMS_STATS.GATHER_schema_STATS

    Hi All,
    My database just got upgraded from Oracle 9i to Oracle 11g.
    While everything else is working fine post upgrade Oracle, the DBMS_STATS.GATHER_schema_STATS with METHOD_OPT => 'FOR COLUMNS SIZE ALL' , which was working fine in Oracle 9i is throwing error after upgarde.
    Below is the error I received:
    SQL> execute DBMS_STATS.GATHER_schema_STATS ('cins_dm', METHOD_OPT => 'FOR COLUMNS SIZE AUTO');
    BEGIN DBMS_STATS.GATHER_schema_STATS ('cins_dm', METHOD_OPT => 'FOR COLUMNS SIZE AUTO'); END;
    ERROR at line 1:
    ORA-20001: method_opt should follow the syntax "[FOR ALL [INDEXED|HIDDEN] COLUMNS [size_caluse]]" when gathering statistics on a group of tables
    ORA-06512: at "SYS.DBMS_STATS", line 9641
    ORA-06512: at "SYS.DBMS_STATS", line 9716
    ORA-06512: at "SYS.DBMS_STATS", line 10048
    ORA-06512: at "SYS.DBMS_STATS", line 18939
    ORA-06512: at "SYS.DBMS_STATS", line 19132
    ORA-06512: at "SYS.DBMS_STATS", line 19088
    ORA-06512: at line 1
    OS Details:
    Has this option got obsolete in Oracle 11g?
    What is the alternative to this?
    OS and Databse Details*
    OS:
    scrbbiddkbry002:sas# uname -a
    SunOS scrbbiddkbry002 5.9 Generic_122300-51 sun4u sparc SUNW,Sun-Fire-V240
    Oracle Client:
    SQL*Plus: Release 9.2.0.1.0 - Production
    Oracle Server:
    SQL> select * from v$version;
    BANNER
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
    PL/SQL Release 11.1.0.7.0 - Production
    CORE 11.1.0.7.0 Production
    TNS for Solaris: Version 11.1.0.7.0 - Production
    NLSRTL Version 11.1.0.7.0 - Production
    Edited by: user13071592 on Aug 3, 2010 2:38 AM

    Hi,
    While going through the link, it seems that METHOD_OPT => 'FOR COLUMNS SIZE AUTO' is obsolete in Oracle 11g and I will have to use METHOD_OPT => 'FOR ALL COLUMNS SIZE AUTO' instead of that. But the option METHOD_OPT => 'FOR COLUMNS SIZE AUTO' used to take just 5 minutes to complete while METHOD_OPT => 'FOR ALL COLUMNS SIZE AUTO' is taking 1 hour.
    I want it to take time (5-6 minutes) which the original METHOD_OPT => 'FOR COLUMNS SIZE AUTO' was taking.

  • Link with examples of using dbms_stats package

    Please,
    Should Someone let me know when I could find a link or some example on using the new DBMS_STATS package to gather data statisitcs?
    Thanks

    All, made in Oracle:
    http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14231/general.htm#sthref1861
    http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14211/stats.htm#PFGRF30102
    http://download-west.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_stats.htm#sthref7887
    http://download-west.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_stats.htm#sthref7903
    http://download-west.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_stats.htm#ARPLS059

  • Error using dbms_stats.drop_extended_stats

    Hi!
    I have the following problem:
    I want to drop extended stats and i get the following error:
    SQL> begin
    2 dbms_stats.drop_extended_stats (
    3 ownname => 'ORAP'
    4 ,tabname => 'TDORGEH'
    5 ,extension => '(O2_KOE||''*'')'
    6 );
    7 end;
    8 /
    begin
    FEHLER in Zeile 1:
    ORA-00001: Unique Constraint (SYS.I_WRI$_OPTSTAT_HH_OBJ_ICOL_ST) verletzt
    ORA-06512: in "SYS.DBMS_STATS", Zeile 8443
    ORA-06512: in "SYS.DBMS_STATS", Zeile 8497
    ORA-06512: in "SYS.DBMS_STATS", Zeile 31747
    ORA-06512: in Zeile 2
    SQL> SELECT extension_name, extension
    2 FROM dba_stat_extensions
    3 WHERE table_name = 'TDORGEH';
    EXTENSION_NAME EXTENSION
    SYS_STUU82KTNIFD_P94KDKJ9#0$08 ("O2_KOE"||'*')
    SYS_STUH6U9E_VV_9BVM9I3NNRX#8S ("O3_KOE"||'*')
    SYS_STUCUZFT$CCNA7ZD6R08R3T660 ("O4_KOE"||'*')
    SYS_STUCSINP1TWGAB#R_V3$XR72E7 ("O5_KOE"||'*')
    SYS_STUFD58RVB7F0J1IOL2Q#Z$_VB ("O6_KOE"||'*')
    SYS_STU#84ID#J#21ML9$7ZN#HQ7$Q ("O7_KOE"||'*')
    SYS_STUCMDCY97QZOEH7TEIAB43GUX ("O8_KOE"||'*')
    SYS_STUL3EYD$4V756XR5TCCV7KP94 ("O9_KOE"||'*')
    SYS_STUWBXP9BM7ZXAR$JL9C6XVT7B ("O10_KOE"||'*')
    9 Zeilen ausgewõhlt.
    What is the problem?

    Hi,
    While going through the link, it seems that METHOD_OPT => 'FOR COLUMNS SIZE AUTO' is obsolete in Oracle 11g and I will have to use METHOD_OPT => 'FOR ALL COLUMNS SIZE AUTO' instead of that. But the option METHOD_OPT => 'FOR COLUMNS SIZE AUTO' used to take just 5 minutes to complete while METHOD_OPT => 'FOR ALL COLUMNS SIZE AUTO' is taking 1 hour.
    I want it to take time (5-6 minutes) which the original METHOD_OPT => 'FOR COLUMNS SIZE AUTO' was taking.

  • Using DBMS_STAT.CREATE_STAT_TABLE

    could someone please advise me the format DBMS_STAT.CREATE_STAT_TABLE is used and what columns need to be in there and the format. Thanks in advance

    This procedure create stats table for you, please look at the example below:
    [email protected]> exec dbms_stats.create_stat_table('mob','mobstats')
    PL/SQL procedure successfully completed.
    [email protected]> desc mobstats
    Name Null? Type
    STATID VARCHAR2(30)
    TYPE CHAR(1)
    VERSION NUMBER
    FLAGS NUMBER
    C1 VARCHAR2(30)
    C2 VARCHAR2(30)
    C3 VARCHAR2(30)
    C4 VARCHAR2(30)
    C5 VARCHAR2(30)
    N1 NUMBER
    N2 NUMBER
    N3 NUMBER
    N4 NUMBER
    N5 NUMBER
    N6 NUMBER
    N7 NUMBER
    N8 NUMBER
    N9 NUMBER
    N10 NUMBER
    N11 NUMBER
    N12 NUMBER
    D1 DATE
    R1 RAW(32)
    R2 RAW(32)
    CH1 VARCHAR2(1000)
    Best Regards
    Krystian Zieja / mob

  • Gathering daily statistics of a table using DBMS_STATS..!!

    Hi all,
    Can please somebody help me for how to collect daily statistics of a table..!!
    executing the DBMS_stats is fine but when i assign as a job using OEM the job never starts. It just shows the status as job submitted but never executes..
    Is there any other way to execute the DBMS_STATS daily...??

    In 10g, it is executed daily at 22:00 by default.
    Otherwise, you can execute something like
    begin
    dbms_job.isubmit(job       => 1,
                     what      => 'BEGIN
    DBMS_STATS.GATHER_DATABASE_STATS (
    estimate_percent      => DBMS_STATS.AUTO_SAMPLE_SIZE,
    block_sample          => TRUE,
    method_opt            => ''FOR ALL COLUMNS SIZE AUTO'',
    degree                => 6,
    granularity           => ''ALL'',
    cascade               => TRUE,
    options               => ''GATHER STALE''
    END;',
                     next_date => sysdate + 2,
                     interval  => 'TRUNC(SysDate +1 ) +  22/24',
                     no_parse  => TRUE);
    end;
    commit;Make sure you commit.

  • Problems using dbms_stats.auto_sample_size

    Hi,
    when I try to execute the following statement:
    exec dbms_stats.analyze_schema('SNT', dbms_stats.auto_sample_size);
    I get the following error:
    SQL> execute dbms_stats.gather_schema_stat
    BEGIN dbms_stats.gather_schema_stats('SNT'
    FEHLER in Zeile 1:
    ORA-00933: SQL command not properly ended
    ORA-06512: at "SYS.DBMS_STATS", line 9136
    ORA-06512: at "SYS.DBMS_STATS", line 9616
    ORA-06512: at "SYS.DBMS_STATS", line 9800
    ORA-06512: at "SYS.DBMS_STATS", line 9854
    ORA-06512: at "SYS.DBMS_STATS", line 9831
    ORA-06512: at line 1
    If I use:
    exec dbms_stats.analyze_schema('SNT', 30);
    the statement run without problems. This is an Ora 9.2 release.
    What could be the problem for the first statement ?? Why Oracle doesn't accept the auto_sample_size ??
    Thanks in advance
    Dana

    fyi: i can only reproduce bug 2968571 with 9.2.0.3 and 9.2.0.4

  • Problem using CTXXPATH index

    Hi all,
    i'm using Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 on Windows.
    I created this table
    create table PERSISTENT_COMPOSITION
      COMPOSITION_ID NUMBER(19) not null,
      XML_CONTENT    SYS.XMLTYPE not null,
    )and filled it with more or less 1.000.000 records (that si 1.000.000 xml document loaded into XML_CONTENT).
    Then first of all i tested it with a simple query just like the following:
    SELECT *
      FROM PERSISTENT_COMPOSITION t
    WHERE existsNode(t.xml_content, '/composition/archetype_details/archetype_id[value="openEHR-EHR-COMPOSITION.composition_test.v1"]') = 1;obtaining the expected result: 50,000 records found.
    Now, in order to improve query performances, i created a CTXXPATH index as follows:
    CREATE INDEX IDX#COMP_CTXXPATH ON PERSISTENT_COMPOSITION(XML_CONTENT) INDEXTYPE IS CTXSYS.CTXXPATH;Then i tested the new performances using exactly the same query shown above...and here comes the problem: the query returns NO RESULT! No record was found! I looked at the query execution plan and it uses the created index IDX#COMP_CTXXPATH...but no record could be found...
    I thought it could be a matter of namespace: in fact loaded xml documents have a xmlns set and so i changed the query as follows:
    SELECT *
    FROM persistent_composition t
    WHERE existsNode(t.xml_content,
                      '/composition/archetype_details/archetype_id[value="openEHR-EHR-COMPOSITION.composition_test.v1"]',
                 'xmlns="http://this.is.an.xmlns.url.org/v1"') = 1and surprise: i obtained my 50,000 results just like before BUT, looking at the query execution plan, the IDX#COMP_CTXXPATH index HASN'T BEEN USED!!!
    I really don't understand why using the IDX#COMP_CTXXPATH i get no result....can someone help me?
    Thank you very much
    P.S: i tried using ANALYZE (both on index and on table), CTX_DDL.sync_index and CTX_DDL.optimize_index but got no result..
    Edited by: user11295548 on 29-giu-2009 5.47

    Besides following Mark's advice, and I could be mistaken regarding this in combination with domain indexes, you should NOT use ANALYZE anymore in a Oracle 10 environment. Instead use DBMS_STATS. Its more flexible.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_4005.htm#SQLRF01105
    Note:
    Do not use the COMPUTE and ESTIMATE clauses of ANALYZE to collect optimizer statistics.
    These clauses are supported for backward compatibility.
    Instead, use the DBMS_STATS package, which lets you collect statistics in parallel,
    collect global statistics for partitioned objects, and fine tune your statistics collection
    in other ways. The optimizer, which depends upon statistics, will eventually use only
    statistics that have been collected by DBMS_STATS.
    See PL/SQL Packages and Types Reference for more information on the
    DBMS_STATS package. You must use the ANALYZE statement (rather than
    DBMS_STATS) for statistics collection not related to the cost-based optimizer, such as:
    - To use the VALIDATE or LIST CHAINED ROWS clauses
    - To collect information on freelist blocks

  • Error when running DBMS_STATS package

    Hi all.
    Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production
    PL/SQL Release 9.2.0.4.0 - Production
    CORE 9.2.0.3.0 Production
    TNS for Solaris: Version 9.2.0.4.0 - Production
    NLSRTL Version 9.2.0.4.0 - Production
    I am trying to gather schema stats using dbms_stats package and I see the following:
    SQL> BEGIN DBMS_STATS.gather_schema_stats('SYSADM');
    2 END;
    3 /
    ERROR at line 1:
    ORA-29913: error in executing ODCIEXTTABLEOPEN callout
    ORA-29400: data cartridge error
    KUP-04040: file G534513-1004.txt in EXT_WINDIR not found
    ORA-06512: at "SYS.DBMS_STATS", line 9375
    ORA-06512: at "SYS.DBMS_STATS", line 9857
    ORA-06512: at "SYS.DBMS_STATS", line 10041
    ORA-06512: at "SYS.DBMS_STATS", line 10095
    ORA-06512: at "SYS.DBMS_STATS", line 10072
    ORA-06512: at line 1
    The directory exists but the file is long gone. How can I get around this error?
    Thanks

    See if this helps,
    ERROR WITH EXTERNAL TABLE
    HTH
    Aman....

  • How to set dbms_stats parameters for a single table

    Hi,
    I see that dbms_stats has the following procedure:
    PROCEDURE SET_PARAM
    Argument Name Type In/Out Default?
    PNAME VARCHAR2 IN
    PVAL VARCHAR2 IN
    Is there a way to change the parameters only for a single table?
    I need to set METHOD_OPT=>'FOR ALL COLUMNS SIZE 1' only for a specific table...

    I'm sorry, mate. It looks like setting individual table preferences was introduced in 11g (and doesn't seem to work all that well).
    You can still:
    1. Explicitly specify any of the supported parameters by using DBMS_STATS.GATHER_TABLE_STATS() for the individual table and run it along.
    2. Write a PL/SQL wrapper for let's say DBMS_STATS.GATHER_SCHEMA_STATS/GATHER_DTABASE_STATS that would gather the stats for the whole schema but ignore this particular table. Then gather the stats for the table with the METHOD_OPT parameter of your choice that could be different from the one used for the rest of the schema.
    This could be achieved by locking particular table stats with DBMS_STATS.LOCK_TABLE_STATS, running GATHER_SCHEMA_STATS with force=>FALSE (which is the default). That parameter will make the procedure ignore any tables with locked stats. As the last step of the wrapper you can execute DBMS_STATS.GATHER_TABLE_STATS for the table in question with the desired METHOD_OPT and force=>TRUE.
    It's a little more work, but may solve your problem.
    Max
    Edited by: Max Seleznev on Nov 28, 2012 6:21 PM
    Edited by: Max Seleznev on Nov 28, 2012 6:22 PM

  • Index is not used (why and what should i do) table too big

    hi guys,
    having a headache now. (on 10gR2 on linux system)
    I used to have a large table and this is how i managed it. (i am on standard edition (thus i have no partitioning)
    i would have a
    1) cron job run daily to keep track of the lowest and highest ID of the table PER MONTH (inserted into a table)
    2) below is the table
    CDR     MONTH     01-AUG-11 00:00:00     94118236     97584656
    CDR     MONTH     01-SEP-11 00:00:00     97581362     100573669
    CDR     MONTH     01-OCT-11 00:00:00     100570865     103631203
    CDR     MONTH     01-NOV-11 00:00:00     103629760     106497084
    CDR     MONTH     01-DEC-11 00:00:00     106494085     107306335
    so as you can see, for the month of dec for example, the lowest CDR is 10649408 and the highest is 107306335.
    3) so everytime i write a sql on this table if i want to get data for NOV
    select * from cdr where ID >= get_cdr_id('CDR','NOV','SMALLEST');
    and it would be
    select * from cdr where ID >= 103629760;
    In the past, the index will be used (index range scan), but now the optimiser is doing a FTS and is taking too much time.
    therefore i went to force the index
    select /*+INDEX(C, CDR_PK)*/* from cdr C where cdr_id > 103629760 and cdr_id < 106497084;
    and the COST -> 1678927 (CDR, INDEX_ROWID)
    13158 (CDR_PK, RANGE SCAN)
    -- the result return is fast and good.
    without the index
    select * from cdr C where cdr_id > 100570865 and cdr_id < 103631203
    the COST -> 440236 (CDR,FULL)
    -- but the result return is slow like anything
    My question is
    1) which cost should i look at ?
    the one with index hint have much higher COST, but the results return are so FAST.
    1678927 (with hint) compare with 440236 (FTS)
    2) is using the index is the correct way, why isnt my optimiser using it ?! how do i make the optimiser used it ?
    Regards,
    Noob

    Iordan Iotzov wrote:
    About the clustering factor– I think there are two possibilities:
    1) The “clustering factor” is generally correct, i.e. it represents the true value of how the data is “scattered” through the table. The clustering factor for the fragment of data you are interested in (where cdr_id > 100570865 and cdr_id < 103631203), however, is different (smaller).
    2)Oracle did not compute the “clustering factor” correctly. It is not uncommon occurrence, particularly in 10g. This blog entry by Randolf Geist is quite informative - http://oracle-randolf.blogspot.com/2010/01/clusteringfactor-what-if-analysis.html. Comprehensive information on that topic is available in Jonathan Lewis’ book Cost Based Oracle Fundamentals (chapter 5).
    You can make the index more attractive by setting lower “clustering factor” value using DBMS_STATS.SET_INDEX_STATS. If you choose to do that, you should review your whole stats gathering procedure, because the next gathering would most likely reset the “clustering factor” to its old (high) value.
    Iordan Iotzov
    http://iiotzov.wordpress.com/

Maybe you are looking for

  • Word wrapping with JTextPane and styleDocument

    Hello, Can someone help me with the following problem. I have a JTextPane where i add a styledDocument. If i fill this with text it doen't word-warp the text! import javax.swing.JTextPane; import javax.swing.text.BadLocationException; import javax.sw

  • Format a specific word in report 10g

    Dear All, I have a query that show a remarks of transaction as mention below If you need any further information/details, please feel free to contact at email address "[email protected]" or contact # xxxx-xxxxxxx now I want the output like below If y

  • Widget Validation Problem when creating a form with JS

    Hi all! :D I'm making a section on a webpage that when you click a botton it displays a form created with js, in that form I create the "span's" for spry validation but they are not working. The function to create the form is something like this: //#

  • Repository with 2 or more fact tables

    Helllo everyone. Is there any official document describing how to setup a repository with two or more fact tables? I have created a repository with three fact tables and the needed dimension tables, but there are some loops through table links. Local

  • And the cover flow? all of us want it back

    why don't remove cover flow from finder to