DBMS_STATS.AUTO_SAMPLE_SIZE in a mapping

Hi all,
I would like to know if there is a way to implement DBMS_STATS.AUTO_SAMPLE_SIZE in a mapping.
So far I know it is possible the following.
ANALYZE_TABLE_STATEMENTS (true/false)
ANALYZE_TABLE_SAMPLE_PERCENTAGE (100, also it is possible to set -24 in the GUI)
Thanks!
Sebastián

Hi all,
I believe this does not come native and as I thought. It is required to write it yourself.
@OWB_Product_Mgt:
It would be great if you can consider this change for future editions of OWB: to have the option to define how to calculate statistics after mapping execution [GATHER_TABLE_STATS Procedure Parameters ( method_opt, estimate_percent, etc.)]
Regards,
Sebastian
Edited by: sebastian.v on Jul 29, 2010 5:06 PM

Similar Messages

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

ERROR in dbms_stats

Hi,
i am executing dbms_stats . but i am receiving the following error as
SQL> exec dbms_stats.gather_schema_stats ( ownname => 'STA' , estimate_percent => 10 );
BEGIN dbms_stats.gather_schema_stats ( ownname => 'STA' , estimate_percent => 10 ); END;
ERROR at line 1:
ORA-06521: PL/SQL: Error mapping function
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
please provide me the solution

I find this better
@>ed
Wrote file afiedt.buf
1 begin
2     dbms_stats.gather_schema_stats(
3 ownname          => 'HR',
4 estimate_percent => dbms_stats.auto_sample_size,
5 degree           => 7
6     );
7* end;
@>/
PL/SQL procedure successfully completed.Using estimate_percent => dbms_stats.auto_sample_size to let Oracle determine the appropriate sample size
for good statistics.
Please visit here:
http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_stats.htm#i1036456
Adith

Execute DBMS_STATS in PL/SQL and get ORA-00933

Hi all.
Im trying to execute the following procedure:
as
v_inicio_gather date;
v_fin_gather date;
v_inicio_delete date;
v_fin_delete date;
v_error varchar2(100);
sql_stmt varchar2(100);
begin
select sysdate into v_inicio_gather from dual;
DBMS_STATS.GATHER_DATABASE_STATS(ESTIMATE_PERCENT=>DBMS_STATS.AUTO_SAMPLE_SIZE,DEGREE=>1,GRANULARITY=>'ALL',CASCADE=>TRUE);
select sysdate into v_fin_gather from dual;
v_error := 'OK';
sql_stmt := 'insert into estadisticas_log values (:1, :2, :3, :4, :5)';
execute immediate sql_stmt using v_inicio_gather,v_fin_gather,v_inicio_delete,v_fin_delete, v_error;
commit;
exception
when others then
v_error := 'Codigo de error '|| sqlcode || ': ' || sqlerrm;
sql_stmt := 'insert into estadisticas_log values (:1, :2, :3, :4, :5)';
execute immediate sql_stmt using v_inicio_gather,v_fin_gather,v_inicio_delete,v_fin_delete, v_error;
commit;
end;
I get the error ORA 933 "SQL command not properly ended"
If I comment the dbms_stats call doesn't return error. Is it correctly called?
I'm using oracle 9.2.0.4.
Thanks in advance.

Sorry, but I don't understand you.
I declared my variables varchar2(100) and you say that they could be a bit small and after that why don't declare them as varchar2(2000). I don't have much idea of Oracle, but I think 100 is smaller than 2000 ;).
Could you be more specific?
Thank you.
Also your variables sizes could be a bit small. Why
not declare them as varchar2(2000) or better
I don't see the need to do use dynamic sql.
What was wrong with:
insert into estadisticas_log values
(v_inicio_gather,v_fin_gather,v_inicio_delete,v_fin_de
lete, v_error);
EXCEPTION
insert into estadisticas_log values
(v_inicio_gather,v_fin_gather,v_inicio_delete,v_fin_d
lete, v_error);Also your variables sizes could be a bit small. Why
not declare them as varchar2(2000) or better
v_error estadisticas_log.error%type;
sql_stmt estadisticas_log.sql_stmt%type;
Of cause you would need to use the correct column
name.

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

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.

Dbms_stats Error from Enterprise Manager

A job is scheduled to do dbms_stats on a 10g R2
In the PL/SQL Block it has:
begin
exec dbms_stats.gather_schema_stats ( ownname => 'myTest', options => 'GATHER', estimate_percent => dbms_stats.auto_sample_size, method_opt => 'for all columns size auto', cascade => true, degree => 7 );
exec dbms_stats.gather_schema_stats ( ownname => 'myDev', options => 'GATHER', estimate_percent => dbms_stats.auto_sample_size, method_opt => 'for all columns size auto', cascade => true, degree => 7 );
end;
The error is
ORA-06550: line ORA-06550: line 2, column 8: PLS-00103: Encountered the symbol "DBMS_STATS" when expecting one of the following: := . ( @ % ; The symbol ":=" was substituted for "DBMS_STATS" to continue. ORA-06550: line 3, column 6: PLS-00103: Encountered the symbol "DBMS_STATS" when expecting one of the following: := . ( @ % ; The symbol ":=" was substituted for "DBMS_STATS" to continue. , column :
how to fix it?

You don't use EXEC inside a pl/sql block.
Example.
TUBBY_TUBBZ?exec dbms_stats.gather_table_stats(user, 'PARTY_TIMES');
PL/SQL procedure successfully completed.
begin
exec dbms_stats.gather_table_stats(user, 'PARTY_TIMES');
3 end;
4 /
exec dbms_stats.gather_table_stats(user, 'PARTY_TIMES');
ERROR at line 2:
ORA-06550: line 2, column 6:
PLS-00103: Encountered the symbol "DBMS_STATS" when expecting one of the following:
:= . ( @ % ;
The symbol ":=" was substituted for "DBMS_STATS" to continue.
begin
dbms_stats.gather_table_stats(user, 'PARTY_TIMES');
end;
4 /
PL/SQL procedure successfully completed.
TUBBY_TUBBZ?

ORA-00904 error in DBMS_STATS.GATHER_SCHEMA_STATS

Oracle 9.2.0.5 on Solaris
I am trying to run weekly stat gathering on a schema, using DBMS_STAT
I am getting this error on a specific table, wehich aborts the entire process:
ORA-00904: "SEARCHKEYWORKS": invalid identifier
there is no such field. the table creator confirmed that initally he called a field SEARCHKEYWORKS, but later dropped it and created a new one with different name. maybe we did run DBMS_STATS on this table before the change.
when trying to delete stats for this table, using bms_stats.delete_table_stats(ownname=> 'yyyy', tabname=> 'xxxx') I get a ORA-20000, unable to set values for column BRIEFDESCRIPTION, an existing column
this table is referenced from many other tables, so a simple drop/recreate would be a pain. any way to fix this?
Note: I can run the old-style command ANALYZE TABLE xxx COMPUTE STATISTICS just fine; its just the DBMS_STATS package that can't be run on this table.

thanks for the support.
the weekly task that first reported the error was
EXECUTE DBMS_STATS.GATHER_SCHEMA_STATS('SSSSSS',DBMS_STATS.AUTO_SAMPLE_SIZE,FALSE,'FOR ALL COLUMNS SIZE 1',NULL,'DEFAULT',TRUE);
the log file showed the error. where looking which table was last analyzed I gathered it was this table.
then I tried manually only this table, from manager console using their default, which is:
dbms_stats.gather_table_stats(ownname=> 'SSSSSS', tabname=> 'XXXXXX', partname=> NULL);
Hey,
could you post your dbms_stats complete syntax?
Jaffar

Difference between dbms_stats and COMPUTE STATISTICS

Hello everyone,
Can anyone tell me what is the difference between:
dbms_stats.gather_table_stats(
    ownname => 'me',
    tabname => 'ORGANISATIONS',
    estimate_percent => dbms_stats.auto_sample_size
);and
ANALYZE TABLE ORGANISATIONS COMPUTE STATISTICS;I guess both method are valid to compute statistics, but when I run the first method, the num_rows in USER_TABLES is wrong.
But when I execute the second method, I get the correct num_rows.
So, what is exactly the difference and which one is best?
Thanks,

Hello,
It's not recommended to use ANALYZE statement to collect Optimizer statistics. So you should use DBMS_STATS.
Else, about the number of rows, as you used an Estimate method, you may have a number of row which is not accurate.
What is the result if you choose this:
estimate_percent => NULL
NB: Here, NULL means COMPUTE.
You may have more detail on the following link:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/stats.htm#PFGRF003
This Note from My Oracle Support may give you many useful advices:
Recommendations for Gathering Optimizer Statistics on 10g [ID 605439.1]Hope this help.
Best regards,
Jean-Valentin

Error in DAC ETL Full Load (Supply Chain Inventory Transactions)

Hi Gurus,
My Environment is like this,
Syatems: windows 2003 server 32 bit
DAC: 10.1.3.4.1 with Patch 10052370
Informatica : Power Center 8.6.1 Hot Fix 11
OBIA: 7.9.6.2
OBIEE: 10.1.3.4.1
I Created a plan with one Subject area Supply Chain Inventory Transactions. while running i am getting an error (out of 241 tasks 22 got failed). Nothing got Failed in Informatica. TASK_Group_Load_PositionHierarchy got failed. when i go through the log the error is like this.
Error:
Values :
Null Map
MESSAGE:::ORA-00604: error occurred at recursive SQL level 1
ORA-01654: unable to extend index SYS.I_WRI$_OPTSTAT_H_OBJ#_ICOL#_ST by 128 in tablespace SYSAUX
ORA-06512: at "SYS.DBMS_STATS", line 18408
ORA-06512: at "SYS.DBMS_STATS", line 18429
ORA-06512: at line 1
EXCEPTION CLASS::: java.sql.SQLException
Error:
MESSAGE:::DataWarehouse:DBMS_STATS.GATHER_TABLE_STATS(ownname => 'DWH_REP', tabname => 'W_POSITION_DH', estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE, method_opt => 'FOR ALL INDEXED COLUMNS SIZE AUTO',cascade => false, degree => DBMS_STATS.DEFAULT_DEGREE)
ORA-00604: error occurred at recursive SQL level 1
ORA-01654: unable to extend index SYS.I_WRI$_OPTSTAT_H_OBJ#_ICOL#_ST by 128 in tablespace SYSAUX
ORA-06512: at "SYS.DBMS_STATS", line 18408
ORA-06512: at "SYS.DBMS_STATS", line 18429
ORA-06512: at line 1
Values :
Null Map
Please Help me to Solve this.
Edited by: 846311 on Apr 11, 2011 10:52 PM

Hi Naveen,
Thanks for your reply,
I added one more temp tablespace like temp3, it resolves my problem, i am getting sucesses now. temp tablespace is using while exicuting large queries like aggrications.
Thanks,
Rajesh Thumuluri

Error when upgrade Oracle client 9.2.0.5.0 to 9.2.0.5.3

Hi all,
I'm new with Oracle community so I hope you guys can help me and give me some suggestion with my case.
I got an error when upgrade Oracle client 9.2.0.5.0 to 9.2.0.5.3
I tried many times but can’t do upgrade successfully
This the error message I got when doing the job:
[ http://picasaweb.google.com/hoagao84/Oracle#5443442931867670386]
Appreciate your help.
Log files:
Command arguments are: apply
OPatch version is: 1.0.0.0.48
Using ORACLE_HOME/oui to look up oui libs...
Oracle Home = d:\oracle\ora92
Location of Oracle Inventory = D:\oracle\ora92\inventory
Oracle Universal Installer shared library = D:\oracle\ora92\oui\lib\win32\oraInstaller.dll
Path to Java = "D:\oracle\ora92\jdk\jre\bin\java.exe"
Location of Oracle Inventory Pointer = N/A
Location of Oracle Universal Installer components = D:\oracle\ora92\oui
Required Jar File under Oracle Universal Installer = jlib\OraInstaller.jar
Checking if this is a RAC system...
Accessing inventory... This may take up to 300 seconds.
(retry 10 times, delay 30 seconds each time)
System Command: ""D:\oracle\ora92\jdk\jre\bin\java.exe" -Dopatch.retry=10 -Dopatch.delay=30 -classpath "D:\oracle\ora92\oui\jlib\OraInstaller.jar;D:\oracle\ora92\oui\jlib\srvm.jar;D:\oracle\ora92\opatch\jlib\opatch.jar;D:\oracle\ora92\oui\jlib\xmlparserv2.jar;D:\oracle\ora92\oui\jlib\share.jar;.:D:\oracle\ora92\jlib\srvm.jar" opatch/O2O "d:\oracle\ora92" "D:\oracle\ora92\oui" opatch.pl 1.0.0.0.48"
Result:
output to OPatch:
IS_CLUSTER=0
CHECK_CLUSTER=1
NODE_LIST=NULL
NODE_COUNT=0
LOCAL_NODE=NULL
IS_CFS=0
RAC_CODE=0
HOME_INDEX=1
This is not a RAC system
Interim Patch ID: 3738339
Checking the patch inventory.
Component Name: oracle.rdbms
Component Version: 9.2.0.5.0
Component Name: oracle.rsf.rdbms_rsf
Component Version: 9.2.0.5.0
Component Name: oracle.rsf.oracore_rsf
Component Version: 9.2.0.5.0
Component Name: oracle.rsf.xdk_rsf
Component Version: 9.2.0.5.0
Component Name: oracle.rsf.dbjava_rsf
Component Version: 9.2.0.5.0
Component Name: oracle.java.javavm.javatools
Component Version: 9.2.0.5.0
Component Name: oracle.cartridges.context
Component Version: 9.2.0.5.0
Component Name: oracle.cartridges.locator
Component Version: 9.2.0.5.0
Component Name: oracle.rsf.net_rsf
Component Version: 9.2.0.5.0
Component Name: oracle.rsf.ldap_rsf
Component Version: 9.2.0.5.0
Component Name: oracle.emprod.oemagent.base_oemagent
Component Version: 9.2.0.5.0
Component Name: oracle.isearch.is_common
Component Version: 9.2.0.5.0
Component Name: oracle.options.olap.cwmlite
Component Version: 9.2.0.5.0
Component Name: oracle.rsf.nlsrtl_rsf
Component Version: 9.2.0.5.0
Bugs fixed by this patch 3738339:
3741539 : LOGICAL STANDBY FAILS ORA-1422 MERGING PARTITIONS WITH LOB COLUMN
2800494 : KCBZIB XHINT FORCES SINGLE BLOCK READS INADVERTENTLY FOR SINGLE INSTANCE
3239873 : EXTREMELY HIGH PARSING TIMES WITH AND BETWEEN IN ORACLE 9.2.0
2918138 : ORA-600 (KOHDTF048) WHEN USING PIPELINED PL/SQL TABLE FUNCTIONS
3575743 : 2004-S144E
3554319 : APPSST; ORA-00600 [KQLUDP2] RUN DURING APPS UPGRADE
3666502 : ORA-00600 [1236] RANDOMLY OCCURING
3752406 : MERGE LABEL REQUEST ON TOP OF 9.2.0.5 FOR BUGS LISTED BELOW
3528282 : 2004S075E
3412818 : REPEATED MESSAGES IN LGWR TRACE
2690205 : 2003-S190E
3543125 : 2004-S089E
3571233 : 2004-S141E
3458446 : 2004S059E
2810394 : LNXN2PD RETURNS SCALE OF 42 WHEN COVERTING ORACLE NUMBER 0. TO PACKED
3323435 : 2003-S126E
3356103 : ORA-600 [OPIBND0; OACCSID] IN PARALLEL QUERY SERVER P001 EXECUTING OLAP QUERY
3668224 : CBO CALCULATE LOWER CMPTD CDN AND LEADS TO BAD EXECUTION PLAN.
3492040 : ORA-600 [KGHFRF1] SELECTING FROM V$LOGMNR_CONTENTS
3150750 : SM; (DBMS_STATS/AUTO_SAMPLE_SIZE) ESTIMATED NDV IS WRONG WITH HIGH SKEWS
3566469 : 2004-S138E
3320622 : 2003-S191E
3749394 : SCORE() FOR FUZZY TEXT OPERATOR DIFFERENT FOR FUNCTIONAL VERSUS INDEX ACCESS
3609791 : PSR 9.2.0.5.0 BREAKS CALL DB2 STORED PROCEDURE WITH DECIMAL PARM. SQLCODE -310
3698501 : CGS/IMR GENERATES SAME SEQ/INCARNATION NUMBER AFTER RECONFIG
3668572 : ORA-979 WHEN CURSOR_SHARING=FORCE OR SIMILAR
3179637 : UNABLE TO CREATE AN ORACLECONTEXT ON AD UNDER A CHILD DOMAIN
3571226 : 2004-S140E
3240280 : JOBS SUDDENLY STOP ALTHOUGH NEXT_DATE <= SYSDATE
2964252 : LPX-00252 WHEN PARSING VALID XML / DTD FILE
3617519 : TRANSFORMATION FAILING WITH ORA-932 INCONSISTENT DATATYPE
3172282 : ORACLE CORE DUMPS WHEN TRY TO LIST ALL ACES FOR A SPECIFIC ACL
3637624 : WRONG RESULTS WITH DISTINCT COUNT AND UNNESTED EXISTS SUBQUERY
3542588 : SAME EVENT 38041 USED FOR BUG FIXES 3444115 AND 3131551
3358490 : ORA-00600 [KQSCCCK;1],[],[],[],[],[],[],[]
3177513 : WRONG PLAN - JOIN NOT AVOIDED USING BITMAP JOIN INDEX IF UNIQUE INDEX TOO
3509265 : SHUTDOWN DID NOT COMPLETE WITH WAITING FOR INSTANCES TO LEAVE; 2
3516951 : BAD EXECUTION PLAN WITH MERGE JOIN CARTESIAN IN TEMP TABLE
2954891 : ORA-600 KJMXMPM;DIFFUS], [990307644], [990307644], [3304659678]
3388633 : LOGICAL STANDBY APPLY STOPPED WITH ORA-00600; [17090]
3371796 : EXPLAIN PLAN HANGS ON KKORMINL
3622875 : ORA-1499 AND ANALYZE TABLE VALIDATE STRUCTURE CASCADE ONLINE
3412136 : BAD EXECUTION WITH MERGE JOIN CARTESIAN IN ORACLE 9.2.0.4 AND MERGEFIX 3363655
3540576 : 2004-S083E
3575747 : 2004-S145E
3566813 : CTAS WITH UNION ALL AND ORDER BY RESULTS IN ORA-3113
3811906 : MERGE LABEL REQUEST ON TOP OF 9.2.0.5
2824035 : FXD; ORA-22921 CAUSING 4 DIFS IN LRGXG2.
3354470 : 2003-S195E
3518909 : UGA MEMORY NOT RELEASED AFTER USING XMLPARSER
3617042 : BAD PLAN FOR SCH-XMLTYPE BASED WITH COLLECTIONS MAPPED TO OCT
3583686 : MEMORY ALLOCATION ERROR DURING SPATIAL QUERY
3597640 : MERGE LABEL REQUEST ON TOP OF 9.2.0.5.0
3559212 : WRONG RESULTS RETURNED WITH 9.2.0.4 AND CBO
3625370 : CGS/IMR RECONFIGURATION GOT HUNG DURING A NEW MEMBER JOINING
3475932 : CROSS INSTANCE ARCHIVE LOG NOT GENERATED REMOTELY
3635177 : PSRC; ORA-7445 [KXCCUIN] POSSIBLE FROM DML
3430832 : ORA-600 [25012] AFTER CREATE OF INDEX ONLINE PARALLEL ON PART TABLE
2338704 : FXD; 1; QUERIES ON COLLECTIONS STORED IN OUT-OF-LINE TABLES ARE NOT VIEW MERGED
3253770 : 9I-GSI-CRITICAL PROGRAMS TIME OUT WAITING FOR LIBRARY CACHE PIN
Reading patch XML files and doing sanity checks.
Read the command to action file map.
Performing initial safety check.
Checking active processes:
Accessing inventory... This may take up to 300 seconds.
(retry 10 times, delay 30 seconds each time)
System Command: ""D:\oracle\ora92\jdk\jre\bin\java.exe" -Dopatch.retry=10 -Dopatch.delay=30 -classpath "D:\oracle\ora92\oui\jlib\OraInstaller.jar;D:\oracle\ora92\oui\jlib\srvm.jar;D:\oracle\ora92\opatch\jlib\opatch.jar;D:\oracle\ora92\oui\jlib\xmlparserv2.jar;D:\oracle\ora92\oui\jlib\share.jar;." opatch/CheckConflict "D:\oracle\ora92\oui" "d:\oracle\ora92" opatch.pl 1.0.0.0.48 3738339 "3253770 2338704 3430832 3635177 3475932 3625370 3559212 3597640 3583686 3617042 3518909 3354470 2824035 3811906 3566813 3575747 3540576 3412136 3622875 3371796 3388633 2954891 3516951 3509265 3177513 3358490 3542588 3637624 3172282 3617519 2964252 3240280 3571226 3179637 3668572 3698501 3609791 3749394 3320622 3566469 3150750 3492040 3668224 3356103 3323435 2810394 3458446 3571233 3543125 2690205 3412818 3528282 3752406 3666502 3554319 3575743 2918138 3239873 2800494 3741539 " C:\TEMP\patch92053\3738339\etc\config\actions"
Result:
d:\oracle\ora92\opatch\opatch.pl version: 1.0.0.0.48
Copyright (c) 2001,2002,2003 Oracle Corporation. All Rights Reserved.
Error in executing Java program to check conflict
ERROR: OPatch failed during pre-reqs check.

This is all the message when I run command in CMD prompt.
C:\temp\patch92053\3738339\perl d:\oracle\ora92\opatch\opatch.pl apply
Opatch Version 1.0.0.0.48
Perl Version 5.008007
Oracle Home = d:\oracle\ora92
Location of Oracle Inventory = D:\oracle\ora92\inventory
Oracle Universal Installer shared library = D:\Oracle\ora92\oui\lib\win32\oraInstaller.dll
Path to Java = "D:\oracle\ora92\jdk\jre\bin\java.exe"
Location of oracle Inventory Pointer = N/A
Location of Oracle Universal Installer components = D:\Oracle\ora92\oui
Require Jar File under Oracle Universal Installer = jlib\OraInstaller.jar
The filename, directory name, or volume label syntax is incorrect.
D:\oracle\ora92\opatch\opatch.pl version 1.0.0.48
Copyright (c) 2001,2002,2003 Oracle Corporation. All Rights Reserved
Error in executing Java program to check conflict
Error: Opatch failed during pre-reqs check.

OWB Speed

I find OWB development environment very sluggish at my client place. It takes lot of time to open a mapping or deployment manager etc. Export and import are very slow too. I have 800 MB on my desktop.
I found OWB much faster when Oracle and OWB running on same machine having 400 MB only.
Can someone suggest about what can be done to improve performance. Will indexing of Repository tables help. Should we analyze repository on regular basis. I am telling the scnario where 3-4 people working on same repository.

Hi,
There can be three factors affecting the performance of OWB Client working with Design Repository. Here is what you can do about them now as well as what OWB development has done (a lot!) to improve this in the next release (November 2004). They are in the order of greatest impact.
1. Design Repository management.
Problem: CHANGELOG table in the OWB design repository is typically several orders of magnitude smaller in row count than pctree, intralink, or interlink, so the nested loop plan is best. The optimizer's row estimate in the absence of gathered statistics does not serve us very well here.
Solution in the next release:
* Automated gathering of schema statistics (and refresh statistics on a regular basis)
* Increased use of SQL bind variables
* Improved SQL hints
* Ensured definition of all necessary indexes
* Used COMPRESS for indexes
Workaround for now: Try analyzing OWB design repository with the following statements. This is only worthwhile if the size of the repository is large.
exec dbms_stats.gather_table_stats(null, 'PCTREE', null,
DBMS_STATS.AUTO_SAMPLE_SIZE, false, 'FOR ALL COLUMNS SIZE AUTO');
exec dbms_stats.gather_table_stats(null, 'INTERLINK', null,
DBMS_STATS.AUTO_SAMPLE_SIZE, false, 'FOR ALL COLUMNS SIZE AUTO');
exec dbms_stats.gather_table_stats(null, 'INTRALINK', null,
DBMS_STATS.AUTO_SAMPLE_SIZE, false, 'FOR ALL COLUMNS SIZE AUTO');
exec dbms_stats.gather_table_stats(null, 'CHANGELOG', null,
DBMS_STATS.AUTO_SAMPLE_SIZE, false, 'FOR ALL COLUMNS SIZE AUTO');
exec dbms_stats.gather_index_stats(null, 'IDX_PCTREE_PARENTID', null,
DBMS_STATS.AUTO_SAMPLE_SIZE);
exec dbms_stats.gather_index_stats(null, 'IDX_PCTREE_CHILDID', null,
DBMS_STATS.AUTO_SAMPLE_SIZE);
exec dbms_stats.gather_index_stats(null, 'IDX_PCTREE_PARENTID_CHILDID',
null, DBMS_STATS.AUTO_SAMPLE_SIZE);
exec dbms_stats.gather_index_stats(null, 'IDX_PCTREE_CHILDID_PARENTID',
null, DBMS_STATS.AUTO_SAMPLE_SIZE);
exec dbms_stats.gather_index_stats(null, 'IDX_INTERLINK_LINKFROM',
null, DBMS_STATS.AUTO_SAMPLE_SIZE);
exec dbms_stats.gather_index_stats(null, 'IDX_INTERLINK_LINKTO', null,
DBMS_STATS.AUTO_SAMPLE_SIZE);
exec dbms_stats.gather_index_stats(null, 'IDX_INTRALINK_LINKFROM',
null, DBMS_STATS.AUTO_SAMPLE_SIZE);
exec dbms_stats.gather_index_stats(null, 'CHANGELOG_PK', null,
DBMS_STATS.AUTO_SAMPLE_SIZE);
2. Memory management.
Solution in the next release: A lot of improvements to prevent memory leaks and unnecessary flushing of needed objects.
Workaround for now: Try a higher Java Virtual Machine (JVM) limit for you OWB Client: Edit -Xmx value in [OWB Home]\owb\bin\win32\owbclient.bat from default 384M. This is only worthwhile if the client machine
has enough real memory to support the VM sizes of all actively running applications and if Windows Task Manager shows the owbclient java session Memory Usage and VM Size values close to the Xmx value, then OWB starts spending a larger portion of its effort managing memory.
3. Network latency.
Problem: Network latency is why having OWB Client installed local to the Oracle database containing the design repository will always be faster, as you observe "I found OWB much faster when Oracle and OWB running on same machine having 400 MB only." Obviously this does not solve the problem in multiple developer environment, but it is not as big of the factors above. We are confident that OWB Client 'chatting' over the network is already optimized.
Nikolai Rochnik

"analyze index" vs "rebuild index"

Hi,
I don't undestand the difference between "analyze index" and "rebuild index".
I have a table where I do a lot of "insert" and "update" and "query", What is the best thing to do ??
thanks
Giordano

When you use dbms_stats.gather_schema_stats package with cascade=>true option, you are also collecting stats for the indexes, no need to collects stats separately using dbms_stats.gather_index_stats.Of course, but I refered to the rebuild index question. Therefore I only mentioned the GATHER_INDEX_STATS.
Auto_sample_size has many problems/bugs in 9iOk didn't know that - I'm using 10gR2.
But this discussion made me curious. So I tried something (10gR2):
CREATE TABLE BIG NOLOGGING AS
WITH GEN AS (
SELECT ROWNUM ID FROM ALL_OBJECTS WHERE ROWNUM <=10000)
SELECT V1.ID,RPAD('A',10) C FROM GEN V1,GEN V2
WHERE ROWNUM <=10000000;
SELECT COUNT(*) FROM BIG;
COUNT(*)
10000000
So I had a Table containing 10 Million rows. Now I indexed ID:
CREATE INDEX BIG_IDX ON BIG(ID)
I tested two different methods:
1.) GATHER_TABLE_STATS with estimate 10%
EXEC DBMS_STATS.GATHER_TABLE_STATS(TABNAME=>'BIG',OWNNAME=>'DIMITRI',CASCADE=>TRUE,ESTIMATE_PERCENT=>10);
It took about 6 seconds (I only set timing on in sqlplus, no 10046 trace) Now I checked the estimated values:
SELECT NUM_ROWS,SAMPLE_SIZE,ABS(10000000-NUM_ROWS)/100000 VARIANCE,'TABLE' OBJECT FROM USER_TABLES WHERE TABLE_NAME='BIG'
UNION ALL
SELECT NUM_ROWS,SAMPLE_SIZE,ABS(10000000-NUM_ROWS)/100000 VARIANCE,'INDEX' OBJECT FROM USER_INDEXES WHERE INDEX_NAME='BIG_IDX';
NUM_ROWS SAMPLE_SIZE VARIANCE OBJEC
9985220 998522 ,1478 TABLE
9996210 999621 ,0379 INDEX
2.) GATHER_TABLE_STATS with DBMS_STATS.AUTO_SAMPLE_SIZE
EXEC DBMS_STATS.DELETE_TABLE_STATS(OWNNAME=>'DIMITRI',TABNAME=>'BIG');
EXEC DBMS_STATS.GATHER_TABLE_STATS(TABNAME=>'BIG',OWNNAME=>'DIMITRI',CASCADE=>TRUE,ESTIMATE_PERCENT=>DBMS_STATS.AUTO_SAMPLE_SIZE);
It took about 1,5 seconds. Now the results:
NUM_ROWS SAMPLE_SIZE VARIANCE OBJEC
9826851 4715 1,73149 TABLE
10262432 561326 2,62432 INDEX
The estimate 10% was more exact - also a 1,7 and 2,6 percent variance is still ok. It's also very interesting, that using AUTO_SAMPLE_SIZE
causes oracle to execute a estimate 5% for the index and a estimate 0.5 for the table.
I tried again with a table containing only 1 Million records and oracle did an estimate with 100% for the index.
So for me I will continue using AUTO_SAMPLE_SIZE. Its very flexible, fast and accurate.
Dim
PS: Is there a way to format code like one can do in HTML using <code> or <pre>?

How to configure Oracle Sql Developer for 9i

Hi,
We are using oracle 9i for existing application, and i am trying to connect oracle 9i through SQL developer 1.5.1, i got an error message "Unsupported Oracle Database Version".
Appreciate if any body guide me in this.
regards
Husal.

After removing dictionary statistics with dbms_stats.delete_schema_stats(ownname => 'SYS') I noticed the initial SQL Developer object list query became very slow.
Removal of dictionary statistics increased the predicted Oracle optimizer (CBO) costs. Previous SYS statistics were collected perhaps without realising the consequences.
You may wish to try dbms_stats.gather_schema_stats(ownname => 'SYS', method_opt => 'FOR ALL COLUMNS SIZE AUTO', sample_size => dbms_stats.auto_sample_size).
Recent Oracle 10G versions include a gather_dictionary_stats routine.
Suggest you try this on a development DB first.

Database Upgradation from oracle 9.2.0.8 to oracle11gR2

Hi
we are using AIX 5.3 TL 10 SP4 and we are upgrading DB from oracle9.2.0.8 to oracle 11.2.0.2
i am having some doubt from below pre-upgrade scripts out put.
oratst@ebsdevdb on /tmp # sqlplus "/as sysdba"
SQL*Plus: Release 9.2.0.8.0 - Production on Mon Jul 4 10:11:48 2011
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
SQL> spool 11202_upgrade.txt
SQL> @utlu112i.sql
Oracle Database 11.2 Pre-Upgrade Information Tool 07-04-2011 10:17:06
Script Version: 11.2.0.2.0 Build: 001
Database:
--> name: EBSTEST
--> version: 9.2.0.8.0
--> compatible: 9.2.0
--> blocksize: 8192
--> timezone file: V1
Logfiles: [make adjustments in the current environment]
--> The existing log files are adequate. No changes are required.
Tablespaces: [make adjustments in the current environment]
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 8546 MB
--> TOOLS tablespace is adequate for the upgrade.
.... minimum required size: 8 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 61 MB
--> AR_TABLE tablespace is adequate for the upgrade.
.... minimum required size: 33497 MB
--> FND_TABLE tablespace is adequate for the upgrade.
.... minimum required size: 45447 MB
--> AMVD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> ASOD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> CCTD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> IBUD tablespace is adequate for the upgrade.
.... minimum required size: 1 MB
--> IEMD tablespace is adequate for the upgrade.
.... minimum required size: 5 MB
--> IEOD tablespace is adequate for the upgrade.
.... minimum required size: 4 MB
--> JTFD tablespace is adequate for the upgrade.
.... minimum required size: 135 MB
--> OKCD tablespace is adequate for the upgrade.
.... minimum required size: 34 MB
--> XDPD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> XNPD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> APPS_UNDOTS1 tablespace is adequate for the upgrade.
.... minimum required size: 849 MB
Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]
Note: Pre-upgrade tool was run on a lower version 64-bit database.
--> If Target Oracle is 32-Bit, refer here for Update Parameters:
WARNING: --> "compatible" must be set to at least 10.1.0
--> If Target Oracle is 64-Bit, refer here for Update Parameters:
WARNING: --> "compatible" must be set to at least 10.1.0
WARNING: --> "shared_pool_size" needs to be increased to at least 532 MB
WARNING: --> "java_pool_size" needs to be increased to at least 128 MB
Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]
-- No renamed parameters found. No changes are required.
Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]
--> optimizer_max_permutations 10.1 OBSOLETE
--> row_locking 10.1 OBSOLETE
--> undo_suppress_errors 10.1 OBSOLETE
--> max_enabled_roles 10.1 DEPRECATED
--> enqueue_resources 10.2 OBSOLETE
--> sql_trace 10.2 DEPRECATED
--> background_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest"
--> user_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest"
Components: [The following database components will be upgraded or installed]
--> Oracle Catalog Views [upgrade] VALID
--> Oracle Packages and Types [upgrade] VALID
--> JServer JAVA Virtual Machine [upgrade] VALID
--> Oracle XDK for Java [upgrade] VALID
--> Real Application Clusters [upgrade] INVALID
--> Oracle Text [upgrade] VALID
--> Oracle XML Database [install]
--> Oracle Java Packages [upgrade] VALID
--> Oracle interMedia [upgrade] VALID
--> Spatial [upgrade] VALID
Miscellaneous Warnings
WARNING: --> Passwords exist in some database links.
.... Passwords will be encrypted during the upgrade.
.... Downgrade of database links with passwords is not supported.
WARNING: --> Deprecated CONNECT role granted to some user/roles.
.... CONNECT role after upgrade has only CREATE SESSION privilege.
WARNING: --> Database is using a timezone file older than version 14.
.... After the release migration, it is recommended that DBMS_DST package
.... be used to upgrade the 9.2.0.8.0 database timezone version
.... to the latest version which comes with the new release.
WARNING: --> Database contains INVALID objects prior to upgrade.
.... The list of invalid SYS/SYSTEM objects was written to
.... registry$sys_inv_objs.
.... The list of non-SYS/SYSTEM objects was written to
.... registry$nonsys_inv_objs.
.... Use utluiobj.sql after the upgrade to identify any new invalid
.... objects due to the upgrade.
.... USER ADWANIAH has 1 INVALID objects.
.... USER APPS has 34 INVALID objects.
.... USER CHAKKACHANSA has 1 INVALID objects.
.... USER FA_USER has 9 INVALID objects.
.... USER SYSSEL has 2 INVALID objects.
.... USER SYSTEM has 30 INVALID objects.
.... USER XXITDFINAD has 7 INVALID objects.
WARNING: --> SYSTEM schema default tablespace has been altered.
.... The SYSTEM schema default tablespace is currently set to TOOLS.
.... Prior to upgrading your database please reset the
.... SYSTEM schema default tablespace to SYSTEM using the command:
.... ALTER USER SYSTEM DEFAULT TABLESPACE SYSTEM;
WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP package.
.... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
.... USER APPS has dependent objects.
Recommendations
Oracle recommends gathering dictionary statistics prior to
upgrading the database.
To gather dictionary statistics execute the following commands
while connected as SYSDBA:
EXECUTE dbms_stats.gather_schema_stats('CTXSYS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('DBSNMP',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('MDSYS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('ORDPLUGINS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('ORDSYS',options=>'GATHER'
estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('OUTLN',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('SYS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('SYSTEM',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
Oracle recommends removing all hidden parameters prior to upgrading.
To view existing hidden parameters execute the following command
while connected AS SYSDBA:
SELECT name,description from SYS.V$PARAMETER WHERE name
LIKE '\_%' ESCAPE '\'
Changes will need to be made in the init.ora or spfile.
Oracle recommends reviewing any defined events prior to upgrading.
Changes will need to be made in the init.ora or spfile.
Oracle recommends reviewing any defined events prior to upgrading.
To view existing non-default events execute the following commands
while connected AS SYSDBA:
Events:
SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2
WHERE UPPER(name) ='EVENT' AND isdefault='FALSE'
Trace Events:
SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2
WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'
Changes will need to be made in the init.ora or spfile.
SYSAUX Tablespace:
[Create tablespace in the Oracle Database 11.2 environment]
--> New "SYSAUX" tablespace
.... minimum required size for database upgrade: 500 MB
From above output script
1)SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 8546 MB
From system tablespace minimum required size means free space from system tablespace or total size of system tablespace?
i am going to use dbua utility for upgrade means does it alter tablespace as per output of scripts or we need to manually alter tablespace size as per requirement?
2)WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP package.
.... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
.... USER APPS has dependent objects.
what is above warning and how can i configure ACL's for APPS User?
Thanks
With Regards
A-Z

Hi
oratst@ebsdevdb on /ebdbh/11g/data/cfgtoollogs/dbua/ebstest/upgrade1 # more Upgrade_Directive.log
Connected.
ODMA_DIRECTIVE:VERSION:9.2.0.8
ODMA_DIRECTIVE:MIGRATE_SID:
ODMA_DIRECTIVE:ORA:IGNORE:06512:
ODMA_DIRECTIVE:ORA:FATAL:00600:
ODMA_DIRECTIVE:ORA:FATAL:01012:
ODMA_DIRECTIVE:ORA:FATAL:01031:
ODMA_DIRECTIVE:ORA:FATAL:01034:
ODMA_DIRECTIVE:ORA:FATAL:01078:
ODMA_DIRECTIVE:ORA:FATAL:01092:
ODMA_DIRECTIVE:ORA:FATAL:01109:
ODMA_DIRECTIVE:ORA:FATAL:01119:
ODMA_DIRECTIVE:ORA:FATAL:01507:
ODMA_DIRECTIVE:ORA:FATAL:01722:
ODMA_DIRECTIVE:ORA:FATAL:03113:
ODMA_DIRECTIVE:ORA:FATAL:03114:
ODMA_DIRECTIVE:ORA:FATAL:07445:
ODMA_DIRECTIVE:ORA:FATAL:12560:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01650:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01651:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01652:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01653:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01654:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01655:
ODMA_DIRECTIVE:ORA:RECOVER_ROLL:01562:
ODMA_DIRECTIVE:ORA:RECOVER_INIT:04031:
ODMA_DIRECTIVE:SCRIPT:UPGRADE:rdbms/admin/catupgrd.sql:
ODMA_DIRECTIVE:BOUNCE_DATABASE:UPGRADE:
ODMA_DIRECTIVE:SCRIPT:UPGRADE:rdbms/admin/catuppst.sql:
ODMA_DIRECTIVE:SCRIPT:UPGRADE:sqlplus/admin/help/hlpbld.sql helpus.sql:
Thanks
With Regards
A-Z

DBMS_STATS.AUTO_SAMPLE_SIZE in a mapping

Similar Messages

Maybe you are looking for