Oracle Communications User Data Repository (OCUDR) Rel 12.2 : NOAM Servers Have Not Come Up When Autobackup.tar File Is Used For DB Restore in OCUDR.

Asset ID:	1-72-2353427.1
Update Date:	2018-03-07
Keywords:

Solution Type Problem Resolution Sure

Solution 2353427.1 : Oracle Communications User Data Repository (OCUDR) Rel 12.2 : NOAM Servers Have Not Come Up When Autobackup.tar File Is Used For DB Restore in OCUDR.

Applies to:

Oracle Communications User Data Repository - Version UDR 12.2 and later
Information in this document applies to any platform.

Symptoms

Restore the backup using auto generated system Backup file, NOAM is not coming up and we need to manually bring up the NOAM

File used for backup:
====================
Any files which is present in this path "/var/TKLC/db/filemgmt/backup/"

Changes

1) Perform DB Restore through NOAM GUI (Status& Manage ->Database )
2) Select the Active NOAM and Use the Provisioning Auto Backup file to restore the database.

Cause

Observation:
============
1) After some time the NOAM VIP was no more pingable.
2) Standby NOAM Server moves to an OOS state.
3) The Active NOAM server is not listing any servers (status&manage ->Servers) and not allowing to enable global provisioning or Replication. (The NodeInfo table is empty)
4) Both the NOAM-A and NOAM-B are accessible through XMI and CLI.
5) The HA role of all the servers are "Unavailable".
6) After the restore "MAINT_CMD_failed" error was observed and restore was unsuccessful.

Solution

Workaround :
If this issue occurs execute the following steps
[1] tar -tvf <backup file>
[2] touch a file under UpdateLog directory
[3] tar cvf <tar file name> metabdata/* ./*
[4] perform restore.

This issue will be fixed permanently in OCUDR Rel 12.4

References

<BUG:24664321> - NO SERVERS HAVE NOT COME UP WHEN AUTOBACKUP.TAR FILE IS USED FOR DB RESTORE

Attachments

This solution has no attachment