[Info-ingres] [Users] How to Log errors while executing ingres sql command

DATABASE

    Sponsored Links

    Next

  • 1. Consistency points in r3
    The way CP flushing is done has changed repeatedly over the years. Way back in the bad old days, a consistency point flush used to stall the server. Also, the WB threads used to help out with CP flushes. Later the behaviour was changed so that CP flushes no longer stall the server and the WB threads no longer assist. I can't pretend to follow its vagaries from rev to rev. I am suddenly curious to know a bit more about CP flushing in Ingres r3. Specifically, how high a priority does CP flushing have? When I see two CP flushes of similar numbers of buffers using a similar number of DIOs, should I expect to see the duration of the flush vary by a factor of up to 10? Roy
  • 2. [Info-Ingres] AIX + Ingres 2.6 + OS Threads
    hi, Is there anyone using AIX + Ingres 2.6 + OS Threads? Does it work fine? Our current configuration uses 10 dbms servers with shared memory and internal threads (7 for each server). We think about changing to OS threads, but in the past our experiences were not good (AIX + Ingres 2.0 + OS Threads). Any experiences are welcome! Thanks. -- Atenciosamente, Daniel Ordob Bortol Nleo de Informica Justi Federal - RS (51) 3214-9064

[Info-ingres] RE: [Users] How to Log errors while executing ingres sql command

Postby Paul White » Tue, 21 Feb 2006 14:20:22 GMT

his is a multi-part message in MIME format.

Hi Ajay,
Check out the archives at info ingres. I believe someone will have done
this before.

To register
http://mailman.cariboulake.com/mailman/listinfo.py/info-ingres

or check out the news feed at comp.databases.ingres

Paul




________________________________

From: Ajay Dalvi [mailto:dalvi_ajay at <mailto: XXXX@XXXXX.COM >
extenprise.net]
Sent: Monday, 20 February 2006 3:56 PM
To: XXXX@XXXXX.COM ; Paul White
Subject: RE: [Users] How to Log errors while executing ingres sql
command


Hi Paul,
First of all Thanks for your reply.
I am still having one problem. I have to actually log the full error
description. As in your case, the output of the sql command will be in
mylog file, but it will contain other statements apart from errors, but
I want to log only error messages.
Grrepping E_ will be usefull only if the error description is of one
line.
If error description is more than one line for e.g.

E_XF0019 There was a table or view specified on the command line that
does
not exist or is not owned by you, or has been supplied more than
once.

In this case, If we grep it using E_ then we will get only first line.
For this I am trying to create regular expression which wll grep error
msg with multiple lines description.
If you can provide some help for this, it will be helpfull for me.

-Ajay


On Sun, 2006-02-19 at 22:49, Paul White wrote:

Hello Ajay,
Here's what I do in a unix script.


sql mydb <<eof > mylog
Select stuff...
\g
eof

grep "E_" mylog > /dev/null
if [ $? -eq 0 ] ; then
echo "Error occurred"
exit 1
fi


-----Original Message-----
From: users-bounces+pwhite= XXXX@XXXXX.COM
[mailto:users-bounces+pwhite= XXXX@XXXXX.COM
<mailto:users-bounces+pwhite= XXXX@XXXXX.COM > ] On
Behalf
Of XXXX@XXXXX.COM
Sent: Monday, 20 February 2006 3:09 AM
To: XXXX@XXXXX.COM
Subject: [Users] How to Log errors while executing ingres sql
command

Hi all,
I am using ingres sql command to execute the sql
commands
(create/insert/delete), While executing ingres 'sql' command,
all the
errors that raises gets displayed on standard output with error
number
in format E_<>.

On linux, I am executing this comand through shell script. I
want to log
the errors which raises by sql, I have tried this by following
way:

sql database_name < sql_file 2>> log_file

But the errors are not getting logged in to specified log file.

Just for comparision, in postgres database, we can do this as

psql database_name -f sql_file 2>>log_file.

In this case , errors gets logged properly in specified log
file.

So can any one please tell me how I can achieve the same
behaviour in
ingres.

-Ajay


--
This message has been scanned for viruses and dangerous content
by
Extenprise mailscanner, and is believed to be clean.

_______________________________________________
Users mailing list
XXXX@XXXXX.COM
<http://ingres.ca.com/mailman/listinfo/users>
http://ingres.ca.com/mailman/listinfo/users

_______________________________________________
Users mailing list
XXXX@XXXXX.COM
<http://ingres.ca.com/mailman/listinfo/users>
http://ingres.ca.com/mailman/listinfo/users


--
This message has been scanned for viruses and
dangerous content by Extenprise mailscanne

Similar Threads:

1.[Info-ingres] FW: [Users] How to Log errors while executing ingres sql command

2.[Info-ingres] How to Log errors while executing ingres sql command

3.[Info-ingres] RES: [Info-ingres] RES: [Info-ingres] SQL Injection attacks

> -----Mensagem original-----
> De:  XXXX@XXXXX.COM  
> [mailto: XXXX@XXXXX.COM ] Em nome de Emiliano
> Enviada em: Monday, June 12, 2006 10:06 AM
> Para:  XXXX@XXXXX.COM 
> Assunto: Re: [Info-ingres] RES: [Info-ingres] SQL Injection attacks
> 
> On 2006-06-12, Leandro Pinto Fava < XXXX@XXXXX.COM > wrote:
> > Three years ago we had a case of SQL Injection against our web
portal of
> > students's info. This portal was made using ICE and reports in 1999
> > (with very bad security control). Now we have this portal made in
PHP
> > and the possibility of SQL injection is nearly null (I think :-().
We
> > had another web application (ASP) that suffered a successful SQL
> > injetcion too. The problems were corrected as well.
> 
> And (to hook into the delightful discussion I'm having with Roy), I'll
> bet you dimes to dollars that both were using query assembly.

The ASP app was, but the ICE app was not directly. Report Writer
internally should work with query assembly when passing parameters to
run a report.

> 
> The PHP function addslashes ought to protect you if you use it
> consistently. PHP ADODb has parameter binds, which are better.

Yes.

> 
> > In our case the problems were in the application layer.
> 
> HTML injection?

No, when I said application layer, I wanted to say the problem was not
in database server.

Leandro.

4.[Info-ingres] RES: [Info-ingres] RES: [Info-ingres] SQL Injection attacks

5.[Info-ingres] RES: [Info-ingres] SQL Injection attacks

6. How to Log errors while executing ingres sql command

7. [Info-Ingres] Ingres SQL question

8. [Info-ingres] Scheduled SQL Job pulling from Ingres Fails



Return to DATABASE

 

Who is online

Users browsing this forum: No registered users and 84 guest