All,

Is that possible to change “IBIF_max_messages” limit to one particular Procedure or turn off the FOCRRR messages in the report?
I have an issue here: I have a procedure that will insert up to 30,000 rows to a Oracle database. But after every row insert the message was generating like follow. Right now we have set IBIF_max_messages -50000, since the following message coming after every row and once it reaches to 50, 000, and then server was generating an error. How we can turn off the FOCERR messages?
Reporting Server messages exceeded IBIF_max_messages, report retrieval aborted.
0 NUMBER OF RECORDS IN TABLE= 1 LINES= 1
(FOC1364) ROWS AFFECTED BY PASSTHRU COMMAND : 1/INSERT
(FOC1364) ROWS AFFECTED BY PASSTHRU COMMAND : 1/INSERT
(FOC1364) ROWS AFFECTED BY PASSTHRU COMMAND : 1/INSERT

Thanks in advance.

This message has been edited. Last edited by: <Kathryn Henning>,

Have you thought about turning ECHO OFF or MSG OFF ?

Set IBIF_Max_messages to 0 ( no limit)
Also try SETMSG=OFF

Thanks,
Ram

This might help you.

http://documentation.informati.../source/topic101.htm

Thanks,
Ram

I would suggest not setting max messages to 0 as it would allow massive results to be returned to the browser.

Chalk one up to experience over knowledge

We just need to be aware that there are several settings that can provide a quick fix but they are not always the best to suggest to rookies.

T

I agree to Waz and Tony, as Set IBIF_Max_messages to 0 should be used only for debug purpose.

Are you using direct INSERT statement or Stored procedure?
If its direct INSERT statements, then try calling a stored procedure and INSERT records from SP. Hope this will work.

Thanks,
Ram

This message has been edited. Last edited by: Ram Prasad E,

With databases, the general preference for doing inserts like that seems to be to bulk-load them instead of inserting every single record separately. In general that performs better too.

So if you prepare your records into a file or statement with that intent, I'd suggest doing one of these:

• ISTR that Oracle does have a bulk-load feature.
  
• If you use plain SQL, you can insert multiple records in one INSERT statement. For example:

  -- Not available before Oracle 11 I think
  INSERT INTO table (field1, field2, field3) VALUES (1, 'A', 'foo'), (2, 'B', 'bar'), (3, 'C', 'baz');
  -- or in earlier versions
  INSERT INTO table (field1, field2, field3) SELECT 1, 'A', 'foo' FROM dual UNION SELECT 2, 'B', 'bar' FROM dual UNION SELECT 3, 'C', 'baz' FROM dual;

  
  
• You could create your insert statements as an SQL file and send that to your database directly.

I realize this merely prevents your problem with IBIF_MAX_MESSAGES from happening instead of solving it and I agree that it would be useful to have a report-scope tunable for that.