Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Respected Contributor.. Rakesh kumar Respected Contributor..
Respected Contributor..
107 views

SA database issue cannot start "vaultdaemon "dependency check failed

Jump to solution

Dear Team,

 

We are facing issue on SA Linux core server .

 

cannot start "vaultdaemon "dependency check failed

we have checked listen port it is working properly and firewall stopped also but getting the same 

we have run the /etc/init.d/opsware -oracle start but not slowed still.

 

Regards,

Rakesh

0 Likes
1 Solution

Accepted Solutions
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: SA database issue cannot start "vaultdaemon "dependency check failed

Jump to solution

You should make sure you Oracle is up and listening.

You can use tnsping or sqlplus to manually connect to the SA DB instance to make sure it is up.

0 Likes
2 Replies
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: SA database issue cannot start "vaultdaemon "dependency check failed

Jump to solution

You should make sure you Oracle is up and listening.

You can use tnsping or sqlplus to manually connect to the SA DB instance to make sure it is up.

0 Likes
Respected Contributor.. Rakesh kumar Respected Contributor..
Respected Contributor..

Re: SA database issue cannot start "vaultdaemon "dependency check failed

Jump to solution

 

[root@ndcrrsadb bin]# ./lsnrctl status

 

LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 10-SEP-2019 08:11:06

 

Copyright (c) 1991, 2014, Oracle.  All rights reserved.

 

Message 1053 not found; No message file for product=network, facility=TNSMessage 1020 not found; No message file for product=network, facility=TNSMessage 1021 not found; No message file for product=network, facility=TNSMessage 1022 not found; No message file for product=network, facility=TNSMessage 1023 not found; No message file for product=network, facility=TNSMessage 1026 not found; No message file for product=network, facility=TNSMessage 1034 not found; 

 

After commenting the irrelevant entry truth.SACORE2 and restarting the listener – now the lsnrctl status  ok

 

Service "truth" has 2 instance(s).

 Instance "truth", status UNKNOWN, has 1 handler(s) for this service...

  Instance "truth", status READY, has 1 handler(s) for this service...

The command completed successfully

 

Sqlplus connect to the truth instance was successful

 

Now all SA services started successfully.  thanks for the suggestion .

 

Regards,

Rakesh

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.