OpenText Adds Full Folder Sync to ECM Everywhere iOS Client

Earlier this week, OpenText released an update to their iOS ECM Everywhere client to version 10.5.21.

The new update will allow ECM Everywhere users to quickly mark all of the files in a single folder for offline access.  If you want to sync a sub-folder and it’s contents for offline access, you will need to drill down to that level and manually mark the folder offline.

ECM Everywhere is the iOS, Android and BlackBerry client for OpenText’s Content Server 10.5 and 10.0 content management systems.  ECM Everywhere is a free download from the Apple App Store, Google Play Store and BlackBerry App World.

For more information on OpenText ECM Everywhere 10.5, visit the OpenText.com website.

The Incident at RetentionUpdateOrder [UPDATED]

During an upgrade of a quality assurance (QA) instance of OpenText Content Server 10.0.0 SP2 Update 12 to Content Server 10.5.0 Update 2014-06 I ran into an incident at the RetentionUpdateOrder table.

[01/14/2015 04:25:31 PM] : Applying the database schema upgrade
[01/14/2015 04:25:31 PM] : Error executing statement
[01/14/2015 04:25:31 PM] : create table RetentionUpdateOrder ( … )
[01/14/2015 04:25:31 PM] : Error: Error executing an Sql statement.
[01/14/2015 04:25:31 PM] : Error: Error executing an Sql statement.
[01/14/2015 04:25:31 PM] : The Module Upgrade Failed Due To Errors

The error, as it turns out, was caused because my database already had a table called “RetentionUpdateOrder” in it.  Great, now what?

A quick look at my QA and production Content Server 10.0 databases revealed that the table in question existed in both.  This was not a table that I added, altered, or otherwise modified, so it had to come from the core installation of Content Server or one of the modules that my employer has elected to install.

I needed to know how big the scope of this problem was.  As it turned out, RetentionUpdateOrder was not alone.  Three of it’s friends were also giving me a little bit of heartburn during the upgrade; they are: RetentionUpdateOrder, RetentionUpdateRetry, RetentionUpdateFailed, and RetentionUpdateLog.

WARNING: This post talks about modifications to your Content Server database.  You should only directly alter your Content Server database under the supervision of a trained OpenText engineer.

Once I knew which tables involved in the upgrade, I used the following SQL to figure that out how much data was going to have to deal with.  Thankfully, using the following SQL command, the results all came back as zero rows.

use [yourContentServerDBName]
go
select COUNT(*) from RetentionUpdateOrder
go
select COUNT(*) from RetentionUpdateRetry
go
select COUNT(*) from RetentionUpdateFailed
go
select COUNT(*) from RetentionUpdateLog
go

To workaround this issue, wrote a short little SQL script to backup the tables in my database, and then drop the original so I could restart the Content Server database schema upgrade process and have it finish successfully.  Here’s the rough utility SQL script that I wrote to clean up the table situation.

use [yourContenServerDBName]
go
select * into RetentionUpdateOrder_CS10_5_Backup
    from RetentionUpdateOrder
go
if OBJECT_ID(‘livelink..RetentionUpdateOrder’,’U’) is not null
    drop table RetentionUpdateOrder
go
select * into RetentionUpdateRetry_CS10_5_Backup
    from RetentionUpdateRetry
go
if OBJECT_ID(‘livelink..RetentionUpdateRetry’,’U’) is not null
    drop table RetentionUpdateRetry
go
select * into RetentionUpdateFailed_CS10_5_Backup
    from RetentionUpdateFailed
go
if OBJECT_ID(‘livelink..RetentionUpdateFailed’,’U’) is not null
    drop table RetentionUpdateFailed
go
select * into RetentionUpdateLog_CS10_5_Backup
    from RetentionUpdateLog
go
if OBJECT_ID(‘livelink..RetentionUpdateLog’,’U’) is not null
    drop table RetentionUpdateLog
go

To jump start the database schema upgrade again, in my browser, I navigated back to the admin home page at ?func=admin.index and then jumped over to the database upgrade page at ?func=admin.dbupgrade.  (You may be prompted to log back in as ‘admin’.)

Once I restarted the database schema upgrade, it was a few short minutes until I got the following message back from my Content Server 10.5 instance:

[01/16/2015 05:45:03 PM] : Applying the database schema upgrade
[01/16/2015 05:45:03 PM] : Applying the data upgrade
[01/16/2015 05:45:03 PM] : The database upgrade completed with no errors.

Outstanding!  Your results may vary from mine. It is always to have a good set of backups, rollback plans and we should always test upgrades in test instances before moving on to QA, DR, and production.  If you get into trouble, or have questions, don’t forget to contact the OpenText Support Team.

UPDATE:

After talking to OpenText support, two important bits of information have surfaced about this issue.  They are:

1. The four RetentionUpdate tables discussed here are for the Archive Storage Provider module and NOT the Records Manager module.

2. If you have an aversion to writing SQL, you can avoid all of this by installing the Archive Storage Provider 10.0.2 module update before attempting to upgrade to Content Server 10.5.0.  Naturally, this is the method preferred by the OpenText Support team and I agree with them.  If you chose to use the backup/drop table method I described here, that is a viable workaround.  Any updates or alterations of a Content Server/Livelink database should be done only with guidance from Support.

OpenText Announces the Acquisition of Informative Graphics Corp.

Yesterday, OpenText announced that they have entered into a deal to acquire Informative Graphics Corporation.

Waterloo, ON – 2015-1-5 – OpenText™ (NASDAQ: OTEX, TSX: OTC), a global leader in Enterprise Information Management (EIM), today announced that it has acquired Informative Graphics Corporation (IGC), a leading developer of viewing, annotation, redaction and publishing commercial software. As a valued OpenText partner for more than a decade, IGC technologies will be further integrated into the ECM product portfolio and extended into other OpenText Suites.  

With the acquisition of IGC, OpenText strengthens its capabilities for secure access to any content, on any device, on premises and in the cloud. Having already deployed more than 250 joint customers and more than 300,000 seats of Brava!® for OpenText Content Server, OpenText can now extend the reach of IGC offerings to more OpenText customers globally. 

“With a proven record of success as an OpenText partner, we are excited to welcome the IGC team into our company,” said Mark J. Barrenechea, president and chief executive officer of OpenText. “As customers make the shift to the digital workplace and the cloud, document viewing and mark-up on any device will enable organizations to leverage their information and drive growth and success in their organizations.”

Content Server administrators should be pretty excited about this acquisition.  Brava! is a well known mark-up module for CAD documents stored in Content Server.  I’ve seen and talked to the folks from IGC at past Enterprise World conferences and have always been impressed with their software.  With OpenText’s acquisition, the software should become even more tightly integrated into the Content Suite of software.

You can read the full press release on the OpenText website. CEO Mark Barrenechea also a blog post up about the acquisition.