Sponsored Content
UNIX Standards and Benchmarks UNIX & LINUX Benchmarks (Version 3.11) UNIX Benchmarks ocs_vtsup: error locking odm database Post 302072066 by MarcoFromLR on Thursday 27th of April 2006 04:13:31 AM
Old 04-27-2006
ocs_vtsup: error locking odm database

Hi ,

I also have this error, I'm not using HACMP but i'm using snapview with and CX300 ( EMC san ).
This error is rising after a snapview command failed to complete ( admsnap activated -s session_name ) .

If someone can gives some detail on this message perhaps it would help me to know why sometimes the snapview session fails to activate.

Thanks.
Marco, From La Rochelle (France).
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Clean an LV out of the ODM

I recently had a disk crash and was not able to clean the dump lv off the disk. Now trying to create new lvdump I am running into errors. My question is how do I remove the old lv out of the ODM? I have tried going through smit and also just rmlv and it cannot find the lv. Yet when I run lslv on... (0 Replies)
Discussion started by: Wamland
0 Replies

2. AIX

Removing devices from ODM

I have replace a couple of hdisks in and old AIX 4 system. I have them assigned to the hdisk numbers previously in the system. When I don an lsvg -p vgname, i see them old devices by device number still come up as missing. I think they are still in the ODM,, how can I remove them? Thanks Mike (5 Replies)
Discussion started by: mhenryj
5 Replies

3. AIX

Script for Comparing VGDA and ODM

Hi there guys, if you have already this script as this will help us in determining of the two are consistent, and if it is not, which is the one correct. Hope you also have for this one.:) (1 Reply)
Discussion started by: sky_lark02
1 Replies

4. AIX

Odm & Lvm

Can i have BIG help on ODM and LVM??? I m new to AIX..... Devang (2 Replies)
Discussion started by: 10aix
2 Replies

5. AIX

remove default gateway on ODM

Hi All, I remove the default gateway by using a command line but I need also to remove it from ODM so that reboot will not trigger it back. How do I remove it from ODM of AIX 5.3? Thanks for any comment you may add. (4 Replies)
Discussion started by: itik
4 Replies

6. Programming

Berkeley database + row level locking

Hello all, Any idea with which release of BDB row/record level locking was introduced? Am sure many/somebody are working with BDB. I tried searching the forum and this what I could get. https://www.unix.com/software-releases-rss-news/88232-berkeley-db-java-edition-3-3-74-default-branch.html... (1 Reply)
Discussion started by: matrixmadhan
1 Replies

7. AIX

Problem with the ODM base

Hi, I gonna try to explain my problem. When I list my tty I have something like that: sa3 is the RAN where the tty are connected. Yesterday I tried to delete every tty from the RAN I had a problem with a tty which was not possible to delete with rmdev -dl, so I had to : - delete it... (0 Replies)
Discussion started by: Castelior
0 Replies

8. OS X (Apple)

error in locking .Xauthority file

Here is my scenario The applications that I want to run are on Linux Server and the client machines that are having problem in locking the .Xauthority files are Macs which share the same domain as that of client solaris machine. i.e. The home directory of particular user on Solaris & the home... (4 Replies)
Discussion started by: mhatrey
4 Replies

9. AIX

Removing object from ODM base

Hello! I did a big mistake and now I have to change the ODM base manually :wall: I had a server of test with 2 VG (rootvg and datavg). I had to test something on it with an other AIX version. So, to be sure to restore it, i did a mksysb before but I had completly forgotten the second vg and... (1 Reply)
Discussion started by: Castelior
1 Replies

10. AIX

How to add the attribute to odm if it contains negative value?

Hi All, I am trying to add odm_wait attribute to CuAt programatically using putattr(&pCuAt). I was able to add when the odm_wait has positive value . But, I am facing issues when the odm_wait has negative value As per IBM, these are the odm_wait possible values #define ODM_WAIT -1 /*... (3 Replies)
Discussion started by: Sachin1987
3 Replies
SUNW.derby(5)						     Sun Cluster Miscellaneous						     SUNW.derby(5)

NAME
SUNW.derby, derby - resource type implementation of the Java DB database DESCRIPTION
SUNW.derby is the failover resource type that enables you to use the Java DB database with Sun Cluster. The Java DB database is based on the Derby database. For information about the database, see http://db.apache.org/derby/. The extension properties associated with the SUNW.derby resource type are as follows: Child_mon_level(integer) Provides control over the processes that are monitored through the process monitor facility. This property denotes the level to which the forked children processes are monitored. Omitting this property or setting this property to the default value is the same as omit- ting the -C option for pmfadm(1M) (all children and their descendents are monitored). Category Optional Default -1 Tunable At creation DB_path(string) Specifies the location of the data file for the Java DB database. The value for DB_path is a string specifying PATH. The specified path should be a path controlled by your chosen storage, for example HAStoragePlus. Category Mandatory Default -1 Tunable At creation DB_port(integer) Specifies the port for the Java DB database. Category Mandatory Default 1527 Tunable At creation DB_probe_port(integer) Specifies the port that Sun Cluster uses to test the health of the server for the Java DB database. Category Mandatory Default 1528 Tunable At creation Monitor_retry_count(integer) Controls fault-monitor restarts. The property indicates the number of times that the process monitor facility restarts the fault moni- tor. The property corresponds to the -n option passed to the pmfadm(1M) command. The Resource Group Manager (RGM) counts the number of restarts in a specified time window (see Monitor_retry_interval). Note that Monitor_retry_count refers to the restarts of the fault monitor itself, not of the SUNW.derby resource. Category Optional Default 2 Tunable Anytime Monitor_retry_interval(integer) Indicates the time window in minutes during which the RGM counts fault-monitor failures. The property corresponds to the -t option passed to the pmfadm(1M) command. If the number of times that the fault monitor fails exceeds the value of the extension property Mon- itor_retry_count, the process monitor facility does not restart the fault monitor. Category Optional Default 2 minutes Tunable Anytime Probe_timeout(integer) Specifies the timeout value, in seconds, for the probe command. Category Optional Default 30 seconds Tunable Anytime SEE ALSO
pmfadm(1M) Sun Cluster 3.2 12 Nov 2005 SUNW.derby(5)
All times are GMT -4. The time now is 06:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy