ORA-904 and star transformation

Hi,
We have oracle 10.2.0.4 with most recent patches.
When I run the following sql statement I got an ORA-00904: "DT"."SID_0FISCYEAR": invalid identifier
If I drop an index on /BIC/EZYEE_SDLT table on SID_0FISCPER column the sql statement run without error !
IS it an Oracle bug ?
SELECT /*+ STAR_TRANSFORMATION FACT(F) */ "S39"."COSTCENTER" AS "0COSTCENTER" ,"S40"."COMPANY" AS "0COMPANY" ,
"S41"."COMP_CODE" AS "0COMP_CODE" ,"S42"."CS_PLEVEL" AS "0CS_PLEVEL" ,"S43"."FISCPER" AS "0FISCPER" ,
LPAD("DT"."SID_0FISCPER3",000003, 0 ) AS "0FISCPER3" ,"S44"."FISCYEAR" AS "0FISCYEAR" ,
"S45"."COMPANY" AS "0PCOMPANY" ,"S46"."/BIC/ZBPSADJT" AS "ZBPSADJT" ,"S47"."/BIC/ZENT" AS "ZENT" ,
"S48"."/BIC/ZMEASURE1" AS "ZMEASURE1" ,"S49"."/BIC/ZTPBU0" AS "ZTPBU0" ,"S50"."/BIC/ZVAR_IND" AS "ZVAR _IND" ,
"S51"."/BIC/ZYEEDESC" AS "ZYEEDESC" , SUM ( "F"."AMOUNT" ) AS "0AMOUNT" , COUNT( * ) AS " 1ROWCOUNT"
FROM "/BIC/EZYEE_SDLT" "F" JOIN "/BIC/DZYEE_SDLT2" "D2" ON "F" . "KEY_ZYEE_SDLT2" = "D2"."DIMID" JOIN "/BI0/SCOSTCENTER" "S39"
ON "D2" . "SID_0COSTCENTER" = "S39" . "SID" JOIN "/BI0/SCOMPANY" "S40" ON "D2" . "SID_0COMPANY" = "S40" . "SID" JOIN "/BI0/SCOMP_CODE" "S41"
ON "D2" . "SID_0COMP_CODE" = "S41" . "SID" JOIN "/BIC/SZENT" "S47" ON "D2" . "SID_ZENT" = "S47" . "SID" JOIN "/BIC/DZYEE_SDLT6" "D6"
ON "F" . "KEY_ZYEE_SDLT6" = "D6" . "DIMID" JOIN "/BI0/SCS_PLEVEL" "S42"
ON "D6" . "SID_0CS_PLEVEL" = "S42" . "SID" JOIN "/BIC/SZBPSADJT" "S46" ON "D6" . "SID_ZBPSADJT" = "S46" . "SID" JOIN "/BIC/DZYEE_SDLTT" "DT"
ON "F" . "KEY_ZYEE_SDLTT" = "DT" . "DIMID" AND "F" . "SID_0FISCPER" = "DT" . "SID_0FISCPER" JOIN "/BI0/SFISCPER" "S43"
ON "DT" . "SID_0FISCPER" = "S43" . "SID" JOIN "/BI0/SFISCYEAR" "S44" ON "DT" . "SID_0FISCYEAR" = "S44" . "SID" JOIN "/BIC/DZYEE_SDLT1" "D1"
ON "F" . "KEY_ZYEE_SDLT1" = "D1" . "DIMID" JOIN "/BI0/SCOMPANY" "S45" ON "D1" . "SID_0PCOMPANY" = "S45" . "SID" JOIN "/BIC/SZTPBU0" "S49"
ON "D1" . "SID_ZTPBU0" = "S49" . "SID" JOIN "/BIC/DZYEE_SDLT3" "D3" ON "F" . "KEY_ZYEE_SDLT3" = "D3" . "DIMID" JOIN "/BIC/SZMEASURE1" "S48"
ON "D3" . "SID_ZMEASURE1" = "S48" . "SID" JOIN "/BIC/SZVAR_IND" "S50" ON "D3" . "SID_ZVAR_IND" = "S50" . "SID" JOIN "/BIC/SZYEEDESC" "S51"
ON "D3" . "SID_ZYEEDESC" = "S51" . "SID" JOIN "/BIC/DZYEE_SDLTP" "DP" ON "F" . "KEY_ZYEE_SDLTP" = "DP" . "DIMID" JOIN "/BIC/DZYEE_SDLTU" "DU"
ON "F" . "KEY_ZYEE_SDLTU" = "DU" . "DIMID" JOIN "/BIC/DZYEE_SDLT5" "D5" ON "F" . "KEY_ZYEE_SDLT5" = "D5" . "DIMID"
WHERE ( ( ( ( "DP"."SID_0CHNGID" = 0 ) ) AND ( ( "D2"."SID_0CO_AREA" = 3 ) ) AND ( ( "DU"."SID_0CURRENCY" = 31 ) )
AND ( ( "DP"."SID_0RECORDTP" = 0 ) ) AND ( ( "DP"."SID_0REQUID" <= 2000000250 ) ) AND ( ( "D5"."SID_0VERSION" = 1058 ) )
AND ( ( "D5"."SID_ZACTYEAR" = 20002009 ) ) AND ( ( "D5"."SID_ZSCENARIO" = 88 ) ) ) )
GROUP BY "S39"."COSTCENTER" ,"S40"."COMPANY" ,"S41"."COMP_CODE" ,"S42"."CS_PLEVEL" ,"S43"."FISCPER" ,"DT"."SID_0FISCPER3" ,"S44"."FISCYEAR" ,"S45"."COMPANY" ,"S46"."/BIC/ZBPSADJT" ,"S47"."/BIC/ZENT" ,"S48"."/BIC/ZMEASURE1" ,"S49"."/BIC/ZTPBU0" ,"S50"."/BIC/ZVAR_IND" ,"S51"."/BIC/ZYEEDESC";
Thank you for your help.
Maniss

Hi sanjay,
It not a column name problem or a typo because when I run the same sql statement after I remove the index I don't get the error
Thanks,
Maniss

Similar Messages

Risky enable star transformations and trusted Query Rewrites?

Hi,
I need some advice/opinions from someone experienced with large scale
data warehousing.
I'm working on a fairly large data warehouse (around 3 TB), and we're
using Oracle 10.1.0.2.0.
So, I found out about MV's and Star Transformations, and that we're not
using them.
Naturally I decided to try them out in our test environment and I was
more than pleased (actually, I nearly wet my pants) with the potential
performance boost we could get for some of our more critical solutions.
However, I also noticed that the production environment has the
following settings:
star_transformation_enabled = false
query_rewrite_integrity = enforced
...which basically disables all the cool stuff. In the testing
environment I used the following:
star_transformation_enabled = true
query_rewrite_integrity = trusted (to make use of func. dep in
dimensions)
I would like to stand on somewhat solid grounds and increase my
understanding before aproaching our DBA's with the suggestion to change
system global settings :)
Basically, my question(s) are:
1. What are the impact of enabling Star Transformations on a system?
Is there any at all, if no previous solution has been built in a way
to
make use of star transformations?
Or could this change result in fine-tuned queries performing badly
since they
suddenly make use of star transformations?
2. Is "query_rewrite_integrity" used by Oracle for other things besides
Materialized Views?
I'm thinking, if the only thing it's used for is to resolve query
rewrites for MV's, then it's safe to change it, because there are no
such MV's.
Note that I'd like to set it to TRUSTED, in order to make real use
of the dependencies declared with CREATE DIMENSION...
I would be happy to know what you think about this.
Any thoughts, opinions are welcome since this is new grounds for me.
Best Regards
R.

Following parameters are deprecated in release 10.2.
LOGMNR_MAX_PERSISTENT_SESSIONS
MAX_COMMIT_PROPAGATION_DELAY
REMOTE_ARCHIVE_ENABLE
SERIAL_REUSE
SQL_TRACE
Check this in your parameter file.
As per Oracle Errors Documents.
Error : ORA-32004
Cause:     One or more obsolete and/or parameters were specified in the
     SPFILE or the PFILE on the server side.
Action:     See alert log for a list of parameters that are obsolete. or
     deprecated. Remove them from the SPFILE or the server side PFILE
Regards,
Sabdar Syed.

Star transformation and Partition pruning

All experts,
I need advice on my situation -
I have data warehouse running on oracle 11.2.0.1
We are using star trnasformation. The fact table is partitioned.
However, with the star query (fact joined to dimensions with keys and filters only on dimensions), partition pruning is not happening.
I read some documents online and it seems that partition pruning is not going to happen unless I directly filter fact (which is against the best paractices of star query).
Please advice

SELECT
PTL_EDW.D_TIME.CAL_YYYYMM,
(( ( ( sum(PTL_EDWPERF.F_JOB_OIL_COST.LABOR_COST) )+( sum(PTL_EDWPERF.F_JOB_OIL_COST.OUTSIDE_COST) )+( sum(PTL_EDWPERF.F_JOB_OIL_COST.PARTS_COST) ) )-( ( sum(PTL_EDWPERF.F_JOB_OIL_COST.RECOVERY_LABOR_AMOUNT) )+( sum(PTL_EDWPERF.F_JOB_OIL_COST.RECOVERY_OUTSIDE_AMOUNT) )+( sum(PTL_EDWPERF.F_JOB_OIL_COST.RECOVERY_PARTS_AMOUNT) ) )+( ( sum(PTL_EDWPERF.F_JOB_OIL_COST.WARRANTY_LABOR_AMOUNT) )+( sum(PTL_EDWPERF.F_JOB_OIL_COST.WARRANTY_OUTSIDE_AMOUNT) )+( sum(PTL_EDWPERF.F_JOB_OIL_COST.WARRANTY_PARTS_AMOUNT) ) ) )+( sum(PTL_EDWPERF.F_JOB_OIL_COST.OIL_COST) ))
FROM
PTL_EDWPERF.F_JOB_OIL_COST,
PTL_EDW.D_LOCATION_MASTER D_LOCATION_DOMICILE,
PTL_EDW.D_VEHICLE_CAP_STATUS,
PTL_EDW.D_UNIT_MASTER,
PTL_EDW.D_ACCOUNT_CODE,
PTL_EDW.D_TIME
WHERE
( PTL_EDWPERF.F_JOB_OIL_COST.ACCOUNT_CODE_KEY = PTL_EDW.D_ACCOUNT_CODE.ACCOUNT_CODE_KEY)
AND ( PTL_EDWPERF.F_JOB_OIL_COST.VEHICLE_CAP_STATUS_KEY=PTL_EDW.D_VEHICLE_CAP_STATUS.VEHICLE_CAP_STATUS_KEY )
AND ( PTL_EDWPERF.F_JOB_OIL_COST.CHARGING_LOCATION_KEY=D_LOCATION_DOMICILE.LOCATION_MASTER_KEY )
AND (PTL_EDWPERF.F_JOB_OIL_COST.UNIT_MASTER_KEY = PTL_EDW.D_UNIT_MASTER.UNIT_MASTER_KEY)
AND (PTL_EDWPERF.F_JOB_OIL_COST.RO_ACCOUNTING_MONTH_KEY = PTL_EDW.D_TIME.TIME_KEY)
AND ( exists (select 1 from ptl_edw.s_location where s_location.ssoid = '600028988' and PTL_EDWPERF.F_JOB_OIL_COST.CHARGING_LOCATION_KEY = decode(s_location.location_master_key, -99999, PTL_EDWPERF.F_JOB_OIL_COST.CHARGING_LOCATION_KEY, s_location.location_master_key)) )
AND
--PTL_EDWPERF.F_JOB_OIL_COST.PARTITION_KEY BETWEEN 201011 AND 201104
PTL_EDW.D_TIME.CAL_YYYYMM BETWEEN 200601 AND 201104
AND
D_LOCATION_DOMICILE.CORP_CD IN ( '2000','HPTL' )
AND
( ( PTL_EDW.D_VEHICLE_CAP_STATUS.VEHICLE_CAP_STATUS ) IN ( 'ACCRUED','ACTIVE' ) )
AND
( PTL_EDW.D_UNIT_MASTER.CONTRACT_GROUP = 'P' )
AND
PTL_EDW.D_UNIT_MASTER.UNIT_CATEGORY IN ( 'TRACTOR','TRAILER','TRUCK' )
AND
PTL_EDW.D_ACCOUNT_CODE.ACCOUNT_CODE_GROUP1 IN ( 'COMMERCIAL RENTAL','CONTRACT MAINTENANCE - GUAR','CONTRACT MAINTENANCE - OTHER','CONTRACT MAINTENANCE - PEG','LEASE','TRAILER PLUS' )
GROUP BY
PTL_EDW.D_TIME.CAL_YYYYMM
-- bg4643wj2d3xn
=====================================
Elapsed: 00:39:35.08
Execution Plan
Plan hash value: 2317670688
| Id | Operation | Name | Rows | Bytes |TempSpc| Cost (%CPU)| Time | Pstart| Pstop |
| 0 | SELECT STATEMENT | | 9 | 666 | | 186K (1)| 00:43:36 | | |
| 1 | HASH GROUP BY | | 9 | 666 | | 186K (1)| 00:43:36 | | |
|* 2 | FILTER | | | | | | | | |
|* 3 | HASH JOIN | | 557K| 39M| | 186K (1)| 00:43:35 | | |
|* 4 | VIEW | index$_join$_006 | 1925 | 19250 | | 16 (7)| 00:00:01 | | |
|* 5 | HASH JOIN | | | | | | | | |
|* 6 | INDEX RANGE SCAN | D_TIME_CALYYYYMM_IDX2 | 1925 | 19250 | | 5 (20)| 00:00:01 | | |
| 7 | INDEX FAST FULL SCAN | D_TIME_TIME_KEY_PK | 1925 | 19250 | | 14 (0)| 00:00:01 | | |
|* 8 | HASH JOIN | | 557K| 34M| 32M| 186K (1)| 00:43:34 | | |
| 9 | PARTITION RANGE ALL | | 557K| 26M| | 131K (1)| 00:30:46 | 1 | 133 |
| 10 | TABLE ACCESS BY LOCAL INDEX ROWID| F_JOB_OIL_COST | 557K| 26M| | 131K (1)| 00:30:46 | 1 | 133 |
| 11 | BITMAP CONVERSION TO ROWIDS | | | | | | | | |
| 12 | BITMAP AND | | | | | | | | |
| 13 | BITMAP MERGE | | | | | | | | |
| 14 | BITMAP KEY ITERATION | | | | | | | | |
| 15 | BUFFER SORT | | | | | | | | |
|* 16 | VIEW | index$_join$_179 | 2 | 20 | | 2 (50)| 00:00:01 | | |
|* 17 | HASH JOIN | | | | | | | | |
| 18 | INLIST ITERATOR | | | | | | | | |
|* 19 | INDEX UNIQUE SCAN | D_CAPSTS_ETL_IDX | 2 | 20 | | 0 (0)| 00:00:01 | | |
| 20 | INDEX FAST FULL SCAN | D_VEHICLE_CAP_STATUS_PK | 2 | 20 | | 1 (0)| 00:00:01 | | |
|* 21 | BITMAP INDEX RANGE SCAN | BIMAP_JOBOIL_COST_VEH_CAP_KY | | | | | | 1 | 133 |
| 22 | BITMAP MERGE | | | | | | | | |
| 23 | BITMAP KEY ITERATION | | | | | | | | |
| 24 | BUFFER SORT | | | | | | | | |
|* 25 | TABLE ACCESS FULL | D_TIME | 1925 | 51975 | | 19 (6)| 00:00:01 | | |
|* 26 | BITMAP INDEX RANGE SCAN | BIMAP_JOBOIL_CST_RO_ACC_MTH_KY | | | | | | 1 | 133 |
| 27 | BITMAP MERGE | | | | | | | | |
| 28 | BITMAP KEY ITERATION | | | | | | | | |
| 29 | BUFFER SORT | | | | | | | | |
|* 30 | TABLE ACCESS FULL | D_ACCOUNT_CODE | 11 | 165 | | 4 (0)| 00:00:01 | | |
|* 31 | BITMAP INDEX RANGE SCAN | BIMAP_JOBOIL_COST_ACCT_CODE_KY | | | | | | 1 | 133 |
| 32 | BITMAP MERGE | | | | | | | | |
| 33 | BITMAP KEY ITERATION | | | | | | | | |
| 34 | BUFFER SORT | | | | | | | | |
|* 35 | VIEW | index$_join$_172 | 3136 | 28224 | | 19 (6)| 00:00:01 | | |
|* 36 | HASH JOIN | | | | | | | | |
| 37 | INLIST ITERATOR | | | | | | | | |
|* 38 | INDEX RANGE SCAN | D_LOCNMST_ETL_IDX | 3136 | 28224 | | 12 (17)| 00:00:01 | | |
| 39 | INDEX FAST FULL SCAN | LOCATION_MASTER_KEY_PK | 3136 | 28224 | | 10 (0)| 00:00:01 | | |
|* 40 | BITMAP INDEX RANGE SCAN | BIMAP_JOBOIL_COST_CHRG_LOCN_KY | | | | | | 1 | 133 |
|* 41 | TABLE ACCESS FULL | D_UNIT_MASTER | 1790K| 23M| | 51484 (2)| 00:12:01 | | |
|* 42 | TABLE ACCESS BY INDEX ROWID | S_LOCATION | 1 | 23 | | 12 (0)| 00:00:01 | | |
|* 43 | INDEX RANGE SCAN | S_LOCN_SSOID_IDX | 14 | | | 1 (0)| 00:00:01 | | |
Predicate Information (identified by operation id):
2 - filter( EXISTS (SELECT 0 FROM "PTL_EDW"."S_LOCATION" "S_LOCATION" WHERE "S_LOCATION"."SSOID"='600028988' AND
DECODE("S_LOCATION"."LOCATION_MASTER_KEY",(-99999),:B1,"S_LOCATION"."LOCATION_MASTER_KEY")=:B2))
3 - access("F_JOB_OIL_COST"."RO_ACCOUNTING_MONTH_KEY"="D_TIME"."TIME_KEY")
4 - filter("D_TIME"."CAL_YYYYMM">=200601 AND "D_TIME"."CAL_YYYYMM"<=201104)
5 - access(ROWID=ROWID)
6 - access("D_TIME"."CAL_YYYYMM">=200601 AND "D_TIME"."CAL_YYYYMM"<=201104)
8 - access("F_JOB_OIL_COST"."UNIT_MASTER_KEY"="D_UNIT_MASTER"."UNIT_MASTER_KEY")
16 - filter("D_VEHICLE_CAP_STATUS"."VEHICLE_CAP_STATUS"='ACCRUED' OR "D_VEHICLE_CAP_STATUS"."VEHICLE_CAP_STATUS"='ACTIVE')
17 - access(ROWID=ROWID)
19 - access("D_VEHICLE_CAP_STATUS"."VEHICLE_CAP_STATUS"='ACCRUED' OR "D_VEHICLE_CAP_STATUS"."VEHICLE_CAP_STATUS"='ACTIVE')
21 - access("F_JOB_OIL_COST"."VEHICLE_CAP_STATUS_KEY"="D_VEHICLE_CAP_STATUS"."VEHICLE_CAP_STATUS_KEY")
25 - filter("D_TIME"."CAL_YYYYMM">=200601 AND "D_TIME"."CAL_YYYYMM"<=201104)
26 - access("F_JOB_OIL_COST"."RO_ACCOUNTING_MONTH_KEY"="D_TIME"."TIME_KEY")
30 - filter("D_ACCOUNT_CODE"."ACCOUNT_CODE_GROUP1"='COMMERCIAL RENTAL' OR "D_ACCOUNT_CODE"."ACCOUNT_CODE_GROUP1"='CONTRACT MAINTENANCE
- GUAR' OR "D_ACCOUNT_CODE"."ACCOUNT_CODE_GROUP1"='CONTRACT MAINTENANCE - OTHER' OR "D_ACCOUNT_CODE"."ACCOUNT_CODE_GROUP1"='CONTRACT
MAINTENANCE - PEG' OR "D_ACCOUNT_CODE"."ACCOUNT_CODE_GROUP1"='LEASE' OR "D_ACCOUNT_CODE"."ACCOUNT_CODE_GROUP1"='TRAILER PLUS')
31 - access("F_JOB_OIL_COST"."ACCOUNT_CODE_KEY"="D_ACCOUNT_CODE"."ACCOUNT_CODE_KEY")
35 - filter("D_LOCATION_DOMICILE"."CORP_CD"='2000' OR "D_LOCATION_DOMICILE"."CORP_CD"='HPTL')
36 - access(ROWID=ROWID)
38 - access("D_LOCATION_DOMICILE"."CORP_CD"='2000' OR "D_LOCATION_DOMICILE"."CORP_CD"='HPTL')
40 - access("F_JOB_OIL_COST"."CHARGING_LOCATION_KEY"="D_LOCATION_DOMICILE"."LOCATION_MASTER_KEY")
41 - filter("D_UNIT_MASTER"."CONTRACT_GROUP"='P' AND ("D_UNIT_MASTER"."UNIT_CATEGORY"='TRACTOR' OR
"D_UNIT_MASTER"."UNIT_CATEGORY"='TRAILER' OR "D_UNIT_MASTER"."UNIT_CATEGORY"='TRUCK'))
42 - filter(DECODE("S_LOCATION"."LOCATION_MASTER_KEY",(-99999),:B1,"S_LOCATION"."LOCATION_MASTER_KEY")=:B2)
43 - access("S_LOCATION"."SSOID"='600028988')
Note
- star transformation used for this statement
Statistics
3034 recursive calls
0 db block gets
28519518 consistent gets
1075291 physical reads
0 redo size
2519 bytes sent via SQL*Net to client
567 bytes received via SQL*Net from client
6 SQL*Net roundtrips to/from client
4 sorts (memory)
0 sorts (disk)
64 rows processed
Partition is range on YYYYMM(numeric format)

Could not get schema Object:java.sql.SQLSyntaxErrorException ora-904

All of a sudden I get
Could not get schema Object:java.sql.SQLSyntaxErrorException: ORA-00904: "SYS"."O"."NAME": ongeldige ID
when doing anything in the tables tree in the connections pane
The only thing I set recently is pga_aggregate_target
Environment
Oracle 11.2.0.1
OS Windows Vista Ultimate sp2
Sql developer 2.1.1.64.39 with its own JDK
As the download links on OTN are broken I can not upgrade, and I'd rather not work in command line sqlplus.
Help!!!
Sybrand Bakker
Senior Oracle DBA

My copy of sqldeveloper isn't located in that directory. Would that matter?
In the mean time I have disabled filtering the tables node. Opening the tables node doesn't result in exceptions anymore.
Now, when I click on any table in that node I get 4 identical ora-904 error messages for sys.o.name for any table.
Apparently it is querying either the all_objects view and it thinks it is querying sys.obj$.
I didn't yet enable sql_trace for the session, I'm more or less giving up on sqldeveloper. I can not use the space bar in any datagrid, sqldeveloper has always been extreemly unresponsive when navigating the schema browser (as opposed to Toad), etc, etc. Too bad I bought Sue Harpers book, but I think I will be de-installing sqldeveloper soon.
Sybrand Bakker
Senior Oracle DBA

Why is the Star Transformation using two indexes for the same dimension?

Hi,
Recently, I have made an investigation about the Star Transformation feature. I have found a strange test case, which plays an important role in my strategy for our overall DWH architecture. Here it is:
The Strategy:
I would like to have the classical Star Transformation approach (single column Bitmap Indexes for each dimension foreign key column in the fact table), together with additional Bitmap Join Indexes for some of the dimension attributes, which would benefit from the materialization of the join (bitmap merge operation will be skipped/optimized).
The query:
select dp.brand, ds. region_name, dc.region_name
     , count(*), sum(f.extended_price)
from fact_line_item f
     , dim_part       dp
     , dim_supplier   ds
     , dim_customer   dc
where dp.mfgr        = 10                 -- dimension selectivity = 1/10 --> acttual/fact selectivity = 6/10
   and f.part_dk      = dp.dk
   and ds.region_name = 'REGION #1' -- dimension selectivity = 1/9
   and f.supplier_dk = ds.dk
   and dc.region_name = 'REGION #1' -- dimension selectivity = 1/11
   and f.customer_dk = dc.dk
group by dp.brand, ds. region_name, dc.region_name
The actual plan:
| Id | Operation                              | Name                        | Starts | E-Rows | Cost (%CPU)| A-Rows |   A-Time   | Buffers | Reads |
|   0 | SELECT STATEMENT                       |                             |      1 |        | 3247 (100)|      1 |00:01:42.05 |     264K|    220K|
|   1 | HASH GROUP BY                         |                             |      1 |      2 | 3247   (1)|      1 |00:01:42.05 |     264K|    220K|
|* 2 |   HASH JOIN                            |                             |      1 | 33242 | 3037   (1)|    217K|00:01:29.67 |     264K|    220K|
|* 3 |    TABLE ACCESS FULL                   | DIM_SUPPLIER                |      1 |   1112 |   102   (0)|   1112 |00:00:00.01 |     316 |      4 |
|* 4 |    HASH JOIN                           |                             |      1 | 33245 | 2934   (1)|    217K|00:01:29.10 |     264K|    220K|
|* 5 |     TABLE ACCESS FULL                  | DIM_CUSTOMER                |      1 |    910 |   102   (0)|    910 |00:00:00.08 |     316 |      8 |
|* 6 |     HASH JOIN                          |                             |      1 | 33248 | 2831   (1)|    217K|00:01:28.57 |     264K|    220K|
|* 7 |      TABLE ACCESS FULL                 | DIM_PART                    |      1 |     10 |     3   (0)|     10 |00:00:00.01 |       6 |      0 |
|   8 |      PARTITION RANGE ALL               |                             |      1 | 36211 | 2827   (1)|    217K|00:01:28.01 |     264K|    220K|
|   9 |       TABLE ACCESS BY LOCAL INDEX ROWID| FACT_LINE_ITEM              |      6 | 36211 | 2827   (1)|    217K|00:01:33.85 |     264K|    220K|
| 10 |        BITMAP CONVERSION TO ROWIDS     |                             |      6 |        |            |    217K|00:00:07.09 |   46980 |   3292 |
| 11 |         BITMAP AND                     |                             |      6 |        |            |     69 |00:00:08.33 |   46980 |   3292 |
| 12 |          BITMAP MERGE                  |                             |      6 |        |            |    193 |00:00:02.09 |    2408 |   1795 |
| 13 |           BITMAP KEY ITERATION         |                             |      6 |        |            |   4330 |00:00:04.66 |    2408 |   1795 |
| 14 |            BUFFER SORT                 |                             |      6 |        |            |     60 |00:00:00.01 |       6 |      0 |
|* 15 |             TABLE ACCESS FULL          | DIM_PART                    |      1 |     10 |     3   (0)|     10 |00:00:00.01 |       6 |      0 |
|* 16 |            BITMAP INDEX RANGE SCAN     | FACT_LI__P_PART_DIM_KEY_BIX |     60 |        |            |   4330 |00:00:02.11 |    2402 |   1795 |
|* 17 |          BITMAP INDEX SINGLE VALUE     | FACT_LI__P_PART_MFGR_BJX    |      6 |        |            |   1747 |00:00:06.65 |     890 |    888 |
| 18 |          BITMAP MERGE                  |                             |      6 |        |            |    169 |00:00:02.78 |   16695 |    237 |
| 19 |           BITMAP KEY ITERATION         |                             |      6 |        |            |   5460 |00:00:01.56 |   16695 |    237 |
| 20 |            BUFFER SORT                 |                             |      6 |        |            |   5460 |00:00:00.02 |     316 |      0 |
|* 21 |             TABLE ACCESS FULL          | DIM_CUSTOMER                |      1 |    910 |   102   (0)|    910 |00:00:00.01 |     316 |      0 |
|* 22 |            BITMAP INDEX RANGE SCAN     | FACT_LI__P_CUST_DIM_KEY_BIX |   5460 |        |            |   5460 |00:00:02.07 |   16379 |    237 |
| 23 |          BITMAP MERGE                  |                             |      6 |        |            |    170 |00:00:03.65 |   26987 |    372 |
| 24 |           BITMAP KEY ITERATION         |                             |      6 |        |            |   6672 |00:00:02.23 |   26987 |    372 |
| 25 |            BUFFER SORT                 |                             |      6 |        |            |   6672 |00:00:00.01 |     316 |      0 |
|* 26 |             TABLE ACCESS FULL          | DIM_SUPPLIER                |      1 |   1112 |   102   (0)|   1112 |00:00:00.01 |     316 |      0 |
|* 27 |            BITMAP INDEX RANGE SCAN     | FACT_LI__S_SUPP_DIM_KEY_BIX |   6672 |        |            |   6672 |00:00:02.74 |   26671 |    372 |
The Question:
Why is the Star Transformation using both indexes FACT_LI__P_PART_DIM_KEY_BIX and FACT_LI__P_PART_MFGR_BJX for the same dimension criteria (dp.mfgr = 10)?? The introduction of the additional Bitmap Join Index actually make Oracle to do the work twice !!!
Anybody, any idea ?!?

Dom, here it is the plan with the predicates:
| Id | Operation                              | Name                        | Starts | E-Rows | Cost (%CPU)| A-Rows |   A-Time   | Buffers | Reads |
|   0 | SELECT STATEMENT                       |                             |      1 |        | 3638 (100)|      1 |00:06:41.17 |     445K|    236K|
|   1 | HASH GROUP BY                         |                             |      1 |      2 | 3638   (1)|      1 |00:06:41.17 |     445K|    236K|
|* 2 |   HASH JOIN                            |                             |      1 | 33242 | 3429   (1)|    217K|00:08:18.02 |     445K|    236K|
|* 3 |    TABLE ACCESS FULL                   | DIM_SUPPLIER                |      1 |   1112 |   102   (0)|   1112 |00:00:00.03 |     319 |    313 |
|* 4 |    HASH JOIN                           |                             |      1 | 33245 | 3326   (1)|    217K|00:08:17.47 |     445K|    236K|
|* 5 |     TABLE ACCESS FULL                  | DIM_CUSTOMER                |      1 |    910 |   102   (0)|    910 |00:00:00.01 |     319 |    313 |
|* 6 |     HASH JOIN                          |                             |      1 | 33248 | 3223   (1)|    217K|00:08:16.63 |     445K|    236K|
|* 7 |      TABLE ACCESS FULL                 | DIM_PART                    |      1 |     10 |     3   (0)|     10 |00:00:00.01 |       6 |      0 |
|   8 |      PARTITION RANGE ALL               |                             |      1 | 36211 | 3219   (1)|    217K|00:08:16.30 |     445K|    236K|
|   9 |       TABLE ACCESS BY LOCAL INDEX ROWID| FACT_LINE_ITEM              |      6 | 36211 | 3219   (1)|    217K|00:08:40.89 |     445K|    236K|
| 10 |        BITMAP CONVERSION TO ROWIDS     |                             |      6 |        |            |    217K|00:00:32.00 |   46919 | 19331 |
| 11 |         BITMAP AND                     |                             |      6 |        |            |     69 |00:00:34.50 |   46919 | 19331 |
| 12 |          BITMAP MERGE                  |                             |      6 |        |            |    193 |00:00:00.58 |    2353 |      1 |
| 13 |           BITMAP KEY ITERATION         |                             |      6 |        |            |   4330 |00:00:00.10 |    2353 |      1 |
| 14 |            BUFFER SORT                 |                             |      6 |        |            |     60 |00:00:00.01 |       6 |      0 |
|* 15 |             TABLE ACCESS FULL          | DIM_PART                    |      1 |     10 |     3   (0)|     10 |00:00:00.01 |       6 |      0 |
|* 16 |            BITMAP INDEX RANGE SCAN     | FACT_LI__P_PART_DIM_KEY_BIX |     60 |        |            |   4330 |00:00:00.07 |    2347 |      1 |
|* 17 |          BITMAP INDEX SINGLE VALUE     | FACT_LI__P_PART_MFGR_BJX    |      6 |        |            |   1747 |00:01:23.64 |     882 |    565 |
| 18 |          BITMAP MERGE                  |                             |      6 |        |            |    169 |00:00:09.14 |   16697 |   7628 |
| 19 |           BITMAP KEY ITERATION         |                             |      6 |        |            |   5460 |00:00:02.19 |   16697 |   7628 |
| 20 |            BUFFER SORT                 |                             |      6 |        |            |   5460 |00:00:00.01 |     316 |      0 |
|* 21 |             TABLE ACCESS FULL          | DIM_CUSTOMER                |      1 |    910 |   102   (0)|    910 |00:00:00.01 |     316 |      0 |
|* 22 |            BITMAP INDEX RANGE SCAN     | FACT_LI__P_CUST_DIM_KEY_BIX |   5460 |        |            |   5460 |00:00:08.78 |   16381 |   7628 |
| 23 |          BITMAP MERGE                  |                             |      6 |        |            |    170 |00:00:21.46 |   26987 | 11137 |
| 24 |           BITMAP KEY ITERATION         |                             |      6 |        |            |   6672 |00:00:10.29 |   26987 | 11137 |
| 25 |            BUFFER SORT                 |                             |      6 |        |            |   6672 |00:00:00.01 |     316 |      0 |
|* 26 |             TABLE ACCESS FULL          | DIM_SUPPLIER                |      1 |   1112 |   102   (0)|   1112 |00:00:00.01 |     316 |      0 |
|* 27 |            BITMAP INDEX RANGE SCAN     | FACT_LI__S_SUPP_DIM_KEY_BIX |   6672 |        |            |   6672 |00:00:20.94 |   26671 | 11137 |
Predicate Information (identified by operation id):
   2 - access("F"."SUPPLIER_DK"="DS"."DK")
   3 - filter("DS"."REGION_NAME"='REGION #1')
   4 - access("F"."CUSTOMER_DK"="DC"."DK")
   5 - filter("DC"."REGION_NAME"='REGION #1')
   6 - access("F"."PART_DK"="DP"."DK")
   7 - filter("DP"."MFGR"=10)
15 - filter("DP"."MFGR"=10)
16 - access("F"."PART_DK"="DP"."DK")
17 - access("F"."SYS_NC00017$"=10)
21 - filter("DC"."REGION_NAME"='REGION #1')
22 - access("F"."CUSTOMER_DK"="DC"."DK")
26 - filter("DS"."REGION_NAME"='REGION #1')
27 - access("F"."SUPPLIER_DK"="DS"."DK")
Note
   - star transformation used for this statement

Error message for ORA-904 incomplete in german locale [1.1.0.22.71]

Hello Forum,
when I enter an SQL which generates an ORA-904, the error message looks somewhat weird with german locale:
-- First with AMERICAN setting:
alter session set nls_language='AMERICAN';
select a from dual;
alter session set succeeded.
Error starting at line 2 in command:
select a from dual
Error at Command Line:2 Column:7
Error report:
SQL Error: ORA-00904: "A": invalid identifier
00904. 00000 - "%s: invalid identifier"
*Cause:
*Action:
-- And now with GERMAN setting:
alter session set nls_language='GERMAN';
select a from dual;
alter session set succeeded.
Error starting at line 4 in command:
select a from dual
Error at Command Line:4 Column:7
Error report:
SQL Error: ORA-00904: Ungültiger Spaltenname
00904. 00000 - "%s: invalid identifier"
*Cause:
*Action:
As you can see, the name of the invalid column is not displayed when nls_language="GERMAN".
Maybe the second line '00904. 00000 - "%s: invalid identifier"' results from having a german Windows XP.
I don't know how it looks on english Windows or how it should look like. :-)
I run SQLDeveloper on XP Pro and Oracle 9.2 (on W2k).
Regards,
dhalek

dhalek,
If you take a closer look, the 00904. 00000 - "%s: invalid identifier" line is present in both languages - it's something that gets always appended.
As for the German message SQL Error: ORA-00904: Ungültiger Spaltenname, you see it's lacking any reference to the column. The German translator apparently let that slip out. If the substitution parameter was there, but unsubstituted for some reason, it would look like SQL Error: ORA-00904: "": Ungültiger Spaltenname.
You can contact Oracle through Metalink if you want this to get sorted out...
K.

ORA-00904 and packaged function in report

Oracle 9.2.0.7
APEX 2.0
Is APEX not able to deal with SQL that calls a packaged function?
I ask because I'm able to execute this query:
SELECT s.doc_id,
s.last_name || ', ' || s.first_name full_name,
s.p_id,
s.create_date
, rwa_wfrole.get_role_list(s.proj_id, s.p_id) wfrole_label
FROM signatures_vw s
WHERE s.proj_id = 182
AND s.status = 'APPROVED'
ORDER BY s.create_date, s.last_name, s.first_name
in SQL*Plus, but not in the SQL Workshop or in a report region. In the latter case I get "ORA-00904 invalid identifier" for "rwa_wfrole.get_role_list"... which is a packaged function. Actually, to be more precise, it's a package in a remote database. In the APEX instance, I have a synonym pointing to it.
Thanks for insight.
-John

I can't reproduce this in 10g. I did find bug 4177810 (Fixed in 9.2.0.8 Server Patch Set) that looks a bit like this problem.
Description
    An unexpected ORA-904 can occur for some internally generated SQL
    when the select list contains non-column constants and the select
    appears in the FROM clause. This can occur for SQL produced for
    parallel query or for remote / distributed queries.
    Workaround:
      Rewrite the query to avoid constant expressions in the FROM clause select lists.***************************
There are also recommendations dating way back that you should include the schema name in the Create Synonym statement.
Scott

SQLDEV 2.1.0.63 gives ORA-904 on UT_TEST_RESULTS when running unit test

Hi, I am trying to create and run my first unit test using sqldeveloper 2.1.0.63 but it fails with followkng error:
----- Error Stack Dump -----
ORA-00904: "TEST_USER_NAME": invalid identifier
----- Current SQL Statement for this session (sql_id=b9c4zd8fqmykv) -----
select utr_id, name, status, message, run_date,coverage,test_user_name from ut_test_results where ut_id = :ID order by run_date desc
table ut_test_results indeed does not have this column test_user_name:
SYS@madlnlcs11/map SQL> DESC UT_SP5.UT_TEST_RESULTS
Name Null? Type
UTR_ID NOT NULL VARCHAR2(40)
UT_ID NOT NULL VARCHAR2(40)
NAME NOT NULL VARCHAR2(120)
STATUS NOT NULL VARCHAR2(20)
MESSAGE VARCHAR2(2000)
COVERAGE NOT NULL NUMBER(1)
RUN_DATE NOT NULL TIMESTAMP(6)
CREATED_ON NOT NULL TIMESTAMP(6)
CREATED_BY NOT NULL VARCHAR2(120)
UPDATED_ON NOT NULL TIMESTAMP(6)
UPDATED_BY NOT NULL VARCHAR2(120)
how come there's this mismatch? The Unitest repository was created by the same sqldeveloper !
regards,
Andre

This seems to be coming from the repository being marked as Shared repository. Appearantly sqldeveloper is issueing a different query, referencing TEST_USER_NAME, in that case. After I did a DESELECT AS SHARED REPOSITORY and drop/recreate of the repository the error ORA-904 no longer occurs.

Ora-904 in plsql

i have a function "FA" in schema "A". i gave a grant (execute) to a role "rleA". In another schema "B" i created other procedure "PB" accessing function created before "FA" and gave grant by role "rleA" to schema "B". In this case, raise the error ora-904 in line where "FA" is. If i execute the line error without a plsql block, it works or if i give grant direct to "B" it works too (in plsql).
anybody help ?

I am facing the same problem. I am using Oracle Database 10g Express Edition.
If any one has the solution please share it .
ORA-00904: : invalid identifier

ORA-01843 and ORA-02291 when installing AIA 2.0 on Linux server

Hello,
When installing AIA 2.0 on a RHEL 4.7 Linux server, even if OUI does say the installion is successful, the installActions log are not that good...
We've got some ORA-01843 and ORA-02291 errors when running the createDiagnosticsCAVSData.sql.
[exec] createBSRIntegScenarioTables:
[exec] [echo] ----Creating createCAVSTables--------------
[exec] [sql] Executing resource: /exec/applis/tbaia/products/AIA/seeddata/DatabaseObjects/createBSRIntegScenarioTables.sql
[exec] [sql] 152 of 152 SQL statements executed successfully
[exec]
[exec] createDiagnosticsCAVSData:
[exec] [echo] ----Creating createCAVSTables--------------
[exec] [sql] Executing resource: /exec/applis/tbaia/products/AIA/seeddata/DatabaseObjects/createDiagnosticsCAVSData.sql
[exec] [sql] Failed to execute: Insert into CAVS_DEFINITIONS (DEFINITION_ID,TYPE,DESCRIPTION,STATE,SERVICE_TYPE,URL_WSDL,URL_ENDPOINT,SOAP_ACTION,SOAP_TRANSPORT_TYPE,MESSAGE_REQUEST,MESSAGE_RESPONSE,DELAY,VERSION,PROJECT_NAME,PROJECT_VERSION,EBS_NAME,EBS_VERSION,PROCESS_NAME,PROCESS_VERSION,SERVICE_NAME,SERVICE_VERSION,MESSAGE_NAME,MESSAGE_VERSION,PIP_NAME,PIP_VERSION,APPLICATION_NAME,APPLICATION_VERSION,TEST_PRIORITY,REFERENCE_ID_EXTERNAL,AUDITED_ON,AUDITED_BY) values (501,'Test','BPEL Transformation Diagnostics','Unlocked','Synchronous',null,'http://dvedvb40:7777/orabpel/default/AIADiagnosticsTransformBpelProcess/1.0','process','HTTP','<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body xmlns:ns1="http://xmlns.oracle.com/BRM/schemas/BusinessOpcodes"> <ns1:PCM_OP_BILL_DEBIT_inputFlist> <ns1:BAL_GRP_OBJ>Test</ns1:BAL_GRP_OBJ> <ns1:DEBIT elem="523"> <ns1:BAL_OPERAND>1000</ns1:BAL_OPERAND> <ns1:TYPE>881</ns1:TYPE> </ns1:DEBIT> <ns1:DESCR>Sample Input</ns1:DESCR> <ns1:END_T>2007-07-31T12:00:00.000+5:30</ns1:END_T> <ns1:POID>A123</ns1:POID> <ns1:PROGRAM_NAME>100</ns1:PROGRAM_NAME> <ns1:SERVICE_OBJ>NA</ns1:SERVICE_OBJ> <ns1:SESSION_OBJ>NA</ns1:SESSION_OBJ> <ns1:START_T>2007-07-31T11:00:00.000+5:30</ns1:START_T> <ns1:STR_VERSION>527</ns1:STR_VERSION> <ns1:STRING_ID>528</ns1:STRING_ID> <ns1:SUB_BALANCES elem="530"> <ns1:CONTRIBUTOR_STR>Diagnostics</ns1:CONTRIBUTOR_STR> <ns1:ROLLOVER_DATA>1</ns1:ROLLOVER_DATA> <ns1:VALID_FROM>2007-07-31T11:00:00.000+5:30</ns1:VALID_FROM> <ns1:VALID_TO>2007-07-31T11:00:00.000+5:30</ns1:VALID_TO> </ns1:SUB_BALANCES> </ns1:PCM_OP_BILL_DEBIT_inputFlist> </soap:Body> </soap:Envelope>','<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header/> <env:Body> <PCM_OP_BILL_DEBIT_outputFlist xmlns:ns0="http://xmlns.oracle.com/BRM/schemas/BusinessOpcodes" xmlns="http://xmlns.oracle.com/BRM/schemas/BusinessOpcodes"> <ns0:POID>Transformed POID value : A123</ns0:POID> <ns0:RESULTS elem="Transformed Element value : 523"/> </PCM_OP_BILL_DEBIT_outputFlist> </env:Body> </env:Envelope>',null,0,null,null,null,null,'Diagnostics Transformation',null,'DiagTransformationBPEL','1.0',null,null,'AIA Diagnostics',null,null,null,null,null,to_date('01-OCT-07','DD-MON-RR'),'oc4jadmin')
[exec] [sql] java.sql.SQLException: ORA-01843: not a valid month
[exec] [sql] Failed to execute: Insert into CAVS_DEFINITION_NSXPATHS (DEFINITION_ID,NAMESPACE_ALIAS,NAMESPACE) values (501,'env','http://schemas.xmlsoap.org/soap/envelope/')
[exec] [sql] java.sql.SQLException: ORA-02291: integrity constraint (AIA.DEFINITION_NSXPATHS_D_FK) violated - parent key not found
[exec] [sql] *1 of 43 SQL statements executed successfully*
Any advice to solve this issue?
Thanks in advance.
Regards,
K.
Edited by: KaRiNe_Fr on 3 juin 2009 01:55 createDiagnosticsCAVSData.sql instead of createBSRIntegScenarioTables.sql...

Hello,
me again...
Is this table CAVS_DEFINITIONS important to be populated for the rest of the AIA installation?
The installation keeps on failing and it is a real issue for us...
If of any use, here are some results from SQL requests onto our AIA database:
SQL> SELECT * FROM NLS_DATABASE_PARAMETERS ;
PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET WE8ISO8859P15
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD.MM.YYYY
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
PARAMETER VALUE
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 10.2.0.4.0
20 rows selected.
SQL> select to_date('01-OCT-07','DD-MON-RR') from dual;
TO_DATE('
01-OCT-07
Regards,
KaRiNe.
Edited by: KaRiNe_Fr on 3 juin 2009 01:59

Will star transformation be scalable?

This is rather an algorithmic question
I happen to read a post about a real-world problem.
http://groups.google.com/group/comp.databases.oracle.server/browse_thread/thread/0db61c4fab79769a?hl=en
Simple back envelope analysis shows that star transformation would be very expensive in terms of storage:
The fact table F has 750 million rows, a dimensional table D has 70k rows. Suppose I have a bitmap join index between F and D to support star transformation.
How large would the bitmap index be?
70k values, each need a bitmap vector of 750M bits. The bitmap size would be 70k x (750M/8) bytes=6.6kGb. Is that too large?
Or, I miss something? If partition can help, how?
I guess my general questions is that if the dimension table's cardinality is in the order of thousands, what solution would Oracle provide? Thanks.
T.K.

Thanks for the link. However, I do not see any metrics mentioning about bitmap compression degree.
I agree that 6.6kG join bitmap index is not in the compression form. However, in general to what degree can a bitmap be compressed? In this particular example, suppose it can be compressed by a ratio of 100. Then, we still need 6.6kG/100=66G for the bitmap join index. Decompressing it on the fly also take a lot of CPUs cycles. Adding more CPU cores would not benefit since most cores share the same L2 cache. (cache misses would be a bottleneck)
Are there any benchmark results or documents discussing bitmap compression effect and showing the practical side of a reasonable large db benefiting from Star transformation like this example?
thanks,
T.k.

SQLDev 4.0 EA1 error ORA-904 "SP"."CHILD_ADDRESS" invalid identifier.

Recieve error ORA-904 "SP"."CHILD_ADDRESS" invalid identifier when accessing the Explain Plan tab in Session Monitor. Client in Win 7 64 bit, DB is Oracle 10.1.
This behavior still exists with 4 EA3.

Copy the monitor sessions report down to a user defined report, check out the SQL being used in the Explain Plan tab, and try running that in your 10.1.0.5 database. We don't support that version of the database, but you can change up the sql in your user defined report to work for that instance if necessary.

Scheduled Web Intelligence report fails with ORA-01013 and WIS 10901

Hi,
the environment I'm working in is BOXI R2 SP4 on a Solaris 10 server using WebLogic running against Oracle 9i database.
I have a report written by one of the users. In SQL Viewer the SQL detailed is two joined Select statements. Each time this report is either scheduled or refreshed is fails with an ORA-01012 and WIS 10901 error.
I am of the understanding that this failure relates to the fact that the 'Limit Execution Time To;' value is being exceeded.
I also understand that this value is infact divided by the number of Select statements present, and that each Select statment is them allocated an equal portion of this value.
If any of this is incorrect please correct me.
I therefore have two questions
1. As such would I be correct in assuming that in my scenario where 2 Select statments are present and where the execution limit is set to 30 minutes, that each Select has 15 minutes to complete, and that if either fails the ORA-01012 and WIS 10901 error is generated.
2. Also would this error message get generated as soon as the first failure occurred, or would BO initiate a cancellation of the SQL by Oracle, ORA-01012, only when the final request has either succeeded or failed.

The queries are not executed in parallel but in serial. So the total execution time configured will be for all the Select statements in the report combined.
As for your second question, since the execution is not parallel hence BO will not initiate any error message until the total execution time exceeds the defined limit. This could be during the execution of first select statement or the second.
Try executing the queries directly in database one by one and see how much time they are taking.
- Noman Jaffery

Instance terminted with ORA-00445 and ORA-00494

Hi Folks,
Oracle 11g Instance terminated after ORA-00445 and ORA-00494. Not sure what is the problem didnot have this problem before. Can any body pls help?
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
Below is the message found in alertlog.
Archived Log entry 17939 added for thread 1 sequence 17973 ID 0xee1270c6 dest 1:
Thu Apr 19 02:32:15 2012
WARNING:io_getevents timed out 600 sec
Thu Apr 19 02:32:17 2012
WARNING:io_getevents timed out 600 sec
Thu Apr 19 02:33:32 2012
WARNING:io_getevents timed out 600 sec
Thu Apr 19 02:35:56 2012
Process 0x0xdfb80810 appears to be hung while dumping
Current time = 1203097316, process death time = 1203032607 interval = 60000
Attempting to kill process 0x0xdfb80810 with OS pid = 7563
OSD kill succeeded for process 0xdfb80810
Thu Apr 19 02:36:32 2012
WARNING:io_getevents timed out 600 sec
Thu Apr 19 02:38:11 2012
Errors in file /apps/opt/oracle/admin/diag/rdbms/vchsit2/vchsit2/trace/vchsit2_smco_8548.trc (incident=76297):
ORA-00445: background process "W000" did not start after 120 seconds
Incident details in: /apps/opt/oracle/admin/diag/rdbms/vchsit2/vchsit2/incident/incdir_76297/vchsit2_smco_8548_i76297.trc
Thu Apr 19 02:38:11 2012
Errors in file /apps/opt/oracle/admin/diag/rdbms/vchsit2/vchsit2/trace/vchsit2_arc2_7523.trc (incident=76329):
ORA-00494: enqueue [CF] held for too long (more than 900 seconds) by 'inst 1, osid 7315'
Incident details in: /apps/opt/oracle/admin/diag/rdbms/vchsit2/vchsit2/incident/incdir_76329/vchsit2_arc2_7523_i76329.trc
Thu Apr 19 02:38:11 2012
Fatal NI connect error 12537, connecting to:
(LOCAL=NO)
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 19-APR-2012 02:38:11
Tracing not turned on.
Tns error struct:
ns main err code: 12537
TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (2743) as a result of ORA-609
Thu Apr 19 02:38:12 2012
Trace dumping is performing id=[cdmp_20120419023812]
Killing enqueue blocker (pid=7315) on resource CF-00000000-00000000 by (pid=7523)
by killing session 6.1
Killing enqueue blocker (pid=7315) on resource CF-00000000-00000000 by (pid=7523)
by terminating the process
ARC2 (ospid: 7523): terminating the instance due to error 2103
Instance terminated by ARC2, pid = 7523
Thu Apr 19 10:43:07 2012

Hi;
Please see:
ORA-00445: Background Process "xxxx" Did Not Start After 120 Seconds [ID 1345364.1]
Regard
Helios

ORA-12500 and Memory limited

This is list of environment
- Oracle 8.1.7
- OS is AIX
- RAM = 2GB
- 3 instances
when user try to connect too much that will show ORA-12500 and I select this statement in a problem instance
"select count(1) from v$session" the result estimate is 502.
"select count(1) from v$process" the result estimate is 504
and another instance 10 sessions and 20 sessions.
This's folloing a part of parameters.
bitmap_merge_area_size integer 1048576
create_bitmap_area_size integer 8388608
db_block_buffers integer 10000
db_block_lru_latches integer 2
db_block_max_dirty_target integer 10000
db_block_size integer 8192
distributed_transactions integer 243
hash_area_size integer 16777216
hash_multiblock_io_count integer 32
java_pool_size string 20000K
large_pool_size string 0
processes integer 800
sessions integer 885
shared_pool_reserved_size string 15000000
shared_pool_size string 300000000
sort_area_retained_size integer 1048576
sort_area_size integer 4194304
sort_multiblock_read_count integer 32
transactions integer 973
transactions_per_rollback_segment integer 5
How to modify or change some parameter for fix this problem?

I think you need to give more description about problem.
You might review the following Oracle Metalink Document:
SQL*Net (oracle Networking) Common Errors & Diagnostic Worksheet: Doc ID: Note:45878.1
https://metalink.oracle.com/metalink/plsql/f?p=130:14:5712140308577577466::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,45878.1,1,0,1,helvetica
If possible also upgrade your database.
Adith

ORA-904 and star transformation

Similar Messages

Maybe you are looking for