Google it ....

Showing posts with label Got ORA-1013 while running PLSQL. Show all posts
Showing posts with label Got ORA-1013 while running PLSQL. Show all posts

Wednesday, June 5, 2019

Got ORA-1013 while running PLSQL

A big trace file was generated in udump,

The following content was in the trace file:
*** 2019-06-05 16:15:01.725
*** SESSION ID:(1159.11779) 2019-06-05 16:15:01.725
*** CLIENT ID:() 2019-06-05 16:15:01.725
*** SERVICE NAME:(TESTDB) 2019-06-05 16:15:01.725
*** MODULE NAME:(PL/SQL Developer) 2019-06-05 16:15:01.725
*** ACTION NAME:(Script for A.PRC_TEST@TESTDB) 2019-06-05 16:15:01.725
 
*********START PLSQL RUNTIME DUMP************
***Got internal error Exception caught in pl/sql run-time while running PLSQL***
***Got ORA-1013 while running PLSQL***
PACKAGE BODY TESTUSER.A:
library unit=7f877518 line=3 opcode=84 static link=2abba709c568 scope=1
FP=2abba709c718 PC=7b6ce24a Page=0 AP=2abba709c568 ST=2abba709c798
DL0=2abae5fd86e8 GF=2abae5fd8740 DL1=2abae5fd8708 DPF=2abae5fd8730 DS=7b6ce3f0
   DON library unit variable list instantiation
------ ------------ ------------- -------------

This is expected behavior, if using Ctrl+C to terminate a running PL/SQL, a trace file is generated for debugging purposes.

This issue can be reproduced by the following steps:
1. Open a session and running:
declare
n number;
begin
loop
n := n + 1;
end loop;
end;
/

==>Then terminate this session with ctrl+c

2. Check udump and a trace is generated:

Solution

To avoid generating big trace file, please set MAX_DUMP_FILE_SIZE to a smaller value to get smaller trace files:

For example:
You can run the following command to set MAX_DUMP_FILE_SIZE to 1GB:
SQL> alter system set max_dump_file_size='1024M';
SQL> show parameter max_dump_file_size