Lock never expires

Hello,
About once a month it happens that a lock of a "ENV->txn_checkpoint( ENV, 0, 0, 0 )"
simply blocks and does not expire. In the down below `db_stat -CA` the lock is kept
more than 5 hours ("*expires 02-01-00:03:07.151182000*"), until I could do a
`db_recover` and bring BDB back to life.
The environment is set to:
ENV->set_lk_detect( ENV, DB_LOCK_OLDEST );
ENV->set_timeout( ENV, 60 * 1000 * 1000, DB_SET_LOCK_TIMEOUT );
ENV->set_timeout( ENV, 60 * 1000 * 1000, DB_SET_TXN_TIMEOUT );
Once a minute i do:
ENV->lock_detect( ENV, 0, DB_LOCK_OLDEST, &rejected );
ENV->lock_detect( ENV, 0, DB_LOCK_EXPIRE, &rejected );
From "00:03:00" to "05:22:00" I have seen many rejected locks but the perpetual
lock "80b7b6fb" (PID:32179) from the txn_checkpoint() was never brocken.
Thanks
Josef
I had to remove quite a lot from `db_stat -CA` not to exceed 30000 chars:
Default locking region information:
435392 Last allocated locker ID
0x7fffffff Current maximum unused locker ID
9   Number of lock modes
32768   Maximum number of locks possible
32768   Maximum number of lockers possible
32768   Maximum number of lock objects possible
80 Number of lock object partitions
6401    Number of current locks
7214    Maximum number of locks at any one time
283 Maximum number of locks in any one bucket
0   Maximum number of locks stolen by for an empty partition
0   Maximum number of locks stolen for any one partition
6397    Number of current lockers
6397    Maximum number of lockers at any one time
159 Number of current lock objects
1413    Maximum number of lock objects at any one time
3   Maximum number of lock objects in any one bucket
0   Maximum number of objects stolen by for an empty partition
0   Maximum number of objects stolen for any one partition
3231M   Total number of locks requested (3231111865)
3231M   Total number of locks released (3231086892)
1928    Total number of locks upgraded
423527 Total number of locks downgraded
70117   Lock requests not available due to conflicts, for which we waited
18553   Lock requests not available due to conflicts, for which we did not wait
1   Number of deadlocks
60M Lock timeout value (60000000)
34509   Number of locks that have timed out
60M Transaction timeout value (60000000)
4514    Number of transactions that have timed out
17MB 360KB The size of the lock region
24M The number of partition locks that required waiting (0%)
8468160 The maximum number of times any partition lock was waited for (0%)
3545    The number of object queue operations that required waiting (0%)
57474   The number of locker allocations that required waiting (0%)
64 The number of region locks that required waiting (0%)
3   Maximum hash bucket length
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lock REGINFO information:
Lock    Region type
5   Region ID
__db.005    Region name
0x925f1000 Region address
0x925f10c4 Region primary address
0   Region maximum allocation
0   Region allocated
Region allocations: 169 allocations, 0 failures, 0 frees, 1 longest
Allocations by power-of-two sizes:
1KB   2
2KB   0
4KB   0
8KB   1
16KB   0
32KB   160
64KB   0
128KB   0
256KB   0
512KB   2
1024KB 0
REGION_JOIN_OK Region flags
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lock region parameters:
65561   Lock region region mutex [64/12M 0% 16646/3074799296] <wakeups 10/11>
32771   locker table size
32771   object table size
724 obj_off
3020556 locker_off
0   need_dd
next_timeout: 02-01-05:22:01.599805000
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lock conflict matrix:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Locks grouped by lockers:
Locker   Mode      Count Status ----------------- Object ---------------
[...] sniped rows starting with a ' ' [...]
80b88442 dd= 6 locks held 1    write locks 0    pid/thread 16452/3064153872 priority 100       expires 02-01-05:22:22.246053000 lk expires 02-01-05:22:22.246053000
80b88442 READ          1 WAIT    mediastatistic.db         page          0
80b88442 READ          1 HELD    mediastatistic.db         handle        0
80b88445 dd= 1 locks held 1    write locks 0    pid/thread 16634/3063199504 priority 100       expires 02-01-05:23:01.279172000 lk expires 02-01-05:23:01.279172000
80b88445 READ          1 WAIT    mediastatistic.db         page          0
80b88445 READ          1 HELD    mediastatistic.db         handle        0
80b7b6fb dd=4548 locks held 3    write locks 3    pid/thread 32179/3064153872 priority 100       expires 02-01-00:03:07.151182000
80b7b6fb WRITE         1 HELD    queue_status.db           page          1
80b7b6fb WAS_WRITE     1 HELD    queue_user.db             page         15
80b7b6fb WAS_WRITE     2 HELD    queue.db                  page       3417
80b883ee dd=57 locks held 5    write locks 5    pid/thread 21788/3063506704 priority 100       expires 02-01-05:22:02.091000000 lk expires 02-01-05:22:02.091000000
80b883ee READ          1 WAIT    queue_status.db           page          1
80b883ee WAS_WRITE     1 HELD    queue_process.db          page          1
80b883ee WAS_WRITE     1 HELD    queue_user.db             page          2
80b883ee WAS_WRITE     1 HELD    queue_media.db            page          1
80b883ee WAS_WRITE     1 HELD    queue_usercreated.db      page          2
80b883ee WAS_WRITE     2 HELD    queue.db                  page        620
80b883ef dd=56 locks held 0    write locks 0    pid/thread 31279/3063117584 priority 100       expires 02-01-05:22:02.094269000 lk expires 02-01-05:22:02.094269000
80b883ef WRITE         1 WAIT    queue.db                  page       3417
80b883f4 dd=53 locks held 4    write locks 4    pid/thread 3880/3062753040 priority 100       expires 02-01-05:22:02.112277000 lk expires 02-01-05:22:02.112277000
80b883f4 WRITE         1 WAIT    queue_process.db          page          1
80b883f4 WAS_WRITE     1 HELD    queue_user.db             page          5
80b883f4 WAS_WRITE     1 HELD    queue_usercreated.db      page         10
80b883f4 WAS_WRITE     1 HELD    queue_useractive.db       page          1
80b883f4 WAS_WRITE     2 HELD    queue.db                  page       1589
80b883f6 dd=52 locks held 1    write locks 1    pid/thread 6752/3063416592 priority 100       expires 02-01-05:22:02.120049000 lk expires 02-01-05:22:02.120049000
80b883f6 WRITE         1 WAIT    queue_usercreated.db      page         10
80b883f6 WAS_WRITE     2 HELD    queue.db                  page        359
80b88401 dd=50 locks held 2    write locks 2    pid/thread 15858/3063584528 priority 100       expires 02-01-05:22:02.176324000 lk expires 02-01-05:22:02.176324000
80b88401 WRITE         1 WAIT    mediastatistic.db         page          0
80b88401 WRITE         1 HELD    mediastatistic.db         page     127272
80b88401 WAS_WRITE     1 HELD    mediastatistic.db         page     127272
80b88407 dd=48 locks held 0    write locks 0    pid/thread 15053/3063318288 priority 100       expires 02-01-05:22:02.209851000 lk expires 02-01-05:22:02.209851000
80b88407 WRITE         1 WAIT    mediastatistic.db         page     127272
80b88408 dd=47 locks held 0    write locks 0    pid/thread 23242/3064022800 priority 100       expires 02-01-05:22:02.213305000 lk expires 02-01-05:22:02.213305000
80b88408 WRITE         1 WAIT    queue.db                  page        620
80b88409 dd=46 locks held 0    write locks 0    pid/thread 14254/3064424208 priority 100       expires 02-01-05:22:02.218573000 lk expires 02-01-05:22:02.218573000
80b88409 WRITE         1 WAIT    queue.db                  page        359
80b8840b dd=45 locks held 0    write locks 0    pid/thread 3639/3063240464 priority 100       expires 02-01-05:22:02.225444000 lk expires 02-01-05:22:02.225444000
80b8840b READ          1 WAIT    queue_useractive.db       page          1
80b8840c dd=44 locks held 0    write locks 0    pid/thread 15783/3063670544 priority 100       expires 02-01-05:22:02.225574000 lk expires 02-01-05:22:02.225574000
80b8840c WRITE         1 WAIT    mediastatistic.db         page     127272
80b8840e dd=43 locks held 1    write locks 1    pid/thread 23404/3062658832 priority 100       expires 02-01-05:22:02.232718000 lk expires 02-01-05:22:02.232718000
80b8840e WRITE         1 WAIT    queue_usercreated.db      page         10
80b8840e WAS_WRITE     2 HELD    queue.db                  page       2439
80b88414 dd=40 locks held 0    write locks 0    pid/thread 15532/3062458128 priority 100       expires 02-01-05:22:02.339357000 lk expires 02-01-05:22:02.339357000
80b88414 WRITE         1 WAIT    mediastatistic.db         page     127272
80b88415 dd=39 locks held 0    write locks 0    pid/thread 12934/3063731984 priority 100       expires 02-01-05:22:02.346746000 lk expires 02-01-05:22:02.346746000
80b88415 WRITE         1 WAIT    queue.db                  page        359
80b88416 dd=38 locks held 2    write locks 2    pid/thread 15896/3063670544 priority 100       expires 02-01-05:22:02.411124000 lk expires 02-01-05:22:02.411124000
80b88416 WRITE         1 WAIT    mediastatistic.db         page          0
80b88416 WRITE         1 HELD    mediastatistic.db         page     126767
80b88416 WAS_WRITE     1 HELD    mediastatistic.db         page     126767
80b88417 dd=37 locks held 0    write locks 0    pid/thread 14569/3063420688 priority 100       expires 02-01-05:22:02.426556000 lk expires 02-01-05:22:02.426556000
80b88417 WRITE         1 WAIT    mediastatistic.db         page     127272
80b88419 dd=36 locks held 1    write locks 1    pid/thread 1345/3063146256 priority 100       expires 02-01-05:22:02.538765000 lk expires 02-01-05:22:02.538765000
80b88419 READ          1 WAIT    queue_useractive.db       page          1
80b88419 WAS_WRITE     2 HELD    queue.db                  page       1585
80b8841e dd=35 locks held 0    write locks 0    pid/thread 29349/3063453456 priority 100       expires 02-01-05:22:02.618734000 lk expires 02-01-05:22:02.618734000
80b8841e WRITE         1 WAIT    queue.db                  page       3417
80b8841f dd=34 locks held 0    write locks 0    pid/thread 6200/3063899920 priority 100       expires 02-01-05:22:02.622259000 lk expires 02-01-05:22:02.622259000
80b8841f WRITE         1 WAIT    queue.db                  page        359
80b88420 dd=33 locks held 0    write locks 0    pid/thread 10999/3062880016 priority 100       expires 02-01-05:22:02.622284000 lk expires 02-01-05:22:02.622284000
80b88420 WRITE         1 WAIT    queue.db                  page        359
80b88421 dd=32 locks held 1    write locks 1    pid/thread 15349/3062720272 priority 100       expires 02-01-05:22:02.629291000 lk expires 02-01-05:22:02.629291000
80b88421 WRITE         1 WAIT    queue_usercreated.db      page          6
80b88421 WAS_WRITE     2 HELD    queue.db                  page        309
80b88422 dd=31 locks held 0    write locks 0    pid/thread 15969/3062982416 priority 100       expires 02-01-05:22:02.632325000 lk expires 02-01-05:22:02.632325000
80b88422 WRITE         1 WAIT    mediastatistic.db         page     127272
80b88423 dd=30 locks held 2    write locks 2    pid/thread 21631/3061966608 priority 100       expires 02-01-05:22:02.634340000 lk expires 02-01-05:22:02.634340000
80b88423 WRITE         1 WAIT    queue_media.db            page          1
80b88423 WAS_WRITE     1 HELD    queue_usercreated.db      page          6
80b88423 WAS_WRITE     2 HELD    queue.db                  page       3058
80b88424 dd=29 locks held 0    write locks 0    pid/thread 1500/3062712080 priority 100       expires 02-01-05:22:02.648949000 lk expires 02-01-05:22:02.648949000
80b88424 WRITE         1 WAIT    queue.db                  page       1585
80b88425 dd=28 locks held 0    write locks 0    pid/thread 15274/3063731984 priority 100       expires 02-01-05:22:02.681320000 lk expires 02-01-05:22:02.681320000
80b88425 WRITE         1 WAIT    mediastatistic.db         page     127272
80b88427 dd=27 locks held 0    write locks 0    pid/thread 5970/3063367440 priority 100       expires 02-01-05:22:02.722208000 lk expires 02-01-05:22:02.722208000
80b88427 WRITE         1 WAIT    queue.db                  page        359
80b88428 dd=26 locks held 0    write locks 0    pid/thread 21321/3063117584 priority 100       expires 02-01-05:22:02.736108000 lk expires 02-01-05:22:02.736108000
80b88428 WRITE         1 WAIT    queue.db                  page        620
80b8842a dd=25 locks held 0    write locks 0    pid/thread 14491/3063039760 priority 100       expires 02-01-05:22:02.874833000 lk expires 02-01-05:22:02.874833000
80b8842a WRITE         1 WAIT    mediastatistic.db         page     127272
80b8842b dd=24 locks held 20   write locks 19   pid/thread 2067/3064137488 priority 100       expires 02-01-05:22:02.881527000 lk expires 02-01-05:22:02.881527000
80b8842b WRITE         1 WAIT    queue.db                  page        359
80b8842b WAS_WRITE     1 HELD    mediareferer.db           page      11187
80b8842b WAS_WRITE     2 HELD    mediadocument.db          page      91943
80b8842b WAS_WRITE     2 HELD    mediafile.db              page     182304
80b8842b WAS_WRITE     2 HELD    mediafile_livestream.db   page          1
80b8842b WAS_WRITE     1 HELD    mediastatistic.db         page          0
80b8842b WAS_WRITE     2 HELD    mediastatistic.db         page     127441
80b8842b WAS_WRITE     1 HELD    media.db                  page      59394
80b8842b WAS_WRITE     1 HELD    media.db                  page          1
80b8842b WAS_WRITE     1 HELD    media_personalpublished.db page          1
80b8842b WAS_WRITE     2 HELD    media_personalpublished.db page          6
80b8842b WAS_WRITE     1 HELD    media_personallanguagetypepublished.db page          1
80b8842b WAS_WRITE     2 HELD    media_personallanguagetypepublished.db page          8
80b8842b WAS_WRITE     1 HELD    media_personaltypepublished.db page          1
80b8842b WAS_WRITE     2 HELD    media_personaltypepublished.db page          6
80b8842b WAS_WRITE     1 HELD    media_personallanguagepublished.db page          1
80b8842b WAS_WRITE     2 HELD    media_personallanguagepublished.db page          6
80b8842b WAS_WRITE     1 HELD    media_language.db         page          7
80b8842b WAS_WRITE     1 HELD    media_user.db             page        175
80b8842b READ          1 HELD    media.db                  page      60382
80b8842b WAS_WRITE     3 HELD    media.db                  page      60382
80b8842c dd=23 locks held 2    write locks 2    pid/thread 16079/3062560528 priority 100       expires 02-01-05:22:02.914927000 lk expires 02-01-05:22:02.914927000
80b8842c WRITE         1 WAIT    mediastatistic.db         page          0
80b8842c WRITE         1 HELD    mediastatistic.db         page     127104
80b8842c WAS_WRITE     1 HELD    mediastatistic.db         page     127104
80b8842d dd=22 locks held 0    write locks 0    pid/thread 15946/3063805712 priority 100       expires 02-01-05:22:02.917872000 lk expires 02-01-05:22:02.917872000
80b8842d WRITE         1 WAIT    mediastatistic.db         page     127104
80b8842e dd=21 locks held 0    write locks 0    pid/thread 16391/3062630160 priority 100       expires 02-01-05:22:02.933898000 lk expires 02-01-05:22:02.933898000
80b8842e WRITE         1 WAIT    mediastatistic.db         page     127104
80b8842f dd=20 locks held 0    write locks 0    pid/thread 14468/3064334096 priority 100       expires 02-01-05:22:02.980551000 lk expires 02-01-05:22:02.980551000
80b8842f WRITE         1 WAIT    mediastatistic.db         page     127272
80b88430 dd=19 locks held 2    write locks 2    pid/thread 15108/3063666448 priority 100       expires 02-01-05:22:03.005311000 lk expires 02-01-05:22:03.005311000
80b88430 WRITE         1 WAIT    mediastatistic.db         page          0
80b88430 WRITE         1 HELD    mediastatistic.db         page     126936
80b88430 WAS_WRITE     1 HELD    mediastatistic.db         page     126936
80b88431 dd=18 locks held 0    write locks 0    pid/thread 15605/3064194832 priority 100       expires 02-01-05:22:03.005324000 lk expires 02-01-05:22:03.005324000
80b88431 WRITE         1 WAIT    mediastatistic.db         page     126936
80b88432 dd=17 locks held 2    write locks 2    pid/thread 15550/3064497936 priority 100       expires 02-01-05:22:03.088119000 lk expires 02-01-05:22:03.088119000
80b88432 WRITE         1 WAIT    mediastatistic.db         page          0
80b88432 WRITE         1 HELD    mediastatistic.db         page     126091
80b88432 WAS_WRITE     1 HELD    mediastatistic.db         page     126091
80b88433 dd=16 locks held 0    write locks 0    pid/thread 14983/3062826768 priority 100       expires 02-01-05:22:03.110238000 lk expires 02-01-05:22:03.110238000
80b88433 WRITE         1 WAIT    mediastatistic.db         page     127104
80b88434 dd=15 locks held 0    write locks 0    pid/thread 14858/3064395536 priority 100       expires 02-01-05:22:03.128270000 lk expires 02-01-05:22:03.128270000
80b88434 WRITE         1 WAIT    mediastatistic.db         page     127104
80b88435 dd=14 locks held 0    write locks 0    pid/thread 16143/3063744272 priority 100       expires 02-01-05:22:03.138039000 lk expires 02-01-05:22:03.138039000
80b88435 WRITE         1 WAIT    mediastatistic.db         page     126767
80b88436 dd=13 locks held 0    write locks 0    pid/thread 15823/3062839056 priority 100       expires 02-01-05:22:03.151565000 lk expires 02-01-05:22:03.151565000
80b88436 WRITE         1 WAIT    mediastatistic.db         page     127272
80b88437 dd=12 locks held 0    write locks 0    pid/thread 15694/3063637776 priority 100       expires 02-01-05:22:03.203599000 lk expires 02-01-05:22:03.203599000
80b88437 WRITE         1 WAIT    mediastatistic.db         page     127104
80b88439 dd=11 locks held 2    write locks 2    pid/thread 2077/3062581008 priority 100       expires 02-01-05:22:04.313716000 lk expires 02-01-05:22:04.313716000
80b88439 WRITE         1 WAIT    mediastatistic.db         page          0
80b88439 WRITE         1 HELD    mediastatistic.db         page     104797
80b88439 WAS_WRITE     1 HELD    mediastatistic.db         page     104797
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Locks grouped by object:
Locker   Mode      Count Status ----------------- Object ---------------
[...] snip [...]

Hello,
This bug did not raise in BDB 5.1.25 yet.
BDB 5.1.25 is the first release, that runs stable for two month
without the need of a `db_recover`. Maybe #18789 ?
Thanks
Josef

Similar Messages

DB- put(), lock never expires

Hello,
Sometimes we perceive locks, which won't expire.
This happens only on tables, where we sometimes use "DB->put()" without a previous "DB->read(DB_RMW)".
We could solve this issue only by a `db_recover`, `db_deadlock`won't help.
Down below you will find the affected locks taken from `db_stat -CA`.
Thanks a lot
Josef
   c9dce dd=47 locks held 0    write locks 0    pid/thread 5397/3058980624 flags 0    priority 100        lk expires 10-15-07:47:03.290149000
   c9dce READ_UNCOMMITTED    1 WAIT    queue_status.db           page          1
   c61b1 dd=1759 locks held 0    write locks 0    pid/thread 15617/3060799248 flags 0    priority 100        lk expires 10-15-07:47:30.303037000
   c61b1 READ          1 WAIT    queue.db                  page          2
   c620c dd=1668 locks held 0    write locks 0    pid/thread 15619/3060266768 flags 0    priority 100        lk expires 10-15-07:47:15.075252000
   c620c READ          1 WAIT    queue.db                  page          2
   c629a dd=1527 locks held 0    write locks 0    pid/thread 15621/3059812112 flags 0    priority 100        lk expires 10-15-07:47:33.457257000
   c629a READ          1 WAIT    queue.db                  page        823
   c62be dd=1491 locks held 0    write locks 0    pid/thread 15622/3059201808 flags 0    priority 100        lk expires 10-15-07:47:40.568046000
   c62be READ          1 WAIT    queue.db                  page        823
85190b1a dd=18 locks held 4    write locks 4    pid/thread 21915/3058906896 flags 1    priority 100       expires 10-15-07:46:40.664800000
85190b1a WRITE         1 HELD    queue_status.db           page          1
85190b1a WAS_WRITE     1 HELD    queue_user.db             page          2
85190b1a WAS_WRITE     1 HELD    queue_usercreated.db      page         12
85190b1a WAS_WRITE     2 HELD    queue.db                  page        449
85190db6 dd=17 locks held 3    write locks 3    pid/thread 28933/3058747152 flags 1    priority 100       expires 10-15-07:46:51.076595000 lk expires 10-15-07:46:51.076595000
85190db6 READ          1 WAIT    queue_status.db           page          1
85190db6 WAS_WRITE     1 HELD    queue_user.db             page         38
85190db6 WAS_WRITE     1 HELD    queue_usercreated.db      page          6
85190db6 WAS_WRITE     2 HELD    queue.db                  page        361
85190dc4 dd=16 locks held 3    write locks 3    pid/thread 413/3059558160 flags 1    priority 100       expires 10-15-07:46:51.118201000 lk expires 10-15-07:46:51.118201000
85190dc4 READ          1 WAIT    queue_status.db           page          1
85190dc4 WAS_WRITE     1 HELD    queue_user.db             page         11
85190dc4 WAS_WRITE     1 HELD    queue_usercreated.db      page          4
85190dc4 WAS_WRITE     2 HELD    queue.db                  page        246
85190df0 dd=15 locks held 3    write locks 3    pid/thread 14667/3059738384 flags 1    priority 100       expires 10-15-07:46:51.595167000 lk expires 10-15-07:46:51.595167000
85190df0 READ          1 WAIT    queue_status.db           page          1
85190df0 WAS_WRITE     1 HELD    queue_user.db             page         30
85190df0 WAS_WRITE     1 HELD    queue_usercreated.db      page          7
85190df0 WAS_WRITE     2 HELD    queue.db                  page          2
85190e41 dd=14 locks held 1    write locks 1    pid/thread 17126/3059300112 flags 1    priority 100       expires 10-15-07:46:52.977349000 lk expires 10-15-07:46:52.977349000
85190e41 WRITE         1 WAIT    queue_usercreated.db      page          4
85190e41 WAS_WRITE     2 HELD    queue.db                  page        823

We got the same issue again. Is there any helpful information (e.g. the backtrace) I could provide?
8161947b dd=14 locks held 4    write locks 4    pid/thread 14137/3058943760 flags 1    priority 100       expires 10-19-11:29:11.398638000 lk expires 10-19-11:29:11.398638000
8161947b READ          1 WAIT    queue_status.db           page          1
8161947b WAS_WRITE     1 HELD    queue_user.db             page         34
8161947b WAS_WRITE     1 HELD    queue_usercreated.db      page          6
8161947b WAS_WRITE     1 HELD    queue_useractive.db       page          3
8161947b WAS_WRITE     2 HELD    queue.db                  page        180
8161973f dd= 2 locks held 0    write locks 0    pid/thread 31338/3060123408 flags 0    priority 100       expires 10-19-11:29:21.708633000 lk expires 10-19-11:29:21.708633000
8161973f READ          1 WAIT    queue.db                  page        180
   3a2ad dd=45 locks held 0    write locks 0    pid/thread 14395/3058960144 flags 0    priority 100        lk expires 10-19-11:29:14.196558000
   3a2ad READ_UNCOMMITTED    1 WAIT    queue_status.db           page          1
   34c1a dd=1862 locks held 0    write locks 0    pid/thread 31311/3059177232 flags 0    priority 100        lk expires 10-19-11:30:03.598454000
   34c1a READ          1 WAIT    queue.db                  page        180
   34c49 dd=1815 locks held 0    write locks 0    pid/thread 31312/3059156752 flags 0    priority 100        lk expires 10-19-11:29:37.516824000
   34c49 READ          1 WAIT    queue.db                  page        180
   34c97 dd=1737 locks held 0    write locks 0    pid/thread 31318/3059496720 flags 0    priority 100        lk expires 10-19-11:29:21.791232000
   34c97 READ          1 WAIT    queue.db                  page       1375
   34ce4 dd=1676 locks held 0    write locks 0    pid/thread 31330/3058968336 flags 0    priority 100        lk expires 10-19-11:29:52.221321000
   34ce4 READ          1 WAIT    queue.db                  page        180
   34dbc dd=1460 locks held 0    write locks 0    pid/thread 31336/3059418896 flags 0    priority 100        lk expires 10-19-11:29:27.140724000
   34dbc READ          1 WAIT    queue.db                  page       1375

How to set password never expires for a user?

Hello,
I can't seem to find in the Administrative Console a place to enable "Password never expires".
I know that if I edit the USR_PWD_NEVER_EXPIRES field in the OIM DB and put the value '1' it will work.
However, I'd like to know how and if it is possible to activate this option on a user via OIM.
Thanks in advance,
Tomic

Hi,
Now I got it.Try this one.
In FormMetaData.xml you will find.
<Attribute name="-13" variantType="String" dataLength="1" map="Users.Password Never Expires" />
Modify it to.
<Attribute name="-13" variantType="String" dataLength="1" displayComponentType="CheckBox" map="Users.Password Never Expires" />
Add this in.
<Form name="3">
<AttributeReference editable="true" optional="true">-13</AttributeReference>
I never need this but I hope above will work.
About disabling the resource I have few suggestion for you.
1.You can have your password policy consistent across the resources you are integrating in OIM.
2.Write an entity adapter so that when ever password is expired then can disable all provisioned user.
3.Alternatively you can also write a schedule task which will check for password expire date and disable the resource.
4.You will also need to enable the resources when password is changed.You can catch change password event through event handler or entity adapter.
Please let me know if you have fllow up questions.
Regards
Nitesh

How to set database user password to never expire

Hello all,
I have a linux server with Oracle 11g installed which is used primarily for testing by a few developers and QA folks. I want to set the DB user password to never expire. I have run the following (which works on a windows machine) but the password still states that it will expire in 7 days. Is there something else I can do to 'force' the pw to infinity? I've tried stopping shutting down the DB, stopping / restarting listener...
ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;
select * from dba_profiles where profile = 'DEFAULT' and resource_name LIKE 'PASSWORD_LIFE_TIME';
"PROFILE"     "RESOURCE_NAME"     "RESOURCE_TYPE"     "LIMIT"
"DEFAULT"     "PASSWORD_LIFE_TIME"     "PASSWORD"     "UNLIMITED"
select profile from dba_users where username='TEST';
"PROFILE"
"DEFAULT"
select username, account_status, to_char(expiry_date, 'DD-MM-YYYY') EXP_DATE from dba_users where username = 'TEST';
"USERNAME"     "ACCOUNT_STATUS"     "EXP_DATE"
"TEST"     "OPEN"     ""
Help appreciated.

With 11g, Password_life_time in DEFAULT profile is set to 180days.
Default profile values in 11g.
SQL> SELECT * FROM dba_profiles WHERE profile = 'DEFAULT' AND resource_type = 'PASSWORD';
PROFILE                        RESOURCE_NAME                    RESOURCE
LIMIT
DEFAULT                        FAILED_LOGIN_ATTEMPTS            PASSWORD
10
DEFAULT                        PASSWORD_LIFE_TIME               PASSWORD
180
DEFAULT                        PASSWORD_REUSE_TIME              PASSWORD
UNLIMITED
PROFILE                        RESOURCE_NAME                    RESOURCE
LIMIT
DEFAULT                        PASSWORD_REUSE_MAX               PASSWORD
UNLIMITED
DEFAULT                        PASSWORD_VERIFY_FUNCTION         PASSWORD
NULL
DEFAULT                        PASSWORD_LOCK_TIME               PASSWORD
1
PROFILE                        RESOURCE_NAME                    RESOURCE
LIMIT
DEFAULT                        PASSWORD_GRACE_TIME              PASSWORD
7
7 rows selected.Change the password_grace_time to unlimited.
HTH
-Anantha

Human Task Expires Though Task Duration Never Expires in DeadLines Level

Human Task is expires thogh task Duration Never Expires in DeadLines level
1)I have Created a Human Task
2) I am assigning task based on User Input ( If User proivdes BPM ) task will will assigned to 'BPM' Group
3) In Assignment Advanced leve i have set Limit allocated duration to 5 Min
4) Dead Line Level I have set Task never Expires
5) I have created Task , Task is assigned to 'BPM' Group
6) 'BPMUser1' Acquired task
7) After few min task get released automatically
8) Task Expires after 5 Min

...and if I only send an email in the "When a Task Expires" step, the "When
a Task Expires" will get called again and again to remind the original approver. However, when I reassign the task the When
a Task Expires" will never get called again. stumped.

Using dbca to create a db and all the users are locked and expired

I create a template using dbca on 10gR2 with schema and data and when I use that to build a clone on another machine the users passwords are all locked and expired. I am doing this in silent mode from the command line and I am looking for a flag that produces the unlock users passwords feature which seems to be there if you manually run dbca from the GUI.

This is a unix script I use to unlock accouts. I should notice this script is used for educational pourposes, in a production database it is not a good practice to leave demo accounts unlocked and overall with login=password.
sqlplus -S /nolog <<ENDSQL
     connect / as sysdba
     SET LINESIZE 132
     SET PAGESIZE 0
     SET TERMOUT OFF
     SET NEWPAGE 0
     SET SPACE 0
     SET ECHO OFF
     SET FEEDBACK OFF
     SET HEADING OFF
     SPOOL x.sql
     SELECT 'ALTER USER '||username||' IDENTIFIED BY '||username||' ACCOUNT UNLOCK;'
     FROM   dba_users
     WHERE account_status LIKE '%LOCK%';
     SPOOL OFF
     @x.sql
     !rm x.sql
     exit
<<ENDSQL~ Madrid.

Turn off Password never expires on local administrator account

Hello Experts,
we have some servers where the Password Never Expires flag is checked , and I am trying to find out a scripting way to uncheck these option so that password expires on the Local administrator account(Not AD Account).
There are -bor 0x10000 (https://social.technet.microsoft.com/Forums/en-US/e4e96a5e-3b28-4673-8c61-d4abdf8f2426/win-7-setting-the-option-password-never-expires-for-a-specific-local-user?forum=winserverpowershell)
which turn this option ON.
But , what is need is exact opposite. I want to turn off the option so that , the password gets expired.
Thanks,
-Prashant Girennavar.
MCSA|MCITP SA|Microsoft Exchange 2003 Blog - http://prashant1987.wordpress.com Disclaimer: This posting is provided AS-IS with no warranties/guarantees and confers no rights.

PowerShell example:
$ADS_UF_DONT_EXPIRE_PASSWD = 0x10000
$admin = [ADSI] "WinNT://$Env:USERDOMAIN/$Env:COMPUTERNAME/Administrator,User"
$flags = $admin.UserFlags[0]
if ( ($flags -band $ADS_UF_DONT_EXPIRE_PASSWD) -ne 0 ) {
$flags = $flags -band (-bnot $ADS_UF_DONT_EXPIRE_PASSWD)
$admin.UserFlags = $flags
$admin.SetInfo()
Retrieve UserFlags (bit array), and if the bit is set, clear it. Reassign UserFlags with cleared bit, and write the change.
-- Bill Stewart [Bill_Stewart]

SharePoint Service Accounts - Passwords have expiration date when they are set to never expire

The managed accounts in my farm all have the Enable automatic password change
unchecked. Also these same accounts in AD have the Password never expires
checked.
If I use get-spmanagedaccount to view the accounts, some passwords show as already expired or have a future expiration date.  The automatic change is set to False and nothing is listed under the Change Schedule.
The strange thing to me is that the passwords listed as expired are still valid and haven't been changed. I even ran an iisreset just to check and there were no issues. When I look in CA the next password change area is blank for all accounts.
My question is why do the accounts list a password expiration date if it's set to
not automatically change passwords.  If you do change the password through AD you will see a new expiration date set for 90 days later.  I'm just wondering how much I should worry about the service accounts that are listed
as having expired passwords even though the passwords aren't expired.  My sites and services are running but I'm just curious if this could potentially cause other errors.
Thoughts?  Prayers? Condolences?
Jennifer Knight (MCITP, MCPD)

I checked the My farm as well, you are correct. Even you did not select the automatic password change still it showed 90 days as expiry.
You don't need to worry about it, it will not hurt, one of the dev farm having account which expired almost 10 months ago. :)
you can double check with in central admin and you will see no expiration set over their.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Impact UnCheck the Password Never Expires option in domain Users

Hi,
What will be impact if i uncheck the password never expires option in Domain Users ? All users are having different different password age.
Normally we will create user account with Password Never Expires checked. But we need to uncheck for password policy.
Ex: ID - 1234, 1234 Password Never Expires is checked, if i unchecked that what will be impact ?? 1234 ID will prompts to reset the password again after unchecked Password Never Expires ?
Regards, Hari Prasad.D

> If my Password age is 7days as per policy and my user Age as below, how
> the prompt will come and how it will work ? Which are the users will get
> prompt ?
Start thinking...
> 1234 - Password age is 4
No Prompt. Info tip in Notification Area "password will expire in 3 days".
> 4567 - Password age is 8
Password expired, must change now.
> 9874 - Password age is 1
No Prompt. Info tip in Notification Area "password will expire in 6 days."
> 5678 - Password age is 15
Password expired, must change now.
Martin
Mal ein
GUTES Buch über GPOs lesen?
NO THEY ARE NOT EVIL, if you know what you are doing:
Good or bad GPOs?
And if IT bothers me - coke bottle design refreshment :))

Hello trying to get help with the option on auto lock (never is not on option on 4s or new I pad 2? Both are up to date with the latest 6.1.2

Just trying to get help in auto lock it is not an options for (never) on 4s or new i pad 2 both are a mirror of each other it seems I have had problems with this phone from day 1 all up dates have been installed. Calling the support line is good if you get someone that is advance and that is not worried about there call time which I may have to do however I do know that this site is great help any help will be appreciated. This is my husband phone and I pad we purchased both phones @ the same time I have his older I pad he was given a new one for work which is the latest HELP please thanks. No problems with my phone or pad.

I have a Dell U3014 as well as a couple of older Dells turned up sideways as "ears".
Other than supplying the desktop "theme" (if you can call a complete lack of style along with a fair bit of inconsistency a "theme"), the OS really shouldn't be causing you to have a washed-out desktop experience. That's more a
matter of your display driver not really doing its job. What video card do you have?
FYI, one of the reasons I like Aero Glass for Win 8.1 (a 3rd party package) is that it allows me to make the desktop more pleasant to use and helps set the client areas (i.e., where work gets done) apart from the window chrome.
From what I can see, the color-management logic in Windows 8.1 is essentially unchanged from what it was in Windows 7. That there has been NO progress in this area is really a disappointment. It's an area where Microsoft has again just stopped
trying to make improvements.
If it's at all interesting to you, here's a screen grab of a REALLY cluttered up desktop. I don't normally work this way; this was an exercise to see how much I could get running. I finally gave up starting more stuff as I grew tired
and it just kept working fine...
http://Noel.ProDigitalSoftware.com/ForumPosts/Win81/BusyDesktop.png
-Noel
Detailed how-to in my eBooks:
Configure The Windows 7 "To Work" Options
Configure The Windows 8 "To Work" Options

Auto-Lock "Never" not available

I added an Exchange mail account and I found that the "Never" option is no longer available in *Settings > General > Auto-Lock*. This is a well-documented issue as in this article:
http://www.macworld.com/article/152642/2010/07/noneverautolock.html
I emailed my IT, but they are slow to respond to this kind of non-critical issues. But, the inability to choose "Never" under Auto-Lock is truly annoying in certain situations.
Is there anything I can do on my iPhone to bring back the "Never" option?

If I were to change the Exchange account to a regular account and let iPhone "Fetch" email, then the Never option returns as expected.
I contacted the IT Department at my school again. This time, they don't even reply.

Screen Lock never works!

My iPod's screen lock has never worked. It tells me to enter the code, then the Screen Lock menu shows with the choice "Turn Screen Lock On >" saying that.
Help appreciated!
Thanks!
Laptop: IBM R40 - Desktop: Unknown Windows XP Owns an iPod, Palm Z22

Do you have the latest iPod/iTunes software?
iPod Updater
Upgrade to iTunes 6
Upgrade iPod's software
Try formating your iPod via "My Computer":
Go to "My Computer".
Right-click your iPod, click on "Format".
To begin the formatting process, start in “FAT32”, but make sure that “quick format” is not selected.
This process will take a while. But after it is done, be sure to perform a restore on your iPod.
Have you tried uninstalling-reinstalling your iPod's software?
Also, have you tried all the Five R's?
The Five R's
~~Kylene

What happens to lock on expired item in partitioned cache?

With a partitioned cache, what happens if an object with a lock on it expires?
In other words, if I put it in with an expiry, something locks it, and it expires while the lock is present, what happens?

Hi mesocyclone,
The lock/unlock API is completely orthogonal to the data-related API (get, put, invoke, etc). Presence of absence of the data has no effect on the lock.
Regards,
Gene

Web Dynpro application needs to never expire.

Hi
I have a Web Dynpro application (NW2004 SP12) that displays spreadsheet like sales data to anyone who walks past the screen in a common area in the office/s. It should therefore run unattended. It refreshes the data on a timer. The data comes from a back-end aRFC. Everything works fine but about every 1.5 days the application times out (session expires) and needs to be re-opened (this seems to be a large administrative problem to re-login at all the deployment sites).
It gives an error 500application has expired. Please restart with the refresh button
In testing/troubleshooting I used the direct URL to the application running on WAS and not through a Portal iView.
I also changed the System destination from using SSO to using a dedicated user to the back-end.
Does anyone have an idea on how to auto refresh a Web Dynpro application or auto-renew the session so that it can run forever or a way to re-login automatically?
Thanks in advance,
Rick Viljoen

Hi Isidro
Yes, this was my final solution. Here is the code for the htm page. It will refresh/reload every 6 hours. Hope it helps.
Regards,
Rickus
<html>
<head></head>
<body>
<div id = div1></div>
<script type="text/javascript">
function putIF(hldr,x,y,w,h,url) {
   // Iframe
   holder=document.getElementById(hldr);
   holder.style.position ='absolute';
   holder.style.left=x;
   holder.style.top=y;
   holder.style.width=w;
   IF=document.createElement("iframe");
   IF.setAttribute("height", h);
   IF.setAttribute("width", w);
   IF.setAttribute("src", url);
   if (holder.hasChildNodes()) {
          var oChild=holder.children(0);
          holder.removeChild(oChild);
   holder.appendChild(IF);
   var myDate=new Date();
   window.status="Last reload on: " + myDate;
function refreshiframe() {
     myWidth = document.body.offsetWidth-21;
     myHeight = document.body.offsetHeight-4;
     putIF("div1","0px","0px",myWidth,myHeight,"http://<server>:<port>/webdynpro/dispatcher/local/SalesD/SalesD?j_user=xxx&j_password=ppp");
     window.setTimeout(refreshiframe, 21600000);
refreshiframe();
</script>
</body></html>

UME User account password never expires

Is there a user type in the UME on java where the user account will not expire? Much like the service user type on ABAP.
Thanks Mikie

Mike,
This is actually what you are looking for:
http://help.sap.com/saphelp_nw04s/helpdata/en/4e/225b42eeb66255e10000000a155106/frameset.htm
You want the technical user type.
-Michael
Ooops I answered to quickly. Someone else already answered.
-Michael
Edited by: Michael Shea on Mar 12, 2008 10:35 AM
My mistake.
Well actually no I am correct. Mike, you are looking for user types.
Edited by: Michael Shea on Mar 12, 2008 10:43 AM

Lock never expires

Similar Messages

Maybe you are looking for