If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Informational Warnings

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 06-22-04, 10:55
beckdb2 beckdb2 is offline
Registered User
 
Join Date: Mar 2004
Posts: 24
Informational Warnings

DB2 UDB Version 8.1 AIX
--------------------------------------------------------------------------

Hello,

I have a general question. Does anyone know how to keep an application from returning informational warnings. I have tried the DIAGLEVEL and NOTIFYLEVEL. Setting them both to '2', which should only return errors. I was under the impression that this only applied to the diag and notification logs, but I tried it anyway. Well, it didn't work. The user are using a third party tool and when they issue a delete they recieve the DB2 warning:

SQL0513W The SQL Statement Will Modify an Entire Table or View

Is there a way to keep these messages from happening?

Thanks,

Beck
Reply With Quote
  #2 (permalink)  
Old 06-23-04, 14:24
beckdb2 beckdb2 is offline
Registered User
 
Join Date: Mar 2004
Posts: 24
Hmmmmmmmmmmm?
Reply With Quote
  #3 (permalink)  
Old 06-23-04, 14:32
J Petruk J Petruk is offline
Registered User
 
Join Date: Mar 2004
Location: Toronto, ON, Canada
Posts: 513
Quote:
Originally Posted by beckdb2
Hmmmmmmmmmmm?
Geez, give us time to think!

IMO I don't think there's a way to turn them off, they'll always be available to the caller and you may be at the mercy of the 3rd party tool's handling of them.

Do you know what this 3rd party tool is using to connect? ODBC or JDBC?
__________________
--
Jonathan Petruk
DB2 Database Consultant
Reply With Quote
  #4 (permalink)  
Old 06-23-04, 17:08
beckdb2 beckdb2 is offline
Registered User
 
Join Date: Mar 2004
Posts: 24
The 3rd Party tool is Ascential Data Stage. ODBC connections. My programmer said that he saw on an Ascential forum where the DBA stopped these from happening. The warning is definetly a DB2 SQL warning. Unfortunately, the forum didnt saw how he did it. Just trying to see if anyone had any ideas.
Reply With Quote
  #5 (permalink)  
Old 06-23-04, 17:17
J Petruk J Petruk is offline
Registered User
 
Join Date: Mar 2004
Location: Toronto, ON, Canada
Posts: 513
Quote:
Originally Posted by beckdb2
The 3rd Party tool is Ascential Data Stage. ODBC connections. My programmer said that he saw on an Ascential forum where the DBA stopped these from happening. The warning is definetly a DB2 SQL warning. Unfortunately, the forum didnt saw how he did it. Just trying to see if anyone had any ideas.
db2cli.ini
IGNOREWARNLIST

Bam!
__________________
--
Jonathan Petruk
DB2 Database Consultant
Reply With Quote
  #6 (permalink)  
Old 06-24-04, 14:58
beckdb2 beckdb2 is offline
Registered User
 
Join Date: Mar 2004
Posts: 24
Thanks,

I believe we are on the right track. From reading the documentation this looks like exactly what needs to be done. I updated the db2cli.ini on the appserver with:

[common]
IGNOREWARNLIST="'10504'"
WARNINGLIST="'10504'"

The common section should apply to all connections that this client makes, but its STILL not working. Does anything else need to be done to make these changes take effect?
Reply With Quote
  #7 (permalink)  
Old 07-01-04, 17:00
AD29 AD29 is offline
Registered User
 
Join Date: Jun 2004
Posts: 10
We made these changes to db2cli.ini:
[common]
IGNOREWARNLIST="'10504'"
WARNINGLIST="'10504'"

And then rebound with:

db2 bind @db2cli.lst

and we still can not prevent the "10504" error from being passed to the application. Do we need to possibly bind the application? Is there anything else? Has anyone successfully prevented errors from being passed to the application, and if so, can you add anything to this?

Jim
Reply With Quote
  #8 (permalink)  
Old 05-18-07, 06:23
hjullens hjullens is offline
Registered User
 
Join Date: May 2007
Posts: 1
The correct syntax would be:

[COMMON]
IgnoreWarnList="'01504'"

(01504 instead of 10504)
Rebinding is not necessary as DataStage connects at each job.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On