Re-run a single SQL statement on several report page

Hello

I have a Page containing reports 3 and I was wondering if it is possible to re - run only one of these reports using a button or preferably a Select list that allows me to choose which 3 reports I want to ' Refresh/re-run '. I'm wrong completely here but I assumed that you choose the option to send a Page causes all regions to refresh that is re - run SQL queries, they are "based on". Any suggestion or correction to my hypothesis would be welcome.

Kind regards

Kevin.

KevinFitz wrote:

Each query region will in the sense of 'SELECT MAX' (customer_nr) + 1 as a customernrcnt customer and I expected that the value of the counter is displayed in an area increment as a result of change/selecting a value in the list.

Is it realistic for me to see the results, I think using this method?

Is - it there any activity in the other database sessions that will result in CUSTOMER_NR is incremented? If this isn't the case, then no, it not there no possibility to see any increase in the numbers. If you have a defined sequence and report on it, then refresh the reports will show a difference:

select customer_seq.nextval seq from dual

Tags: Database

Similar Questions

run in parallel sql statement block
Hello
I'm looking for a way to run 2 blocks from the sql statement at the same time in sqlplus

Block1
drop table CTSGLOB_TABLE;
create the table CTSGLOB_TABLE select * from CTSGLOB_VIEW;
create index TEMPS_CTSGLOB_IDX ON CTSGLOB_TABLE("TEMPS");
create index ORGA_CTSGLOB_IDX ON CTSGLOB_TABLE("ORGA");
create index RUBSRH_CTSGLOB_IDX ON CTSGLOB_TABLE("RUBSRH");

Block2
drop table CTSGLOB_TABLE_2;
create the table CTSGLOB_TABLE_2 select * from CTSGLOB_VIEW_2;
create index TEMPS_CTSGLOB_IDX_2 ON CTSGLOB_TABLE_2("TEMPS");
create index ORGA_CTSGLOB_IDX_2 ON CTSGLOB_TABLE_2("ORGA");
create index RUBSRH_CTSGLOB_IDX_2 ON CTSGLOB_TABLE_2("RUBSRH");

I know that I can open 2 client session to run, but I would like to know another way.

Best regards
Jean-Marc
Well, that depends on what you mean exactly when you say "run 2 blocks from the sql statement at the same time in sqlplus '...
You can also copy all statements in a sql script and run that, just.
If this isn't what you want, then please explain why.

Run the second sql statement only if the first sql statement is set to zero.
Hey guys I seem to have a mental block here. I have two sql statements. I would like to than the second to run only if the first sql statement is set to zero. I know that I can use PLsql but I would really like to see if I can do this with sql upward. Your answers are very much appreciated.
This is the first sql
```
  Select     ft.fund_code, 
             ft.orgn_code, 
             ft.acct_code, 
             ft.amount, 
             fb.owner_pidm, 
             ft.prog_code      
      from ftrbremb fb , ftcractg ft
      where fb.doc_code = 'TR000038'
      and fb.ftpbport_id = ft.ftpbport_id
```
second sql statement
```
     Select ft.fund_code, 
             ft.orgn_code, 
             ft.acct_code, 
             ft.amount, 
             fb.owner_pidm, 
             ft.prog_code      
      from ftrbremb fb , ftcractg ft, ftprexps fx
      where fb.doc_code = 'TR000038'
      --and fb.ftpbport_id = ft.ftpbport_id
      and fx.ftrbremb_id = fb.id
      and ft.ftprexps_id = fx.id;
```
How can I combine these two statements together so that when the first is null the second run. As a bonus, I want to get just the first line as well.
Any help would be greatly appreciated. I tried to accomplish with the case statement but it dosent everything seems to work for me.
Thank you
Miguel,

the idea is simple: join the two queries (via the union of all) and to change the second part as to return only the rows if the first query returns no rows by changing the NOT EXISTS (first request). Hope I made it clear... ;)

SQL statements consume several times
Hi all

Recently I have faced the issue, 10 processes are taking place (means 10 sql statements) 4 declarations are huge time. For timebieng, I killed all sessions, but I know that's not just solve the problem. Can someone please explain briefly how to analyze the issue, root cause conclusion and giving if possible solutions for example please...

What are the parameter that should be considered for the solution.

Concerning

KRISHNA
Hello Krishna,

The steps you need to take are explained in this thread:
How to post a SQL tuning application HOW TO: post a request for tuning SQL - model poster statement

In short:
review the query plans, or ideally: trace/tkprof processes.
After the output here, as well as your database version and optimizer parameter values.

How to run a SQL statement to use a specific implementation plan

Hi all
I have a SQL that has recently been run badly. I tried the Advisor tuning SQL for the given SQL query and it gives the following information:
GENERAL INFORMATION SECTION
-------------------------------------------------------------------------------
Name of the task of tuning: 2q94zb7djr2xn
The owner task of tuning: LMDBPROD
Type of work: single SQL statement
County of execution: 2
The current run: EXEC_8869
Type of execution: TUNE SQL
Scope: COMPLETE
Time Limit (seconds): 60
Status: COMPLETED
Started on the: 03/02/2014-20:43:39
To the: 03/02/2014 20:44:25
-------------------------------------------------------------------------------
Name of the schema: LMDBPROD
SQL ID: 2q94zb7djr2xn
SQL text: SELECT NPCOMMON. FGET_ACTION_CODE (ORDNUM) ACTIONCODE, STATUS,
SUMA COUNT (*) FROM SORDER, WHERE HEADORDNUM IS NOT NULL AND
NPCOMMON. FGET_PRODUCTOFFER4ORDER (ORDNUM) IN (SELECT ID FROM)
PRODUCTOFFER WHERE PPSPECIFICATION_ID IN (SELECT ID FROM)
PPSPECIFICATION WHERE PCLASS_CODE IN (SELECT PCLASS_CODE FROM)
ARUSERGROUP WHERE CODE IN (SELECT ARUSERGROUP_CODE FROM)
ARUSER_ARUSERGROUP WHERE ARUSER_USERNAME =: B1 AND STATUS = '1')
AND STATUS = '1'))) GROUP BY NPCOMMON. FGET_ACTION_CODE (ORDNUM),
STATUS
-------------------------------------------------------------------------------
RESULTS SECTION (1 result)
-------------------------------------------------------------------------------
1-alternative Plan conclusion
---------------------------
Some implementation plans alternative for this statement was found by searching
performance data in real-time and historical of the system.
The following table lists these plans sorted by their average time.
See "SECTION of ALTERNATIVE PLANS" section for detailed information on each
plan.
plan ID hash last visit elapsed note of origin (s)
-- ---------- -------------------- ------------ --------------- ----------------
1 617797893 2013-07-11/07: 45:20 9.555 no reproducible STS
2 1311086720 2014-01-31/04: 00:44 19.569 AWR
3 1226863820 2014-01-31/18: 00:24 AWR 21.158
4 1359606848 2014-02-03/16: 00:34 21.492 AWR original plan
The plan with hash 617797893 seems the most efficient one and is based on some specific SQL Tuning Set I ran on this time. But the note says that the plan is not reproducible. Is there anyway how can I force the SQL statement to execute the plan? The database version is Standard Edition 11.2.0.1.0
Best regards
Rodriguez

Hello

I think you can use this

http://rnm1978.WordPress.com/2011/06/28/Oracle-11g-how-to-force-a-sql_id-to-use-a-plan_hash_value-using-SQL-baselines/

before 11 g, we used to create an outline stored for this.

concerning

Plans of multiple executions for the same SQL statement

Dear experts,

awrsqrpt. SQL shows several plans for a single SQL statement executions. How is it possible that a single SQL statement will be several Plans of executions within the AWR report.

Here is the output of the awrsqrpt for your reference.

WORKLOAD REPOSITORY SQL Report

Snapshot Period Summary

DB Name         DB Id    Instance     Inst Num Release     RAC Host
------------ ----------- ------------ -------- ----------- --- ------------
TESTDB          2157605839 TESTDB1               1 10.2.0.3.0  YES testhost1

              Snap Id      Snap Time      Sessions Curs/Sess
            --------- ------------------- -------- ---------
Begin Snap:     32541 11-Oct-08 21:00:13       248     141.1
  End Snap:     32542 11-Oct-08 21:15:06       245     143.4
   Elapsed:               14.88 (mins)
   DB Time:               12.18 (mins)

SQL Summary                            DB/Inst: TESTDB/TESTDB1  Snaps: 32541-32542

                Elapsed
   SQL Id      Time (ms)
------------- ----------
51szt7b736bmg     25,131
Module: SQL*Plus
UPDATE TEST SET TEST_TRN_DAY_CL = (SELECT (NVL(ACCT_CR_BAL,0) + NVL(ACCT_DR_BAL,
0)) FROM ACCT WHERE ACCT_TRN_DT = (:B1 ) AND TEST_ACC_NB = ACCT_ACC_NB(+)) WHERE
 TEST_BATCH_DT = (:B1 )

          -------------------------------------------------------------

SQL ID: 51szt7b736bmg                  DB/Inst: TESTDB/TESTDB1  Snaps: 32541-32542
-> 1st Capture and Last Capture Snap IDs
   refer to Snapshot IDs witin the snapshot range
-> UPDATE TEST SET TEST_TRN_DAY_CL = (SELECT (NVL(ACCT_CR_BAL,0) + NVL(AC...

    Plan Hash           Total Elapsed                 1st Capture   Last Capture
#   Value                    Time(ms)    Executions       Snap ID        Snap ID
--- ---------------- ---------------- ------------- ------------- --------------
1   2960830398                 25,131             1         32542          32542
2   3834848140                      0             0         32542          32542
          -------------------------------------------------------------


Plan 1(PHV: 2960830398)
-----------------------

Plan Statistics                        DB/Inst: TESTDB/TESTDB1  Snaps: 32541-32542
-> % Total DB Time is the Elapsed Time of the SQL statement divided
   into the Total Database Time multiplied by 100

Stat Name                                Statement   Per Execution % Snap
---------------------------------------- ---------- -------------- -------
Elapsed Time (ms)                            25,131       25,130.7     3.4
CPU Time (ms)                                23,270       23,270.2     3.9
Executions                                        1            N/A     N/A
Buffer Gets                               2,626,166    2,626,166.0    14.6
Disk Reads                                      305          305.0     0.3
Parse Calls                                       1            1.0     0.0
Rows                                        371,735      371,735.0     N/A
User I/O Wait Time (ms)                         564            N/A     N/A
Cluster Wait Time (ms)                            0            N/A     N/A
Application Wait Time (ms)                        0            N/A     N/A
Concurrency Wait Time (ms)                        0            N/A     N/A
Invalidations                                     0            N/A     N/A
Version Count                                     2            N/A     N/A
Sharable Mem(KB)                                 26            N/A     N/A
          -------------------------------------------------------------

Execution Plan
------------------------------------------------------------------------------------------------
| Id  | Operation                    | Name            | Rows  | Bytes | Cost (%CPU)| Time     |
------------------------------------------------------------------------------------------------
|   0 | UPDATE STATEMENT             |                 |       |       |  1110 (100)|          |
|   1 |  UPDATE                      | TEST            |       |       |            |          |
|   2 |   TABLE ACCESS FULL          | TEST            |   116K|  2740K|  1110   (2)| 00:00:14 |
|   3 |   TABLE ACCESS BY INDEX ROWID| ACCT            |     1 |    26 |     5   (0)| 00:00:01 |
|   4 |    INDEX RANGE SCAN          | ACCT_DT_ACC_IDX |     1 |       |     4   (0)| 00:00:01 |
------------------------------------------------------------------------------------------------




Plan 2(PHV: 3834848140)
-----------------------

Plan Statistics                        DB/Inst: TESTDB/TESTDB1  Snaps: 32541-32542
-> % Total DB Time is the Elapsed Time of the SQL statement divided
   into the Total Database Time multiplied by 100

Stat Name                                Statement   Per Execution % Snap
---------------------------------------- ---------- -------------- -------
Elapsed Time (ms)                                 0            N/A     0.0
CPU Time (ms)                                     0            N/A     0.0
Executions                                        0            N/A     N/A
Buffer Gets                                       0            N/A     0.0
Disk Reads                                        0            N/A     0.0
Parse Calls                                       0            N/A     0.0
Rows                                              0            N/A     N/A
User I/O Wait Time (ms)                           0            N/A     N/A
Cluster Wait Time (ms)                            0            N/A     N/A
Application Wait Time (ms)                        0            N/A     N/A
Concurrency Wait Time (ms)                        0            N/A     N/A
Invalidations                                     0            N/A     N/A
Version Count                                     2            N/A     N/A
Sharable Mem(KB)                                 26            N/A     N/A
          -------------------------------------------------------------

Execution Plan
---------------------------------------------------------------------------------------------
| Id  | Operation                    | Name         | Rows  | Bytes | Cost (%CPU)| Time     |
---------------------------------------------------------------------------------------------
|   0 | UPDATE STATEMENT             |              |       |       |     2 (100)|          |
|   1 |  UPDATE                      | TEST         |       |       |            |          |
|   2 |   TABLE ACCESS BY INDEX ROWID| TEST         |     1 |    28 |     2   (0)| 00:00:01 |
|   3 |    INDEX RANGE SCAN          | TEST_DT_IND  |     1 |       |     1   (0)| 00:00:01 |
|   4 |   TABLE ACCESS BY INDEX ROWID| ACCT         |     1 |    26 |     4   (0)| 00:00:01 |
|   5 |    INDEX RANGE SCAN          | INDX_ACCT_DT |     1 |       |     3   (0)| 00:00:01 |
---------------------------------------------------------------------------------------------



Full SQL Text

SQL ID       SQL Text
------------ -----------------------------------------------------------------
51szt7b736bm UPDATE TEST SET TEST_TRN_DAY_CL = (SELECT (NVL(ACCT_CR_BAL, 0) +
              NVL(ACCT_DR_BAL, 0)) FROM ACCT WHERE ACCT_TRN_DT = (:B1 ) AND PB
             RN_ACC_NB = ACCT_ACC_NB(+)) WHERE TEST_BATCH_DT = (:B1 )

Your contribution is very much appreciated.

Thank you for taking your time to answer my question.

Concerning

Oracle Lover3 wrote:
How will I know (from Plan 1 and Plan 2) whose execution plan chose for the current run?

Since you're already on 10.2, you can identify the actual execution plan by checking in V$ SESSION SQL_ID and SQL_CHILD_NUMBER column. This can be used to identify the plan in V$ SQL_PLAN (columns SQL_ID and CHILD_NUMBER) and in 10g, you can use the convenient DBMS_XPLAN. Function DISPLAY_CURSOR for the information of the real plan using these two parameters.

Kind regards
Randolf

Oracle related blog stuff:
http://Oracle-Randolf.blogspot.com/

SQLTools ++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676 /.
http://sourceforge.NET/projects/SQLT-pp/

parameters in the SQL statement.
Hello

I am creating a report of PL/SQL. The report, for example, has 3 columns say X, Y, Z. When I run the report, I have 2 Optional parameters P1 and P2.
My question is,

If I enter a value in the parameter P1, then where condition of the report should be something like
WHERE X = P1.

If I enter a value in the parameter P2, then where condition of the report should be something like
WHERE Y = P2.

If I enter a value in the parameters P1 and P2, then where condition of the report should be something like
WHERE X = P1 AND Y = P2.

Can someone give an idea how to make this possiblie.

Thank you
Kumar
I'm a fan of NVL for this...
```
WHERE X = NVL(P1, X)
  AND Y = NVL(P2, Y)
```
Therefore if P1 or P2 is null, you get X = X or Y = Y, actually drop your sql criteria. You can also link, in which case you have only a single sql statement analyze and you needn't pl/sql at all.

Excuting multiple sql statements
Hi to everyone.

I am quite new to Oracle, even though I have a great experience with SQL and MySQL commands. I am facing a problem that I guess it's really Basic.

I got a dump of an Oracle database in a format .sql. I mean that the schema and data are built thanks to a large number of sql statements. In particular the schema is done by many 'create a table... '. «While the data are built through «insert into...» ». My need is to import these databases into a new Oracle Oracle 10 g XE database.

I installed it on a Debian system, and I can properly run a single SQL command both through the web interface http://localhost: 8080/apex and logging as user oracle through the name of sqlplus user/passwd command.

My problem is that the data is spread over approximately 12000 SQL «INSERT INTO...» "so all one by one run might be a bit boring :-)

< u > so I ask if there is a way to tell Oracle to execute multiple SQL statements he read a file (like MySQL for example). < /u >

I'm planning to write a script to do if there is no better way. I know there's no way to dump databases Oracle, but I can change the .sql format since it's the only one I had.
in SQL * Plus you can run a SQL file with the start command or the abridged version: @
```
SQL> start filename.sql

or 

SQL> @filename.sql
```

Order of execution of SQL statements

Hello
I have two SQL statements where the first statement executes on a table with more than 40 million lines, the second statement is running on a table more 6 million lines. When they are running their own each take about 0.15 seconds to run, but when combined they take 20 minutes to run, (the second SQL statement is inserted in the WHERE clause of the statement of first). It would seem that after combining these statements, the first statement goes through all 40 million lines before it performs the SELECT in the WHERE clause. I think that what is necessary is to ensure the SELECT in the WHERE clause is executed first... or something like that! Anyone has any ideas on how to combine these statements but not suffer from the performance impact?
The first statement is:
Select csi.instance_id,
OEL.ordered_item
of apps.csi_item_instances csi,.
Apps.oe_order_lines_all oel
where csi.instance_id in
(1718000,3698000,48740202)
and csi.last_oe_order_line_id = oel.line_id;
The second statement is:
Select / * + INDEX (IEA (attribute_id)) * /.
IEA.instance_id
apps.csi_iea_values do
where iea.attribute_id = 10004
and iea.attribute_value is not null;
The joint return is:
Select csi.instance_id,
OEL.ordered_item
of apps.csi_item_instances csi,.
Apps.oe_order_lines_all oel
where csi.instance_id in
(select / * + INDEX (IEA (attribute_id)) * /)
IEA.instance_id
apps.csi_iea_values do
where iea.attribute_id = 10004
and iea.attribute_value is not null)
and csi.last_oe_order_line_id = oel.line_id;
Thanks for any help,
Mike

Your subquery returns probably just two values that you did originally as constants - but the optimizer thinks that you're going to get 564 K lines. This is why the indicator for the simple query has a beneficial effect, it forces the Oracle to use an index when it would otherwise make a search.

When the subquery is incorporated, however, the optimizer uses its cardinality expected to decide whether to use a nested loop join or the hash join to CSI_ITEM_INSTANCES, since the large enough estimate, he uses the hash with a join analysis complete. That's why I pointed out that the fact to tell the optimizer to how many lines outside the subquery should make a difference.

Have you tried the "common table expression" approach, rather than approach no_merge, but it would not help because it does not change the optimizer for cardinality estimate. If you want to repeat the method CTE adding boards / * + materialize cardinality (2) * / to the query in the WITH clause, you should get the desired result.

Concerning

Jonathan Lewis

Interrupted SQL statement and start several times with several SQL_EXEC_ID

Hi all
We meet a strange phenomenon, maybe someone can help.
We see that sometimes, when our client runs a single statement, implemented Oracle to process the statement with a special SQL_EXEC_ID, but after a while stops and starts processing the statement along with different SQL_EXEC_ID. Then, after a while, it happens again - stop Oracle processes the statement and start from the beginning with the new SQL_EXEC_ID. This happens again and again until we kill all of the other sessions on the database (then it ends).
What we see exactly: Client executes the statement (sql_id = "2tp7pz6yv87qp"). Monitor us v $ SQL_MONITOR and get this:
SELECT Sql_id, sql_exec_id, to_char (SQL_EXEC_START, "HH24:MI:SS MON-DD-YYYY) SQL_EXEC_START, status OF V$ SQL_MONITOR where sql_id = '2tp7pz6yv87qp' ORDER BY SQL_EXEC_START DESC;
2tp7pz6yv87qp 16777216 28 may 2015 07:19:14 the EXECUTION
After a while check us again and see this:
2tp7pz6yv87qp 16777217 28 may 2015 07:36:17 the EXECUTION
2tp7pz6yv87qp 16777216 28 may 2015 07:19:14 FACT
After a while, we see this:
2tp7pz6yv87qp 16777219 28 may 2015 08:09:58 the EXECUTION
2tp7pz6yv87qp 16777218 28 may 2015 07:53:37 FACT
2tp7pz6yv87qp 16777217 28 may 2015 07:36:17 FACT
2tp7pz6yv87qp 16777216 28 may 2015 07:19:14 FACT
and so on — will happen again and again until we kill all of the other sessions in the database.
When comparing the follow-up of the different SQL_EXEC_IDs SQL reports, we see that each of them did exactly the same job: used the same execution plan, beginning treatment she even read/wrote the same amount of e/s and each of them stopped at the same point during execution. You can see that for each SQL_EXEC_ID execution 'stops' in the middle and never reach the end of the plan. She always stops in the JOIN by HASH and never continue to the next steps in the implementation plan.
When you look more deeply, we see in V$ ACTIVE_SESSION_HISTORY always last thing that happens for every SQL_EXEC_ID is HASH JOIN RIGHT OUTER (SQL_PLAN_OPERATION = HASH and SQL_PLAN_OPTIONS = RIGHT OUTER JOIN). Then comes the new SQL_EXEC_ID and it starts to do the same thing as the previous SQL_EXEC_ID did when it was launched.
Kill all other sessions, run finally ends. We see that the final (successful) SQL_EXEC_ID work and completes his plan to run to completion.
When executing the same single statement (when it comes to the single session in the database), it ends with a single SQL_EXEC_ID. Its SQL monitoring report looks like the final execution when the phenomenon occurs after killing all other sessions.
-We checked that the customer executing the query only once. AWR also only shows simple execution of the query.
-We have reproduced in many different clients (plus SQL, JDBC thin client OIC and DBMS_SCHEDULER job).
-It has no PARALLEL in the query or table.
-In this case for different statements (different INSERT-SELECT and MERGE instructions).
-Version: Oracle Database 11 g Enterprise Edition Release 11.2.0.3.0 - 64 bit Production
Does anyone have an idea?

Finally found the root cause of the problem.

This phenomenon occurs when the cursor of the active query being invalidated. This can occur in several scenarios, in our case, what happens when we work on a single partition (read or write) and perform DDL operations on different partitions of the same or the tables.

Steps to reproduce:

1 launch long command DML that affect the single partition

2. in the course of executing this SQL, do one of the following values in a session different all 1 minute:

2.1 do the indexes to a different partition unusable: ALTER TABLE X EDIT PARTITION Y UNUSABLE LOCAL INDEX

2.2 rebuild the unusable index of different partition: ALTER TABLE X EDIT PARTITION Y REBUILD UNUSABLE LOCAL INDEX

2.3 a partition different truncate

Support of Oracle we were told that this problem is known and there are several requests for bugs and improvements thereon, for example this one:

Bug 12905327 : TRUNCATE to an INVALID PARTITION TABLE UNNECESSARILY IMMEDIATELY all THE SLIDERS

In our case (ETL process), we used to perform all these operations DDL and DML operations long (we work on different partitions in parallel). In order to solve, we have separated these operations to the different phases in our process and don't be DDL and DML operations at the same time more. This solved the problem for us.

Several SQL statements with zero executions in the region of SQL

Hello
one of my databases has a large number of statements in the SQL box with zero executions. Some of them analyzed several times without a single run. Why the database stores these statements and how to avoid or reduce them?
My problem is that the only time or zero time sql statements take the largest part of the area of sql:
-sql statement and only once and without executing sql statements
Select
Count (1) num_sql_total,.
sum (decode (executions, 1, 1, 0)) num_one_use_sql,.
sum (decode (executions, 0, 1, 0)) num_no_use_sql,.
Sum (RUNTIME_MEM) / 1024/1024 mb_used,.
sum (decode (executions, sharable_mem, 1, 0)) / 1024/1024 mb_for_one_use_sql,.
sum (decode (executions, 0, sharable_mem, 0)) / 1024/1024 mb_for_no_use_sql
Of
GV$ sqlarea
where
RUNTIME_MEM > 0;
NUM_SQL_TOTAL NUM_ONE_USE_SQL NUM_NO_USE_SQL MB_USED MB_FOR_ONE_USE_SQL MB_FOR_NO_USE_SQL
23318
8739
8027
1420,95619106293
381,41183757782
530,999855041504
Concerning
Thomas

This is not unusual. Another app could analyze for example hard the most often used SQLs in upstairs app - making benefit of further processing (in theory) of sweet analysis when you use these SQLs.

In fact, I remember reading something to this effect as a performance for some factor or another Oracle document or note?

So unless you have serious questions of shared pool, why bother with these sliders? What would be the problem?

Try to run a SQL statement through the window of OEM 12 c run SQL. Statement fails

All,
I have a 11g database. When it is initially installed, I installed it in $ORACLE_BASE = / orabin/app/oracle/product and $ORACLE_HOME = $ORACLE_BASE/11gDB_R2. This is the version 11.2.0.1 to give birth to 11.2.0.3.
Recently, I installed 11.2.0.4 in $ORACLE_BASE/11.2.0.4. Then, I upgraded my database at 11.2.0.4. Everything works fine.
All my scripts on the linux host logon changed to point my environment at $ORACLE_BASE/11.2.0.4 House and my $PATH when I connect to the linux host is: /orabin/app/oracle/product/11.2.0.4/bin:/orabin/app/oracle/product/11.2.0.4/OPatch:/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/oracle/bin
On my OEM Console, the database appears as 11.2.0.4 and me can manage very well.
However, when I try to use the window of the OEM Console to execute SQL to execute any type of SQL statement, it fails.
The failure error is:
Could not launch/orabin/app/oracle/product/11gDB_R2/bin/sqlplus-s/nolog: no such file or directory
It would be a mistake since the 11gDB_R2 directory tree (the 11.2.0.3 software) has been removed from the host, now that the database is set to level and working as 11.2.0.4.
I wonder if somewhere in the OEM software, there is always a pointer to the old ORACLE_HOME? I can't find anything in the .bashrc or other shell scripts that are executed when a Shell session on the host computer which were still the reference to the old directory of 11gDB_R2 so I'm a bit puzzled.
I have 8 guests, and all have been improved in the same way at 11.2.0.4. For some databases, the OEM window run SQL is executing the SQL code.
Someone has some ideas on this?

Go to the Configuration of the analysis of the database (when you set the password) and update of the Oracle home. Also do this for all targets listener on this host as well.

sql statements run correctly
Hello

It is a question of certification.

Question: 3
Examine the structure of the table of PROGRAMS:
Name Null? Type
---------- ------------- ---------------
PROG_ID NOT NULL NUMBER (3)
PROG_COST NUMBER (8.2)
START_DATE DATE NULL NOT
END_DATE DATE
The two SQL statements would be run successfully? (Choose two.)
A. SELECT NVL (ADD_MONTHS(END_DATE,1), SYSDATE) OF programs;
B. SELECT TO_DATE (NVL (SYSDATE-END_DATE, SYSDATE)) OF programs;
C. SELECT NVL (MONTHS_BETWEEN (start_date, end_date), 'Ongoing') OF programs;
D. SELECT NVL (TO_CHAR (MONTHS_BETWEEN (start_date, end_date)), 'Ongoing') OF
programs;

Answers: A, D

My question is:
If A and D are correct woud B and C run successfully also right?

Please specify.
What? You are able to do this in your test db?
You get an error for B and C for this reason - the expressions in the two queries will assess a number. B trying to do a TO_DATE on a NUMBER, and C tries to substitute a VARCHAR2 string where a NUMBER is expected.

Capture the SQL statement before it runs
Hello world

I have a question about the capture of query sql statement in Oracle before he run? Is it possible to do and can give you the answer to this problem? Enter here means I can catch the declaration of all applications (like SQL, I * sqlplus or another application making the request to the database). I want to do this because my teacher asks me to analyze the request and if it violates any policy = > stop before Oracle run it.

I tried this solution
[Select trigger for Oracle | http://technology.amis.nl/2005/09/26/select-trigger-in-oracle-database-introducing-fine-grained-auditing/].
but I think he looks not the answer. Because for the audit of the refined, the event handler is called when the first row is obtained. This is the average Oracle a analyze this quere and run to get the first row.

Please help me with this problem

Edited by: pirent420 at 04:05 06/05/2012
Hello
That's what you ask...

www.Oracle.com/technetwork/Products/Database-Firewall/index.html

Some other related things are:

the database Vault control many things related to this in terms of what time of the day and access where data etc.

Resource Manager can block statements if they want to use too many resources.

The standard model of privilege/role/grant prevents access you something, that you are not allowed to see.

Views can hide columns if necessary.

DTV and RLS can hide lines

It depends exactly on the requirement.

See you soon,.
Harry

Sql statement variable gives several values
Hello

I have a variable that has sql statement and it gives several values and I want to use this variable in one of the filter of interface condition to filter the data in the source table (which has millions of records).

some could let me know the best method to achieve this scenario.

Appreciate your help.
You are right. Yesterday, I don't think in this case where the data could be from a different server. But I completely forgot today.
Ok. Here you can find how to use sys_connect_by_path

http://asktom.Oracle.com/pls/asktom/f?p=100:11:0:P11_QUESTION_ID:907278700346567560

Be careful with the size because I think that there is a limit to what can contain the variable ODI.

After you have assessed the variable is how it could be used in the filter

ITEM_TYPE_ID IN (#var_csv_id_list)

Re-run a single SQL statement on several report page

Similar Questions

Maybe you are looking for