Transferring SQL Profiles between databases

We'd like to be able to ship SQL Profiles for 10gR2 with our application for commonly problematic SQL.
Does anyone know of a way that we can extract these profiles and apply them during application installation/upgrade?
There is a bug indicating that Query Profiles get set to not force matching during exp/imp. What I can't see is whether or not there is a way to export just the SQL Profiles. There seems nothing appropriate in database_export_objects.
Maybe there is another way that I am not aware of...

Thank you - but won't this retrieve profiles (resource limits applicable to users/sessions) rather than SQL Profiles (replacement sets of hints applied automatically to SQL statements - much like outlines - generated by SQL Tuning Advisor).
It is SQL Profiles generated by the SQL Tuning Advisor that I am looking to transfer. Few of our customers will want to spend money on the Tuning Advisor, but they will all want to have these queries running quickly!

Similar Messages

Transforming the Raster Data between Databases

Hi
I have a Requirement to Import and Export The Raster Data Between Data bases .. Could Any Body Give Me Hint...
Rajanikanthc

NedimAT pointed you to the 10g manual. If your database is 11g, please check it out from the 11g manual, Section 3.21 Transferring GeoRaster Data Between Databases:
http://download.oracle.com/docs/cd/E11882_01/appdev.112/e11827/geor_operations.htm#CIHECFGC
Depending on your requirements and the source and target database environments, you may also consider using Transportable Tablespace to transfer the raster data, particularly when you want to transfer only part of the database based on queries or cropping areas. Check section 3.22:
http://download.oracle.com/docs/cd/E11882_01/appdev.112/e11827/geor_operations.htm#CHDGEGHB
hope this helps
Jeffrey

Question about moving a SQL profile to a different database

All,
I know in 11g I can move SQL baselines to another host. Does anyone know if I can more just a single SQL Profile and how that is accomplished. I'm not seeing a PL/SQL package do to this but I may be missing it. Also, no hits on Metalink or Ask Tom on how to do this. I have this vague memory that it is possible but I'll be dammed if I can figure out how to do it.
thanks in advance
J Sebastian

Just to inform
http://blog.flimatech.com/2010/06/08/how-does-one-move-sql-profiles-from-one-instance-to-another/
Have very good example how to move SQL profile

Transfer whole schema between databases

Hi,
I have a question on how to move an entire schema between two databases which are of the same version and patchset.
I identified the possible methods as follows:
1) Using exp/imp or expdp/impdp, but that's quite slow on larger schemas and the transported data might not be physically the same as on the source database (indexes are rebuilt, tables get loaded with data again....).
2) Using transportable tablespaces. This is fast, the physical data layout is the same as on the source database, but unfortunately only the objects in the transported tablespace get transferred. Schema objects like PL/SQL packages, private synonyms, functions.... and grants aren't transferred since they are stored in the SYSTEM tablespace.
Is there any other way to move a schema between databases? Maybe some combination of expdp/impdp (transfer of user object definitions stored in the SYSTEM tablespace like PL/SQL code, view definitions, etc.) and transportable tablespaces (transfer data segments like tables, indexes....)
From what I know RMAN can't do that since the smallest "logical object" it can restore/recover is the whole tablespace with tablespace point in time recovery.
Thanks in advance for any answer.
Regards,
Jure

user633661 wrote:
Hi,
I have a question on how to move an entire schema between two databases which are of the same version and patchset.
I identified the possible methods as follows:
1) Using exp/imp or expdp/impdp, but that's quite slow on larger schemas and the transported data might not be physically the same as on the source database (indexes are rebuilt, tables get loaded with data again....).
2) Using transportable tablespaces. This is fast, the physical data layout is the same as on the source database, but unfortunately only the objects in the transported tablespace get transferred. Schema objects like PL/SQL packages, private synonyms, functions.... and grants aren't transferred since they are stored in the SYSTEM tablespace.
Is there any other way to move a schema between databases? Maybe some combination of expdp/impdp (transfer of user object definitions stored in the SYSTEM tablespace like PL/SQL code, view definitions, etc.) and transportable tablespaces (transfer data segments like tables, indexes....)
From what I know RMAN can't do that since the smallest "logical object" it can restore/recover is the whole tablespace with tablespace point in time recovery.
Thanks in advance for any answer.
Regards,
JureIf you have only one business schema, then you may go with duplication of database.
Otherwise, you can go with Schema Based Replication with Streams or as you said combination of expdp/impdp and transport.

Use of SQL Profiles where each schema has very different data distribution and volumes

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE 11.2.0.3.0 Production
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
Our architecture has multiple client schemas in the same database. Each schema has the same code base (tables, procedures etc) but each client's data is very different in terms of volumes and skew/distribution per table. This architecture was done based on cost - I know it's not ideal but it can't change.....
I am fairly seasoned with performance management and so know the usual tricks of when to eat up the table using parallel full table scans etc. I couldn't further optimise a given stmt for our largest table. I'll call it TSPCI and it has monthly partitions (2 years) and totals about 35Gb in the largest client schema.
Anyway, I was surprised when ADDM suggested that I could achieve 98% improvement if I were to use a given SQL Profile. Great?
So, here's my issue - I've found that the same SQL_ID is shared across all those different client schemas: I can't see how to get it to pick/use the SQL Profile in only a particular client schema - let's call it NEX - and not in another (lets call it COL).
If I generate a SQL Profile as NEX, has it analysed and built the SQL Profile based on the NEX schema and is it therefore invalid/undesirable to have that SQL Profile used in the COL schema??
I suppose that I could add a small change (say /*+ NEX */) to the SQL in the NEX schema to make the given sql unique there and then generate a SQL Profile for that..........
What am I missing here?

Well, I can confirm the behaviour: accept a SQL Profile for a given SQL in one schema and verified that it is used in another schema (where the data volume and distribution is very different).
I can also confirm the workaround - simply add a hint to the SQL to make it unique such that I could use different sql profiles for the otherwise exact same sql in different schemas.
I'm happy enough with this workaround but I'll leave this thread unanswered in case someone can suggest a better approach.

Sql profiles in 11.1.0.7

We just upgraded from 10.1.0.3 to 11.1.0.7 and some very complex queries are running slower. When I check the plans in a non-production 11g database, the join orders are slightly different. I also have traces from my 10g production database and that I loaded into a sql tuning set in production. I am running the sql tuning advisor. When I get a recommendation to use the old plan, I implement it in the 10.2.0.5 Oracle Enterprise manager grid control.
How do I tell the sql_id of the sql profile? Is it part of the name? So if I look in dba_sql_profiles and see
SYS_SQLPROF_012a8f339c4b0001
Is the last part the sql_id? When I search on that value, I do not see it in v$sql. It does not appear that my queries are using the sql profile. So there might a slight difference from these queries (space maybe) than the ones I have. How do I confirm that my queries are using a sql profile as well?

Dear user11990507,
I do think that the value "012a8f339c4b0001" is nothing to do with the SQL_ID in the v$sql fixed view. It can be generated based on an algorithm like generating SQL_IDs. That is an internal information and i really don't know much about it.
You can also accept, alter or drop an SQL profile with the below commands;
DECLARE my_sqlprofile_name VARCHAR2(30);
BEGIN my_sqlprofile_name := DBMS_SQLTUNE.ACCEPT_SQL_PROFILE (task_name => 'my_sql_tuning_task', name => 'my_sql_profile', force_match => TRUE);
END;
BEGIN
DBMS_SQLTUNE.ALTER_SQL_PROFILE(name => 'my_sql_profile', attribute_name => 'STATUS', value => 'DISABLED');
END;
BEGIN
DBMS_SQLTUNE.DROP_SQL_PROFILE(name => 'my_sql_profile');
END;
DBA_SQL_PROFILES;
http://download.oracle.com/docs/cd/B28359_01/server.111/b28320/statviews_4256.htm#REFRN23477
Check the SQL_TEXT column for you particular SQLs.
Hope That Helps.
Ogan

Trace for a specific IP address in SQL Profiler

Hello,
I am looking for a way to trace from a specific ip address in sql profiler, Is there any filter that we can use to trace the database calls from a specific ip address.
Thanks in advance.

Thanks for the reply, I have tried by selecting hostname from column filters and gave my system name in Like.
When i run application from localhost then it returns trace results, but on live domain it is not returning trace results, M i missing something in configuring filters?

SQL PROFILE USED/NOT USED

Hi All,
We have slow runnig query problem with below queries:
QUERY 1
=======
SELECT "PC0".pxObjClass AS "pxObjClass", "PC0".PXINSNAME AS "pxInsName"
, "PC0".WORKTYPENAME AS "WorkTypeName" , "PC0".PYSTATUSWORK AS
"pyStatusWork" , "PC0".PXCREATEDATETIME AS "pxCreateDateTime",
"PC0".LINKEDREFTO as "pxInsHandle" FROM V_FORM_RELATIONSHIPS_R_1_0
"PC0" WHERE ( "PC0".LINKEDREFFROM = :1 ) AND ( "PC0".pxObjClass = :2
   ) ORDER BY "PC0".PXINSNAME DESC , "PC0".PXCREATEDATETIME
QUERY 2
=======
SELECT PYID AS "pyID" , PXOBJCLASS AS "pxObjClass" , PZINSKEY AS
"pzInsKey", PZINSKEY as "pxInsHandle" FROM V_WORK_R_1_0   WHERE (
PYID = :1 ) AND ( pxObjClass = :2   )
V_WORK_R_1_0 is a view which union all of two table without any where clause
V_FORM_RELATIONSHIPS_R_1_0 is another view that is made up of V_WORK_R_1_0 view and one more table.
Production DBA accepted both the SQL PROFILE created for these two queries.
FROM DBA_HIST_SQLSTATS it looks like sometime the profile getting used and sometime old plan is being used.How to ensure that correct SQLPROFILE once accepted is used?
This is 4 node RAC oracle 11.2.0.2.0 on Linux
For first query below are sql stats
col BEGIN_INTERVAL_TIME for a26
col end_INTERVAL_TIME for a26
col ROWS_PROCESSED_TOTAL for 99999
col ROWS_PROCESSED_delta for 99999
select s.begin_interval_time, s.end_interval_time , q.snap_id, q.dbid, q.sql_id, q.plan_hash_value, q.optimizer_cost, q.optimizer_mode
--,ROWS_PROCESSED_TOTAL,ROWS_PROCESSED_delta--,CPU_TIME_TOTAL,CPU_TIME_DELTA,ELAPSED_TIME_TOTAL,ELAPSED_TIME_DELTA
from dba_hist_sqlstat q, dba_hist_snapshot s
where q.dbid = 4026476544 and q.sql_id = '1um96ykvtwrh4'
and q.snap_id = s.snap_id
and s.begin_interval_time between sysdate-2 and sysdate
order by 1,s.snap_id desc;
BEGIN_INTERVAL_TIME        END_INTERVAL_TIME             SNAP_ID       DBID SQL_ID        PLAN_HASH_VALUE OPTIMIZER_COST OPTIMIZER_
03-JUL-13 06.00.33.805 AM 03-JUL-13 07.00.21.439 AM       17316 4026476544 1um96ykvtwrh4       377865450             20 ALL_ROWS
03-JUL-13 06.00.33.843 AM 03-JUL-13 07.00.21.475 AM       17316 4026476544 1um96ykvtwrh4       377865450             20 ALL_ROWS
03-JUL-13 06.00.33.843 AM 03-JUL-13 07.00.21.475 AM       17316 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 06.00.33.843 AM 03-JUL-13 07.00.21.474 AM       17316 4026476544 1um96ykvtwrh4       377865450             20 ALL_ROWS
03-JUL-13 07.00.21.475 AM 03-JUL-13 08.00.06.051 AM       17317 4026476544 1um96ykvtwrh4       377865450             20 ALL_ROWS
03-JUL-13 08.00.06.023 AM 03-JUL-13 09.00.11.626 AM       17318 4026476544 1um96ykvtwrh4       377865450             20 ALL_ROWS
03-JUL-13 08.00.06.023 AM 03-JUL-13 09.00.11.626 AM       17318 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 08.00.06.051 AM 03-JUL-13 09.00.11.596 AM       17318 4026476544 1um96ykvtwrh4       377865450             20 ALL_ROWS
03-JUL-13 08.00.06.051 AM 03-JUL-13 09.00.11.623 AM       17318 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 08.00.06.051 AM 03-JUL-13 09.00.11.596 AM       17318 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 11.00.10.502 AM 03-JUL-13 12.00.16.034 PM       17321 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 11.00.10.502 AM 03-JUL-13 12.00.16.033 PM       17321 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 11.00.10.503 AM 03-JUL-13 12.00.16.034 PM       17321 4026476544 1um96ykvtwrh4       377865450             20 ALL_ROWS
03-JUL-13 12.00.16.034 PM 03-JUL-13 01.00.42.715 PM       17322 4026476544 1um96ykvtwrh4       377865450                ALL_ROWS
03-JUL-13 01.00.42.685 PM 03-JUL-13 02.00.10.200 PM       17323 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 01.00.42.714 PM 03-JUL-13 02.00.10.200 PM       17323 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 03.00.15.887 PM 03-JUL-13 04.00.05.570 PM       17325 4026476544 1um96ykvtwrh4      1122713586         179347 ALL_ROWS
03-JUL-13 03.00.15.887 PM 03-JUL-13 04.00.05.570 PM       17325 4026476544 1um96ykvtwrh4       377865450          30585 ALL_ROWS
03-JUL-13 03.00.15.914 PM 03-JUL-13 04.00.05.541 PM       17325 4026476544 1um96ykvtwrh4      1122713586         179347 ALL_ROWS
03-JUL-13 03.00.15.915 PM 03-JUL-13 04.00.05.570 PM       17325 4026476544 1um96ykvtwrh4       377865450          30585 ALL_ROWS
03-JUL-13 04.00.05.541 PM 03-JUL-13 05.00.09.865 PM       17326 4026476544 1um96ykvtwrh4      1122713586         179347 ALL_ROWS
03-JUL-13 05.00.09.866 PM 03-JUL-13 06.00.26.710 PM       17327 4026476544 1um96ykvtwrh4      1122713586         179347 ALL_ROWS
03-JUL-13 08.00.12.716 PM 03-JUL-13 09.00.00.960 PM       17330 4026476544 1um96ykvtwrh4      1122713586         179347 ALL_ROWS
03-JUL-13 08.00.12.716 PM 03-JUL-13 09.00.00.989 PM       17330 4026476544 1um96ykvtwrh4      1122713586         179347 ALL_ROWS
377865450 is the sql_hash of explain plan given by SQL_PROFILE
select
    2 extractvalue(value(d), '/hint') as outline_hints
    3 from
    4 xmltable('/*/outline_data/hint'
    5 passing (
    6 select
    7 xmltype(other_xml) as xmlval
    8 from
    9 dba_hist_sql_plan
   10 where
   11 sql_id = '&sql_id'
   12 and plan_hash_value = &plan_hash_value
   13 and other_xml is not null
   14   15 ) d;
Enter value for sql_id: 1um96ykvtwrh4
old 11: sql_id = '&sql_id'
new 11: sql_id = '1um96ykvtwrh4'
Enter value for plan_hash_value: 377865450
old 12: and plan_hash_value = &plan_hash_value
new 12: and plan_hash_value = 377865450
OUTLINE_HINTS
IGNORE_OPTIM_EMBEDDED_HINTS
OPTIMIZER_FEATURES_ENABLE('11.2.0.2')
DB_VERSION('11.2.0.2')
ALL_ROWS
OUTLINE_LEAF(@"SEL$B01C6807")
OUTLINE_LEAF(@"SEL$8E13D68A")
OUTLINE_LEAF(@"SET$5715CE2E")
PUSH_PRED(@"SEL$F5BB74E1" "VW"@"SEL$2" 3)
OUTLINE_LEAF(@"SEL$F5BB74E1")
MERGE(@"SEL$2")
OUTLINE(@"SEL$3")
OUTLINE_HINTS
OUTLINE(@"SEL$4")
OUTLINE(@"SET$1")
OUTLINE(@"SEL$F5BB74E1")
MERGE(@"SEL$2")
OUTLINE(@"SEL$1")
OUTLINE(@"SEL$2")
INDEX_RS_ASC(@"SEL$F5BB74E1" "LR"@"SEL$2" ("LINK_RELATIONSHIP"."PXLINKEDREFFROM"
NO_ACCESS(@"SEL$F5BB74E1" "VW"@"SEL$2")
LEADING(@"SEL$F5BB74E1" "LR"@"SEL$2" "VW"@"SEL$2")
OUTLINE_HINTS
USE_NL(@"SEL$F5BB74E1" "VW"@"SEL$2")
INDEX_RS_ASC(@"SEL$8E13D68A" "W"@"SEL$4" ("WORK_COMMON"."PZINSKEY"))
INDEX_RS_ASC(@"SEL$B01C6807" "WORK_BATCH"@"SEL$3" ("WORK_BATCH"."PZINSKEY"))
select id, operation, options, object_name, cost
from dba_hist_sql_plan
where dbid = 4026476544 and sql_id = '1um96ykvtwrh4'
and plan_hash_value = 377865450 2    3    4
    5 ;
    ID OPERATION                      OPTIONS                        OBJECT_NAME                     COST
     0 SELECT STATEMENT                                                                                20
     1 SORT                           ORDER BY                                                         20
     2 FILTER
     3 NESTED LOOPS                                                                                    19
     4 TABLE ACCESS                   BY INDEX ROWID                 LINK_RELATIONSHIP                  5
     5 INDEX                          RANGE SCAN                     RELATIONSHIP_REFFROM               3
     6 VIEW                                                          V_WORK_R_1_0                       7
     7 UNION ALL PUSHED PREDICATE
     8 TABLE ACCESS                   BY INDEX ROWID                 WORK_BATCH                         4
     9 INDEX                          UNIQUE SCAN                    WORK_BATCH_PK                      3
    10 TABLE ACCESS                   BY INDEX ROWID                 WORK_COMMON                        3
    11 INDEX                          UNIQUE SCAN                    WORK_COMMON_PK                     2
EXPLAIN PLAN OF SQL_PROFILE PROVIDED
select * from table(dbms_xplan.display_awr('1um96ykvtwrh4',377865450,4026476544, 'ALL +peeked_binds +ALLSTATS LAST'));
PLAN_TABLE_OUTPUT
SQL_ID 1um96ykvtwrh4
SELECT "PC0".pxObjClass AS "pxObjClass", "PC0".PXINSNAME AS "pxInsName"
, "PC0".WORKTYPENAME AS "WorkTypeName" , "PC0".PYSTATUSWORK AS
"pyStatusWork" , "PC0".PXCREATEDATETIME AS "pxCreateDateTime",
"PC0".LINKEDREFTO as "pxInsHandle" FROM V_FORM_RELATIONSHIPS_R_1_0
"PC0" WHERE ( "PC0".LINKEDREFFROM = :1 ) AND ( "PC0".pxObjClass = :2
    ) ORDER BY "PC0".PXINSNAME DESC , "PC0".PXCREATEDATETIME
Plan hash value: 377865450
| Id | Operation                        | Name                 | E-Rows |E-Bytes| Cost (%CPU)| E-Time   |
|   0 | SELECT STATEMENT                 |                      |        |       |    20 (100)|          |
|   1 | SORT ORDER BY                   |                      |      2 | 1362 |    20   (5)| 00:00:01 |
|   2 |   FILTER                         |                      |        |       |            |          |
|   3 |    NESTED LOOPS                  |                      |      2 | 1362 |    19   (0)| 00:00:01 |
|   4 |     TABLE ACCESS BY INDEX ROWID | LINK_RELATIONSHIP    |      2 |   204 |     5   (0)| 00:00:01 |
|   5 |      INDEX RANGE SCAN            | RELATIONSHIP_REFFROM |      2 |       |     3   (0)| 00:00:01 |
|   6 |     VIEW                         | V_WORK_R_1_0         |      1 |   579 |     7   (0)| 00:00:01 |
|   7 |      UNION ALL PUSHED PREDICATE |                      |        |       |            |          |
|   8 |       TABLE ACCESS BY INDEX ROWID| WORK_BATCH           |      1 |    89 |     4   (0)| 00:00:01 |
|   9 |        INDEX UNIQUE SCAN         | WORK_BATCH_PK        |      1 |       |     3   (0)| 00:00:01 |
| 10 |       TABLE ACCESS BY INDEX ROWID| WORK_COMMON          |      1 |   109 |     3   (0)| 00:00:01 |
| 11 |        INDEX UNIQUE SCAN         | WORK_COMMON_PK       |      1 |       |     2   (0)| 00:00:01 |
Query Block Name / Object Alias (identified by operation id):
     1 - SEL$F5BB74E1
     4 - SEL$F5BB74E1 / LR@SEL$2
     5 - SEL$F5BB74E1 / LR@SEL$2
     6 - SET$5715CE2E / VW@SEL$2
     7 - SET$5715CE2E
     8 - SEL$B01C6807 / WORK_BATCH@SEL$3
     9 - SEL$B01C6807 / WORK_BATCH@SEL$3
    10 - SEL$8E13D68A / W@SEL$4
    11 - SEL$8E13D68A / W@SEL$4
Peeked Binds (identified by position):
     1 - :1 (VARCHAR2(30), CSID=873): 'xxxx-xxx-SERVICEREQUEST-WORK-ACCTMAINT AM-13640'
Note
     - Warning: basic plan statistics not available. These are only collected when:
      * hint 'gather_plan_statistics' is used for the statement or
      * parameter 'statistics_level' is set to 'ALL', at session or system level
OLD EXPLAIN PLAN IS
select * from table(dbms_xplan.display_awr('1um96ykvtwrh4',1122713586,4026476544, 'ALL +peeked_binds +ALLSTATS LAST'));
PLAN_TABLE_OUTPUT
SQL_ID 1um96ykvtwrh4
SELECT "PC0".pxObjClass AS "pxObjClass", "PC0".PXINSNAME AS "pxInsName"
, "PC0".WORKTYPENAME AS "WorkTypeName" , "PC0".PYSTATUSWORK AS
"pyStatusWork" , "PC0".PXCREATEDATETIME AS "pxCreateDateTime",
"PC0".LINKEDREFTO as "pxInsHandle" FROM V_FORM_RELATIONSHIPS_R_1_0
"PC0" WHERE ( "PC0".LINKEDREFFROM = :1 ) AND ( "PC0".pxObjClass = :2
    ) ORDER BY "PC0".PXINSNAME DESC , "PC0".PXCREATEDATETIME
Plan hash value: 1122713586
| Id | Operation                 | Name                  | E-Rows |E-Bytes|E-Temp | Cost (%CPU)| E-Time   |
|   0 | SELECT STATEMENT          |                       |        |       |       |   171K(100)|          |
|   1 | SORT ORDER BY            |                       | 32220 |    20M|    22M|   171K (1)| 00:34:18 |
|   2 |   FILTER                  |                       |        |       |       |            |          |
|   3 |    HASH JOIN              |                       | 32220 |    20M| 3560K|   166K (1)| 00:33:22 |
|   4 |     VIEW                  | index$_join$_002      | 31931 | 3180K|       | 1648   (1)| 00:00:20 |
|   5 |      HASH JOIN            |                       |        |       |       |            |          |
|   6 |       INDEX RANGE SCAN    | RELATIONSHIP_REFFROM | 31931 | 3180K|       |   430   (1)| 00:00:06 |
|   7 |       INDEX FAST FULL SCAN| AK1_LINK_RELATIONSHIP | 31931 | 3180K|       | 1096   (1)| 00:00:14 |
|   8 |     VIEW                  | V_WORK_R_1_0          |   3946K| 2178M|       | 54733   (1)| 00:10:57 |
|   9 |      UNION-ALL            |                       |        |       |       |            |          |
| 10 |       TABLE ACCESS FULL   | WORK_BATCH            |   3910K|   331M|       | 53959   (1)| 00:10:48 |
| 11 |       TABLE ACCESS FULL   | WORK_COMMON           | 35334 | 3761K|       |   774   (1)| 00:00:10 |
Query Block Name / Object Alias (identified by operation id):
     1 - SEL$F5BB74E1
     4 - SEL$838CAA44 / LR@SEL$2
     5 - SEL$838CAA44
     6 - SEL$838CAA44 / indexjoin$_alias$_001@SEL$838CAA44
     7 - SEL$838CAA44 / indexjoin$_alias$_002@SEL$838CAA44
     8 - SET$1        / VW@SEL$2
     9 - SET$1
    10 - SEL$3        / WORK_BATCH@SEL$3
    11 - SEL$4        / W@SEL$4
Peeked Binds (identified by position):
     1 - :1 (VARCHAR2(30), CSID=873): 'xxxxxx-xxx-SERVICEREQUEST-WORK-BD-DOCUMENTREQUEST ACE_BD_DR-166646'
Note
     - Warning: basic plan statistics not available. These are only collected when:
      * hint 'gather_plan_statistics' is used for the statement or
      * parameter 'statistics_level' is set to 'ALL', at session or system level
52 rows selected.
Select sql_id,plan_hash_value,old_hash_value,child_number,OUTLINE_CATEGORY,CPU_TIME,ELAPSED_TIME,SQL_PROFILE from gv$sql where sql_id='1um96ykvtwrh4';
SQL_ID        PLAN_HASH_VALUE OLD_HASH_VALUE CHILD_NUMBER OUTLINE_CA   CPU_TIME ELAPSED_TIME SQL_PROFILE
1um96ykvtwrh4       377865450     3763442152            2                 81989       198629 SYS_SQLPROF_013fa7a18f7c0001
1um96ykvtwrh4      1122713586     3763442152            0              44147289    172322738
1um96ykvtwrh4      1122713586     3763442152            1            1905933242   6101663681
1um96ykvtwrh4       377865450     3763442152            3                 55988       108690 SYS_SQLPROF_013fa7a18f7c0001
FOR QUERY 2
col BEGIN_INTERVAL_TIME for a26
col end_INTERVAL_TIME for a26
select s.begin_interval_time, s.end_interval_time , q.snap_id, q.dbid, q.sql_id,q.VERSION_COUNT, q.plan_hash_value, q.optimizer_cost, q.optimizer_mode
from dba_hist_sqlstat q, dba_hist_snapshot s
where q.dbid = 4026476544 and q.sql_id = '4prk4w6sdtxa5'
and q.snap_id = s.snap_id
and s.begin_interval_time between sysdate-2 and sysdate
order by 1,s.snap_id desc;
BEGIN_INTERVAL_TIME        END_INTERVAL_TIME             SNAP_ID       DBID SQL_ID        PLAN_HASH_VALUE OPTIMIZER_COST OPTIMIZER_
04-JUL-13 12.00.01.427 PM 04-JUL-13 01.00.02.453 PM       17346 4026476544 4prk4w6sdtxa5      3168544609          56710 ALL_ROWS
04-JUL-13 12.00.01.430 PM 04-JUL-13 01.00.02.413 PM       17346 4026476544 4prk4w6sdtxa5       455675889            985 ALL_ROWS
04-JUL-13 12.00.01.430 PM 04-JUL-13 01.00.02.413 PM       17346 4026476544 4prk4w6sdtxa5      3168544609          56710 ALL_ROWS
04-JUL-13 12.00.01.430 PM 04-JUL-13 01.00.02.413 PM       17346 4026476544 4prk4w6sdtxa5       455675889            985 ALL_ROWS
04-JUL-13 12.00.01.430 PM 04-JUL-13 01.00.02.413 PM       17346 4026476544 4prk4w6sdtxa5      3168544609          56710 ALL_ROWS
OLD EXPLAIN PAL
select * from table(dbms_xplan.display_awr('4prk4w6sdtxa5',3168544609,4026476544, 'ALL +peeked_binds +ALLSTATS LAST'));
PLAN_TABLE_OUTPUT
SQL_ID 4prk4w6sdtxa5
SELECT PYID AS "pyID" , PXOBJCLASS AS "pxObjClass" , PZINSKEY AS
"pzInsKey", PZINSKEY as "pxInsHandle" FROM V_WORK_R_1_0   WHERE (
PYID = :1 ) AND ( pxObjClass = :2   )
Plan hash value: 3168544609
| Id | Operation                      | Name            | E-Rows |E-Bytes| Cost (%CPU)| E-Time   |
|   0 | SELECT STATEMENT               |                 |        |       | 53846 (100)|          |
|   1 | VIEW                          | V_WORK_R_1_0    |      2 | 1238 | 53846   (1)| 00:10:47 |
|   2 |   UNION-ALL                    |                 |        |       |            |          |
|   3 |    FILTER                      |                 |        |       |            |          |
|   4 |     TABLE ACCESS FULL          | WORK_BATCH      |      1 |    67 | 53844   (1)| 00:10:47 |
|   5 |    FILTER                      |                 |        |       |            |          |
|   6 |     TABLE ACCESS BY INDEX ROWID| WORK_COMMON     |      1 |   578 |     2   (0)| 00:00:01 |
|   7 |      INDEX RANGE SCAN          | AK1_WORK_COMMON |      1 |       |     1   (0)| 00:00:01 |
Query Block Name / Object Alias (identified by operation id):
     1 - SET$1 / V_WORK_R_1_0@SEL$1
     2 - SET$1
     3 - SEL$2
     4 - SEL$2 / WORK_BATCH@SEL$2
     5 - SEL$3
     6 - SEL$3 / W@SEL$3
     7 - SEL$3 / W@SEL$3
Peeked Binds (identified by position):
     1 - :1 (VARCHAR2(30), CSID=873): 'CM-22180'
Note
     - dynamic sampling used for this statement (level=2)
     - Warning: basic plan statistics not available. These are only collected when:
      * hint 'gather_plan_statistics' is used for the statement or
      * parameter 'statistics_level' is set to 'ALL', at session or system level
NEW EXPLAIN PLAN IS
select * from table(dbms_xplan.display_awr('4prk4w6sdtxa5',455675889,4026476544, 'ALL +peeked_binds +ALLSTATS LAST'));
PLAN_TABLE_OUTPUT
SQL_ID 4prk4w6sdtxa5
SELECT PYID AS "pyID" , PXOBJCLASS AS "pxObjClass" , PZINSKEY AS
"pzInsKey", PZINSKEY as "pxInsHandle" FROM V_WORK_R_1_0   WHERE (
PYID = :1 ) AND ( pxObjClass = :2   )
Plan hash value: 455675889
| Id | Operation                            | Name            | E-Rows |E-Bytes| Cost (%CPU)| E-Time   |    TQ |IN-OUT| PQ Distrib |
|   0 | SELECT STATEMENT                     |                 |        |       |   985 (100)|          |        |      |            |
|   1 | PX COORDINATOR                      |                 |        |       |            |          |        |      |            |
|   2 |   PX SEND QC (RANDOM)                | :TQ10001        |      2 | 1238 |   985   (1)| 00:00:12 | Q1,01 | P->S | QC (RAND) |
|   3 |    BUFFER SORT                       |                 |      2 | 1238 |            |          | Q1,01 | PCWP |            |
|   4 |     VIEW                             | V_WORK_R_1_0    |      2 | 1238 |   985   (1)| 00:00:12 | Q1,01 | PCWP |            |
|   5 |      UNION-ALL                       |                 |        |       |            |          | Q1,01 | PCWP |            |
|   6 |       FILTER                         |                 |        |       |            |          | Q1,01 | PCWC |            |
|   7 |        PX BLOCK ITERATOR             |                 |      1 |    67 |   983   (1)| 00:00:12 | Q1,01 | PCWC |            |
|   8 |         TABLE ACCESS FULL            | WORK_BATCH      |      1 |    67 |   983   (1)| 00:00:12 | Q1,01 | PCWP |            |
|   9 |       BUFFER SORT                    |                 |        |       |            |          | Q1,01 | PCWC |            |
| 10 |        PX RECEIVE                    |                 |      1 |    59 |     2   (0)| 00:00:01 | Q1,01 | PCWP |            |
| 11 |         PX SEND ROUND-ROBIN          | :TQ10000        |      1 |    59 |     2   (0)| 00:00:01 |        | S->P | RND-ROBIN |
| 12 |          FILTER                      |                 |        |       |            |          |        |      |            |
| 13 |           TABLE ACCESS BY INDEX ROWID| WORK_COMMON     |      1 |    59 |     2   (0)| 00:00:01 |        |      |            |
| 14 |            INDEX RANGE SCAN          | AK1_WORK_COMMON |      1 |       |     1   (0)| 00:00:01 |        |      |            |
Query Block Name / Object Alias (identified by operation id):
     1 - SEL$1
     4 - SET$1 / V_WORK_R_1_0@SEL$1
     5 - SET$1
     6 - SEL$2
     8 - SEL$2 / WORK_BATCH@SEL$2
    12 - SEL$3
    13 - SEL$3 / W@SEL$3
    14 - SEL$3 / W@SEL$3
Peeked Binds (identified by position):
     1 - :1 (VARCHAR2(30), CSID=873): 'AM-15042'
Note
     - automatic DOP: Computed Degree of Parallelism is 64
     - SQL profile "SYS_SQLPROF_013fa79ff2ee0000" used for this statement
     - Warning: basic plan statistics not available. These are only collected when:
      * hint 'gather_plan_statistics' is used for the statement or
      * parameter 'statistics_level' is set to 'ALL', at session or system level
53 rows selected.
HINT USED IN EXPLAIN PLAN GIVEN BY SQL_PROFILE
select
   extractvalue(value(d), '/hint') as outline_hints
   from
   xmltable('/*/outline_data/hint'
   passing (
   select
   xmltype(other_xml) as xmlval
   from
   dba_hist_sql_plan
   where
   sql_id = '&sql_id'
   and plan_hash_value = &plan_hash_value
   and other_xml is not null
)) d;
   OUTLINE_HINTS
IGNORE_OPTIM_EMBEDDED_HINTS
OPTIMIZER_FEATURES_ENABLE('11.2.0.2')
DB_VERSION('11.2.0.2')
OPT_PARAM('optimizer_dynamic_sampling' 5)
ALL_ROWS
SHARED(64)
OUTLINE_LEAF(@"SEL$2")
OUTLINE_LEAF(@"SEL$3")
OUTLINE_LEAF(@"SET$1")
OUTLINE_LEAF(@"SEL$1")
NO_ACCESS(@"SEL$1" "V_WORK_R_1_0"@"SEL$1")
INDEX_RS_ASC(@"SEL$3" "W"@"SEL$3" ("WORK_COMMON"."PYID"))
FULL(@"SEL$2" "WORK_BATCH"@"SEL$2")
col OUTLINE_CATEGORY for a10
col SQL_PROFILE for a30
select sql_id,plan_hash_value,old_hash_value,child_number,OUTLINE_CATEGORY,CPU_TIME,ELAPSED_TIME,SQL_PROFILE from gv$sql where sql_id='4prk4w6sdtxa5';
SQL_ID        PLAN_HASH_VALUE OLD_HASH_VALUE CHILD_NUMBER OUTLINE_CA   CPU_TIME ELAPSED_TIME SQL_PROFILE
4prk4w6sdtxa5      3168544609      353644632            0            2633226703   4.4271E+10
4prk4w6sdtxa5       455675889      353644632            1              27225852    759830164 SYS_SQLPROF_013fa79ff2ee0000
4prk4w6sdtxa5       455675889      353644632            2             119988890   9664144040 SYS_SQLPROF_013fa79ff2ee0000
4prk4w6sdtxa5       455675889      353644632            3              85872011   5942746451 SYS_SQLPROF_013fa79ff2ee0000
4prk4w6sdtxa5      3168544609      353644632            0             335776954    337580538
4prk4w6sdtxa5      3168544609      353644632            1             399056329    401261240
4prk4w6sdtxa5      3168544609      353644632            2             484240383    486679352
4prk4w6sdtxa5      3168544609      353644632            3             401375979    492360355
4prk4w6sdtxa5      3168544609      353644632            4             930830490   2.2156E+10
4prk4w6sdtxa5      3168544609      353644632            5             403837610    472368680
4prk4w6sdtxa5      3168544609      353644632            6            1136393235   2.5397E+10
4prk4w6sdtxa5      3168544609      353644632            7             858015552   1.6636E+10
4prk4w6sdtxa5       455675889      353644632            8              68884598   6001624174 SYS_SQLPROF_013fa79ff2ee0000
4prk4w6sdtxa5       455675889      353644632            9              21730702    629077530 SYS_SQLPROF_013fa79ff2ee0000
4prk4w6sdtxa5       455675889      353644632           10              93504893   8216578447 SYS_SQLPROF_013fa79ff2ee0000
OTHER INFO
SQL> select table_name,owner,index_name,INDEX_TYPE from dba_indexes where table_name in ('WORK_BATCH','WORK_COMMON','LINK_RELATIONSHIP');
TABLE_NAME                     OWNER                          INDEX_NAME                     INDEX_TYPE
LINK_RELATIONSHIP              ACE                            SYS_IL0000120332C00018$$       LOB
WORK_BATCH                     ACE                            SYS_IL0000120308C00085$$       LOB
WORK_COMMON                    ACE                            SYS_IL0000243612C00085$$       LOB
LINK_RELATIONSHIP              ACE                            LINK_RELATIONSHIP_PK           NORMAL
LINK_RELATIONSHIP              ACE                            AK1_LINK_RELATIONSHIP          NORMAL
LINK_RELATIONSHIP              ACE                            RELATIONSHIP_REFFROM           NORMAL
WORK_BATCH                     ACE                            WORK_BATCH_PK                  NORMAL
WORK_BATCH                     ACE                            IDX1_WORK_BATCH                NORMAL
WORK_COMMON                    ACE                            AK2_WORK_COMMON                NORMAL
WORK_COMMON                    ACE                            AK1_WORK_COMMON                NORMAL
WORK_COMMON                    ACE                            WORK_COMMON_PK                 NORMAL
col object_name for a25
select created,object_name,object_type,owner,LAST_DDL_TIME from dba_objects where object_name in ('WORK_BATCH','WORK_COMMON','WORK_BATCH_PK','WORK_COMMON_PK','AK1_LINK_RELATIONSHIP','RELATIONSHIP_REFFROM')
    2
CREATED     OBJECT_NAME               OBJECT_TYPE         OWNER                          LAST_DDL_TI
28-JUN-2012 WORK_BATCH                TABLE               ACE                            15-JUN-2013
28-JUN-2012 WORK_BATCH_PK             INDEX               ACE                            29-MAY-2013
30-NOV-2012 RELATIONSHIP_REFFROM      INDEX               ACE                            03-JUL-2013
23-FEB-2013 AK1_LINK_RELATIONSHIP     INDEX               ACE                            23-FEB-2013
15-JUN-2013 WORK_COMMON               TABLE               ACE                            15-JUN-2013
15-JUN-2013 WORK_COMMON_PK            INDEX               ACE                            15-JUN-2013
09-MAR-2013 WORK_BATCH                SYNONYM             ACE_USER                       09-MAR-2013
col COLUMN_NAME for a20
Select INDEX_NAME,TABLE_NAME,COLUMN_NAME,COLUMN_POSITION from dba_ind_columns where table_name in ('WORK_BATCH','WORK_COMMON','LINK_RELATIONSHIP');
INDEX_NAME                     TABLE_NAME                     COLUMN_NAME          COLUMN_POSITION
RELATIONSHIP_REFFROM           LINK_RELATIONSHIP              PXLINKEDREFFROM                    1
AK1_LINK_RELATIONSHIP          LINK_RELATIONSHIP              PXLINKEDREFTO                      1
LINK_RELATIONSHIP_PK           LINK_RELATIONSHIP              PZINSKEY                           1
IDX1_WORK_BATCH                WORK_BATCH                     CAPTUREUNIQUEID                    1
WORK_BATCH_PK                  WORK_BATCH                     PZINSKEY                           1
WORK_COMMON_PK                 WORK_COMMON                    PZINSKEY                           1
AK1_WORK_COMMON                WORK_COMMON                    PYID                               1
AK2_WORK_COMMON                WORK_COMMON                    PXOBJCLASS                         1
SQL> select distinct tablespace_name from dba_tablespaces where tablespace_name like '%INDEX%';
TABLESPACE_NAME
ACE_INDEXES_M
RBS_INDEXES_S
SPS_INDEXES_S
ACE_INDEXES_S
ACE_INDEXES_L
FI_INDEXES_S
FI_INDEXES_M
RBS_INDEXES_M
8 rows selected.
   col SEARCH_CONDITION for a25
   col OWNER for a10
   select OWNER,CONSTRAINT_NAME,CONSTRAINT_TYPE,TABLE_NAME,SEARCH_CONDITION,INDEX_NAME from dba_constraints where TABLE_NAME in ('WORK_BATCH','WORK_COMMON','LINK_RELATIONSHIP')
   OWNER      CONSTRAINT_NAME                C TABLE_NAME                     SEARCH_CONDITION          INDEX_NAME
ACE        SYS_C00150550                  C WORK_COMMON                    "PZINSKEY" IS NOT NULL
ACE        WORK_BATCH_PK                  P WORK_BATCH                                               WORK_BATCH_PK
ACE        LINK_RELATIONSHIP_PK           P LINK_RELATIONSHIP                                        LINK_RELATIONSHIP_PK
ACE        WORK_COMMON_PK                 P WORK_COMMON                                              WORK_COMMON_PK
select attr_val hint
from dba_sql_profiles p, sqlprof$attr h
where p.signature = h.signature
and name like ('SYS_SQLPROF_013fa7a18f7c0001')
order by attr#
   select LAST_ANALYZED,SAMPLE_SIZE,num_rows from dba_tables where table_name in ('WORK_BATCH','WORK_COMMON','LINK_RELATIONSHIP');
LAST_ANALYZ SAMPLE_SIZE   NUM_ROWS
02-JUL-2013     4122880    4122880
02-JUL-2013       81108      81108
03-JUL-2013       40802      40802
SQL> select count(pzinskey) from ace.WORK_BATCH;
COUNT(PZINSKEY)
    4138044
SQL> select count(pzinskey) from ace.WORK_COMMON;
COUNT(PZINSKEY)
      40805

Hi,
i think you should give a try on baseline.
Profiles are more subject to stats ad dynamic sampling.
You can find this useful:
Kerry Osborne SQL Profiles Disable Automatic Dynamic Sampling
This doesn't match your case but can give some advices.
Regs,
Drew

How to check if an SQL profile is being used or not?

Hi,
We have a couple of SQL profiles and outlines in the database. There has been a couple of code changes and it is now difficult to keep track if an SQL profile or an Outline is still being used? Is there any way to find that?
Thanks in advance

Find the entry corresponding to the SQL statement you are reviewing in V$SQL. Look at OUTLINE_CATEGORY and SQL_PROFILE columns. NULL indicates that no Outline/Profile was used.

Replication SQL Server 7 Database to Oracle 9i

Hi -
I'm new to Database Replication, what are the steps for database replication from a MS SQL Server 7 database to Oracle 9i? Eventually this SQL Server Database will be going to SQL Server 2000 are the steps different, if so what are they?
Thanks
Much

I do not what you mean with Replicate between SQL Server and Oracle. Perhaps you mean migrate from SQL Server to Oracle or to stablish a transparent gateway.
I am going to give you this reference:
Migration Workbench Reference Guide for Microsoft SQL Server and Sybase Adaptive Server Migrations Contents / Search / Index / PDF
Heterogeneous Connectivity Administrator's Guide Contents / Search / Index / PDF
http://otn.oracle.com/pls/db92/db92.docindex?remark=homepage
Joel P�rez

SQL Profiler's equivalent in Oracle.

Hi All,
We are using Oracle 10g as backend for our application. We would like to see which database objects (stored procedures, functions, triggers etc) are getting called at the Oracle database server when various users connect to the application and they perfrom various transactions from the UI.
There is a similar tool available in SQL server. That is SQL Profiler.
Is there any similar tool which is present for Oracle database server for tracking the database objects invoked?
Please suggest any option available in Oracle or any third party tools pluggable into Oracle database.
Thanks,

U can view the active processes from the V$PROCESS provided u have privileges on this view.

Interaction between Database and Forms Developer

Can someone tell me the how can i make a successful connection between database 9i ans developers suites 9i so that i can ru them on a computer to develop applications. if there is any procedure please let me know or send me thelink. Also tell me how to install both of them i mean the order of installation. Your help will be highly appreciated!
Thank
Muhammad Umair

Install each one of them in a different oracle home.
Once installed you need to configure a sql*net connection from the Forms oracle home.
You can use the sqlnet easy config utility for this.

Alert log: failed to establish dependency between database and diskgroup

Hi, I have a database 11.2.0 with ASM. When I startup an instance I see this error in alert log:
ERROR: failed to establish dependency between database SPBUFOR and diskgroup resource ora.SPBUFOR_FLASH.dg
SPBUFOR_FLASH is a diskgroup where a flash recovery area is located.
Database is opened cleanly but I need to know that everything works fine.
How can I resolve this issue ?

ASM ALERT LOG:
Wed Oct 05 15:35:12 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/oracle/product/11.2.0/grid/dbs/arch
Autotune of undo retention is turned on.
IMODE=BR
ILAT =0
LICENSE_MAX_USERS = 0
SYS auditing is disabled
NOTE: Volume support enabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Automatic Storage Management option.
Using parameter settings in server-side spfile +CSA_DATA/asm/asmparameterfile/registry.253.758208241
System parameters with non-default values:
large_pool_size = 12M
instance_type = "asm"
remote_login_passwordfile= "EXCLUSIVE"
asm_diskgroups = "CSA_FLASH"
asm_diskgroups = "SPBUFOR_DATA"
asm_diskgroups = "SPBUFOR_FLASH"
asm_power_limit = 1
diagnostic_dest = "/u01/app/oracle"
Wed Oct 05 15:35:13 2011
PMON started with pid=2, OS id=24108
Wed Oct 05 15:35:14 2011
VKTM started with pid=3, OS id=24112 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Wed Oct 05 15:35:14 2011
GEN0 started with pid=4, OS id=24118
Wed Oct 05 15:35:14 2011
DIAG started with pid=5, OS id=24122
Wed Oct 05 15:35:14 2011
PSP0 started with pid=6, OS id=24127
Wed Oct 05 15:35:14 2011
DIA0 started with pid=7, OS id=24131
Wed Oct 05 15:35:14 2011
MMAN started with pid=8, OS id=24135
Wed Oct 05 15:35:14 2011
DBW0 started with pid=9, OS id=24139
Wed Oct 05 15:35:14 2011
LGWR started with pid=10, OS id=24143
Wed Oct 05 15:35:14 2011
CKPT started with pid=11, OS id=24148
Wed Oct 05 15:35:14 2011
SMON started with pid=12, OS id=24157
Wed Oct 05 15:35:14 2011
RBAL started with pid=13, OS id=24163
Wed Oct 05 15:35:14 2011
GMON started with pid=14, OS id=24173
Wed Oct 05 15:35:14 2011
MMON started with pid=15, OS id=24177
Wed Oct 05 15:35:14 2011
MMNL started with pid=16, OS id=24181
ORACLE_BASE from environment = /u01/app/oracle
Wed Oct 05 15:35:15 2011
SQL> ALTER DISKGROUP ALL MOUNT
NOTE: Diskgroups listed in ASM_DISKGROUPS are
CSA_FLASH
SPBUFOR_DATA
SPBUFOR_FLASH
Diskgroup with spfile:CSA_DATA
NOTE: cache registered group CSA_DATA number=1 incarn=0x75fe76df
NOTE: cache began mount (first) of group CSA_DATA number=1 incarn=0x75fe76df
NOTE: cache registered group CSA_FLASH number=2 incarn=0x760e76e0
NOTE: cache began mount (first) of group CSA_FLASH number=2 incarn=0x760e76e0
NOTE: cache registered group SPBUFOR_DATA number=3 incarn=0x760e76e1
NOTE: cache began mount (first) of group SPBUFOR_DATA number=3 incarn=0x760e76e1
NOTE: cache registered group SPBUFOR_FLASH number=4 incarn=0x761e76e2
NOTE: cache began mount (first) of group SPBUFOR_FLASH number=4 incarn=0x761e76e2
NOTE: Loaded library: /opt/oracle/extapi/64/asm/orcl/1/libasm.so
NOTE: Assigning number (1,0) to disk (ORCL:CSA_D1)
NOTE: Assigning number (1,1) to disk (ORCL:CSA_D2)
NOTE: Assigning number (2,0) to disk (ORCL:CSA_F1)
NOTE: Assigning number (2,1) to disk (ORCL:CSA_F2)
NOTE: Assigning number (3,0) to disk (ORCL:SPBUFOR_D1)
NOTE: Assigning number (3,1) to disk (ORCL:SPBUFOR_D2)
NOTE: Assigning number (3,2) to disk (ORCL:SPBUFOR_D3)
NOTE: Assigning number (4,0) to disk (ORCL:SPBUFOR_F1)
NOTE: Assigning number (4,1) to disk (ORCL:SPBUFOR_F2)
NOTE: start heartbeating (grp 1)
kfdp_query(CSA_DATA): 6
kfdp_queryBg(): 6
NOTE: cache opening disk 0 of grp 1: CSA_D1 label:CSA_D1
NOTE: F1X0 found on disk 0 au 2 fcn 0.0
NOTE: cache opening disk 1 of grp 1: CSA_D2 label:CSA_D2
NOTE: cache mounting (first) external redundancy group 1/0x75FE76DF (CSA_DATA)
NOTE: cache recovered group 1 to fcn 0.25573
NOTE: LGWR attempting to mount thread 1 for diskgroup 1 (CSA_DATA)
NOTE: LGWR found thread 1 closed at ABA 4.2486
NOTE: LGWR mounted thread 1 for diskgroup 1 (CSA_DATA)
NOTE: LGWR opening thread 1 at fcn 0.25573 ABA 5.2487
NOTE: cache mounting group 1/0x75FE76DF (CSA_DATA) succeeded
NOTE: cache ending mount (success) of group CSA_DATA number=1 incarn=0x75fe76df
NOTE: start heartbeating (grp 2)
kfdp_query(CSA_FLASH): 8
kfdp_queryBg(): 8
NOTE: cache opening disk 0 of grp 2: CSA_F1 label:CSA_F1
NOTE: F1X0 found on disk 0 au 2 fcn 0.0
NOTE: cache opening disk 1 of grp 2: CSA_F2 label:CSA_F2
NOTE: cache mounting (first) external redundancy group 2/0x760E76E0 (CSA_FLASH)
NOTE: cache recovered group 2 to fcn 0.49881
NOTE: LGWR attempting to mount thread 1 for diskgroup 2 (CSA_FLASH)
NOTE: LGWR found thread 1 closed at ABA 3.5793
NOTE: LGWR mounted thread 1 for diskgroup 2 (CSA_FLASH)
NOTE: LGWR opening thread 1 at fcn 0.49881 ABA 4.5794
NOTE: cache mounting group 2/0x760E76E0 (CSA_FLASH) succeeded
NOTE: cache ending mount (success) of group CSA_FLASH number=2 incarn=0x760e76e0
NOTE: start heartbeating (grp 3)
kfdp_query(SPBUFOR_DATA): 10
kfdp_queryBg(): 10
NOTE: cache opening disk 0 of grp 3: SPBUFOR_D1 label:SPBUFOR_D1
NOTE: F1X0 found on disk 0 au 2 fcn 0.0
NOTE: cache opening disk 1 of grp 3: SPBUFOR_D2 label:SPBUFOR_D2
NOTE: cache opening disk 2 of grp 3: SPBUFOR_D3 label:SPBUFOR_D3
NOTE: cache mounting (first) external redundancy group 3/0x760E76E1 (SPBUFOR_DATA)
NOTE: cache recovered group 3 to fcn 0.317867
NOTE: LGWR attempting to mount thread 1 for diskgroup 3 (SPBUFOR_DATA)
NOTE: LGWR found thread 1 closed at ABA 3.8570
NOTE: LGWR mounted thread 1 for diskgroup 3 (SPBUFOR_DATA)
NOTE: LGWR opening thread 1 at fcn 0.317867 ABA 4.8571
NOTE: cache mounting group 3/0x760E76E1 (SPBUFOR_DATA) succeeded
NOTE: cache ending mount (success) of group SPBUFOR_DATA number=3 incarn=0x760e76e1
NOTE: start heartbeating (grp 4)
kfdp_query(SPBUFOR_FLASH): 12
kfdp_queryBg(): 12
NOTE: cache opening disk 0 of grp 4: SPBUFOR_F1 label:SPBUFOR_F1
NOTE: F1X0 found on disk 0 au 2 fcn 0.0
NOTE: cache opening disk 1 of grp 4: SPBUFOR_F2 label:SPBUFOR_F2
NOTE: cache mounting (first) external redundancy group 4/0x761E76E2 (SPBUFOR_FLASH)
NOTE: cache recovered group 4 to fcn 0.16114
NOTE: LGWR attempting to mount thread 1 for diskgroup 4 (SPBUFOR_FLASH)
NOTE: LGWR found thread 1 closed at ABA 2.1922
NOTE: LGWR mounted thread 1 for diskgroup 4 (SPBUFOR_FLASH)
NOTE: LGWR opening thread 1 at fcn 0.16114 ABA 3.1923
NOTE: cache mounting group 4/0x761E76E2 (SPBUFOR_FLASH) succeeded
NOTE: cache ending mount (success) of group SPBUFOR_FLASH number=4 incarn=0x761e76e2
kfdp_query(CSA_DATA): 13
kfdp_queryBg(): 13
NOTE: Instance updated compatible.asm to 11.2.0.0.0 for grp 1
SUCCESS: diskgroup CSA_DATA was mounted
kfdp_query(CSA_FLASH): 14
kfdp_queryBg(): 14
NOTE: Instance updated compatible.asm to 11.2.0.0.0 for grp 2
SUCCESS: diskgroup CSA_FLASH was mounted
kfdp_query(SPBUFOR_DATA): 15
kfdp_queryBg(): 15
NOTE: Instance updated compatible.asm to 11.2.0.0.0 for grp 3
SUCCESS: diskgroup SPBUFOR_DATA was mounted
kfdp_query(SPBUFOR_FLASH): 16
kfdp_queryBg(): 16
NOTE: Instance updated compatible.asm to 11.2.0.0.0 for grp 4
SUCCESS: diskgroup SPBUFOR_FLASH was mounted
SUCCESS: ALTER DISKGROUP ALL MOUNT
SQL> ALTER DISKGROUP ALL ENABLE VOLUME ALL
SUCCESS: ALTER DISKGROUP ALL ENABLE VOLUME ALL
NOTE: diskgroup resource ora.CSA_DATA.dg is online
NOTE: diskgroup resource ora.CSA_FLASH.dg is online
NOTE: diskgroup resource ora.SPBUFOR_DATA.dg is online
NOTE: diskgroup resource ora.SPBUFOR_FLASH.dg is online
Wed Oct 05 15:35:44 2011
Starting background process ASMB
Wed Oct 05 15:35:44 2011
ASMB started with pid=18, OS id=24330
Thu Oct 06 11:48:19 2011
SQL> alter diskgroup SPBUFOR_DATA check all
NOTE: starting check of diskgroup SPBUFOR_DATA
kfdp_checkDsk(): 17
kfdp_checkDsk(): 18
Thu Oct 06 11:48:30 2011
kfdp_checkDsk(): 19
SUCCESS: check of diskgroup SPBUFOR_DATA found no errors
SUCCESS: alter diskgroup SPBUFOR_DATA check all
Thu Oct 06 11:48:56 2011
SQL> alter diskgroup SPBUFOR_FLASH check all
NOTE: starting check of diskgroup SPBUFOR_FLASH
kfdp_checkDsk(): 20
kfdp_checkDsk(): 21
SUCCESS: check of diskgroup SPBUFOR_FLASH found no errors
SUCCESS: alter diskgroup SPBUFOR_FLASH check all

Parallel database connections and single query between databases

Hi, I am looking to execute this SQL query between 2 different databases to update a local database based on data selected from a remote one.
e.g.:
- Local database name: db1
- local database schema: dbo
- local database table1
- remote database name: db2
- remote database schema: dbo
- Remote database table: table2
- Query: "SELECT * FROM db2.dbo.table2 WHERE NOT EXISTS(SELECT * FROM db1.dbo.table1)" <- This gets e the record set i would need to insert, and I already have a vi to do that kinda thing.
How do I go about this?
Thanks,
Mohamed

Mohamed,
There is a VI in the Database Connectivity Toolkit that allows you to execute SQL queries: DB Tools Execute Query.
http://zone.ni.com/reference/en-XX/help/370016E-01/lvdatabase/db_tools_execute_query/
Is this what you are looking for?
Drew T.
NIC AE Specialist

Sql profiler analysis services discover begin really slow

Hi,
When we are trying to run MDX query on a cube, it takes really long time to open. So we tried to monitor using SQL Profiler, it shows "Discover begin, 5-mdschema_dimensions" this step takes really long.
We've researched some threads, but couldn't find why this step is taking so long. Can anyone please let us know if this is related to anything which is affecting performance?
Appreciate for your help.

Can you post the query? Dimensions? Populations?
Troubleshooting MDX queries:
http://bluewatersql.wordpress.com/2013/05/06/troubleshooting-mdx-queries/
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Transferring SQL Profiles between databases

Similar Messages

Maybe you are looking for