Guru Of Geeks

Solution 1 sudo apt-get -y install dconf-tools dconf write / org / gnome / desktop / remote-access / require-encryption false / usr / lib / vino / vino-server --sm-disable start Solution 2 gsettings set org.gnome.Vino require-encryption false

Right click it->Edit Digital Clock settings. Change clock format from %R to %r.

First (in a terminal) start your editor: vi ~/.config/openbox/lubuntu-rc.xml Then search for the mentioned faulty code: <keybind key="C-A-L"> <action name="Execute"> <command>xscreensaver-command -lock</command> </action> </keybind> and change it to use the dm-tool: <keybind key="C-A-L"> <action name="Execute"> <command>dm-tool lock</command> </action> </keybind> Then add a section, so the Windows+L combination works too: <keybind key="W-L"> <action name="Execute"> <command>dm-tool lock</command> </action> </keybind> Finally, finish the editor (saving the file) and activate it: openbox --reconfigure Good luck

Question If DataStage project or temp directory runs out of disk space, some of the buffered write requests might not get correctly completed and the project might ended up having corrupted hash files. There is one approach to check the project for corrupted hash files. Answer Run the uvbackup process and redirect the backup to null devices. The uvbackup produces an output file that can be used to identify the corrupted files. Here are the steps (please note that you must be logged in as DataStage Administrator): Source your dsenv file in $DSHOME (. ./dsenv) Go to your project directory (../InformationServer/Project/<project name>) List all files and direct them to a file (ls > myfiles.txt) - this is used to list of files for the uvbackup Run the uvbackup and redirect output to null with this command: "$DSHOME/bin/uvbackup -V -f -cmdfil myfiles.txt -s uvbackupout.txt -t /dev/null  2>&1 > testing123.txt" grep ...

​ find . -maxdepth 1 -type f |head -1000|xargs cp -t $destdir

​​ RT_CONFIGnn is a UniVerse table (dont hack it with a text editor). It contains the runtime configuration information for job number nn. Things like what links connect to what stages, what resources have to be notified when others finish, and so on. Obviously this information is used when the job is run. Most of it is put there when the job is compiled in Designer, though run-time defaults for job parameters can be set from Director.

Problem(Abstract) The 'lssam' command is showing Control=SuspendedPropagated for HADR resource group when the database resource is shown as Failed offline on one node and Online on the other. What does this mean ? Environment Here's an example of the lssam output that shows this situation : Online IBM.ResourceGroup:db2_db2inst1_db2inst1_AM-rg Request=Lock Nominal=Online '- Online IBM.Application:db2_db2inst1_db2inst1_AM-rs Control=SuspendedPropagated |- Failed offline IBM.Application:db2_db2inst1_db2inst1_AM-rs:alx00005 Node=Offline '- Online IBM.Application:db2_db2inst1_db2inst1_AM-rs:alx00006 Resolving the problem It is expected behaviour to see the Control flag set to SuspendedPropogated when the resource group is locked. It is also expected behaviour to see the HADR resource group locked when it is not in a peer connected state. The DB2 engine is suppose to unlock the group once peer connected stat...