Hi,

Shutdown immediate is usually the normal preferred way to shutdown Oracle.

Ingstop also has an -immediate option as well as -force.
I think the Ingres ingstop -immediate is more like Oracle's shutdown abort.
It implies a '-force' but waits until the next startup to rollback pending transactions.

-----Original Message-----
From: info-ingres-bounces@kettleriverconsulting.com [mailto:info-ingres-bounces@kettleriverconsulting.com] On Behalf Of thiagomz
Sent: September 17, 2008 10:43 AM
To: info-ingres@kettleriverconsulting.com
Subject: [Info-Ingres] Shutdown / ingstop

Guys,

What is equivalent of 'shutdown immediate' from oracle on ingres ?

ingstop -f ?
ingstop -force ?

Why this Warning ????

"NOTE: this operation may leave databases accessed in this installation in an inconsistent state."

What is the better way to shutdown ingres ?

tkz guys !

$ ingstop -force

Ingres/ingstop


---------------------------------------------------------------------------

    |

    |

    |

    |

    |

    |

    |

    |

---------------------------------------------------------------------------

--
Regards,

Thiago Zerbinato
Oracle/Ingres DBA
Ribeirao Preto/SP
Brazil
_______________________________________________
Info-Ingres mailing list
Info-Ingres@kettleriverconsulting.com
http://www.kettleriverconsulting.com/mailman/listinfo/info-ingres

Run ingstop to let current db activity / sessions finish and to stop new
sessions connecting.
You need to allow time for various ingres processes to finish (eg archiver)

ingstop -force terminates any current activity causing transactions to
rollback. I've never experienced inconsistent database with this command.

ingstop -kill is bad. it sends a kill signal to the various processes and
CAN leave data in an inconsistent state and you can lose transactions in
memory. However when the server comes back up it will automatically
rollforward to the last saved transaction. (Make sure your database and all
tables are fully journalled.)

I usually run
ingstop
iimonitor (show sessions formatted).
ingstop -force

Paul

-----Original Message-----
From: info-ingres-bounces@kettleriverconsulting.com
[mailto:info-ingres-bounces@kettleriverconsulting.com]On Behalf Of
thiagomz
Sent: Thursday, 18 September 2008 12:43 AM
To: info-ingres@kettleriverconsulting.com
Subject: [Info-Ingres] Shutdown / ingstop

Guys,

What is equivalent of 'shutdown immediate' from oracle on ingres ?

ingstop -f ?
ingstop -force ?

Why this Warning ????

"NOTE: this operation may leave databases accessed in this installation
in an inconsistent state."

What is the better way to shutdown ingres ?

tkz guys !

$ ingstop -force

Ingres/ingstop

---------------------------------------------------------------------------

    |

    |

    |

    |

    |

    |

    |

    |

---------------------------------------------------------------------------

--
Regards,

Thiago Zerbinato
Oracle/Ingres DBA
Ribeirao Preto/SP
Brazil
_______________________________________________
Info-Ingres mailing list
Info-Ingres@kettleriverconsulting.com
http://www.kettleriverconsulting.com/mailman/listinfo/info-ingres

Thiago,

Will the users connect from the same system or remotely?  If remotely
(i.e., client/server configuration) then you can kill the
Communication Server processes (iigcc) easily with a command such as:
kill -6 `ps -fuingres | grep iigcc | grep -v grep | awk '{ print
$2 }'`

At my old company we created wrapper scripts for startup & shutdown
that did many things (managed log files, tracked if the system was
supposed to be up or down for monitoring purposes, etc.) and this
command was one of the first things that we did for shutdown.  We
would kill the iigcc, wait a few seconds, and then Ingres would
shutdown cleanly without requiring additional flags.

If the sessions are running on the same system then you might need to
perform an "ingstop -immediate".  It is better / safer that doing
"ingstop -force".  Those wrapper scripts that I mentioned would try a
plain ingstop first, and if that failed they would perform an ingstop -
immediate.  We had logic to also do an ingstop -force and then an OS
kill (because we never wanted a shutdown to not work), but those
events were logged and we would receive email as well.  I don't recall
ever seeing that happen outside of a test scenario.

You can find more ingstop information here as well:
http://docs.ingres.com/cmdref/ingstopCommandStopanIngresInstance

Cheers,

Chip Nickolett

Has anyone seen this before ... when trying to run this SQL when connected
to the Star database.  Works fine if I run directly in MSSQL.

SELECT
'INV',                                         /* BinTypeCode */
location,                                      /* BinCode */
description,                           /* BinDescription */
'2101',                                        /* StoreCode */
'DEF',                                         /* PriorityCode */
 CASE WHEN locationhold = '0'
      THEN 'Y'
      ELSE 'N'
 END                                           /* ActiveFlag */
FROM
Location
* * * * * * * * * * * * \g
Executing . . .

E_UL0303 Unexpected query tree node.
   (Mon Oct  6 17:20:44 2008)


********************************************************************
Mon Oct  6 17:20:44 2008 E_OP068A_BAD_TREE      consistency check
   - error converting query tree to text
********************************************************************
E_UL0303 Unexpected query tree node.
   (Mon Oct  6 17:20:44 2008)
-----------------------------------------
David G. Brooks
Systems Consultant
Vision Systems Software
(P.O. Box 804, Bridgetown)
Omega Building - Suite 5
Dayrells Court Business Centre
Dayrells Road
Christ Church  BB14030
BARBADOS

URL:   http://www.VisionSystemsSoftware.com/

Tel: (246) 431-0193 - Work
       (246) 266-8732 - Cel
       (246) 436-1417 - Home

Fax: (246) 431-0192 - Work

Vision Systems Software
www.visionsystemssoftware.com

Tel:(246)431-0193 Fax:(246)431-0192 eMail:

Vision@visionsystemssoftware.com

Disclaimer:

Information in this electronic e-mail is confidential and may be legally
privileged. It is intended solely for the addressee. If you have received

this e-mail message in error, please notify us immediately and destroy or
delete the message from your computer. If you are the intended recipient,

any form of reproduction, dissemination, copying, disclosure,
modification,
distribution and/or publication of this e-mail unless authorised is
strictly

prohibited and may be unlawful. Please rely on your own virus checker and
procedures with regard to any attachments to this message