gpt4 book ai didi

Oracle查询sql错误信息的控制和定位

转载 作者:qq735679552 更新时间:2022-09-29 22:32:09 25 4
gpt4 key购买 nike

CFSDN坚持开源创造价值,我们致力于搭建一个资源共享平台,让每一个IT人在这里找到属于你的精彩世界.

这篇CFSDN的博客文章Oracle查询sql错误信息的控制和定位由作者收集整理,如果你对这篇文章有兴趣,记得点赞哟.

在sqlplus中执行的sql出错之后应该如何处理和对应,多行sql语句或者存储过程的信息如何进行错误定位,这篇文章将结合实例进行简单地说明.

环境准备 。

使用Oracle的精简版创建docker方式的demo环境,详细可参看:

如何进行错误定位 。

场景:

假如有3行insert的sql语句,中间一行出错之后,后续继续执行的情况下,如何定位到第二行?

dbms_utility.format_error_backtrace 。

通过使用dbms_utility.format_error_backtrace可以得到ERROR at line xxx:的信息,这对我们较为有用,我们接下来进行确认 。

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
oracle@e871d42341c0:~$ sqlplus system/abcd1234@XE <<EOF
> SET SERVEROUTPUT ON
> desc student
> delete from student;
> select * from student;
> insert into student values (1001, 'liumiaocn' );
> insert into student values (1001, 'liumiao' );
> insert into student values (1003, 'michael' );
> select * from student;
> commit ;
> exec dbms_output.put_line(dbms_utility.format_error_backtrace);
> EOF
SQL*Plus: Release 11.2.0.2.0 Production on Sun Oct 21 13:06:07 2018
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to :
Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
SQL> SQL> Name    Null ?  Type
  ----------------------------------------- -------- ----------------------------
  STUID    NOT NULL NUMBER(4)
  STUNAME     VARCHAR2(50)
SQL>
2 rows deleted.
SQL>
no rows selected
SQL>
1 row created.
SQL> insert into student values (1001, 'liumiao' )
*
ERROR at line 1:
ORA-00001: unique constraint (SYSTEM.SYS_C007024) violated
SQL>
1 row created.
SQL>
    STUID STUNAME
---------- --------------------------------------------------
    1001 liumiaocn
    1003 michael
SQL>
Commit complete.
SQL>
PL/SQL procedure successfully completed.
SQL> Disconnected from Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
oracle@e871d42341c0:~$

可以看到,报错的时候提示了行号,但是行号是1,这是因为这种写法以一行为单位,自然是如此,如果是单个多行的存储过程,将会更加清晰.

?
1
2
ERROR at line 1:
ORA-00001: unique constraint (SYSTEM.SYS_C007024) violated

所以我们将这个例子进行改造,三行insert的sql放到文件之中,然后在使用dbms_utility.format_error_backtrace来进行确认 。

?
1
2
3
4
5
6
7
8
9
10
oracle@e871d42341c0:~$ cat /tmp/sqltest1.sql
desc student
delete from student;
select * from student;
insert into student values (1001, 'liumiaocn' );
insert into student values (1001, 'liumiao' );
insert into student values (1003, 'michael' );
select * from student;
commit ;
oracle@e871d42341c0:~$

然后在尝试一下是否能够确认行号,会发现仍然不能精确定位:

  。

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
oracle@e871d42341c0:~$ sqlplus system/abcd1234@XE <<EOF
> SET SERVEROUTPUT ON
> @/tmp/sqltest1.sql
> exec dbms_output.put_line(dbms_utility.format_error_backtrace);
> EOF
SQL*Plus: Release 11.2.0.2.0 Production on Sun Oct 21 13:08:27 2018
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to :
Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
SQL> SQL> Name    Null ?  Type
  ----------------------------------------- -------- ----------------------------
  STUID    NOT NULL NUMBER(4)
  STUNAME     VARCHAR2(50)
2 rows deleted.
no rows selected
1 row created.
insert into student values (1001, 'liumiao' )
*
ERROR at line 1:
ORA-00001: unique constraint (SYSTEM.SYS_C007024) violated
1 row created.
    STUID STUNAME
---------- --------------------------------------------------
    1001 liumiaocn
    1003 michael
Commit complete.
SQL>
PL/SQL procedure successfully completed.
SQL> Disconnected from Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
<a href= "mailto:oracle@e871d42341c0:~$" rel= "external nofollow" >oracle@e871d42341c0:~$</a>

因为dbms_utility.format_error_backtrace更多的场景是在于存储过程的错误定位,接下来我们使用一个简单的存储过程例子来进行确认错误行号定位, 先看一个正常的存储过程,把上面的内容稍微修改一下:

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
oracle@e871d42341c0:~$ cat /tmp/addstudent.sql
create or replace PROCEDURE addstudents
IS
student_count number;
BEGIN
delete from student;
select count (*) into student_count from student;
dbms_output.put( 'sql set count before :' );
dbms_output.put_line(student_count);
insert into student values (1001, 'liumiaocn' );
insert into student values (1002, 'liumiao' );
insert into student values (1003, 'michael' );
select count (*) into student_count from student;
dbms_output.put( 'sql set count after :' );
dbms_output.put_line(student_count);
END ;
/
exec addstudents();
oracle@e871d42341c0:~$

结果执行信息如下 。

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
oracle@e871d42341c0:~$ sqlplus system/liumiao123 <<EOF
set serveroutput on ;
@/tmp/addstudent.sql
EOF
SQL*Plus: Release 11.2.0.2.0 Production on Mon Oct 22 04:42:11 2018
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to :
Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
SQL> SQL>
Procedure created.
sql set count before :0
sql set count after :3
PL/SQL procedure successfully completed.
SQL> Disconnected from Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
oracle@e871d42341c0:~$

接下来我们修改一下内容,使得第二行主键重复 。

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
oracle@e871d42341c0:~$ cat /tmp/addstudent.sql
create or replace PROCEDURE addstudents
IS
student_count number;
BEGIN
delete from student;
select count (*) into student_count from student;
dbms_output.put( 'sql set count before :' );
dbms_output.put_line(student_count);
insert into student values (1001, 'liumiaocn' );
insert into student values (1001, 'liumiao' );
insert into student values (1003, 'michael' );
select count (*) into student_count from student;
dbms_output.put( 'sql set count after :' );
dbms_output.put_line(student_count);
END ;
/
exec addstudents();
oracle@e871d42341c0:~$

再次执行,自然会出错,但是可以看到,正确报出了所在行数,这是procedure的机制提示的信息 。

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
oracle@e871d42341c0:~$ sqlplus system/liumiao123 <<EOF
set serveroutput on ;
@/tmp/addstudent.sql
EOF
SQL*Plus: Release 11.2.0.2.0 Production on Mon Oct 22 04:44:25 2018
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to :
Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
SQL> SQL>
Procedure created.
sql set count before :0
BEGIN addstudents(); END ;
*
ERROR at line 1:
ORA-00001: unique constraint (SYSTEM.SYS_C007024) violated
ORA-06512: at "SYSTEM.ADDSTUDENTS" , line 10
ORA-06512: at line 1
SQL> Disconnected from Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
oracle@e871d42341c0:~$

可以看到,ORA-06512: at “SYSTEM.ADDSTUDENTS”, line 10的信息就是我们期待的信息,提示出在这个存储过程的第10行执行出现问题,而实际可以使用dbms_utility.format_error_backtrace结合exception给出更为清晰地方式,比如:

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
oracle@e871d42341c0:~$ cat /tmp/addstudent.sql
create or replace PROCEDURE addstudents
IS
student_count number;
BEGIN
delete from student;
select count (*) into student_count from student;
dbms_output.put( 'sql set count before :' );
dbms_output.put_line(student_count);
insert into student values (1001, 'liumiaocn' );
insert into student values (1001, 'liumiao' );
insert into student values (1003, 'michael' );
select count (*) into student_count from student;
dbms_output.put( 'sql set count after :' );
dbms_output.put_line(student_count);
exception
when others then
dbms_output.put( 'exception happend with line info : ' );
dbms_output.put_line(dbms_utility.format_error_backtrace);
END ;
/
exec addstudents();
oracle@e871d42341c0:~$

执行结果确认:

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
oracle@e871d42341c0:~$ sqlplus system/liumiao123 <<EOF
set serveroutput on ;
@/tmp/addstudent.sql
EOF
SQL*Plus: Release 11.2.0.2.0 Production on Mon Oct 22 04:49:27 2018
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to :
Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
SQL> SQL>
Procedure created.
sql set count before :0
exception happend with line info : ORA-06512: at "SYSTEM.ADDSTUDENTS" , line 10
PL/SQL procedure successfully completed.
SQL> Disconnected from Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
oracle@e871d42341c0:~$

这样则可以看出能够比较清晰地进行错误的定位了,但是由于功能受限,所以实际使用场景仍然较为有限,但是定位存储过程的信息则可以使用dbms_utility.format_error_backtrace等进行确认.

小结 。

多行sql执行定位可以考虑拆成单行来确认,而存储过程则可结合format_error_backtrace等进行确认以提供问题出现的所在行号.

总结 。

以上就是这篇文章的全部内容了,希望本文的内容对大家的学习或者工作具有一定的参考学习价值,谢谢大家对我的支持。如果你想了解更多相关内容请查看下面相关链接 。

原文链接:https://blog.csdn.net/liumiaocn/article/details/83900869 。

最后此篇关于Oracle查询sql错误信息的控制和定位的文章就讲到这里了,如果你想了解更多关于Oracle查询sql错误信息的控制和定位的内容请搜索CFSDN的文章或继续浏览相关文章,希望大家以后支持我的博客! 。

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com