Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Unified Presence 9 Cisco DB Error

Hello, after server power loss on Presence pub 9.1.1.41900-1, we have error:

A Cisco DB[STOPPED]  Component is not running

-------------------- utils dbreplication status --------------------
Database is down; please restart the database before reattempting a status check

file view activelog cm/log/informix/ccm.log

23:34:37 IBM Informix Dynamic Server Started.

Wed Jun 14 23:34:38 2017

23:34:38 Event alarms enabled. ALARMPROG = '/usr/local/cm/bin/ccmalarmprogram.sh'
23:34:38 Booting Language <c> from module <>
23:34:38 Loading Module <CNULL>
23:34:38 Booting Language <builtin> from module <>
23:34:38 Loading Module <BUILTINNULL>
23:34:38 SQLTRACE: SQL History Tracing set to 2000 SQL statements.
23:34:44 Waiting 600 seconds for startup to complete.
23:34:44 DR: DRAUTO is 0 (Off)
23:34:44 DR: ENCRYPT_HDR is 0 (HDR encryption Disabled)

options: q=quit, n=next, p=prev, b=begin, e=end (lines 45881 - 45900 of 46102) :
23:34:44 Event notification facility epoll enabled.
23:34:44 IBM Informix Dynamic Server Version 11.50.UC9XD Software Serial Number AAA#B000000
23:34:45 (4) connection rejected - no calls allowed for sqlexec
23:34:45 (5) connection rejected - no calls allowed for sqlexec
23:34:45 (6) connection rejected - no calls allowed for sqlexec
23:34:45 (7) connection rejected - no calls allowed for sqlexec
23:34:45 (8) connection rejected - no calls allowed for sqlexec
23:34:45 (9) connection rejected - no calls allowed for sqlexec
23:34:45 (10) connection rejected - no calls allowed for sqlexec
23:34:45 (11) connection rejected - no calls allowed for sqlexec
23:34:45 (12) connection rejected - no calls allowed for sqlexec
23:34:45 (13) connection rejected - no calls allowed for sqlexec
23:34:45 (14) connection rejected - no calls allowed for sqlexec
23:34:45 (15) connection rejected - no calls allowed for sqlexec
23:34:45 (16) connection rejected - no calls allowed for sqlexec
23:34:45 (17) connection rejected - no calls allowed for sqlexec
23:34:45 (18) connection rejected - no calls allowed for sqlexec
23:34:45 (19) connection rejected - no calls allowed for sqlexec
23:34:45 (20) connection rejected - no calls allowed for sqlexec
23:34:45 (21) connection rejected - no calls allowed for sqlexec

options: q=quit, n=next, p=prev, b=begin, e=end (lines 45901 - 45920 of 46102) :
23:34:45 (22) connection rejected - no calls allowed for sqlexec
23:34:45 (23) connection rejected - no calls allowed for sqlexec
23:34:45 (24) connection rejected - no calls allowed for sqlexec
23:34:45 (25) connection rejected - no calls allowed for sqlexec
23:34:45 (26) connection rejected - no calls allowed for sqlexec
23:34:45 (27) connection rejected - no calls allowed for sqlexec
23:34:45 (28) connection rejected - no calls allowed for sqlexec
23:34:45 (29) connection rejected - no calls allowed for sqlexec
23:34:45 (30) connection rejected - no calls allowed for sqlexec
23:34:45 (31) connection rejected - no calls allowed for sqlexec
23:34:45 (32) connection rejected - no calls allowed for sqlexec
23:34:45 (33) connection rejected - no calls allowed for sqlexec
23:34:45 (34) connection rejected - no calls allowed for sqlexec
23:34:45 (35) connection rejected - no calls allowed for sqlexec
23:34:45 (36) connection rejected - no calls allowed for sqlexec
23:34:45 (37) connection rejected - no calls allowed for sqlexec
23:34:45 (38) connection rejected - no calls allowed for sqlexec
23:34:45 (39) connection rejected - no calls allowed for sqlexec
23:34:45 (40) connection rejected - no calls allowed for sqlexec
23:34:45 (41) connection rejected - no calls allowed for sqlexec

options: q=quit, n=next, p=prev, b=begin, e=end (lines 45921 - 45940 of 46102) :
23:34:46 (42) connection rejected - no calls allowed for sqlexec
23:34:46 IBM Informix Dynamic Server Initialized -- Shared Memory Initialized.

23:34:46 Started 1 B-tree scanners.
23:34:46 B-tree scanner threshold set at 5000.
23:34:46 B-tree scanner range scan size set to -1.
23:34:46 B-tree scanner ALICE mode set to 6.
23:34:46 B-tree scanner index compression level set to med.
23:34:46 Physical Recovery Started at Page (1:7261).
23:34:46 Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored.
23:34:46 Logical Recovery Started.
23:34:46 10 recovery worker threads will be started.
23:34:46 Checkpoint Record not Found in Logical Log.
23:34:47 Cannot Rollforward from Checkpoint.
23:34:48 oninit: Fatal error in shared memory initialization

23:34:48 IBM Informix Dynamic Server Stopped.

What we can do to restore server database? 

2 REPLIES
Cisco Employee

You probably want to call TAC

You probably want to call TAC for this, or restore your server from a backup.

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
New Member

After recovery disk file

After recovery disk file-check, have same error

file view activelog cm/log/informix/ccm.log

oninit: fatal error in shared memory initializaion

12
Views
0
Helpful
2
Replies