Connections migration DB issues

I thought I had already posted this but was remided by our slack chat today that I hadn’t. When migrating the Connections meetrics database from V5 to V6 there is an error that is thrown when the DB2 restore tries to run the upgrade command.

DB20000I The RESTORE DATABASE command completed successfully.
SQL2519N The database was restored but the restored database was not upgraded to the current release

The error related to the application heap size, and there is not enough space allocated to run the upgrade command.

Get the current heap size by running the following db2 command

db2 GET DATABASE CONFIGURATION FOR METRICS

You can resolve the issue running the commands:

db2 UPDATE DB CFG FOR METRICS USING APPLHEAPSZ 1536
db2 UPGRADE DATABASE METRICS

I set the APPLHEAPSZ to double the current one. I have also previously seen the same issue with the Cognos DB – which can be resolved in the same way

db2 UPDATE DB CFG FOR COGNOS USING APPLHEAPSZ 2018
db2 UPGRADE DATABASE COGNOS

I have seen this issue with both Connections V5 and 5.5 DB2 databases updating to V6 and this has fixed it for me (and now some others) .. when you google the error you don’t get much in the way of help, so hopefully this will help others who get stuck.

 

 

 

Connections adoption – full list of videos

Here are the full list of videos from the Connections adoption month campaign from IBM.

 

Video List

IBM Connections Tip #1 – Build your network
IBM Connections Tip #2 – Advertise your skills
IBM Connections Tip #3 – Update your status every day
IBM Connections Tip #4 – Bookmark in Connections
IBM Connections Tip #5 – Stop sending files in emails
IBM Connections Tip #6 – Stop doing work in emails!
IBM Connections Tip #7 – Co-create with Wikis!
IBM Connections Tip #8 – Create a self help forum
IBM Connections Tip #9 – Follow wisely!
IBM Connections Tip #10 – Check your activity stream daily
IBM Connections Tip #11 – Only create mission driven communities
IBM Connections Tip #12 – Lead by Example
 

Graphic List

Connections Adoption Month – midway update

Connections Adoption Month – midway update

So we are half of the way though Connections Adoptions month (july 2018) and if you have been following theย IBM_ICSsupportย  twitter account, you will have noticed some videos and tips these have also been posted over on the Connections Cloud Collaboration blog.

These videos are between 1 and 2 mins each and are bite size chunks on the 12 Winning social habbits with IBM Connections. I have collated these videos into a list (which I will append with all of the videos once they are published) and any of the other social posts around this subject.

The videos are great ways of introducing users on how IBM Connections can help with their day to day tasks. Personally I spend a lot of time in IBM Connections, the internal BCC one, Customer Connections systems, IBM in the Cloud (NA and CE Connections Cloud), the ICON UK Cloud Connections – I use connections a lot! There are so many times that we have shown how doing some of these simple tasks can help make people more productive – there has been many “AHA!” moments ๐Ÿ™‚

Grab the videos, share the images (in a number of langages) and get your users engaging .. ๐Ÿ˜€ If you think there are languages missing let us know and we can ask IBM to translate the graphics.

Happy collaborating

 

Video List

IBM Connections Tip #1 – Build your network
IBM Connections Tip #2 – Advertise your skills
IBM Connections Tip #3 – Update your status every day
IBM Connections Tip #4 – Bookmark in Connections
IBM Connections Tip #5 – Stop sending files in emails
IBM Connections Tip #6 – Stop doing work in emails!
IBM Connections Tip #7 – Co-create with Wikis!

 

Graphic List

It’s IBM Connections Adoption Month woo hoo

I have been a little quiet on the blog as I have been working on a number of Connections related projects and today I see that IBM have designated July as IBM Connections Adoptions month. You can read a brief post about it here.

IBM have produced a fantastic info graphic – (the link to download the large PDF is attached to the image) – we winning social habbits with IBM Connecitons

I have written about this over on the BCC blog as we have lots of articles to help with adoption and offer connections services.

I LOVE IBM Connections – and have done since it was first thrown in my direction as “you know about that WebSphere stuff” almost 10 years ago now. I use connections every day, my customers love it and so do our ICS community .. lets lead the way with showing this awesome software some love and helping people get stuff done.

GDPR and IBM Connections / Docs On-Prem

At IBM Think back in March, the Connections Offering Management team promised us some information to help with GDPR compliency. The Connections Cloud information has been available for a while and the On-Premises docuemtation was on the way.

Today my friend and fellow IBM Champion Roberto alerted me to the technotes that are available.

IBM Connections: http://bit.ly/cnxGDPR

IBM Docs: http://bit.ly/docsGDPR

There is a new section in each of the knowledgebases entitled Managing personal data in accordance with GDPR – see here for Connections and here for Docs (note the docs section mostly points to the Connections KB).

The technotes refer to a number of standard tasks that should be configured as part of the install and configuration process – such as using SSL for HTTP traffic, disabling anonymous access etc.

I am sure that this information will evolve as time goes on, but its a great start.

Which version of IBM Docs to I have installed?

This morning, after a bit of attempting to work it out for myself .. I ask my good firiend and co speaker Roberto Boccadoro if there was a simple way to work out what version is installed?

WebSphere, Connections and the HTTP Server / Plugins etc all have command line options to find what version (and fixes) are installed and unfortunately its not so simple with docs ..

If you have kept the install files handy you can check but finding out the iFix version under the install\DocsApp directory where there is a handy file called ifix-version.json.

which gives you the iFix version .. which is just a number, 7, 15 or 25 etc. but how does that collate to which Docs version, CR and iFix you have installed?

Roberto has made a searchable list to make it simple to see what iFix version relates to which Docs version.

See Roberto’s awesome blog post here – and thank you so much my friend for doing this as it will save a bunch of time ๐Ÿ™‚

Connections 6 CR1 is now available

As promised by IBM we have got it in November (so thanks Connections Team ) …

The full Fix list can be found in this technote here – IBM Fix List for Connections CR1

You can download it from Fix Central here – IBM Connections 6 CR1 download

Included in CR1 are all the day 1 fixes and the fixpacks from June – along with a bunch of other fixes, enhancements and preperations for Connections Pink

 

Current Status – Patching Dev ๐Ÿ™‚ will let you know if i see any issues.

IBM Docs 2 CR3 is here – and with some cool new features

So at last IBM Docs 2 CR3 has been released and with it some awesome new features that the community have been asking for (thank you IBM).

 

What’s new in Docs 2 CR3? LOADS of new features and fixes including …

The most exciting is probably the ability to deploy the Conversion server on linux (finally)!!

  • You can directly deploy Conversion server on Linux when installing IBM Docs.
  • If you already have IBM Docs installed with Conversion server on Windows, you can migrate existing Conversion server from Windows to Linux.

 

A track change feature for the Docs editor which is another feature that has been on the wish list for a while

  • Added Track Change support in Document Editor. People with editing access can use a new view in the sidebar to see what changes were made to the file and when and who. Changes can be filtered by the timeline and editors. File owners can turn Track Change on and off, and clear change history.

 

You can install CR3 straight over Docs 2, no need for the other CRs or iFixes – make sure you run the DB updates though to update the Docs schema.

 

Additional features and full realse notes can be found here: IBM Connections Docs 2 CR3 release notes

Download it now from Fix Central ๐Ÿ™‚

Issues with IBM Connections 5 / 5.5 and Chrome 60

There is a known issue with Connections 5 CR4 and all versions of Connections 5.5 when using Chrome version 60.

It affects events not being displayed and errors relating to events in the UI. It has also been reported that comments can be affected also.

After multiple BP’s and Customers reported this IBM Support have come up with a fix very quickly.

The fix you need is IFLO92844 – currently it is only available from IBM support – not sure how long it will be until it is available on fix central.

Open a PMR with IBM and reference these 3 PMR numbers: 76364,082,000 – 76379,082,000 – 38309,756,000 and ask for IFLO92844. You will need to specify the Connections version and CR.

The fix updates the Common app and takes about 10 mins to deploy.

Thank you IBM Connections Support / Dev for resolving this so quickly

Connections 6 migration observations

I am sure that lots of you have installed or started migrations to Connections 6 by now .. but I have found a couple of gotchas across the installs and updates that I have managed so far.

I am listing them here for sanities sake as I know when we google an error – this blog will show up ๐Ÿ™‚

 

Connections 6 itself

 

Generally this was a nice smooth install and all worked as it should in a clean 6 environment

On testing a migration though I found issues when trying to migrate some of the DBs.

After dropping and restoring the DBs some were not updating to the latest DB2 version – this is resolved by running the update DB command

db2 upgrade db <DBNAME>

this upgrades the DB to the latest DB2 version – I run this after each restore command now to ensure the DB does update

for example

db2 restore db BLOGS from E:\install\V55_Backup\db2_backup taken at 20170718123342 ON E:\ into BLOGS
db2 upgrade db BLOGS

 

The metrics DB would not restore as it was complaining about heap size – after a quick google on the error I found a page suggesting just to change the application heap size using the following command

db2 UPDATE DB CFG FOR METRICS USING APPLHEAPSZ 4000

This resolved the problem and the metrics DB could be restored

 

I have also seen issues with the Connections DB update wizard when the databases have a lot of data. In a mature environment I generally run through the wizard and save the update commands to a text file. Then execute them manually from the db2 command window – for example

Activities
 1. E:\IBM\SQLLIB\bin\db2cmd -c -w -i db2 -td@ -vf connections.sql\activities\db2\upgrade-55CR2-60.sql
 2. E:\IBM\SQLLIB\bin\db2cmd -c -w -i db2 -td@ -vf connections.sql\activities\db2\appGrants.sql
 3. E:\IBM\SQLLIB\bin\db2cmd -c -w -i db2 -td@ -vf connections.sql\activities\db2\reorg.sql
 4. E:\IBM\SQLLIB\bin\db2cmd -c -w -i db2 -td@ -vf connections.sql\activities\db2\runstats.sql

Blogs
 1. E:\IBM\SQLLIB\bin\db2cmd -c -w -i db2 -td@ -vf connections.sql\blogs\db2\upgrade-55-60.sql
 2. E:\IBM\SQLLIB\bin\db2cmd -c -w -i db2 -td@ -vf connections.sql\blogs\db2\appGrants.sql
 3. E:\IBM\SQLLIB\bin\db2cmd -c -w -i db2 -td@ -vf connections.sql\blogs\db2\reorg.sql
 4. E:\IBM\SQLLIB\bin\db2cmd -c -w -i db2 -td@ -vf connections.sql\blogs\db2\runstats.sql

Bookmarks
 1. E:\IBM\SQLLIB\bin\db2cmd -c -w -i db2 -td@ -vf connections.sql\dogear\db2\upgrade-55-60.sql
 2. E:\IBM\SQLLIB\bin\db2cmd -c -w -i db2 -td@ -vf connections.sql\dogear\db2\appGrants.sql
 3. E:\IBM\SQLLIB\bin\db2cmd -c -w -i db2 -td@ -vf connections.sql\dogear\db2\reorg.sql
 4. E:\IBM\SQLLIB\bin\db2cmd -c -w -i db2 -td@ -vf connections.sql\dogear\db2\runstats.sql

.................. ETC.

For some reason if you have large DBs the wizard struggles massively. Running the commands manually from the command window also allows you to dump each commands logs out into a text file if you need to. Great for debugging and used a LOT when I ran through the AIX Oracle to Windows DB2 migration last year.

 

Once the DBs were restored and updated run the reorg and runstats against each of the DBs before you start it up and if you can also run theย clearScheduler.sql for each DB.

That should sort out the majority of DB issues you may see during the update.

 

Connections TouchPoint

 

Again a fairly easy process once you work out what the documentation is talking about – things of note

The document speaks of copying the touchpoint folder contents to the htdocs directory –

 

 

 

 

 

 

you have to copy the entire folder – for example

Copy files from E:\install\Connections\Touchpoint\touchpoint to E:\IBM\HTTPServer\htdocs\touchpoint the wording in the documentation doesn’t really make that clear.

All of the paths etc in the documenation are case sensitive.

Another thing of note which has tripped me up twice now so I have to blog it (thank you Ben for the extra eyes on this one) is the contents of the touchpoint.deploy.properties

The touchpoint.deploy.properties which is included in the install files is different from the example the documentation gives, we basically mix the two and have the contents of the file looking like this

# when install to a clustered environment, provide clusterName.
# when install to a standalone server, provide node and server name.
clusterName=apps
#nodeName=icbvtDB2Node01
#serverName=server1

# setting required REE custom properties
ree.prop.image.upload.path=E:/IBM/CnxData/shared/touchpoint/upload_pic
ree.prop.profiles.app.entrypoint.host=connections.url.com
ree.prop.profiles.app.entrypoint.scheme=https
ree.prop.profiles.app.entrypoint.port=443

NOTE:ย  If using windows the image upload path must have / the linux way not \ the windows way. It will fail if you don’t even if you have it in “E:\IBM\etc…” it appears to be a java / python thing and the error will complain that it can not pass the properties file if the slashes are not /

 

IBM Docs CR2

 

To use IBM Docs with Connections 6 you must update to CR2 for Docs – that is fine (and see previous blog posts about issues with applying the CR2 fix).

There is an awesome gotcha that my good friend Roberto pointed me in the direction of the fix for – this one was a good one (thank you Marti for writing the blog)

The symptoms are Docs editing works fine, but when attempting to view a file the error : CLFAF400W: Canโ€™t access the document repository appears

Its a super quick fix – edit the viewer-config.json which can be found in the (i.e \IBM\WebSphere\AppServer\profiles\Dmgr01\config\cells\<cell name>\IBMDocs-config)

Under the section

"components": [
 {
 "config": {
 "uploadRepository": "lcfiles",

find the line

 "class" : "com.ibm.concord.viewer.lc3.repository.LCFilesEJBRepository",

and replace it with

 "class": "com.ibm.concord.viewer.lc3.repository.LCFilesCMISRepository"

Just above that you can see the files_path

 "files_path": "E://IBM//CnxData//shared/files/upload"

Add the additional info to that section

 "j2c_alias": "connectionsAdmin", 
 "s2s_method": "j2c_alias", 
 "server_url": "https://connections.url.com/files",
 "files_path": "E://IBM//CnxData//shared/files/upload"

So the full section will now look like this:

 "components": [
 {
 "config": {
 "uploadRepository": "lcfiles", 
 "adapters": [
 {
 "config": {
 "j2c_alias": "connectionsAdmin", 
 "s2s_method": "j2c_alias", 
 "server_url": "https://connections.url.com/files",
 "files_path": "E://IBM//CnxData//shared/files/upload"
 }, 
 "id": "lcfiles", 
 "class": "com.ibm.concord.viewer.lc3.repository.LCFilesCMISRepository"
 },

 

Save the file and do a full sync once a restart of the viewer app is done the viewer will now work.

 

One other thing of note when it comes to migrating the Docs data and DBs is that almost every time you do a migration the wasadmin user will be out of sync and you will see duplicate user issues in the log.

easily resolved by running the syncMember command from the DMGR\bin directory

wsadmin.bat -lang jython

execfile("filesAdmin.py")

FilesMemberService.syncMemberExtIdByLogin("wasadmin")

 

Other things you should do once the docs data has been migrated is to run the generate thumbnails command (also from wsadmin in the filesAdmin section)

wsadmin.bat -lang jython

execfile("filesAdmin.py")

FilesThumbnailService.generateForAllFiles()

 

Also to migrate any drafts from the docs installer directory i.e

wsadmin.bat -lang jython -f E:/IBM/ConnectionsDocs/Docs/installer/docs/tasks/start_migration_tool.py

 

Hopefully you won’t come across any or more than one of these issues, but if you do hopefully there will be a quick resolution.

If I find anything else I will be sure to blog them.