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 DEBIAN
dancer::session::abstract
Dancer::Session::Abstract(3pm) User Contributed Perl Documentation Dancer::Session::Abstract(3pm)
NAME
Dancer::Session::Abstract - abstract class for session engine
SPEC
role
A Dancer::Session object represents a session engine and should provide anything needed to manipulate a session, whatever its storing
engine is.
id The session id will be written to a cookie, by default named "dancer.session", it is assumed that a client must accept cookies to be
able to use a session-aware Dancer webapp. (The cookie name can be change using the "session_name" config setting.)
storage engine
When the session engine is enabled, a before filter takes care to initialize the appropriate session engine (according to the setting
"session").
Then, the filter looks for a cookie named "dancer.session" (or whatever you've set the "session_name" setting to, if you've used it) in
order to retrieve the current session object. If not found, a new session object is created and its id written to the cookie.
Whenever a session call is made within a route handler, the singleton representing the current session object is modified.
After terminating the request, a flush is made to the session object.
DESCRIPTION
This virtual class describes how to build a session engine for Dancer. This is done in order to allow multiple session storage backends
with a common interface.
Any session engine must inherit from Dancer::Session::Abstract and implement the following abstract methods.
Configuration
These settings control how a session acts.
session_name
The default session name is "dancer_session". This can be set in your config file:
setting session_name: "mydancer_session"
session_secure
The user's session id is stored in a cookie. If true, this cookie will be made "secure" meaning it will only be served over https.
session_expires
When the session should expire. The format is either the number of seconds in the future, or the human readable offset from "expires" in
Dancer::Cookie.
By default, there is no expiration.
session_is_http_only
This setting defaults to 1 and instructs the session cookie to be created with the "HttpOnly" option active, meaning that JavaScript will
not be able to access to its value.
Abstract Methods
retrieve($id)
Look for a session with the given id, return the session object if found, undef if not.
create()
Create a new session, return the session object.
flush()
Write the session object to the storage engine.
destroy()
Remove the current session object from the storage engine.
session_name (optional)
Returns a string with the name of cookie used for storing the session ID.
You should probably not override this; the user can control the cookie name using the "session_name" setting.
Inherited Methods
The following methods are not supposed to be overloaded, they are generic and should be OK for each session engine.
build_id
Build a new uniq id.
read_session_id
Reads the "dancer.session" cookie.
write_session_id
Write the current session id to the "dancer.session" cookie.
perl v5.14.2 2012-01-27 Dancer::Session::Abstract(3pm)