Portal startup displays EJPSK0028E and EJPSG0015E errors after database transfer

IBM® WebSphere® Portal is successfully installed, configured, and a database transfer is successfully performed. During the next startup after the database transfer, EJPSK0028E and EJPSG0015E errors are observed in the Portal log file SystemOut.log,. This Technote will explain how to troubleshoot and resolve these errors.

The Portal login page is not accessible. In the Portal log file SystemOut.log, the following errors may appear:

[datetime] 0000001c VaultServiceI E com.ibm.wps.services.credentialvault.VaultServiceImpl checkSystemDNInitialized EJPSK0028E: Invalid system user DN 'systemcred.dn' property value. Ensure that the DN value is valid in the vault service properties file.
com.ibm.wps.util.DataBackendException: EJPSG0015E: Data Backend Problem java.security.PrivilegedActionException: java.lang.NullPointerException
at
com.ibm.wps.services.puma.PumaServiceImpl.findUserById(PumaServiceImpl.java:457)
Caused by: java.lang.NullPointerException

The database transfer finished successfully but reviewing the database configuration files revealed incorrect values for many parameters required by the database transfer. As a result, the Portal system begins the errors on its next startup since it cannot locate correct data in the newly transferred database.

The following files may be helpful in diagnosing database transfer difficulties:

- <profile-root>\logs\WebSphere_Portal\SystemOut.log
- <profile-root>\ConfigEngine\log\ConfigTrace.log
- <profile-root>\ConfigEngine\properties\wkplc.properties
- <profile-root>\ConfigEngine\properties\wkplc_dbtype.properties
- <profile-root>\ConfigEngine\properties\wkplc_comp.properties

An example of a full path including the profile root is as follows:

c:\IBM\WebSphere\wp_profile\logs\WebSphere_Portal\SystemOut.log

In addition to the primary symptoms noted, the following may also be visible in the SystemOut.log during startup after a successful database transfer:

[datetime] 00000015 SchedulerImpl E SCHD0124E: Unable to initialize TaskStore due to error: SCHD0046E: The table RELEASE.WPS_SCDTREG in datasource jdbc/relDS used by scheduler resource WPSTaskScheduler (wps/Scheduler) is missing or is not accessible.
[datetime] 00000015 SchedulerServ E SCHD0128E: The daemon for scheduler wps/Scheduler could not be started: com.ibm.ws.scheduler.exception.SchedulerDataStoreException: SCHD0124E: Unable to initialize TaskStore due to error: SCHD0046E: The table RELEASE.WPS_SCDTREG in datasource jdbc/relDS used by scheduler resource WPSTaskScheduler (wps/Scheduler) is missing or is not accessible.
Caused by: com.ibm.websphere.scheduler.SchedulerNotAvailableException: SCHD0124E: Unable to initialize TaskStore due to error: SCHD0046E: The table RELEASE.WPS_SCDTREG in datasource jdbc/relDS used by scheduler resource WPSTaskScheduler (wps/Scheduler) is missing or is not accessible.

In this specific case, the wkplc_comp.properties file contained the following

source.release.DbSchema=wpdbDS

The correct setting should be:

source.release.DbSchema=release

To correct the error message shown in the SystemOut.log file, perform the following steps:

1. Modify the source.release.DbSchema property in the wkplc_comp.properties file with the correct setting.

2. Drop and recreate the existing databases as explained in the Portal 6.1 Information Center.

3. Rerun the database transfer using the configuration task:

ConfigEngine (.sh/.bat) database-transfer -DTransferDomainList=release

4. Start the Portal server and review the SystemOut.log file. The errors should no longer be present.



CAUTIONARY NOTE: This Technote and its solution should ONLY be followed if and only if these errors are seen on the next startup immediately after running a database transfer. If these errors appear after the system has been running for an extended period of time, please contact IBM Support for further assistance in troubleshooting.