How Authorization Schemes Work → An authorization scheme extends the security of your application's authentication scheme. You can specify an authorization scheme for an entire application, a page, or specific component such as a region, item, or button. For example, you could use an authorization scheme to selectively determine which tabs, regions, or navigation bars a user sees. An authorization scheme either succeeds or fails.
SQL Work Areas → dedicated to work areas allocated by memory-intensive operators such as the following: Sort-based … example, a sort operator uses a work area (sometimes called the sort area) to perform the in-memory sort … of a set of rows. Similarly, a hash-join operator uses a work area (also called the hash area) to … does not fit into a work
How Inverse Groups Work → This section explains how inverse groups are implemented, and how they work. It contains these
How Does Oracle SOAP Work? → Consider this example: a GetLastTradePrice SOAP request is sent to a StockQuote service. The request takes a string parameter, the company stock symbol, and returns a float in the SOAP response. The XML document represents the SOAP message. The SOAP envelope element is the top element of the XML document. XML namespaces are used to clarify SOAP identifiers from application-specific identifiers. The
Privileges Needed to Work with Triggers → To create a trigger in your schema, you must have the CREATE TRIGGER system privilege, and either: Own the table specified in the triggering statement, or Have the ALTER privilege for the table in the triggering statement, or Have the ALTER ANY TABLE system privilege To create a trigger in another user's schema, or to reference a table in another schema from a trigger in your schema, you must have
How Page Processing and Page Rendering Work → The HTML DB engine dynamically renders and process pages based on data stored in database tables. To view a rendered version of your application, you run or submit it to the HTML DB engine. When you run an application, the HTML DB engine relies on two processes: Show Page is the page rendering process. It assembles all the page attributes (including regions, items, and buttons) into a viewable HTML
Apache HTTP Server → [APACHE DOCUMENTATION] Apache HTTP Server How Directory, Location and Files sections work The
Doing Independent Units of Work with Autonomous Transactions → An autonomous transaction is an independent transaction started by another transaction, the main transaction. Autonomous transactions do SQL operations and commit or roll back, without committing or rolling back the main transaction. For example, if you write auditing data to a log table, you want to commit the audit data even if the operation you are auditing later fails; if something goes wrong
How Materialized Views Work with Object Types and Collections → Oracle object types are user-defined datatypes that make it possible to model complex real-world entities such as customers and orders as single entities, called objects, in the database. You create object types using the CREATE TYPE... AS OBJECT statement. You can replicate object types and objects between master sites and materialized view sites in a replication environment. An Oracle object that
1.6.9 Why Does SPOOL Not Work in Pro*C/C++? → SPOOL is a special command used in SQL*Plus. It is not an embedded SQL command. See "Key Concepts of Embedded SQL Programming ".
How Data Labels and User Labels Work Together → has no access to HIGHLY_SENSITIVE data. Figure 2-4 shows how data labels and user labels work together
ORA-16116: no work available → event for diagnostic purposes. ORA-16116: no work available
ORA-02181: invalid option to ROLLBACK WORK → STORAGE, ONLINE, OFFLINE, FORCE, RETENTION. ORA-02181: invalid option to ROLLBACK WORK
PLS-01701: Illegal syntax in ROLLBACK WORK statement → Cause: DROP is non-ANSI Action: Sect. 6.2 PLS-01701: Illegal syntax in ROLLBACK WORK statement
PLS-01702: Illegal syntax in COMMIT WORK statement → Cause: Illegal syntax in ROLLBACK WORK statement. Action: none PLS-01702: Illegal syntax in COMMIT WORK statement
ORA-22335: The client cannot work with an altered type → statement to upgrade the data in the dependent tables then resubmit the statement. ORA-22335: The client cannot work with an altered type
ORA-02185: a token other than WORK follows COMMIT → without the quota. ORA-02185: a token other than WORK follows COMMIT
ORA-00155: cannot perform work outside of global transaction → suspended. Action: Contact the transaction monitor customer support. ORA-00155: cannot perform work outside of global transaction
PCC-00105: Keyword WORK required here by ANSI → … However, for ANSI/ISO compliance, do not use the FOR clause. PCC-00105: Keyword WORK required here by ANSI
PCB-00312: Keyword WORK required here by ANSI → Cause: An Oracle extension to the ANSI/ISO SQL standard was used. Specifically, the keyword WORK … COMMIT WORK RELEASE END-EXEC. This informational message is issued by the FIPS Flagger when FIPS=YES … . Action: No action required. However, for ANSI/ISO compliance, do not use the keyword WORK.