option 81 backup issue

[phones1]

Hi Guys

I've been away a couple of weeks to the following issue. I have an opt81 rls 5 that is up & running but isn't completing the back up correctly. below is the log let me know your ideas on how to fix.

RECORD COUNT = 971
DATADUMP COMPLETE



Starting CCBR backup to "/u/ccbr/ccbr.gz":
CCBR backup failed!

TEMU020 Errno 0x380003: Failure opening file /u/db/node


Backing up reten.bkp

TEMU111 Error occured backing up internal data base

Starting database backup
to local Removable Media Device
Database backup failed!

TEMU020 Errno 0x380003: Failure opening file /u/db/node

EDD007


.
EDD000


.
TEMU062 Database backup to removable media failed

ld 43
BACKGROUND SESSION 0 ABORTED.
EDD000


.dat

DATABASE ISSUE DATE(d/m/y)/TIME SIZE(recs) SEQNO
Main 550J 12/05/2016 at 09:55:05 972 3987
Secondary 550J 12/05/2016 at 09:49:37 972 3986
Backup database not accessible.
Current backup is on RMD: /cf2/backup/single/

TEMU020 Errno 0x380003: Failure opening file /cf2/backup/single/config.rec/

CIOD157 INFO: FMD 0 is ACTIVE, RDUN is ENABLED

.
EDD00


pdt> ll

Directory of '/u':

SIZE DATE TIME NAME
---------- ----------- -------- ------------
64 May-12-2016 09:55:36 system.ini
4096 May-05-2016 15:17:18 ccbr <DIR>
4096 May-12-2016 09:55:34 ACCOUNTS <DIR>
4096 May-12-2016 09:55:46 DB <DIR>
4096 May-12-2016 09:55:42 PATCH <DIR>
4096 May-12-2016 09:55:24 SMP_DB <DIR>

pdt> cd db
pdt> ll

Directory of '/u/db':

SIZE DATE TIME NAME
---------- ----------- -------- ------------
probs accessing entry: /u/db (3670031)
probs accessing entry: /u/db//u/patch. (3670019)
probs accessing entry: /u/db//u/patch. (3670019)
probs accessing entry: /u/db//u/patch. (3670019)
probs accessing entry: /u/db//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch.//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch.//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch.//u/patch.//u/patch.//u/patch. (3670019)
probs accessing entry: /u/db//u/patch.//u/patch.//u/patch.//u/patch.//u/patch.//u/patch. (3670019)

pdt>


Thanks


Phones1

Remember if it doesn't work hit it harder

Scott UK

 

[KCFLHRC]

My first guess is you have some database corruption. Probably take Avaya to fix it.

 

[Firebird Scrambler]

I found this below

After Upgrade to 05.50 CPP4 CPPM Rls 05.50, Backup fails with TEMU0111 & TEMU020

Problem :
After Upgrade to 05.50 the LD43 Backup fails with TEMU0111 & TEMU020

Additional info :
Getting errors during the backup complaining that the /u/db/ntp.db file is missing or can't write to it
Also same for the /u/ccbr/ccbr.gz file

Couldn't find the files on the 05.50 RMD so we FTP'ed the files off the MOC House Switch and installed them into the /u/ccbr & /u/db directories.
This solved the problem





Firebird Scrambler
Nortel Meridian 1 / Succession and BCM / Norstar Programmer in the UK
Advance knowledge on BCM support

http://www.linkedin.com/in/davidbromley

 

[KCFLHRC]

CS1000: LD 43: EDD (DATADUMP) results in EDD007 TEMU020 Errno 0x380003: Failure opening file /u/db/zone.tmp
Rate Content Rate this Page

Doc ID: SOLN209199
Version: 3.0
Status: Published
Published date: 29 Aug 2012
Updated: 02 Dec 2014
Author:
Stanley Martz

Details

System outputs the following error messages during a datadump.

TEMU020 Errno 0x380003: Failure opening file /u/db/zone.tmp
TEMU018 Failed to dump specific data - /u/db
TEMU017 Error dumping ERL database - failed to open file /u/db/erl.tmp for writing (errno 0x380003)
TEMU024 PORT_STATE_MGTError dumping ELIN database - failed to open file for writing (errno 0x380003) - /u/db/elin.tmp
TEMU018 Failed to dump specific data - elin.db
TEMU020 Errno 0x380003: Failure opening file u/db/ntp.tmp
TEMU018 Failed to dump specific data - /u/db
TEMU020 Errno 0x380003: Failure opening file /u/db/cdmzones.tmp
TEMU027 Error dumping ZBD Numbering Zones database - cdmzones.db
TEMU026 Error dumping ZBD database - CDM failed to open file /u/db/cdm.tmp for writing (errno 0x380003)
TEMU018 Failed to dump specific data - cdm.db
TEMU020 Errno 0x380003: Failure opening file /u/db/msczsrn.tmp
TEMU027 Error dumping ZBD Numbering Zones database - msczsrn.db
TEMU020 Errno 0x380003: Failure opening file /u/db/portstate.tmp
TEMU018 Failed to dump specific d
TEMU018 Failed to dump specific data - subnet.db
TEMU019 Error dumping Subnet LIS database - failed to open file for writing (errno 0x380003) - /u/db/subnet.tmp
TEMU018 Failed to dump specific data - erl.db

Cannot create a file or sub-directory in directory /u/db
Problem Clarification

Call Server fails to data dump.
Cause

Possibly a permissions problem with directory /u/db
Solution

I renamed /u/db to /u/dbold, created a new /u/db directory, then copied all files and sub-directories from /u/dbold to /u/db using the following command:

PDT> dosFsCopyDir /u/dbold /u/db