OID is INVALID when query dba_registry
Hi Everyone.
I have a problem with OAS in Development environment... when I query dba_registry (as follows) I got the following output:
SQL> l
1 select comp_id, comp_name, version, status, modified
2 from dba_registry
3* where status = 'INVALID'
SQL> /
COMP_ID COMP_NAME VERSION STATUS MODIFIED
OID Oracle Internet Directory 10.1.2.3.0 ; INVALID 07-AUG-2008 02:11:20
I also ran @?/rdbms/admin/utlrp.sql and no errors were found
SQL> @?/rdbms/admin/utlrp
TIMESTAMP
COMP_TIMESTAMP UTLRP_BGN 2009-09-02 11:15:26
PL/SQL procedure successfully completed.
TIMESTAMP
COMP_TIMESTAMP UTLRP_END 2009-09-02 11:16:12
PL/SQL procedure successfully completed.
Invoking Ultra Search Install/Upgrade validation procedure VALIDATE_WK
Ultra Search VALIDATE_WK done with no error
PL/SQL procedure successfully completed.
And also check opmctl status, and OID process is ALIVE:
--> opmnctl status
Processes in Instance: INSTANCE.server.domain
------------------------------------------------+---------
ias-component | process-type | pid | status
------------------------------------------------+---------
LogLoader | logloaderd | N/A | Down
dcm-daemon | dcm-daemon | 2505 | Alive
OC4J | OC4J_SECURITY | 7134 | Alive
HTTP_Server | HTTP_Server | 7100 | Alive
OID | OID | 7104 | Alive
DSA | DSA | N/A | Down
Do you have any idea on how to solve OID INVALID status???
I'd really appreciate your time and help
Check if any ODS components are invalid
# Review $ORACLE_HOME/ldap/admin/LOGS/ldapupgrade.log
Check for any errors or messages.
- If any significant problems are seen, correct them and rerun oidiugrd.sql
- If no problems are found, or invalid status persists after rerunning, continue with the following steps:
# Check the ODS schema for invalid objects and correct as necessary
% sqlplus / as sysdba
SQL> select owner,object_name,object_type from dba_objects
2> where owner='ODS' and status='INVALID';
# Cut the final validation portion of oidiugrd.sql and run it by itself:
alter session set current_schema = SYS;
execute DBMS_IAS_VERSION.SET_COMPONENT_UPGRADED(COMPONENT_ID=>'OID');
declare
rc integer;
begin
rc := ods.ldapUpgUtls.validateODS();
if rc = 0 then
DBMS_IAS_VERSION.SET_COMPONENT_VALID(COMPONENT_ID=>'OID');
else
DBMS_IAS_VERSION.SET_COMPONENT_INVALID(COMPONENT_ID=>'OID');
end if;
end;
-SRP
Similar Messages
-
I am trying to modify a query for LOV page item but get an Invalid LOV query error when trying to Apply Changes to my page(query however works in SQL*Plus)
I am trying to change the date format of query result to MON YYYY.
Original query that works:
select distinct bill.BILLED_DATE display_value, bill.BILL_ID return_value
from BILL;
New Query that fails in APEX (but works in SQL*Plus)
select distinct to_char(bill.BILLED_DATE, 'MON YYYY') display_value,
bill.BILL_ID return_value from BILL;
Anyone have any idea what I need to do to make this work?
"1 error has occurred
LOV query is invalid, a display and a return value are needed, the column names need to be different. If your query contains an in-line query, the first FROM clause in the SQL statement must not belong to the in-line query"Strange, this lov does work and is no different than yours:
select distinct to_char(sysdate,'MON YYYY') disp, 1 retval from dual
What are the results from the query? Can there be something wrong with that?
Regards Guido -
QBE Error when query by String for Number column
Hi,
I have a table with Number column.
The column structure is like below:
<af:column>
<af:inputText>
<f:validator .../>
<af:converNumber ..../>
</af:inputtext>
</af:column>
QBE is enabled for this column.
It works fine when query by Number value, such as '123'. But when I query by string like 'asd', it will return an error.
Anyone met this problem?Hi Arun,
I am using Jdev 11.1.1.7.0.
In my case,
I have a application table, from where user can create new row inline. Some fields in the row have type Long or Number. We are also using <af:converNumber ..../> inside <af:inputText> to do format.
I do have a query panel above the table. But we want the user can also filter the records using QBE. Other columns are working fine, except the columns with type 'Number' or 'Long'.
I checked the incident log, below are some useful information:
Caused by: java.sql.SQLSyntaxErrorException: ORA-01722: invalid number
Caused by: oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation. Statement: SELECT ... FROM ... WHERE ... AND ( ( (MeaRulesEO.DEFAULT_MEA_PERIOD = :vc_temp_1 ) ) )
It seems 'MeaRulesEO.DEFAULT_MEA_PERIOD = :vc_temp_1' causes the error. Jdev assumes every input from QBE header as number. If String is entered, Jdev will return error.
I also checked that if the table is read-only, this problem does not exist.
Please help on this. Thank you. -
I bought The Dark Knight a few years ago, I tried to download the digital copy before but I gave up. Now that I have my iPhone, I'm determined to get all the digital copies I'm entitled to! So I'm here to find out how to remedy the situation. iTunes says the code is invalid when it clearly should work. I didn't buy the DVD off the street or anything. iTunes doesn't give me any further options, so what can I do? Anybody have any advice, please?
Yeah, I actually did get it. I had to send an e-mail to Warner Bros. with all available info and my issue and they sent me another code that actually worked.
So I actually just had to do what varjak paw suggested, it just took a few days (maybe a week) and I forgot to get back to you guys. So, belated but all the same thank you, varjak paw! -
MY I PHONE WILL NOT LET ME DOWNLOAD ANYMORE APPS CUS OF MY BILLING INFORMATION IVE FIXED THIS ERROR SEVERAL TIMES ALREADY & IT STILL TELLS ME "SECURITY CODE INVALID" WHEN I KNOW FOR A FACT IT IS NOT. HELP ME
Contact the card issuer and find out what the problem is.
Was the card issued in the same countryas the store you're trying to use? -
Delay when querying from CUBE_TABLE object, what is it?
Hi Guys,
We are using Oracle OLAP 11.2.0.2.0 with an 11g Cube, 7 Dimensions, Compressed and partitioned by Month.
We have run into a performance issue when implementing OBIEE.
The main issue we have is a delay while drilling on a hierarchy. Users have been waiting 7-12 seconds per drill on a hierarchy, and the query is only returning a few cells of data. We have managed to isolate this to slow performing queries on CUBE_TABLE.
For example, the following query returns one cell of data:
SELECT FINSTMNT_VIEW.BASE, FINSTMNT_VIEW.REPORT_TYPE, FINSTMNT_VIEW.COMPANY, FINSTMNT_VIEW.SCENARIO, FINSTMNT_VIEW.PRODUCT, FINSTMNT_VIEW.ACCOUNT, FINSTMNT_VIEW.SITE, FINSTMNT_VIEW.TIME
FROM "SCHEMA1".FINSTMNT_VIEW FINSTMNT_VIEW
WHERE
FINSTMNT_VIEW.REPORT_TYPE IN ('MTD' )
AND FINSTMNT_VIEW.COMPANY IN ('E01' )
AND FINSTMNT_VIEW.SCENARIO IN ('ACTUAL' )
AND FINSTMNT_VIEW.PRODUCT IN ('PT' )
AND FINSTMNT_VIEW.ACCOUNT IN ('APBIT' )
AND FINSTMNT_VIEW.SITE IN ('C010885' )
AND FINSTMNT_VIEW.TIME IN ('JUN11' ) ;
1 Row selected in 4.524 Seconds
Note: FINSTMNT_VIEW is the automatically generated cube view.
CREATE OR REPLACE FORCE VIEW "SCHEMA1"."FINSTMNT_VIEW" ("BASE","REPORT_TYPE", "COMPANY", "SCENARIO", "PRODUCT", "ACCOUNT", "SITE", "TIME")
AS
SELECT "BASE", "REPORT_TYPE", "COMPANY", "SCENARIO", "PRODUCT", "ACCOUNT", "SITE", "TIME"
FROM TABLE(CUBE_TABLE('"SCHEMA1"."FINSTMNT"') ) ;
If we increase the amount of data returned by adding to the query, it only increased the query time by .4 seconds
SELECT FINSTMNT_VIEW.BASE, FINSTMNT_VIEW.REPORT_TYPE, FINSTMNT_VIEW.COMPANY, FINSTMNT_VIEW.SCENARIO, FINSTMNT_VIEW.PRODUCT, FINSTMNT_VIEW.ACCOUNT, FINSTMNT_VIEW.SITE, FINSTMNT_VIEW.TIME
FROM "SCHEMA1".FINSTMNT_VIEW FINSTMNT_VIEW
WHERE
FINSTMNT_VIEW.REPORT_TYPE IN ('MTD' )
AND FINSTMNT_VIEW.COMPANY IN ('E01' )
AND FINSTMNT_VIEW.SCENARIO IN ('ACTUAL' )
AND FINSTMNT_VIEW.PRODUCT IN ('PT' )
AND FINSTMNT_VIEW.ACCOUNT IN ('APBIT' )
AND FINSTMNT_VIEW.SITE IN ('C010885', 'C010886', 'C010891', 'C010892', 'C010887', 'C010888', 'C010897', 'C010893', 'C010890', 'C010894', 'C010896', 'C010899' )
AND FINSTMNT_VIEW.TIME IN ('JUN11' ) ;
12 rows selected - In 4.977 Seconds
If we increase the data returned even more:
SELECT FINSTMNT_VIEW.BASE, FINSTMNT_VIEW.REPORT_TYPE, FINSTMNT_VIEW.COMPANY, FINSTMNT_VIEW.SCENARIO, FINSTMNT_VIEW.PRODUCT, FINSTMNT_VIEW.ACCOUNT, FINSTMNT_VIEW.SITE, FINSTMNT_VIEW.TIME
FROM "SCHEMA1".FINSTMNT_VIEW FINSTMNT_VIEW
WHERE
FINSTMNT_VIEW.REPORT_TYPE IN ('MTD' )
AND FINSTMNT_VIEW.COMPANY IN ('ET', 'E01', 'E02', 'E03', 'E04' )
AND FINSTMNT_VIEW.SCENARIO IN ('ACTUAL' )
AND FINSTMNT_VIEW.PRODUCT IN ('PT', 'P00' )
AND FINSTMNT_VIEW.ACCOUNT IN ('APBIT' )
AND FINSTMNT_VIEW.SITE IN ('C010885', 'C010886', 'C010891', 'C010892', 'C010887', 'C010888', 'C010897', 'C010893', 'C010890', 'C010894', 'C010896', 'C010899' )
AND FINSTMNT_VIEW.TIME IN ('JUN11', 'JUL11', 'AUG11', 'SEP11', 'OCT11', 'NOV11', 'DEC11', 'JAN12') ;
118 rows selected - In 14.213 Seconds
If we take the time for each query and divide by the number of rows, we can see that querying more data results in a much more efficient query:
Time/Rows returned:
1 Row - 4.524
12 Rows - 0.4147
118 Rows - 0.120449153
It seems like there is an initial delay of approx 4 seconds when querying the CUBE_TABLE object. Using AWM to query the same data using LIMIT and RPR is almost instantaneous...
Can anyone explain what this delay is, and if there is any way to optimise the query?
Could it be the AW getting attached before each query?
Big thanks to anyone that can help!Thanks Nasar,
I have run a number of queries with logging enabled, the things you mentioned all look good:
Loop Optimization: GDILoopOpt COMPLETED
Selection filter: FILTER_LIMITS_FAST 7
ROWS_FAILED_FILTER 0
ROWS_RETURNED 1
Predicates: 7 pruned out of 7 predicates
The longest action I have seen in the log is the PAGING operation... but I do not see this on all queries.
Time Total Time OPERATION
2.263 27.864 PAGING DYN_PAGEPOOL TRACE GREW 9926KB to 59577KB
1.825 25.601 PAGING DYN_PAGEPOOL TRACE GREW 8274KB to 49651KB
1.498 23.776 PAGING DYN_PAGEPOOL TRACE GREW 6895KB to 41377KB
1.232 22.278 PAGING DYN_PAGEPOOL TRACE GREW 5747KB to 34482KB
1.17 21.046 PAGING DYN_PAGEPOOL TRACE GREW 4788KB to 28735KB
1.03 19.876 PAGING DYN_PAGEPOOL TRACE GREW 3990KB to 23947KB
2.808 18.846 PAGING DYN_PAGEPOOL TRACE GREW 3325KB to 19957KB
What is strange is that the cube operation log does not account for all of the query time. For example:
SELECT "BASE_LVL" FROM TABLE(CUBE_TABLE('"EXAMPLE"."FINSTMNT"'))
WHERE
"RPT_TYPE" = 'MTD' AND
"ENTITY" = 'ET' AND
"SCENARIO" = 'ACTUAL' AND
"PRODUCT" = 'PT' AND
"GL_ACCOUNT" = 'APBIT' AND
"CENTRE" = 'TOTAL' AND
"TIME" = 'YR09';
This query returns in 6.006 seconds using SQL Developer, if I then take the CUBE_OPERATION_LOG for this query and subtract the start time from the end time, I only get 1.67 seconds. This leaves 4.3 seconds unaccounted for... This is the same with the my other queries, see actual time and logged time below:
Query Actual Logged Variance
S3 6.006 1.67 4.336
L1 18.128 13.776 4.352
S1 4.461 0.203 4.258
L2 4.696 0.39 4.306
S2 5.882 1.575 4.307
Any ideas on what this could be or how I can capture this 4.3 second overhead?
Your help has been greatly appreciated. -
Receiving OCI/ORA-27163 when querying XML data in 11g.
When querying a table with a column stored in XML format, we get this error for large XML values. This works in Oracle 10g but this error happens when the same data is queried in an 11.2.0.3 instance. I have had a support request open with Oracle for about a month and so far it has not made any progress. What we've seen are the following:
1. The xml data itself is good.
2. The good xml data when queried with a wholly 10g client/server environment, works.
3. The same good xml data when inserted into a table in an 11g instance through a stored package run from the 11g instance (server to server) gets the 27163 error.
4. The same xml data when queried in a 10g instance from an 11g client fails with the 27163 error.
5. If we disable the 11g XML parser by setting an internal event (alter session set events='31156 trace name context forever, level 0x400';), then run the same code that was run in item 3 above, it does not get the 27163 error. However, the xml loaded to the 11g instance can then only be queried without getting the 27163 error if we use an older 10g client. An 11g client consistently gets the error.
The server versions are 11.2.0.3 (upgraded from 10.2.0.4). The SQL*Net client versions that we have tested on are 11.2.0.2 and 11.2.0.3 (both produce the 27163 error).
With considerable trial and error, we found that it is some combination of the file size and format that causes the error. Copied below is the smallest sample data of a failing XML that will produce this erro (about 8K). Remove any single character even in an a comment and the file parses successfully – but it’s not the file size alone as the original 800+KB file where we first dicovered this problem will process if the period in the attribute: @value=”${item.id}” is removed.
We are at our wit's end, and with an 11g migration project looming, any ideas anyone can suggest would be very helpful.
Thanks,
Joe
Here is a test case to play around with. Sorry I don't have a way to upload a zip file for this, but you can cut & paste from the post:
1. CREATE TABLE my_xml_test
(record_id NUMBER(4,0),
xml SYS.XMLTYPE,
comments VARCHAR2(200))
ALTER TABLE my_xml_test
ADD CONSTRAINT my_xml_test_pk PRIMARY KEY (record_id)
USING INDEX
2. mkdir SampleData
3. cd into SampleData, copy the XML I will post in the first reply to this message into a new text document called xml_items_removed.xml.
4. cd .. and create a file called 20120112_11g_bad_xml_issue.txt with this in it:
1, .\SampleData\xml_items_removed.xml,"Fails: OriginalXML w/ all instances of <Item> removed (count 600) -- reduces file size to ca. 55KB but still fails (Saved by XMLSpy)"
5. Next create your SQL*Loader control file (call it my_xml_test.ctl):
LOAD DATA
APPEND INTO TABLE my_xml_test
FIELDS TERMINATED BY "," OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
record_id,
ext_fname FILLER CHAR(200),
xml LOBFILE(ext_fname) TERMINATED BY EOF,
comments
6. sqlldr <username>/<password>@<database> control=my_xml_test.ctl data=20120112_11g_bad_xml_issue.txt log=20120112_11g_bad_xml_issue.log bad=20120112_11g_bad_xml_issue.bad
7. Once the data is loaded, query my_xml_test table that you created in step 1. You should get the 27163 error:
SELECT a.record_id,
comments,
a.XML,
length(a.XML.GetClobVal()) clob_length
FROM my_xml_test a<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2012 sp1 (http://www.altova.com) by Martin l (National Board of Medical Examiners) -->
<IRData application="Item Review" version="1.3" itempool="2006001" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ViewerTypes>
<Viewer id="its-viewer">
<Title>Item Text</Title>
<Description>Item Text</Description>
<BaseUrl>https://www.starttest.com/flex/4.3.0.0/InstitutionViewItem.aspx</BaseUrl>
<Parameters>
<Parameter name="pid" value="MSST"/>
<Parameter name="iid" value="01123"/>
<Parameter name="username" value="SomeUser"/>
<Parameter name="item" value="${item.id}"/>
<Parameter name="code" value="${CODE}"/>
</Parameters>
</Viewer>
</ViewerTypes>
<Filters>
<Filter id="drop-single-filter">
<AttributeSource>drop</AttributeSource>
<ControlType>select-1-drop-down-plus-all</ControlType>
</Filter>
<Filter id="onoff-single-filter">
<AttributeSource>onoff</AttributeSource>
<ControlType>select-1-drop-down-plus-all</ControlType>
</Filter>
<Filter id="reviewed-single-filter">
<AttributeSource>reviewed</AttributeSource>
<ControlType>select-1-drop-down-plus-all</ControlType>
</Filter>
<Filter id="build-multi-filter">
<AttributeSource>build</AttributeSource>
<ControlType>select-1-drop-down-plus-all</ControlType>
</Filter>
<Filter id="flag-multi-filter">
<AttributeSource>flag</AttributeSource>
<ControlType>select-1-drop-down-plus-all</ControlType>
</Filter>
<Filter id="u1dt-multi-filter">
<AttributeSource>U1DT</AttributeSource>
<ControlType>select-1-drop-down-plus-all</ControlType>
</Filter>
<Filter id="fb2-multi-filter">
<AttributeSource>FB2</AttributeSource>
<ControlType>select-1-drop-down-plus-all</ControlType>
</Filter>
<Filter id="fb1t-multi-filter">
<AttributeSource>FB1T</AttributeSource>
<ControlType>select-1-drop-down-plus-all</ControlType>
</Filter>
<Filter id="scorecat-multi-filter">
<AttributeSource>scorecat</AttributeSource>
<ControlType>select-1-drop-down-plus-all</ControlType>
</Filter>
<Filter id="images-multi-filter">
<AttributeSource>PIXN</AttributeSource>
<ControlType>select-1-drop-down-plus-all</ControlType>
</Filter>
<Filter id="vignettes-multi-filter">
<AttributeSource>VIG1</AttributeSource>
<ControlType>select-1-drop-down-plus-all</ControlType>
</Filter>
</Filters>
<DataPanels>
<Control displayed="true">
<Filters>
<Filter>
<Description>Drop</Description>
<FilterSource>drop-single-filter</FilterSource>
</Filter>
<Filter>
<Description>Version</Description>
<FilterSource>build-multi-filter</FilterSource>
</Filter>
<Filter>
<Description>On/Off Test</Description>
<FilterSource>onoff-single-filter</FilterSource>
</Filter>
<Filter>
<Description>Review status</Description>
<FilterSource>reviewed-single-filter</FilterSource>
</Filter>
<Filter>
<Description>Flag</Description>
<FilterSource>flag-multi-filter</FilterSource>
</Filter>
<Filter>
<Description>Discipline</Description>
<FilterSource>fb1t-multi-filter</FilterSource>
</Filter>
<Filter>
<Description>Organ System</Description>
<FilterSource>u1dt-multi-filter</FilterSource>
</Filter>
<Filter>
<Description>Step 1 outline</Description>
<FilterSource>fb2-multi-filter</FilterSource>
</Filter>
<Filter>
<Description>Images</Description>
<FilterSource>images-multi-filter</FilterSource>
</Filter>
<Filter>
<Description>Vignettes</Description>
<FilterSource>vignettes-multi-filter</FilterSource>
</Filter>
<Filter>
<Description>Score categories</Description>
<FilterSource>scorecat-multi-filter</FilterSource>
</Filter>
</Filters>
</Control>
<ItemList displayed="true">
<Attributes>
<Attribute displayed="true">
<Description>Item</Description>
<AttributeSource>itemref</AttributeSource>
<ControlType>text-display</ControlType>
</Attribute>
<Attribute displayed="true">
<Description>On test</Description>
<AttributeSource>onoff</AttributeSource>
<ControlType>checkbox-select</ControlType>
</Attribute>
<Attribute displayed="true">
<Description>Drop</Description>
<AttributeSource>drop</AttributeSource>
<ControlType>checkbox-select</ControlType>
</Attribute>
<Attribute displayed="true">
<Description>Reviewed</Description>
<AttributeSource>reviewed</AttributeSource>
<ControlType>check-display</ControlType>
</Attribute>
<Attribute displayed="true">
<Description>Flag</Description>
<AttributeSource>flag</AttributeSource>
<ControlType>select-1-drop-down</ControlType>
</Attribute>
<Attribute displayed="true">
<Description>Description</Description>
<AttributeSource>DESCR</AttributeSource>
<ControlType>text-display</ControlType>
</Attribute>
<Attribute displayed="true">
<Description>Discipline</Description>
<AttributeSource>FB1T</AttributeSource>
<ControlType>text-display</ControlType>
</Attribute>
<Attribute displayed="true">
<Description>Organ System</Description>
<AttributeSource>U1DT</AttributeSource>
<ControlType>text-display</ControlType>
</Attribute>
<Attribute displayed="true">
<Description>Step 1 outline</Description>
<AttributeSource>FB2</AttributeSource>
<ControlType>text-display</ControlType>
</Attribute>
<!-- Attribute displayed="false"> <Description>Organ System plus</Description> <AttributeSource>ORGA</AttributeSource> <ControlType>text-display</ControlType> </Attribute -->
<Attribute displayed="true">
<Description>Images</Description>
<AttributeSource>PIXN</AttributeSource>
<ControlType>text-display</ControlType>
</Attribute>
<Attribute displayed="true">
<Description>Vignettes</Description>
<AttributeSource>VIG1</AttributeSource>
<ControlType>text-display</ControlType>
</Attribute>
<Attribute displayed="true">
<Description>Diff</Description>
<AttributeSource>pvalue</AttributeSource>
<ControlType>text-display</ControlType>
</Attribute>
<Attribute displayed="true">
<Description>Discr</Description>
<AttributeSource>rbvalue</AttributeSource>
<ControlType>text-display</ControlType>
</Attribute>
<Attribute displayed="true">
<Description>Answer Key</Description>
<AttributeSource>key</AttributeSource>
<ControlType>text-display</ControlType>
</Attribute>
<Attribute displayed="true">
<Description>Notes</Description>
<AttributeSource>notes</AttributeSource>
<ControlType>text-display</ControlType>
</Attribute>
</Attributes>
</ItemList>
<CurrentItemInfo>
<ItemText displayed="true"/>
<ItemData>
<Attribute>
<DataSource>scorecat</DataSource>
<ControlType>select-each-value</ControlType>
</Attribute>
</ItemData>
</CurrentItemInfo>
</DataPanels>
</IRData>
<?BASELINE FB2-A.02.01 on:4 off:3?>
<?BASELINE FB2-A.02.02 on:4 off:4?>
<?BASELINE FB2-A.03.01 on:3 off:1?>
<?BASELINE FB2-A.03.02 on:0 off:1?>
<?BASELINE FB2-A.03.04 on:3 off:2?>
<?BASELINE FB2-A.03.05 on:1 off:0?>
<?BASELINE FB2-A.03.07 on:4 off:2?>
<?BASELINE FB2-A.04.01 on:2 off:5?>
<?BASELINE FB2-A.04.02 on:5 off:3?>
<?BASELINE FB2-A.04.03 on:3 off:1?>
<?BASELINE FB2-A.04.04 on:1 off:1?>
<?BASELINE FB2-A.05.01 on:12 off:14?>
<?BASELINE FB2-A.05.02 on:9 off:1?>
<?BASELINE FB2-A.05.03 on:0 off:6?>
<?BASELINE FB2-A.06.01 on:7 off:9?>
<?BASELINE FB2-A.06.02 on:2 off:6?>
<?BASELINE FB2-A.06.03 on:10 off:5?>
<?BASELINE FB2-A.06.04 on:1 off:1?>
<?BASELINE FB2-A.07 on:23 off:20?> -
When query is taking too long time
When query is taking too long time,Where and how to start tuning it?
Here i've listed few things need to be considered,out of my knowledge and understanding
1.What the sql is waiting for(wait events)
2.Parameter modification need to be done at system/session level
3.The query has to be tuned (using hints )
4.Gathering/deleting statistics
List out any other things that need to be taken into account?
Which approach must be followed and on what basis that approach must be considered?When query is taking too long time,Where and how to start tuning it?explain plan will be good start . trace also
Here i've listed few things need to be considered,out of my knowledge and understanding
1.What the sql is waiting for(wait events)When Oracle executes an SQL statement, it is not constantly executing. Sometimes it has to wait for a specific event to happen befor it can proceed.
Read
http://www.adp-gmbh.ch/ora/tuning/event.html
2.Parameter modification need to be done at system/session levelDepend on parameter , define parameter , trace done on session level for example
3.The query has to be tuned (using hints )Could be help you but you must know how to use .
4.Gathering/deleting statisticsDo it in non working hours , it will impact on database performance , but its good
List out any other things that need to be taken into account?Which account ?
Which approach must be followed and on what basis that approach must be considered?you could use lot of tools , Trace , AWR -
Getting serial number is invalid when trying to install acrobat 9 pro
Hello,
I am getting a message stating that the serial number is invalid when trying to re-install adobe acrobat 9 pro on windows 8. adobe support confirmed that the srial number I am trying to us is valid though. any help is appreciated.Nope,I downloaded the software from adobe website: Download Acrobat products | 9, 8
All it says is "Invalid Serial Number" I already checked with adobe support and they confirmed that the serial number is valid, they won't provide any more help "because acrobat 9 is out of support now". -
I keep getting "Error Subject token invalid" when I try to activate HBO GO on my Apple TV 3.
I keep getting "Error Subject token invalid" when I try to activate HBO GO on my Apple TV 3. Everything else is activating fine. My ISP is XFinity. Anyone seen this? I have done a complete reset and restore, and have the latest software.
Hello dprice3885,
Thanks for using Apple Support Communities.
Take a look at the Wi-Fi troubleshooting since you can access the network but not the content.
Apple TV: Basic troubleshooting
http://support.apple.com/kb/HT6106
Apple TV (2nd and 3rd generation): Troubleshooting Wi-Fi networks and connections
http://support.apple.com/kb/TS4546
Have a nice day,
Mario -
App-v 5.0 SP2 hotfix 5, an error occurred when querying the App-V WMI provider
Hi,
We have installed App-v 5.0 SP2 + hotfix 5 (via SCCM 2012 R2 CU1) on some Windows 7 clients. That worked fine but no app-v applications go through.
Error:
AppVPackageQueryClient5X::GetPackageDataByPackageGUID() failed for virtual application [a835fa1-f82a-4efe-957a-8c6678d4a431]. (0x87d01290) AppVHandler 5/08/2014 10:23:56 3440 (0x0D70)
CAppV5XHandler::DiscoverIndividuleApp() failed. (0x87d01290) AppVHandler 5/08/2014 10:23:56 3440 (0x0D70)
+++ Discovery of application [AppDT Id: ScopeId_8B8D93AF-5181-48FE-9202-2CFE5FC93EE2/DeploymentType_50eba242-3688-4b4f-9b61-84f0123f667d, Revision: 7] returned an error (0x87d01290). AppVHandler 5/08/2014 10:23:56
3440 (0x0D70)
CAppV5XHandler::DiscoverApp() failed. (0x87d01290) AppVHandler 5/08/2014 10:23:56 3440 (0x0D70)
Deployment type detection failed with error 0x87d01290. AppDiscovery 5/08/2014 10:23:56 3440 (0x0D70)
Failed to perform detection of app deployment type Microsoft - Console, revision 6) for user. Error 0x87d01290 AppDiscovery 5/08/2014 10:23:56 3440 (0x0D70)
Error = 0x87d01290 = An error occurred when querying the App-V WMI provider.
Please advise on this specific error. Should we look for corruption in app-v client, problem in sccm client ...?
J.
Jan Hoedt
Update: clients which don't have problems are client which had hotfix 4 THEN hotfix 5 installed. Should we install it that order? Client WITH problems have App-v 5.0 SP2 then hotfix 5 directly.
Update2: I installed the app-v client via setup.exe, the hotfix 4 also via setup.exe but since it installed all language packs, I decided to extract hotfix 5 and use the msp.
Could that be cause of the issue? I could use the exe of hotfix 5 but then I need to be sure how NOT to install all the language packs.I think we found a solution ourselves.
My update2 (question) explains it:
Update2: I installed the app-v client via setup.exe, the hotfix 4 also via setup.exe but since it installed all language packs, I decided to extract hotfix 5 and use the msp.
Could that be cause of the issue? I could use the exe of hotfix 5 but then I need to be sure how NOT to install all the language packs.
We installed App-v 5.0 SP2 via exe then installed hotfix via msp (extracted msp), this doesn't seem to work (though installation was succesfull). When we deploy the hotfix via the exe it works correctly.
Not sure why though.
Jan Hoedt -
Inconsistent SDO_RELATE results when querying 2.5D data
Oracle 11.1.0.7 with Patch 8343061 on Windows Server 2003 32bit.
I'm getting inconsistent results from SDO_RELATE results when querying 2.5D data. Some geometries I expect to be OVERLAPBDYDISJOINT, are not always being returned by SDO_RELATE when using the OVERLAPBDYDISJOINT mask. It seems that the order of the tables makes a difference to the result.
Here's a table with one 2.5D geometry and a 2D index:
CREATE TABLE TEST1 (
ID NUMBER PRIMARY KEY,
GEOMETRY SDO_GEOMETRY);
INSERT INTO TEST1 (id, geometry) VALUES (
1,
SDO_GEOMETRY(3002, 2157, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(561695.935, 834005.726, 25.865,
561696.229, 834005.955, 25.867, 561686.278, 834015.727, 26.088, 561685.179, 834019.771, 26.226, 561680.716, 834022.389, 26.226,
561674.434, 834025.125, 26.171, 561671.963, 834032.137, 25.667, 561670.832, 834037.185, 25.619, 561667.946, 834042.976, 25.84,
561666.717, 834047.218, 26.171, 561664.229, 834051.781, 26.778, 561660.041, 834055.935, 26.64, 561657.514, 834061.742, 26.53,
561658.59, 834067.116, 27.882, 561657.67, 834070.739, 28.821, 561653.028, 834073.777, 29.042, 561653.234, 834078.769, 28.379,
561658.336, 834080.105, 29.511, 561664.582, 834079.468, 31.94, 561669.257, 834075.821, 33.707, 561672.716, 834074.456, 33.707,
561676.875, 834077.262, 33.735, 561675.868, 834081.55, 33.707, 561673.131, 834087.641, 33.679, 561672.208, 834093.502, 33.238,
561668.578, 834100.894, 33.735, 561666.013, 834106.399, 33.679, 561661.408, 834111.23, 33.514, 561654.854, 834117.181, 33.486,
561651.695, 834122.292, 33.569, 561649.112, 834128.847, 33.431, 561645.982, 834134.786, 33.293, 561642.485, 834141.235, 33.072,
561642.138, 834150.085, 33.293, 561646.072, 834159.721, 36.578, 561647.274, 834165.532, 37.02, 561646.359, 834170.867, 37.02,
561645.42, 834175.485, 36.799, 561642.44, 834180.977, 36.826, 561638.677, 834185.419, 36.771, 561636.693, 834194.824, 37.158,
561635.462, 834202.105, 37.241, 561631.998, 834208.745, 37.268, 561628.871, 834213.994, 37.241, 561627.554, 834220.393, 37.82,
561625.79, 834226.697, 39.532, 561620.561, 834236.494, 39.891, 561619.265, 834249.687, 39.697, 561619.883, 834260.02, 41.326,
561620.977, 834264.399, 43.093, 561622.557, 834270.723, 43.452, 561622.172, 834276.978, 43.452, 561621.347, 834285.541, 43.479,
561622.214, 834292.055, 43.645, 561619.718, 834302.583, 43.755, 561616.762, 834316.47, 43.755, 561608.842, 834328.241, 43.7,
561606.346, 834334.93, 43.7, 561605.27, 834341.929, 43.7, 561603.925, 834350.648, 43.728, 561602.462, 834358.405, 43.838,
561599.552, 834366.629, 44.031, 561594.551, 834374.291, 43.396, 561590.644, 834383.986, 43.065, 561588.48, 834392.21, 44.942,
561586.923, 834397.32, 46.737, 561584.608, 834402.898, 49.299, 561581.389, 834410.194, 50.077, 561580.437, 834419.49, 51.907,
561580.438, 834427.63, 53.127, 561582.245, 834433.389, 55.791, 561586.664, 834433.397, 57.503, 561593.88, 834433.608, 57.475,
561596.305,834439.653, 57.42, 561591.804, 834445.862, 57.309, 561589.097, 834447.689, 57.014)));
SELECT sdo_geom.validate_geometry_with_context(geometry, 0.0005) FROM TEST1;
DELETE FROM user_sdo_geom_metadata WHERE table_name = 'TEST1' AND column_name = 'GEOMETRY';
INSERT INTO user_sdo_geom_metadata VALUES ('TEST1','GEOMETRY',
MDSYS.SDO_DIM_ARRAY(
MDSYS.SDO_DIM_ELEMENT('X',400000,750000,0.0005),
MDSYS.SDO_DIM_ELEMENT('Y',500000,1000000,0.0005),
MDSYS.SDO_DIM_ELEMENT('Z',-10000,10000,0.0005)
), 2157);
DROP INDEX TEST1_SPIND;
CREATE INDEX TEST1_SPIND ON TEST1(GEOMETRY) INDEXTYPE IS MDSYS.SPATIAL_INDEX PARAMETERS ('layer_gtype=line sdo_indx_dims=2');And here's another table with a 2D geometry and a 2D index:
CREATE TABLE TEST2 (
ID NUMBER PRIMARY KEY,
GEOMETRY SDO_GEOMETRY);
INSERT INTO TEST2 (id, geometry) VALUES (
1,
SDO_GEOMETRY(2002, 2157, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(561816.516, 834055.581, 561819.504, 834057.173,
561817.942, 834060.818, 561810.044, 834078.997, 561805.576, 834087.634, 561801.572, 834094.299, 561798.558, 834100.467,
561796.254, 834107.637, 561793.754, 834115.605, 561794.049, 834123.694, 561793.698, 834130.518, 561792.905, 834138.883,
561787.867, 834145.772, 561782.544, 834150.548, 561777.707, 834156.53, 561773.945, 834161.32, 561771.061, 834166.957,
561768.155, 834173.131, 561764.735, 834178.744, 561759.603, 834187.782, 561756.146, 834195.493, 561753.416, 834198.821,
561754.141, 834205.691, 561756.768, 834209.681, 561757.217, 834216.701, 561753.086, 834232.46, 561744.371, 834254.589,
561740.936, 834263.001, 561737.198, 834272.208, 561732.231, 834284.915, 561730.52, 834297.01, 561728.339, 834310.053,
561727.825, 834328.069, 561730.461, 834342.992, 561729.808, 834367.948, 561730.216, 834396.988, 561732.273, 834419.047,
561732.783, 834424.668, 561731.647, 834432.212, 561731.872, 834439.436, 561731.39, 834449.269, 561732.041, 834462.813,
561733.583, 834471.926, 561733.229, 834485.049, 561730.868, 834498.462, 561726.379, 834512.59, 561725.776, 834528.932,
561727.488, 834555.23, 561729.357, 834577.873, 561731.05, 834595.931, 561731.163, 834611.928, 561734.057, 834637.031,
561732.67, 834636.4, 561725.401, 834633.796, 561721.039, 834632.493, 561718.777, 834632.167, 561710.437, 834632.888,
561647.929, 834636.658, 561644.963, 834630.085, 561632.796, 834629.813, 561625.553, 834627.647, 561620.473, 834626.711,
561608.718, 834624.94, 561599.935, 834619.684, 561596.67, 834613.843, 561594.27, 834607.774, 561592.513, 834601.752,
561591.349, 834593.899, 561597.265, 834584.888, 561595.956, 834571.479, 561595.075, 834556.196, 561593.997, 834539.68,
561594.316, 834528.071, 561595.261, 834516.44, 561595.538, 834504.804, 561597.227, 834497.417, 561599.3, 834490.416,
561601.265, 834482.61, 561605.126, 834475.502, 561599.232, 834473.683, 561593.076, 834471.379, 561599.154, 834451.112,
561589.097, 834447.689, 561591.804, 834445.862, 561596.305, 834439.653, 561593.88, 834433.608, 561582.245, 834433.389,
561580.438, 834427.63, 561580.437, 834419.49, 561581.389, 834410.194, 561584.608, 834402.898, 561586.923, 834397.32,
561588.48, 834392.21, 561590.644, 834383.986, 561594.551, 834374.291, 561599.552, 834366.629, 561602.462, 834358.405,
561603.925, 834350.648, 561605.27, 834341.929, 561606.346, 834334.93, 561608.842, 834328.241, 561616.762, 834316.47,
561619.718, 834302.583, 561622.214, 834292.055, 561621.347, 834285.541, 561622.172, 834276.978, 561622.557, 834270.723,
561620.977, 834264.399, 561619.883, 834260.02, 561619.265, 834249.687, 561620.561, 834236.494, 561625.79, 834226.697,
561627.554, 834220.393, 561628.871, 834213.994, 561631.998, 834208.745, 561635.462, 834202.105, 561636.693, 834194.824,
561638.677, 834185.419, 561642.44, 834180.977, 561645.42, 834175.485, 561646.359, 834170.867, 561647.274, 834165.532,
561646.072, 834159.721, 561642.138, 834150.085, 561642.485, 834141.235, 561645.982, 834134.786, 561649.112, 834128.847,
561651.695, 834122.292, 561654.854, 834117.181, 561661.408, 834111.23, 561666.013, 834106.399, 561668.578, 834100.894,
561672.208, 834093.502,561673.131, 834087.641, 561675.868, 834081.55, 561676.875, 834077.262, 561672.716, 834074.456,
561669.257, 834075.821, 561664.582, 834079.468, 561658.336, 834080.105, 561653.234, 834078.769, 561653.028, 834073.777,
561657.67, 834070.739, 561658.59, 834067.116, 561657.514, 834061.742, 561660.041, 834055.935, 561664.229, 834051.781,
561666.717, 834047.218, 561667.946, 834042.976, 561670.832, 834037.185, 561671.963, 834032.137, 561674.434, 834025.125,
561680.716, 834022.389, 561685.179, 834019.771, 561686.278, 834015.727, 561696.229, 834005.955, 561695.935, 834005.726,
561677.805, 833994.91, 561683.163, 833985.817, 561703.01, 833949.434, 561725.891, 833961.856, 561744.35, 833971.197,
561768.396, 833983.86, 561777.842, 833988.883, 561798.333, 833999.743, 561797.243, 834005.725, 561783.574, 834040.515,
561798.127, 834046.391, 561807.001, 834050.509, 561816.516, 834055.581)));
SELECT sdo_geom.validate_geometry_with_context(geometry, 0.0005) FROM TEST2;
DELETE FROM user_sdo_geom_metadata WHERE table_name = 'TEST2' AND column_name = 'GEOMETRY';
INSERT INTO user_sdo_geom_metadata VALUES ('TEST2','GEOMETRY',
MDSYS.SDO_DIM_ARRAY(
MDSYS.SDO_DIM_ELEMENT('X',400000,750000,0.0005),
MDSYS.SDO_DIM_ELEMENT('Y',500000,1000000,0.0005)
), 2157);
DROP INDEX TEST2_SPIND;
CREATE INDEX TEST2_SPIND ON TEST2(GEOMETRY) INDEXTYPE IS MDSYS.SPATIAL_INDEX PARAMETERS ('layer_gtype=line sdo_indx_dims=2');Now if I check how these two geometries relate to each other, the answer is OVERLAPBDYDISJOINT, which makes sense when inspecting the geometries.
SQL> SELECT
2 sdo_geom.relate(t1.geometry, 'determine', t2.geometry, 0.0005) relate_1_to_2,
3 sdo_geom.relate(t2.geometry, 'determine', t1.geometry, 0.0005) relate_2_to_1
4 FROM test2 t2, test1 t1
5 WHERE t1.id = t2.id;
RELATE_1_TO_2 RELATE_2_TO_1
OVERLAPBDYDISJOINT OVERLAPBDYDISJOINT
1 row selected.So, I'd expect this query to return something...
SELECT /*+ ORDERED */ t1.id, t2.id, sdo_geom.relate(t1.geometry, 'determine', t2.geometry, 0.0005) relate
FROM test2 t2, test1 t1
WHERE sdo_relate(t1.geometry, t2.geometry, 'mask=overlapbdydisjoint') = 'TRUE'
AND t1.id = 1
AND t2.id = 1;Nada. And this...
SELECT /*+ ORDERED */ t1.id, t2.id, sdo_geom.relate(t1.geometry, 'determine', t2.geometry, 0.0005) relate
FROM test1 t1, test2 t2
WHERE sdo_relate(t2.geometry, t1.geometry, 'mask=overlapbdydisjoint') = 'TRUE'
AND t1.id = 1
AND t2.id = 1;Nada.
And this...
SQL> SELECT /*+ ORDERED */ t1.id, t2.id, sdo_geom.relate(t1.geometry, 'determine', t2.geometry, 0.0005) relate
2 FROM test2 t2, test1 t1
3 WHERE sdo_relate(t2.geometry, t1.geometry, 'mask=overlapbdydisjoint') = 'TRUE'
4 AND t1.id = 1
5 AND t2.id = 1;
ID ID RELATE
1 1 OVERLAPBDYDISJOINT
1 row selected.This version gives the right answer.
Can anyone explain this?Hi,-
I think you are running into these bugs 7158518 and 7710726.
Could you please request the patch for the bugs so that they are published on Metalink
if they dont exist there?
Please let us know if these fix your problem.
Best regards
baris -
In forms 4.5 when query record assigning value is possible?How?
Hi all,
when query record ,depending on condition i can assign value.
I done but it give error first delete or create record error?
How can i overcome this problem.
Thanks
venkata.IF v_value = 'Y'
THEN
lvl$std.copy_number(0,'BLK1.V_ITEM_NAME1');
ND IF;
I written in post-query.What does
lvl$std.copy_number(0,'BLK1.V_ITEM_NAME1');do that
:blk1.v_item_name1 := 0;doesn't? -
Strange explain plan when query SYS tables
Oracle Version 9.2.0.7
We have an application that runs the following query on Oracle 9.2.0.7
SELECT T1.TABLE_NAME,T1.COLUMN_NAME, T1.SRID, T2.SDO_UB, T2.SDO_LB, T1.OWNER FROM ALL_SDO_GEOM_METADATA T1, TABLE(T1.DIMINFO) T2 WHERE T1.OWNER=UPPER(:"SYS_B_0") AND T1.TABLE_NAME=UPPER(:"SYS_B_1")
Without the self join the query is fine, but with the self join on our customers database the explain plan is doing full table scans and Hash Joins on SYS tables and takes 2 minutes.
Rows Row Source Operation
2 FILTER
2 NESTED LOOPS
1 TABLE ACCESS FULL SDO_GEOM_METADATA_TABLE
2 COLLECTION ITERATOR PICKLER FETCH
1 UNION-ALL
0 FILTER
0 NESTED LOOPS OUTER
0 HASH JOIN
37 TABLE ACCESS FULL TS$
0 HASH JOIN OUTER
0 NESTED LOOPS OUTER
0 NESTED LOOPS OUTER
0 NESTED LOOPS
1 NESTED LOOPS
1 TABLE ACCESS BY INDEX ROWID USER$
1 INDEX UNIQUE SCAN I_USER1 (object id 44)
1 TABLE ACCESS BY INDEX ROWID OBJ$
1 INDEX RANGE SCAN I_OBJ2 (object id 37)
0 TABLE ACCESS CLUSTER TAB$
1 INDEX UNIQUE SCAN I_OBJ# (object id 3)
0 TABLE ACCESS CLUSTER SEG$
0 INDEX UNIQUE SCAN I_FILE#_BLOCK# (object id 9)
0 TABLE ACCESS BY INDEX ROWID OBJ$
0 INDEX UNIQUE SCAN I_OBJ1 (object id 36)
0 TABLE ACCESS FULL USER$
0 INDEX UNIQUE SCAN I_OBJ1 (object id 36)
0 NESTED LOOPS
0 FIXED TABLE FULL X$KZSRO
0 INDEX RANGE SCAN I_OBJAUTH2 (object id 109)
0 FIXED TABLE FULL X$KZSPR
0 FILTER
0 NESTED LOOPS OUTER
0 HASH JOIN
54 TABLE ACCESS FULL USER$
0 HASH JOIN
29447 TABLE ACCESS FULL OBJ$
0 HASH JOIN OUTER
0 HASH JOIN OUTER
0 HASH JOIN OUTER
0 NESTED LOOPS
0 NESTED LOOPS OUTER
0 NESTED LOOPS OUTER
0 NESTED LOOPS
0 NESTED LOOPS
0 NESTED LOOPS
1 NESTED LOOPS
1 TABLE ACCESS BY INDEX ROWID USER$
1 INDEX UNIQUE SCAN I_USER1 (object id 44)
1 TABLE ACCESS BY INDEX ROWID OBJ$
1 INDEX RANGE SCAN I_OBJ2 (object id 37)
0 TABLE ACCESS CLUSTER TAB$
1 INDEX UNIQUE SCAN I_OBJ# (object id 3)
0 TABLE ACCESS CLUSTER TS$
0 INDEX UNIQUE SCAN I_TS# (object id 7)
0 TABLE ACCESS CLUSTER COL$
0 TABLE ACCESS CLUSTER SEG$
0 INDEX UNIQUE SCAN I_FILE#_BLOCK# (object id 9)
0 TABLE ACCESS BY INDEX ROWID OBJ$
0 INDEX UNIQUE SCAN I_OBJ1 (object id 36)
0 TABLE ACCESS CLUSTER COLTYPE$
0 TABLE ACCESS FULL USER$
0 TABLE ACCESS FULL OBJ$
0 TABLE ACCESS FULL USER$
0 INDEX UNIQUE SCAN I_OBJ1 (object id 36)
0 NESTED LOOPS
0 FIXED TABLE FULL X$KZSRO
0 INDEX RANGE SCAN I_OBJAUTH2 (object id 109)
0 FIXED TABLE FULL X$KZSPR
1 FILTER
1 NESTED LOOPS
1 NESTED LOOPS OUTER
1 NESTED LOOPS
1 TABLE ACCESS BY INDEX ROWID USER$
1 INDEX UNIQUE SCAN I_USER1 (object id 44)
1 TABLE ACCESS BY INDEX ROWID OBJ$
1 INDEX RANGE SCAN I_OBJ2 (object id 37)
0 INDEX UNIQUE SCAN I_TYPED_VIEW1 (object id 105)
1 INDEX UNIQUE SCAN I_VIEW1 (object id 104)
0 NESTED LOOPS
0 FIXED TABLE FULL X$KZSRO
0 INDEX RANGE SCAN I_OBJAUTH2 (object id 109)
0 FIXED TABLE FULL X$KZSPR
On our development database it takes 0.07 sec with no full table scans and no hash joins.
Rows Row Source Operation
2 NESTED LOOPS
1 TABLE ACCESS BY INDEX ROWID SDO_GEOM_METADATA_TABLE
1 INDEX RANGE SCAN SDO_GEOM_IDX (object id 36753)
1 UNION-ALL
0 FILTER
0 NESTED LOOPS
0 NESTED LOOPS OUTER
0 NESTED LOOPS OUTER
0 NESTED LOOPS OUTER
0 NESTED LOOPS OUTER
0 NESTED LOOPS
1 NESTED LOOPS
1 TABLE ACCESS BY INDEX ROWID USER$
1 INDEX UNIQUE SCAN I_USER1 (object id 44)
1 TABLE ACCESS BY INDEX ROWID OBJ$
1 INDEX RANGE SCAN I_OBJ2 (object id 37)
0 TABLE ACCESS CLUSTER TAB$
1 INDEX UNIQUE SCAN I_OBJ# (object id 3)
0 TABLE ACCESS BY INDEX ROWID OBJ$
0 INDEX UNIQUE SCAN I_OBJ1 (object id 36)
0 INDEX UNIQUE SCAN I_OBJ1 (object id 36)
0 TABLE ACCESS CLUSTER USER$
0 INDEX UNIQUE SCAN I_USER# (object id 11)
0 TABLE ACCESS CLUSTER SEG$
0 INDEX UNIQUE SCAN I_FILE#_BLOCK# (object id 9)
0 TABLE ACCESS CLUSTER TS$
0 INDEX UNIQUE SCAN I_TS# (object id 7)
0 NESTED LOOPS
0 FIXED TABLE FULL X$KZSRO
0 INDEX RANGE SCAN I_OBJAUTH2 (object id 109)
0 FIXED TABLE FULL X$KZSPR
0 FILTER
0 NESTED LOOPS
0 NESTED LOOPS
0 NESTED LOOPS OUTER
0 NESTED LOOPS OUTER
0 NESTED LOOPS OUTER
0 NESTED LOOPS OUTER
0 NESTED LOOPS OUTER
0 NESTED LOOPS OUTER
0 NESTED LOOPS
0 NESTED LOOPS
0 NESTED LOOPS
0 NESTED LOOPS
1 NESTED LOOPS
1 TABLE ACCESS BY INDEX ROWID USER$
1 INDEX UNIQUE SCAN I_USER1 (object id 44)
1 TABLE ACCESS BY INDEX ROWID OBJ$
1 INDEX RANGE SCAN I_OBJ2 (object id 37)
0 TABLE ACCESS CLUSTER TAB$
1 INDEX UNIQUE SCAN I_OBJ# (object id 3)
0 TABLE ACCESS CLUSTER TS$
0 INDEX UNIQUE SCAN I_TS# (object id 7)
0 TABLE ACCESS CLUSTER COL$
0 TABLE ACCESS CLUSTER COLTYPE$
0 TABLE ACCESS CLUSTER SEG$
0 INDEX UNIQUE SCAN I_FILE#_BLOCK# (object id 9)
0 TABLE ACCESS BY INDEX ROWID OBJ$
0 INDEX UNIQUE SCAN I_OBJ1 (object id 36)
0 TABLE ACCESS CLUSTER USER$
0 INDEX UNIQUE SCAN I_USER# (object id 11)
0 TABLE ACCESS BY INDEX ROWID OBJ$
0 INDEX UNIQUE SCAN I_OBJ1 (object id 36)
0 TABLE ACCESS CLUSTER USER$
0 INDEX UNIQUE SCAN I_USER# (object id 11)
0 INDEX UNIQUE SCAN I_OBJ1 (object id 36)
0 TABLE ACCESS BY INDEX ROWID OBJ$
0 INDEX RANGE SCAN I_OBJ3 (object id 38)
0 TABLE ACCESS CLUSTER USER$
0 INDEX UNIQUE SCAN I_USER# (object id 11)
0 NESTED LOOPS
0 FIXED TABLE FULL X$KZSRO
0 INDEX RANGE SCAN I_OBJAUTH2 (object id 109)
0 FIXED TABLE FULL X$KZSPR
1 FILTER
1 NESTED LOOPS
1 NESTED LOOPS OUTER
1 NESTED LOOPS
1 TABLE ACCESS BY INDEX ROWID USER$
1 INDEX UNIQUE SCAN I_USER1 (object id 44)
1 TABLE ACCESS BY INDEX ROWID OBJ$
1 INDEX RANGE SCAN I_OBJ2 (object id 37)
0 INDEX UNIQUE SCAN I_TYPED_VIEW1 (object id 105)
1 INDEX UNIQUE SCAN I_VIEW1 (object id 104)
0 NESTED LOOPS
0 FIXED TABLE FULL X$KZSRO
0 INDEX RANGE SCAN I_OBJAUTH2 (object id 109)
0 FIXED TABLE FULL X$KZSPR
2 COLLECTION ITERATOR PICKLER FETCH
ALL_SDO_GEOM_METADATA is a view in the MDSYS schema (generated by Oracle ).
SELECT SDO_OWNER OWNER,
SDO_TABLE_NAME TABLE_NAME,
SDO_COLUMN_NAME COLUMN_NAME,
SDO_DIMINFO DIMINFO,
SDO_SRID SRID
FROM SDO_GEOM_METADATA_TABLE
WHERE
(exists
(select table_name from all_tables
where table_name=sdo_table_name
and owner = sdo_owner
union all
select table_name from all_object_tables
where table_name=sdo_table_name
and owner = sdo_owner
union all
select view_name table_name from all_views
where view_name=sdo_table_name
and owner = sdo_owner))
Statistics have been gathered for the MDSYS user.
If this had not been SYS schema I would have immediately concluded that fresh statistics are required. The SYS objects concerend are valid with all indexes
From my understanding you are not meant to gather stats for the SYS schema in Oracle 9 as Data Dictionary queries still uses RBO?
Any ideas as to why Oracle is doing full table scans when querying SYS tables? The optimizer_mode is set to FIRST_ROWS.
Any ideas greatly recevied.
ThanksMaybe I'm missing something but this:
INDEX FULL SCAN SISESTAT I0_ESTRUTURA_COMERCIALindicates that one of those indexes is being used.
This:
T_ESTRUTURA_COMERCIALIs nowhere to be found in your Explain Plan. It appears that either you have posted the wrong plan
or Oracle is doing a query rewrite to a materialized view. -
ORA-00604 ORA-00904 When query partitioned table with partitioned indexes
Got ORA-00604 ORA-00904 When query partitioned table with partitioned indexes in the data warehouse environment.
Query runs fine when query the partitioned table without partitioned indexes.
Here is the query.
SELECT al2.vdc_name, al7.model_series_name, COUNT (DISTINCT (al1.vin)),
al27.accessory_code
FROM vlc.veh_vdc_accessorization_fact al1,
vlc.vdc_dim al2,
vlc.model_attribute_dim al7,
vlc.ppo_list_dim al18,
vlc.ppo_list_indiv_type_dim al23,
vlc.accy_type_dim al27
WHERE ( al2.vdc_id = al1.vdc_location_id
AND al7.model_attribute_id = al1.model_attribute_id
AND al18.mydppolist_id = al1.ppo_list_id
AND al23.mydppolist_id = al18.mydppolist_id
AND al23.mydaccytyp_id = al27.mydaccytyp_id
AND ( al7.model_series_name IN ('SCION TC', 'SCION XA', 'SCION XB')
AND al2.vdc_name IN
('PORT OF BALTIMORE',
'PORT OF JACKSONVILLE - LEXUS',
'PORT OF LONG BEACH',
'PORT OF NEWARK',
'PORT OF PORTLAND'
AND al27.accessory_code IN ('42', '43', '44', '45')
GROUP BY al2.vdc_name, al7.model_series_name, al27.accessory_codeI would recommend that you post this at the following OTN forum:
Database - General
General Database Discussions
and perhaps at:
Oracle Warehouse Builder
Warehouse Builder
The Oracle OLAP forum typically does not cover general data warehousing topics.
Maybe you are looking for
-
System hang after when try to run report from a form
Hi all, I was able to run the report by using the run_report command from form builder to call a report with any problem. However, when I attached in my application, the form is being call out but when try to click on the print button from the form,
-
Should've asked this the first day the trade promo was going on but....
Question: In the verbiage for the PS4 trade and save promo you have going on now the headline for the promo on the PS4 page says you get $175 in GIFT CARDS. But in the fine print it says you get a 'minimum $100 gift card' an a $75 coupon towards a PS
-
Tel Nav update error msg "JVM Error 545"
dowloaded tel nav update and after re boot rcvd subject msg on a white screen background and device completely frozen. Several resets and no change.
-
How do you label photos using ios8
Can you label photos in ios 8. Add metadata, etc.
-
New Features/functionalities in ERP6 withEHP4 SP5 when comparedto ECC6 SP11
Hi , My current version is ECC6.0 SP11. We are looking forward to Upgrade to ERP 6 with EHP 4 SP5 / SAP NW 7.01 SP5. Kindly please let me know the new features or functionalities of my new version when compared to my current version. Regards Harish