Problem with restore in RSS Instance
Posted in 2016
Topics: Backup & Restore, Storage & Space Management, Server Administration, Logging & Checkpoints, Platform-Specific Issues
Problem description:
Informix 12.10 Enterprise Edition Operating System:
Read Heat Linux 6.5 64 bit
Affected part of system: RSS to the Disaster Recovery Server
The problem started with a LOCK database engine caused by FULL logs.
We tried to fire up "ontape -c &" but it failed. It said that continuous
backup was already in progress.
We tried unsuccessfully fire up "ontape -a".
As informix still LOCKED we tried "onmode -ky". After more or less 15 minutes
the command prompt doesn't come back...
We needed to do a restart of the operating system with "shutdown -r now".
After reboot the logs was backed up by an "ontape -c &" which is on the
startup script.
The instance went up to online.
Finding on the logs we see the following:
"11:43:07 Process exited with return code 126: /bin/sh /bin/sh -c
/opt/informix/1210/etc/alarmprogram.sh 3 20 "Logical Logs are Full -- Backup
is Needed." "Logical Log Files are almost Full -- Backup is Needed. In Data
replication scenario, this could block failure- recovery of the paired server."
Looking for the synchronization of the instances with "onstat -g rss" we saw
that the logs were no more been received by secondary node as the number of
last log received / next log to send was no more increasing.
Then we tried to remove rss with "onmode -d standard" on the Disaster Recovery
server.
The prompt doesn't come back.
So we decided to make a backup on the primary node and restore with
"cat backup_file.bak|ontape -p -t STDIO - v".
After restore it said "Program over".
Then we reboot the machine on the DR but the Informix doesn't come up. Looking
for the logs we see:
19:45:57 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed in
DBSPACETEMP: 'tmpdbs1' 19:45:57 Warning: Invalid
(non-existent/blobspace/disabled) dbspace listed in DBSPACETEMP: 'tmpdbs2'
Now we don't have a replication to the DR. We tried other backups, we tried
also to delete RSS using onmode -d delete ol_rsnode
May anyone help us solve this problem?
Regards
Pedro Neves
Immediately after the restore you have to run the "onmode -d RSS" and wait
for the secondary to sync before you can safely shutdown and restart it.
Art
Art S. Kagel, President and Principal Consultant
ASK Database Management
www.askdbmgt.com
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on the IIUG, nor any other organization with which I am
associated either explicitly, implicitly, or by inference. Neither do
those opinions reflect those of other individuals affiliated with any
entity with which I am affiliated nor those of the entities themselves.
On Tue, Mar 8, 2016 at 5:31 AM, PEDRO NEVES <pedroivomz@gmail.com> wrote:
> Problem description:
>
> Informix 12.10 Enterprise Edition Operating System:
> Read Heat Linux 6.5 64 bit
> Affected part of system: RSS to the Disaster Recovery Server
>
> The problem started with a LOCK database engine caused by FULL logs.
> We tried to fire up "ontape -c &" but it failed. It said that continuous
> backup was already in progress.
> We tried unsuccessfully fire up "ontape -a".
> As informix still LOCKED we tried "onmode -ky". After more or less 15
> minutes
> the command prompt doesn't come back...
> We needed to do a restart of the operating system with "shutdown -r now".
> After reboot the logs was backed up by an "ontape -c &" which is on the
> startup script.
> The instance went up to online.
> Finding on the logs we see the following:
> "11:43:07 Process exited with return code 126: /bin/sh /bin/sh -c
> /opt/informix/1210/etc/alarmprogram.sh 3 20 "Logical Logs are Full --
> Backup
> is Needed." "Logical Log Files are almost Full -- Backup is Needed. In Data
> replication scenario, this could block failure- recovery of the paired
> server."
>
> Looking for the synchronization of the instances with "onstat -g rss" we
> saw
> that the logs were no more been received by secondary node as the number of
> last log received / next log to send was no more increasing.
>
> Then we tried to remove rss with "onmode -d standard" on the Disaster
> Recovery
> server.
>
> The prompt doesn't come back.
>
> So we decided to make a backup on the primary node and restore with
> "cat backup_file.bak|ontape -p -t STDIO - v".
> After restore it said "Program over".
>
> Then we reboot the machine on the DR but the Informix doesn't come up.
> Looking
> for the logs we see:
>
> 19:45:57 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed
> in
> DBSPACETEMP: 'tmpdbs1' 19:45:57 Warning: Invalid
> (non-existent/blobspace/disabled) dbspace listed in DBSPACETEMP: 'tmpdbs2'
>
> Now we don't have a replication to the DR. We tried other backups, we tried
> also to delete RSS using onmode -d delete ol_rsnode
>
> May anyone help us solve this problem?
>
> Regards
>
> Pedro Neves
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--047d7bd76bea14efdb052d884472
Thank you Art Kagel Solved! Best Regards
Related threads
- Posting from the Informix-list
- Migrating from IDS 9.40.UC6 to 11.50.UC3
- Ip for a network session
- questions onstat -g