Oracle's database architecture consists of physical database components like data files and log files as well as memory structures in the system global area (SGA). The SGA contains structures like the database buffer cache, redo log buffer, and shared pool. When a SQL statement is processed, the user process connects to a server process which interacts with components in the SGA and writes to the redo log buffer. The statement is then parsed, executed, and rows are fetched before a commit ensures transactions are recovered.
- This document describes how to run a Forms Developer application using OC4J, navigate forms, and perform common data operations. It covers starting OC4J, running a form in a browser, retrieving restricted and unrestricted data, inserting, updating, and deleting records, and displaying database errors.
- At runtime, the Forms Client is downloaded by the browser. The Forms Servlet creates an HTML file and the Forms Listener Servlet starts a session between the client and Runtime Engine, which handles application logic and database connections.
- Users can navigate forms using menus, toolbars, buttons, and keys. There are two main modes: Normal allows changes while Enter-Query only allows queries without changes
This document outlines the objectives and content of an Oracle Forms Developer course. The course objectives are to create form modules with database interaction and GUI controls, display forms in multiple windows and layouts, test and debug forms. The content covers working in the Forms environment, creating basic and master-detail forms, items, windows, triggers for various purposes like validation and navigation, transaction processing, reusable code, and multiple form applications. The 5-day course consists of 25 lessons covering these topics.
Running a Forms Developer Application describes how to run and navigate an Oracle Forms application. The key points are:
1. A Forms application runs in a browser using a Java applet. The Forms servlet and listener servlet manage communication between the applet and runtime engine.
2. Users can navigate forms using menus, toolbars, buttons or function keys. Queries return all records by default or can be restricted.
3. There are two modes: enter-query allows queries but not changes; normal mode allows queries, changes and committing updates to the database.
4. Errors are displayed using the Help > Display Error menu. Records can be inserted, updated and deleted then
The document discusses the key differences between the World Wide Web (WWW) and Lotus Notes. It notes that WWW uses HTTP and URLs for communication and naming, while Notes uses its own RPC protocol and identifiers. It also summarizes some of the differences in their models for storage, clients, servers, synchronization, replication, fault tolerance, and access control.
OpenKM is a Free/Libre document management system that provides a web interface for managing arbitrary files. OpenKM includes a content repository, Lucene indexing, and jBPM workflow. The OpenKM system was developed using Java technology.
The document provides instructions for using Oracle Forms Developer 10g to build internet applications, including an instructor guide with objectives, course content, and chapters on creating forms, working in the Forms Builder environment, creating data blocks and items, and more. It contains proprietary information from Oracle Corporation and is protected by copyright law.
OneBridge Online Log Viewer (OOLV) is a web-based tool that allows administrators to access and search OneBridge logs without requiring remote control access to the server. It provides filters to search and display specific log information across large datasets without performance issues. OOLV matches the interface of the OneBridge Mobile Groupware log browser and allows viewing of synchronization logs, errors, warnings, and user activity.
The document describes a public library management application with both Windows and web-based front ends. The application allows users to add new members, check books in and out, and has been converted to a web service for interoperability. Key features include validation, error handling, and an intuitive user interface. Sample code is provided for both the Windows and ASP.NET versions. Security was added to the web service using WSE certificates.
- This document describes how to run a Forms Developer application using OC4J, navigate forms, and perform common data operations. It covers starting OC4J, running a form in a browser, retrieving restricted and unrestricted data, inserting, updating, and deleting records, and displaying database errors.
- At runtime, the Forms Client is downloaded by the browser. The Forms Servlet creates an HTML file and the Forms Listener Servlet starts a session between the client and Runtime Engine, which handles application logic and database connections.
- Users can navigate forms using menus, toolbars, buttons, and keys. There are two main modes: Normal allows changes while Enter-Query only allows queries without changes
This document outlines the objectives and content of an Oracle Forms Developer course. The course objectives are to create form modules with database interaction and GUI controls, display forms in multiple windows and layouts, test and debug forms. The content covers working in the Forms environment, creating basic and master-detail forms, items, windows, triggers for various purposes like validation and navigation, transaction processing, reusable code, and multiple form applications. The 5-day course consists of 25 lessons covering these topics.
Running a Forms Developer Application describes how to run and navigate an Oracle Forms application. The key points are:
1. A Forms application runs in a browser using a Java applet. The Forms servlet and listener servlet manage communication between the applet and runtime engine.
2. Users can navigate forms using menus, toolbars, buttons or function keys. Queries return all records by default or can be restricted.
3. There are two modes: enter-query allows queries but not changes; normal mode allows queries, changes and committing updates to the database.
4. Errors are displayed using the Help > Display Error menu. Records can be inserted, updated and deleted then
The document discusses the key differences between the World Wide Web (WWW) and Lotus Notes. It notes that WWW uses HTTP and URLs for communication and naming, while Notes uses its own RPC protocol and identifiers. It also summarizes some of the differences in their models for storage, clients, servers, synchronization, replication, fault tolerance, and access control.
OpenKM is a Free/Libre document management system that provides a web interface for managing arbitrary files. OpenKM includes a content repository, Lucene indexing, and jBPM workflow. The OpenKM system was developed using Java technology.
The document provides instructions for using Oracle Forms Developer 10g to build internet applications, including an instructor guide with objectives, course content, and chapters on creating forms, working in the Forms Builder environment, creating data blocks and items, and more. It contains proprietary information from Oracle Corporation and is protected by copyright law.
OneBridge Online Log Viewer (OOLV) is a web-based tool that allows administrators to access and search OneBridge logs without requiring remote control access to the server. It provides filters to search and display specific log information across large datasets without performance issues. OOLV matches the interface of the OneBridge Mobile Groupware log browser and allows viewing of synchronization logs, errors, warnings, and user activity.
The document describes a public library management application with both Windows and web-based front ends. The application allows users to add new members, check books in and out, and has been converted to a web service for interoperability. Key features include validation, error handling, and an intuitive user interface. Sample code is provided for both the Windows and ASP.NET versions. Security was added to the web service using WSE certificates.
The document discusses the communication process between web browsers and servers. It explains that HTTP is used to send requests from browsers to servers and responses from servers to browsers. It also describes the typical anatomy of an ASPX page, including page directives, code, and layout. Additionally, it covers single-file and code-behind models, website compilation, and the purpose and hierarchy of web configuration files.
The document summarizes Willie Jackson's .NET portfolio, which includes several phases of a library management application and an XML parsing application. Phase 1 created a Windows Forms application with classes for library members and books that retrieves data from a SQL Server database through stored procedures. Phase 2 added a ASP.NET website with master pages that allows librarians to check out books. Phase 3 created a web service allowing partner libraries to access the business layer. The XML parsing application allows authorized users to easily edit XML files using LINQ to XML without reading the XML code.
This document provides an overview and content review of 17 modules covering topics related to developing web applications using the Microsoft .NET framework and ASP.NET. The modules cover using Visual Studio .NET, .NET languages, creating ASP.NET web forms, adding code and tracing, validating user input, creating user controls, accessing data, working with XML and web services, managing state, configuring and optimizing ASP.NET applications, securing ASP.NET applications, and a review game and course evaluation.
This document provides an overview of the course "Visual Basic and Databases". It discusses what will be covered in the course including understanding how to use Visual Basic as a front-end interface to build database applications. It also reviews the basic concepts of databases, how Visual Basic fits into database management systems, and the steps to build a Visual Basic application. The requirements to complete the course are also outlined.
Alfresco Content Services provides open, flexible, highly scalable Enterprise Content Management
(ECM) capabilities. Content is accessible wherever and however you work and easily integrates with
your other business applications.
This document summarizes phases of a .NET library management application project. It describes creating a Windows Forms UI (Phase 1), replacing the business logic with student-written code (Phase 2), replacing the UI with an ASP.NET web interface (Phase 3), exposing functionality via web services (Phase 4), and a final group project modifying a student survey system to allow custom surveys.
The document describes how ASP pages are displayed and processed. It involves the following steps:
1) The browser requests the file from the server.
2) The server searches for and retrieves the file from its hard drive. If there is ASP code, it is processed.
3) The server returns the file to the browser.
4) The browser interprets the ASP file and displays it.
This document outlines the phases of development for a .NET library management system portfolio. Phase 1 involved designing and developing a web application front-end using ASP.NET with validation rules and AJAX controls. Phase 2 replaced the data access layer with one using LINQ and stored procedures. Phase 3 added a WCF service hosted by IIS using SSL and consumed by a Silverlight client. The final project expanded functionality to include searching, editing members, renewing memberships, and promoting juveniles to adults.
This document discusses using SQLite as a local database solution for Adobe AIR applications. It provides an overview of SQLite and AIR, demonstrates creating and querying a SQLite database using AIR, and discusses considerations for synchronous and asynchronous database operations, data storage, tools for managing SQLite databases, and potential issues to be aware of when using SQLite.
This document provides an overview of consuming and creating XML web services. It discusses finding, calling, and creating XML web services using HTTP, proxies, and ASP.NET. Key topics covered include the XML web service execution model, calling services using HTTP or a proxy, handling errors, and creating a web service by declaring web methods and building the project. The document concludes with a review of the lessons and describes an example lab application that consumes and exposes XML web services.
The document discusses various components of Oracle E-Business Suite applications, including:
1) E-Business Login which provides a unified login experience and home page for Oracle applications.
2) A self-service interface built using standard web technologies like JSP, servlets, and CSS for customizing business logic and user interfaces.
3) Workflow processes that can be triggered by events in applications and coordinate human and system tasks.
This chapter discusses updating web pages with Ajax. It introduces the XMLHttpRequest object, which allows asynchronous JavaScript requests and responses between a client and server without reloading the page. It covers the steps to make HTTP requests and process responses, including opening and sending requests, receiving data, and handling synchronous vs asynchronous requests. It also discusses techniques for making cross-domain requests, such as using JSON-P or CORS.
This web application written in Django allows users to validate XML documents and run XQuery queries against XML files stored in either a BaseX or eXist database. It has modules for user management, storage of XML files, and querying the databases. The storage module creates default XML files for new users and the query module generates API tokens and database users. Main views include registration, login/logout, managing XML files, validating XML, and running XQueries on BaseX and eXist. Asynchronous AJAX requests are also used.
This document provides an overview of streams and file input/output (I/O) in Java. It discusses different types of streams like input streams, output streams, byte streams, text streams, and standard streams. It also covers FileInputStream, FileOutputStream, FileReader, FileWriter, and how to use streams to read from and write to files and directories. Examples are provided demonstrating how to copy files, read from the keyboard, and use byte arrays as input streams.
The document discusses creating a simple form module in Oracle Apps using form builder wizards. It describes using the data block wizard to create a data block and the layout wizard to design the form's presentation. It also covers creating a control block, setting data block properties, establishing master-detail relationships between blocks, and configuring block coordination and deletion behavior.
Servlets as introduction (Advanced programming)Gera Paulos
Servlets allow servers to generate dynamic web page content. Servlets are Java programs that run on web servers to respond to client HTTP requests by generating documents like HTML pages. Servlets extend server functionality beyond static pages by enabling content generation, secure access, database interaction, and session tracking for each client. The servlet container receives requests and directs them to servlets, which process requests and return responses like HTML documents to clients. Servlets offer advantages over CGI like better performance since they run within the server address space rather than as separate processes.
External Data Connector for SharePoint is a connector and bridging solution to connect SharePoint with external databases and applications. This connector allows you to import data from different external sources and make them part of SharePoint Lists. Reports from external sources can be imported into SharePoint Libraries. Metadata imported from external data sources and applications can be updated into SharePoint columns. Any changes to the imported data sets, records, files, documents and reports can be updated back in the source through export.
in C++ console application, It Help you to find out how design library Management system.
This mini project in C++ Library Management System is a console application without graphic developed using the C++ programming language. It is compiled in Code::Blocks and DEV C++ with the GNU compiler. In this, you can perform book-related operations like in a REAL library management system with computer.
Here, you can perform functions such as add books, return books, issue books, delete record of books issued, view record of books issued, search for books, and more. File handling has been extensively used in this project for almost all functions. So, this project can definitely guide you to understand C++ mini projects in a better way.
The source code is organized well, and it has multiple comment lines to help you understand the project better.
For library management, this project considers six departments – Computer, Electrical, Civil, Mechanical, Chemical and BioChemistry. These departments work simultaneously with the operations mentioned above.
These are the functions used in this mini project:
void mainmenu(void) – This function is used to display the main menu of this project. Scroll down to Output to view the main menu.
void returnfunc(void) – Inside this function, the main menu function (mentioned above) is called when the user presses a key. With this, the user can return back to the main menu.
void addbooks(void) – This function adds books in a file. For that, you need to mention the department to which you want to add the book.
Oracle enterprise manager 12c migrate to pluggable databaseNaveen KNS
Oracle Enterprise Manager 12c allows users to convert an Oracle Database 11g database into a pluggable database within a 12c container database. The key steps are: 1) Configure both the 11g and 12c databases in EM12c, ensuring the 11g database has archive logging enabled and compatible character sets. 2) Select the 12c container database and initiate a migration using the user-managed data pump full transportable export/import option. 3) Provide connection details for the 11g database, schedule the conversion job, and submit it for processing. Once complete, the converted 11g database will be accessible as a pluggable database within the 12c container database.
racle DBA Interview Questions and Answers, CBT, Oracle E-books, Certifications http://oracledba-interview.blogspot.com.The best collections of Videos CBT or oracle dba the best collection of oracle dba Books interview questions even a dummy can get a job easily.Learn Oracle DBA in 1 2 3 steps
This document discusses various Oracle database concepts including:
- Creating tables, indexes, sequences, views and synonyms using SQL statements
- Using the Database Configuration Assistant (DBCA) to create, configure and manage Oracle databases
- Describing Oracle database architecture including memory structures, process structures and storage structures
The document discusses the communication process between web browsers and servers. It explains that HTTP is used to send requests from browsers to servers and responses from servers to browsers. It also describes the typical anatomy of an ASPX page, including page directives, code, and layout. Additionally, it covers single-file and code-behind models, website compilation, and the purpose and hierarchy of web configuration files.
The document summarizes Willie Jackson's .NET portfolio, which includes several phases of a library management application and an XML parsing application. Phase 1 created a Windows Forms application with classes for library members and books that retrieves data from a SQL Server database through stored procedures. Phase 2 added a ASP.NET website with master pages that allows librarians to check out books. Phase 3 created a web service allowing partner libraries to access the business layer. The XML parsing application allows authorized users to easily edit XML files using LINQ to XML without reading the XML code.
This document provides an overview and content review of 17 modules covering topics related to developing web applications using the Microsoft .NET framework and ASP.NET. The modules cover using Visual Studio .NET, .NET languages, creating ASP.NET web forms, adding code and tracing, validating user input, creating user controls, accessing data, working with XML and web services, managing state, configuring and optimizing ASP.NET applications, securing ASP.NET applications, and a review game and course evaluation.
This document provides an overview of the course "Visual Basic and Databases". It discusses what will be covered in the course including understanding how to use Visual Basic as a front-end interface to build database applications. It also reviews the basic concepts of databases, how Visual Basic fits into database management systems, and the steps to build a Visual Basic application. The requirements to complete the course are also outlined.
Alfresco Content Services provides open, flexible, highly scalable Enterprise Content Management
(ECM) capabilities. Content is accessible wherever and however you work and easily integrates with
your other business applications.
This document summarizes phases of a .NET library management application project. It describes creating a Windows Forms UI (Phase 1), replacing the business logic with student-written code (Phase 2), replacing the UI with an ASP.NET web interface (Phase 3), exposing functionality via web services (Phase 4), and a final group project modifying a student survey system to allow custom surveys.
The document describes how ASP pages are displayed and processed. It involves the following steps:
1) The browser requests the file from the server.
2) The server searches for and retrieves the file from its hard drive. If there is ASP code, it is processed.
3) The server returns the file to the browser.
4) The browser interprets the ASP file and displays it.
This document outlines the phases of development for a .NET library management system portfolio. Phase 1 involved designing and developing a web application front-end using ASP.NET with validation rules and AJAX controls. Phase 2 replaced the data access layer with one using LINQ and stored procedures. Phase 3 added a WCF service hosted by IIS using SSL and consumed by a Silverlight client. The final project expanded functionality to include searching, editing members, renewing memberships, and promoting juveniles to adults.
This document discusses using SQLite as a local database solution for Adobe AIR applications. It provides an overview of SQLite and AIR, demonstrates creating and querying a SQLite database using AIR, and discusses considerations for synchronous and asynchronous database operations, data storage, tools for managing SQLite databases, and potential issues to be aware of when using SQLite.
This document provides an overview of consuming and creating XML web services. It discusses finding, calling, and creating XML web services using HTTP, proxies, and ASP.NET. Key topics covered include the XML web service execution model, calling services using HTTP or a proxy, handling errors, and creating a web service by declaring web methods and building the project. The document concludes with a review of the lessons and describes an example lab application that consumes and exposes XML web services.
The document discusses various components of Oracle E-Business Suite applications, including:
1) E-Business Login which provides a unified login experience and home page for Oracle applications.
2) A self-service interface built using standard web technologies like JSP, servlets, and CSS for customizing business logic and user interfaces.
3) Workflow processes that can be triggered by events in applications and coordinate human and system tasks.
This chapter discusses updating web pages with Ajax. It introduces the XMLHttpRequest object, which allows asynchronous JavaScript requests and responses between a client and server without reloading the page. It covers the steps to make HTTP requests and process responses, including opening and sending requests, receiving data, and handling synchronous vs asynchronous requests. It also discusses techniques for making cross-domain requests, such as using JSON-P or CORS.
This web application written in Django allows users to validate XML documents and run XQuery queries against XML files stored in either a BaseX or eXist database. It has modules for user management, storage of XML files, and querying the databases. The storage module creates default XML files for new users and the query module generates API tokens and database users. Main views include registration, login/logout, managing XML files, validating XML, and running XQueries on BaseX and eXist. Asynchronous AJAX requests are also used.
This document provides an overview of streams and file input/output (I/O) in Java. It discusses different types of streams like input streams, output streams, byte streams, text streams, and standard streams. It also covers FileInputStream, FileOutputStream, FileReader, FileWriter, and how to use streams to read from and write to files and directories. Examples are provided demonstrating how to copy files, read from the keyboard, and use byte arrays as input streams.
The document discusses creating a simple form module in Oracle Apps using form builder wizards. It describes using the data block wizard to create a data block and the layout wizard to design the form's presentation. It also covers creating a control block, setting data block properties, establishing master-detail relationships between blocks, and configuring block coordination and deletion behavior.
Servlets as introduction (Advanced programming)Gera Paulos
Servlets allow servers to generate dynamic web page content. Servlets are Java programs that run on web servers to respond to client HTTP requests by generating documents like HTML pages. Servlets extend server functionality beyond static pages by enabling content generation, secure access, database interaction, and session tracking for each client. The servlet container receives requests and directs them to servlets, which process requests and return responses like HTML documents to clients. Servlets offer advantages over CGI like better performance since they run within the server address space rather than as separate processes.
External Data Connector for SharePoint is a connector and bridging solution to connect SharePoint with external databases and applications. This connector allows you to import data from different external sources and make them part of SharePoint Lists. Reports from external sources can be imported into SharePoint Libraries. Metadata imported from external data sources and applications can be updated into SharePoint columns. Any changes to the imported data sets, records, files, documents and reports can be updated back in the source through export.
in C++ console application, It Help you to find out how design library Management system.
This mini project in C++ Library Management System is a console application without graphic developed using the C++ programming language. It is compiled in Code::Blocks and DEV C++ with the GNU compiler. In this, you can perform book-related operations like in a REAL library management system with computer.
Here, you can perform functions such as add books, return books, issue books, delete record of books issued, view record of books issued, search for books, and more. File handling has been extensively used in this project for almost all functions. So, this project can definitely guide you to understand C++ mini projects in a better way.
The source code is organized well, and it has multiple comment lines to help you understand the project better.
For library management, this project considers six departments – Computer, Electrical, Civil, Mechanical, Chemical and BioChemistry. These departments work simultaneously with the operations mentioned above.
These are the functions used in this mini project:
void mainmenu(void) – This function is used to display the main menu of this project. Scroll down to Output to view the main menu.
void returnfunc(void) – Inside this function, the main menu function (mentioned above) is called when the user presses a key. With this, the user can return back to the main menu.
void addbooks(void) – This function adds books in a file. For that, you need to mention the department to which you want to add the book.
Oracle enterprise manager 12c migrate to pluggable databaseNaveen KNS
Oracle Enterprise Manager 12c allows users to convert an Oracle Database 11g database into a pluggable database within a 12c container database. The key steps are: 1) Configure both the 11g and 12c databases in EM12c, ensuring the 11g database has archive logging enabled and compatible character sets. 2) Select the 12c container database and initiate a migration using the user-managed data pump full transportable export/import option. 3) Provide connection details for the 11g database, schedule the conversion job, and submit it for processing. Once complete, the converted 11g database will be accessible as a pluggable database within the 12c container database.
racle DBA Interview Questions and Answers, CBT, Oracle E-books, Certifications http://oracledba-interview.blogspot.com.The best collections of Videos CBT or oracle dba the best collection of oracle dba Books interview questions even a dummy can get a job easily.Learn Oracle DBA in 1 2 3 steps
This document discusses various Oracle database concepts including:
- Creating tables, indexes, sequences, views and synonyms using SQL statements
- Using the Database Configuration Assistant (DBCA) to create, configure and manage Oracle databases
- Describing Oracle database architecture including memory structures, process structures and storage structures
The document provides an overview of Oracle architecture including:
- Data is stored in data blocks which make up extents that form segments within tablespaces. Segments represent database objects like tables and indexes.
- The system global area (SGA) resides in memory and caches data and structures for efficient processing. It includes the database buffer cache, redo log buffer, and shared pool.
- Server processes handle SQL statements by parsing, executing, and returning results. Background processes perform functions like checkpoint, recovery, and writing data to disk.
- Transactions are written to the redo log and undo segments maintain rollback information. This supports data consistency, recovery, and rolling back transactions.
The document provides an overview of Oracle database physical and logical structures, background processes, backup methods, and administrative tasks. It describes key components like datafiles, control files, redo logs, tablespaces, schemas and segments that make up the physical and logical structure. It also explains the system global area (SGA) and program global area (PGA) memory structures and background processes like SMON, PMON, DBWR, LGWR and ARCH that manage the database instance. Common backup methods like cold backups, hot backups and logical exports are summarized. Finally, it lists some daily, weekly and other administrative tasks.
- Oracle Database is a comprehensive, integrated database management system that provides an open approach to information management.
- The Oracle architecture includes database structures like data files, control files, and redo log files as well as memory structures like the system global area (SGA) and process global area (PGA).
- Key components of the Oracle architecture include the database buffer cache, shared pool, redo log buffer, and background processes that manage instances.
This lesson covers Oracle Database 10g architecture, including memory structures, process structures, and storage structures. It aims to teach students how to use RMAN for backup and recovery, employ monitoring practices, and manage resources, jobs, security and globalization issues. The suggested schedule outlines topics like installation, database creation, storage, users, backup and recovery concepts, performance, and the HR schema example database.
This document provides an overview of the physical and logical structures of an Oracle database, including datafiles, control files, redo logs, and tablespaces. It also describes Oracle instances, the system global area (SGA), program global area (PGA), and background processes. Administrative tasks like backups, monitoring, and patching are discussed. Specific details are given about the Computer Science database, including its server, tablespaces, and 4mm DAT tape backup method.
This document provides an overview of Oracle DBA training topics including relational database management systems (RDBMS), RDBMS and SQL, DBA tasks, Oracle database architecture, Oracle instance architecture, background processes, system global area (SGA), shared pool, library cache, and data dictionary cache. Key points covered include how RDBMS stores and accesses data through tables, the roles of consistency and concurrency in RDBMS, common DBA responsibilities like installation, backup/recovery, monitoring and performance tuning, and important components that make up the Oracle database architecture like instances, processes, memory structures, and caches.
MS SQL Server is a database server produced by Microsoft that enables users to write and execute SQL queries and statements. It consists of several features like Query Analyzer, Profiler, and Service Manager. Multiple instances of SQL Server can be installed on a machine, with each instance having its own set of users, databases, and other objects. SQL Server uses data files, filegroups, and transaction logs to store database objects and record transactions. The data dictionary contains metadata about database schemas and is stored differently in Oracle and SQL Server.
This document provides an overview of the Oracle database architecture. It describes the major architectural components including memory structures like the system global area (SGA) and program global area (PGA), background processes, logical and physical storage structures, and Automatic Storage Management (ASM). The objectives are to explain these components, how they relate to each other, and their functions in managing the Oracle database.
The document provides an overview of Oracle 10g database architecture including its physical and logical structures as well as processes. Physically, a database consists of datafiles, redo logs, and control files. Logically, it is divided into tablespaces containing schemas, segments, and other objects. The Oracle instance comprises the system global area (SGA) shared memory and background processes that manage tasks like writing redo logs and checkpointing data blocks. User processes connect to the database through sessions allocated in the program global area.
This document provides an overview of the Oracle database architecture. It describes the major components of Oracle's architecture, including the memory structures like the system global area and program global area, background processes, and the logical and physical storage structures. The key components are the database buffer cache, redo log buffer, shared pool, processes, tablespaces, data files, and redo log files.
This document discusses backup and recovery concepts in Oracle databases. It covers different types of failures that can occur, including statement failures, user process failures, network failures, instance failures, and media failures. It describes how to configure the database for recoverability through techniques like implementing the flash recovery area, multiplexing control files and redo log files, and placing the database in ARCHIVELOG mode to archive redo logs. The goal is to minimize data loss and mean time to recovery (MTTR) through redundancy and fast recovery processes.
Exploring the Oracle Database Architecture.pptMohammedHdi1
The document provides an overview of the Oracle database architecture, including its major components, memory structures, background processes, storage structures, and how they interact. It describes the system global area (SGA) and program global area (PGA) memory structures. It outlines the roles of key background processes like the database writer, log writer, and checkpoint processes. It also maps the logical and physical storage structures of the database from segments to data blocks, and describes the role of Automatic Storage Management (ASM) in managing database storage.
The document provides an overview of the Oracle database architecture, including its major components, memory structures, background processes, storage structures, and how they interact. It describes the system global area (SGA) and program global area (PGA) memory structures. It outlines the roles of key background processes like the database writer, log writer, and checkpoint processes. It also maps the logical and physical storage structures of the database from segments and extents down to data blocks and disk blocks. Finally, it gives an overview of Automatic Storage Management (ASM) and how it manages Oracle database files and storage.
This document provides an overview of SQL tuning and tools for improving SQL performance. It discusses reasons for inefficient SQL such as stale statistics, missing indexes, and suboptimal execution plans. It describes Oracle tools for monitoring and tuning SQL like AWR, ADDM, SQL Tuning Advisor, and SQL Access Advisor. It outlines tasks for SQL tuning including identifying high-load SQL, gathering statistics, and creating new indexes. It also provides guidance on proactive tuning through good application design, data modeling, indexing strategies, and writing efficient SQL.
This document provides an introduction to Oracle 10g, including its architecture and components. It discusses the Oracle instance, System Global Area (SGA) and Program Global Area (PGA). It describes the key background processes like SMON, PMON, DBWn, LGWR, CKPT and ARCn. It also explains the critical Oracle files - parameter file, control files, redo log files and data files. Finally, it outlines Oracle's logical data structures of tablespaces, segments, extents and data blocks.
The document outlines the main components of the Oracle architecture, including the Oracle instance, System Global Area (SGA), database, background processes, and connections between users and the database. It describes the primary functions and interactions of components like the database buffer cache, redo log buffer, and background processes like DBWn, LGWR, and SMON.
XML is a markup language that allows users to define their own tags and structure for documents. It separates content from formatting and is extensible, platform-independent, and human-readable. Well-formed XML documents follow syntax rules like having matching open and close tags and properly nested elements. Valid XML documents also comply with constraints defined in their associated DTD. Common XML components include elements, attributes, namespaces, comments, and CDATA sections.
This document provides an overview of XML (Extensible Markup Language) including:
- The basic structure and components of an XML document including elements, attributes, entities, and advanced components.
- An example well-commented XML document.
- The basic rules for creating a well-formed XML document including being case sensitive, requiring start and end tags, proper nesting, and more.
- Common errors in element naming and how to avoid them.
- How to walk through modifying an example XML document to add new elements and ensure it remains well-formed.
XML (Extensible Markup Language) allows users to define their own customized markup languages to structure data. It was created as a simplified version of SGML to make it usable on the web. XML is important because it removes constraints of HTML and allows for richer content than HTML alone. XML will enable easier exchange of data between businesses and applications.
XML is a markup language that allows users to define their own tags and structure for documents. It separates content from formatting and is extensible, platform-independent, and human-readable. Well-formed XML documents follow syntax rules like having matching open and close tags and properly nested elements. Valid XML documents also comply with constraints defined in their associated DTD. Common XML components include elements, attributes, namespaces, comments, and CDATA sections.
This document provides an overview of XML (Extensible Markup Language) including:
- The basic structure and components of an XML document including elements, attributes, entities, and advanced components.
- An example well-commented XML document.
- The basic rules for creating a well-formed XML document including being case sensitive, requiring start and end tags, proper nesting, and more.
- Common errors in element naming and how to avoid them.
- How to add new elements and attributes to an example XML document to ensure it remains well-formed.
XML stands for Extensible Markup Language and is used to mark up data so it can be processed by computers, whereas HTML is used to mark up text to be displayed for users. Both XML and HTML use elements enclosed in tags, attributes, and entities, but XML only describes content while HTML describes both structure and appearance. XML allows users to define their own tags, and is strictly structured, making it suitable for data processing by computers.
This document provides an overview of XML, including its basic structure and components. XML documents use elements to structure and tag content. Elements must be properly nested within a single root element and can have attributes. The relationships between these elements form a tree structure. XML documents also support comments, processing instructions, and character encoding. CSS and XSLT can be used to display and transform XML for web users. While databases are better for structured data, XML is well suited for loosely structured or large records.
The document provides an introduction to shell scripting basics in UNIX/Linux. It discusses what a shell and shell script are, introduces the popular bash shell, and covers running commands, variables, logic, and other shell scripting concepts. The key points covered include:
- A shell is a program that takes commands and runs other programs. Popular shells include bash, csh, tcsh, and ksh.
- A shell script is a text file containing shell commands that is executable. Creating and running a simple "Hello world" script is demonstrated.
- Running commands, pipes, redirection, variables, logic, and flow control like if/else, for loops are explained.
- Useful bash
This document provides an introduction and overview of the Unix operating system. It covers topics such as getting help, the file system, the shell, network security, email clients, text editors, input/output redirection, printing, process management, and the X window system. The document is intended to help new Unix users understand basic Unix concepts and commands.
Linux is an open source operating system created by Linus Torvalds in 1991. It uses a Linux kernel and includes many common Unix tools. Linux is free to use and modify due to its open source licensing. It runs on many hardware platforms and is growing in popularity for servers, desktops, and embedded systems due to its low cost, stability, and security. Users can download Linux from distributions like Red Hat which package the Linux kernel with additional software and support.
After completing this section, students should be able to log into the Linux system, understand and manipulate the UNIX file system, describe the role of the shell, use basic file commands like cd, ls, cp, and rm, use standard input/output and piping, and understand the UNIX philosophy. The document provides an introduction to UNIX operating systems, shells, file systems, basic commands, and input/output redirection.
This document provides an overview of the C programming language, including its history, characteristics, and syntax. C was developed in the 1970s alongside Unix and became widely used for system programming. It allows for close interaction with the operating system and hardware. The document walks through a simple "Hello World" program to demonstrate C's syntax, including preprocessing, compilation, linking, and execution. It also provides a more complex guessing game example to illustrate additional C language features like variables, operators, conditionals, and loops.
This document provides an introduction to the C programming language. It discusses key concepts like functions, variables, data types, memory, scopes, expressions, operators, control flow with if/else statements and loops. It also explains how passing arguments by value means functions cannot directly modify their parameters, but passing addresses allows modifying variables in the calling scope. Overall it serves as a helpful primer on basic C syntax and programming concepts for newcomers to the language.
This document provides an overview of introductory concepts in C programming, including simple programs to print text and perform arithmetic. It covers basic syntax like comments, functions, variables, data types, operators, input/output, and conditional statements. Memory concepts are introduced, as well as the preprocessor, standard libraries, and control flow structures like if/else. Examples are provided to demonstrate printing text, taking user input, performing calculations, and making decisions based on relational comparisons.
This document provides an introduction to C programming over 13 pages. It covers the purpose and schedule of the lectures, differences between C and Java, C program structure, keywords, variables, data types, and more. The main points are that the lectures will provide a crash course in C with an emphasis on differences from Java, cover practical examples and topics related to C programming, and include history, language overview, pointers, memory management, compiling and debugging.
This document provides an introduction to programming in C. It begins by discussing computers, hardware, software, data, and information processing. It then discusses what programming is and how to approach solving problems through programming. The document outlines the major components of a C program and provides a first example program. It also covers key C programming concepts like variables, data types, expressions, control flow, functions, pointers, arrays, strings, structures, files and memory allocation. The document is intended to introduce readers to programming in C from a high level.
The document provides an overview of the C programming language. It begins with a brief history of C and how it evolved from the B programming language to support UNIX. It describes C as a systems programming language that is close to hardware but with higher-level constructs than assembly. The rest of the document outlines key C language concepts like data types, variables, operators, functions, and control structures. It provides examples of how to use basic programming elements like if/else statements and switch statements.
This document contains repeated text about printing or viewing notes pages for a preface rather than slides. It provides instructions to print or view notes pages for a preface section eight separate times without any other notable information.
This document provides an overview and objectives for a course on Oracle database administration. It covers topics such as controlling user access, managing schema objects, manipulating large data sets, generating reports, managing data in different time zones, retrieving data using subqueries, hierarchical retrieval, and regular expression support. Each chapter provides learning objectives and exercises for students to reinforce the concepts covered.
Regular expressions can be used in SQL to search, match, and replace strings. Key regular expression functions include REGEXP_INSTR, REGEXP_SUBSTR, and REGEXP_REPLACE. Meta characters like *, +, and [] are used to define patterns to match. For example, 'a+' would match one or more occurrences of 'a' in a string.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Webinar: Designing a schema for a Data WarehouseFederico Razzoli
Are you new to data warehouses (DWH)? Do you need to check whether your data warehouse follows the best practices for a good design? In both cases, this webinar is for you.
A data warehouse is a central relational database that contains all measurements about a business or an organisation. This data comes from a variety of heterogeneous data sources, which includes databases of any type that back the applications used by the company, data files exported by some applications, or APIs provided by internal or external services.
But designing a data warehouse correctly is a hard task, which requires gathering information about the business processes that need to be analysed in the first place. These processes must be translated into so-called star schemas, which means, denormalised databases where each table represents a dimension or facts.
We will discuss these topics:
- How to gather information about a business;
- Understanding dictionaries and how to identify business entities;
- Dimensions and facts;
- Setting a table granularity;
- Types of facts;
- Types of dimensions;
- Snowflakes and how to avoid them;
- Expanding existing dimensions and facts.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Project Management Semester Long Project - Acuityjpupo2018
Acuity is an innovative learning app designed to transform the way you engage with knowledge. Powered by AI technology, Acuity takes complex topics and distills them into concise, interactive summaries that are easy to read & understand. Whether you're exploring the depths of quantum mechanics or seeking insight into historical events, Acuity provides the key information you need without the burden of lengthy texts.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
9. Oracle Instance Management System Monitor SMON Database Writer DBW0 Log Writer LGWR Process Monitor PMON Archiver ARC0 SGA Java pool Shared pool Large pool Streams pool Database buffer cache Redo log buffer Check point CKPT
10. Oracle Memory Structures Java pool Database buffer cache Redo log buffer Shared pool Large pool SGA Streams pool Server process 1 PGA Server process 2 PGA Back- ground process PGA
12. Oracle Processes System monitor SMON Database writer DBW0 Check point CKPT Log writer LGWR Process monitor PMON Archiver ARC0 Server process Server process Server process Server process System Global Area SGA Background processes
15. Connecting to an Instance User Server Server User Client User Server Oracle server Server Application server Browser
16.
17.
18.
19.
20.
21.
22. Processing a DML Statement UPDATE employees ... SGA Redo log buffer Database buffer cache Shared pool User process Server process 1 1 2 3 4 Database Data files Control files Redo log files
26. COMMIT Processing 1 3 4 Instance SGA Redo log buffer Database buffer cache Shared pool LGWR 2 User process Server process Database Data files Control files Redo log files
27.
28.
29.
30.
Editor's Notes
Oracle Database 10 g : SQL Fundamentals II D - Objectives This appendix introduces the Oracle server architecture by describing the files, processes, and memory structures involved in establishing a database connection and executing a SQL command.
Oracle Database Architecture: Overview The Oracle database consists of two main components — the instance and the database itself. The database consists of the physical files such as: The control file where the database configuration is stored The redo log files that have information required for database recovery The data files where all data is stored The parameter file which contains the parameters that control the size and properties of an instance The password file which contains the super user or SYSDBA password The instance consists of the System Global Area (SGA) and the server processes that perform tasks within the database.
Oracle Database 10 g : SQL Fundamentals II D - Database Physical Architecture The files that make up an Oracle database are organized into the following: Control files: These files contain data about the database itself, called the metadata. These files are critical to the database. Without them you cannot open the data files to access the data within the database. Data files: These files contain the data of the database. Online redo log files: These files allow for instance recovery of the database. If the database were to crash and not lose any data files, the instance will be able to recover the database with the information in these files. There are other files which are not officially part of the database but are important to the successful running of the database. These are: Parameter file: The parameter file is used to define how the instance will be configured when it starts up. Password file: This file allows users to connect remotely to the database and perform administrative tasks. Archive log files: These files contain an ongoing history of the redo generated by the instance. These files allow for database recovery. By using these files and a backup of the database, it is possible to recover a lost data file.
Oracle Database 10 g : SQL Fundamentals II D - Control Files When you start the instance and mount the database, the control file is read. The entries in the control file specify the physical files that constitute the database. When you add additional files to your database, the control file is automatically updated. The location of the control files is specified in an initialization parameter. To protect against failure of the database due to the loss of the control file, you should multiplex the control file on at least three different physical devices. By specifying multiple files through the initialization parameter, you enable the Oracle database server to maintain multiple copies of the control file.
Oracle Database 10 g : SQL Fundamentals II D - Redo Log Files Redo log files are used to record changes to the database as a result of transactions and internal Oracle database server actions. They protect the database from loss of integrity due to system failures caused by power outages, disk failures, and so on. Redo log files should be multiplexed to ensure that the information stored in them is not lost in the event of a disk failure. The redo log consists of groups of redo log files. A group consists of a redo log file and its multiplexed copies. Each identical copy is said to be a member of that group and each group is identified by a number. The log writer process (LGWR) writes redo records from the redo log buffer to a redo log group until the file is filled or a log switch operation is requested. Then it switches and writes to the files in the next group. The redo log groups are used in a circular fashion.
Oracle Database 10 g : SQL Fundamentals II D - Tablespaces and Data Files A database is divided into logical storage units called tablespaces, which can be used to group related logical structures. Each database is logically divided into one or more tablespaces. One or more data files are explicitly created for each tablespace to physically store the data of all logical structures in a tablespace. Note: You can also create bigfile tablespaces, which are tablespaces with a single, but very large (up to 4 G blocks) data file. Traditional smallfile tablespaces (which are the default), can contain multiple data files, but the files cannot be as large. For more information about bigfile tablespaces, refer to the Database Administrator’s Guide .
Oracle Database 10 g : SQL Fundamentals II D - Segments, Extents, and Blocks Database objects such as tables and indexes are stored in tablespaces as segments. Each segment contains one or more extents. An extent consists of contiguous data blocks, which means that each extent can exist only in one data file. Data blocks are the smallest unit of I/O in the database. When the database requests a set of data blocks from the OS, the OS maps this to the actual OS block on the storage device. Because of this, you need not be aware of the physical address of any of the data in your database. This also means that a data file can be striped and or mirrored on several disks. The size of the data block can be set at database creation time. The default size of 8 K is adequate for most databases. If your database supports a data warehouse application that has large tables and indexes, then a larger block may be beneficial. If your database supports a transactional application where reads and write are very random, then specifying a smaller block size may be beneficial. The maximum block size is dependent on your OS. The minimum block size is 2 K and should rarely (if ever) be used. You can have tablespaces with different block sizes. Generally this should be used only to support transportable tablespaces. For details, refer to the Database Administrator’s Guide .
Oracle Database 10 g : SQL Fundamentals II D - Oracle Instance Management An Oracle database server consists of an Oracle database and an Oracle instance. An Oracle instance consists of memory buffers known as the System Global Area (SGA) and background processes. The instance is idle (nonexistent) until it is started. When the instance is started, an initialization parameter file is read and the instance is configured accordingly. After the instance is started and the database is opened, users can access the database.
Oracle Database 10 g : SQL Fundamentals II D - Oracle Memory Structures The basic memory structures associated with an Oracle instance include: System Global Area (SGA): Shared by all server and background processes Program Global Area (PGA): Private to each server and background process; there is one PGA for each process The System Global Area (SGA) is a shared memory area that contains data and control information for the instance. The SGA consists of the following data structures: Database buffer cache: Caches blocks of data retrieved from the database Redo log buffer: Caches redo information (used for instance recovery) until it can be written to the physical redo log files stored on disk Shared pool: Caches various constructs that can be shared among users Large pool: Optional area used for buffering large I/O requests Java pool: Used for all session-specific Java code and data within the Java Virtual Machine (JVM) Streams pool: Used by Oracle Streams When you start the instance using Enterprise Manager or SQL*Plus, the memory allocated for the SGA is displayed.
Oracle Database 10 g : SQL Fundamentals II D - Oracle Memory Structures (continued) With the dynamic SGA infrastructure, the size of the database buffer cache, the shared pool, the large pool, the Java pool, and the Streams pool can be changed without shutting down the instance. The preconfigured database has been pretuned with adequate settings for the memory parameters. However, as your database usage expands you may find it necessary to alter the settings of the memory parameters. Oracle provides alerts and advisors to identify memory sizing problems and to help you determine appropriate values for memory parameters. A Program Global Area (PGA) is a memory region which contains data and control information for each server process. A server process services a client’s requests. Each server process has its own private PGA area that is created when the server process is started. Access to it is exclusive to that server process, and is read and written only by Oracle code acting on behalf of it. The amount of PGA memory used and its content depends on whether the instance is configured in shared server mode. Generally, the PGA contains the following: Private SQL area: Contains data such as bind information and run-time memory structures. Each session that issues a SQL statement has a private SQL area. Session memory: Memory allocated to hold session variables and other information related to the session
Oracle Database 10 g : SQL Fundamentals II D - Oracle Processes When you invoke an application program or an Oracle tool such as Enterprise Manager, the Oracle server creates a server process to execute commands issued by the application. Oracle also creates a set of background processes for an instance that interact with each other and with the operating system to manage the memory structures, asynchronously perform I/O to write data to disk, and do general housekeeping. Which background processes are present depends upon the features that are being used in the database. The most common background processes are the following: System monitor (SMON): Performs crash recovery when the instance is started following a failure Process monitor (PMON): Performs process cleanup when a user process fails Database writer (DBW n ): Writes modified blocks from the database buffer cache to the files on disk Checkpoint (CKPT): Signals DBW n at checkpoints and updates all of the data files and control files of the database to indicate the most recent checkpoint Log writer (LGWR): Writes redo log entries to disk Archiver (ARC n ): Copies the redo log files to archival storage when the log files are full or a log switch occurs
Oracle Database 10 g : SQL Fundamentals II D - Other Key Files The Oracle server also uses other files that are not part of the database: The parameter file defines the characteristics of an Oracle instance. For example, it contains parameters that size some of the memory structures in the SGA. The password file authenticates which users are permitted to start up and shut down an Oracle instance. Archived redo log files are offline copies of the redo log files that may be necessary for recovery from media failures.
Oracle Database 10 g : SQL Fundamentals II D - Components Used to Process SQL Not all of the components of an Oracle instance are used to process SQL statements. The user and server processes are used to connect a user to an Oracle instance. These processes are not part of the Oracle instance, but are required to process a SQL statement. Some of the background processes, SGA structures, and database files are used to process SQL statements. Depending on the type of SQL statement, different components are used: Queries require additional processing to return rows to the user. Data manipulation language (DML) statements require additional processing to log the changes made to the data. Commit processing ensures that the modified data in a transaction can be recovered. Some required background processes do not directly participate in processing a SQL statement but are used to improve performance and to recover the database. The optional background process, ARC0, is used to ensure that a production database can be recovered.
Oracle Database 10 g : SQL Fundamentals II D - Processes Used to Connect to an Instance Before users can submit SQL statements to the Oracle server, they must connect to an instance. The user starts a tool such as i SQL*Plus or runs an application developed using a tool such as Oracle Forms. This application or tool is executed in a user process . In the most basic configuration, when a user logs on to the Oracle server, a process is created on the computer running the Oracle server. This process is called a server process. The server process communicates with the Oracle instance on behalf of the user process that runs on the client. The server process executes SQL statements on behalf of the user. Connection A connection is a communication pathway between a user process and an Oracle server. A database user can connect to an Oracle server in one of three ways: The user logs on to the operating system running the Oracle instance and starts an application or tool that accesses the database on that system. The communication pathway is established using the interprocess communication mechanisms available on the host operating system.
Oracle Database 10 g : SQL Fundamentals II D - Processes Used to Connect to an Instance (continued) Connection (continued) The user starts the application or tool on a local computer and connects over a network to the computer running the Oracle instance. In this configuration, called client/server, network software is used to communicate between the user and the Oracle server. In a three-tiered connection, the user’s computer communicates over the network to an application or a network server, which is connected through a network to the machine running the Oracle instance. For example, the user runs a browser on a network computer to use an application residing on an NT server that retrieves data from an Oracle database running on a UNIX host. Sessions A session is a specific connection of a user to an Oracle server. The session starts when the user is validated by the Oracle server, and it ends when the user logs out or when there is an abnormal termination. For a given database user, many concurrent sessions are possible if the user logs on from many tools, applications, or terminals at the same time. Except for some specialized database administration tools, starting a database session requires that the Oracle server be available for use. Note: The type of connection explained here, where there is a one-to-one correspondence between a user and server process, is called a dedicated server connection.
Oracle Database 10 g : SQL Fundamentals II D - Query Processing Steps Queries are different from other types of SQL statements because, if successful, they return data as results. Whereas other statements simply return success or failure, a query can return one row or thousands of rows. There are three main stages in the processing of a query: Parse Execute Fetch During the parse stage, the SQL statement is passed from the user process to the server process, and a parsed representation of the SQL statement is loaded into a shared SQL area. During the parse, the server process performs the following functions: Searches for an existing copy of the SQL statement in the shared pool Validates the SQL statement by checking its syntax Performs data dictionary lookups to validate table and column definitions The execute fetch executes the statement using the best optimizer approach and the fetch retrieves the rows back to the user.
Oracle Database 10 g : SQL Fundamentals II D - Shared Pool Components During the parse stage, the server process uses the area in the SGA known as the shared pool to compile the SQL statement. The shared pool has two primary components: Library cache Data dictionary cache Library Cache The library cache stores information about the most recently used SQL statements in a memory structure called a shared SQL area. The shared SQL area contains: The text of the SQL statement The parse tree: A compiled version of the statement The execution plan: The steps to be taken when executing the statement The optimizer is the function in the Oracle server that determines the optimal execution plan. If a SQL statement is re-executed and a shared SQL area already contains the execution plan for the statement, the server process does not need to parse the statement. The library cache improves the performance of applications that reuse SQL statements by reducing parse time and memory requirements. If the SQL statement is not reused, it is eventually aged out of the library cache.
Oracle Database 10 g : SQL Fundamentals II D - Shared Pool Components (continued) Data Dictionary Cache The data dictionary cache, also known as the dictionary cache or row cache, is a collection of the most recently used definitions in the database. It includes information about database files, tables, indexes, columns, users, privileges, and other database objects. During the parse phase, the server process looks for the information in the dictionary cache to resolve the object names specified in the SQL statement and to validate the access privileges. If necessary, the server process initiates the loading of this information from the data files. Sizing the Shared Pool The size of the shared pool is specified by the initialization parameter SHARED_POOL_SIZE .
Oracle Database 10 g : SQL Fundamentals II D - Function of the Database Buffer Cache When a query is processed, the server process looks in the database buffer cache for any blocks it needs. If the block is not found in the database buffer cache, the server process reads the block from the data file and places a copy in the buffer cache. Because subsequent requests for the same block may find the block in memory, the requests may not require physical reads. The Oracle server uses a least recently used algorithm to age out buffers that have not been accessed recently to make room for new blocks in the buffer cache. Sizing the Database Buffer Cache The size of each buffer in the buffer cache is equal to the size of an Oracle block, and it is specified by the DB_BLOCK_SIZE parameter. The number of buffers is equal to the value of the DB_BLOCK_BUFFERS parameter.
Oracle Database 10 g : SQL Fundamentals II D - Program Global Area Components A Program Global Area (PGA) is a memory region that contains data and control information for a server process. It is a nonshared memory created by Oracle when a server process is started. Access to it is exclusive to that server process, and is read and written only by the Oracle server code acting on behalf of it. The PGA memory allocated by each server process attached to an Oracle instance is referred to as the aggregated PGA memory allocated by the instance. In a dedicated server configuration, the PGA of the server includes the following components: Sort area: Used for any sorts that may be required to process the SQL statement Session information: Includes user privileges and performance statistics for the session Cursor state: Indicates the stage in the processing of the SQL statements that are currently used by the session Stack space: Contains other session variables The PGA is allocated when a process is created and deallocated when the process is terminated.
Oracle Database 10 g : SQL Fundamentals II D - DML Processing Steps A data manipulation language (DML) statement requires only two phases of processing: Parse is the same as the parse phase used for processing a query. Execute requires additional processing to make data changes. DML Execute Phase To execute a DML statement: If the data and rollback blocks are not already in the buffer cache, the server process reads them from the data files into the buffer cache. The server process places locks on the rows that are to be modified. In the redo log buffer, the server process records the changes to be made to the rollback and data. The rollback block changes record the values of the data before it is modified. The rollback block is used to store the before image of the data, so that the DML statements can be rolled back if necessary. The data block changes record the new values of the data.
Oracle Database 10 g : SQL Fundamentals II D - DML Processing Steps (continued) DML Execute Phase (continued) The server process records the before image to the rollback block and updates the data block. Both of these changes are done in the database buffer cache. Any changed blocks in the buffer cache are marked as dirty buffers; that is, buffers that are not the same as the corresponding blocks on the disk. The processing of a DELETE or INSERT command uses similar steps. The before image for a DELETE contains the column values in the deleted row, and the before image of an INSERT contains the row location information. Because the changes made to the blocks are only recorded in memory structures and are not written immediately to disk, a computer failure that causes the loss of the SGA can also lose these changes.
Oracle Database 10 g : SQL Fundamentals II D - Redo Log Buffer Characteristics The server process records most of the changes made to data file blocks in the redo log buffer, which is a part of the SGA. The redo log buffer has the following characteristics: Its size in bytes is defined by the LOG_BUFFER parameter. It records the block that is changed, the location of the change, and the new value in a redo entry. A redo entry makes no distinction between the type of block that is changed; it only records which bytes are changed in the block. The redo log buffer is used sequentially, and changes made by one transaction may be interleaved with changes made by other transactions. It is a circular buffer that is reused after it is filled, but only after all the old redo entries are recorded in the redo log files.
Oracle Database 10 g : SQL Fundamentals II D - Rollback Segment Before making a change, the server process saves the old data value in a rollback segment. This before image is used to: Undo the changes if the transaction is rolled back Provide read consistency by ensuring that other transactions do not see uncommitted changes made by the DML statement Recover the database to a consistent state in case of failures Rollback segments, such as tables and indexes, exist in data files, and rollback blocks are brought into the database buffer cache as required. Rollback segments are created by the DBA. Changes to rollback segments are recorded in the redo log buffer.
Oracle Database 10 g : SQL Fundamentals II D - Fast COMMIT The Oracle server uses a fast commit mechanism that guarantees that the committed changes can be recovered in case of instance failure. System Change Number Whenever a transaction commits, the Oracle server assigns a commit system change number (SCN) to the transaction. The SCN is monotonically incremented and is unique within the database. It is used by the Oracle server as an internal time stamp to synchronize data and to provide read consistency when data is retrieved from the data files. Using the SCN enables the Oracle server to perform consistency checks without depending on the date and time of the operating system. Steps in Processing COMMIT s When a COMMIT is issued, the following steps are performed: The server process places a commit record, along with the SCN, in the redo log buffer. LGWR performs a contiguous write of all the redo log buffer entries up to and including the commit record to the redo log files. After this point, the Oracle server can guarantee that the changes will not be lost even if there is an instance failure.
Oracle Database 10 g : SQL Fundamentals II D - Fast COMMIT (continued) Steps in Processing COMMIT s (continued) The user is informed that the COMMIT is complete. The server process records information to indicate that the transaction is complete and that resource locks can be released. Flushing of the dirty buffers to the data file is performed independently by DBW0 and can occur either before or after the commit. Advantages of the Fast COMMIT The fast commit mechanism ensures data recovery by writing changes to the redo log buffer instead of the data files. It has the following advantages: Sequential writes to the log files are faster than writing to different blocks in the data file. Only the minimal information that is necessary to record changes is written to the log files, whereas writing to the data files would require whole blocks of data to be written. If multiple transactions request to commit at the same time, the instance piggybacks redo log records into a single write. Unless the redo log buffer is particularly full, only one synchronous write is required per transaction. If piggybacking occurs, there can be less than one synchronous write per transaction. Because the redo log buffer may be flushed before the COMMIT , the size of the transaction does not affect the amount of time needed for an actual COMMIT operation. Note: Rolling back a transaction does not trigger LGWR to write to disk. The Oracle server always rolls back uncommitted changes when recovering from failures. If there is a failure after a rollback, before the rollback entries are recorded on disk, the absence of a commit record is sufficient to ensure that the changes made by the transaction are rolled back.
Oracle Database 10 g : SQL Fundamentals II D - Summary Oracle Database Files The Oracle database includes the following files: Control files: Contain information required to verify the integrity of the database, including the names of the other files in the database (The control files are usually mirrored.) Data files: Contain the data in the database, including tables, indexes, rollback segments, and temporary segments Online redo logs: Contain the changes made to the data files (Online redo logs are used for recovery and are usually mirrored.) Other files commonly used with the database include: Parameter file: Defines the characteristics of an Oracle instance Password file: Authenticates privileged database users Archived redo logs: Are backups of the online redo logs
Oracle Database 10 g : SQL Fundamentals II D - Summary (continued) SGA Memory Structures The System Global Area (SGA) has three primary structures: Shared pool: Stores the most recently executed SQL statements and the most recently used data from the data dictionary Database buffer cache: Stores the most recently used data Redo log buffer: Records changes made to the database using the instance Background Processes A production Oracle instance includes the following processes: Database writer ( DBW0 ): Writes changed data to the data files Log writer ( LGWR ): Records changes to the data files in the online redo log files System monitor ( SMON ): Checks for consistency and initiates recovery of the database when the database is opened Process monitor ( PMON ): Cleans up the resources if one of the processes fails Checkpoint process ( CKPT ): Updates the database status information after a checkpoint Archiver ( ARC0 ): Backs up the online redo log to ensure recovery after a media failure (This process is optional, but is usually included in a production instance.) Depending on its configuration, the instance may also include other processes. SQL Statement Processing Steps The steps used to process a SQL statement include: Parse: Compiles the SQL statement Execute: Identifies selected rows or applies DML changes to the data Fetch: Returns the rows queried by a SELECT statement