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
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
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
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
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
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
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
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)
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
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
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
LEARN ABOUT XFREE86
deb-triggers
deb-triggers(5) dpkg suite deb-triggers(5)
NAME
deb-triggers - package triggers
SYNOPSIS
triggers
DESCRIPTION
A package declares its relationship to some trigger(s) by including a triggers file in its control archive (i.e. DEBIAN/triggers during
package creation).
This file contains directives, one per line. Leading and trailing whitespace and everything after the first # on any line will be trimmed,
and empty lines will be ignored.
The trigger control directives currently supported are:
interest trigger-name
interest-await trigger-name
interest-noawait trigger-name
Specifies that the package is interested in the named trigger. All triggers in which a package is interested must be listed using
this directive in the triggers control file. The "noawait" variant does not put the triggering packages in triggers-awaited state.
This should be used when the functionality provided by the trigger is not crucial.
activate trigger-name
activate-await trigger-name
activate-noawait trigger-name
Arranges that changes to this package's state will activate the specified trigger. The trigger will be activated at the start of the
following operations: unpack, configure, remove (including for the benefit of a conflicting package), purge and deconfigure. The
"noawait" variant does not put the triggering packages in triggers-awaited state. This should be used when the functionality
provided by the trigger is not crucial.
If this package disappears during the unpacking of another package the trigger will be activated when the disappearance is noted
towards the end of the unpack. Trigger processing, and transition from triggers-awaited to installed, does not cause activations.
In the case of unpack, triggers mentioned in both the old and new versions of the package will be activated.
Unknown directives are an error which will prevent installation of the package.
The "-noawait" variants should always be favored when possible since triggering packages are not put in triggers-awaited state and can thus
be immediately configured without requiring the processing of the trigger. If the triggering packages are dependencies of other upgraded
packages, it will avoid an early trigger processing run and make it possible to run the trigger only once as one of the last steps of the
upgrade.
The "-noawait" variants are supported since dpkg 1.16.1, and will lead to errors if used with an older dpkg.
The "-await" alias variants are supported since dpkg 1.17.21, and will lead to errors if used with an older dpkg.
SEE ALSO
dpkg-trigger(1), dpkg(1), /usr/share/doc/dpkg-dev/triggers.txt.gz.
1.19.0.5 2018-04-16 deb-triggers(5)