;
-```
-
-The following table describes the different conditions that might trigger an `action`:
-
-| **Condition** | **Description** |
-| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `NOT FOUND` | The server returns a `NOT FOUND` condition when it encounters a `SELECT` that returns no rows, or when a `FETCH` reaches the end of a result set. |
-| `SQLERROR` | The server returns an `SQLERROR` condition when it encounters a serious error returned by an SQL statement. |
-| `SQLWARNING` | The server returns an `SQLWARNING` condition when it encounters a non-fatal warning returned by an SQL statement. |
-
-The following table describes the actions that result from a client encountering a `condition`:
-
-| **Action** | **Description** |
-| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `CALL function [([args])]` | Instructs the client application to call the named `function`. |
-| `CONTINUE` | Instructs the client application to proceed to the next statement. |
-| `DO BREAK` | Instructs the client application to a C break statement. A break statement may appear in a `loop` or a `switch` statement. If executed, the break statement terminate the `loop` or the `switch` statement. |
-| `DO CONTINUE` | Instructs the client application to emit a C `continue` statement. A `continue` statement may only exist within a loop, and if executed, will cause the flow of control to return to the top of the loop. |
-| `DO function ([args])` | Instructs the client application to call the named `function`. |
-| `GOTO label` or `GO TO label` | Instructs the client application to proceed to the statement that contains the `label`. |
-| `SQLPRINT` | Instructs the client application to print a message to standard error. |
-| `STOP` | Instructs the client application to stop execution. |
-
-The following code fragment prints a message if the client application encounters a warning, and aborts the application if it encounters an error:
-
-```text
-EXEC SQL WHENEVER SQLWARNING SQLPRINT;
-EXEC SQL WHENEVER SQLERROR STOP;
-```
-
-Include the following code to specify that a client should continue processing after warning a user of a problem:
-
-```text
-EXEC SQL WHENEVER SQLWARNING SQLPRINT;
-```
-
-Include the following code to call a function if a query returns no rows, or when a cursor reaches the end of a result set:
-
-```text
-EXEC SQL WHENEVER NOT FOUND CALL error_handler(__LINE__);
-```
diff --git a/product_docs/docs/epas/12/ecpgplus_guide/index.mdx b/product_docs/docs/epas/12/ecpgplus_guide/index.mdx
deleted file mode 100644
index 89311ae0fa3..00000000000
--- a/product_docs/docs/epas/12/ecpgplus_guide/index.mdx
+++ /dev/null
@@ -1,30 +0,0 @@
----
-navTitle: ECPGPlus
-title: "ECPGPlus Guide"
-
-legacyRedirectsGenerated:
- # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
- - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/13/index.html"
- - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/13/conclusion.html"
- - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/13/introduction.html"
----
-
-EnterpriseDB has enhanced ECPG (the PostgreSQL pre-compiler) to create ECPGPlus. ECPGPlus allows you to include Pro\*C compatible embedded SQL commands in C applications when connected to an EDB Postgres Advanced Server (Advanced Server) database. When you use ECPGPlus to compile an application, the SQL code is syntax-checked and translated into C.
-
-ECPGPlus supports:
-
-- Oracle Dynamic SQL – Method 4 (ODS-M4).
-- Pro\*C compatible anonymous blocks.
-- A `CALL` statement compatible with Oracle databases.
-
-As part of ECPGPlus's Pro\*C compatibility, you do not need to include the `BEGIN DECLARE SECTION` and `END DECLARE SECTION` directives.
-
-**PostgreSQL Compatibility**
-
-While most ECPGPlus statements will work with community PostgreSQL, the `CALL` statement, and the `EXECUTE…END EXEC` statement work only when the client application is connected to EDB Postgres Advanced Server.
-
-
-
-introduction overview using_embedded_sql using_descriptors building_executing_dynamic_sql_statements error_handling reference conclusion
-
-
diff --git a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/01_dbms_alert.mdx b/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/01_dbms_alert.mdx
deleted file mode 100644
index 44bca71f7dc..00000000000
--- a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/01_dbms_alert.mdx
+++ /dev/null
@@ -1,395 +0,0 @@
----
-title: "DBMS_ALERT"
-
-legacyRedirectsGenerated:
- # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
- - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-built-in-package-guide/13/dbms_alert.html"
----
-
-The `DBMS_ALERT` package provides the capability to register for, send, and receive alerts. The following table lists the supported procedures:
-
-| Function/Procedure | Return Type | Description |
-| ----------------------------------------------------- | ----------- | --------------------------------------------------- |
-| `REGISTER(name)` | n/a | Register to be able to receive alerts named, `name` |
-| `REMOVE(name)` | n/a | Remove registration for the alert named, `name` |
-| `REMOVEALL` | n/a | Remove registration for all alerts. |
-| `SIGNAL(name, message)` | n/a | Signals the alert named, `name`, with `message` |
-| `WAITANY(name OUT, message OUT, status OUT, timeout)` | n/a | Wait for any registered alert to occur. |
-| `WAITONE(name, message OUT, status OUT, timeout)` | n/a | Wait for the specified alert, `name`, to occur. |
-
-Advanced Server's implementation of `DBMS_ALERT` is a partial implementation when compared to Oracle's version. Only those functions and procedures listed in the table above are supported.
-
-Advanced Server allows a maximum of `500` concurrent alerts. You can use the `dbms_alert.max_alerts` GUC variable (located in the `postgresql.conf` file) to specify the maximum number of concurrent alerts allowed on a system.
-
-To set a value for the `dbms_alert.max_alerts` variable, open the `postgresql.conf` file (located by default in `/opt/PostgresPlus/12AS/data`) with your choice of editor, and edit the `dbms_alert.max_alerts` parameter as shown:
-
-```text
-dbms_alert.max_alerts = alert_count
-```
-
-`alert_count`
-
-`alert_count` specifies the maximum number of concurrent alerts. By default, the value of `dbms_alert.max_alerts` is `100`. To disable this feature, set `dbms_alert.max_alerts` to `0`.
-
-For the `dbms_alert.max_alerts` GUC to function correctly, the `custom_variable_classes` parameter must contain `dbms_alerts`:
-
-```text
-custom_variable_classes = 'dbms_alert, …'
-```
-
-After editing the `postgresql.conf` file parameters, you must restart the server for the changes to take effect.
-
-## REGISTER
-
-The `REGISTER` procedure enables the current session to be notified of the specified alert.
-
-```text
-REGISTER( VARCHAR2)
-```
-
-**Parameters**
-
-`name`
-
- Name of the alert to be registered.
-
-**Examples**
-
-The following anonymous block registers for an alert named, `alert_test`, then waits for the signal.
-
-```text
-DECLARE
- v_name VARCHAR2(30) := 'alert_test';
- v_msg VARCHAR2(80);
- v_status INTEGER;
- v_timeout NUMBER(3) := 120;
-BEGIN
- DBMS_ALERT.REGISTER(v_name);
- DBMS_OUTPUT.PUT_LINE('Registered for alert ' || v_name);
- DBMS_OUTPUT.PUT_LINE('Waiting for signal...');
- DBMS_ALERT.WAITONE(v_name,v_msg,v_status,v_timeout);
- DBMS_OUTPUT.PUT_LINE('Alert name : ' || v_name);
- DBMS_OUTPUT.PUT_LINE('Alert msg : ' || v_msg);
- DBMS_OUTPUT.PUT_LINE('Alert status : ' || v_status);
- DBMS_OUTPUT.PUT_LINE('Alert timeout: ' || v_timeout || ' seconds');
- DBMS_ALERT.REMOVE(v_name);
-END;
-
-Registered for alert alert_test
-Waiting for signal...
-```
-
-## REMOVE
-
-The `REMOVE` procedure unregisters the session for the named alert.
-
-```text
-REMOVE( VARCHAR2)
-```
-
-**Parameters**
-
-`name`
-
- Name of the alert to be unregistered.
-
-## REMOVEALL
-
-The `REMOVEALL` procedure unregisters the session for all alerts.
-
-```text
-REMOVEALL
-```
-
-## SIGNAL
-
-The `SIGNAL` procedure signals the occurrence of the named alert.
-
-```text
-SIGNAL( VARCHAR2, VARCHAR2)
-```
-
-**Parameters**
-
-`name`
-
- Name of the alert.
-
-`message`
-
- Information to pass with this alert.
-
-**Examples**
-
-The following anonymous block signals an alert for `alert_test`.
-
-```text
-DECLARE
- v_name VARCHAR2(30) := 'alert_test';
-BEGIN
- DBMS_ALERT.SIGNAL(v_name,'This is the message from ' || v_name);
- DBMS_OUTPUT.PUT_LINE('Issued alert for ' || v_name);
-END;
-Issued alert for alert_test
-```
-
-## WAITANY
-
-The `WAITANY` procedure waits for any of the registered alerts to occur.
-
-```text
-WAITANY( OUT VARCHAR2, OUT VARCHAR2,
- OUT INTEGER, NUMBER)
-```
-
-**Parameters**
-
-`name`
-
- Variable receiving the name of the alert.
-
-`message`
-
- Variable receiving the message sent by the `SIGNAL` procedure.
-
-`status`
-
- Status code returned by the operation. Possible values are: 0 – alert occurred; 1 – timeout occurred.
-
-`timeout`
-
- Time to wait for an alert in seconds.
-
-**Examples**
-
-The following anonymous block uses the `WAITANY` procedure to receive an alert named, `alert_test` or `any_alert`:
-
-```text
-DECLARE
- v_name VARCHAR2(30);
- v_msg VARCHAR2(80);
- v_status INTEGER;
- v_timeout NUMBER(3) := 120;
-BEGIN
- DBMS_ALERT.REGISTER('alert_test');
- DBMS_ALERT.REGISTER('any_alert');
- DBMS_OUTPUT.PUT_LINE('Registered for alert alert_test and any_alert');
- DBMS_OUTPUT.PUT_LINE('Waiting for signal...');
- DBMS_ALERT.WAITANY(v_name,v_msg,v_status,v_timeout);
- DBMS_OUTPUT.PUT_LINE('Alert name : ' || v_name);
- DBMS_OUTPUT.PUT_LINE('Alert msg : ' || v_msg);
- DBMS_OUTPUT.PUT_LINE('Alert status : ' || v_status);
- DBMS_OUTPUT.PUT_LINE('Alert timeout: ' || v_timeout || ' seconds');
- DBMS_ALERT.REMOVEALL;
-END;
-
-Registered for alert alert_test and any_alert
-Waiting for signal...
-```
-
-An anonymous block in a second session issues a signal for `any_alert`:
-
-```text
-DECLARE
- v_name VARCHAR2(30) := 'any_alert';
-BEGIN
- DBMS_ALERT.SIGNAL(v_name,'This is the message from ' || v_name);
- DBMS_OUTPUT.PUT_LINE('Issued alert for ' || v_name);
-END;
-
-Issued alert for any_alert
-```
-
-Control returns to the first anonymous block and the remainder of the code is executed:
-
-```text
-Registered for alert alert_test and any_alert
-Waiting for signal...
-Alert name : any_alert
-Alert msg : This is the message from any_alert
-Alert status : 0
-Alert timeout: 120 seconds
-```
-
-## WAITONE
-
-The `WAITONE` procedure waits for the specified registered alert to occur.
-
-```text
-WAITONE( VARCHAR2, OUT VARCHAR2,
- OUT INTEGER, NUMBER)
-```
-
-**Parameters**
-
-`name`
-
- Name of the alert.
-
-`message`
-
- Variable receiving the message sent by the `SIGNAL` procedure.
-
-`status`
-
- Status code returned by the operation. Possible values are: 0 – alert occurred; 1 – timeout occurred.
-
-`timeout`
-
- Time to wait for an alert in seconds.
-
-**Examples**
-
-The following anonymous block is similar to the one used in the `WAITANY` example except the `WAITONE` procedure is used to receive the alert named, `alert_test`.
-
-```text
-DECLARE
- v_name VARCHAR2(30) := 'alert_test';
- v_msg VARCHAR2(80);
- v_status INTEGER;
- v_timeout NUMBER(3) := 120;
-BEGIN
- DBMS_ALERT.REGISTER(v_name);
- DBMS_OUTPUT.PUT_LINE('Registered for alert ' || v_name);
- DBMS_OUTPUT.PUT_LINE('Waiting for signal...');
- DBMS_ALERT.WAITONE(v_name,v_msg,v_status,v_timeout);
- DBMS_OUTPUT.PUT_LINE('Alert name : ' || v_name);
- DBMS_OUTPUT.PUT_LINE('Alert msg : ' || v_msg);
- DBMS_OUTPUT.PUT_LINE('Alert status : ' || v_status);
- DBMS_OUTPUT.PUT_LINE('Alert timeout: ' || v_timeout || ' seconds');
- DBMS_ALERT.REMOVE(v_name);
-END;
-
-Registered for alert alert_test
-Waiting for signal...
-```
-
-Signal sent for `alert_test` sent by an anonymous block in a second session:
-
-```text
-DECLARE
- v_name VARCHAR2(30) := 'alert_test';
-BEGIN
- DBMS_ALERT.SIGNAL(v_name,'This is the message from ' || v_name);
- DBMS_OUTPUT.PUT_LINE('Issued alert for ' || v_name);
-END;
-
-Issued alert for alert_test
-```
-
-First session is alerted, control returns to the anonymous block, and the remainder of the code is executed:
-
-```text
-Registered for alert alert_test
-Waiting for signal...
-Alert name : alert_test
-Alert msg : This is the message from alert_test
-Alert status : 0
-Alert timeout: 120 seconds
-```
-
-## Comprehensive Example
-
-The following example uses two triggers to send alerts when the `dept` table or the `emp` table is changed. An anonymous block listens for these alerts and displays messages when an alert is received.
-
-The following are the triggers on the `dept` and `emp` tables:
-
-```text
-CREATE OR REPLACE TRIGGER dept_alert_trig
- AFTER INSERT OR UPDATE OR DELETE ON dept
-DECLARE
- v_action VARCHAR2(25);
-BEGIN
- IF INSERTING THEN
- v_action := ' added department(s) ';
- ELSIF UPDATING THEN
- v_action := ' updated department(s) ';
- ELSIF DELETING THEN
- v_action := ' deleted department(s) ';
- END IF;
- DBMS_ALERT.SIGNAL('dept_alert',USER || v_action || 'on ' ||
- SYSDATE);
-END;
-
-CREATE OR REPLACE TRIGGER emp_alert_trig
- AFTER INSERT OR UPDATE OR DELETE ON emp
-DECLARE
- v_action VARCHAR2(25);
-BEGIN
- IF INSERTING THEN
- v_action := ' added employee(s) ';
- ELSIF UPDATING THEN
- v_action := ' updated employee(s) ';
- ELSIF DELETING THEN
- v_action := ' deleted employee(s) ';
- END IF;
- DBMS_ALERT.SIGNAL('emp_alert',USER || v_action || 'on ' ||
- SYSDATE);
-END;
-```
-
-The following anonymous block is executed in a session while updates to the `dept` and `emp` tables occur in other sessions:
-
-```text
-DECLARE
- v_dept_alert VARCHAR2(30) := 'dept_alert';
- v_emp_alert VARCHAR2(30) := 'emp_alert';
- v_name VARCHAR2(30);
- v_msg VARCHAR2(80);
- v_status INTEGER;
- v_timeout NUMBER(3) := 60;
-BEGIN
- DBMS_ALERT.REGISTER(v_dept_alert);
- DBMS_ALERT.REGISTER(v_emp_alert);
- DBMS_OUTPUT.PUT_LINE('Registered for alerts dept_alert and emp_alert');
- DBMS_OUTPUT.PUT_LINE('Waiting for signal...');
- LOOP
- DBMS_ALERT.WAITANY(v_name,v_msg,v_status,v_timeout);
- EXIT WHEN v_status != 0;
- DBMS_OUTPUT.PUT_LINE('Alert name : ' || v_name);
- DBMS_OUTPUT.PUT_LINE('Alert msg : ' || v_msg);
- DBMS_OUTPUT.PUT_LINE('Alert status : ' || v_status);
- DBMS_OUTPUT.PUT_LINE('------------------------------------' ||
- '-------------------------');
- END LOOP;
- DBMS_OUTPUT.PUT_LINE('Alert status : ' || v_status);
- DBMS_ALERT.REMOVEALL;
-END;
-
-Registered for alerts dept_alert and emp_alert
-Waiting for signal...
-```
-
-The following changes are made by user, mary:
-
-```text
-INSERT INTO dept VALUES (50,'FINANCE','CHICAGO');
-INSERT INTO emp (empno,ename,deptno) VALUES (9001,'JONES',50);
-INSERT INTO emp (empno,ename,deptno) VALUES (9002,'ALICE',50);
-```
-
-The following change is made by user, john:
-
-```text
-INSERT INTO dept VALUES (60,'HR','LOS ANGELES');
-```
-
-The following is the output displayed by the anonymous block receiving the signals from the triggers:
-
-```text
-Registered for alerts dept_alert and emp_alert
-Waiting for signal...
-Alert name : dept_alert
-Alert msg : mary added department(s) on 25-OCT-07 16:41:01
-Alert status : 0
--------------------------------------------------------------
-Alert name : emp_alert
-Alert msg : mary added employee(s) on 25-OCT-07 16:41:02
-Alert status : 0
--------------------------------------------------------------
-Alert name : dept_alert
-Alert msg : john added department(s) on 25-OCT-07 16:41:22
-Alert status : 0
--------------------------------------------------------------
-Alert status : 1
-```
diff --git a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/01_enqueue.mdx b/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/01_enqueue.mdx
deleted file mode 100644
index 7487f87c635..00000000000
--- a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/01_enqueue.mdx
+++ /dev/null
@@ -1,120 +0,0 @@
----
-title: "ENQUEUE"
-
-legacyRedirectsGenerated:
- # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
- - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-built-in-package-guide/13/enqueue.html"
----
-
-The `ENQUEUE` procedure adds an entry to a queue. The signature is:
-
-```text
-ENQUEUE(
- IN VARCHAR2,
- IN DBMS_AQ.ENQUEUE_OPTIONS_T,
- IN DBMS_AQ.MESSAGE_PROPERTIES_T,
- IN ,
- OUT RAW)
-```
-
-**Parameters**
-
-`queue_name`
-
- The name (optionally schema-qualified) of an existing queue. If you omit the schema name, the server will use the schema specified in the `SEARCH_PATH`. Please note that unlike Oracle, unquoted identifiers are converted to lower case before storing. To include special characters or use a case-sensitive name, enclose the name in double quotes.
-
- For detailed information about creating a queue, see `DBMS_AQADM.CREATE_QUEUE`.
-
-`enqueue_options`
-
- `enqueue_options` is a value of the type, `enqueue_options_t`:
-
-```text
-DBMS_AQ.ENQUEUE_OPTIONS_T IS RECORD(
- visibility BINARY_INTEGER DEFAULT ON_COMMIT,
- relative_msgid RAW(16) DEFAULT NULL,
- sequence_deviation BINARY INTEGER DEFAULT NULL,
- transformation VARCHAR2(61) DEFAULT NULL,
- delivery_mode PLS_INTEGER NOT NULL DEFAULT PERSISTENT);
-```
-
-Currently, the only supported parameter values for `enqueue_options_t` are:
-
-| `visibility` | `ON_COMMIT`. |
-| -------------------- | ------------ |
-| `delivery_mode` | `PERSISTENT` |
-| `sequence_deviation` | `NULL` |
-| `transformation` | `NULL` |
-| `relative_msgid` | `NULL` |
-
-`message_properties`
-
- `message_properties` is a value of the type, `message_properties_t`:
-
-```text
-message_properties_t IS RECORD(
- priority INTEGER,
- delay INTEGER,
- expiration INTEGER,
- correlation CHARACTER VARYING(128) COLLATE pg_catalog.”C”,
- attempts INTEGER,
- recipient_list “AQ$_RECIPIENT_LIST_T”,
- exception_queue CHARACTER VARYING(61) COLLATE pg_catalog.”C”,
- enqueue_time TIMESTAMP WITHOUT TIME ZONE,
- state INTEGER,
- original_msgid BYTEA,
- transaction_group CHARACTER VARYING(30) COLLATE pg_catalog.”C”,
- delivery_mode INTEGER
-DBMS_AQ.PERSISTENT);
-```
-
-The supported values for `message_properties_t` are:
-
-| | |
-| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `priority` | If the queue table definition includes a `sort_list` that references `priority`, this parameter affects the order that messages are dequeued. A lower value indicates a higher dequeue priority. |
-| `delay` | Specify the number of seconds that will pass before a message is available for dequeueing or `NO_DELAY`. |
-| `expiration` | Use the expiration parameter to specify the number of seconds until a message expires. |
-| `correlation` | Use correlation to specify a message that will be associated with the entry; the default is `NULL`. |
-| `attempts` | This is a system-maintained value that specifies the number of attempts to dequeue the message. |
-| `recipient_list` | This parameter is not supported. |
-| `exception_queue` | Use the `exception_queue` parameter to specify the name of an exception queue to which a message will be moved if it expires or is dequeued by a transaction that rolls back too many times. |
-| `enqueue_time` | `enqueue_time` is the time the record was added to the queue; this value is provided by the system. |
-| `state` | This parameter is maintained by DBMS_AQ; state can be:
`DBMS_AQ.WAITING` – the delay has not been reached.
`DBMS_AQ.READY` – the queue entry is ready for processing.
`DBMS_AQ.PROCESSED` – the queue entry has been processed.
`DBMS_AQ.EXPIRED` – the queue entry has been moved to the exception queue. |
-| `original_msgid` | This parameter is accepted for compatibility and ignored. |
-| `transaction_group` | This parameter is accepted for compatibility and ignored. |
-| `delivery_mode` | This parameter is not supported; specify a value of `DBMS_AQ.PERSISTENT`. |
-
-`payload`
-
- Use the `payload` parameter to provide the data that will be associated with the queue entry. The payload type must match the type specified when creating the corresponding queue table (see `DBMS_AQADM.CREATE_QUEUE_TABLE`).
-
-`msgid`
-
- Use the `msgid` parameter to retrieve a unique (system-generated) message identifier.
-
-**Example**
-
-The following anonymous block calls `DBMS_AQ.ENQUEUE`, adding a message to a queue named `work_order`:
-
-```text
-DECLARE
-
- enqueue_options DBMS_AQ.ENQUEUE_OPTIONS_T;
- message_properties DBMS_AQ.MESSAGE_PROPERTIES_T;
- message_handle raw(16);
- payload work_order;
-
-BEGIN
-
- payload := work_order('Smith', 'system upgrade');
-
-DBMS_AQ.ENQUEUE(
- queue_name => 'work_order',
- enqueue_options => enqueue_options,
- message_properties => message_properties,
- payload => payload,
- msgid => message_handle
- );
- END;
-```
diff --git a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/02_dequeue.mdx b/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/02_dequeue.mdx
deleted file mode 100644
index 4a45c6c09e5..00000000000
--- a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/02_dequeue.mdx
+++ /dev/null
@@ -1,132 +0,0 @@
----
-title: "DEQUEUE"
-
-legacyRedirectsGenerated:
- # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
- - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-built-in-package-guide/13/dequeue.html"
----
-
-The `DEQUEUE` procedure dequeues a message. The signature is:
-
-```text
-DEQUEUE(
- IN VARCHAR2,
- IN DBMS_AQ.DEQUEUE_OPTIONS_T,
- OUT DBMS_AQ.MESSAGE_PROPERTIES_T,
- OUT ,
- OUT RAW)
-```
-
-**Parameters**
-
-`queue_name`
-
- The name (optionally schema-qualified) of an existing queue. If you omit the schema name, the server will use the schema specified in the `SEARCH_PATH`. Please note that unlike Oracle, unquoted identifiers are converted to lower case before storing. To include special characters or use a case-sensitive name, enclose the name in double quotes.
-
- For detailed information about creating a queue, see `DBMS_AQADM.CREATE_QUEUE`.
-
-`dequeue_options` is a value of the type, `dequeue_options_t`:
-
-```text
-DEQUEUE_OPTIONS_T IS RECORD(
- consumer_name CHARACTER VARYING(30),
- dequeue_mode INTEGER,
- navigation INTEGER,
- visibility INTEGER,
- wait INTEGER,
- msgid BYTEA,
- correlation CHARACTER VARYING(128),
- deq_condition CHARACTER VARYING(4000),
- transformation CHARACTER VARYING(61),
- delivery_mode INTEGER);
-```
-
-Currently, the supported parameter values for `dequeue_options_t` are:
-
-| | |
-| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `consumer_name` | Must be `NULL`. |
-| `dequeue_mode` | The locking behavior of the dequeue operation. Must be either:
`DBMS_AQ.BROWSE` – Read the message without obtaining a lock.
`DBMS_AQ.LOCKED` – Read the message after acquiring a lock.
`DBMS_AQ.REMOVE` – Read the message before deleting the message.
`DBMS_AQ.REMOVE_NODATA` – Read the message, but do not delete the message. |
-| `navigation` | Identifies the message that will be retrieved. Must be either:
`FIRST_MESSAGE` – The first message within the queue that matches the search term.
`NEXT_MESSAGE` – The next message that is available that matches the first term. |
-| `visibility` | Must be `ON_COMMIT` – if you roll back the current transaction the dequeued item will remain in the queue. |
-| `wait` | Must be a number larger than 0, or:
`DBMS_AQ.FOREVER` – Wait indefinitely.
`DBMS_AQ.NO_WAIT` – Do not wait. |
-| `msgid` | The message ID of the message that will be dequeued. |
-| `correlation` | Accepted for compatibility, and ignored. |
-| `deq_condition` | A `VARCHAR2` expression that evaluates to a `BOOLEAN` value indicating if the message should be dequeued. |
-| `transformation` | Accepted for compatibility, and ignored. |
-| `delivery_mode` | Must be `PERSISTENT`; buffered messages are not supported at this time. |
-
-`message_properties` is a value of the type, `message_properties_t`:
-
-```text
-message_properties_t IS RECORD(
- priority INTEGER,
- delay INTEGER,
- expiration INTEGER,
- correlation CHARACTER VARYING(128) COLLATE pg_catalog.”C”,
- attempts INTEGER,
- recipient_list “AQ$_RECIPIENT_LIST_T”,
- exception_queue CHARACTER VARYING(61) COLLATE pg_catalog.”C”,
- enqueue_time TIMESTAMP WITHOUT TIME ZONE,
- state INTEGER,
- original_msgid BYTEA,
- transaction_group CHARACTER VARYING(30) COLLATE pg_catalog.”C”,
- delivery_mode INTEGER
-DBMS_AQ.PERSISTENT);
-```
-
-The supported values for `message_properties_t` are:
-
-| | |
-| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `priority` | If the queue table definition includes a `sort_list` that references `priority`, this parameter affects the order that messages are dequeued. A lower value indicates a higher dequeue priority. |
-| `delay` | Specify the number of seconds that will pass before a message is available for dequeueing or `NO_DELAY`. |
-| `expiration` | Use the expiration parameter to specify the number of seconds until a message expires. |
-| `correlation` | Use correlation to specify a message that will be associated with the entry; the default is `NULL`. |
-| `attempts` | This is a system-maintained value that specifies the number of attempts to dequeue the message. |
-| `recipient_list` | This parameter is not supported. |
-| `exception_queue` | Use the `exception_queue` parameter to specify the name of an exception queue to which a message will be moved if it expires or is dequeued by a transaction that rolls back too many times. |
-| `enqueue_time` | `enqueue_time` is the time the record was added to the queue; this value is provided by the system. |
-| `state` | This parameter is maintained by DBMS_AQ; state can be:
`DBMS_AQ.WAITING` – the delay has not been reached.
`DBMS_AQ.READY` – the queue entry is ready for processing.
`DBMS_AQ.PROCESSED` – the queue entry has been processed.
`DBMS_AQ.EXPIRED` – the queue entry has been moved to the exception queue. |
-| `original_msgid` | This parameter is accepted for compatibility and ignored. |
-| `transaction_group` | This parameter is accepted for compatibility and ignored. |
-| `delivery_mode` | This parameter is not supported; specify a value of `DBMS_AQ.PERSISTENT`. |
-
-`payload`
-
- Use the `payload` parameter to retrieve the payload of a message with a dequeue operation. The payload type must match the type specified when creating the queue table.
-
-`msgid`
-
- Use the `msgid` parameter to retrieve a unique message identifier.
-
-**Example**
-
-The following anonymous block calls `DBMS_AQ.DEQUEUE`, retrieving a message from the queue and a payload:
-
-```text
-DECLARE
-
- dequeue_options DBMS_AQ.DEQUEUE_OPTIONS_T;
- message_properties DBMS_AQ.MESSAGE_PROPERTIES_T;
- message_handle raw(16);
- payload work_order;
-
-BEGIN
- dequeue_options.dequeue_mode := DBMS_AQ.BROWSE;
-
- DBMS_AQ.DEQUEUE(
- queue_name => 'work_queue',
- dequeue_options => dequeue_options,
- message_properties => message_properties,
- payload => payload,
- msgid => message_handle
- );
-
- DBMS_OUTPUT.PUT_LINE(
- 'The next work order is [' || payload.subject || '].'
- );
-END;
-```
-
-The payload is displayed by `DBMS_OUTPUT.PUT_LINE`.
diff --git a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/03_register.mdx b/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/03_register.mdx
deleted file mode 100644
index ac2bcd2df1d..00000000000
--- a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/03_register.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: "REGISTER"
-
-legacyRedirectsGenerated:
- # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
- - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-built-in-package-guide/13/register.html"
----
-
-Use the `REGISTER` procedure to register an email address, procedure or URL that will be notified when an item is enqueued or dequeued. The signature is:
-
-```text
-REGISTER(
- IN SYS.AQ$_REG_INFO_LIST,
- IN NUMBER)
-```
-
-**Parameters**
-
-`reg_list` is a list of type `AQ$_REG_INFO_LIST`; that provides information about each subscription that you would like to register. Each entry within the list is of the type `AQ$_REG_INFO`, and may contain:
-
-
-
-
-
-| Attribute | Type | Description |
-| ----------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `name` | VARCHAR2 (128) | The (optionally schema-qualified) name of the subscription. |
-| `namespace` | NUMERIC | The only supported value is `DBMS_AQ.NAMESPACE_AQ (0)` |
-| `callback` | VARCHAR2 (4000) | Describes the action that will be performed upon notification. Currently, only calls to PL/SQL procedures are supported. The call should take the form:
`plsql://schema.procedure`
Where:
schema specifies the schema in which the procedure resides.
procedure specifies the name of the procedure that will be notified. |
-| `context` | RAW (16) | Any user-defined value required by the procedure. |
-
-`count`
-
- `count` is the number of entries in `reg_list`.
-
-**Example**
-
-The following anonymous block calls `DBMS_AQ.REGISTER`, registering procedures that will be notified when an item is added to or removed from a queue. A set of attributes (of `sys.aq$_reg_info` type) is provided for each subscription identified in the `DECLARE` section:
-
-```text
-DECLARE
- subscription1 sys.aq$_reg_info;
- subscription2 sys.aq$_reg_info;
- subscription3 sys.aq$_reg_info;
- subscriptionlist sys.aq$_reg_info_list;
-BEGIN
- subscription1 := sys.aq$_reg_info('q', DBMS_AQ.NAMESPACE_AQ,
-'plsql://assign_worker?PR=0',HEXTORAW('FFFF'));
- subscription2 := sys.aq$_reg_info('q', DBMS_AQ.NAMESPACE_AQ,
-'plsql://add_to_history?PR=1',HEXTORAW('FFFF'));
- subscription3 := sys.aq$_reg_info('q', DBMS_AQ.NAMESPACE_AQ,
-'plsql://reserve_parts?PR=2',HEXTORAW('FFFF'));
-
- subscriptionlist := sys.aq$_reg_info_list(subscription1,
-subscription2, subscription3);
- dbms_aq.register(subscriptionlist, 3);
- commit;
- END;
- /
-```
-
-The `subscriptionlist` is of type `sys.aq$_reg_info_list`, and contains the previously described `sys.aq$_reg_info` objects. The list name and an object count are passed to `dbms_aq.register`.
diff --git a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/04_unregister.mdx b/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/04_unregister.mdx
deleted file mode 100644
index 762b412c003..00000000000
--- a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/04_unregister.mdx
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: "UNREGISTER"
-
-legacyRedirectsGenerated:
- # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
- - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-built-in-package-guide/13/unregister.html"
----
-
-Use the `UNREGISTER` procedure to turn off notifications related to enqueueing and dequeueing. The signature is:
-
-```text
-UNREGISTER(
- IN SYS.AQ$_REG_INFO_LIST,
- IN NUMBER)
-```
-
-**Parameter**
-
-`reg_list`
-
-`reg_list` is a list of type `AQ$_REG_INFO_LIST`; that provides information about each subscription that you would like to register. Each entry within the list is of the type `AQ$_REG_INFO`, and may contain:
-
-
-
-
-
-| Attribute | Type | Description |
-| ----------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `name` | VARCHAR2 (128) | The (optionally schema-qualified) name of the subscription. |
-| `namespace` | NUMERIC | The only supported value is `DBMS_AQ.NAMESPACE_AQ (0)` |
-| `callback` | VARCHAR2 (4000) | Describes the action that will be performed upon notification. Currently, only calls to PL/SQL procedures are supported. The call should take the form:
`plsql://schema.procedure`
Where:
schema specifies the schema in which the procedure resides.
procedure specifies the name of the procedure that will be notified. |
-| `context` | RAW (16) | Any user-defined value required by the procedure. |
-
-`count`
-
- `count` is the number of entries in `reg_list`.
-
-**Example**
-
-The following anonymous block calls `DBMS_AQ.UNREGISTER`, disabling the notifications specified in the example for `DBMS_AQ.REGISTER`:
-
-```text
-DECLARE
- subscription1 sys.aq$_reg_info;
- subscription2 sys.aq$_reg_info;
- subscription3 sys.aq$_reg_info;
- subscriptionlist sys.aq$_reg_info_list;
-BEGIN
- subscription1 := sys.aq$_reg_info('q', DBMS_AQ.NAMESPACE_AQ,
-'plsql://assign_worker?PR=0',HEXTORAW('FFFF'));
- subscription2 := sys.aq$_reg_info('q', DBMS_AQ.NAMESPACE_AQ,
-'plsql://add_to_history?PR=1',HEXTORAW('FFFF'));
- subscription3 := sys.aq$_reg_info('q', DBMS_AQ.NAMESPACE_AQ,
-'plsql://reserve_parts?PR=2',HEXTORAW('FFFF'));
-
- subscriptionlist := sys.aq$_reg_info_list(subscription1,
-subscription2, subscription3);
- dbms_aq.unregister(subscriptionlist, 3);
- commit;
- END;
- /
-```
-
-The `subscriptionlist` is of type `sys.aq$_reg_info_list`, and contains the previously described `sys.aq$_reg_info` objects. The list name and an object count are passed to `dbms_aq.unregister`.
diff --git a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/01_decrypt.mdx b/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/01_decrypt.mdx
deleted file mode 100644
index 2a822fc109b..00000000000
--- a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/01_decrypt.mdx
+++ /dev/null
@@ -1,98 +0,0 @@
----
-title: "DECRYPT"
-
-legacyRedirectsGenerated:
- # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
- - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-built-in-package-guide/13/decrypt.html"
----
-
-The `DECRYPT` function or procedure decrypts data using a user-specified cipher algorithm, key and optional initialization vector. The signature of the `DECRYPT` function is:
-
-```text
-DECRYPT
- ( IN RAW, IN INTEGER, IN RAW, IN RAW
- DEFAULT NULL) RETURN RAW
-```
-
-The signature of the `DECRYPT` procedure is:
-
-```text
-DECRYPT
- ( INOUT BLOB, IN BLOB, IN INTEGER, IN RAW,
- IN RAW DEFAULT NULL)
-```
-
-or
-
-```text
-DECRYPT
- ( INOUT CLOB, IN CLOB, IN INTEGER, IN RAW,
- IN RAW DEFAULT NULL)
-```
-
-When invoked as a procedure, `DECRYPT` returns `BLOB` or `CLOB` data to a user-specified `BLOB`.
-
-**Parameters**
-
-`dst`
-
- `dst` specifies the name of a `BLOB` to which the output of the `DECRYPT` procedure will be written. The `DECRYPT` procedure will overwrite any existing data currently in `dst`.
-
-`src`
-
- `src` specifies the source data that will be decrypted. If you are invoking `DECRYPT` as a function, specify `RAW` data; if invoking `DECRYPT` as a procedure, specify `BLOB` or `CLOB` data.
-
-`typ`
-
- `typ` specifies the block cipher type and any modifiers. This should match the type specified when the `src` was encrypted. Advanced Server supports the following block cipher algorithms, modifiers and cipher suites:
-
-| **Block Cipher Algorithms** | |
-| ---------------------------------- | ----------------------------------------------------------- |
-| `ENCRYPT_DES` | `CONSTANT INTEGER := 1;` |
-| `ENCRYPT_3DES` | `CONSTANT INTEGER := 3;` |
-| `ENCRYPT_AES` | `CONSTANT INTEGER := 4;` |
-| `ENCRYPT_AES128` | `CONSTANT INTEGER := 6;` |
-| **Block Cipher Modifiers** | |
-| `CHAIN_CBC` | `CONSTANT INTEGER := 256;` |
-| `CHAIN_ECB` | `CONSTANT INTEGER := 768;` |
-| **Block Cipher Padding Modifiers** | |
-| `PAD_PKCS5` | `CONSTANT INTEGER := 4096;` |
-| `PAD_NONE` | `CONSTANT INTEGER := 8192;` |
-| **Block Cipher Suites** | |
-| `DES_CBC_PKCS5` | `CONSTANT INTEGER := ENCRYPT_DES + CHAIN_CBC + PAD_PKCS5;` |
-| `DES3_CBC_PKCS5` | `CONSTANT INTEGER := ENCRYPT_3DES + CHAIN_CBC + PAD_PKCS5;` |
-| `AES_CBC_PKCS5` | `CONSTANT INTEGER := ENCRYPT_AES + CHAIN_CBC + PAD_PKCS5;` |
-
-`key`
-
- `key` specifies the user-defined decryption key. This should match the key specified when the `src` was encrypted.
-
-`iv`
-
- `iv` (optional) specifies an initialization vector. If an initialization vector was specified when the `src` was encrypted, you must specify an initialization vector when decrypting the `src`. The default is `NULL`.
-
-**Examples**
-
-The following example uses the `DBMS_CRYPTO.DECRYPT` function to decrypt an encrypted password retrieved from the `passwords` table:
-
-```text
-CREATE TABLE passwords
-(
- principal VARCHAR2(90) PRIMARY KEY, -- username
- ciphertext RAW(9) -- encrypted password
-);
-
-CREATE FUNCTION get_password(username VARCHAR2) RETURN RAW AS
- typ INTEGER := DBMS_CRYPTO.DES_CBC_PKCS5;
- key RAW(128) := 'my secret key';
- iv RAW(100) := 'my initialization vector';
- password RAW(2048);
-BEGIN
-
- SELECT ciphertext INTO password FROM passwords WHERE principal = username;
-
- RETURN dbms_crypto.decrypt(password, typ, key, iv);
-END;
-```
-
-Note that when calling `DECRYPT`, you must pass the same cipher type, key value and initialization vector that was used when `ENCRYPTING` the target.
diff --git a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/02_encrypt.mdx b/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/02_encrypt.mdx
deleted file mode 100644
index 6152bf1f3f3..00000000000
--- a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/02_encrypt.mdx
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: "ENCRYPT"
-
-legacyRedirectsGenerated:
- # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
- - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-built-in-package-guide/13/encrypt.html"
----
-
-The `ENCRYPT` function or procedure uses a user-specified algorithm, key, and optional initialization vector to encrypt `RAW`, `BLOB` or `CLOB` data. The signature of the `ENCRYPT` function is:
-
-```text
-ENCRYPT
- ( IN RAW, IN INTEGER, IN RAW,
- IN RAW DEFAULT NULL) RETURN RAW
-```
-
-The signature of the `ENCRYPT` procedure is:
-
-```text
-ENCRYPT
- ( INOUT BLOB, IN BLOB, IN INTEGER, IN RAW,
- IN RAW DEFAULT NULL)
-```
-
-or
-
-```text
-ENCRYPT
- ( INOUT BLOB, IN CLOB, IN INTEGER, IN RAW,
- IN RAW DEFAULT NULL)
-```
-
-When invoked as a procedure, `ENCRYPT` returns `BLOB` or `CLOB` data to a user-specified `BLOB`.
-
-**Parameters**
-
-`dst`
-
- `dst` specifies the name of a `BLOB` to which the output of the `ENCRYPT` procedure will be written. The `ENCRYPT` procedure will overwrite any existing data currently in `dst`.
-
-`src`
-
- `src` specifies the source data that will be encrypted. If you are invoking `ENCRYPT` as a function, specify `RAW` data; if invoking `ENCRYPT` as a procedure, specify `BLOB` or `CLOB` data.
-
-`typ`
-
- `typ` specifies the block cipher type that will be used by `ENCRYPT`, and any modifiers. Advanced Server supports the block cipher algorithms, modifiers and cipher suites listed below:
-
-| **Block Cipher Algorithms** | |
-| ---------------------------------- | ----------------------------------------------------------- |
-| `ENCRYPT_DES` | `CONSTANT INTEGER := 1;` |
-| `ENCRYPT_3DES` | `CONSTANT INTEGER := 3;` |
-| `ENCRYPT_AES` | `CONSTANT INTEGER := 4;` |
-| `ENCRYPT_AES128` | `CONSTANT INTEGER := 6;` |
-| **Block Cipher Modifiers** | |
-| `CHAIN_CBC` | `CONSTANT INTEGER := 256;` |
-| `CHAIN_ECB` | `CONSTANT INTEGER := 768;` |
-| **Block Cipher Padding Modifiers** | |
-| `PAD_PKCS5` | `CONSTANT INTEGER := 4096;` |
-| `PAD_NONE` | `CONSTANT INTEGER := 8192;` |
-| **Block Cipher Suites** | |
-| `DES_CBC_PKCS5` | `CONSTANT INTEGER := ENCRYPT_DES + CHAIN_CBC + PAD_PKCS5;` |
-| `DES3_CBC_PKCS5` | `CONSTANT INTEGER := ENCRYPT_3DES + CHAIN_CBC + PAD_PKCS5;` |
-| `AES_CBC_PKCS5` | `CONSTANT INTEGER := ENCRYPT_AES + CHAIN_CBC + PAD_PKCS5;` |
-
-`key`
-
- `key` specifies the encryption key.
-
-`iv`
-
- `iv` (optional) specifies an initialization vector. By default, `iv` is `NULL`.
-
-**Examples**
-
-The following example uses the `DBMS_CRYPTO.DES_CBC_PKCS5` Block Cipher Suite (a pre-defined set of algorithms and modifiers) to encrypt a value retrieved from the `passwords` table:
-
-```text
-CREATE TABLE passwords
-(
- principal VARCHAR2(90) PRIMARY KEY, -- username
- ciphertext RAW(9) -- encrypted password
-);
-CREATE PROCEDURE set_password(username VARCHAR2, cleartext RAW) AS
- typ INTEGER := DBMS_CRYPTO.DES_CBC_PKCS5;
- key RAW(128) := 'my secret key';
- iv RAW(100) := 'my initialization vector';
- encrypted RAW(2048);
-BEGIN
- encrypted := dbms_crypto.encrypt(cleartext, typ, key, iv);
- UPDATE passwords SET ciphertext = encrypted WHERE principal = username;
-END;
-```
-
-`ENCRYPT` uses a key value of `my secret key` and an initialization vector of `my initialization vector` when encrypting the `password`; specify the same key and initialization vector when decrypting the `password`.
diff --git a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/09_dbms_output.mdx b/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/09_dbms_output.mdx
deleted file mode 100644
index 6aae5df5c95..00000000000
--- a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/09_dbms_output.mdx
+++ /dev/null
@@ -1,426 +0,0 @@
----
-title: "DBMS_OUTPUT"
-
-legacyRedirectsGenerated:
- # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
- - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-built-in-package-guide/13/dbms_output.html"
----
-
-The `DBMS_OUTPUT` package provides the capability to send messages (lines of text) to a message buffer, or get messages from the message buffer. A message buffer is local to a single session. Use the `DBMS_PIPE` package to send messages between sessions.
-
-The procedures and functions available in the `DBMS_OUTPUT` package are listed in the following table.
-
-| Function/Procedure | Return Type | Description |
-| --------------------------------------- | ----------- | ---------------------------------------------------------------------------------------------------- |
-| `DISABLE` | n/a | Disable the capability to send and receive messages. |
-| `ENABLE(buffer_size)` | n/a | Enable the capability to send and receive messages. |
-| `GET_LINE(line OUT, status OUT)` | n/a | Get a line from the message buffer. |
-| `GET_LINES(lines OUT, numlines IN OUT)` | n/a | Get multiple lines from the message buffer. |
-| `NEW_LINE` | n/a | Puts an end-of-line character sequence. |
-| `PUT(item)` | n/a | Puts a partial line without an end-of-line character sequence. |
-| `PUT_LINE(item)` | n/a | Puts a complete line with an end-of-line character sequence. |
-| `SERVEROUTPUT(stdout)` | n/a | Direct messages from `PUT, PUT_LINE,` or `NEW_LINE` to either standard output or the message buffer. |
-
-The following table lists the public variables available in the `DBMS_OUTPUT` package.
-
-| **Public Variables** | **Data Type** | **Value** | **Description** |
-| -------------------- | ------------- | --------- | ------------------ |
-| `chararr` | `TABLE` | | For message lines. |
-
-## CHARARR
-
-The `CHARARR` is for storing multiple message lines.
-
-```text
-TYPE chararr IS TABLE OF VARCHAR2(32767) INDEX BY BINARY_INTEGER;
-```
-
-## DISABLE
-
-The `DISABLE` procedure clears out the message buffer. Any messages in the buffer at the time the `DISABLE` procedure is executed will no longer be accessible. Any messages subsequently sent with the `PUT, PUT_LINE,` or `NEW_LINE` procedures are discarded. No error is returned to the sender when the `PUT, PUT_LINE,` or `NEW_LINE` procedures are executed and messages have been disabled.
-
-Use the `ENABLE` procedure or `SERVEROUTPUT(TRUE)` procedure to re-enable the sending and receiving of messages.
-
-```text
-DISABLE
-```
-
-**Examples**
-
-This anonymous block disables the sending and receiving messages in the current session.
-
-```text
-BEGIN
- DBMS_OUTPUT.DISABLE;
-END;
-```
-
-## ENABLE
-
-The `ENABLE` procedure enables the capability to send messages to the message buffer or retrieve messages from the message buffer. Running `SERVEROUTPUT(TRUE)` also implicitly performs the `ENABLE` procedure.
-
-The destination of a message sent with `PUT, PUT_LINE,` or `NEW_LINE` depends upon the state of `SERVEROUTPUT`.
-
-- If the last state of `SERVEROUTPUT` is `TRUE`, the message goes to standard output of the command line.
-- If the last state of `SERVEROUTPUT` is `FALSE`, the message goes to the message buffer.
-
-```text
-ENABLE [ ( INTEGER) ]
-```
-
-**Parameter**
-
-`buffer_size`
-
- Maximum length of the message buffer in bytes. If a `buffer_size` of less than 2000 is specified, the buffer size is set to 2000.
-
-**Examples**
-
-The following anonymous block enables messages. Setting `SERVEROUTPUT(TRUE)` forces them to standard output.
-
-```text
-BEGIN
- DBMS_OUTPUT.ENABLE;
- DBMS_OUTPUT.SERVEROUTPUT(TRUE);
- DBMS_OUTPUT.PUT_LINE('Messages enabled');
-END;
-
-Messages enabled
-```
-
-The same effect could have been achieved by simply using `SERVEROUTPUT(TRUE)`.
-
-```text
-BEGIN
- DBMS_OUTPUT.SERVEROUTPUT(TRUE);
- DBMS_OUTPUT.PUT_LINE('Messages enabled');
-END;
-
-Messages enabled
-```
-
-The following anonymous block enables messages, but setting `SERVEROUTPUT(FALSE)` directs messages to the message buffer.
-
-```text
-BEGIN
- DBMS_OUTPUT.ENABLE;
- DBMS_OUTPUT.SERVEROUTPUT(FALSE);
- DBMS_OUTPUT.PUT_LINE('Message sent to buffer');
-END;
-```
-
-## GET_LINE
-
-The `GET_LINE` procedure provides the capability to retrieve a line of text from the message buffer. Only text that has been terminated by an end-of-line character sequence is retrieved – that is complete lines generated using `PUT_LINE`, or by a series of `PUT` calls followed by a `NEW_LINE` call.
-
-```text
-GET_LINE( OUT VARCHAR2, OUT INTEGER)
-```
-
-**Parameters**
-
-`line`
-
- Variable receiving the line of text from the message buffer.
-
-`status`
-
- 0 if a line was returned from the message buffer, 1 if there was no line to return.
-
-**Examples**
-
-The following anonymous block writes the `emp` table out to the message buffer as a comma-delimited string for each row.
-
-```text
-EXEC DBMS_OUTPUT.SERVEROUTPUT(FALSE);
-
-DECLARE
- v_emprec VARCHAR2(120);
- CURSOR emp_cur IS SELECT * FROM emp ORDER BY empno;
-BEGIN
- DBMS_OUTPUT.ENABLE;
- FOR i IN emp_cur LOOP
- v_emprec := i.empno || ',' || i.ename || ',' || i.job || ',' ||
- NVL(LTRIM(TO_CHAR(i.mgr,'9999')),'') || ',' || i.hiredate ||
- ',' || i.sal || ',' ||
- NVL(LTRIM(TO_CHAR(i.comm,'9990.99')),'') || ',' || i.deptno;
- DBMS_OUTPUT.PUT_LINE(v_emprec);
- END LOOP;
-END;
-```
-
-The following anonymous block reads the message buffer and inserts the messages written by the prior example into a table named `messages`. The rows in `messages` are then displayed.
-
-```text
-CREATE TABLE messages (
- status INTEGER,
- msg VARCHAR2(100)
-);
-
-DECLARE
- v_line VARCHAR2(100);
- v_status INTEGER := 0;
-BEGIN
- DBMS_OUTPUT.GET_LINE(v_line,v_status);
- WHILE v_status = 0 LOOP
- INSERT INTO messages VALUES(v_status, v_line);
- DBMS_OUTPUT.GET_LINE(v_line,v_status);
- END LOOP;
-END;
-
-SELECT msg FROM messages;
-
- msg
------------------------------------------------------------------
- 7369,SMITH,CLERK,7902,17-DEC-80 00:00:00,800.00,,20
- 7499,ALLEN,SALESMAN,7698,20-FEB-81 00:00:00,1600.00,300.00,30
- 7521,WARD,SALESMAN,7698,22-FEB-81 00:00:00,1250.00,500.00,30
- 7566,JONES,MANAGER,7839,02-APR-81 00:00:00,2975.00,,20
- 7654,MARTIN,SALESMAN,7698,28-SEP-81 00:00:00,1250.00,1400.00,30
- 7698,BLAKE,MANAGER,7839,01-MAY-81 00:00:00,2850.00,,30
- 7782,CLARK,MANAGER,7839,09-JUN-81 00:00:00,2450.00,,10
- 7788,SCOTT,ANALYST,7566,19-APR-87 00:00:00,3000.00,,20
- 7839,KING,PRESIDENT,,17-NOV-81 00:00:00,5000.00,,10
- 7844,TURNER,SALESMAN,7698,08-SEP-81 00:00:00,1500.00,0.00,30
- 7876,ADAMS,CLERK,7788,23-MAY-87 00:00:00,1100.00,,20
- 7900,JAMES,CLERK,7698,03-DEC-81 00:00:00,950.00,,30
- 7902,FORD,ANALYST,7566,03-DEC-81 00:00:00,3000.00,,20
- 7934,MILLER,CLERK,7782,23-JAN-82 00:00:00,1300.00,,10
-(14 rows)
-```
-
-## GET_LINES
-
-The `GET_LINES` procedure provides the capability to retrieve one or more lines of text from the message buffer into a collection. Only text that has been terminated by an end-of-line character sequence is retrieved – that is complete lines generated using `PUT_LINE`, or by a series of `PUT` calls followed by a `NEW_LINE` call.
-
-```text
-GET_LINES( OUT CHARARR, IN OUT INTEGER)
-```
-
-**Parameters**
-
-`lines`
-
- Table receiving the lines of text from the message buffer. See `CHARARR` for a description of `lines.`
-
-`numlines IN`
-
- Number of lines to be retrieved from the message buffer.
-
-`numlines OUT`
-
- Actual number of lines retrieved from the message buffer. If the output value of `numlines` is less than the input value, then there are no more lines left in the message buffer.
-
-**Examples**
-
-The following example uses the `GET_LINES` procedure to store all rows from the `emp` table that were placed on the message buffer, into an array.
-
-```text
-EXEC DBMS_OUTPUT.SERVEROUTPUT(FALSE);
-
-DECLARE
- v_emprec VARCHAR2(120);
- CURSOR emp_cur IS SELECT * FROM emp ORDER BY empno;
-BEGIN
- DBMS_OUTPUT.ENABLE;
- FOR i IN emp_cur LOOP
- v_emprec := i.empno || ',' || i.ename || ',' || i.job || ',' ||
- NVL(LTRIM(TO_CHAR(i.mgr,'9999')),'') || ',' || i.hiredate ||
- ',' || i.sal || ',' ||
- NVL(LTRIM(TO_CHAR(i.comm,'9990.99')),'') || ',' || i.deptno;
- DBMS_OUTPUT.PUT_LINE(v_emprec);
- END LOOP;
-END;
-
-DECLARE
- v_lines DBMS_OUTPUT.CHARARR;
- v_numlines INTEGER := 14;
- v_status INTEGER := 0;
-BEGIN
- DBMS_OUTPUT.GET_LINES(v_lines,v_numlines);
- FOR i IN 1..v_numlines LOOP
- INSERT INTO messages VALUES(v_numlines, v_lines(i));
- END LOOP;
-END;
-
-SELECT msg FROM messages;
-
- msg
------------------------------------------------------------------
- 7369,SMITH,CLERK,7902,17-DEC-80 00:00:00,800.00,,20
- 7499,ALLEN,SALESMAN,7698,20-FEB-81 00:00:00,1600.00,300.00,30
- 7521,WARD,SALESMAN,7698,22-FEB-81 00:00:00,1250.00,500.00,30
- 7566,JONES,MANAGER,7839,02-APR-81 00:00:00,2975.00,,20
- 7654,MARTIN,SALESMAN,7698,28-SEP-81 00:00:00,1250.00,1400.00,30
- 7698,BLAKE,MANAGER,7839,01-MAY-81 00:00:00,2850.00,,30
- 7782,CLARK,MANAGER,7839,09-JUN-81 00:00:00,2450.00,,10
- 7788,SCOTT,ANALYST,7566,19-APR-87 00:00:00,3000.00,,20
- 7839,KING,PRESIDENT,,17-NOV-81 00:00:00,5000.00,,10
- 7844,TURNER,SALESMAN,7698,08-SEP-81 00:00:00,1500.00,0.00,30
- 7876,ADAMS,CLERK,7788,23-MAY-87 00:00:00,1100.00,,20
- 7900,JAMES,CLERK,7698,03-DEC-81 00:00:00,950.00,,30
- 7902,FORD,ANALYST,7566,03-DEC-81 00:00:00,3000.00,,20
- 7934,MILLER,CLERK,7782,23-JAN-82 00:00:00,1300.00,,10
-(14 rows)
-```
-
-## NEW_LINE
-
-The `NEW_LINE` procedure writes an end-of-line character sequence in the message buffer.
-
-```text
-NEW_LINE
-```
-
-**Parameter**
-
-The `NEW_LINE` procedure expects no parameters.
-
-## PUT
-
-The `PUT` procedure writes a string to the message buffer. No end-of-line character sequence is written at the end of the string. Use the `NEW_LINE` procedure to add an end-of-line character sequence.
-
-```text
-PUT(- VARCHAR2)
-```
-
-**Parameter**
-
-`item`
-
- Text written to the message buffer.
-
-**Examples**
-
-The following example uses the `PUT` procedure to display a comma-delimited list of employees from the `emp` table.
-
-```text
-DECLARE
- CURSOR emp_cur IS SELECT * FROM emp ORDER BY empno;
-BEGIN
- FOR i IN emp_cur LOOP
- DBMS_OUTPUT.PUT(i.empno);
- DBMS_OUTPUT.PUT(',');
- DBMS_OUTPUT.PUT(i.ename);
- DBMS_OUTPUT.PUT(',');
- DBMS_OUTPUT.PUT(i.job);
- DBMS_OUTPUT.PUT(',');
- DBMS_OUTPUT.PUT(i.mgr);
- DBMS_OUTPUT.PUT(',');
- DBMS_OUTPUT.PUT(i.hiredate);
- DBMS_OUTPUT.PUT(',');
- DBMS_OUTPUT.PUT(i.sal);
- DBMS_OUTPUT.PUT(',');
- DBMS_OUTPUT.PUT(i.comm);
- DBMS_OUTPUT.PUT(',');
- DBMS_OUTPUT.PUT(i.deptno);
- DBMS_OUTPUT.NEW_LINE;
- END LOOP;
-END;
-
-7369,SMITH,CLERK,7902,17-DEC-80 00:00:00,800.00,,20
-7499,ALLEN,SALESMAN,7698,20-FEB-81 00:00:00,1600.00,300.00,30
-7521,WARD,SALESMAN,7698,22-FEB-81 00:00:00,1250.00,500.00,30
-7566,JONES,MANAGER,7839,02-APR-81 00:00:00,2975.00,,20
-7654,MARTIN,SALESMAN,7698,28-SEP-81 00:00:00,1250.00,1400.00,30
-7698,BLAKE,MANAGER,7839,01-MAY-81 00:00:00,2850.00,,30
-7782,CLARK,MANAGER,7839,09-JUN-81 00:00:00,2450.00,,10
-7788,SCOTT,ANALYST,7566,19-APR-87 00:00:00,3000.00,,20
-7839,KING,PRESIDENT,,17-NOV-81 00:00:00,5000.00,,10
-7844,TURNER,SALESMAN,7698,08-SEP-81 00:00:00,1500.00,0.00,30
-7876,ADAMS,CLERK,7788,23-MAY-87 00:00:00,1100.00,,20
-7900,JAMES,CLERK,7698,03-DEC-81 00:00:00,950.00,,30
-7902,FORD,ANALYST,7566,03-DEC-81 00:00:00,3000.00,,20
-7934,MILLER,CLERK,7782,23-JAN-82 00:00:00,1300.00,,10
-```
-
-## PUT_LINE
-
-The `PUT_LINE` procedure writes a single line to the message buffer including an end-of-line character sequence.
-
-```text
-PUT_LINE(
- VARCHAR2)
-```
-
-**Parameter**
-
-`item`
-
- Text to be written to the message buffer.
-
-**Examples**
-
-The following example uses the `PUT_LINE` procedure to display a comma-delimited list of employees from the `emp` table.
-
-```text
-DECLARE
- v_emprec VARCHAR2(120);
- CURSOR emp_cur IS SELECT * FROM emp ORDER BY empno;
-BEGIN
- FOR i IN emp_cur LOOP
- v_emprec := i.empno || ',' || i.ename || ',' || i.job || ',' ||
- NVL(LTRIM(TO_CHAR(i.mgr,'9999')),'') || ',' || i.hiredate ||
- ',' || i.sal || ',' ||
- NVL(LTRIM(TO_CHAR(i.comm,'9990.99')),'') || ',' || i.deptno;
- DBMS_OUTPUT.PUT_LINE(v_emprec);
- END LOOP;
-END;
-
-7369,SMITH,CLERK,7902,17-DEC-80 00:00:00,800.00,,20
-7499,ALLEN,SALESMAN,7698,20-FEB-81 00:00:00,1600.00,300.00,30
-7521,WARD,SALESMAN,7698,22-FEB-81 00:00:00,1250.00,500.00,30
-7566,JONES,MANAGER,7839,02-APR-81 00:00:00,2975.00,,20
-7654,MARTIN,SALESMAN,7698,28-SEP-81 00:00:00,1250.00,1400.00,30
-7698,BLAKE,MANAGER,7839,01-MAY-81 00:00:00,2850.00,,30
-7782,CLARK,MANAGER,7839,09-JUN-81 00:00:00,2450.00,,10
-7788,SCOTT,ANALYST,7566,19-APR-87 00:00:00,3000.00,,20
-7839,KING,PRESIDENT,,17-NOV-81 00:00:00,5000.00,,10
-7844,TURNER,SALESMAN,7698,08-SEP-81 00:00:00,1500.00,0.00,30
-7876,ADAMS,CLERK,7788,23-MAY-87 00:00:00,1100.00,,20
-7900,JAMES,CLERK,7698,03-DEC-81 00:00:00,950.00,,30
-7902,FORD,ANALYST,7566,03-DEC-81 00:00:00,3000.00,,20
-7934,MILLER,CLERK,7782,23-JAN-82 00:00:00,1300.00,,10
-```
-
-## SERVEROUTPUT
-
-The `SERVEROUTPUT` procedure provides the capability to direct messages to standard output of the command line or to the message buffer. Setting `SERVEROUTPUT(TRUE)` also performs an implicit execution of `ENABLE`.
-
-The default setting of `SERVEROUTPUT` is implementation dependent. For example, in Oracle SQL\*Plus, `SERVEROUTPUT(FALSE)` is the default. In PSQL, `SERVEROUTPUT(TRUE)` is the default. Also note that in Oracle SQL\*Plus, this setting is controlled using the SQL\*Plus `SET` command, not by a stored procedure as implemented in Advanced Server.
-
-```text
-SERVEROUTPUT( BOOLEAN)
-```
-
-**Parameter**
-
-`stdout`
-
- Set to `TRUE` if subsequent `PUT, PUT_LINE`, or `NEW_LINE` commands are to send text directly to standard output of the command line. Set to `FALSE` if text is to be sent to the message buffer.
-
-**Examples**
-
-The following anonymous block sends the first message to the command line and the second message to the message buffer.
-
-```text
-BEGIN
- DBMS_OUTPUT.SERVEROUTPUT(TRUE);
- DBMS_OUTPUT.PUT_LINE('This message goes to the command line');
- DBMS_OUTPUT.SERVEROUTPUT(FALSE);
- DBMS_OUTPUT.PUT_LINE('This message goes to the message buffer');
-END;
-
-This message goes to the command line
-```
-
-If within the same session, the following anonymous block is executed, the message stored in the message buffer from the prior example is flushed and displayed on the command line as well as the new message.
-
-```text
-BEGIN
- DBMS_OUTPUT.SERVEROUTPUT(TRUE);
- DBMS_OUTPUT.PUT_LINE('Flush messages from the buffer');
-END;
-
-This message goes to the message buffer
-Flush messages from the buffer
-```
diff --git a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/12_dbms_random.mdx b/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/12_dbms_random.mdx
deleted file mode 100644
index 2a237c8fc29..00000000000
--- a/product_docs/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/12_dbms_random.mdx
+++ /dev/null
@@ -1,235 +0,0 @@
----
-title: "DBMS_RANDOM"
-
-legacyRedirectsGenerated:
- # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
- - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-built-in-package-guide/13/dbms_random.html"
----
-
-The `DBMS_RANDOM` package provides a number of methods to generate random values. The procedures and functions available in the `DBMS_RANDOM` package are listed in the following table.
-
-| Function/Procedure | Return Type | Description |
-| ------------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `INITIALIZE(val)` | n/a | Initializes the `DBMS_RANDOM` package with the specified seed `value`. Deprecated, but supported for backward compatibility. |
-| `NORMAL()` | `NUMBER` | Returns a random `NUMBER`. |
-| `RANDOM` | `INTEGER` | Returns a random `INTEGER` with a value greater than or equal to -2^31 and less than 2^31. Deprecated, but supported for backward compatibility. |
-| `SEED(val)` | n/a | Resets the seed with the specified `value`. |
-| `SEED(val)` | n/a | Resets the seed with the specified `value`. |
-| `STRING(opt, len)` | `VARCHAR2` | Returns a random string. |
-| `TERMINATE` | n/a | `TERMINATE` has no effect. Deprecated, but supported for backward compatibility. |
-| `VALUE` | `NUMBER` | Returns a random number with a value greater than or equal to `0` and less than `1`, with 38 digit precision. |
-| `VALUE(low, high)` | `NUMBER` | Returns a random number with a value greater than or equal to `low` and less than `high`. |
-
-## INITIALIZE
-
-The `INITIALIZE` procedure initializes the `DBMS_RANDOM` package with a seed value. The signature is:
-
-```text
-INITIALIZE( IN INTEGER)
-```
-
-This procedure should be considered deprecated; it is included for backward compatibility only.
-
-**Parameters**
-
-`val`
-
- `val` is the seed value used by the `DBMS_RANDOM` package algorithm.
-
-**Example**
-
-The following code snippet demonstrates a call to the `INITIALIZE` procedure that initializes the `DBMS_RANDOM` package with the seed value, `6475`.
-
-```text
-DBMS_RANDOM.INITIALIZE(6475);
-```
-
-## NORMAL
-
-The `NORMAL` function returns a random number of type `NUMBER`. The signature is:
-
-```text
- NUMBER NORMAL()
-```
-
-**Parameters**
-
-`result`
-
- `result` is a random value of type `NUMBER`.
-
-**Example**
-
-The following code snippet demonstrates a call to the `NORMAL` function:
-
-```text
-x:= DBMS_RANDOM.NORMAL();
-```
-
-## RANDOM
-
-The `RANDOM` function returns a random `INTEGER` value that is greater than or equal to -2 ^31 and less than 2 ^31. The signature is:
-
-```text
- INTEGER RANDOM()
-```
-
-This function should be considered deprecated; it is included for backward compatibility only.
-
-**Parameters**
-
-`result`
-
- `result` is a random value of type `INTEGER`.
-
-**Example**
-
-The following code snippet demonstrates a call to the `RANDOM` function. The call returns a random number:
-
-```text
-x := DBMS_RANDOM.RANDOM();
-```
-
-## SEED
-
-The first form of the `SEED` procedure resets the seed value for the `DBMS_RANDOM` package with an `INTEGER` value. The `SEED` procedure is available in two forms; the signature of the first form is:
-
-```text
-SEED( IN INTEGER)
-```
-
-**Parameters**
-
-`val`
-
- `val` is the seed value used by the `DBMS_RANDOM` package algorithm.
-
-**Example**
-
-The following code snippet demonstrates a call to the `SEED` procedure; the call sets the seed value at `8495`.
-
-```text
-DBMS_RANDOM.SEED(8495);
-```
-
-## SEED
-
-The second form of the `SEED` procedure resets the seed value for the `DBMS_RANDOM` package with a string value. The `SEED` procedure is available in two forms; the signature of the second form is:
-
-```text
-SEED( IN VARCHAR2)
-```
-
-**Parameters**
-
-`val`
-
- `val` is the seed value used by the `DBMS_RANDOM` package algorithm.
-
-**Example**
-
-The following code snippet demonstrates a call to the `SEED` procedure; the call sets the seed value to `abc123`.
-
-```text
-DBMS_RANDOM.SEED('abc123');
-```
-
-## STRING
-
-The `STRING` function returns a random `VARCHAR2` string in a user-specified format. The signature of the `STRING` function is:
-
-```text
- VARCHAR2 STRING( IN CHAR, IN NUMBER)
-```
-
-**Parameters**
-
-`opt`
-
- Formatting option for the returned string. `option` may be:
-
-| **Option** | **Specifies Formatting Option** |
-| ---------- | ------------------------------- |
-| `u` or `U` | Uppercase alpha string |
-| `l` or `L` | Lowercase alpha string |
-| `a` or `A` | Mixed case string |
-| `x` or `X` | Uppercase alpha-numeric string |
-| `p` or `P` | Any printable characters |
-
-`len`
-
- The length of the returned string.
-
-`result`
-
- `result` is a random value of type `VARCHAR2`.
-
-**Example**
-
-The following code snippet demonstrates a call to the `STRING` function; the call returns a random alpha-numeric character string that is 10 characters long.
-
-```text
-x := DBMS_RANDOM.STRING('X', 10);
-```
-
-## TERMINATE
-
-The `TERMINATE` procedure has no effect. The signature is:
-
-```text
-TERMINATE
-```
-
-The `TERMINATE` procedure should be considered deprecated; the procedure is supported for compatibility only.
-
-## VALUE
-
-The `VALUE` function returns a random `NUMBER` that is greater than or equal to 0, and less than 1, with 38 digit precision. The `VALUE` function has two forms; the signature of the first form is:
-
-```text
- NUMBER VALUE()
-```
-
-**Parameters**
-
-`result`
-
- `result` is a random value of type `NUMBER`.
-
-**Example**
-
-The following code snippet demonstrates a call to the `VALUE` function. The call returns a random `NUMBER`:
-
-```text
-x := DBMS_RANDOM.VALUE();
-```
-
-## VALUE
-
-The `VALUE` function returns a random `NUMBER` with a value that is between user-specified boundaries. The `VALUE` function has two forms; the signature of the second form is:
-
-```text
- NUMBER VALUE(