Welcome to Port3101.org : Your BES Connection Mark forums read | View Forum Leaders
Port3101.org : Your BES Connection



Reply
LinkBack Thread Tools Display Modes
KB14537 - Issue with a BlackBerry MDS database upgrade script during a large upgrade
 
  #1 (permalink)  
Old 04-01-2009, 03:08 PM
hdawg's Avatar
Proprietor
 
Join Date: Nov 2008
Posts: 2,257
Blog Entries: 147
Default KB14537 - Issue with a BlackBerry MDS database upgrade script during a large upgrade

KB14537 - Issue with a BlackBerry MDS database upgrade script during a large data upgrade


Environment

  • BlackBerry® Enterprise Server software version 4.1 Service Pack 2 (4.1.2) and Service Pack 3 (4.1.3) for Microsoft® Exchange
  • BlackBerry® Enterprise Server software version 4.1 Service Pack 2 (4.1.2) and Service Pack 3 (4.1.3) Novell® GroupWise®
  • Microsoft® SQL Server®



Overview

BlackBerry Enterprise Server with BlackBerry® Mobile Data System was upgraded successfully according to the BlackBerry Enterprise Server installer log. The BlackBerry MDS Services database schema was upgraded correctly, but the BlackBerry MDS Services default data is not populated correctly. At runtime, a BlackBerry smartphone user might have following exception in the BlackBerry MDS Services log:
[ERROR] (10/04 03:32:31) [[CompactListener]] Servlet.service() for servlet CompactListener threw exception
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at net.rim.wica.ag.services.lifecycle.DeviceEntity.getIntVersion(DeviceEntity.java:401)
at net.rim.wica.ag.services.lifecycle.DeviceEntity.getSecurityVersion(DeviceEntity.java:119)
at net.rim.wica.ag.services.security.DeviceVersionProvider.getSecurityVersion(DeviceVersionProvider.jav a:36
at net.rim.wica.transport.internal.security.SecureMessageV1_0.verifyVersion(SecureMessageV1_0.java:275)
at net.rim.wica.transport.internal.security.SecureMessageV1_0.verifySecurity(SecureMessageV1_0.java:249 )
at net.rim.wica.ag.services.message.MessageFactory$MessageFromDeviceSecurityHandler.getPlainPayload(Mes sageFactory.java:221)
at net.rim.wica.ag.services.message.MessageFactory.createMessageFromDevice(MessageFactory.java:236)
at net.rim.wica.ag.application.listener.CompactListener.doPost(CompactListener.java:163)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at net.rim.wica.ag.application.listener.CompactFilter.doFilter(CompactFilter.java:61)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:407)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.jav a:744)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Unknown Source)
[ERROR] (10/04 03:32:32) [[CompactListener]] Servlet.service() for servlet CompactListener threw exception
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at net.rim.wica.ag.services.lifecycle.DeviceEntity.getIntVersion(DeviceEntity.java:401)
at net.rim.wica.ag.services.lifecycle.DeviceEntit.getSecurityVersion(DeviceEntity.java:119)
at net.rim.wica.ag.services.security.DeviceVerionProvider.getSecurityVersion(DeviceVersionProvider.java :36)
at net.rim.wica.transport.internal.security.SecureMessageV1_0.verifyVersion(SecureMessageV1_0.java:275)
at net.rim.wica.transport.internal.security.SecureMessageV1_0.verifySecurity(SecureMessageV1_0.java:249 )
at net.rim.wica.ag.services.message.MessageFactory$MessageFromDeviceSecurityHandler.getPlainPayload(Mes sageFactory.java:221)
at net.rim.wica.ag.services.message.MessageFactory.createMessageFromDevice(MessageFactory.java:236)
at net.rim.wica.ag.application.listener.CompactListener.doPost(CompactListener.java:163)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at net.rim.wica.ag.application.listener.CompactFilter.doFilter(CompactFilter.java:61)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:407)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.jav a:744)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Unknown Source)



Cause

An issue occurs with the BlackBerry MDS database upgrade script during a large data upgrade.



Resolution

BlackBerry MDS upgrade to BlackBerry Enterprise Server software version 4.1 service pack 2 or 4.1.3
  1. Run the BlackBerry Enterprise Server software version 4.1.2 installer.
  2. When prompted, restart Windows®.
  3. The BlackBerry Enterprise Server installer window will display prompting you to continue the BlackBerry Enterprise Server installation. Select the appropriate BlackBerry MDS database upgrade script before continuing with the BlackBerry Enterprise Server installation.
    • To upgrade to BlackBerry Enterprise Server software version 4.1.2, replace the following files located in this directory, $BES_INSTALL_ROOT_DIR$\\ConfigUtil\db\AGDatabases\Server\DBInstallScripts\sqlserver\4.1:
      • UpgradeV20060502.sql
      • UpgradeV20060519.sql
      • UpgradeV20060529.sql
      • UpgradeV20060724.sql
      • UpgradeV20060726.sql The default installation directory is C:\Program Files\Research In Motion\BlackBerry Enterprise Server\ConfigUtil\db\AGDatabases\Server\DBInstallScripts\sqlserver\4.1.
    • To upgrade to BlackBerry Enterprise Server 4.1.3, replace the following files located in this directory, $BES_INSTALL_ROOT_DIR$\\ConfigUtil\db\AGDatabases\Server\DBInstallScripts\sqlserver\4.1:
      • UpgradeV20060502.sql
      • UpgradeV20060519.sql
      • UpgradeV20060529.sql
      • UpgradeV20060724.sql
      • UpgradeV20060726.sql
      • UpgradeV20060818.sql The default isntallation directory is C:\Program Files\Research In Motion\BlackBerry Enterprise Server\ConfigUtil\db\AGDatabases\Server\DBInstallScripts\sqlserver\4.1.
  4. Continue with the BlackBerry Enterprise Server installer.
Runtime exception appears in the BlackBerry MDS log file following the BlackBerry Enterprise Server upgrade
If the runtime exception appears in the BlackBerry MDS log file following the BlackBerry Enterprise Server upgrade, complete the following steps:
  1. Stop BlackBerry MDS Windows Services.
    • For a BlackBerry Enterprise Server 4.1.2 upgrade, run MDSSDataMigrateTo412.sql against the BlackBerry MDS database on the Microsoft SQL Server
    • For a BlackBerry Enterprise Server 4.1.3 upgrade, run MDSSDataMigrateTo413.sql against the BlackBerry MDS database on the Microsoft SQL Server.
  2. Start the BlackBerry MDS Windows Service.
The following are sample steps to run the script on Microsoft SQL Server 2000 when upgrading to BlackBerry Enterprise Server 4.1.3
  1. Stop the BlackBerry MDS Windows Service through the Windows Control Panel and back up the BlackBerry MDS database.
  2. Start the Microsoft SQL Query Analyzer and log in using a BlackBerry MDS database owner account or a super user account.
  3. Open the MDSSDataMigrationTo413.sql file in a text editor, copy all content, and paste it in the Microsoft SQL Query Analyzer.
  4. Replace _DATABASENAME_ in the first line with the BlackBerry MDS database in your environment.
  5. Run the all script in the Microsoft SQL Query Analyzer.
  6. If no error occurs, start the BlackBerry MDS Windows Service.
Note: Contact BlackBerry® Technical Support Services for applicable database scripts.
__________________
http://blog.port3101.org/hdawg/
Reply With Quote
Sponsored Links
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Software Config Issue (upgrade 3rd party app) Joolie Port 3101: The BES Admin Bar & Grill 1 11-17-2010 05:56 AM
BES application upgrade issue deltecs_bes Port 3101: The BES Admin Bar & Grill 1 04-30-2010 03:00 PM
KB15678 - Unable to complete BlackBerry Configuration Database upgrade... Si Featured BlackBerry KB Articles 0 03-20-2009 04:13 AM
KB14537 - Issue with a BlackBerry MDS database upgrade script during a large data.... Si Featured BlackBerry KB Articles 0 03-05-2009 04:42 AM
KB16184 - DB Upgrade Failed error when upgrading BESMgmr database during BES upgrade hdawg Featured BlackBerry KB Articles 0 01-14-2009 07:44 PM


All times are GMT -4. The time now is 11:23 PM.
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2019, vBulletin Solutions, Inc.


 

SEO by vBSEO 3.3.2 PL2