Toad World® Forums

TOAD Script Error


#1

Good Morning All,
I am running a script that builds a series of dynamic sql statements (like select count(*),‘FARACHG’ from FIMSMGR.FARACHG;) against a set of oracle tables. I spool these statements in the first step and then run the spooled op in the second.

I started running into this message --> “Maximum grid count exceeded. Grids will no longer be created” at about release 9.? a while back. Despite my best efforts, I can’t seem to locate a setting to increase this parameter(?). It appears to be set at 100 at the moment.

Anyone have any ideas what I’m running into and how to -fix- it?

TIA,

Tim


#2

Tim,
We fixed the max grids at 100 due to memory considerations and some limitations in the controls we’re using.

Greg


#3

Thanks Greg, I’ll adjust accordingly…
image001.jpeg


#4

Thanks Greg, I’ll adjust accordingly…
image001.jpeg


#5

Tim,

… Despite my best efforts, I can’t seem to
locate a setting to increase this parameter(?). It appears
to be set at 100 at the moment.

Anyone have any ideas what I’m running into and how to -fix- it?

Does it help if you go to view->Toad Options->Execute/compile and
uncheck the option to “show script grids”?

I usually have this unchecked so I only get the results for the whole
script in one script output tab. I don’t get the individual output
grids.

Cheers,
Norm. [TeamT]

Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else. We have checked this email and its attachments for viruses. But you should still check any attachment before opening it. We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes. If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk

Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else.

We have checked this email and its attachments for viruses. But you should still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes.

If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk


#6

Think about using EXECUTE immediate. We used to have 2 step jobs also. One to spool and then the second to execute what was spooled. It was simpler to control to turn them all into EXECUTE immediate. I also created a procedure that would take a variable and do one of three things:

  1. just dbms_output the info
  2. execute and dbms_output
  3. execute only

#7

The script should keep executing but just won’t make any more than 100 grids. Of course it’ll be faster if you turn the grids off like Norm does.

Greg [TeamCaffeine]