IBM i2 ibase 8 Upgrading to IBM i2 ibase 8 or IBM i2 Analyst's Workstation 8 VERSION MAY 2012

Transcription

1 IBM i2 ibase 8 Upgrading to IBM i2 ibase 8 or IBM i2 Analyst's Workstation 8 VERSION MAY 2012

2 Note: Before using this information and the product it supports, read the information in Notices on page 24. This edition applies to version 8, release 9, modification 1 of IBM i2 ibase (product number 5725-G15) and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces part number Copyright International Business Machines Corporation 1991, US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contacting IBM Support IBM Support provides assistance with product defects, answers FAQs, and helps users resolve problems with the product. Before you begin After trying to find your answer or solution by using other self-help options such as technotes, you can contact IBM Support. Before contacting IBM Support, your company or organization must have an active IBM software subscription and support contract, and you must be authorized to submit problems to IBM. For information about the types of available support, see the Support portfolio topic in the Software Support Handbook. Procedure To contact IBM Support about a problem: 1. Define the problem, gather background information, and determine the severity of the problem. For more information, see the Getting IBM Support topic in the Software Support Handbook. 2. Gather diagnostic information. 3. Submit the problem to IBM Support in one of the following ways: Online through the IBM Support Portal at You can open, update, and view all of your service requests from the Service Request portlet on the Service Request page. By phone: For the phone number to call in your region, see the Directory of worldwide contacts web page at Results If the problem that you submit is for a software defect or for missing or inaccurate documentation, IBM Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the IBM Support website daily, so that other users who experience the same problem can benefit from the same resolution. Publication number SC

3 Contents IBM i2 ibase Upgrading to IBM i2 ibase 8 or IBM i2 Analyst's Workstation Contacting IBM Support...2 Who should read this white paper?...3 Planning the upgrade...4 Best practices throughout the upgrade process...7 The upgrade process...9 Part 1: Upgrading to SQL Server 2005 or Part 2: Upgrading ibase clients...9 Part 3: Upgrading the databases...11 Part 4: Converting security files and databases to Unicode...14 Part 5: Configuring new features...15 Frequently Asked Questions Unicode Conversion...17 Troubleshooting...18 Appendix A: Client file types used by ibase...20 Appendix B: Database file types used by ibase...21 Appendix C: Selectively upgrade schedules in the Scheduler database...22 Appendix D: Additional Information...23 Notices...23 Trademarks...24 Who should read this white paper? This document provides guidance for people involved in upgrading to IBM i2 ibase 8.9 or IBM i2 Analyst's Workstation 8.9. It explains the upgrade process from all versions of ibase 4, 5, and 8 (including ibase Database Replication) and Analyst's Workstation 2, 3, and 8 (which include ibase 4, 5, and 8 respectively). As some of the powerful new features of ibase 8 only work if storing data in Microsoft SQL Server 2005 or 2008 for example, Bulk Importing and Search 360 ibase databases currently running Microsoft SQL Server 2000 should be converted to Microsoft SQL Server 2005/2008. For further information about upgrading to a later version of SQL Server, please refer to the white paper named Upgrading ibase 8 databases to SQL Server 2005 or This document is designed to provide sufficient information to help you to plan and execute your upgrade to ibase 8.9. The upgrade route described should be closely followed to avoid issues that may hamper or delay your upgrade process. 3

4 Planning the upgrade The upgrade process to ibase 8.9 is designed to meet the needs of multiple types of environment. Depending on the setup within your organization, a number of deployment options are available to minimize the impact on day-to-day operations. Important: IBM i2 Intelligence Analysis software at version 8.9 is not compatible with earlier versions of i2 software. Upgrading directly is not supported. To install IBM i2 software at version 8.9, you must first uninstall all of your existing i2 software, then install the new versions. Before performing an upgrade, the following areas should be taken into account: Original system configuration and use Requirements of the system after the upgrade Client locations Timescale for deployment Original system configuration and use Every ibase deployment is configured to match the needs of different users, so it is important that you recognize which features end users are currently using, and ensure that these are configured correctly after the upgrade. Requirements of the system after the upgrade You should perform an analysis of the new features of ibase 8 to ensure that all the features relevant to your organization are set up correctly. Client location The installation process will differ depending on the number of users and the method of connection used by ibase clients when connecting to the server. For deployments in organizations that only use locally hosted databases and clients, the upgrade may take place in a single phase. For deployments in organizations that include remote users, large numbers of clients, or who share data with other agencies, a phased approach to the upgrade may be more suitable. This will ensure that all relevant parties are given a chance to upgrade their client software before the database upgrade takes place. Depending on the number of client machines involved, you can carry out deployment of the ibase 8 clients manually, or schedule it for automatic deployment using enterprise systems management software. Timescale for deployment Creating a realistic timescale for deployment will allow you to plan the deployment around the peak times of your system use. Database size increases Ensuring that you have enough disk capacity is of vital importance when planning your upgrade to ibase 8. For SQL Server databases, the conversion to Unicode and implementation of Search 360 indexing both require a significant amount of disk space. 4

5 The best method of calculating the amount of space required is to use a test system that matches your production environment; however the following information can be used to provide an estimate of the space requirements. Based on a database that has a relative size of 1: The temporary data usage will increase to 4 times the original database size whilst Unicode conversion is taking place The size of the database after Unicode conversion will be 1.5 times the original database size if the database transaction log has been reduced. The temporary data usage will increase to 6 times the original database size whilst Search 360 is being enabled The total final size will be 4.5 times the original database size, if the database transaction log has been reduced. In summary, you should ensure that you have at least 6 times the original database size in free disk space before attempting an upgrade. Note: This size does not take into account other information stored on the server. 5

6 6

7 Best practices throughout the upgrade process Test the upgrade first Perform an upgrade to ibase 8.9 in a test environment before you perform it against a live system. Note: The test environment you use should closely match your current system, allowing you to troubleshoot any issues that arise. Remember that IBM i2 Intelligence Analysis software at version 8.9 is not compatible with earlier versions of i2 software. Upgrading directly is not supported. To install IBM i2 software at version 8.9, you must first uninstall all of your existing i2 software, then install the new versions. Communicate with all system users Once the upgrade testing has been successfully completed, you should send a communication to all system users advising them of the planned work, timescales, and how this will affect them. Note: You should continue this communication throughout the process, alerting users to the progress that has been made. Back up your system It is of utmost importance that you make a complete backup of your existing ibase configuration and databases and verify they are successfully backed up before and after you perform the upgrade. To back up your system, follow the instructions in Part 3:Upgrading the databases - Identify and backup ibase databases, security files and ibase SQL Server databases to ensure that the upgraded databases are successfully backed up and your changes stored. Note: Ensure that backups are stored in different secure locations to insure against any unforeseen issues and to prevent extra space being used on your Server. Use Microsoft SQL Server 2005 or 2008 ibase 8.9 is only supported on Microsoft SQL Server 2005 or If you need to upgrade both ibase and Microsoft SQL Server, do so in two phases. If upgrading from ibase 5, first perform the Microsoft upgrade, and then upgrade all ibase components. If upgrading from ibase 8.0, 8.1 or 8.5, first upgrade all ibase components, and then perform the Microsoft upgrade. Database Administration Both before and after the database has been upgraded, a Schema Integrity Check should be carried out to ensure that the database is in a stable condition. The Wizard checks the schema, reporting any problems that were found and offering to fix those it can repair. Additional actions for users of ibase 8 Scheduler When making any changes to the database, you should ensure that the ibase Scheduler has completed any outstanding import or export tasks, and has been turned off before the change takes place. If Scheduler databases are on more than one SQL Server, an alternative to stopping the Scheduler service is to deactivate any Scheduler triggers that operate over the databases on the server you are upgrading. This will ensure that scheduled imports for databases on other servers continue unaffected. 7

8 Once the modification has been completed, enable ibase 8 Scheduler to perform its imports and exports by either starting the Scheduler service or reactivating the Scheduler triggers using the ibase 8 Scheduler Configuration tool. Additional actions for replicated databases You must carefully plan the upgrade of replicated security files and databases. Data consistency issues can arise if changes are made to the security files or databases at multiple sites while the databases are not being replicated. When making any changes to the database, you should ensure that database replication has been stopped by the SQL Server DBA before the changes are carried out. Replication of the audit log is optional, but if you have chosen to replicate it, the SQL Server DBA must stop replication on this database too. We advise that you consider the upgrade from ibase 5 to ibase 8 as a schema change, and follow the recommended method for this process as documented in the Setting Up ibase Database Replication section of the Administration Center, in combination with the notes provided in this white paper. The new ibase 8 Audit History features are supported with ibase Database Replication, so the upgrade from ibase 5 to ibase 8 is an opportunity to turn it on as part of the schema change process. See the ibase Administration Center for full details of the steps involved. ibase replication does not support mixed SQL Server environments, so you should upgrade or migrate the publishing database to SQL Server 2005 or SQL Server 2008 before any of the subscribers. When you do so, it will be necessary to remove replication. Again, you should consider this operation to be a schema change, to prevent data changes occurring when SQL Server replication is not configured. When performing an upgrade of SQL Server 2000, the publication and subscriptions can remain on the servers. However, you should refer to the steps Microsoft have published on their support pages about running the Snapshot Agent to complete the upgrade process. Once the change is complete, the SQL Server DBA should restart replication between the servers before allowing any users to access the database again. Additional considerations for Analyst's Workstation Analyst's Workstation uses Analysis Services for storing Data Miner 8 cube data. When upgrading from ibase 5 to ibase 8, the Data Miner cubes will continue to function. However, if you choose to upgrade or migrate your ibase databases from SQL Server 2000 to SQL Server 2005/2008, you will also have to convert your cubes from SQL Server 2000 Analysis Services to SQL Server 2005/2008 Analysis Services. There are a number of known limitations when upgrading from Analysis Services 2000 to Analysis Services 2005/2008 that affect Data Miner 8 cubes. For this reason, if you are planning to upgrade from Analysis Services 2000 to Analysis Services 2005/2008, delete all existing cubes in Data Miner 3 prior to the upgrade from ibase 5 to ibase 8 and SQL Server 2000 to 2005/2008. You can then rebuild them on the Analysis Services 2005/2008 server using Data Miner 8 after the ibase databases have been upgraded. 8

9 The upgrade process In order to minimize the disruption to end users, you can perform each of the parts listed below separately, reducing the time that systems need to be continuously offline: Part 1: SQL server upgrade (optional) Part 2: Client software upgrade Part 3: Database upgrades Part 4: Conversion to Unicode Part 5: New feature configuration (optional) Note: In order to ensure that the upgrade has installed all the features correctly, the database should be opened and closed in ibase Designer 8.9 before use. After you have upgraded a database using ibase 8.9, you should not attempt to access that database with a version of ibase Designer earlier than 8.9. During the upgrade, should you decide to use a staggered upgrade route, upgraded ibase 8 clients and ibase 5 clients are able to interoperate with ibase 5 databases. However, ibase 5 clients are not able to work with ibase 8 databases. Part 1: Upgrading to SQL Server 2005 or 2008 Some of the new features that are available in ibase 8.9 are only supported if the database is running SQL Server 2005 or If you would like to upgrade or migrate your SQL Server version, please read the white paper named Upgrading ibase 8 databases to SQL Server 2005 or 2008 that will guide you through this process. Note: If your database was created using an earlier version than of ibase you will need to upgrade to version before attempting to upgrade to SQL Server. If you are upgrading from 8.0, 8.1, or 8.5 upgrade ibase before upgrading SQL Server. Part 2: Upgrading ibase clients Depending on the volume and location of end users, you can update the ibase client software on a machine-by-machine basis, or deploy it across a network using Windows Installer and enterprise systems management software. Whichever method you use to deploy the client software, the following actions need to be performed. Backing up client data There are a number of files that are deployed with the ibase client and may have been modified by end users. When the upgrade occurs, these will be overwritten with the version 8 default versions. A full list of the files that may be affected can be found in Appendix A: Client file types used by ibase. If these files have been modified, you must back them up before the upgrade takes place. 9

10 Upgrading the client software ibase 8 clients are compatible with databases that were set up on ibase 5, so when the backup of client data is complete, you can begin the update of client software. Notes: You may upgrade your ibase 5 clients, and then upgrade your ibase 5 databases at a later date. However, you must upgrade any ibase 4 databases before you can use them with ibase 8. ibase 8 Designer does not support backward compatibility. You should only use it with databases that have been upgraded. Users of ibase Designer should upgrade their installed software at the same time as the databases are upgraded. IBM i2 Text Chart may not be used with an ibase 8 client and an ibase 5 database. To use Text Chart with an ibase 5 database, you must use an ibase 5 client and TextChart 3. To use Text Chart with an ibase 8 database, you must use an ibase 8 client and Text Chart 8. Merging the client data changes When the upgrade is complete, you will need to restore any client data that was included in the backup process to the client system. Files that can be copied directly You can copy the following files directly from the backup: WSExclude.txt FTExclude.txt i2.wor i2.apr Files that require merging You must merge the following files from the backup with the new ibase 8 versions of each file: commandgroups.mdb iconlist.txt i2.mxd For each of the above files: 1. Open the new version that has been installed with ibase Merge in any changes that have been made to the ibase 5 file. 3. Save the file in the installed location. Upgrading the ibase Scheduler In order to allow the scheduler to interact with clients that have been upgraded to ibase 8, you must also update ibase Scheduler. This method will retain all scheduler history in the Scheduler database: 1. Stop the Scheduler service. 2. Upgrade ibase 5 to ibase 8 on the machine running the Scheduler service. 3. Restart the Scheduler service. 10

11 Note: You cannot run ibase 5 and ibase 8 on the same machine. Therefore, if you are unable to update all clients in the set period, you will need to install ibase 8 Scheduler and an ibase 8 system to run on a different machine from their ibase 5 equivalents. For further instructions, see Appendix C: Selectively upgrade schedules in the Scheduler database. Note: Upgrading the security files and databases to ibase 8 will prevent ibase 5 Scheduler from running scheduled imports and exports. Part 3: Upgrading the databases Stop the ibase Scheduler Before backing up the database, ensure that the Scheduler service on the machine that runs scheduled tasks is not performing an import or export in a database that you are in the process of updating. Then, place the service in the stopped state to prevent future imports or exports from running. Note: If the Scheduler is in the process of running an import or export, wait for it to complete before stopping the service. For information on how to stop a Windows service, refer to the Microsoft support pages. Note: If multiple ibase databases are using the Scheduler, an alternative to stopping the service is to deactivate any Scheduler triggers that operate over the databases you are updating. This will ensure that scheduled imports for the other databases continue unaffected. Identifying ibase databases, security files, and ibase SQL Server databases You should always back up all ibase files prior to any maintenance work, to create a restore point. Identifying all ibase databases You can obtain the location and names of databases on each machine through the MRU List Manager accessed from the Tools menu in either ibase or ibase Designer: The list of files you obtain from the MRU List Manager will provide the paths and names of the databases that have been opened by the currently logged-in user even if the database no longer exists. It is advisable to ask the user of the machine to provide this list for you prior to the upgrade. Identifying all ibase database files Before you upgrade an ibase database, you must back up every file it uses. Locating the ibase security (.ids) and database (.idb) files will reveal most of the others. The ibase security file is usually located in the same folder as the databases it secures. The files that you should back up are listed in Appendix B: Database file types used by ibase. 11

12 Determining the types of database in use The ibase security and database files will help you identify the locations of any SQL Server databases that ibase uses. To determine whether the security and database files are SQL Server or Access: 1. In an ibase 5 or ibase 8 client (not ibase 8 Designer), log in as a system administrator, and open each database. 2. From the File menu, select Security File Properties and Database Properties in turn. In the case of SQL Server security files and databases, the properties dialogs will display the database name and the SQL Server name. In general: An ibase database name will not contain any spaces, and will always contain at least one underscore character. An ibase database will also have an associated audit log database that has the same name as the database, with a suffix of _Log. An ibase security file database is suffixed with _Sec. You must make a note of the names of the SQL Server and the ibase databases, ready for the next part of the process. Backing up all ibase files and databases When you have a full list of all the files and databases that are required, you can start the backup process. Additional actions for replicated databases When making any changes to the database, you should ensure that database replication has been stopped by the SQL Server DBA before the changes are carried out. Replication of the audit log is optional, but if you have chosen to replicate it, the SQL Server DBA must stop replication on this database too. Note: You will need both network and database admin permissions in order to back up your system successfully. Performing the SQL Server database backup To back up the SQL Server database: 1. Log in to the system with database administrator rights. 2. Verify that there are no users accessing the database. 3. Set the user access option on the ibase SQL Server databases to single user. Provided the DBA does not exit the database, only the DBA will have access to the databases, preventing changes from being made during the backup. 4. Perform the backups (including any Analysis Services databases and Audit Log databases for this database), and then take the databases offline. Note: Changing the user access option to single user will not prevent users from accessing the database altogether after the SQL Server DBA has made the backup and exited the database. However, it does restrict the number of users and the amount of change that may occur if a user does access the database. If you are upgrading multiple databases, you must perform steps 3 and 4 sequentially for each database in turn. This will prevent other ibase users from opening the database and locking you out. 12

13 1. Log in to the system with network administrator rights. 2. Identify the files to be backed up from the list that you prepared earlier. 3. Back up the files to a safe location. Between backing up and upgrading the databases, you must not allow any users to access ibase security files or databases. Locking users out of the database after the backup ensures that no data loss occurs in the unlikely event that you encounter problems during the upgrade. Note: Ensure that the backup has been moved to a secure location before proceeding, and restore the backup to a test environment to ensure all key files have been recorded. Upgrading the security files and databases Usually, you will upgrade all security files and databases, but there may be occasions when you need to keep some databases in an earlier ibase format. For example, you might share these databases (or charts created from them) with other agencies that are not in a position to upgrade. If there is a reason why you cannot upgrade a particular database to ibase 8, you can still selectively upgrade other databases. However, you should be aware that when you upgrade a security file, you must also upgrade all databases secured by that security file. To upgrade a subset of databases that are secured by a single security file, you must copy the security file and move the database that you want to convert to a new location. Note: Copying a security file that is in SQL Server format requires that you also copy the SQL Server component of the security file to a new instance of SQL Server. Finally, to perform the upgrade of the ibase database and its security file: 1. If you have a SQL Server security file, ask the database administrator to bring the security database online. 2. Open the security file in ibase 8 Designer; this will initiate the upgrade. 3. Ask the database administrator to bring the log file and database online. 4. Open the database in ibase 8 Designer. 5. Select the Upgrade to ibase 8 option when prompted; this will initiate the upgrade. 6. Ask the database administrator to change the upgraded database to multi-user mode, and allow the users back in to the database. During this process, ibase 8 Designer displays a series of warning and status messages that you must acknowledge in order to continue. When the upgrade is complete, you can only roll back the process by reverting to your backups of the connection files and SQL Server databases. Additional actions for users of ibase 8 Scheduler If you are planning to perform a staggered upgrade, enable ibase 8 Scheduler to perform its imports and exports by either starting the Scheduler service, or reactivating the Scheduler triggers using the ibase 8 Scheduler Configuration tool. Additional actions for replicated databases If you are planning to perform a staggered upgrade, ask your SQL Server DBA to reconfigure replication between the servers before allowing any users to access the database again. 13

14 Part 4: Converting security files and databases to Unicode As part of the process of upgrading to ibase 8.9, if you want to be able to store Unicode in your database or use IBM i2 ibase IntelliShare, any databases that have not been converted to Unicode should be converted as part of the upgrade process before any of the new features are used. This will need to be done for any SQL Server database that is being upgraded that has been created in ibase 5 or earlier and has not already been converted to support Unicode. Please note: Unicode conversion will increase the size of your database considerably, and you will need to ensure that you have significant disk space before beginning the upgrade process. We recommend running the upgrade on a test environment before attempting to upgrade any live system, and that a backup is made before the upgrade is started. The following metrics may help you to estimate the space requirements: Peak use While the conversion process is running, a large amount of data is stored in temporary tables. On average, this is four times the size of the database. Final size after shrinking After the database conversion has completed (and maintenance steps such as archiving the transaction log have occurred), the database is expected to be around one-and-a-half times its original size. Warning: Before converting to Unicode, you should back up your security file and all databases secured by this file, and ensure that both the scheduler and database replication if used are turned off. To convert a security file to Unicode: 1. In ibase Designer, log on but do not open the database. 2. From the Tools menu, select Database Setup > Convert to Unicode > Convert Security File to Unicode. Once the conversion is complete, convert all the databases secured by the converted file the conversion of a large database may take several hours, and you cannot interrupt the conversion once started: 1. Open the database secured by the converted security file. 2. If you use Full-Text Search, delete the existing indexes. You will need to recreate the index once the conversion is complete. 3. From the Tools menu, select Database Setup > Convert to Unicode > Convert Database to Unicode. Note: After converting the database to Unicode, you will need to warn users that new information will be stored using multiple data encodings. ibase's Sounds Like operations are only supported when using English search terms. Note: When a security file has been converted to Unicode, it is only compatible with databases that have also been converted to Unicode. For further information on Unicode support, see the Administration Center. 14

15 Part 5: Configuring new features Once the databases have been upgraded, you can configure the new features of ibase 8 to match end user requirements. The following features do not require any additional configuration: Schema changes Importing the contents of a folder You must configure the following features before use: User accounts Audit history and restricted audit logs (SQL Server only) Alerting (SQL Server only) Unicode support Database subsets Search 360 (SQL Server 2005 or 2008 only) Link Reporting XML import and export (SQL Server 2005 or 2008 only) User accounts You can set up user accounts either to use the sign-on credentials of a network user (ease of use), or to match a specific security policy. Additionally, you can modify the user accounts to enable alerting and access to the audit history. Setting up single sign-on ibase 8 introduces Windows single sign-on. In order to support existing ibase user functionality and access control restrictions, each Windows user or group must have an ibase user account. In order to improve security, only Windows users and groups that are domain-based and accessible through Active Directory (via LDAP) are supported. You cannot create ibase user accounts for Windows users or groups that are local machine-based. The simplest mapping between ibase and a Windows user or group is described below: Windows user when the user opens an ibase security file, they are automatically logged on if their Windows credentials match those of a specific Windows user that is mapped to an ibase user in the security file. They log on as that ibase user. Windows group when the user opens an ibase security file, they are automatically logged on if they are a member of a Windows group (for example, Administrators) that is mapped to an ibase user. In the case where there are multiple ibase user matches (because the Windows user is a member of multiple groups), the user is prompted to select an ibase user. For more information on how to set up single sign-on accounts, please refer to the ibase 8 Designer Help pages. 15

16 Defining a security policy ibase 8 provides a significant improvement to security management that enables you to define and maintain a password security policy for users who do not use single sign-on. A security policy is specific to each security file, and can only be set up by users who have access to ibase 8 Designer: Use ibase 8 Designer to define a security policy. You can define this in any existing ibase security file, once it is upgraded to ibase 8. The policies you define should match those of the wider corporate IT strategy, to avoid ibase users facing unexpected logon failures that may come at operationally inconvenient times. For more information on how to set up security policies, please refer to the ibase 8 Designer Help pages. Granting users permissions to use auditing and alerting features Alerting only users who have been granted permission can define alerts. For an ibase 8 user to receive an alert by , the user s address must be specified in the security file. For alerts to be issued from a particular database, alerting must be turned on in that database using ibase 8 Designer. Audit History you can restrict access to the audit logs of users who work on sensitive data. This requires changes to the user accounts of those who work on sensitive data, and to the user accounts of those authorized to view restricted audit logs. Users who do not have access to restricted audit logs can still view the audit history of any record accessible to them, but they cannot display a list of records worked on by users with restricted audit logs. You can also prevent users from viewing the history of entity and link records. A user who has the Audit Administrator role uses the Audit Viewer or ibase Audit History dialog in the usual way, and they can view the records touched by any ibase user. Use ibase 8 Designer to manage the permissions of users. Initializing database subsets You can use database subsets to give users in the field a small ibase database to work with. Database subsets have the same design as your main database, and contain a small selection of records from it (up to a maximum of 50,000 records). Optionally, you can synchronize the main database and a database subset in order to: Upload new records from the database subset into the main database Download a selection of new and updated records from the main database into the database subset You use ibase (not ibase Designer) to create and synchronize database subsets. In ibase, you must initialize the database for database subsets before you can use this feature. For further information on database subsets, see the Administration Center. Setting up Search 360 Search 360 is the recommended replacement for Full-Text Search in ibase 8. It is only supported on SQL Server 2005 or 2008 databases. For more information on how to set up Search 360, please refer to the ibase 8 Administration Center. Note: Be aware that enabling Search 360 will significantly increase the size of your database, and may take considerable time to complete. Test the configuration before you apply it to a live environment. 16

17 Setting up Link Reporting Link Reporting can be enabled by a Database Administrator using ibase using the Initialize Database for Link Reports option from the Tools menu. XML import and Export (SQL Server 2005 or 2008) In order to set up your system to allow XML import and export, bulk importing must be initialized and configured. Database subsets must also be initialized for XML export. For further information on bulk importing and database subsets, see Administration Center Help. Frequently Asked Questions Unicode Conversion Q: Who needs to convert their databases to Unicode? A: Anyone who is upgrading a SQL Server database that was created in ibase 5 or earlier; has not already converted their database to support Unicode; and who wishes to upgrade to ibase 8.9 and to store Unicode in their database or use IBM i2 ibase IntelliShare. Q: How do I tell whether my database has already been converted to Unicode? A: Using the Tools > Database Setup > Convert Database to Unicode option, you will be notified that the database already supports Unicode and the process will not continue. If the database does not support Unicode, you will be guided through the upgrade process. You can cancel this process before it starts. Q: What do I need to do before converting to Unicode? A: Before converting a production environment to Unicode: Back up your SQL database. Try the conversion on a test environment that replicates your production environment as closely as possible. Ensure that you have sufficient space to perform the conversion. As the conversion may take some time, try to arrange the conversion to occur at a time when the system is not in use. Q: How long will the conversion take? A: The time taken by the conversion process varies between databases, and may be many hours for large databases. Test the conversion on a test system to get an accurate estimate before converting your production environment. Q: How much disk space will the conversion use? A: There are two factors to consider when converting your database to Unicode: Peak use While the conversion process is running, a large amount of data is stored in temporary tables. On average, this is four times the size of the database. Final size after shrinking After the database conversion has completed (and maintenance steps such as archiving the transaction log have occurred), the database is expected to be around one-and-a-half times its original size. 17

18 Troubleshooting Restoring ibase files and SQL Server databases If the upgrade fails, to roll back the process: 1. Restore all SQL Server ibase databases, ibase audit log databases, and ibase security file databases overwriting the partially upgraded databases. 2. Restore all.ids,.idb,.idl and.idx files. SQL Server 2000 symptoms When upgrading an ibase database hosted on SQL Server 2000, you may receive a message letting you know you do not have dbo rights. To solve this issue, please ensure that you have dbo rights on the SQL Server database. Issues after Unicode conversion Rebuilding the Full Text Search Index After an ibase database has been converted to Unicode, ibase users may see the following error message when they try to rebuild the Full Text Search index: File 'sysft_i2catalog' cannot be reused until after the next BACKUP LOG operation. To solve this problem: 1. Launch SQL Server Management Studio 2. Right-click the ibase database, and select Tasks > Backup from the context menu 3. For Backup type, select Transaction log 4. Perform the backup After performing the backup, you can try again to rebuild the Full Text Search index. Indexing performance SQL Server databases that have already been upgraded to ibase 8 from an earlier version and have Unicode support enabled may experience performance problems when Queries or Find operations are carried out. Locating connection files The following list gives some reasons why you may not be able to locate connection files for all the databases on an SQL Server instance: The MRU list on a machine has been cleared, so the database was not reported. Searching the entire network for ibase databases is not feasible. A machine was overlooked during the machine identification phase of the upgrade. A machine that was used for ibase has been retired due to age or failure. The database still resides on the SQL Server machine even though the database connection file (.idb) is no longer in use (and may have been deleted). The original network share location for connecting files has been dropped or changed. 18

19 You can obtain the ibase version and location of the connection file for the ibase security file or database by examining the contents of the _Configuration table. (An ibase log database does not contain this table because all its details can be obtained from its associated database connection file.) The _Configuration table has two columns: Item and Data. Item contains the name of the entry, while Data contains the value for the entry. The following table details the value of the Item column for the relevant entries: Security file Database Entry within the _Configuration table Security file location SQLServer:ConnectionFile SYS:SecurityFile Database location Not applicable SQLServer:ConnectionFile Version SYS:Version SYS:Version You can determine whether a database is used by Analyst s Workstation, and which Analysis Server was used to build Data Miner cubes: The presence of a table named _dmcuberegister indicates that the database is used by Data Miner. The field Cube Location within the _dmcuberegister table contains the Analysis Server name. The name of the ibase database is contained in the Analysis Services database name. Using this information, your SQL Server DBA will be able to determine the Analysis Services databases that correspond to an ibase database. 19

20 Appendix A: Client file types used by ibase The following table displays the type of files that may be present on a client installation that should be taken into account when performing a backup: File name scheduler_database_name.mdb Description The database used to control imports and exports performed by ibase 5 Scheduler. The location of this database can be specified during the installation of ibase 5 Scheduler. CommandGroups.mdb Defines the set of command groups for use within security files. This file is installed with ibase on each machine, but may have been modified to define a different set of command groups for use with security files. Usually located in the CommandGroups subfolder of the ibase 5 installation folder, but ibase may have been redirected to look for this file in another folder. IconList.txt Defines the icons available to ibase and the mapping between the displayed name and the operating system file name. Usually located in the Configuration subfolder of the ibase 5 installation folder, but ibase may have been redirected to look for this file in another folder. WSExclude.txt FTExclude.txt Word Search and Full-Text Search word exclusion lists. Usually located in the Configuration subfolder of the ibase 5 installation folder. i2.wor, i2.mxd, i2.apr GIS workspace files used by ibase. These files are installed with ibase GIS Interfaces 2 on each machine, but may have been modified since installation. 20

21 Appendix B: Database file types used by ibase The following table displays the type of files that may be present on a database installation that should be taken into account when performing a backup: File name security_file_name.ids database_name.idb database_name.idl database_name.idx security_file_name.ids.bak, security_file_name.ids.bak1, n database_name.idb.bak, database_name.idb.bak1,...n database_name *.doc, database_name *.dot database_name.tct database_name *.ant Description ibase security file or ibase security connection file for SQL Server. ibase database or ibase database connection file for SQL Server. ibase audit log. This file exists for all ibase Access databases and ibase SQL Server databases that have been upsized from Jet format. Located in the same folder as the ibase database. Word search index for ibase Access databases. Located in the same folder as the ibase database. Backups of the security file created by an ibase version upgrade or when the security file was upgraded to SQL Server. Backup of the database file created by an ibase version upgrade or when the database was upgraded to SQL Server. ibase report templates. Located in the same folder as the ibase database. Text Chart template for use with the database. Located in the same folder as the ibase database. Analyst's Notebook template for use with the database. Located in the same folder as the ibase database. 21

22 Appendix C: Selectively upgrade schedules in the Scheduler database If some of your ibase databases are to remain in ibase 5 format, or you plan to upgrade over an extended period of time, it is possible to set up a system that contains two instances of the ibase Scheduler. As you cannot run ibase 5 and ibase 8 on the same machine, you will need to install ibase 8 Scheduler and an ibase 8 system to run on a different machine from their ibase 5 equivalents. This method will retain Scheduler logs in the ibase 5 Scheduler database for imports and exports that were executed before the database was upgraded. New log entries for ibase 8 databases will be created in the ibase 8 Scheduler database. ibase 5 Scheduler machine ibase 8 Scheduler machine 1 Install ibase 5 Scheduler Configuration tool. ibase 8 will be installed later. Note: It is not necessary to install the ibase 5 Scheduler service on this machine. 2 Stop the ibase 5 Scheduler service. 3 Copy the ibase 5 Scheduler database to the new Scheduler machine. 4 Open the copy of the Scheduler database using the ibase 5 Scheduler Configuration tool. 5 Purge the Scheduler logs. 6 Deactivate all the Scheduler triggers. 7 Upgrade this machine to ibase 8, ensuring that both the scheduler configuration tool and service are installed. 8 Open the copy of the Scheduler database using the ibase 8 Scheduler Configuration tool. This will upgrade the database to ibase 8 format. The Scheduler service will not attempt to execute any of the tasks because all the triggers have been deactivated. 9 Prior to upgrading a security file, deactivate all ibase 5 Scheduler triggers for databases that are secured with the security file. 10 On the ibase 8 Scheduler machine, after upgrading a database from ibase 5 to ibase 8, activate all ibase 8 Scheduler triggers for the upgraded database. 22

23 Appendix D: Additional Information What documentation is provided? To help you get the most from your investment, ibase 8 is provided with comprehensive help and release notes. Administrators using ibase 8 Designer are supported by a comprehensive online Administration Center that specifically addresses information needed for database configuration, maintenance and performance. The help is supported by an example database and (where appropriate) sample data Version compatibility considerations ibase 8.9 is only supported when used with compatible versions of IBM i2 products: IBM i2 Analyst s Notebook 8.9, IBM i2 Text Chart 8.9, IBM i2 ibase IntelliShare 8.9, and IBM i2 Analyst s Workstation 8.9. If you are using a combination of previous versions of these products, you must upgrade them all at the same time in order to maintain compatibility. For further information, please refer to the Release Notes. Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. 23

24 Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM United Kingdom Limited Hursley House Hursley Park Winchester, Hants, SO21 2JN UK Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. 24