IBM Cognos content database (Derby) could not be started

If you use the IBM Derby (default) database as the Cognos Content database (e.g. for development, testing or demos), recent Fix Packs may result in a failure to connect on starting. This most recently was observed for Cognos 10.2.1 FP6

There are a couple of TechNotes on the issue:

Unable to start the IBM Cognos content store database

and technote 1678962 (IBM cognos content database could not be started), of which the content is as follows:

Problem (Abstract)

After installing FP3, IBM Cognos Content Database service does not start

[Error] IBM Cognos Content Database service is starting.

Tue Jul 08 09:10:20 CST 2014: Access denied (“” “localhost: 1527” “listen, resolve”) Access denied (“” “localhost: 1527” “listen, resolve”)
at ( 100)
at ( 174)
at java.lang.SecurityManager.checkPermission ( 562)
at java.lang.SecurityManager.checkListen ( 1147)
at ( 452)
at <init> ( 257).
at ( 6)
at org.apache.derby.impl.drda.NetworkServerControlImpl.createServerSocket (Unknown Source)
at org.apache.derby.impl.drda.NetworkServerControlImpl.access $ 000 (Unknown Source)
at org.apache.derby.impl.drda.NetworkServerControlImpl $ (Unknown Source)
at ( 330)
at org.apache.derby.impl.drda.NetworkServerControlImpl.blockingStart (Unknown Source)
at org.apache.derby.impl.drda.NetworkServerControlImpl.executeWork (Unknown Source)
at org.apache.derby.drda.NetworkServerControl.main (Unknown Source)
IBM Cognos Content Database service failed to start.

Solve the problem

Turn off the Derby service

Built Cognos Content Store DB (Derby) startup problems, the solution is as follows:

Open this file Cognos installation directory:
\ c10_64 \ bin \ jre \ 7.0 \ lib \ security \ java.policy

2 Add the following fields to file grant sub-segments:
permission “localhost: *”, “listen, accept, connect, resolve”;

3 In the Configuration alone start a content database to check whether it can start

Our experience was that the TechNotes provided some clues, but the solution we found that worked is to follow the second TechNote, but to use the following line in the Java.policy file;

permission “localhost:1527”, “listen, accept, connect, resolve”;