【正文】
?Used by Application Continuity ?Can be used independently of Application Continuity 4. Enforce Oute 1. Work Request 2. DB Calls 12c ORACLE Database 3. Errors 4. Reliable Commit Oute Copyright 169。 2023, Oracle and/or its affiliates. All rights reserved. 19 Phases in Application Continuity 1Capture 2Reconnect 3Replay ? Demarcates database request ? Holds original calls with binds validation ? Manages queues ? Checks request has replay enabled ? Handles timeouts ? Creates a new connection ? Validates target database ? Uses Transaction Guard to enforce last mit ? Replays held calls ? Continues replay, if user visible results match, based on validations ? Continues request Copyright 169。 2023, Oracle and/or its affiliates. All rights reserved. 27 Side Effects When Replay is enabled, some calls may be repeated. Apps may need to use disableReplay() API to prevent this: ? Autonomous transactions ? UTL_HTTP , UTL_URL ? UTL_FILE, UTL_FILE_TRANSFER files operations ? UTL_SMPT, UTL_TCP, UTL_MAIL sending messages ? DBMS_PIPE, RPCs to external sources ? DBMS_ALERT or other notifications Copyright 169。 2023, Oracle and/or its affiliates. All rights reserved. 31 Copyright 169。 If owned, ALTER SEQUENCE.. [sequence object] [KEEP|NOKEEP]。 2023, Oracle and/or its affiliates. All rights reserved. 23 Exclusions Global Request Target Database ? Do not use default database service ? Excludes XA ? For Java, deprecated concrete classes ? Restricted calls – Alter System – Alter Database ? Not supported for Active Data Guard with read/write database links ? Does not support: – Logical Standby – Golden Gate Copyright 169。 2023, Oracle and/or its affiliates. All rights reserved. 15 ? On Service ? COMMIT_OUTCOME ? Values – TRUE and FALSE ? Default – FALSE ? Applies to new sessions ? RETENTION_TIMEOUT ? Units – seconds ? Default – 24 hours (86400) ? Maximum value – 30 days (