Hi,
The database should be fine - I've never had problems with crash recovery
but for peace of mind you could try the following:
db2 list tablespaces - all tablespaces should be in a normal state, i.e.
state 0x0000. A quick way of doing this on AIX is the following line:
db2 list tablespaces | grep State | sort | uniq
You should see only:
State = 0x0000
Any other states need investigating.
Another thing you could do is a sample select from each of your tables.
This might flush out things such as corrupt indexes which may otherwise only
be discovered when an application asks for that data. Sample command:
"select * from <table_name> fetch first one row only"
If you wanted to be serious about it you could run the db2dart utility, but
that would really be overkill.
Thanks,
Mark Savin
DBA
Euler Trade Indemnity
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, February 07, 2003 2:04 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: [DB2EUG] Crash recovery
>
> Hi all,
>
> Today we had a power failure. Our DB2 v7.2 on AIX detected this and used
> Crash Recovery.
> Are there any actions needed by the DBA, or is everithing ok after a crash
> recovery?
>
> See messages from db2dump.log file below
>
> Regards
> Raoul Joemman
>
>
>
> Crash Recovery is needed.
> DIA3908W Crash recovery has been initiated.
> Using parallel recovery with 3 agents 4 QSets 28 queues and 2 chunks
> DIA3916W Forward phase of crash recovery has completed.
> DIA3909W Crash recovery completed.
>
>
>
>
>
>
> *****************************************************************
> This e-mail and any attachment may contain confidential
> and privileged material intended for the addressee only.
> If you are not the addressee, you are notified that no part of
> the e-mail or any attachment may be disclosed, copied or
> distributed, and that any other action related to this e-mail
> or attachment is strictly prohibited, and may be unlawful.
> If you have received this e-mail by error, please notify the
> sender immediately by return e-mail, and delete this message.
> Martinair Holland N.V., its subsidiaries and/or its employees
> shall not be liable for the incorrect or incomplete transmission
> of this e-mail or any attachments, nor responsible for any
> delay in receipt.
> *****************************************************************
>
> -
> ::: When replying to the list, please use 'Reply-All' and make sure
> ::: a copy goes to the list ([EMAIL PROTECTED]).
> *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
> *** For more information, check http://www.db2eug.uni.cc
-
::: When replying to the list, please use 'Reply-All' and make sure
::: a copy goes to the list ([EMAIL PROTECTED]).
*** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
*** For more information, check http://www.db2eug.uni.cc
