Open test: Performance-How to troubleshoot a database query result is too large to cause recording to fail (serial 3)

7.3 How to troubleshoot a database query result is too large to cause a recording failure 1. Questions raised

In a Invoicing management application system testing process, found that after the query, because the query result data record number of excessive, and cause subsequent scripts can not continue recording.

2. Answer questions

we found in the testing process that many of the settings are related to database applications. The solution to this problem can be accomplished by setting the vugen.ini cmdsize item.

Vugen.ini files are stored in the Windows system directory, first find out if the "[Sqloracleinspector]" item exists in the file, and see if there is already "cmdsize= XXXXX"Item, if it does not exist, add the following to the file:

[Sqloracleinspector]

cmdsize=100000

in this case, the database used by the application we are testing is Oracle, so for "[Sqloracleinspector]", "100000" of the settings and records return the number of entries are related, so you can find the relevant information in similar situations to set the corresponding.

For more information, please pay attention to the big open technology public number or the official website

www.dakaikeji.com.cn

650) this.width=650; "Src=" http://mmbiz.qpic.cn/mmbiz_jpg/ Sz1zkaagrnova3yveqiazhr8qt23leeypmrnvm85rmkuibxibz2iatel3qwpblrr33sgicdgrsh4h8kicw4lw6rc0iang/640?wx_fmt=jpeg &tp=webp&wxfrom=5&wx_lazy=1 "alt=" 640?wx_fmt=jpeg&tp=webp&wxfrom=5&wx_lazy "style=" Padding:0px;margin:0px;vertical-align:top;border:none;height:auto;line-height:25.6px;width:auto; "/>

Open test: Performance-How to troubleshoot a database query result is too large to cause recording to fail (serial 3)