[firebird-support] Re: Help with trigger syntax

2011-11-01 Thread grip_2ls
Thank you all for your help and advice.

N

--- In firebird-support@yahoogroups.com, Mark Rotteveel mark@... wrote:

 On Tue, 01 Nov 2011 10:00:38 +1300, Helen Borrie helebor@...
 wrote:
  At 07:56 AM 1/11/2011, you wrote:
 On 31-10-2011 17:46, grip_2ls wrote:
  Hi Mark
 
  Thanks for the advise but I don't think that is the issue. If you
  remove the second select statement it compiles and runs fine.
 
 That was exactly the issue I was pointing out. You are using SELECT 
 without INTO to call SendMail. That doesn't work as Sean also pointed
 out.
  
  Furthermore, invoking that Sendmail procedure as a select procedure is
 not
  sensible in this environment or any other.  Make it an executable
 procedure
  and, in the trigger code, call it with EXECUTE PROCEDURE (:var1, :var2,
  etc.)  Selectable procedures are intended to return sets and shouldn't
 be
  used to execute DML.
 
 Helen, it was actually a singleton select against RDB$DATABASE calling the
 SendMail UDF in the column list.





Re: [firebird-support] nbackup failure - cause?

2011-11-01 Thread Nick Upson
the level 0 backup restores ok and gbak will then backup  restore that,
could the corruption be somewhere that that doesn't matter?
how can I find and deal with it?

On 1 November 2011 09:47, Nick Upson nick.up...@gmail.com wrote:

 sorry, didn't think to say, its version 2.1.4


 On 31 October 2011 17:21, Alexey Kovyazin a...@ib-aid.com wrote:

 **


 Hello Nick,

 It seems like you have database corruption.
 What is Firebird version?

 Regards,
 Alexey Kovyazin
 IBSurgeon (www.ib-aid.com)


  Hi,
 
  I have recently started using nbackup and have a system where, at the
  end of an attempt to do a level 0 I got
 
  Fatal lock manager error: invalid lock id (158048), errno: 22
  --Invalid argument
 
  attempts to do subsequent level 1 backups produced:
 
  unsuccessful metadata update
  -Database is already in the physical backup mode
  Failure: Database error
  [
  PROBLEM ON begin backup.
  SQLCODE:-607
  ]
 
  I've never seen anything like this in my earlier testing, can anyone
  tell me what happened (firebird.log has nothing at these times)
 
 

 [Non-text portions of this message have been removed]

  





[Non-text portions of this message have been removed]





++

Visit http://www.firebirdsql.org and click the Resources item
on the main (top) menu.  Try Knowledgebase and FAQ links !

Also search the knowledgebases at http://www.ibphoenix.com 

++
Yahoo! Groups Links

* To visit your group on the web, go to:
http://groups.yahoo.com/group/firebird-support/

* Your email settings:
Individual Email | Traditional

* To change settings online go to:
http://groups.yahoo.com/group/firebird-support/join
(Yahoo! ID required)

* To change settings via email:
firebird-support-dig...@yahoogroups.com 
firebird-support-fullfeatu...@yahoogroups.com

* To unsubscribe from this group, send an email to:
firebird-support-unsubscr...@yahoogroups.com

* Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/



Re: [firebird-support] nbackup failure - cause?

2011-11-01 Thread Alexey Kovyazin
Hello,

Unfortunately, I can't say more without thorough investigation.
It can be bug or corruption or misconfiguration.

Regards,
Alexey Kovyazin

 the level 0 backup restores ok and gbak will then backup  restore that,
 could the corruption be somewhere that that doesn't matter?
 how can I find and deal with it?

 On 1 November 2011 09:47, Nick Upsonnick.up...@gmail.com  wrote:

 sorry, didn't think to say, its version 2.1.4


 On 31 October 2011 17:21, Alexey Kovyazina...@ib-aid.com  wrote:

 **


 Hello Nick,

 It seems like you have database corruption.
 What is Firebird version?

 Regards,
 Alexey Kovyazin
 IBSurgeon (www.ib-aid.com)


 Hi,

 I have recently started using nbackup and have a system where, at the
 end of an attempt to do a level 0 I got

 Fatal lock manager error: invalid lock id (158048), errno: 22
 --Invalid argument

 attempts to do subsequent level 1 backups produced:

 unsuccessful metadata update
 -Database is already in the physical backup mode
 Failure: Database error
 [
 PROBLEM ON begin backup.
 SQLCODE:-607
 ]

 I've never seen anything like this in my earlier testing, can anyone
 tell me what happened (firebird.log has nothing at these times)


 [Non-text portions of this message have been removed]





 [Non-text portions of this message have been removed]



 

 ++

 Visit http://www.firebirdsql.org and click the Resources item
 on the main (top) menu.  Try Knowledgebase and FAQ links !

 Also search the knowledgebases at http://www.ibphoenix.com

 ++
 Yahoo! Groups Links









++

Visit http://www.firebirdsql.org and click the Resources item
on the main (top) menu.  Try Knowledgebase and FAQ links !

Also search the knowledgebases at http://www.ibphoenix.com 

++
Yahoo! Groups Links

* To visit your group on the web, go to:
http://groups.yahoo.com/group/firebird-support/

* Your email settings:
Individual Email | Traditional

* To change settings online go to:
http://groups.yahoo.com/group/firebird-support/join
(Yahoo! ID required)

* To change settings via email:
firebird-support-dig...@yahoogroups.com 
firebird-support-fullfeatu...@yahoogroups.com

* To unsubscribe from this group, send an email to:
firebird-support-unsubscr...@yahoogroups.com

* Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/



[firebird-support] Questions about nbackup

2011-11-01 Thread sboydlns
I have been looking into switching from gbak to nbackup.  From what I have read 
about nbackup I am left with some, possibly incorrect, impressions.

1) nbackup is a page level backup rather than a row-by-row backup like gbak.
2) nbackup does no integrity checking of the database as it is backed up.  It 
simply copies the database page by page.
3) If 2) is true, then this would seem to imply that I could back up a 
corrupted database using nbackup without ever knowing that the database was 
corrupt.
4) If 2)  3) are true this would seem to imply that I could restore a 
corrupted database using nbackup and wind up with a corrupted database, the 
same as the original.

Please feel free to correct my misconceptions.






[firebird-support] Re: Handling deadlocks with classic mode

2011-11-01 Thread vincent999x
Ann,
  Thanks for the suggestion.  If I can tie a deadlock to a process ID, that 
will work out great.  I was intimidated by the lock manager before but after 
looking at its printout again, it doesn't seem that bad.

Thomas,
  We do not have SysInternals ProcessExplorer on our server, but I see that it 
is freely available so we will shortly.

  Thanks to all for your help.  I think I have enough information and tools now 
to solve my Firebird issues.

   Regards,
 vince
  

--- In firebird-support@yahoogroups.com, Ann Harrison aharrison@... wrote:

 Vince,
 
   Thanks for the response.  We are running Windows.  I'm not sure how much
  information about the fb_inet_server processes I can gather -- other than
  how long they've been running.  Not sure how to get the IP address of the
  connecting client.  I'm going to just start killing the oldest
  fb_inet_server processes, but I don't know how I can distinguish the
  listener process.   If I kill that one by mistake, I guess I'll have to
  reboot the whole server because I don't know how to restart just the
  listener.
 
Is there a way to identify the listener process?
 
 
 
 
 Get a full  lock print, find the deadlock, find the owner block for the
 deadlocked resource, and you'll find the process id of the listener there.
  Helen's book describes the contents of the lock print.
 
 Good luck,
 
 Ann
 
 
 [Non-text portions of this message have been removed]





Re: [firebird-support] Questions about nbackup

2011-11-01 Thread Alexey Kovyazin
Hello,

 I have been looking into switching from gbak to nbackup. From what I 
 have read about nbackup I am left with some, possibly incorrect, 
 impressions.

 1) nbackup is a page level backup rather than a row-by-row backup like 
 gbak.
 2) nbackup does no integrity checking of the database as it is backed 
 up. It simply copies the database page by page.
 3) If 2) is true, then this would seem to imply that I could back up a 
 corrupted database using nbackup without ever knowing that the 
 database was corrupt.
 4) If 2)  3) are true this would seem to imply that I could restore a 
 corrupted database using nbackup and wind up with a corrupted 
 database, the same as the original.

In general, you are right.
Read this presentation about backups in Firebird, it has more details 
about corruptions and gbak/nbackup:
http://www.slideshare.net/ibsurgeon/everything-about-backups-firebird-by-dmitry-kuzmenko-ceo-ibsurgeon

Regards,
Alexey Kovyazin
IBSurgeon (www.ib-aid.com)



 Please feel free to correct my misconceptions.

 



[Non-text portions of this message have been removed]



Re: [firebird-support] Re: Firebird 2.5 crashing after calling UDF

2011-11-01 Thread Frank Schlottmann-Gödde
On 26.10.2011 02:49, sir_wally_lewis wrote:
 Thanks for the fixes to my C library Tomasz and for your help.
 
 All my C Library is originally extracted from FreeUDFLibC and I added extra 
 functions.
 
 There were errors in the C Code that I was unaware of.
 
 Amazing that the same unaltered code works under CenTos 64 bit in 2.1 though.
 
 Still do not understand why my freepascal UDF is crashing.

Appears to be another bug similar to

http://tracker.firebirdsql.org/browse/CORE-3646

Even simple ppc64 generated udfs triggers the fb server process to end
on disconnecting the client.

I will create a simplified testcase and add it to the tracker asap.



mit freundlichen Grüßen
Frank Schlottmann-Gödde

-- 
Fascinating creatures, phoenixes, they can carry immensely heavy loads,
  their tears have healing powers and they make highly faithful pets.
  - J.K. Rowling