精华内容
下载资源
问答
  • Mutexes in Oracle Database

    万次阅读 2016-03-16 23:45:25
    Mutexes in Oracle Database This thread can be used as the discussion thread for the recent advisor webcast: Mutexes in Oracle Database held on Apr 30 2013. The summary of the Q&A section is

    Mutexes in Oracle Database

    This thread can be used as the discussion thread for the recent advisor webcast: Mutexes in Oracle Database held on Apr 30 2013.


    The summary of the Q&A section is listed below.

    Is mutexes going to replace latches in future?
    On 10g we had replaced latches with mutexes for certain operations . In 11g, we have replaced lots of latches on library cache into mutex mechanisms. Currently we had only looked into library cache latches only.

    Can you explain more accurately the notion of "child version count" please?
    SQL statement having more than 1 plan hash value is called version count.
    When the SQL has many child cursors under the same parent cursor, the no.of child cursors is the version count. A Version is referred as a child cursor.

    Can a low value of Session_Cache_Cursor cause waits on Library Cache : Mutex X ?
    Session cached Cursor parameter is for Soft parsing.it will not cause Library Cache mutex X

    In which situation we got more version count?
    Version counts are the number of child cursors created because we could not share the already existing child cursor. The reasons are many and can be checked from v$sql_shared_cursor.

    How to fix massive waits on mutex pin s ?
    Refer to the webcast material in pdf.

    Is there any adverse effect of killing the blocking session when it is in Shared Pool?
    no adverse effect..but it would be better to diagnose and fix the issue to prevent it happening in future

    Is the dbms_shared_pool.markhot helps on mutex pin on S?
    yes, it will help for 'cursor: pin S'

    What is the wait mechanism for mutex? I mean for latch if not acquired it was spinning. On mutex I suppose it is not
    Acquiring mutex has mechanism like yield, sleep, exponential backoffs. 
    Refer: Bug 10411618 - Enhancement to add different "Mutex" wait schemes (Doc ID 10411618.8) – 11g

    cursor_sharing = force, most of the times will result into bind peeking. Is it really recommended ? We often go for exact
    In 11g Release you have ACS feature.ie: Adaptive Cursor Sharing to overcome the Bind Peeking issues. when you go for exact , you shared pool will be slightly overhead and you might needed increasing it size

    What can be done to  avoid high version counts 
    Set cursor_sharing to FORCE ..this will help in reducing the version count issues

    Could you elaborate more why massive login/logoff creates library cache : mutex X 
    logon and logoffs acquires mutexes on dictionary objects brought into lib cache and maintain account status..etc  and frequent logon and logoffs impacts normal user logon operations

    Why Mutex X for login/logoff (I expect S) -and this way, are you saying there is a cap in number of login/logoff per sec/min which Oracle can handle ? Any workaround for massive login/logoff in a dedicated environment
    logon and logoffs acquires mutexes on dictionary objects brought into lib cache and maintain account status..etc  and frequent logon and logoffs impacts normal user logon operations 
    this will cause the library cache : mutex X as the contention happens on the same object if the same session is logged in storm

    how do we make parent cursor obsolete?
    _CURSOR_OBSOLETE_THRESHOLD to 100 (this is the number of child cursor after which we obsolete it) 

    what kind of considerations we got to have present, about mutex, when we configure somethign with resource manager
    There is no additional configuration settings required when configuring Resource Manager

    How to fix huge version counts?
    Check the setting of cursor_sharing ..set it to FORCE in many cases it addresses the version count issue

    In the demo, when the cursor was spread over 2 mutexes, we saw a removal of the cursor: pin S wait event from the top 5 wait events.  Was there also a reduction in the amount of CPU used?
    To some extent the CPU Yield will also get reduced

    I've seen frequent instances of library cache mutex x waits especially with 11g. Is there any parameter to supress this apart from increasing the shared pool?
    It has to diagnosed and based on the same solution need to be derived ..its slightly a lengthier process which needs lots of analysis to be done

    Do Version counts happen mostly due to not binding the variables in a sql? Or are there any other reasons?
    Yes, it occurs for bind mismatch as well as there are many other causes. You can query v$sql_shared_cursor to find various mismatches

    Can you give us the sql statement that return all child version of a sql statement ?
    You can query version_count in v$SQLAREA.
    Refer Note.438755.1    High SQL Version Counts - Script to determine reason(s)  - formatted

    How about ADAPTIVE CURSOR feature introduced in 11g will it impact this mutex?
    ACS feature is reduce the effect of Bind Peeking issue and will not impact the mutex.

    Please check the references section:-

    Bug 10187168 - Enhancement to obsolete parent cursors if VERSION_COUNT exceeds a threshold (Doc ID 10187168.8) – 11g
    Bug 10411618 - Enhancement to add different "Mutex" wait schemes (Doc ID 10411618.8) – 11g
    FAQ: 'cursor: mutex ..' / 'cursor: pin ..' / 'library cache: mutex ..' Type Wait Events (Doc ID 1356828.1)
    Troubleshooting: Waits for Mutex Type Events (Doc ID 1377998.1)
    How to Collect Diagnostics for Database Hanging Issues [ID 452358.1]
    How to Generate an AWR Report and Create Baselines [ID 748642.1]
    Init.ora Parameter "_KGL_DEBUG" [Hidden] Reference Note [ID 1388197.1]

    The recording of the webcast is available at:
    https://oracleaw.webex.com/ec0605ld/eventcenter/recording/recordAction.do?theAction=poprecord&AT=pb&AT=pb&AT=pb&AT=pb&AT=pb&AT=pb&isurlact=true&isurlact=true&isurlact=true&isurlact=true&renewticket=0&renewticket=0&renewticket=0&renewticket=0&recordID=74938412&apiname=lsr.php&apiname=lsr.php&apiname=lsr.php&apiname=lsr.php&apiname=lsr.php&rKey=07f9b2110f982b06&rKey=07f9b2110f982b06&rKey=07f9b2110f982b06&rKey=07f9b2110f982b06&rKey=07f9b2110f982b06&rKey=07f9b2110f982b06&needFilter=false&needFilter=false&needFilter=false&needFilter=false&needFilter=false&format=short&format=short&&SP=EC&SP=EC&SP=EC&SP=EC&SP=EC&SP=EC&rID=74938412&rID=74938412&rID=74938412&rID=74938412&rID=74938412&rID=74938412&siteurl=oracleaw&actappname=ec0605ld&actappname=ec0605ld&actname=%2Feventcenter%2Fframe%2Fg.do&actname=%2Feventcenter%2Fframe%2Fg.do&rnd=0326359849&rnd=0326359849&rnd=0326359849&rnd=0326359849&rnd=0326359849&entappname=url0107ld&entappname=url0107ld&entappname=url0107ld&entappname=url0107ld&entactname=%2FnbrRecordingURL.do&entactname=%2FnbrRecordingURL.do&entactname=%2FnbrRecordingURL.do&entactname=%2FnbrRecordingURL.do

    Refer to the following for the archived webcasts:
    https://support.oracle.com/epmos/faces/ui/km/DocTextDisplay.jspx?type=DOC&id=1456176.1

    Please let me know for any questions.

    Regards
    Bala
    展开全文
  • Triggers in Oracle Forms

    千次阅读 2012-11-02 14:53:49
    Triggers in Oracle FormsTriggers are blocks of PL/SQL code that are written to perform tasks when a specific event occurs within an application. In effect, an Oracle Forms trigger is an event-handler

    Triggers in Oracle Forms

    Triggers are blocks of PL/SQL code that are written to perform tasks when a specific event occurs within an application. In effect, an Oracle Forms trigger is an event-handler written in PL/SQL to augment (or occasionally replace) the default processing behavior. Every trigger has a name, and contains one or more PL/SQL statements. A trigger encapsulates PL/SQL code so that it can be associated with an event and executed and maintained as a distinct object.

    Block Processing Triggers:

    Block processing triggers fire in response to events related to record management in a block.

    • When-Create-Record Perform an action whenever Oracle Forms attempts to create a new record in a block.
    • When-Clear-Block Perform an action whenever Oracle Forms flushes the current block; that is, removes all records from the block.
    • When-Database-Record Perform an action whenever Oracle Forms changes a record’s status to Insert or Update, thus indicating that the record should be processed by the next COMMIT_FORM operation.

    Interface Event Triggers:

    Interface event triggers fire in response to events that occur in the form interface. Some of these triggers, such as When-Button-Pressed, fire only in response to operator input or manipulation. Others, like When-Window-Activated, can fire in response to both operator input and programmatic control.

    • When-Button-Pressed Initiate an action when an operator selects a button, either with the mouse or through keyboard selection.
    • When-Checkbox-Changed Initiate an action when the operator toggles the state of a check box, either with the mouse or through keyboard selection.
    • When-Image-Activated Initiate an action whenever the operator double-clicks an image item.
    • When-Image-Pressed Initiate an action whenever an operator clicks on an image item.
    • When-Radio-Changed Initiate an action when an operator changes the current radio button selected in a radio group item.
    • When-Window-Activated Initiate an action whenever an operator or the application activates a window.
    • When-Window-Closed Initiate an action whenever an operator closes a window with the window manager’s Close command.
    • When-Window-Deactivated Initiate an action whenever a window is deactivated as a result of another window becoming the active window.

    Master/Detail Triggers:

    Oracle Forms generates master/detail triggers automatically when a master/detail relation is defined between blocks. The default master/detail triggers enforce coordination between records in a detail block and the master record in a master block. Unless developing custom block-coordination schemes, you do not need to define these triggers.

    • On-Check-Delete-Master Fires when Oracle Forms attempts to delete a record in a block that is a master block in a master/detail relation.
    • On-Clear-Details Fires when Oracle Forms needs to clear records in a block that is a detail block in a master/detail relation because those records no longer correspond to the current record in the master block.
    • On-Populate-Details Fires when Oracle Forms needs to fetch records into a block that is the detail block in a master/detail relation so that detail records are synchronized with the current record in the master block.

    Message-Handling Triggers:

    Oracle Forms automatically issues appropriate error and informational messages in response to runtime events. Message handling triggers fire in response to these default messaging events.

    • On-Error Replace a default error message with a custom error message, or to trap and recover from an error.
    • On-Message To trap and respond to a message; for example, to replace a default message issued by Oracle Forms with a custom message.

    Validation Triggers:

    Validation triggers fire when Oracle Forms validates data in an item or record. Oracle Forms performs validation checks during navigation that occurs in response to operator input, programmatic control, or default processing, such as a Commit operation.

    • When-Validate-Item
    • When-Validate-Record

    Navigational Triggers:

    Navigational triggers fire in response to navigational events. Navigational triggers can be further sub-divided into two categories: Pre- and Post- triggers, and When-New-Instance triggers. Pre- and Post- Triggers fire as Oracle Forms navigates internally through different levels of the object hierarchy. When-New-Instance-Triggers fire at the end of a navigational sequence that places the input focus on a different item.

    • Pre-Form Perform an action just before Oracle Forms navigates to the form from “outside” the form, such as at form startup.
    • Pre-Block Perform an action before Oracle Forms navigates to the block level from the form level.
    • Pre-Record Perform an action before Oracle Forms navigates to the record level from the block level.
    • Pre-Text-Item Perform an action before Oracle Forms navigates to a text item from the record level.
    • Post-Text-Item Manipulate an item when Oracle Forms leaves a text item and navigates to the record level.
    • Post-Record Manipulate a record when Oracle Forms leaves a record and navigates to the block level.
    • Post-Block Manipulate the current record when Oracle Forms leaves a block and navigates to the form level.
    • Post-Form Perform an action before Oracle Forms navigates to “outside” the form, such as when exiting the form.
    • When-New-Form-Instance Perform an action at form start-up. (Occurs after the Pre-Form trigger fires).
    • When-New-Block-Instance Perform an action immediately after the input focus moves to an item in a block other than the block that previously had input focus.
    • When-New-Record-Instance Perform an action immediately after the input focus moves to an item in a different record.
    • When-New-Item-Instance Perform an action immediately after the input focus moves to a different item. 

    Transactional Triggers:

    Transactional triggers fire in response to a wide variety of events that occur as a form interacts with the data source.

    • On-Delete
    • On-Insert
    • On-Update
    • On-Logon
    • On-Logout
    • Post-Database-Commit
    • Post-Delete
    • Post-Insert
    • Post-Update
    • Pre-Commit
    • Pre-Delete
    • Pre-Insert
    • Pre-Update

    Query-Time Triggers:

    Query-time triggers fire just before and just after the operator or the application executes a query in a block.

    • Pre-Query Validate the current query criteria or provide additional query criteria programmatically, just before sending the SELECT statement to the database.
    • Post-Query Perform an action after fetching a record, such as looking up values in other tables based on a value in the current record. Fires once for each record fetched into the block.


    source:http://imdjkoch.wordpress.com/2010/09/15/triggers-in-oracle-forms/

    展开全文
  • AutoInvoice in Oracle Apps R12

    千次阅读 2012-06-26 22:55:30
    AutoInvoice in Oracle Apps R12 AutoInvoice is a powerful, flexible tool you can use to import and validate transaction data from other financial systems and create invoices, debit memos, credit m

    AutoInvoice in Oracle Apps R12

    AutoInvoice is a powerful, flexible tool you can use to import and validate transaction data from other financial systems and create invoices, debit memos, credit memos, and on–account credits in Oracle Receivables. You use a custom feeder program to transfers transaction data from an external system into the AutoInvoice interface tables. AutoInvoice then selects data from the interface tables and creates transaction in Receivables. Receivables rejects transactions with invalid information to ensure the integrity of your data. You can run AutoInvoice together with Customer Interface or separately.
    Oracle Receivables can create invoices from the following Oracle applications:  Oracle Order Management, Oracle Projects,  Oracle Service, Oracle Property Manager.
    Oracle Receivables can create invoices from the following non-Oracle applications:  Legacy system (for transaction history),  Non-Oracle billing applications, Non-Oracle order entry applications.
    Oracle Receivables uses three interface tables for AutoInvoice:
    1. RA_INTERFACE_LINES
    2. RA_INTERFACE_DISTRIBUTIONS
    3. RA_INTERFACE_SALESCREDITS
    AutoInvoice transfers transaction data from the above three interface tables into the following Receivables tables:
    • RA_BATCHES_ALL
    • RA_CUSTOMER_TRX _ALL
    • RA_CUSTOMER_TRX_LINES _ALL
    • RA_CUST_TRX_LINE_GL_DIST_ALL
    • RA_CUST_TRX_LINE_SALESREPS_ALL
    • AR_PAYMENT_SCHEDULES_ALL
    • AR_RECEIVABLE_APPLICATIONS_ALL
    • AR_ADJUSTMENTS_ALL
    RA_INTERFACE_LINES:
    • This table contains information relating to all transactions to be processed by AutoInvoice.
    • Transactions include invoices, debit memos, credit memos, and on-account credits.
    • Each record contains line, tax, freight, or finance charges information.
    • The Line_Type field identifies the type of information contained in the record.
    • A record can be a parent record: Line, Header Freight, or Charges; or a child record: Tax or linelevel Freight.
    • A child record is linked to the parent record using the Link-To Transaction flexfield.
    RA_INTERFACE_DISTRIBUTIONS:
    • This table contains accounting distributions to be used by the transactions defined in RA_INTERFACE_LINES.
    • Accounts defined in this table override any accounts created using AutoAccounting.
    • You can choose to pass some or all account information to AutoInvoice. Any accounts that are not passed will be derived using AutoAccounting.
    • Records in this table are linked to records in the RA_INTERFACE_LINES table using the Transaction flexfield.
    • Not required if AutoAccounting determines GL distributions.
    RA_INTERFACE_SALESCREDITS:
    • This table contains all sales credit information for the transactions in the RA_INTERFACE_LINES table.
    • The two tables are linked using the Transaction flexfield.
    • Not required if not tracking sales credit.
    What occurs during auto-invoice:
    1. Populates the RA_Interface_Lines, RA_Interface_distribution and RA_Interface_salescredit tables.
    2. Lines are grouped and ordered by the grouping rule and line ordering line. Grouping rules are mandatory and determine how transaction lines are grouped into transactions. Optionally, you can use line-ordering rules to determine the order in which lines are displayed on a transaction.
    3. Tax, freight, commitments and credit memos are linked to transaction line by transaction line, transaction reference and transaction link-to descriptive flex fields. To uniquely identify imported transactions and link the tax, freight, commitments and credit memos, define the Transaction flexfields.
    4. GL date is determined.
    5. GL accounting code combinations are assigned using auto accounting rule.
    6. TAX is determined.
    7. All transactions are batched.
    8. Validated lines are used to create the transaction.
    When run, AutoInvoice produces the AutoInvoice Execution Report and the AutoInvoice Validation Report.
    Any entries which failed validation can be reviewed in Oracle Receivables’ AutoInvoice Interface Exceptions window. Depending on the error, changes may need to be made in Receivables, the feeder program or the imported records in the interface tables.
    Transaction flexfields:
    • Transaction flexfields are descriptive flexfields that AutoInvoice uses to uniquely identify transaction lines.
    • Because they are unique for each transaction line, they can also be used to reference and link to other lines.
    • Receivables lets you determine how you want to build your transaction flexfield structure and what information you want to capture.
    • Define a flexfield for each import source. Specify which one to use during import.
    Types of transaction flexfields:
    • Invoice Header (optional): Specifies invoice header information
    • Line (required): Uniquely identifies invoice lines
    • Link-To (optional): Link tax and freight to invoice lines
    • Reference (optional): Links credit memos to transactions
    What is inside AutoInvoice?
    AutoInvoice is a tool consists of 3 main programs. Each program will have unique nature of work to do and they are called internally except Purge program whose execution is derived on the setup otherwise ready to execute stand alone.
    • Master (RAXMTR)
    • Import (RAXTRX)
    • Purge (RAXDEL)
    1] Auto Invoice Master program:
    Selects and marks records in the interface tables to  be processed based on the parameters the user entered and then calls the AutoInvoice Import program. Auto Invoice Master program has no report output.
    • Gathers statistics, it means it gathers the stats on interface tables and set the stats on certain indices on interface tables.
    • Marks interface records for processing by marking request_id.
    • Submits multiple workers for Parallel Processing by creating instances for request.
    2] Auto Invoice Import Program:
    Validates the selected record and creates transaction if it passes validation. Any record that fails validation is left in the interface table with an error code. Depending on the setup, related records may be rejected as well. This program has an output file called Auto Invoice Execution report, which you can view by clicking the View Report button in the Requests window.
    • Workhorse of Auto invoice
    • Validates data
    • Inserts records
    • Deletes interface data
    • Only when system option purge set to ‘Y’
    3] Auto Invoice Purge Program:
    Deletes records from the interface tables. If you set the Purge Interface Table system option to No in Define System Option window, Auto Invoice does not delete processed records from the interface tables after each run, and we must submit Auto Invoice Purge Program periodically to clean up the interface tables. This program only deletes transaction lines that have been successfully imported.
    AutoInvoice Exception Handling:
    Records that fail validation are called ‘Exceptions’
    • Exceptions stay in Interface Tables which is RA_INTERFACE_ERRORS_ALL.
    • Errors can be corrected in the Exception Handling window.
    • Once corrections are made, Auto invoice must be resubmitted.
    • Records that pass validation get transferred to Receivables tables.
    AutoInvoice Exception Handling Windows:
    • Interface Exception window displays exception messages associated with all invalid records.
    • Interface Lines window displays records that fail validation, provides an error message and can be used to correct the errors.
    • The Line Errors windows displays errors associated with a specific line, and can only be opened from Interface Lines window.
    • Interface Exceptions window displays Interface Id, Exception Type, Error Message and Invalid Value associated to the error.
    • Data cannot be edited in this window, but error can be viewed and corrected by clicking the Details button.
    • Error Message and Column name with invalid data are displayed in the Message column, and the invalid value that needs to be corrected is displayed in the Invalid Value column.
    zz: http://prasanthapps.blogspot.com/2011/04/autoinvoice-in-oracle-apps-r12.html
    展开全文
  • Bloom Filter in Oracle Database

    万次阅读 2011-03-07 21:18:00
    Bloom Filter in Oracle Database

    Bloom Filter用的范围很广,不仅在Search Engine中大量采用,在Data Deduplication中也频频遇到。那么它在数据库中的应用情况怎么样呢?放狗找一下,这个比较有意思:http://antognini.ch/papers/BloomFilters20080620.pdf

    今天在和同事讨论问题的时候突然想起来,这个玩意就是以前在Database Machine论文中见过的Bit vector啊:http://academic.research.microsoft.com/Publication/803587

    展开全文
  • Job Completion/Return Process in Oracle MES

    千次阅读 2013-01-31 11:20:06
    How to perform a WIP job Completion in Oracle MES ,Below is basic flow for completion.Define BOM,and Routing, Then Create a Job in Oracle Application(Supply type:Assembly Pull for this demo case)Respo
  • Enabling SSL or TLS in Oracle E-Business Suite Release 12 In This Document Section 1: IntroductionSection 2: Concepts and TerminologySection 3: Application Tier SetupSection 4: Database Tier Set
  • “DROP TABLE IF EXISTS” in Oracle and SQL Server In MySQL it is pretty easy to drop a table if it exists already. In Oracle and Microsoft’s SQL Server it is a little more complicated. ...
  • There are two main security models in Oracle E-Business Suite: “traditional” Oracle E-Business Suite responsibility-based security (usually referred to as “function security”) and Role-Based ...
  • 在搭建oracle 12c rac过程中,已成功安装了grid,在安装database软件时,因为中途出现意外,只能进行重装,将/u01/app/oraInventory目录下文件全部的删除后,database已成功安装在两个节点,但在创建asm磁盘运行...
  • OPMN in Oracle Applications R12

    千次阅读 2013-03-09 00:33:25
    OPMN consists of two main components (Oracle Process Manager) and (Oracle Notification Server).Oracle Process Manager is responsible for1) starting2) stopping3) restarting4) monitoring the services it
  • Material Status Enhancement in Oracle EBS R12.2

    千次阅读 2012-09-11 12:32:07
    Material Status Enhancement Introduction ...The material status feature was originally developed for Oracle Warehouse Management (WMS). Since R12, the material status feature is also available in Or
  • Start/Stop the Workflow Services in Oracle Apps

    千次阅读 2013-02-27 11:48:22
    Navigation:Navigate to Workflow Administrator> Oracle Application Manager > Workflow Manager > Service Components > Workflow Agent Listener Services Start and Stop the Oracle Workflow Services--------
  •   Placement of Voting disk and OCR Files in Oracle RAC 10g and 11gR1 [ID 293819.1]   Modified 27-OCT-2010 Type BULLETIN Status PUBLISHED   In this Document  ...
  • in Class P to Base UOM in Base UOM in Class S 5.  ConvertBase UOM in Class S to  Secondary UOM inClass S (this gives Secondary UOM) From the Two cases, it is evident that a conversion from ...
  • .trc and .trm files in Oracle 11g

    千次阅读 2012-10-12 11:33:05
    The files located in the TRACE directory, with the “.trm” extensions, are called Trace Metadata files. The metadata in .trm files describe the trace records stored inside of .trc trace files. The ...
  • This blog covers installing ODI 11.1.1.7 as well as Weblogic 10.3.6. ...1. Oracle database 11gR2 installed. 2. sysdba privilege of Oracle database 11gR2. 3. Check ODI 11.1.1.6 for c
  • 问题描述: 现有的Query中似乎使用了一个自定义函数String_to_list,为了排查问题,需要查看这个函数的定义。 方法:   --新建的function,并未保存在All_ojbects表中,而是保存在user_objects表中 ...
  • Applies to: Oracle Net Services - Version 10.2.0.3 to 11.2.0.4 [Release 10.2 to 11.2] ...Information in this document applies to any platform. Goal To demonstrate how the COST parameter "SECURE_RE
  • 1.quit from sqlplus2 excute set oracle_sid="new_sid"3.run sqlplus to confirm it.
  • Oracle中的in 和 not in

    万次阅读 2019-04-16 14:56:17
    Oracle中的in和not in 在日常的数据统计中,尽量不要用not in 来查询数据,可以考虑使用exist或者left join 来代替。但是如果用到in 和 not in 时,必须要考虑null值的影响,不能简单理解为not inin的差集。举例 ...
  • oracle中代替in 和not in 高效方法

    万次阅读 2018-09-07 10:51:40
    oracle中效率排行:表连接>exist>not exist>in>not in; 因此如果简单提高效率可以用exist代替in进行操作,当然换成表连接可以更快地提高效率,具体是用left join代替not in 和...
  • Oracle DB In-Memory是预装在Oracle Database 12c(12.1.0.2之后的版本)中的,不需要安装其他软件或者是重新编译现有的的数据库软件。这是因为In-Memory选项是作为SGA的一个新组件无缝集成在Oracle Database...
  • Oraclein查询

    万次阅读 2018-07-28 08:32:17
    In查询 SELECT ID, ASSAY_ITEM_NAME FROM DIC_ASSAY_ITEM WHERE ID IN ( SELECT DISTINCT ASSAY_ITEM_ID FROM DIC_ASSAY_ITEM_METHOD ) 或者 Mapper Li...
  • 关于Oracle存储过程中拼接in语句以及自定义split函数
  • 首先,在oracle中效率排行:表连接>exist>not exist>in>not in,而且使用in查询会有查询条件数量不能超过1000的限制;因此如果简单提高效率可以用exist代替in进行操作,当然换成表连接...
  • Oracle IN MEMORY OPTION

    千次阅读 2014-11-04 00:23:23
    众所周知,ORACLE是行存储数据库。
  • oracle not in 查不出数据

    千次阅读 2015-08-21 16:20:38
    oracle中,sql语句如下: select * from xa_ajxx where ajxx_uuid not in (select ajxx_uuid from sl_zdajbgxq ) 却查不出应有的数据,查询结果为空。 原因是 sl_zdajbgxq中存在着ajxx_uuid为空的数据。...
  • Oracle官方In-Memory Blog的系列文章Getting started with Oracle Database In-Memory非常值得一读。Getting started with Oracle Database In-Memory包括以下文章: Part I - Installing & Enabling 介绍如何启用...
  • oracle for in loop

    千次阅读 2012-07-30 09:17:52
    function get_irc_pn(p_irc in pnrreg.irc%type, p_partid in pnrreg.partid%type) return varchar2 is o_irc_pn varchar2(200); -- p_pnrreg pnrreg%rowtype;
  • 1、in模式参数 输入模式的参数,用于接收参数,在子程序内部,不能进行修改。默认的参数模式:in。--定义打印的存储过程 CREATE OR REPLACE PROCEDURE println (str VARCHAR) AS BEGIN dbms_output.put_line(str);...

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 468,228
精华内容 187,291
关键字:

inoracle