ORA-06519: active autonomous transaction detected and rolled
back
Answer / guest
Cause: Before returning from an autonomous PL/SQL block, all
autonomous transactions started within the block must be
completed (either committed or rolled back). If not, the
active autonomous transaction is implicitly rolled back and
this error is raised.
Action: Ensure that before returning from an autonomous
PL/SQL block, any active autonomous transactions are
explicitly committed or rolled back.
-----------------------------------------------------------------------
06520 through 06529 reserved for Foreign function errors
Please add more information about this Error
Is This Answer Correct ? | 0 Yes | 1 No |
ORA-22323: error table "string"."string" does not exist
RMAN-06170: no controlfile copy found with offline range recid string stamp string datafile string
SQL*Loader-00109: Invalid number of logical records to skip
NNL-00525: Shows or sets the server's default-forwarding status
ORA-02307: cannot alter with REPLACE option a type that is not valid
ORA-07339: spcre: maximum number of semaphore sets exceeded.
TNS-00511: No listener
ORA-28508: invalid value string for Heterogeneous Services initialization parameter string
IMP-00020: long column too large for column buffer size (number)
RMAN-20501: redo logs from parent database incarnation cannot be applied
DGM-16949: "string" was not found
NPL-00311: cannot end constructed ASN.1 encoding, string encoding octets unread