DOCSLIB.ORG

Oracle Fusion Middleware Error Messages Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Oracle® WebLogic Server Error Messages Reference 12c Release 1 (12.1.1) E26117-01 December 2011 This document contains the Message Catalogs for Oracle WebLogic Server. Oracle WebLogic Server Error Messages Reference, 12c Release 1 (12.1.1) E26117-01 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services. Contents Preface ................................................................................................................................................................. v Audience....................................................................................................................................................... v Documentation Accessibility..................................................................................................................... v Conventions ................................................................................................................................................. v 1 BEA-000001 to BEA-2160002 iii iv Preface This manual provides information about the error messages you may encounter when installing and using Oracle Fusion Middleware components. It augments the message texts by providing additional cause and action information. For more information on error messages in Oracle Application Server, browse the documentation on the Oracle Technology Network (OTN) at http://www.oracle.com/technology/products/ias/index.html. Audience This manual is intended for anyone who uses Oracle Fusion Middleware and requires more information about an error message encountered in the product. Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc. Access to Oracle Support Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired. Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. v vi 1 1BEA-000001 to BEA-2160002 BEA-000001: Server must be started by Node Manager when consensus leasing is enabled. Cause: The server was not started by Node Manager. Action: Start the server using Node Manager. Level: 1 Type: INTERNAL_ERROR Impact: ConsensusLeasing BEA-000101: Cannot resolve ClusterAddress: {0} Cause: The cluster address {0} could not be resolved. ClusterAddress should be a DNS name that maps to multiple IP addresses. Action: Set the correct ClusterAddress property for the cluster. Level: 1 Type: NOTIFICATION Impact: Cluster BEA-000102: Joining cluster {0} on {1}:{2} Cause: The server has joined cluster {0}. Action: No action is required. Level: 1 Type: NOTIFICATION Impact: Cluster BEA-000103: Disconnecting from cluster {0} Cause: When a server is suspended, it is no longer a member of cluster {0}. Action: No action is required. Level: 1 Type: NOTIFICATION Impact: Cluster BEA-000104: Cluster members are running incompatible versions. Local version: {0}. Remote version ({1}): {2} Cause: This server is a different version than other servers in this cluster. Action: Ensure that all members of this cluster are running the same version. BEA-000001 to BEA-2160002 1-1 Level: 1 Type: ERROR Impact: Cluster BEA-000105: The server is leaving the cluster because it is an incompatible version. Cause: This server is running a different version of WebLogic Server. Action: Set a different multicast address for this cluster. Use an address in the range of 224.0.0.0 - 239.255.255.255. Avoid the reserved range 224.0.0.0 - 224.0.1.255. Level: 1 Type: NOTIFICATION Impact: Cluster BEA-000107: Failed to install {0} in place of those currently installed due to {1}. Cause: An error occurred while resolving non-local conflicting offers for a node in the JNDI tree. Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis. Level: 1 Type: ERROR Impact: Cluster BEA-000108: Attempt to retract offer {0}, which is neither installed nor pending. Cause: An attempt was made to retract an offer, which was neither previously installed nor is in the conflict resolution stage. Action: No action is required. Level: 1 Type: ERROR Impact: Cluster BEA-000109: An error occurred while sending multicast message: {0}. Cause: An error occurred while trying to send a message over multicast. Action: WebLogic Server will try to recover from this error. If the problem continues to persist, make sure that the network infrastructure and NIC are functioning properly. If you believe no environment problems exist, contact My Oracle Support and provide the stack trace for further analysis. Level: 1 Type: ERROR Impact: Cluster BEA-000110: Multicast socket receive error: {0}. Cause: An error occurred while trying to receive a message over the multicast. Action: Ensure that the NIC is functioning properly. If it appears that no environment problems exist, contact My Oracle Support and provide the stack trace for further analysis. 1-2 Oracle WebLogic Server Error Message Reference Level: 1 Type: ERROR Impact: Cluster BEA-000111: Adding {0} with ID {2} to cluster: {1} view. Cause: This is an informational message. Action: No action is required. Level: 1 Type: NOTIFICATION Impact: Cluster BEA-000112: Removing {0} from cluster view due to timeout. Cause: Removing {0} from cluster as it failed to send heartbeats over the multicast in the past 30 seconds. Action: If a server has been shut down or suspended, no action is required. If the remote server {0} appears to be hung, take thread dumps and send them to My Oracle Support. Level: 1 Type: NOTIFICATION Impact: Cluster BEA-000113: Removing {0} from cluster view due to PeerGone. Cause: The TCP/IP connection
Recommended publications
  • Create Trigger Schema Postgresql

    Create Trigger Schema Postgresql

    Create Trigger Schema Postgresql Diligent Gallagher sometimes gallants any harp reinforms single-mindedly. Lumpier and exarate Scott tongue limitedly and isolated his interactions approvingly and incorruptly. Tinniest and unabolished Berkie never opaquing quiveringly when Morton fall-back his duress. The legitimate unique identifier for house person. Now is are going to supervise an SQL file for adding data argue the table. You might declare a CURSOR, use case query. The privileges required by postgres function level, more triggers are processed by a predefined set of a particular order to store structured data. Use bleach if exists option and remove one arm more views from pan database database in not current. This is considered more consistent. Already loaded into different schemas live inside hasura became a create triggers and creates a couple of creating user? We can prevent all kinds of looping code in procedures with aggregate queries to a client like where tp where not a logical view! CREATE then REPLACE FUNCTION public. This way to be buffered to delete on geometry columns changes have created in postgresql create trigger against by trigger automatically drops an insert and occasional baby animal gifs! This is impossible except by anyone, check before insert or functions in which takes a create trigger postgresql create additional tables are enabled when date? For application that makes their first. We did with respect to spot when a system section provides an audit table belongs to remove trigger is used inside their twin daughters. Such as mentioned in postgresql create schema objects scripted would not. Many explanations from this document have been extracted from there.
  • Developing Applications with Oracle Jdeveloper 12C (12.2.1.2) E76675-01

    Developing Applications with Oracle Jdeveloper 12C (12.2.1.2) E76675-01

    Oracle® Fusion Middleware Developing Applications with Oracle JDeveloper 12c (12.2.1.2) E76675-01 Septermber 2016 Documentation for Oracle JDeveloper users that describes how to use the JDeveloper IDE and provides detailed information on the functionality available within it. Oracle Fusion Middleware Developing Applications with Oracle JDeveloper, 12c (12.2.1.2) E76675-01 Copyright © 2011, 2016, Oracle and/or its affiliates. All rights reserved. Primary Author: Akhilesh Swarnkaar This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
  • Oracle Fusion Middleware Statement of Direction

    Oracle Fusion Middleware Statement of Direction

    Data Sheet Fusion Middleware Statement of Direction Guidance on future product plans for the Fusion Middleware product family. April 2021 Copyright © 2021, Oracle and/or its affiliates Public 1 Fusion Middleware, Statement of Direction, March 2021 Copyright © 2021, Oracle and/or its affiliates Disclaimer The following is intended to outline our general product direction. It is intended for informational purposes only and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. Fusion Middleware Statement of Direction Oracle Fusion Middleware directions Oracle Fusion Middleware is Oracle’s digital business platform for the enterprise. It enables businesses to efficiently create and run agile, intelligent applications in client-server, web and cloud environments. Oracle’s strategy for Fusion Middleware is to continue to modernize the platform while providing bridging technologies to cloud native application development and deployment. Fusion Middleware customers can continue to enjoy superior application performance, reliability, and security today with a clear path to next-generation cloud technologies when ready to make that move. Oracle Fusion Middleware customers can migrate to the cloud at their own pace while continuing to receive support for their existing license software for many years to come. Oracle plans no forced upgrades or migrations. Release details WebLogic Server and Coherence 14.1.1, which began shipping in March 2020, are the first product releases in the Oracle Fusion Middleware 14.1 product line.
  • Creating Triggers with Trigger-By-Example in Graph Databases

    Creating Triggers with Trigger-By-Example in Graph Databases

    Creating Triggers with Trigger-By-Example in Graph Databases Kornelije Rabuzin a and Martina Sestakˇ b Faculty of Organization and Informatics, University of Zagreb, Pavlinska 2, 42000 Varazdin,ˇ Croatia Keywords: Trigger-By-Example, Graph Databases, Triggers, Active Databases. Abstract: In recent years, NoSQL graph databases have received an increased interest in the research community. Vari- ous query languages have been developed to enable users to interact with a graph database (e.g. Neo4j), such as Cypher or Gremlin. Although the syntax of graph query languages can be learned, inexperienced users may encounter learning difficulties regardless of their domain knowledge or level of expertise. For this reason, the Query-By-Example approach has been used in relational databases over the years. In this paper, we demon- strate how a variation of this approach, the Trigger-By-Example approach, can be used to define triggers in graph databases, specifically Neo4j, as database mechanisms activated upon a given event. The proposed ap- proach follows the Event-Condition-Action model of active databases, which represents the basis of a trigger. To demonstrate the proposed approach, a special graphical interface has been developed, which enables users to create triggers in a short series of steps. The proposed approach is tested on several sample scenarios. 1 INTRODUCTION Example approach has been introduced to simplify the process of designing database triggers. The The idea of active mechanisms able to react to a spec- approach uses the Query-By-Example (QBE) as a ified event implemented in database systems dates graphical interface for creating triggers (Lee et al., from 1975, when it was first implemented in IBM’s 2000b), and makes the entire trigger design process System R.
  • Chapter 10. Declarative Constraints and Database Triggers

    Chapter 10. Declarative Constraints and Database Triggers

    Chapter 10. Declarative Constraints and Database Triggers Table of contents • Objectives • Introduction • Context • Declarative constraints – The PRIMARY KEY constraint – The NOT NULL constraint – The UNIQUE constraint – The CHECK constraint ∗ Declaration of a basic CHECK constraint ∗ Complex CHECK constraints – The FOREIGN KEY constraint ∗ CASCADE ∗ SET NULL ∗ SET DEFAULT ∗ NO ACTION • Changing the definition of a table – Add a new column – Modify an existing column’s type – Modify an existing column’s constraint definition – Add a new constraint – Drop an existing constraint • Database triggers – Types of triggers ∗ Event ∗ Level ∗ Timing – Valid trigger types • Creating triggers – Statement-level trigger ∗ Option for the UPDATE event – Row-level triggers ∗ Option for the row-level triggers – Removing triggers – Using triggers to maintain referential integrity – Using triggers to maintain business rules • Additional features of Oracle – Stored procedures – Function and packages – Creating procedures – Creating functions 1 – Calling a procedure from within a function and vice versa • Discussion topics • Additional content and activities Objectives At the end of this chapter you should be able to: • Know how to capture a range of business rules and store them in a database using declarative constraints. • Describe the use of database triggers in providing an automatic response to the occurrence of specific database events. • Discuss the advantages and drawbacks of the use of database triggers in application development. • Explain how stored procedures can be used to implement processing logic at the database level. Introduction In parallel with this chapter, you should read Chapter 8 of Thomas Connolly and Carolyn Begg, “Database Systems A Practical Approach to Design, Imple- mentation, and Management”, (5th edn.).
  • Administrator's Guide for Conversion 11G Release 1 (11.1.1) E10800-02

    Administrator's Guide for Conversion 11G Release 1 (11.1.1) E10800-02

    Oracle® WebCenter Content Administrator's Guide for Conversion 11g Release 1 (11.1.1) E10800-02 November 2011 Oracle WebCenter Content Administrator's Guide for Conversion, 11g Release 1 (11.1.1) E10800-02 Copyright © 2010, 2011 Oracle and/or its affiliates. All rights reserved. Primary Author: Bruce Silver Contributing Author: Eric Raney Contributor: Brian Bergstrom This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
  • [1 ] Oracle® Fusion Middleware

    [1 ] Oracle® Fusion Middleware

    Oracle®[1] Fusion Middleware Release Notes for Oracle Coherence 12c (12.1.3) E51564-05 December 2015 Oracle Fusion Middleware Release Notes for Oracle Coherence, 12c (12.1.3) E51564-05 Copyright © 2014, 2015, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
  • IDUG NA 2007 Michael Paris: Hitchhikers Guide to Data Replication the Story Continues

    IDUG NA 2007 Michael Paris: Hitchhikers Guide to Data Replication the Story Continues

    Session: I09 Hitchhikers Guide to Data Replication The Story Continues ... Michael Paris Trans Union LLC May 9, 2007 9:50 a.m. – 10:50 a.m. Platform: Cross-Platform TransUnion is a global leader in credit and information management. For more than 30 years, we have worked with businesses and consumers to gather, analyze and deliver the critical information needed to build strong economies throughout the world. The result? Businesses can better manage risk and customer relationships. And consumers can better understand and manage credit so they can achieve their financial goals. Our dedicated associates support more than 50,000 customers on six continents and more than 500 million consumers worldwide. 1 The Hitchhiker’s Guide to IBM Data Replication • Rules for successful hitchhiking ••DONDON’’TT PANICPANIC •Know where your towel is •There is more than meets the eye •Have this guide and supplemental IBM materials at your disposal 2 Here are some additional items to keep in mind besides not smoking (we are forced to put you out before the sprinklers kick in) and silencing your electronic umbilical devices (there is something to be said for the good old days of land lines only and Ma Bell). But first a definition Hitchhike: Pronunciation: 'hich-"hIk Function: verb intransitive senses 1 : to travel by securing free rides from passing vehicles 2 : to be carried or transported by chance or unintentionally <destructive insects hitchhiking on ships> transitive senses : to solicit and obtain (a free ride) especially in a passing vehicle -hitch·hik·er noun – person that does the above Opening with the words “Don’t Panic” will instill a level of trust that at least by the end of this presentation you will be able to engage in meaningful conversations with your peers and management on the subject of replication.
  • Oracle Fusion Middleware Programming Enterprise Javabeans for Oracle Weblogic Server, 12C Release 1 (12.1.1) E24972-02

    Oracle Fusion Middleware Programming Enterprise Javabeans for Oracle Weblogic Server, 12C Release 1 (12.1.1) E24972-02

    Oracle® Fusion Middleware Programming Enterprise JavaBeans for Oracle WebLogic Server 12c Release 1 (12.1.1) E24972-02 January 2012 This document is a resource for software developers who develop applications that include WebLogic Server Enterprise JavaBeans (EJBs) using the Java Platform, Enterprise Edition 6. Oracle Fusion Middleware Programming Enterprise JavaBeans for Oracle WebLogic Server, 12c Release 1 (12.1.1) E24972-02 Copyright © 2007, 2012, Oracle and/or its affiliates. All rights reserved. Primary Author: Jeff Schieli This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
  • Forensic Attribution Challenges During Forensic Examinations of Databases

    Forensic Attribution Challenges During Forensic Examinations of Databases

    Forensic Attribution Challenges During Forensic Examinations Of Databases by Werner Karl Hauger Submitted in fulfilment of the requirements for the degree Master of Science (Computer Science) in the Faculty of Engineering, Built Environment and Information Technology University of Pretoria, Pretoria September 2018 Publication data: Werner Karl Hauger. Forensic Attribution Challenges During Forensic Examinations Of Databases. Master's disser- tation, University of Pretoria, Department of Computer Science, Pretoria, South Africa, September 2018. Electronic, hyperlinked versions of this dissertation are available online, as Adobe PDF files, at: https://repository.up.ac.za/ Forensic Attribution Challenges During Forensic Examinations Of Databases by Werner Karl Hauger E-mail: [email protected] Abstract An aspect of database forensics that has not yet received much attention in the aca- demic research community is the attribution of actions performed in a database. When forensic attribution is performed for actions executed in computer systems, it is nec- essary to avoid incorrectly attributing actions to processes or actors. This is because the outcome of forensic attribution may be used to determine civil or criminal liabil- ity. Therefore, correctness is extremely important when attributing actions in computer systems, also when performing forensic attribution in databases. Any circumstances that can compromise the correctness of the attribution results need to be identified and addressed. This dissertation explores possible challenges when performing forensic attribution in databases. What can prevent the correct attribution of actions performed in a database? The first identified challenge is the database trigger, which has not yet been studied in the context of forensic examinations. Therefore, the dissertation investigates the impact of database triggers on forensic examinations by examining two sub questions.
  • Oracle Fusion Middleware Tutorial for Running and Building an Application with Oracle SOA Suite, 11G Release 1 (11.1.1) E10275-02

    Oracle Fusion Middleware Tutorial for Running and Building an Application with Oracle SOA Suite, 11G Release 1 (11.1.1) E10275-02

    Oracle® Fusion Middleware Tutorial for Running and Building an Application with Oracle SOA Suite 11g Release 1 (11.1.1) E10275-02 August 2009 Oracle Fusion Middleware Tutorial for Running and Building an Application with Oracle SOA Suite, 11g Release 1 (11.1.1) E10275-02 Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Primary Author: Deborah Steiner Contributor: Heidi Buelow, Ananda Channaiah, Vamsee Goruganthu, Mark Kennedy, Greg Mally, Lynn Munsinger, Prasen Palvankar, Marja-Liisa Ranta, Clemens Utschig This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
  • SUGI 23: an Investigation of the Efficiency of SQL DML Operations Performed on an Oracle DBMS Using SAS/Accessr Software

    SUGI 23: an Investigation of the Efficiency of SQL DML Operations Performed on an Oracle DBMS Using SAS/Accessr Software

    Posters An Investigation of the Efficiency of SQL DML Operations Performed on an ORACLE DBMS using SAS/ACCESS Software Annie Guo, Ischemia Research and Education Foundation, San Francisco, California Abstract Table 1.1: Before Modification Of Final Records Id Entry MedCode Period1 Period2 Indication AG1001 Entry1 AN312 Postop Day1 Routine AG1001 Entry2 AN312 Postop Day1 Routine In an international epidemiological study of 2000 cardiac AG1001 Final AN312 Postop Day1 Non-routine ← To be updated surgery patients, the data of 7000 variables are entered AG1001 Final HC527 Intraop PostCPB Maintenance ← To be deleted AG1002 Entry1 PV946 Intraop PreCPB Non-routine ← To be inserted through a Visual Basic data entry system and stored in 57 AG1002 Entry2 PV946 Intraop PreCPB Non-routine as ‘Final’ large ORACLE tables. A SAS application is developed to Table 1.2: After Modification Of Final Records automatically convert the ORACLE tables to SAS data sets, Id Entry MedCode Period1 Period2 Indication AG1001 Entry1 AN312 Postop Day1 Routine perform a series of intensive data processing, and based AG1001 Entry2 AN312 Postop Day1 Routine AG1001 Final AN312 Postop Day1 Routine ← Updated upon the result of the data processing, dynamically pass AG1002 Entry1 PV946 Intraop PreCPB Non-routine AG1002 Entry2 PV946 Intraop PreCPB Non-routine ORACLE SQL Data Manipulation Language (DML) AG1002 Final PV946 Intraop PreCPB Non-routine ← Inserted commands such as UPDATE, DELETE and INSERT to ORACLE database and modify the data in the 57 tables. A Visual Basic module making use of ORACLE Views, Functions and PL/SQL Procedures has been developed to The modification of ORACLE data using SAS software can access the ORACLE data through ODBC driver, compare be resource-intensive, especially in dealing with large tables the 7000 variables between the 2 entries, and modify the and involving sorting in ORACLE data.