Merge branch 'main' into dependabot/pip/cloud-infrastructure/ai-infra-gpu/ai-infrastructure/rag-langchain-vllm-mistral/files/langchain-community-0.2.5

Author: AlexanderHodicke

ai-and-app-modernisation/app-integration-and-automation/shared-assets/README.md

@@ -19,6 +19,24 @@ This section contains various examples related to Application Integration: demo
 
 ## Demos
 
+- [Setting Up OAuth and Calling Oracle Integration APIs: A Step-by-Step Guide](https://youtu.be/UrptzZbycm4?si=opv0_wc5F7SV86nx)
+
+    - In this demo video, we provide a step-by-step guide to setting up OAuth and calling Oracle Integration APIs. We'll walk you through registering your application, obtaining client credentials, and generating OAuth tokens. 
+
+    Using Postman, we'll demonstrate how to make authenticated API calls to Oracle Integration, ensuring secure data retrieval and manipulation.
+
+    Parameters referred in video:
+
+    Grant Type : Client Credentials/Authorization Code
+    Access Token URL : https://[idcs url]/oauth2/v1/token
+    Client ID: xxxxx
+    Client Secret: xxxxxx
+    Scope: https://xxxxx:opc:resource:consumer::all
+    Auth URL* : https://[idcs url]/oauth2/v1/authorize
+    Redirect URL* : https://[oic url]/icsapis/agent/oauth/callback
+
+    "*" parameters are required for Authorization Code flow only.
+
 - [Oracle Process Automation - File Manager Component](https://youtu.be/ZnGPteYE_tA?si=KAFsgffX1ZsRkfer)
 
     - The File Manager component allows end users to upload one or more documents using a process form to an external system.This video demonstrate the use of the File Manager

cloud-infrastructure/multicloud/google-interconnect/README.md

@@ -6,14 +6,19 @@ The new Oracle Interconnect for Google Cloud now enables flexible and simplified
 
 Enterprises can seamlessly connect Google Cloud services, such as analytics and AI, to Oracle Cloud services, such as Exadata and Autonomous Database. For organizations seeking to optimize and elevate their cloud infrastructure capabilities and commercial calculus, such a native multicloud model offers the best-of-both-clouds customer experience that encompasses a unified and interoperable technical and commercial stack.
 
-Reviewed: 13.06.2024
+Reviewed: 02.07.2024
 
 # Useful Links
 
 ## General
 
 - [Oracle and Google Cloud Announce a Groundbreaking Multicloud Partnership](https://www.oracle.com/news/announcement/oracle-and-google-cloud-announce-groundbreaking-multicloud-partnership-2024-06-11/)
 - [Step-by-Step Guide: Interconnecting Oracle Cloud Infrastructure and Google Cloud ](https://blogs.oracle.com/cloud-infrastructure/post/interconnecting-oci-google-cloud)
+- [Access to Google Cloud Platform](https://docs.oracle.com/en-us/iaas/Content/Network/Concepts/access-to-google-cloud-platform.htm)
+- [Oracle Interconnect for Google Cloud](https://www.oracle.com/cloud/google/interconnect/)
+- [Oracle and Google Cloud Partnership FAQ ](https://www.oracle.com/cloud/google/interconnect/faq/)
+- [Announcing the Oracle Interconnect for Google Cloud](https://blogs.oracle.com/cloud-infrastructure/post/announcing-oracle-interconnect-google-cloud)
+
 
 
 # License

data-platform/core-converged-db/real-application-testing/db-replay/README.md

@@ -0,0 +1,48 @@
+# Database Replay (DB Replay)
+
+Database Replay can be used to capture a real workload on the production system and replay it on a test system with the exact timing, concurrency, and transaction characteristics of the original workload. This enables you to test the effects of a system change without affecting the production system. Database Replay supports workload capture on a system running Oracle Database 10g Release 2 and newer releases. Because the database workload capture is stored in a platform-independent format, you can capture a workload on one OS platform, e.g. Windows, and replay on a different one, e.g. Linux. Keep in mind it should be used only within the Oracle Database. Other external components like application server, middleware, or client software cannot be considered when testing with Real Application Testing. Either the graphical interface via Enterprise Manager Cloud Control or the command-line API can be used.  
+
+
+Reviewed: 02.07.2024
+
+# When to use this asset?
+
+To learn about Database Replay using the command line API.  
+
+# How to use this asset?
+
+See the README in the files folder.
+
+Please note: Database Replay for Autonomous Database (ADB) works differently. It can be used e.g. to replay a recorded (captured) workload from On-Premises or cloud installations in an Autonomous Database. 
+For more details on the usage in ADB refer to the [documentation](https://docs.oracle.com/en/cloud/paas/autonomous-database/serverless/adbsb/autonomous-real-application-testing.html#GUID-EB8F065E-5FBB-480D-BAF6-5A0446740073) or the posting [Autonomous Database Replay](https://blogs.oracle.com/coretec/post/adb-database-replay).
+ 
+# Useful Links
+
+## Documentation
+
+- [Testing Guide](https://docs.oracle.com/en/database/oracle/oracle-database/19/ratug/database-replay.html#GUID-C5CAF3E6-0F1C-4BD6-BC03-F71744AD600E)
+- [PL/SQL Packages and Types Reference - DBMS_WORKLOAD_CAPTURE](https://docs.oracle.com/en/database/oracle/oracle-database/19/arpls/DBMS_WORKLOAD_CAPTURE.html#GUID-77C6507C-3DE6-4FB4-B180-530BEB840BE8)
+- [PL/SQL Packages and Types Reference - DBMS_WORKLOAD_REPLAY](https://docs.oracle.com/en/database/oracle/oracle-database/19/arpls/DBMS_WORKLOAD_REPLAY.html#GUID-FE03A123-2257-41FF-BA90-AD0114DC1A4F)
+- [Test Workloads with Oracle Real Application Testing - Autonomous Database](https://docs.oracle.com/en/cloud/paas/autonomous-database/serverless/adbsb/autonomous-real-application-testing.html#GUID-EB8F065E-5FBB-480D-BAF6-5A0446740073)
+- [PL/SQL Packages and Types Reference for Autonomous Database - DBMS_CLOUD_ADMIN](https://docs.oracle.com/en/cloud/paas/autonomous-database/serverless/adbsb/dbms-cloud-admin.html#GUID-D76B229E-781E-45C0-9F14-CAF30F9E6E3B)
+
+
+## LiveLabs
+
+- [Real Application Testing: SQL Performance Analyzer and Database Replay](https://apexapps.oracle.com/pls/apex/r/dbpm/livelabs/view-workshop?wid=858&clear=RR,180&session=112790027738609)
+
+
+# Team Publication
+
+- [Testing with Oracle Database Replay](https://blogs.oracle.com/coretec/post/testing-with-oracle-database-replay)
+- [Real Application Testing Database Replay Demo](https://blogs.oracle.com/coretec/post/rat-demo)
+- [Autonomous Database Replay](https://blogs.oracle.com/coretec/post/adb-database-replay)
+
+
+# License
+
+Copyright (c) 2024 Oracle and/or its affiliates.
+
+Licensed under the Universal Permissive License (UPL), Version 1.0.
+
+See [LICENSE](https://github.com/oracle-devrel/technology-engineering/blob/main/LICENSE) for more details.

data-platform/core-converged-db/real-application-testing/db-replay/files/README.md

@@ -0,0 +1,71 @@
+## Database Replay Scripts
+
+This folder provides SQL scripts for the usage of Database Replay (DB Replay). Please adapt and change the scripts to your conditions. 
+
+## Scripts
+
+You can find an example workflow, the executed scripts, and a detailed description in the posting [Testing with Oracle Database Replay](https://blogs.oracle.com/coretec/post/testing-with-oracle-database-replay).
+
+Keep in mind that appropriate permissions are required to
+- Create directory objects
+- Use DBMS_WORKLOAD_CAPTURE and DBMS_WORKLOAD_REPLAY packages
+- Act as a replay client user (e.g. wrc someuser/YOUR_PASSWORD or wrc USER=someuser PASSWORD=YOUR_PASSWORD) //PLEASE CHANGE YOUR_PASSWORD  TO A REAL PASSWORD!
+ 
+In the documentation [DBMS_WORKLOAD_CAPTURE Security Model]( https://docs.oracle.com/en/database/oracle/oracle-database/19/arpls/DBMS_WORKLOAD_CAPTURE.html#GUID-77C6507C-3DE6-4FB4-B180-530BEB840BE8) you will get the detailed information about it.
+
+Before starting a workload capture, you should have a strategy in place to restore the database on the test system. Before a workload can be replayed, the logical state of the application data on the replay system should be similar to that of the capture system when replay begins.
+
+In general, please follow the suggested script order.
+
+### 1) Capture the Database Workload in the production environment 
+
+Before starting, check the [Workload Capture restrictions](https://docs.oracle.com/en/database/oracle/oracle-database/19/ratug/capturing-a-database-workload.html#GUID-4A1995F1-78F9-4080-8DFC-1E3EBCB3F4B8).
+
+- Provide an empty database directory 
+- (optional) Use filters: capturefilter.sql 
+- Start capture: capturestart.sql
+- (optional) Stop capture: capturestop.sql
+- Check capture results: capturemon.sql
+- Export AWR: exportawr.sql
+- Capture report: capturereport.sql
+
+(Note: it may be useful to generate an additional AWR spanning the capture period.) 
+
+### 2) Preprocess the (captured) Database Workload on the test environment  
+
+- Preprocess: processcapture.sql
+- (optional) Check duration: processmonitor.sql
+
+### 3) Replay the Database Workload on the test environment
+
+- (optional) Add filters: replayfilter.sql and replayfilterset.sql 
+- Initialize the replay: replayinitialize.sql
+- (optional) Map connections: remapping.sql
+- (optional) Use filters: replayusefilterset.sql 
+- Prepare the replay: replayprepare.sql
+
+- Workload Replay clients: Number estimation and start
+
+Estimate the number of Workload Replay Clients (WRCs) (e.g. $wrc mode=calibrate replaydir=../replay/..) 
+
+Start WRCs in the background on the replay machine or a separate machine (e.g. $wrc username/password mode=replay replaydir=../replay/...)
+
+- Start the replay: replaystart.sql
+- Monitor the replay: replaymon.sql
+
+### 4) Generate Reports
+ 
+- (optional) Divergence reports: divergences.sql, divergence_detail.sql
+- Replay report: replayreport.sql
+- Import capture AWRs: importAWR.sql
+- ComparePeriod report: comparereplayreport.sql 
+
+(Note: it may be useful to generate an additional AWR spanning the replay period.)      
+
+# License
+
+Copyright (c) 2024 Oracle and/or its affiliates.
+
+Licensed under the Universal Permissive License (UPL), Version 1.0.
+
+See [LICENSE](https://github.com/oracle-devrel/technology-engineering/blob/main/LICENSE) for more details.

data-platform/core-converged-db/real-application-testing/db-replay/files/capturefilter.sql

@@ -0,0 +1,21 @@
+-- This procedure adds a filter to capture a subset of the workload.
+
+/* possible filter types: INSTANCE_NUMBER, USER, MODULE, ACTION, PROGRAM, SERVICE, PDB_NAME 
+
+examples: 
+
+exec dbms_workload_capture.add_filter('ORACLE MANAGEMENT SERVICE (DEFAULT)', 'Program', 'OMS');
+exec dbms_workload_capture.add_filter('ORACLE MANAGEMENT AGENT (DEFAULT)', 'Program', 'emagent%');
+exec dbms_workload_capture.add_filter('U_DBSNMP', 'User', 'DBSNMP');
+*/
+
+-- example 
+execute dbms_workload_capture.add_filter(fname=>'&FILTERNAME', fattribute=>'&filtertype', fvalue=>'&filtervalue');
+
+-- Monitor filters
+set linesize window
+select * from dba_workload_filters;
+
+/* if you need to delete the filters
+execute DBMS_WORKLOAD_CAPTURE.DELETE_FILTER(fname=>'&Filtername');
+*/

data-platform/core-converged-db/real-application-testing/db-replay/files/capturemon.sql

@@ -0,0 +1,6 @@
+-- DBA_WORKLOAD_CAPTURES displays all the workload captures that have been performed in the current database.
+
+set linesize window
+select id, name, status, errors, awr_exported, duration_secs, filters_used, dbtime_total, dbtime, dbtime_total,
+user_calls_total, user_calls, user_calls_unreplayable, transactions, transactions_total, capture_size/1024/1024 
+from dba_workload_captures where name like '&name%';

data-platform/core-converged-db/real-application-testing/db-replay/files/capturereport.sql

@@ -0,0 +1,14 @@
+-- This function generates a report on the workload capture.
+
+
+-- Find report_id 
+select id, name, status, start_time, end_time, awr_exported, connects, user_calls, dir_path 
+from dba_workload_captures where id = (select max(id) from dba_workload_captures);
+
+-- Generate capture report
+spool capturereport.txt
+
+set pagesize 0 long 30000000 longchunksize 1000
+select dbms_workload_capture.report(&report_id, 'TEXT') from dual;
+
+spool off

data-platform/core-converged-db/real-application-testing/db-replay/files/capturestart.sql

@@ -0,0 +1,36 @@
+-- This procedure initiates workload capture on all instances.
+/*
+If you used filters, please review the usage of EXCLUDE and INCLUDE in the start_capture procedure.
+Definition:
+If EXCLUDE, no user request to the database is captured, except for the part of the workload defined by the filters. 
+In this case, all the filters specified using the ADD_FILTER procedures are treated as INCLUSION filters, determining 
+the workload that is captured. 
+Default is INCLUDE.
+
+-- example with user defined filter criteria 
+-- execute dbms_workload_capture.start_capture (name=>'&capturename', dir=>'&dir', default_action=>'EXCLUDE');
+
+other options:
+
+-- with STS (not available for RAC)
+-- execute dbms_workload_capture.start_capture (name=>'&capturename', dir=>'&dir', capture_sts=>TRUE);
+
+-- with duration 
+-- execute dbms_workload_capture.start_capture (name=>'&capturename', dir=>'&dir', duration=>&secs);
+ 
+The optional plsql_mode parameter determines how PL/SQL is handled by DB Replay during capture and replays.
+These two values can be set for the plsql_mode parameter:
+top_level: Only top-level PL/SQL calls are captured and replayed, which is how DB Replay handled PL/SQL prior 
+to Oracle Database 12c Release 2 (12.2.0.1). This is the default value.
+
+Extended: Both top-level PL/SQL calls and SQL called from PL/SQL are captured. When the workload is replayed, 
+the replay can be done at either top-level or extended level.
+*/
+
+
+-- Example EXCLUDE and PL/SQL mode extended
+-- execute dbms_workload_capture.start_capture (name=>'&capturename', dir=>'&dir', plsql_mode => 'extended', default_action=>'EXCLUDE');
+
+
+-- Example INCLUDE (default) and the PL/SQL mode extended
+execute dbms_workload_capture.start_capture (name=>'&capturename', dir=>'&dir', plsql_mode => 'extended');

data-platform/core-converged-db/real-application-testing/db-replay/files/capturestop.sql

@@ -0,0 +1,12 @@
+-- This procedure signals all connected sessions to stop the workload capture and stops future requests to the database from being captured.
+
+execute dbms_workload_capture.finish_capture();
+
+/*
+By default, FINISH_CAPTURE waits for 30 seconds to receive a successful acknowledgement from all sessions in the database cluster before timing out.
+All sessions that either were in the middle of executing a user request or received a new user request, while FINISH_CAPTURE
+was waiting for acknowledgements, flush their buffers and send back their acknowledgement to FINISH_CAPTURE.
+If a database session remains idle (waiting for the next user request) throughout the duration of FINISH_CAPTURE, the session might have unflushed capture buffers and does not send it's acknowledgement to FINISH_CAPTURE. To avoid this, do not have sessions that remain idle (waiting for the next user request) while invoking FINISH_CAPTURE. Either close the database session(s) before running FINISH_CAPTURE or send new database requests to those sessions during FINISH_CAPTURE.
+*/
+~
+

data-platform/core-converged-db/real-application-testing/db-replay/files/comparereplayreport.sql

@@ -0,0 +1,23 @@
+-- This procedure generates a report comparing a replay to its capture or to another replay of the same capture.
+
+-- find replay_id
+select id, awr_begin_snap, awr_end_snap 
+from dba_workload_replays where name like '&replayname%';
+
+
+-- replay_id2 of the workload replay whose report is requested 
+-- If this is NULL, then the comparison is done with the capture
+
+variable result clob
+
+begin
+  dbms_workload_replay.compare_period_report(replay_id1=>&replayid,replay_id2=>null,format=>'HTML',result=>:result);
+end;
+/
+
+set heading off
+set long 1000000
+set pagesize 0
+spool comparereport.html rep
+print result
+spool off