1 PACKAGE dbms_app_cont_prvt AS
2
3 ------------
4 -- OVERVIEW
5 --
6 -- This package is an internal package for applicaton continuity.
7 --
8
9 ----------------------------
10 -- PROCEDURES AND FUNCTIONS
11 --
12
13 FUNCTION partition_exists(part_id NUMBER) RETURN NUMBER;
14 -- Determines if a partition in the transaction history table exists.
15
16 ----------------------------
17 -- 11.2.0.3 SELECT ONLY PROCEDURES AND FUNCTIONS
18 --
19
20 procedure monitor_txn;
21 -- Enables the monitoring of transactions in the server
22
23 procedure prepare_replay(client_ltxid IN RAW,
24 attempting_replay IN BOOLEAN,
25 commit_on_success IN BOOLEAN,
26 call_fncode IN BINARY_INTEGER,
27 sql_text IN VARCHAR2,
28 committed OUT BOOLEAN,
29 embedded OUT BOOLEAN);
30 --
31 -- Asks server to check status of last action and prepare for replay.
32 --
33 -- If necessary -- if the named call could have committed -- then
34 -- forces the outcome of a transaction (see force_outcome).
35 --
36 -- Input parameter(s):
37 -- client_ltxid - LTXID from the client driver.
38 -- attempting_replay - client is attempting replay. If false, just
39 -- checking the ltxid
40 -- commit_on_success - last call submitted with OCI_COMMIT_ON_SUCCES
41 -- call_fncode - O* function call (see opidef.h) for last call
42 -- sql text - SQL text if last call was SQL execute
43 --
44 -- Output parameter(s):
45 -- committed - Transaction has been committed
46 -- embedded - Transaction commit was embedded
47 --
48 -- Exceptions:
49 -- - SERVER_AHEAD, the server is ahead, so the transaction is an
50 -- old transaction and must have already been
51 -- committed.
52 -- - CLIENT_AHEAD, the client is ahead of the server. This can only
53 -- happen if the server has been flashbacked or the
54 -- ltxid is corrupted. In any way, the outcome
55 -- cannot be determined.
56 -- - ERROR, the outcome cannot be determined. During processing an
57 -- error happened.
58 -- error
59 -- Error code raised during the execution of force_outcome.
60 --
61
62 procedure begin_replay;
63 -- Enables the replay mode in the server. While in replay mode, no
64 -- transactions can be either started or committed.
65
66 procedure end_replay;
67 -- Disables the replay mode.
68
69 END dbms_app_cont_prvt;
[Home] [Help]