Download Banner Enterprise Data Warehouse / Installation Guide / 8.3

BANNER ENTERPRISE DATA WAREHOUSE INSTALLATION GUIDE Release 8.3 April 2011 Trademark, Publishing Statement and Copyright Notice SunGard or its subsidiaries in the U.S. and other countries is the owner of numerous marks, including “SunGard,” the SunGard logo, “Banner,” “PowerCAMPUS,” “Advance,” “Luminis,” “DegreeWorks,” “fsaATLAS,” “Course Signals,” and “Open Digital Campus.” Other names and marks used in this material are owned by third parties. © 2011 SunGard. All rights reserved. Contains confidential and proprietary information of SunGard and its subsidiaries. Use of these materials is limited to SunGard Higher Education licensees, and is subject to the terms and conditions of one or more written license agreements between SunGard Higher Education and the licensee in question. This PDF is certified for use with Adobe Reader, version 7.x and higher. Some elements of this PDF may not render properly when viewed using earlier versions of the Acrobat Reader or with other PDF viewing applications. In preparing and providing this publication, SunGard Higher Education is not rendering legal, accounting, or other similar professional services. SunGard Higher Education makes no claims that an institution's use of this publication or the software for which it is provided will insure compliance with applicable federal or state laws, rules, or regulations. Each organization should seek legal, accounting and other similar professional services from competent providers of the organization’s own choosing. Prepared by: SunGard Higher Education 4 Country View Road Malvern, Pennsylvania 19355 United States of America Customer Support Center Website http://connect.sungardhe.com Documentation Feedback http://education.sungardhe.com/survey/documentation.html Distribution Services E-mail Address [email protected] Revision History Log Publication Date Summary April 2011 New version that supports Banner Enterprise Data Warehouse 8.3 software. Banner Enterprise Data Warehouse 8.3 Installation Guide Contents Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 SunGard software prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Terms Used in this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 BPRA Utility Config Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 OMBPlus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 SQLPLUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Step 1 Unzip edw80300i.zip file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Step 2 Modify OWB/OMB Parameter File, edw-params.tcl for Repository Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Step 3 Install OWB Repository for EDW . . . . . . . . . . . . . . . . . . . . . . . . 12 Step 4 Modify login.sql for Banner EDW database . . . . . . . . . . . . . . . . . . 13 Step 5 Build EDW functional objects on the warehouse database . . . . . . . . . 14 Step 6 Import and Deploy OWB Mappings using OMB*Plus . . . . . . . . . . . . 15 Step 7 Verify the state of the Banner EDW . . . . . . . . . . . . . . . . . . . . . . 16 Step 8 Configure the Administrative User Interface . . . . . . . . . . . . . . . . . . 16 Step 1 Copy the Banner EDW 8.3 Deployment Archive . . . . . . . . . . . . . . . 19 Step 2 Build the EDW Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Step 3 Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Step 4 Build and Configure Cubes . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Administrative UI issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Page not enabled for current user role(s) because INSTALL user is missing . . . 31 Checks and Balances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Error Mapping is INVALID in the database . . . . . . . . . . . . . . . . . . . . . . . 33 Staging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Streams Configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Set STREAMS_POOL_SIZE parameter . . . . . . . . . . . . . . . . . . . . . . . . 33 Option 1 - Set STREAMS_POOL_SIZE using ASMM . . . . . . . . . . . . . . . 34 April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Contents 3 Option 2 - Set STREAMS_POOL_SIZE NOT using ASMM . . . . . . . . . . . . 34 Restage an ODS stage table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 ORA-01422: exact fetch returns more than requested number of rows . . . . . . 36 Error restaging tables; ORA-20000: Retrieving source database link terminated . 37 ods_upgrade.sql . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Scripts not connecting correctly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 [product]_etl_install.sql scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 ORA-04045: errors during recompilation/revalidation . . . . . . . . . . . . . . . . 39 ORA-04063: package body "ODSSTG.MGKSTRM" has errors . . . . . . . . . . . 40 ORA-12545: Connect failed because target host or object does not exist . . . . . 42 ORA-20000: Adding a table rule terminated . . . . . . . . . . . . . . . . . . . . . . 43 ORA-20000: Exporting and importing LONG table data terminated . . . . . . . . 45 ORA-20000: Preparing to import terminated. . . . . . . . . . . . . . . . . . . . . . 46 ORA-20000: Retrieving source database link terminated . . . . . . . . . . . . . . 47 ORA-20000: Stopping the capture process terminated . . . . . . . . . . . . . . . . 48 ORA-26723: user "ODSSTG" requires the role "DBA" . . . . . . . . . . . . . . . . 48 ORA-31685: Object type failed due to insufficient privileges . . . . . . . . . . . . 49 ORA-31693: Table data object failed to load/unload . . . . . . . . . . . . . . . . . 50 ORA-31693: Table data object failed to load/unload . . . . . . . . . . . . . . . . . . . . . . . . 51 ORA-39014: One or more workers have prematurely exited . . . . . . . . . . . . 53 ORA-39083: Object type INDEX_STATISTICS failed. . . . . . . . . . . . . . . . . 54 ORA-39125: Worker unexpected fatal error . . . . . . . . . . . . . . . . . . . . . . 55 Cannot stage table; no matching records in MGBSTRM . . . . . . . . . . . . . . . 55 Installation stops responding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 [product]_stage.sql . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 ORA-20000: Preparing to import terminated. . . . . . . . . . . . . . . . . . . . . . 57 gurutlrp.sql script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 ORA-01031: insufficient privileges message Alumni/ODS views invalid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 OWB* and WB_OLAP* invalid objects . . . . . . . . . . . . . . . . . . . . . . . . . 60 UPD_80100* invalid objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 UPDATE_MBT* and DELETE_MBT* invalid objects . . . . . . . . . . . . . . . . . 61 LOAD_MFT_TRANS_HISTORY* invalid objects . . . . . . . . . . . . . . . . . . . 62 4 Banner Enterprise Data Warehouse 8.3 Installation Guide Contents April 2011 EDW_ADV_GIFT_EXTR invalid object . . . . . . . . . . . . . . . . . . . . . . . . . 62 OWB issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 API2422 Connection details are not set for the metadata location . . . . . . . . . 63 DELETE_MAT_PROSPECT_CONT_EXP package not found . . . . . . . . . . . 63 Error importing SUPPORTEDLANGUAGE American English . . . . . . . . . . . . 64 ods_repos.tcl fails; ORA-00922: missing or invalid option . . . . . . . . . . . . . . 65 RTC-5161. Error when trying to deploy the ODSMGR_LOCATION connector SOURCE_DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 OMB06312: Cannot modify any properties of a registered location except the password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Contents 5 6 Banner Enterprise Data Warehouse 8.3 Installation Guide Contents April 2011 Introduction This guide details the steps necessary to install the Banner Enterprise Data Warehouse (Banner EDW) in an Oracle 11gR2 or 10g environment. Refer to the Banner Enterprise Data Warehouse Release Guide and Banner Enterprise Data Warehouse Handbook for details regarding enhancements and functional content included with this release. There are three main components associated with this installation: • Install the EDW components and objects in the warehouse database • Install and configure the Oracle Warehouse Builder components • Install Cognos Reporting Tools Prerequisites Refer to the Banner Performance Reporting & Analytics (BPRA) Resource Guidelines document for the most current information about dependencies and compatibility with BPRA, Banner, and Third Party products. SunGard software prerequisites Banner Enterprise Data Warehouse 8.3 requires the following versions of products preinstalled: • Banner Operational Data Store 8.3 Terms Used in this Document Throughout this document there are references to the EDW. The EDW refers to theBanner Enterprise Data Warehouse. It is referenced solely as “EDW” to avoid confusion with references to the baseline Banner database. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Introduction 7 BPRA Utility Config Files The two primary utilities for installing BPRA products are the Oracle SQLPLUS tool and the Oracle Warehouse Builder (OWB) OMBPlus tool. SQLPLUS is the standard Oracle command-line program used to execute SQL scripts to implement database changes, for example, manipulating tables, packages, and other database objects, inserting rows of data. OMBPlus is basically the same type of utility, but is only used by OWB to manipulate the metadata that OWB uses to generate the ETL processes (called mappings) that move data from Banner to the ODS and EDW reporting database. Both of these utilities are executed at various points throughout a typical BPRA Install or Upgrade and when applying BPRA patches. Both utilities are driven using configuration files. The BPRA recommended Best Practices for managing the utility configuration files (and hence the configuration of the tools) is described in the following sections. OMBPlus OMBPlus runs scripts written in the TCL programming language. The primary BPRA configuration file for OMBPlus is named params.tcl. This driver TCL script contains calls to other scripts that define global variables and procedures used by the various BPRA TCL scripts for installation and configuration of the BPRA OWB components. These scripts are delivered in the “owb” directory within each product. The Best Practice recommendation is to copy the delivered scripts to a top-level directory where you can customize them, then they can be consistently referenced by future installation and patch deliveries. In this document <BPRA_HOME> refers to this centralized location where configuration scripts are stored and referenced by all the BPRA products as needed. For the EDW, copy the edw-params.tcl file from the owb\base directory to the top-level directory and update the existing params.tcl file (delivered with ODS) there to add a call to the edw-params.tcl file (similar to the “source ods-params.tcl” line) so that those variables get automatically set when OMBPlus starts up. Copy these scripts to your <BPRA_HOME> directory: • edw-params.tcl Update the params.tcl script to include the following line: • source edw-params.tcl The “params” script is typically executed each time OMBPlus is started up, by manually entering the “source” command, followed by the file name (fully qualified, if not in the current directory). As documented in the Banner ODS Installation Guide, you should have already modified the <OWB_HOME>/owb/bin/ombinit.tcl startup file to execute the params.tcl script on OWB startup. Inserting a call in the params.tcl script to execute edw- 8 Banner Enterprise Data Warehouse 8.3 Installation Guide Introduction April 2011 params.tcl script will cause this EDW configuration file to be automatically executed as well. SGHE also recommends that you create simple convenience procedures to automate such repeated tasks as entering long “cd” commands. Define the following procedure in bpra_init.tcl: proc cd1 { } { cd /u04/nbuild/edw83/install/temp/edw80300i/edw/owb } puts "cd1 to go to /u04/nbuild/edw83/install/temp/edw80300i/edw/owb" Then you can simply enter the command “cd1” to move to that particular directory. If there is a need to support multiple databases/environments from the BPRA code tree, another recommended SGHE Best Practice is to add a procedure to the initialization process to reset the desired variables to point to the different environment. A sample of this convenience procedure is delivered in the edw-params.tcl. The sample procedure is commented out at the bottom. Simply uncomment that procedure (including the “puts” statement that displays the help message reminder of the procedure name), will enable easy reconfiguration as needed. SQLPLUS The Oracle SQL*Plus utility runs a startup script (referred to as a User Profile) in the file “login.sql”. From the Oracle Configuring SQL*Plus document: SQL*Plus searches for the User Profile in your current directory, and then the directories you specify with the SQLPATH environment variable. SQL*Plus searches this colon-separated list of directories in the order they are listed. The BPRA products deliver a login.sql file in the install directory that includes the SQL*PLUS environment variable settings required by that product installation. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Introduction 9 10 Banner Enterprise Data Warehouse 8.3 Installation Guide Introduction April 2011 Install Banner Enterprise Data Warehouse This section details the steps necessary to install the Banner Enterprise Data Warehouse 8.3 product. Step 1 Unzip edw80300i.zip file The edw80300i.zip file includes all of the software components of the Banner EDW 8.3 release. 1.1. Unzip the edw80300i.zip file. These instructions refer to the <EDW_STAGE_HOME> directory. Wherever you see <EDW_STAGE_HOME> in a command, it is referring to the directory where you just unzipped the delivered media. Replace <EDW_STAGE_HOME> with the appropriate directory path when entering the commands detailed in this document. Step 2 Modify OWB/OMB Parameter File, edw-params.tcl for Repository Configuration The first installation requirement is to create the EDWSTG and EDWMGR schemas and register those schemas in the Oracle Warehouse Builder Repository. This repository stores information on OWB design components such as ETL mappings in addition to execution audit data. April 2011 2.1. Move to the location of the tcl configuration files. This will be the <BPRA_HOME> directory if you followed the Best Practices documented previously in the “BPRA Utility Config Files” section. 2.2. Review the following parameters and change them as necessary within edw-params.tcl. Parameter Description edw_home_dir The Location of the EDW Source Directory edwstg_pass EDW Stage Target Schema EDWSTG Password Banner Enterprise Data Warehouse 8.3 Installation Guide Install Banner Enterprise Data Warehouse 11 Step 3 Parameter Description edwmgr_pass EDW Star Target Schema EDWMGR Password edwodsmgr_pass ODS Source Schema ODSMGR (on ODS) Password Install OWB Repository for EDW Note Oracle 11g only - If you are installing or upgrading this product in an Oracle 11gR2 environment, you may run into warnings or errors while performing the import of specific projects into the OWB Repository. This looks to be an Oracle bug that we are currently working with Oracle on a resolution. Refer to FAQ 1-NXRZ3O for the workaround if you encounter issues during the import. 3.1. Position to correct directory before starting OMB*Plus. The OMB*Plus interface is installed with the OWB software. Because of the way in which OMB*Plus sets required environment variables, you must be positioned within the correct directory from a command line to properly start the application. Unix OMB*Plus startup location: $ cd $OWB_HOME/owb/bin/unix $ ./OMBPlus.sh OMB*Plus: Release 10.2.0.4.36 Copyright (c) 2000, 2006, Oracle. All rights reserved. Windows OMB*Plus startup location: D:> cd $OWB_HOME/owb/bin/win32 D:> OMBPlus.bat OMB*Plus: Release 10.2.0.4.36 Copyright (c) 2000, 2006, Oracle. All rights reserved. Note You must use either forward slashes (/) or double slashes (\\) for directory changes in a Windows environment. The OMB*Plus interface does not recognize the traditional DOS backslash specification. 12 Banner Enterprise Data Warehouse 8.3 Installation Guide Install Banner Enterprise Data Warehouse April 2011 3.2. Run start.tcl file in <EDW_STAGE_HOME>/owb/base directory. The repository creation process can now be started from within the OMB*Plus Environment. Unix and Windows OMB*Plus: 3.2.1. Enter the following command: OMB+> cd <EDW_STAGE_HOME>/owb/base OMB+> source start.tcl 3.2.2. Enter ‘i’ for Install when prompted whether you want to (u)pgrade, (i)nstall, or (r)ecreate project work list. After selecting your licensed products, those products will be dynamically included in the script built for the import and deploy process. The start.tcl process will populate the OWB Repository, the OWB Target Schema, and Repository Access User based on the edw-params.tcl values. 3.2.3. Review the start.log output file within the <EDW_STAGE_HOME>/owb/ directory. base/log Step 4 4.1. Modify login.sql for Banner EDW database Move to the <EDW_STAGE_HOME>/install directory cd <EDW_STAGE_HOME>/install April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Install Banner Enterprise Data Warehouse 13 4.2. Modify the login.sql file located in the <EDW_STAGE_HOME>/install directory to define your institution-specific parameters. The SQL*Plus variables to modify are: SQL*Plus Variable Description home_dir The home_dir variable is used by the installation process to determine where scripts reside on your server. This variable should be set to the root level of your EDW install media. For example, on a Unix system, this value would be specified as /u02/software/edw. On a Windows system, this value would be specific as D:\software\edw. A trailing slash at the end of the directory specification is not required. passwords The next section of the login.sql files defines the passwords to all the ODS/EDW product owner and staging accounts. Specifying them here prevents the scripts from prompting you for them each time they need to connect or switch from one account to the other. It will be a security problem for you to put your regular passwords into the login.sql file. We recommend that you temporarily change all the account passwords for the duration of the install and set them back after the install is completed. default user tablespaces Step 5 This section of the login.sql file defines default DATA and TEMP tablespaces for baseline ODS/EDW product owner and staging schemas. Some other schemas such as the OWB repository users do not have tablespace definitions specified within the login.sql file because they are created in another step. Build EDW functional objects on the warehouse database This step installs the database objects necessary for EDW reporting and data extractions. The Administrative UI objects are also created during this step. 5.1. Enter this command to build the EDW functional objects: sqlplus /nolog @edw_install.sql 14 5.2. Review the edw_install.lst file. 5.3. If you would like to take advantage of expanded Advancement data coverage introduced with Banner EDW 8.2, run the following script from within the install directory. Banner Enterprise Data Warehouse 8.3 Installation Guide Install Banner Enterprise Data Warehouse April 2011 sqlplus /nolog @edw_install_apm.sql If you do not want to take advantage of expanded Advancement data coverage, move to the next step. Step 6 Import and Deploy OWB Mappings using OMB*Plus This step imports and deploys the OWB mappings used to populate the EDW with the data from the source system. This step will import each Product/ Project MDL file and validate and deploy each mapping. Troubleshooting .tcl script issues If you encounter errors while running the .tcl scripts, refer to the “OWB issues” section in the “Troubleshooting” chapter for information about possible resolutions for errors. 6.1. Position to correct directory before starting OMB*Plus. Unix OMB*Plus startup location: $ cd $OWB_HOME/owb/bin/unix $ ./OMBPlus.sh OMB*Plus: Release 10.2.0.4.36 Copyright (c) 2000, 2006, Oracle. All rights reserved. Windows OMB*Plus startup location: D:> cd $OWB_HOME/owb/bin/win32 D:> OMBPlus.bat OMB*Plus: Release 10.2.0.4.36 Copyright (c) 2000, 2006, Oracle. All rights reserved. Note You must use either forward slashes (/) or double slashes (\\) for directory changes in a Windows environment. The OMB*Plus interface does not recognize the traditional DOS backslash specification. 6.2. Run edw_install.tcl file in <EDW_STAGE_HOME>/owb/base directory. The repository creation process can now be started from within the OMB*Plus Environment. Unix and Windows OMB*Plus: 6.2.1. Enter the following command: OMB+> cd <EDW_STAGE_HOME>/owb/base OMB+> source edw_install.tcl April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Install Banner Enterprise Data Warehouse 15 6.2.2. Review all log files within the <EDW_STAGE_HOME>/owb/base/log directory. If you would like to deploy ETL mappings introduced with Banner EDW 8.2 that support Advancement functionality, perform the following steps: 6.3. Run the apm_install.tcl file in <EDW_STAGE_HOME>/owb/apm directory 6.3.1. Enter the following commands: OMB+> cd <EDW_STAGE_HOME>/owb/apm OMB+> source apm_install.tcl 6.3.2. Step 7 Review the apm log files within the <EDW_STAGE_HOME>/owb/apm/log directory. Verify the state of the Banner EDW Recompile any invalid objects as a result of the EDW install process. 7.1. Move to the <EDW_STAGE_HOME>/install directory cd <EDW_STAGE_HOME>/install 7.2. Run the gurutlrp.sql script located in the <EDW_STAGE_HOME>/install directory: sqlplus /nolog @gurutlrp.sql Troubleshooting gurutlrp script issues You should resolve any invalid objects prior to continuing with the Banner EDW installation process. Refer to the “gurutlrp.sql script” section in the “Troubleshooting” chapter for information about possible resolutions for some invalid objects. Step 8 8.1. Configure the Administrative User Interface Copy Required Files to Web Server There are a number of web content files referenced and used by the Administrative UI. These files are delivered in the web_files folder under the ods/ia_admin directory. All of these files need to be copied over to the directory specified as the document root for the DAD on the web server machine. 16 Banner Enterprise Data Warehouse 8.3 Installation Guide Install Banner Enterprise Data Warehouse April 2011 Folder Description Transfer Instructions iahelp IA Admin Help Files Copy the Help zip file in Binary Mode and unzip into the iahelp directory. 8.2. Configure and Run Metadata Publishing Process There are two EDW parameters which must be modified from within the Administrative UI. From the main menu of the Administrative UI, navigate to Options>Set up Parameters and click on the “Show all Internal Groups” drop down box on the left. Choose the METADATA Internal Code Group from the drop down and click on the Search button. The EDW PUBLISH_LOCATION parameter must be set to the publish location defined above. The EDW VIEW_URL parameter should be set to the web server location where you will transfer and store the metadata pages. This parameter value should be referenced as a directory alias. These two EDW parameter records should match the corresponding ODS parameter records. The metadata reports, which list the various data elements used in Banner EDW are available as static HTML pages within the administrative interface. These metadata reports must be 'published' from data stored and maintained in metadata tables under the IA_ADMIN schema. To update the Metadata reports for this release, run the Publishing process as you normally would (either from the Publish process submitted via the Admin UI, interactively through the Meta Data UI, or via the delivered command line script). April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Install Banner Enterprise Data Warehouse 17 18 Banner Enterprise Data Warehouse 8.3 Installation Guide Install Banner Enterprise Data Warehouse April 2011 Install Cognos Content This install requires you to be running a minimum IBM Cognos 8.4.1 Fix Pack 2. Banner EDW 8.3 is also supported on IBM Cognos 10. Step 1 Copy the Banner EDW 8.3 Deployment Archive 1.1. Unzip the edw80300i.zip file on the Cognos server. 1.2. Copy <EDW_STAGE_HOME>/cognos/edw/deploy/ enterprise_data_warehouse_80300.zip to COGNOS_HOME/deployment/ Step 2 Build the EDW Connector If the EDW connector already exists, proceed to Step 3, “Import ” 2.1. Open the Cognos Connection Web Page. 2.2. Click the Launch link in the upper right corner. 2.3. Select Cognos Administration. 2.4. Select the Configuration Tab at the top of the page. You should now be on the Configuration tab of the Data Source Connections page. 2.5. April 2011 Select the New Data Source icon in the upper right corner of the page. Banner Enterprise Data Warehouse 8.3 Installation Guide Install Cognos Content 19 2.6. Enter EDW in the Name field. 2.7. Click Next. The Specify the Connection-New Data Source Wizard page opens. 2.8. 20 Select Oracle from the Type pull-down list. Banner Enterprise Data Warehouse 8.3 Installation Guide Install Cognos Content April 2011 2.9. Click Next. The Data Connector Configuration page opens. Note The TNSNAMES.ORA file must include an entry of EDW for the Oracle client that Cognos uses. 2.10. Enter the following information into the Data Connector Configuration page. • Enter EDW in the SQL*Net connect string field. In the Signon area: • Check User ID • Check Password • Check Create a signon that the Everyone group can use. • Enter EDWMGR in the User ID field. • Enter a password in the Password field. • Enter the same password in the Confirm Password field. 2.11. Click Test the connection.... April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Install Cognos Content 21 2.12. Click Test. 2.13. Click Close when the test succeeds. 2.14. Click Close again to close the New Data Source wizard. 2.15. Click Finish. 2.16. Click OK to confirm that you are finished. After you complete the previous steps, you will see the newly created connector. 22 Banner Enterprise Data Warehouse 8.3 Installation Guide Install Cognos Content April 2011 Step 3 Import 3.1. Click Content Administration on the left panel of the Cognos Menu. 3.2. Click the New Import icon in the upper right area of the toolbar on the Content Administration Page. 3.3. Select the enterprise_data_warehouse_80300 file under Deployment archive Click Next. 3.4. Click Next again on the Specify a name and description page. Note The Name field should be populated with the name of the Banner EDW zip file enterprise_data_warehouse_80300.zip. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Install Cognos Content 23 24 3.5. Check all the boxes (packages, pages, and reports) to import all content. 3.6. Click Next. 3.7. Check Include data sources and connections. 3.8. Choose Keep existing entries under Conflict resolution. Banner Enterprise Data Warehouse 8.3 Installation Guide Install Cognos Content April 2011 3.9. Click Next. 3.10. Keep the default selections: • Select The owner from the source for the Set the owner to field. • Select New and existing entries for the Apply to field. 3.11. Click Next. 3.12. Click Next on the Review the summary Page. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Install Cognos Content 25 3.13. Click Finish. 3.14. Click Run. 3.15. Click OK to confirm that you want to run the file. 3.16. Click the Cognos Home icon on the right side of the Cognos toolbar. The newly installed Banner EDW 8.3 Cognos content will be available once the import process has completed. Step 4 4.1. Build and Configure Cubes Move to <EDW_STAGE_HOME>/cognos/edw/scripts/win cd <EDW_STAGE_HOME>/cognos/edw/scripts/win or cd <EDW_STAGE_HOME>/cognos/edw/scrips/unix Note chmod 770 * 4.2. Edit setUpCognosEnv to reflect the appropriate values for each parameter. These variables will determine paths for loading and publishing of the cube. Additionally, authentication credentials for building cubes can be defined here and automatically utilized in the cube build process rather than requiring modification of delivered cube models to include signons. Note When loading cubes in a Windows environment where authentication is required, update the buildCognosCube.bat file to make use of the cogtr command that utilizes the "-y1" option. Use of this option in a Windows environment that does not require authentication has been found to cause errors. 4.3. Save the changes. 4.4. Execute buildEDWCubes.bat This script will build all the cubes used by Banner EDW 8.3. For each cube the following will be found: • A 1KB file with the name of the cube • A 1KB .ver file with the cube name with a universal timestamp added to it 26 Banner Enterprise Data Warehouse 8.3 Installation Guide Install Cognos Content April 2011 • A folder with the cube name and timestamp (This folder will contain the fully built cube) Upon completion of the cube build, it will publish the cube package based on variables defined in step 4.2 and will update Cognos Connection to use the cube that has just been built. Schedule to run this script via Window’s Job Scheduler or UNIX’s cron. The run time should be after Banner EDW has completed its load/refresh. Note Given that deletion of previous cube loads is not automated, regular maintenance should be performed on the /edw/cubes directory to remove older versions of the loaded cubes. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Install Cognos Content 27 28 Banner Enterprise Data Warehouse 8.3 Installation Guide Install Cognos Content April 2011 Troubleshooting This section describes solutions to issues that may arise during the installation or upgrade of the Banner ODS. Use the information in this section as a troubleshooting reference while performing the Banner ODS installation or upgrade. Issue Category Issue “Administrative UI issues” “Page not enabled for current user role(s) because INSTALL user is missing” 31 “Checks and Balances” “Error Mapping is INVALID in the database” 33 “Staging” “Streams Configuration parameters” 33 “Set STREAMS_POOL_SIZE parameter” 33 “Restage an ODS stage table” 34 “ORA-01422: exact fetch returns more than requested number of rows” 36 “Error restaging tables; ORA-20000: Retrieving source database link terminated” 37 “ods_upgrade.sql” “Scripts not connecting correctly” 38 “[product]_etl_install.sql scripts” “ORA-04045: errors during recompilation/ revalidation” 39 “ORA-04063: package body "ODSSTG.MGKSTRM" has errors” 40 “ORA-20000: Adding a table rule terminated” 43 “ORA-20000: Exporting and importing LONG table data terminated” 45 “ORA-20000: Preparing to import terminated” 46 “ORA-20000: Retrieving source database link terminated” 47 “ORA-20000: Stopping the capture process terminated” 48 April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 29 Issue Category Issue “ORA-26723: user "ODSSTG" requires the role "DBA"” 48 “ORA-31685: Object type failed due to insufficient privileges” 49 “ORA-31693: Table data object failed to load/ unload” 50 “ORA-31693: Table data object failed to load/ unload” 51 “ORA-39014: One or more workers have prematurely exited” 53 “ORA-39083: Object type INDEX_STATISTICS failed” 54 “ORA-39125: Worker unexpected fatal error” 55 “Cannot stage table; no matching records in MGBSTRM” 55 “Installation stops responding” 56 “[product]_stage.sql” “ORA-20000: Preparing to import terminated” 57 “gurutlrp.sql script” “ORA-01031: insufficient privileges message Alumni/ODS views invalid” 58 “OWB* and WB_OLAP* invalid objects” 60 “UPD_80100* invalid objects” 61 “UPDATE_MBT* and DELETE_MBT* invalid objects” 61 “LOAD_MFT_TRANS_HISTORY* invalid objects” 62 “EDW_ADV_GIFT_EXTR invalid object” 62 “API2422 Connection details are not set for the metadata location” 63 “DELETE_MAT_PROSPECT_CONT_EXP package not found” 63 “OWB issues” 30 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 Issue Category Issue “Error importing SUPPORTEDLANGUAGE American English” 64 “ods_repos.tcl fails; ORA-00922: missing or invalid option” 65 “RTC-5161. Error when trying to deploy the 66 ODSMGR_LOCATION connector SOURCE_DB” “OMB06312: Cannot modify any properties of a registered location except the password” 67 Administrative UI issues This section explains issues you may encounter related to the Administrative UI and how to resolve them. Page not enabled for current user role(s) because INSTALL user is missing Related FAQ: 1-91Y2SB After installing or upgrading Banner ODS, you get following error when trying to log in to the Administrative UI as INSTALL user. This page is not enabled for current user role(s) bmenu.P_MainMnu Cause: There are many reasons why the page might not be enabled for the user. The issue in this case is because INSTALL user is missing on the ODS database. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 31 Solution: Create an INSTALL user if one does not exist. 1. Check whether the INSTALL user was created with MGBUSER_PIDM=1. 1.1. You can use the following commands to determine whether INSTALL user was created with MGBUSER_PIDM=1. SELECT MGBUSER_PIDM, MGBUSER_ID FROM MGBUSER; MGBUSER_PIDM MGBUSER_I ------------ --------1 INSTALL 1.2. Because the WTAILOR.TWGRROLE table has roles set up for TWGRROLE_PIDM=1, check the following: SELECT TWGRROLE_PIDM, TWGRROLE_ROLE FROM WTAILOR.TWGRROLE WHERE TWGRROLE_PIDM=1 TWGRROLE_PIDM TWGRROLE_ROLE ------------- -----------------------------1 IAMETADATA 1 IAOPTIONS 1 IASECURITY 1 IASTAGING 1 WTAILORADMIN 2. If INSTALL user was not created with MGBUSER_PIDM=1, then perform the following commands: SQLPLUS IA_ADMIN/<PW> DELETE FROM MGBUSER WHERE MGBUSER_ID = 'INSTALL'; COMMIT; EXEC MGKUSER.P_InsertUser(1, 'INSTALL', 'Install', 'User', '', '111111'); COMMIT; 32 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 Checks and Balances This section explains issues you may encounter when running the ODS Health Check and how to resolve them. Error Mapping is INVALID in the database Related FAQ: 1-CD78E2 When executing the ODS Health_Check Mapping Banner ODS upgrade, you receive the following error: Error: DELETE_MAT_ADVANCEMENT_RATING is INVALID in the database Cause: The mapping name, DELETE_MAT_ADVANCEMENT_RATING, may vary. Solution: Verify the package is valid in the database by executing the following command in the ODS database: sqlplus /nolog @gurutlrp The gurutlrp.sql script compiles invalid packages and objects in the database. Staging This section explains issues you may encounter when staging tables in the ODS database. Streams Configuration parameters Related FAQ: 1-I4UP5C Refer to FAQ 1-I4UP5C - Is my Oracle environment ready for ODS 8.2 and Oracle Streams? This FAQ includes information about configuring Streams parameters. Set STREAMS_POOL_SIZE parameter Related FAQ: 1-EN5VG9 The STREAMS_POOL_SIZE parameter specifies the memory limit or initial amount for the Streams pool to store buffered queue messages in memory. It also provides memory for April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 33 capture processes and apply processes. The Streams pool stores LCRs captured by a capture process. It also stores LCRs and messages that are entered into a buffered queue by applications or users. You have the option of setting the STREAMS_POOL_SIZE parameter using Automatic Shared Memory Management (ASMM) or not. Option 1 - Set STREAMS_POOL_SIZE using ASMM If the settings SGA_TARGET/SGA_MAX_SIZE (in 10g), or MEMORY_TARGET (in 11g) are set using ASMM, the STREAMS_POOL_SIZE parameter value is used as an initial amount of memory allocated to the Streams pool. When the STREAMS_POOL_SIZE is not big enough, it will expand using memory from the SGA parameters. The SGA parameters need to be set to handle other buffers memory and the growth of the streams pool. Oracle recommendation Oracle recommends that the STREAMS_POOL_SIZE be set even if ASMM is used. Oracle recommends the following minimum setting to ensure that there is enough memory to accommodate the Oracle Streams components. • 15 MB for each capture process parallelism • 250 MB or more for each buffered queue • 1 MB for each apply process parallelism SunGard Higher Education recommendation SunGard HE recommends that you set the STREAMS_POOL_SIZE to at least 256MB on both Banner and BPRA environments. Option 2 - Set STREAMS_POOL_SIZE NOT using ASMM If the settings SGA_TARGET/SGA_MAX_SIZE (in 10g), or MEMORY_TARGET (in 11g) are NOT set using ASMM (they are set to 0), then you need to set the STREAMS_POOL_SIZE needs large enough to handle all the stream pool memory demands. Restage an ODS stage table Related FAQ: 1-C8Y1U1, 1-JF68GU Cause: You may need to restage tables if there are errors during the initial import of data during the install or upgrade process or if data becomes out-of-synchronization between the source and warehouse tables. 34 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 Solution: Perform the following steps to restage an ODS stage table. 1. Connect as ODSSTG on the ODS database and run the command sql> EXEC mgkstrm.p_add_to_local_env('BPRA_BANNER', '&OWNER', '&TABLE_NAME','Y'); where &OWNER is the table owner and &TABLE_NAME is the table name to be streamed. 2. Recreate the triggers that were dropped from the previous section. 2.1. Open the /ods80200u/ods/install directory and find the SQL script of type [product]_etl_install.sql related to the OWNER of the table. For example, a table owned by SATURN would use the student_etl_install.sql script. 2.2. Open the [product]_etl_install.sql file and find the trigger declaration (sql script) for the trigger for the table that was re-streamed. 2.3. Execute that SQL script. For example in the student_etl_install.sql you will find the following: PROMPT ******************** PROMPT * Student Triggers * PROMPT ******************** CONNECT SATURN/&&SATURN_PASSWORD @&home_dir/staging/banner/student/triggers/sataatt0.sql -> trigger for SARAATT @&home_dir/staging/banner/student/triggers/satadap0.sql -> trigger for SARADAP @&home_dir/staging/banner/student/triggers/satappd0.sql -> trigger for SARAPPD 3. Delete the errors in the DBA_APPLY_ERROR data dictionary view 3.1. Connect as sys or other user that can execute sys packages and run one of the following commands: exec dbms_apply_adm.delete_all_errors('BPRA_BANNER$APP'); Or you can delete one error at a time by using: exec dbms_apply_adm.delete_error(local_transaction_id IN VARCHAR2); April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 35 ORA-01422: exact fetch returns more than requested number of rows Related FAQ: 1-CB56RZ When executing the STAGE_AREA_STATUS mapping, you receive the following error: P_PROCESS_STATUS Error: ORA-01422: exact fetch returns more than requested number of rows Cause: You may have more than one propagation configured. Solution: Perform the following steps to address this issue. 1. To check the number of propagations, execute the following commands: SQL> conn odsstg/passwd SQL> select db_link from user_db_links; DB_LINK ---------------------BANTEST.WORLD SQL> select propagation_name from dba_propagation@yourDB_LINK_from_select_above PROPAGATION_NAME -----------------------------BANPPRD$PROP BANTEST$PROP 2. If the multiple propagations are intentional, you can change this section of code to select only the desired Propagation (for example, BANTEST) name. 36 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 2.1. Open the mgkstgu.sql script located in the ODS Home/ods/ia_admin/ dbprocs/odsstg directory. 'SELECT propagation_name, '|| 'status, '|| 'error_message, '|| 'destination_queue_owner, '|| 'destination_queue_name '|| 'FROM dba_propagation@'||link_in||' '|| 'WHERE source_queue_owner = :var1 '|| 'AND source_queue_name = :var2 ' || 'AND propagation_name like ''%BANTEST%'' '; Note The quotes around BANTEST are not double quotes but actually two single quotes. The ODSSTG user owns the MGKSTGU. The modified package can be created in sqlplus as ODSSTG. Error restaging tables; ORA-20000: Retrieving source database link terminated Related FAQ: 1-CG4S7J Related error: ORA-20000, ORA-20001 When restaging tables in the ODS, you may get the following errors: ERROR: ORA-20000: Retrieving source database link terminated with the following error: ORA-20001: ERROR IN MGKTLIB.F_GET_MTVPARM_EXTERNAL_CODE: EXTERNAL_CODE not found for GROUP: STAGE CONFIGURATION, CODE: SOURCE ALIAS Cause: A parameter record is missing from the MTVPARM table. Solution: 1. Replace the first parameter BPRA_BANNER of the procedure call mgkstrm.p_add_to_local_env with the value from this statement: select DB_LINK from dba_db_links where OWNER='ODSSTG' — Or — April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 37 2. Validate that both of the following queries generate the same output. SELECT MTVPARM_EXTERNAL_CODE FROM MTVPARM WHERE MTVPARM_INTERNAL_CODE_GROUP = 'STAGE CONFIGURATION' AND MTVPARM_INTERNAL_CODE = 'SOURCE ALIAS'AND NVL(MTVPARM_INTERNAL_CODE_2, ' ') = NVL('BPRA_BANNER', ' '); select DB_LINK from dba_db_links where OWNER='ODSSTG' If the two queries do not generate the same output, then log on to the Administrative UI and update the parameter with an Internal Group of 'STAGE CONFIGURATION' and Internal Code 1 of 'SOURCE ALIAS'. The External Code of this parameter should match the output from the second query above. ods_upgrade.sql Scripts not connecting correctly Related FAQ: 1-92JBVE Some scripts don’t connect correctly. Cause: Scripts that connect as SYS user don’t include the “as sysdba”. Solution: Include the “as sysdba” when entering the password for SYS user. [product]_etl_install.sql scripts During the installation or upgrade process you will run the ETL install scripts that use the naming convention [product]_etl_install.sql to stage and install the ETL components of the ODS database. This section explains issues and Oracle errors you may encounter and how to resolve them. 38 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 ORA-04045: errors during recompilation/revalidation Related error: ORA-00980 Related FAQ: 1-BPQY5E When running the [product]_etl_install.sql scripts, you may encounter an error when creating a view. For example, when running the student_etl_install.sql script, the resulting student_etl_install.lst file includes the following error message: CREATING VIEW: AS_COURSE_OFFERING_FEES FILE: ssvfee0.sql.sql FROM TBBDETC * ERROR at line 9: ORA-04045: errors during recompilation/revalidation of PUBLIC.TBBDETC ORA-00980: synonym translation is no longer valid Solution: Perform the following steps to fix this problem. 1. Log into the ODS database as ODSSRC and drop the AS_COURSE_OFFERING_FEES view. 2. Run the ssvfee0.sql script located in the staging/banner/student/views directory. 3. If an error occurs, type the following: SQL> show errors Note If no errors are displayed or the error information doesn’t point to the problem object, use the script provided in FAQ CMS-12329 “Oracle Metalink Note 1050801.6 Listing PL/SQL Errors and Line Numbers” to identify the problem. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 39 ORA-04063: package body "ODSSTG.MGKSTRM" has errors Related errors: ORA-06508, ORA-06512 Related FAQ: 1-BPQY5C When running the [product]_etl_install.sql scripts, you may encounter an error trying to find part of a package. For example, when running the general_etl_install.sql script, the following error message displays: ERROR at line 1: ORA-04063: package body "ODSSTG.MGKSTRM" has errors ORA-06508: PL/SQL: could not find program unit being called: "ODSSTG.MGKSTRM" ORA-06512: at line 1 Solution: Note The following queues and processes are referenced in this step. Located in Banner database instance: Located in ODS database instance: Capture queue BRAP_BANNER$CAPQ Apply queue BRAP_BANNER$APPQ Capture process BRAP_BANNER$CAP Apply process BRAP_BANNER$APP Propagation process BRAP_BANNER$PROP Re-stage the ODS tables. 1. Drop all the streams objects. 1.1. Login as ODSSTG on the ODS database instance. 1.2. Launch the following command: exec mgkstrc.p_drop_local_env('BPRA_BANNER'); 40 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 2. Create all the streams objects (except for the capture process). 2.1. Launch the following command: exec mgkstrc.p_create_local_env('BAN8.SCT.COM','BPRA_BANNER'); 2.2. BAN8.SCT.COM is the database link name found when running the following command: ODS database> select db_link from dba_db_links where owner='ODSSTG'; 3. Drop all the banner schemas already staged into the ODS database. 3.1. Login to the ODS database as system (verify that your ORACLE_SID is set correctly). 3.2. Run the following drop commands: SQL> drop user general cascade; SQL> drop user taismgr cascade; SQL> drop user saturn cascade; SQL> drop user fimsmgr cascade; SQL> drop user posnctl cascade; SQL> drop user payroll cascade; SQL> drop user faismgr cascade; SQL> drop user alumni cascade; SQL> drop user ftaemgr cascade; 4. Login to the ODS staging area ($ODS_HOME/ods/install) and run the following ETL scripts. This will automatically create the capture process and re-stage the Banner tables. sqlplus /nolog @general_etl_install.sql sqlplus /nolog @arsys_etl_install.sql sqlplus /nolog @student_etl_install.sql sqlplus /nolog @finance_etl_install.sql sqlplus /nolog @posnctl_etl_install.sql sqlplus /nolog @payroll_etl_install.sql sqlplus /nolog @finaid_etl_install.sql sqlplus /nolog @alumni_etl_install.sql sqlplus /nolog @travel_etl_install.sql April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 41 ORA-12545: Connect failed because target host or object does not exist Related FAQ: 1-C76P41 When running the required_tablespaces.sql script, you may encounter the following error: Error running procedure in script required_tablespaces.sql: ORA-12545: Connect failed because target host or object does not exist Cause: The ODS database link is invalid (not pointing to the right service/host/port) or doesn’t exist. Solution: Perform the following steps to address this issue. 1. Modify the login.sql scripts in both of these directories: $ODS_STAGE/ods/ install and $ODS_STAGE/ods/upgrade. 1.1. Verify that the following variables are defined correctly: • &source_host • &source_port • &source_global_name 2. Drop all the old database links (any database link with the name *@SOURCE_DB). 3. Update the mtvparm external_code value with the new source alias name. sql> update mtvparm set MTVPARM_EXTERNAL_CODE = '&source_global_name' where MTVPARM_INTERNAL_CODE_GROUP = 'STAGE CONFIGURATION' and MTVPARM_INTERNAL_CODE = 'SOURCE ALIAS'; sql> commit; 4. Execute the following script: sqlplus /nolog $ODS_STAGE/ods/install/odsstg_install.sql 5. Re-execute the required_tablespaces.sql script from the $ODS_STAGE/ods/ upgrade 42 directory. Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 ORA-20000: Adding a table rule terminated Related errors: ORA-00258, ORA-06512 Related FAQ: 1-BGFQQ5 When running the [product]_etl_install.sql scripts, you may encounter this error when trying to add a table. STAGING GENERAL TABLES... ERROR: ORA-20000: Adding a table rule terminated with the following error: ORA-00258: manual archiving in NOARCHIVELOG mode must identify log ORA-06512: at "SYS.DBMS_STREAMS_ADM", line 372 ORA-06512: at "SYS.DBMS_STREAMS_ADM", line 312 Cause: The Banner database is running in NOARCHIVELOG mode. Solution: The Banner database should be running in ARCHIVELOG mode. Perform the following steps to verify whether the database is in ARCHIVELOG mode and change it if it is not. 1. Login to the Banner database. 2. Verify whether the database is running in ARCHIVELOG mode using one of the following commands: SQL> select name,log_mode from v$database; — Or — SQL> archive log list; 3. If the database is not running in ARCHIVELOG mode, set it to ARCHIVELOG mode using the following command: ALTER DATABASE ARCHIVELOG; 4. Recheck whether the database is in ARCHIVELOG mode using the following command: SQL> archive log list; The database should be running in Archivelog. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 43 After confirming that the Banner database is running in ARCHIVELOG mode, you can restage the Banner schemas into the ODS database. Related FAQ: 1-C73SFY Related errors: ORA-03113 When running the [product]_etl_install.sql scripts, you may encounter this error when trying to add a table. ERROR: ORA-20000: Adding a table rule terminated with the following error: ORA-03113: end-of-file on communication channel Cause: The ORA-03113 error is typically caused by internal RDBMS issues. You may find more details on the error defined in the Banner or ODS database alert.log depending when the error happened. Look for the latest ORA-600 or ORA-07445 message. For example, a sample alert.log included the following error: ORA-07445: exception encountered: core dump [kqlvld()+3756] [SIGSEGV] [Address not mapped to object] [0x000000038] [] [] Solution: If you have access to the Oracle Metalink site, you can troubleshoot the error using the Error Lookup Tool available on the site and the following process. Note If you don't have access to the Oracle Metalink site, log a Service Request about the issue with the alert.log ORA error. 1. Access the Oracle Metalink site. 2. Open the Oracle Metalink note Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool [ID 153788.1]. 3. Choose the Error Code you encountered. For the previous example, this was error code “ORA-07445”. 4. Enter the coredump first argument in the ORA-600 First Argument field. For the example this was, kqlvld()+3756. 44 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 5. Select the Oracle release. (Optional) 6. Click Lookup Error. A list of bugs displays, which should include the RDBMS release in which the bug was fixed. 7. You can either upgrade to the designated RDBMS release with a patch set or apply the patch/workaround for the bug. For example, if the bug number was “6824129”, you can download and install the patch p6824129_10204_Solaris-64.zip to fix the issue. ORA-20000: Exporting and importing LONG table data terminated Related errors: ORA-39001, ORA-06512 Related FAQ: 1-8PX18D When running the [product]_etl_install.sql scripts, there is an error due to an invalid argument. For example, when running the general_etl_install.sql script the following error message displays: ORA-20000: Exporting and importing LONG table data terminated with the following error: ORA-20000: Exporting tables terminated at step DBMS_DATAPUMP.ADD_FILE(FILENAME=>GENERAL002.DMP) with the following error: ORA-39001: invalid argument value ORA-06512: at "ODSSTG.MGKSTRS", line 93 Cause: The path to the directory DATA_PUMP_DIR is either nonexistent or the Oracle user doesn't have the necessary privilege to write in to it. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 45 Solution: 1. Check what the path is for the DATA_PUMP_DIR directory using the following command: SQL> select DIRECTORY_PATH from dba_directories where DIRECTORY_NAME = 'DATA_PUMP_DIR'; 2. Validate that the expdp is working with the ODSSTG user and the DATA_PUMP_DIR directory on both the Banner and ODS environment. The following command is an example you can use to verify that the expdp is working as it should. expdp odsstg/u_pick_it directory=DATA_PUMP_DIR DUMPFILE=general.dmp logfile=general.log schemas=general 3. Drop the payroll/saturn/general user from the ODS database that was previously created by the general_etl_install.sql script. 4. Rerun the general_etl_install.sql script. Note In RAC environments, this error can also occur if the data pump directory is not NFS share or ASM. ORA-20000: Preparing to import terminated Related errors: ORA-02068, ORA-03135, ORA-06512 Related FAQ: 1-9ZIRG5 When running the [product]_etl_install.sql scripts, you may encounter an error during the FTP process when there is a bad file on the target database. For example, the following error messages may display: ORA-20000: Preparing to import terminated with the following error: ORA-02068: following severe error from WIPE.ODSEDW.EDU ORA-03135: connection lost contact ORA-06512: at "SYS.DBMS_FILE_TRANSFER", line 60 ORA-06512: at "SYS.DBMS_FILE_TRANSFER", line 168 ORA-06512: at "ODSSTG.MGKSTRS", line 89 Cause: The error occurs when the FTP process results in a bad file on the target database. 46 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 Solution: Restart the ETL script or manually FTP the *.dmp file and restart the ETL script. Before implementing this solution, you need to modify the *_stage.sql script to recreate the streams table. 1. Open the file “ods80200(i or u)\ods\install\*_stage.sql” (where * is the module name) 2. Modify the lines EXEC mgkstrm.p_add_to_local_env adding a fourth parameter of 'Y’. For example: EXEC mgkstrm.p_add_to_local_env('&&SOURCE_ALIAS', 'ALUMNI', '%','Y'); 3. Create the trigger on the ODS stage table. Execute the following script: ods80200i\staging\banner\<product shema>\triggers\<table name>9.sql where <table name> is replaced with the three letters of the module. For example, the RORSTAT script would be: ods80200i\staging\banner\finaid\triggers\rotstat2.sql ORA-20000: Retrieving source database link terminated Related error: ORA-01422 Related FAQ: 1-B2LWFM When running the [product]_etl_install.sql scripts, you may encounter an error while staging tables in the ODS. For example, when running the general_etl_install.sql script, which calls general_stage.sql, the following error messages display: CREATING TABLE: GTVVPDI FILE: gtvvpdi.sql STAGING GENERAL TABLES... ERROR: ORA-20000: Retrieving source database link terminated with the following error: ORA-01422: exact fetch returns more than requested number of rows Cause: This issue is caused by having multiple entries of the BPRA_BANNER record in the MTVPARM table. One possible reason that you might have multiple BPRA_BANNER records is if you ran the stage_process_install.sql script multiple times. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 47 Solution: Delete all but one of the BPRA_BANNER entries from the MTVPARM table. You can do this from within the Administrative User Interface using the Options>Set Up Parameters option to delete the extra BPRA_BANNER parameter entries. ORA-20000: Stopping the capture process terminated Related errors: ORA-26672, ORA-06512 Related FAQ: 1-8X0BJC When running the [product]_etl_install.sql scripts, there is an error while stopping the Stream process. For example, the following error messages display: ERROR: ORA-20000: Stopping the capture process terminated with the following error: ORA-26672: timeout occurred while stopping STREAMS process BPRA_BANNER$CAP ORA-06512: at "SYS.DBMS_LOGREP_UTIL", line 626 ORA-06512: at "SYS.DBMS_CAPTURE_ADM", line 59 Cause: The operating system has insufficient memory. Solution: Increase the memory allocation to the operating system. One way to do this is to shut down unused databases if more than one database exists on the server. Typically 2050% of the physical memory should be allocated to the operating system to prevent an effect known as “thrashing” where the CPU spends a large amount of time paging and swapping. You can use the following operating system commands to monitor memory: • Red Hat Linux - free • Solaris - sysstat ORA-26723: user "ODSSTG" requires the role "DBA" Related error: ORA-06512 Related FAQ: 1-AZEAYH When running the [product]_etl_install.sql scripts, there is an error while staging tables in the ODS. For example, when running the general_etl_install.sql script the following errors display: 48 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 ORA-26723: user "ODSSTG" requires the role "DBA" ORA-06512: at "SYS.DBMS_STREAMS_ADM", line 372 ORA-06512: at "SYS.DBMS_STREAMS_ADM", line 312 ORA-06512: at line 2 ODSSTG has the DBA role in both Banner and ODS databases. Cause: Database Vault revokes the BECOME USER system privilege, which causes Datapump and Streams to fail. Solution: Perform the following steps: 1. Grant BECOME USER to the ODSSTG schema. 2. Drop general, saturn, and payroll schemas on the ODS database. 3. Rerun the general_etl_install.sql script. ORA-31685: Object type failed due to insufficient privileges Related FAQ: 1-BR3QX3 When running the [product]_etl_install.sql scripts, you may encounter an error creating a foreign key constraint. For example, when running the arsys_etl_install.sql script the following error message displays: STAGING ACCOUNTS RECEIVABLE TABLES... ERROR: ORA-31685: Object type REF_CONSTRAINT:"TAISMGR"."FK1_TBBCONT_INV_STVTERM_CODE" failed due to insufficient privileges. Failing sql is: ALTER TABLE "TAISMGR"."TBBCONT" ADD CONSTRAINT "FK1_TBBCONT_INV_STVTERM_CODE" FOREIGN KEY ("TBBCONT_TERM_CODE") REFERENCES "SATURN"."STVTERM" ("STVTERM_CODE") ENABLE Cause: The object didn’t have proper grant privileges. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 49 Solution: Perform the following steps to grant proper privileges to the object. 1. Grant references to the object: sqlplus /nolog connect odsstg/<odsstg_pwd> GRANT REFERENCES on STVTERM to TAISMGR; 2. Create the constraint: ALTER TABLE "TAISMGR"."TBBCONT" ADD CONSTRAINT "FK1_TBBCONT_INV_STVTERM_CODE" FOREIGN KEY ("TBBCONT_TERM_CODE") REFERENCES "SATURN"."STVTERM" ("STVTERM_CODE") ENABLE ORA-31693: Table data object failed to load/unload Related error: ORA-12899 Related FAQ: 1-9NJNXU When running the [product]_etl_install.sql scripts, you may encounter an error loading objects that are too large. For example, when running the general_etl_install.sql script the following error message displays: ORA-31693: Table data object "SATURN"."SPRADDR" failed to load/unload and is being skipped due to error: ORA-12899: value too large for column "SATURN"."SPRADDR"."SPRADDR_CITY" (actual: 21, maximum: 20) Source object: SATURN.SPRADDR successfully set for staging. Source object: SATURN.SPRHOLD successfully set for staging. Cause: When staging tables into the ODS the nls_length_semantics parameter is set incorrectly. You're trying to stage ODS tables with the nls_length_semantics=CHAR on an ODS database instance where the nls_length_semantics=BYTE. Solution: Change the nls_length_semantics parameter as follows: 50 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 1. Open the init.ora or spfile file. 2. Change the value of the nls_length_semantics parameter to the following: nls_length_semantics=CHAR 3. Shut down the database instance and restarted it for the new parameter setting to be recognized. 4. Re-execute the necessary [product]_etl_install.sql script. ORA-31693: Table data object failed to load/unload Related error: ORA-06502 Related FAQ: 1-8Y76J8 When running the [product]_etl_install.sql scripts, there is an error during datapump net import. For example, when running the finaid_etl_install.sql script the following error message displays: ERROR: ORA-31693: Table data object "FAISMGR"."RCRESAR" failed to load/unload and is being skipped due to error: ORA-06502: PL/SQL: numeric or value error Cause: This error can occur on Oracle database instance 10.2.0.2 or 10.2.0.3. It is associated with Oracle Bug 5718757 - ORA-31693 / ORA-6502 during datapump net import. Solution: This problem (Oracle bug 5718757) is resolved in Oracle 10.2.0.3 Patch 2 (Windows), Oracle 10.2.0.4, or a patch is available from Oracle. You can upgrade to Oracle 10.2.0.4 or apply the patch to fix the bug in Oracle 10.2.0.2. or 10.2.0.3 as follows: April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 51 1. Install Oracle patch 5718757 on your RDBMS home directory. Perform the following steps for pre-configuration. 1.1. Shutdown all the instances that are using the $ORACLE_HOME. 1.2. Extra steps for RAC environment (SSH security between nodes.) $ exec /usr/bin/ssh-agent $SHELL $ /usr/bin/ssh-add 1.2.1. Enter passphrase for /u01/app/oracle/.ssh/id_rsa: xxxxx Identity added: /u01/app/oracle/.ssh/id_rsa (/u01/app/oracle/.ssh/ id_rsa) Identity added: /u01/app/oracle/.ssh/id_dsa (/u01/app/oracle/.ssh/ id_dsa) 2. Login to the ODS database and drop the user FAISMGR with the cascade option. 3. Re-execute the following process: sqlplus /nolog @finaid_etl_install.sql If the problem persists after applying Oracle patch 5718757, you'll need to export and import a number of Financial Aid tables using a .dmp file as follows: 1. In the MGKSTRM package, modify the value for LV_STMT in the P_LOAD_MGBSTRM_TAB procedure. Change from: 'WHERE C.OWNER = MGBSTRM_OWNER '|| 'AND C.TABLE_NAME = MGBSTRM_TABLE_NAME '|| 'AND C.DATA_TYPE IN (''LONG'',''LONG RAW'',''XMLTYPE'')), ''N''), '|| Change to: 'WHERE C.OWNER = MGBSTRM_OWNER '|| 'AND C.TABLE_NAME = MGBSTRM_TABLE_NAME '|| 'AND (C.DATA_TYPE IN (''LONG'',''LONG RAW'',''XMLTYPE'') '|| 'OR C.TABLE_NAME IN (''RCRESAR'',''RCRAPP1'',''RCRAPP2'',''RCRAPP4'', '|| '''RCRAPP3'',''RPRLAPP'',''RCRIMP1'',''ROBUSDF'', '|| 52 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 '''RNROVRD'',''RTVUSER''))), ''N''), '|| Note Your script may not have XMLTYPE if you have not yet applied the posting for RPE 1-ACZKNV. 2. Login to the ODS database as ODSSTG and compile the modified MGKSTRM package. 3. In the ODS database, drop the user FAISMGR with the cascade option. 4. Re-execute the following process: sqlplus /nolog @finaid_etl_install.sql ORA-39014: One or more workers have prematurely exited Related errors: ORA-39029, ORA-31671, ORA-02067, ORA-06512, ORA39125, ORA-02055, ORA-02068, ORA-03113 Related FAQ: 1-8QU7UT When running the [product]_etl_install.sql scripts, there is an error when a worker exits prematurely. For example, when running the student_etl_install.sql script the following error messages display: ERROR: ORA-39014: One or more workers have prematurely exited. ERROR: ORA-39029: worker 1 with process name "DW01" prematurely terminated ERROR: ORA-31671: Worker process DW01 had an unhandled exception. ORA-02067: transaction or savepoint rollback required ORA-06512: at "SYS.KUPW$WORKER", line 13249 ORA-06512: at "SYS.KUPW$WORKER", line 14923 ORA-06512: at "SYS.KUPW$WORKER", line 6293 ORA-39125: Worker unexpected fatal error in KUPW$WORKER.ESTIMATE while calling DBMS_METADATA.FETCH_XML_CLOB [] ORA-06512: at "SYS.KUPW$WORKER", line 3879 ORA-02067: transaction or savepoint rollback required ORA-06512: at "SYS.DBMS_METADATA", line 778 ORA-06512: at "SYS.DBMS_METADATA", line 4280 ORA-06512: at "SYS.KUPW$WORKER", line 9101 ORA-02055: distributed update operation failed; rollback required ORA-02068: following severe error from BAN8 ORA-03113: end-of-file on communication channel ORA-06512: at "SYS.KUPW$WORKER", line 1342 April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 53 ORA-06512: at line 2 Solution: If you are using Automatic Shared Memory Management (ASMM), increase the SGA_TARGET on the ODS database instance. If you are not using ASSM, set the STREAMS_POOL_SIZE to a greater value. ORA-39083: Object type INDEX_STATISTICS failed Related errors: ORA-20000 Related FAQ: 1-91R0CG When running the [product]_etl_install.sql scripts, there is an error related to the index on the object. For example, when running the alumni_etl_install.sql script the following error messages display: ERROR: ORA-39083: Object type INDEX_STATISTICS failed to create with Error: ORA-20000: INDEX "BANINST1"."AGRGDES_KEY_INDEX5" does not exist or insufficient privileges Cause: An object owned by one user has an index that is owned by another user. For example, in the previous error message the AGRGDES table, which is owned by the ALUMNI user, has an AGRGDES_KEY_INDEX5 index that is owned by the BANINST1 user. The table and index should have the same owner. Solution: Recreate the index with the right owner. The following script is a sample you can use to recreate the AGRGDES_KEY_INDEX5 index with the right owner. You could modify this script for your needs depending on the owner mismatch you encounter. DROP INDEX BANINST1.AGRGDES_KEY_INDEX5; CREATE INDEX ALUMNI.AGRGDES_KEY_INDEX5 ON ALUMNI.AGRGDES (AGRGDES_PIDM, AGRGDES_PLEDGE_NO, AGRGDES_CAMPAIGN, AGRGDES_DESG) LOGGING TABLESPACE DEVELOPMENT PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 54 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 128K April 2011 MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE 0 BUFFER_POOL DEFAULT ) NOPARALLEL; ORA-39125: Worker unexpected fatal error Related errors: ORA-06502, ORA-06512 Related FAQ: 1-8QU7UT, 1-C7P0UL When running the [product]_etl_install.sql scripts, this error can occur when staging tables. For example, when running the general_etl_install.sql script the following error messages display: STAGING GENERAL TABLES... ERROR: ORA-39125: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS while calling DBMS_METADATA.FETCH_XML_CLOB [] ORA-06502: PL/SQL: numeric or value error: character string buffer too small ERROR: ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95 ORA-06512: at "SYS.KUPW$WORKER", line 6228 Cause: This issue is due to Oracle Bug 5875568 - IMPDP can error on create table in multibyte with ORA-39125/ORA-6502. Solution: Apply Oracle patch 5875568 to fix the problem. Cannot stage table; no matching records in MGBSTRM Related FAQ: 1-BPQY5A When running the [product]_etl_install.sql scripts, you may encounter an error when staging tables. Cause: A table cannot be staged because there are no matching records in MGBSTRM. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 55 Solution: Perform the following steps to fix this issue. 1. Log into the ODS database as ia_admin. 2. In sqlplus, run the mgbstrm_data_ods.sql script located in the ods/ ia_admin/dbscripts/odsstg directory. 3. Drop the payroll, saturn, and general users in the ODS database. These users were previously created by the general_etl_install.sql script. SQL> drop user general cascade; SQL> drop user saturn cascade; SQL> drop user payroll cascade; 4. Run the general_etl_install.sql script. Installation stops responding Related FAQ: 1-BFL58F When running the [product]_etl_install.sql scripts, the installation process stops responding. Cause: If a new table is being added to the ODS because a new table was added to the source Banner database, this can sometimes cause a [product]_etl_install.sql script to stop. This can happen because the script is waiting for no activity on the new table in the source database. Solution: Run the [product]_etl_install.sql scripts on the ODS database at time when the Banner database environment has little or no activity, for example, during the night. 56 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 [product]_stage.sql ORA-20000: Preparing to import terminated Related errors: ORA-19504, ORA-27038, ORA-02063, ORA-06512 Related FAQ: 1-9EA0I7 When running the [product]_stage.sql scripts this error may occur at the at DBMS_FILE_TRANSFER.PUT_FILE step. Some of the ODS objects are invalid due to tables not being imported from Banner. For example, the following errors may display: ORA-20000: Preparing to import terminated with the following error: ORA-20000: Exporting and importing LONG table data terminated with the following error: ORA-20000: Exporting tables terminated at step DBMS_FILE_TRANSFER.PUT_FILE with the following error: ORA-19504: failed to create file "<Data Pump Directory path>/ <filename>.DMP" ORA-27038: created file already exists Additional information: 1 ORA-02063: preceding 3 lines from TODS ORA-06512: at "ODSSTG.MGKSTRS", line 93 Cause: The issue occurs when DATA_PUMP_DIR directory value is set as same shared NFS storage location on both the source and target database. Solution: Perform the following steps to fix this issue. 1. Check the DATA_PUMP_DIR directory value for both the Banner and ODS databases. 2. If both databases share the same NFS storage location, change one of the values to create distinct DATA_PUMP_DIR directory locations for Banner and the ODS. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 57 gurutlrp.sql script During the installation or upgrade process you will run the gurutlrp.sql script to recompile invalid objects. This section explains issues you may encounter with invalid objects and how to resolve them. ORA-01031: insufficient privileges message Alumni/ODS views invalid Related FAQ: 1-BXWKPD When running the gurultrp.sql script views may be returned as invalid in the Banner database. For example, some Alumni/ODS views were invalid with the following error: 0/0 ORA-01031: insufficient privileges message Cause: Beginning with Banner 7, the Alumni system removed the ODS views from the aluviews.sql script because ownership of these views was passed to ODS. Beginning with Banner ODS 8.2, those composite ODS views were no longer needed in the Banner database as they were moved to the ODS database. Solution: You can safely remove invalid views, in this case the Alumni/ODS views, from the Banner database after verifying that the views are no longer used in the Banner database. Note The following steps use AA_PLEDGE as the view with the error message. You can use these steps for any ODS view that was removed from Banner and moved to the ODS database. 58 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 Verify a view is no longer in Banner database and is in ODS database 1. Login to sqlplus as baninst1. 1.1. Perform a desc AA_PLEDGE to verify the view is invalid: SQL> DESC AA_PLEDGE ERROR: ORA-24372: invalid object for describe SQL> 2. Verify that this view is not being compiled in the aluview.sql script. 2.1. Open the aluview.sql script. 2.2. Search to see if the agvplg0.sql file is being executed. The AA_PLEDGE view is found in the agvplg0.sql file. 2.3. If agvplg0.sql is not being executed then it is most likely now in the ODS database. 3. Verify that you can no longer find the view files in the banner code tree $BANNER_HOME/alumni/views. cd to $BANNER_HOME/alumni/views ls -l agvplg0.sql Note The view file may still exist from an installation previous to Banner 7.0, If the file still exists but all other steps validate, the view is no longer needed and you can remove these files from you banner code tree. 4. Verify that this view is now in the ODS database. 4.1. Login to sqlplus as odsmgr. 4.2. desc AA_PLEDGE. You should see a describe of the view. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 59 Remove ETL views from Banner database To remove all ETL views from the Banner database, perform step 1. To drop a single view, perform step 2. 1. Follow this step to remove all ETL views from the Banner database. 1.1. Run the supplied ETL Uninstall script located in the HOME/banner/ install directory after properly conditioning your Banner database. sqlplus /nolog @banner_etl_uninstall81.sql Review the banner_etl_uninstall81.lis file. 2. Follow this step to drop a single view from the Banner database. 2.1. Login to the banner database as baninst1. 2.2. Perform a drop view AA_PLEDGE. 2.3. Perform a drop public synonym AA_PLEDGE. OWB* and WB_OLAP* invalid objects The following four objects may be invalid in your ODS database under the design repository and target schemas: OWB_COMPPARAM_MV Materialized View OWBREP or EDWREP (OWB design repository schemas for ODS/EDW products) WB_OLAP_LOAD_CUBE PROCEDURE ODSMGR and EDWSTG and EDWMGR (OWB Target Schemas) WB_OLAP_LOAD_DIMENSION PROCEDURE ODSMGR and EDWSTG and EDWMGR (OWB Target Schemas) WB_OLAP_LOAD_DIMENSION_GENUK PROCEDURE ODSMGR and EDWSTG and EDWMGR (OWB Target Schemas) Cause: These invalid objects are the result of the Oracle OLAP option not existing on your ODS or EDW database. They have no impact on the daily operation of the ODS or 60 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 EDW; however, SunGard Higher Education does not recommend dropping these objects due to the potential for future use. In order to successfully compile these objects, the Oracle OLAP components must be completely installed according to the installation instructions provided by Oracle. The Oracle OLAP option is currently not required by the ODS or EDW products. Solution: Keep these objects in the database. UPD_80100* invalid objects Related FAQ: 1-92XJ2L When running the gurultrp.sql script some invalid objects of the following format may display: UPD_80100_MST_PERSON UPD_80100_MAT_PLEDGE Cause: These objects were used in a previous Banner ODS release, but are no longer needed. Solution: You can manually drop invalid objects of format UPD_80100*. UPDATE_MBT* and DELETE_MBT* invalid objects Related FAQ: 1-92XJ2L When running the gurultrp.sql script some invalid objects of the following format may display: UPDATE_MBT_FUNNEL_HISTORY UPDATE_MBT_EM_CAMPAIGN UPDATE_MBT_COMMUNICATION DELETE_MBT_FUNNEL_HISTORY DELETE_MBT_EM_CAMPAIGN DELETE_MBT_COMMUNICATION Cause: These objects are part of the Banner Recruiting and Admissions Performance product and can be ignored. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 61 Solution: You can leave the objects. They will be fixed the with the next install of the Banner Recruiting and Admissions Performance product. LOAD_MFT_TRANS_HISTORY* invalid objects Related FAQ: 1-92XJ2L When running the gurultrp.sql script the following objects may return as invalid: LOAD_MFT_TRANS_HISTORY_5_PART LOAD_MFT_TRANS_HISTORY_4_PART LOAD_MFT_TRANS_HISTORY_3_PART LOAD_MFT_TRANS_HISTORY_2_PART LOAD_MFT_TRANS_HISTORY_1_PART Cause: These objects are part of the Partition Exchange load components and can be ignored. Solution: These objects will be fixed when you upgrade the Partition Exchange load components in a later step of the installation/upgrade. EDW_ADV_GIFT_EXTR invalid object Related FAQ: 1-92XJ2L When running the gurultrp.sql script the EDW_ADV_GIFT_EXTR object may return as invalid. Cause: This object is part of the Banner EDW product and can be ignored. Solution: This object will be fixed when you upgrade the Banner EDW product to release 8.1.1. OWB issues During the installation or upgrade process you will use .tcl scripts to import product mdl files, register the source and target locations, and validate and deploy OWB mappings. 62 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 This section explains issues you may encounter with the OWB portion of the install or upgrade and how to resolve them. API2422 Connection details are not set for the metadata location Related FAQ: 1-9Y95NV During the OWB import, an error occurs when trying to connect to the metadata location. Solution: Supply the connection information and continue with the import. 1. Start the OWB Design Client. 2. Connect with the Repository Owner. 3. Access Tools>Preferences>Security. 4. Check Persist Location Password in Metadata. 5. COMMIT the change. DELETE_MAT_PROSPECT_CONT_EXP package not found Related FAQ: 1-BCYBBS When deploying mappings during upgrade, the DELETE_MAT_PROSPECT_CONT_EXP package was not deployed because it was not found. This resulted in the following errors: VLD-2751: Missing delete matching criteria in MAT_PROSPECT_CONTACT_EXPENSE LOAD_MAT_PROSPECT_CONT_EXP mapping failed with Error Purging Change Table - DELETE package not found: DELETE_MAT_PROSPECT_CONT_EXP Cause: The loading properties are incorrect. This can happen on Oracle Warehouse Builder (OWB) 10.2.0.2. If you are using OWB 10.2.0.2, the settings are not the same after the import. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 63 Solution: If you are running OWB 10.2.0.2, correct the settings and rerun the mappings using the following directions. 1. In OWB, open the editor for the package DELETE_MAT_PROSPECT_CONT_EXP. 2. Double-click on MAT_PROSPECT_CONTACT_EXPENSE icon to show the columns. 3. Click ENTITY_UID to see the Loading Properties. 4. Change the Loading Properties as follows: 4.1. Set Match Column when Updating Row to Yes. 4.2. Set Match Column when Deleting Row to Yes. 5. Redeploy the mappings. 6. Rerun DELETE_MAT_PROSPECT_CONT_EXP and LOAD_MAT_PROSPECT_CONT_EXP. Error importing SUPPORTEDLANGUAGE American English Related FAQ: 1-BNPA3Z When running the mdl import tcl scripts the following error occurs while creating the OWBREP repository. Error at line 6: MDL1261: Error importing SUPPORTEDLANGUAGE American English. Cause: The system can’t complete the import because the base languages are different. The MDL file base language is <American English> with ISO ID <en_US>. The target repository base language is <English> with ISO ID <en_GB>. Solution: If you use ALLOW_DIFFERENT_BASE_LANGUAGE in scripting, you will be able to import the MDL File. Note Under certain circumstances, importing an MDL file with a different base language could mean corruption of the metadata being imported. Oracle recommends moving metadata between repositories with the same characterset and base language. 64 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 To avoid this error, you can manually update the .mdx of the MDL file giving the error, i.e., PUBLIC_PROJECT.mdl. 1. Backup the PUBLIC_PROJECT.mdl file before making any changes. 2. Unzip PUBLIC_PROJECT.mdl. It contains two files: PUBLIC_PROJECT.mdx and mdlcatalog.xml. 3. Open PULBLIC_PROJECT.mdx in an editor look for the following tags: <LANGUAGE> <SUPPORTEDLANGUAGE LanguageName="American English" IsBaseLanguage="true" ISOID="en_US"> </SUPPORTEDLANGUAGE> </LANGUAGE> 4. Change the LanguageName and ISOID to the language of your target repository. For example: LanguageName="English" ISOID="en_GB" ods_repos.tcl fails; ORA-00922: missing or invalid option Related FAQ: 1-B11RX8 During installation, the ods_repos.tcl fails with the following error: Starting Process: install sourcing ods_repos.tcl Now Creating OWB REPOSITORY OWB repository installtion failed. The Warehouse Builder repository owner installation failed on user OWBREP. Execution failed. ORA-00922: missing or invalid option Cause: The ods_repos.tcl script can fail if there are special characters in the owbrep_pass parameter in the params.tcl file. Solution: Modify the params.tcl file changing the owbrep_pass value to include only alphanumeric characters. After adjusting the owbrep_pass value, you can restart the OWB repository creation process by sourcing params.tcl and then start.tcl. April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 65 RTC-5161. Error when trying to deploy the ODSMGR_LOCATION connector SOURCE_DB Related FAQ: 1-CB440Z When deploying the connector from the ODSMGR_LOCATION in the OWB “Control center manager”, you may get the following error: RTC-5161. The Deployment cannot proceed because of an error during the generation or pre-deployment phase... The stdout2.log includes the following messages: java.lang.RuntimeException: Cannot find handler method handleView at oracle.wh.ui.editor.listener.ReflectListener.findMethod(ReflectLis tener.java:80) at oracle.wh.ui.editor.listener.ReflectListener.<init>(ReflectListene r.java:28) Solution: Restart the OWB service and verify that every location is registered correctly. 1. Restart the OWB service. 1.1. Open the directory $OWB_HOME/owb/rtp/sql. 1.2. Execute the following script: stop_service.sql 1.3. Execute the following script: start_service.sql 1.4. Log in as OWBREP and check for errors. 1.5. If there are any errors, run the service_doctor.sql script to see what went wrong. 2. Login to OWB client (Design center). 3. Click Tools>Control Center Manager. 4. Expand one project (can be any one). 5. Right-click BANNER_LOCATION and select Register. Make sure all the information is valid. 66 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 6. Right-click ODSMGR_LOCATION and select Register. Make sure all the information is valid. 7. If information at either location (from previous steps) is not valid, do the following: 7.1. Right-click the location and select Unregister. 7.2. Right-click Register and select Validate/Test the connection. 8. Expand the ODSMGR_LOCATION section and recreate the SOURCE_DB connector. 8.1. Right-click the SOURCE_DB connect and select set action>recreate. 8.2. Right-click the connect and select deploy. 9. Verify that the connector was deployed successfully. 10. Re-deploy all the mappings using the ods_deloy.tcl script. 10.1. Login to OMBPLUS by running the ombplus.sh or ombplus.bat in the OWB Home/owb/bin/unix or OWB Home/owb/bin/win32 directory. 10.2. Change directory to the ODS Home\ods\owb directory as follows: OMB+>cd e:/ods/ods/owb 10.3. Verify the params.tcl file has the correct database information. 10.4. Execute the following commands: OMB+> source params.tcl OMB+> source start.tcl Select 'R' for Recreate when prompted. Select the Product to be re-deployed when prompted. OMB+> cd tcl OMB+> source ods_deploy.tcl OMB06312: Cannot modify any properties of a registered location except the password Related FAQ: 1-CHPFL6 During the Banner ODS upgrade, you encounter the following error: ----------------------------------------Control Center DEFAULT_CONTROL_CENTER altered. ----------------------------------------- April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 67 Location BANNER_LOCATION altered. ----------------------------------------OMB06312 : Cannot modify any properties of a registered location except the password. ----------------------------------------- Cause: The upgrade is trying to change a property in the BANNER_LOCATION (for example, a schema) because the source location is changing from Banner to the ODS. However OWB will not let you perform this operation with an already registered location. Solution: Perform the following steps to resolve this issue. 1. Open the Oracle design center tool (owbclient.sh). 2. Expand any project. 3. Click Tools>Control Center Manager. 4. Right-click BANNER_LOCATION (or the location at fault), and select Unregister. 5. Close all windows when finished. 6. Verify that all the variables are defined correctly in the params.tcl file when the source params.tcl is executed. 7. Perform the Banner ODS upgrade step again. 68 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting April 2011 April 2011 Banner Enterprise Data Warehouse 8.3 Installation Guide Troubleshooting 69 4 Country View Road Malvern, Pennsylvania 19355 United States of America www.sungardhe.com

Top subcategories

Top subcategories

Top subcategories

Top subcategories

Top subcategories

Top subcategories

Top subcategories

Top subcategories

Download Banner Enterprise Data Warehouse / Installation Guide / 8.3