ACR : cannot find eware database

Doc ID    SOLN289341
Version:    2.0
Status:    Published
Published date:    15 Jan 2021
Created Date:    13 May 2016
Author:   
chengdongzhao
 

Details

ACR version 12.
CRS /var partition full.

CRS log shows cannot find eware database. the command psql -l shows no eware database exists in Postgresql.

Database log shows:
database "eware" does not exist
The database subdirectory "base/25620" is missing

Problem Clarification

the first problem is ACR is down

we cannot access the portal

from the ACR logs i found error

2016-04-27 22:31:29,718 [pool-2-thread-1] DEBUG com.swhh.cs.c.j - Current Database version is 0 2016-04-27 22:31:29,718 [pool-2-thread-1] INFO com.swhh.cs.c.j - Upgrading database from V0 to V1 using com.swhh.cscm.b.a@4f2d26d2 2016-04-27 22:31:29,718 [pool-2-thread-1] ERROR com.swhh.cscm.b.a - Cannot upgrade from V0 2016-04-27 22:31:29,719 [pool-2-thread-1] FATAL com.swhh.cs.c.j - Invalid Database version version 0 2016-04-27 22:31:29,719 [pool-2-thread-1] FATAL com.swhh.cs.n.b - startService w

reboot server and restart service cscm has be done
but we still cannot access the ACR portal

status cscm is running
but we can't playback recording

Cause

CRS server /var partition full, user incorrectly removed eware database from Postgresql DB, it caused CRS cannot access DB, and user cannot login ACR web interface.

Or

Due to /VAR partition full the Eware DB get corrupted

Solution

1. link Database data to /calls partition, create eware Database, reuse the original oid path to new eware database, CRS can correct connect to eware Database and working fine, recording data which pending in ACR jobqueue can also upload to CRS.
a. link database data to /calls partition:
•    Logon as root
1.    cd /calls
2.    mkdir pgsql
3.    chown postgres pgsql
4.    chgrp postgres pgsql
 
•    Ensure the DB and CSCM are stopped
1.    service cscm stop
2.    service rhdb stop or service postgresql stop

•    tar the contents of the /var/lib/pgsql/data folder to a tar file in /calls/pgsql
1.    cd /var/lib/pgsql
2.    tar -cvf /calls/pgsql/tempfile.tar data
 
•    untar it back to /calls/pgsql/data
1.    cd /calls/pgsql
2.    tar -xvf /calls/pgsql/tempfile.tar

•    Rename the /var/lib/pgsql/data folder to olddata
1.    cd /var/lib/pgsql
2.    mv data olddata

•    Create a symbolic link from /calls/pgsql/data to /var/lib/pgsql/data
1.    ln -s /calls/pgsql/data /var/lib/pgsql/data
b. create eware database: createdb eware
c. after eware created, there will be a new oid path generated in ../data/base, change the new oid path with another name, change the old oid path (for eware, 16384) name to the new oid path name. Then start postgres, start ACR service, system will working fine and old data can be get back.
2. Suggest user extend CRS /var partition and move Database data back to /var partition.


Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy