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


---------------------------------------------------------------------------
| ***WARNING***
|
|
|
| All connections held in this installation will be terminated
| in 0 minutes!
|
|
| All uncommitted transactions will be rolled back before shutdown is
|
| complete.
|
|
|
| NOTE: this operation may leave databases accessed in this installation
| in an inconsistent state.
|
|
|

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


--
Regards,

Thiago Zerbinato
Oracle/Ingres DBA
Ribeirao Preto/SP
Brazil

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-at-kettleriverconsulting.com [mailto:info-ingres-bounces-at-kettleriverconsulting.com] On Behalf Of thiagomz
Sent: September 17, 2008 10:43 AM
To: info-ingres-at-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


---------------------------------------------------------------------------
| ***WARNING***
|
|
|
| All connections held in this installation will be terminated in 0
| minutes!
|
|
| All uncommitted transactions will be rolled back before shutdown is
|
| complete.
|
|
|
| NOTE: this operation may leave databases accessed in this installation
| in an inconsistent state.
|
|
|

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


--
Regards,

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

-immediate aborts the recovery process as well and the dbms process, so use sparingly if at all.
-force and -kill only work on the dbms so are less proned to causing recovery issues.

Geoff

-----Original Message-----
From: info-ingres-bounces-at-kettleriverconsulting.com [mailto:info-ingres-bounces-at-kettleriverconsulting.com] On Behalf Of Laframboise André
Sent: 17 September 2008 16:10
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] Shutdown / ingstop


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-at-kettleriverconsulting.com [mailto:info-ingres-bounces-at-kettleriverconsulting.com] On Behalf Of thiagomz
Sent: September 17, 2008 10:43 AM
To: info-ingres-at-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


---------------------------------------------------------------------------
| ***WARNING***
|
|
|
| All connections held in this installation will be terminated in 0
| minutes!
|
|
| All uncommitted transactions will be rolled back before shutdown is
|
| complete.
|
|
|
| NOTE: this operation may leave databases accessed in this installation
| in an inconsistent state.
|
|
|

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


--
Regards,

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

_______________________________________________
Info-Ingres mailing list
Info-Ingres-at-kettleriverconsulting.com
http://www.kettleriverconsulting.com...fo/info-ingres

************************************************** ********************
This e-mail including any attachments is provided for general information purposes only and does not constitute advice except to the addressee if expressly stated in this email. For the avoidance of doubt the contents of this email and any attachments are subject to contract and are not intended to and will not constitute a legally binding contract or any part of a legally binding contract.

The information contained in this email and any attachments is confidential. It is intended only for the use of the intended recipient at the email address to which it has been addressed. If the reader of this message is not an intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution or copying of the message or associated attachments is strictly prohibited.

If you have received this e-mail in error, please notify postmaster-at-RWEsystemsUK.com and permanently delete the email and any attachments immediately from your system. You should not retain, copy or use this email or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you for your co-operation.

Neither RWE IT UK Ltd nor any of the other companies in the RWE Group from whom this e-mail originates accept any responsibility for losses or damage as a result of any viruses and it is your responsibility to check attachments (if any) for viruses.

RWE IT UK Ltd Registered office: Mistral, Westlea Campus, Chelmsford Road, Swindon, Wiltshire, SN5 7EZ. Registered in England and Wales: company number 6052966.

*******************************************

Laframboise André escreveu:
> Hi,
>
> Shutdown immediate is usually the normal preferred way to shutdown Oracle.
>
> Ingstop also has an -immediate option as well as -force.

How can I stop ingres in a safe way disconnecting the users ?

I´m executing ipm, killing all users and than running a ingstop without
any parameter, but I spent a lot of time to do that.

--
Regards,

Thiago Zerbinato
Oracle/Ingres DBA
Ribeirao Preto/SP
Brazil

2008/9/17 thiagomz

>
> How can I stop ingres in a safe way disconnecting the users ?
>
> I´m executing ipm, killing all users and than running a ingstop without
> any parameter, but I spent a lot of time to do that.
>
>
Hi Thiago,

You can automate the removal of sessions using a script. I've just added a
Wiki page to show the one I use most often -
http://community.ingres.com/wiki/IMA...essions_Script

HTH
--
Paul Mason

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/ingsto...IngresInstance

Cheers,

Chip Nickolett

Chip (et al),
The friendly guys at Ingres have provided a cleaner way of shutting
down Ingres/Net in recent Ingres versions:

echo "stop" | iinamu -file-

does an immediate shutdown of all GCCs.

echo "quiesce" | iinamu -file-

tells them to shutdown when user-count gets to zero.

Chris Dawe

On Fri, 19 Sep 2008 05:58:48 -0700 (PDT), Chip Nickolett
wrote:

>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/ingsto...IngresInstance
>
>Cheers,
>
>Chip Nickolett

--
uSsPeAnMet-at-lSaPbAyMriSnPtAhMdaStPaA.cMo.uk
Remove all SPAM to reply

Chris,

Slight typo, I think. The Name Server won't shut down a Communications
Server. You meant netutil. These commands work:

echo stop | netutil -file-
echo quiesce | netutil -file-

John

-----Original Message-----
From: info-ingres-bounces-at-kettleriverconsulting.com
[mailto:info-ingres-bounces-at-kettleriverconsulting.com] On Behalf Of
chris.dawe-at-eds.spamtrap.invalid
Sent: Sunday, 21 September 2008 11:39 PM
To: info-ingres-at-kettleriverconsulting.com
Subject: Re: [Info-Ingres] Shutdown / ingstop

Chip (et al),
The friendly guys at Ingres have provided a cleaner way of shutting
down Ingres/Net in recent Ingres versions:

echo "stop" | iinamu -file-

does an immediate shutdown of all GCCs.

echo "quiesce" | iinamu -file-

tells them to shutdown when user-count gets to zero.

Chris Dawe

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

Tel246)431-0193 Fax246)431-0192 eMail:

Vision-at-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

The problem is the case statement. It's stuffed on a distributed
database.



DDB's have several *VERY* annoying restrictions, this is one of them.



Martin Bowes



From: info-ingres-bounces-at-kettleriverconsulting.com
[mailto:info-ingres-bounces-at-kettleriverconsulting.com] On Behalf Of
David Brooks
Sent: 06 October 2008 22:32
To: Ingres and related product discussion forum
Subject: [Info-Ingres] Ingres/Star (IngresII 2.6 to MSSQL)




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

Tel246)431-0193 Fax246)431-0192 eMail:

Vision-at-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