* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Banner Operational Data Store / Installation Guide / 8.2
Survey
Document related concepts
Concurrency control wikipedia , lookup
Microsoft Access wikipedia , lookup
Extensible Storage Engine wikipedia , lookup
Entity–attribute–value model wikipedia , lookup
Functional Database Model wikipedia , lookup
Microsoft Jet Database Engine wikipedia , lookup
Ingres (database) wikipedia , lookup
Microsoft SQL Server wikipedia , lookup
Oracle Database wikipedia , lookup
Relational model wikipedia , lookup
Open Database Connectivity wikipedia , lookup
Clusterpoint wikipedia , lookup
Transcript
Banner Operational Data Store Installation Guide Release 8.2 August 2010 (Revised) 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. © 2009-2010 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. 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 October 2009 New version that supports Banner Operational Data Store 8.2 software. November 2009 Revised to support Banner Operational Data Store 8.2 software including additional prerequisite information. August 2010 Added Troubleshooting chapter, which includes information from FAQs related to Banner ODS installation. Banner Operational Data Store 8.2 Installation Guide Contents Chapter 1 Banner Operational Data Store Installation Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Terms Used in this Document . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Step 1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Step 2 Install Banner Source Database Components . . . . . . . . . . . . . . . 1-8 Step 3 Install ODS Target Database Components . . . . . . . . . . . . . . . . . 1-10 Step 4 Configure the ODS Administrative User Interface. . . . . . . . . . . . . . 1-25 Step 5 Install Reporting Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29 Chapter 2 Banner Self-Service Reporting Installation SSR Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Step 1 Create the SSRMGR schema and its objects . . . . . . . . . . . . . . . . 2-1 Step 2 Create an APEX workspace named “SSR” . . . . . . . . . . . . . . . . . 2-1 Step 3 Add Schema Assignments . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Step 4 Import and Install the SSR Application into the SSR Workspace . . . . . . 2-3 Step 5 Import the SSR Graphic Files . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Step 6 Import the SSR JavaScript File . . . . . . . . . . . . . . . . . . . . . . . 2-5 Step 7 Import the SSR Style Sheet Files . . . . . . . . . . . . . . . . . . . . . . 2-5 Step 8 Customize Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 Install SSR Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Oracle User Account Authentication . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Oracle User Account Authorization . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Publish the SSR End User URL . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 August 2010 Banner Operational Data Store 8.2 Installation Guide Contents iii Self-Service Reporting Installation – Optional Steps . . . . . . . . . . . . . . 2-10 Alternative Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 Application Express User Account Security . . . . . . . . . . . . . . . . . . . . 2-11 Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 Modify Email Sender’s Name . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 Set Default Lines Per Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 Control Access to Population Selection. . . . . . . . . . . . . . . . . . . . . . . 2-15 Set Up a Second SSR Environment . . . . . . . . . . . . . . . . . . . . . . . . 2-15 Create the Database Objects in Different Schemas . . . . . . . . . . . . . . . 2-16 Create Database Objects in Same Schemas with Different Object Names . . . . 2-16 Chapter 3 Oracle Discoverer Installation Oracle Discoverer End User Layer . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Distribution Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Chapter 4 Cognos Business Intelligence 8 Installation Prerequisite Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Import Banner ODS Deployment Archive (packages) into Cognos Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Create portal tab for Banner Operational Data Store . . . . . . . . . . . . . . . . 4-3 Upgrade Framework Manager Model . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Troubleshooting Administrative UI issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T-3 Page not enabled for current user role(s) because INSTALL user is missing . . . T-3 Checks and Balances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T-5 Error Mapping is INVALID in the database . . . . . . . . . . . . . . . . . . . . . T-5 Staging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T-5 Restage an ODS stage table . . . . . . . . . . . . . . . . . . . . . . . . . . . . T-5 iv Banner Operational Data Store 8.2 Installation Guide Contents August 2010 ORA-01422: exact fetch returns more than requested number of rows . . . . . . T-7 Error restaging tables; ORA-20000: Retrieving source database link terminated . T-8 ods_upgrade.sql . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T-9 Scripts not connecting correctly. . . . . . . . . . . . . . . . . . . . . . . . . . . T-9 [product]_etl_install.sql scripts. . . . . . . . . . . . . . . . . . . . . . . . . . T-9 ORA-04045: errors during recompilation/revalidation. . . . . . . . . . . . . . . . T-10 ORA-04063: package body "ODSSTG.MGKSTRM" has errors . . . . . . . . . . T-11 ORA-12545: Connect failed because target host or object does not exist . . . . . T-13 ORA-20000: Adding a table rule terminated . . . . . . . . . . . . . . . . . . . . T-14 ORA-20000: Exporting and importing LONG table data terminated . . . . . . . . T-16 ORA-20000: Preparing to import terminated . . . . . . . . . . . . . . . . . . . . T-17 ORA-20000: Retrieving source database link terminated. . . . . . . . . . . . . . T-18 ORA-20000: Stopping the capture process terminated . . . . . . . . . . . . . . . T-19 ORA-26723: user "ODSSTG" requires the role "DBA" . . . . . . . . . . . . . . . T-19 ORA-31685: Object type failed due to insufficient privileges . . . . . . . . . . . . T-20 ORA-31693: Table data object failed to load/unload . . . . . . . . . . . . . . . . T-21 ORA-31693: Table data object failed to load/unload . . . . . . . . . . . . . . . . . . . . . . T-22 ORA-39014: One or more workers have prematurely exited . . . . . . . . . . . . T-24 ORA-39083: Object type INDEX_STATISTICS failed. . . . . . . . . . . . . . . . T-25 ORA-39125: Worker unexpected fatal error . . . . . . . . . . . . . . . . . . . . T-26 Cannot stage table; no matching records in MGBSTRM . . . . . . . . . . . . . . T-26 Installation stops responding . . . . . . . . . . . . . . . . . . . . . . . . . . . . T-27 [product]_stage.sql . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T-28 ORA-20000: Preparing to import terminated . . . . . . . . . . . . . . . . . . . . T-28 gurutlrp.sql script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T-29 ORA-01031: insufficient privileges message Alumni/ODS views invalid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T-29 OWB* and WB_OLAP* invalid objects . . . . . . . . . . . . . . . . . . . . . . . T-31 UPD_80100* invalid objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . T-32 UPDATE_MBT* and DELETE_MBT* invalid objects . . . . . . . . . . . . . . . . T-32 LOAD_MFT_TRANS_HISTORY* invalid objects . . . . . . . . . . . . . . . . . . T-33 EDW_ADV_GIFT_EXTR invalid object . . . . . . . . . . . . . . . . . . . . . . . T-33 August 2010 Banner Operational Data Store 8.2 Installation Guide Contents v OWB issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T-33 API2422 Connection details are not set for the metadata location . . . . . . . . . T-34 DELETE_MAT_PROSPECT_CONT_EXP package not found . . . . . . . . . . . T-34 Error importing SUPPORTEDLANGUAGE American English . . . . . . . . . . . T-35 ods_repos.tcl fails; ORA-00922: missing or invalid option . . . . . . . . . . . . . T-36 RTC-5161. Error when trying to deploy the ODSMGR_LOCATION connector SOURCE_DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T-37 OMB06312: Cannot modify any properties of a registered location except the password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T-38 vi Banner Operational Data Store 8.2 Installation Guide Contents August 2010 1 Banner Operational Data Store Installation Introduction This guide details the steps necessary to install the Banner Operational Data Store (Banner ODS). Refer to the Banner Operational Data Store Release Guide and Banner Operational Data Store Handbook for details regarding enhancements and functional content included with this release. There are three main components associated with this installation: • Install the ODS components on the Banner source database. • Install the ODS ETL components and objects on the ODS target database. • Install and configure the Oracle Warehouse Builder components Because of the dependent nature of the ODS components, you must run the installation in the order specified in this guide. Terms Used in this Document Throughout this document there are references to the ODS. The ODS refers to the Banner Operational Data Store. It is referenced solely as “ODS” to avoid confusion with references to the baseline Banner database. August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation 1-1 Step 1 Prerequisites Before you perform installation of the ODS, you must verify the database configuration and Oracle Warehouse Builder (OWB) prerequisites. The ODS database should exist on a separate server from the source Banner database. Warning Be sure to read and follow the prerequisites outlined in this section for a smooth installation of the ODS. 1.1. Read the BPRA Resource Guidelines document The BPRA Resource Guidelines document delivered with this release of ODS outlines ODS database requirements and recommendations. Be sure to read the new sizing requirements for the ODS 8.2 architecture changes. 1.2. Banner EDW Compatibility ODS 8.2 is compatible with the following Banner EDW releases: • Banner EDW 8.1 with patch p1-82ynmr_edw80100. You must install the patch after installing or upgrading to ODS 8.2. • Banner EDW 8.1.1. 1.3. Oracle Compatibility If you are running Oracle 10.2.0.3, you may encounter Oracle error ORA06502 while staging tables in the ODS. This error is associated with Oracle bug 5718757, which is resolved in Oracle 10.2.0.3 Patch 2 (Windows) or by upgrading to Oracle 10.2.0.4. To avoid this error, apply Oracle 10.2.0.3 Patch 2 or upgrade to Oracle 10.2.0.4 before installing the Banner ODS. 1.4. Oracle Initialization Parameters The following is a list of suggested settings for parameters that are relevant to an Oracle Streams local capture taken from the Oracle Streams Concepts and Administration Guide. • The COMPATIBLE parameter of the Banner and ODS databases must be at least 10.2.0. • GLOBAL_NAMES should be set to TRUE on both the Banner and ODS databases. The Global Database Name of the Banner and ODS databases may need to be modified to be fully qualified using a database name and a domain by issuing the following command: ALTER DATABASE RENAME GLOBAL_NAME TO fully_qualified_database_name; 1-2 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation August 2010 Note Ensure that the names of the existing database links that connect to the Banner and the ODS databases match the global name of the database they connect to. • The Oracle initialization parameter service_names should match the fully qualified global database name. If the tnsnames.ora file located on client machines reference the SERVICE_NAME, then the value may need to be modified to be fully qualified. If they reference the SID, the value should continue to match the instance_name initialization parameter. Note Make sure there is a valid DATA_PUMP_DIR directory object specified in the Banner and ODS databases. A directory object is a logical name for a physical directory on the database server file system. Any Banner tables that contain a LONG data type column required by the ODS will be exported to a dump file on the Banner server, sent to the ODS server over the database link, and then imported into the ODS. On Unix and Windows, a DATA_PUMP_DIR directory object is created by default. Run the following to see a list of existing directory objects. SELECT * FROM ALL_DIRECTORIES; If needed, create or modify the DATA_PUMP_DIR directory object. This directory object must be created under the SYS user. For example: CREATE OR REPLACE DIRECTORY data_pump_dir AS '/u01/app/Oracle/ product/10.2.0.4/rdbms/log'; Note Avoid modifying global database names once the Streams environment is configured since the Oracle Streams use global database names to function properly. Parameter Description and Recommended Setting AQ_TM_PROCESSES No longer needed in Oracle 10g. However, setting this parameter to 0 (zero) may cause serious problems with Streams architecture. Leave the parameter unset (recommended) or set the value between 1 and 10 in Banner and ODS. COMPATIBLE Set to 10.2.0 or higher in Banner and the ODS. GLOBAL_NAMES Specifies whether a database link is required to have the same name as the database to which it connects. Set to true in Banner and the ODS for Streams to function correctly. August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation 1-3 Parameter Description and Recommended Setting JOB_QUEUE_PROCESSES Maximum number of DBMS_JOB processes. Increase the value by 2 in the Banner database. LOG_ARCHIVE_DEST_n Specifies a directory where the archived redo log files will be created. Note: It is extremely important that Banner archived log files are not removed until they are no longer required by Streams. If you are using an Oracle Flash Recovery Area (FRA), then either specify a separate archive log destination outside of the FRA (recommended), or increase the disk quota of the FRA to reduce the possibility that required archived log files will be removed. Set a value on Banner where n is any integer between 1 and 10. LOG_ARCHIVE_DEST_STATE_ n Specifies the state of the associated destination. OPEN_LINKS Maximum number of concurrent open connections to remote databases in one session. Set to enable on the Banner database. Make sure this parameter is set to the default value of 4 or higher in Banner and the ODS. PARALLEL_MAX_SERVERS Automatically derived value specifies the maximum number of parallel execution processes and parallel recovery processes for an instance. Refer to Oracle documentation for details. SGA_MAX_SIZE Specifies the maximum size of the System Global Area (SGA). Consider increasing this value on the Banner database if you run multiple capture processes. SGA_TARGET Specifies the total size of all SGA components. Oracle recommends enabling the autotuning of the various pools within the SGA by setting SGA_TARGET to a large nonzero value and setting STREAMS_POOL_SIZE to 0. 1-4 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation August 2010 Parameter Description and Recommended Setting SHARED_POOL_SIZE The shared pool contains shared cursors, stored procedures, control structures, and other structures. If the SGA_TARGET and STREAMS_POOL_SIZE are set to zero, then up to 10% of the shared pool is transferred to the Streams pool. STREAMS_POOL_SIZE The Streams pool contains buffered queue messages. If the SGA_TARGET initialization parameter is set to a nonzero value, then the Streams pool size is set by Automatic Shared memory management and STREAMS_POOL_SIZE specifies the minimum size. Increase this value by 20MB on Banner, and by 11MB on the ODS. TIMED_STATISTICS Specifies whether or not elapsed time statistics are collected in the dynamic performance views related to Streams. Set to true in Banner and the ODS if you want to collect timed statistics. UNDO_RETENTION Set in the Banner database, this parameter specifies the amount of time in seconds to retain committed undo information. If you are unsure about the proper setting, try setting this parameter to at least 3600. If you encounter “snapshot too old” errors, then increase this value until these errors cease. Make sure the undo tablespace is large enough to accommodate the UNDO_RETENTION setting. Archiving Redo Logs An Oracle Streams local capture process will periodically read the online redo generation on the source database. If the capture process is slower than the online redo generation, it can seamlessly switch to reading the archived redo until it completes reading the latest redo. For this reason, the Banner database must be put into ARCHIVELOG mode before continuing to install the ODS. Archived redo log files must remain available on the host until they are no longer needed by any Streams capture processes. The data in the ODS ultimately comes from the source Banner tables. Since the Banner data can be reloaded into the ODS at any time, it is recommended that you don’t put the ODS into ARCHIVELOG mode. This will reduce the amount of processing overhead when running the ODS mappings, and will also eliminate the need to maintain archived redo logs on the ODS host. August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation 1-5 Oracle Streams Tablespaces (optional) Create a new tablespace for the Streams administrative user in the Banner and ODS databases if desired. Any Streams objects that are created by the Streams administrative users will reside in these tablespaces. Existing tablespaces may be used, however the SYSTEM tablespace should never be used for this purpose. 1.5. If you are running the ODS on Oracle database version 10.2.0.3, add the following Oracle initialization parameter to the ODS database: _optimizer_order_by_elimination_enabled = false Setting this parameter ensures that reporting views containing both CONNECT BY and ORDER BY clauses function properly. 1.6. Set the following init.ora parameter after the database has been created: NLS_LENGTH_SEMANTICS=CHAR Note When you change the NLS_LENGTH_SEMANTIC parameter after the database has been created, the database must be bounced for the parameter to properly take effect. The ODS product is Unicode compliant. Because of this it must be run on a database with a Unicode character set, regardless of whether or not multibyte characters exist in the database. The only currently supported Unicode character set that may be used in the ODS database is AL32UTF8. The ODS database must be created with the ‘AL32UTF8’ character set. The NLS_LENGTH_SEMANTICS parameter will enable the internal storage of table columns to be multi-byte but will preserve the presentation of character lengths. This parameter only affects tables built explicitly after the parameter is implemented. Therefore, you must set this parameter before you continue with the installation of the ODS product. 1.7. Verify the ODS Database Configuration Verify the Java Virtual Machine, XDK and XML Database components exist and are properly configured in your database. These components are required for OWB functionality. 1.7.1. Query the dba_registry view by typing the following command: select comp_name, status from sys.dba_registry If you are installing the OWB runtime repository in the same ODS instance (this is commonly done because it simplifies the install process), select create custom database instead – this is the only option that allows for the 16K (16384) block size recommended 1-6 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation August 2010 for the runtime repository instance (see p.1-11 of the Oracle Warehouse Builder Installation and Configuration Guide for 10.2 (Part B28224-01). Note GENERAL PURPOSE, DATAWAREHOUSE and TRANSACTION PROCESSING database options should not be selected since this only allows the database to be created in the default 8K (8192) block size. See Oracle Note 387598.1 DBCA Cannot Find Template Files ORA-19870 1.7.2. Check that the following registry entries exist: Oracle XDK VALID Oracle XML Database VALID JServer JAVA Virtual Machine VALID 1.8. Create a temporary tablespace of type temporary in the ODS database. This tablespace entry must exist in your ODS database before you can begin the OWB repository installation. CREATE TEMPORARY TABLESPACE TEMP TEMPFILE ‘/u03/oradata/ODS/temp_ODS_01.dbf’ size 2000M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K; ALTER DATABASE DEFAULT TREMPORARY TABLESPACE TEMP; 1.9. Temporarily set the following database initialization parameter to allow remote SYSDBA connectivity during the ODS installation process. O7_DICTIONARY_ACCESSIBILITY = TRUE Note The leading character of the parameter is the letter ‘O’ not the number zero. During the OWB Repository creation process, the Warehouse Builder command-line interface OMB*Plus attempts a database connection as SYSDBA. By default, the Oracle database does not allow remote SYSDBA connectivity so this connection will fail. Setting the above parameter to TRUE will allow the OMB*Plus interface to properly connect as SYSDBA and create the associated OWB users. It is highly recommended that this accessibility parameter be removed after installation as a security measure. The parameter is not required after the ODS installation. August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation 1-7 1.10. Install OWB Software The Oracle Warehouse Builder (OWB) components are required for the installation and daily operation of the ODS. You should install the supported version of OWB according to the OWB Installation Guide provided by Oracle. The following are general guidelines that you should follow as part of the ODS installation. These guidelines are intended to complement (not replace) the installation instructions provided by Oracle: • Install OWB in an ORACLE_HOME directory separate from any other Oracle products installed on the ODS server. • The creation of the OWB Repository on your ODS database is done as part of the ODS installation process. You should not configure or install the OWB Unified Repository until Section 3 of this installation guide. Step 2 2.1. Install Banner Source Database Components Modify the login.sql file for Banner database parameters. The installation scripts for the ODS components on the Banner source database are located under the ‘banner’ subdirectory of the ODS source code. The ‘install’ subdirectory of ‘banner’ is where all installation related driver scripts reside. All steps detailed in this Section are run from the banner/install subdirectory. The first step of the Banner component installation is to modify several SQL*Plus variables in the login.sql file located under the banner/install subdirectory: SQL*Plus Variable Description plus_cmd The plus_cmd variable determines the command to be used to invoke SQL*Plus when executing a HOST started SQL*Plus task during this upgrade. The default value of this variable is sqlplus. Not currently used by ODS Installation 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 ODS install media. For example, on a Unix system, this value would be specified as /u02/ software/ods. On a Windows system, this value would be specific as D:\software\ods. A trailing slash at the end of the directory specification is not required. splpref home_dir 1-8 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation August 2010 SQL*Plus Variable Description passwords The next section of the login.sql files defines the passwords to all the Banner product owner 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. If you have any other Oracle IDs that own Banner tables, you will have to define their passwords as well. It will be a security problem if you put your passwords into the login.sql file. You should temporarily change all the account passwords for the duration of the upgrade and set them back after the upgrade is completed. tablespaces This section defines the default and temporary tablespaces to be used when creating the Streams Administrative user ODSSTG. database link variables The next section of the login.sql file defines the host, port, and global name of the ODS database. A database link will be created between the Streams administrative user in Banner to the equivalent user in ODS. table and index sizing models The next section of the login.sql file defines what tables and indexes are to be used as sizing and placement models for the new tables created during this upgrade. Each product has a definition for small, medium, large, and huge tables and indexes. If you do not feel the value specified reflects your environment, please feel free to change it. Definitions for products that you do not have will be ignored by the upgrade process. clob/blob sizing models The next section of the login.sql file defines the default clob/ blob sizes which are to be used when creating new columns of these types during the upgrade. Again, if you do not feel the values specified for these variables reflect your environment, please feel free to change them. In addition, be sure to verify that the model ????_tablespace_name of DEVELOPMENT is appropriate for your environment. Definitions that are not used by this upgrade will be ignored. 2.2. Build the ODSSTG schema on Banner database. In this step, you will create a new schema in your Banner database called ODSSTG. This new database user will own all Streams components required to replicate specified changes over a private database link to the ODS. Because of these privileges, the ODSSTG database account should be treated as a trusted account, similar to any Banner product owner, and secured appropriately. You will be prompted for the SYS password after starting the script. A SYS connection is required in order to grant the necessary privileges. August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation 1-9 2.2.1. Access the ODS_HOME/banner/install directory. sqlplus /nolog @odsstg 2.2.2. Click Enter. Review odsstg.lst You must resolve any user creation errors before continuing. 2.3. Install the ODSSTG components on the Banner database. In this step, the necessary packages will be compiled and a database link will be created which connects to an ODSSTG user on the ODS database that will be created in a later step. 2.3.1. Access the ODS_HOME/banner/install directory. sqlplus /nolog @odsstg_banner_install 2.3.2. Click Enter after each entry to continue to the next entry: Review odsstg_banner_install.lst You must resolve any object creation errors before continuing. 2.4. Verify the state of the upgraded environment To recompile any invalid objects as a result of the install process, run the gurutlrp.sql script located in the ODS_HOME/banner/install directory: sqlplus /nolog @gurutlrp.sql Troubleshooting gurutlrp script issues You should resolve any invalid objects prior to continuing with the Banner ODS installation process. Refer to the “gurutlrp.sql script” section in the “Troubleshooting” chapter for information about possible resolutions for some invalid objects. This is the end of the ODS component installation on your Banner database. Step 3 3.1. Install ODS Target Database Components Modify OWB/OMB Parameter File, params.tcl for Repository Installation The first requirement of the ODS installation process is the creation of the Oracle Warehouse Builder Unified Repository. This repository stores information on OWB design components such as ETL mappings in addition to execution audit data. The creation of the unified repository is performed using the OMB*Plus command-line interface tool delivered with OWB. Prior to installing the OWB Unified Repository, several site-specific parameters must be modified accordingly within the params.tcl file, located in the ods/owb 1-10 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation August 2010 directory within ODS_HOME. The params.tcl is the OMB equivalent of the login.sql file for SQL*Plus. Review each parameter listed in params.tcl and modify as necessary based upon your site-specific values such as connect information for the ODS, and schema names and passwords. Many of the parameters are dynamically parsed during OMB*Plus steps, including the repository creation process. The following parameters should be reviewed and changed as necessary within params.tcl: Parameter Description Hostname or IP of your ODS/ EDW database # ODS/EDW Database Port Port Number of your Oracle set owbport 1521 listener for the ODS/EDW database # ODS/EDW Database SID Database SID or Global Name of set owbsid ODS your ODS/EDW Database # OWB ORACLE Database Version 9.2, 10.1, 10.2 Oracle Version of your ODS/ set owbver 10.2 EDW Database. # OWB Repository Owner, OWBREP, Password Username of repository owner. It set owbrep_pass u_pick_it is recommended you use OWBREP. # ODS/EDW Database Host set owbhost odshost Note: Use only alphanumeric characters in the password; do not use any special characters. Repository Access User is created with this password. # SYS Password, needed for repository creation Required for SYS connection to set owbsys_pass change_on_install create the repository # OWBRT SYS Password: set during repository Repository User is created using # creation this password. # OWB Repository User, OWBUSER, Password set owbuser_pass u_pick_it set owbrt_sys_pass u_pick_it # OWB Repository DATA_TABLESPACE name set d_tname DEVELOPMENT # OWB Repository INDEX_TABLESPACE name set i_tname INDX # OWB Repository TEMPORARY_TABLESPACE name set t_tname TEMP # Please Enter the Location of the ODS Source Directory # For Example: /u02/sct/ods, D:\sct\ods # would be /u02/sct/ods, d:/sct/ods set ods_home_dir /u01/sghe/ods # ODS Target Schema, ODSMGR, Password set odsmgr_pass u_pick_it August 2010 Default tablespace for OWB users. Tablespace used for Indexing in OWB. Recommended this be separate than data tablespace. Default Temporary Tablespace of OWB default users. The ODS Home directory. Password specified during creation of ODS Owner, ODSMGR Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation 1-11 Parameter Description This is the hostname of your ODS Stage database # ODS Source Port Port number of your Oracle set source_port 1521 listener for the Banner source database # ODS Source SID Database SID or Global Name of set source_sid BANNER your ODS Stage database. # ODS Source Account, Password Password of ODSSRC user on set source_account_pass u_pick_it ODS Stage database, created in Step 2.2. # Source Database Version: 10.2, 10.1, or 9.2 Oracle version of your Banner set odssource_version 10.2 Database. # ODS Source Host set source_host bannerhost 3.2. OWB Repository Installation The OMB*Plus interface is installed with the OWB software. Because of the way in which OMB sets required environment variables, you must be positioned within the proper directory from a command line to properly start the application: Unix OMB*Plus $OWB_HOME/owb/bin/unix Windows OMB*Plus $OWB_HOME/owb/bin/win32 After launching the OMB interface from within the correct directory, the parameters required for the next step must be properly parsed: Unix OMB*Plus $ ./OMBPlus.sh 3.2.1. Click Enter. OMB*Plus: Release 10.2.0.2.8 Copyright (c) 2000, 2006, Oracle. All rights reserved. OMB+> cd /u01/sghe/ods/ods/owb 3.2.2. Click Enter. OMB+> source params.tcl 1-12 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation August 2010 3.2.3. Click Enter. Parameter values have been set for:odshost:1521:ODS Windows OMB*Plus D:\oracle\owb10.2\owb\bin\win32>OMBPlus.bat 3.2.4. Click Enter. OMB*Plus: Release 10.2.0.2.8 Copyright (c) 2000, 2006, Oracle. All rights reserved. OMB+> cd d:/sghe/ods/ods/owb 3.2.5. Click Enter. OMB+> source params.tcl 3.2.6. Click Enter. Parameter values have been set for : odshost:1521:ODS 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. The repository creation process can now be started from within the OMB*Plus Environment: Unix and Windows OMB*Plus OMB+> source start.tcl 3.2.7. Click Enter. Do you want to (u)pgrade, (i)nstall, or (r)ecreate project work list: Choose ‘i’ for Install 3.2.8. Click Enter. Install Selected Only select the products for which you are licensed on Banner and ODS. The products selected will be dynamically included in the script built for the import and deploy process during this phase. Do you want to select the ADVANCEMENT product?(y) or (n):y Do you want to select the AR product?(y) or (n):y Do you want to select the FINAID product?(y) or (n):y Do you want to select the FINANCE product?(y) or (n):y August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation 1-13 Do you want to select the GENERAL product?(y) or (n):y Do you want to select the HR product?(y) or (n):y Do you want to select the STUDENT product?(y) or (n):y You would like to install the following products: ADVANCEMENT AR FINAID FINANCE GENERAL HR STUDENT Is this correct? y or n Is this correct?(y) or (n):y Starting Process: install After selecting the licensed products, the start.tcl process will build the Unified Repository, in addition to the OWB Target Schema and Repository Access User based upon the parameters within params.tcl. 3.2.9. 3.3. Review the start.log output file within the ods/owb/log directory prior to continuing. Modify login.sql for ODS database The installation scripts for the ODS components on the ODS database are located under the ods subdirectory of the ODS source code. The install subdirectory of ods is where all installation related driver scripts reside. All steps detailed in this section are run from the ods/install subdirectory. The first step of the ODS database component installation is to modify the following SQL*Plus variables in the login.sql file located under the ods/install subdirectory: 1-14 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation August 2010 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 ODS install media. For example, on a Unix system, this value would be specified as /u02/software/ods. On a Windows system, this value would be specific as D:\software\ods. A trailing slash at the end of the directory specification is not required. database link variables The next section of the login.sql file defines the host, port, and global name of the Banner database. A database link will be created between the Streams administrative user in ODS to the equivalent user in Banner. source alias The source alias is used to differentiate between multiple source databases. This value will be used as a prefix when naming the Oracle Streams components. These include the capture and apply processes, queues, and the propagation schedule. A webtailor parameter will be created in ODS associating the source alias with the database link owned by ODSSTG that connects to the Banner database. August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation 1-15 SQL*Plus Variable Description passwords The next section of the login.sql files defines the passwords to all the ODS 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 upgrade and set them back after the upgrade is completed. default user tablespaces This section of the login.sql file defines default DATA and TEMP tablespaces for ODS 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. To successfully stage tables from Banner into the ODS staging area, you need to create tablespaces on the ODS that are identical to the tablespaces in the Banner database. You need to size these tablespaces as needed. For example, if tables in the Banner database use tablespaces separated by Banner product such as, ALUMNI, FINAID, and STUDENT, then create the same tablespaces on the ODS database before you install. If you have customized tablespace names for the Banner tables to be staged, then create identical tablespaces on the ODS database before you install. 3.4. Build the Database Users on the ODS Database In this step, you will run a script that will create the additional baseline ODS users. The login.sql file is referenced for the default tablespaces for each user. The following users are created in this step: 1-16 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation August 2010 User Schema Definition WTAILOR Owns the baseline Web Tailor objects utilized by the ODS Administrative User Interface, the web based administration tool. IA_ADMIN Owns the ODS Administrative User Interface database objects. The administrative web interface is rendered with objects from both the WTAILOR and IA_ADMIN schemas ODSLOV This schema owns all list of values views, utilized by the front-end reporting tools. WWW_USER A schema delivered out-of-the-box with only the query privileges necessary to run the Administrative UI within an Oracle Application Server. This is the user specified on your application server within the DAD that connects to the database ODSSRC This schema owns all of the composite views used to load the ODS data, and packages used to create change table records. ODSSTG This is the Oracle Streams administrative user on the ODS. All of the Oracle Streams components that reside on the ODS are created under this schema. From within the ods/install directory: sqlplus /nolog @ods_users.sql 3.4.1. Click Enter. You will be prompted for the SYS password prior to starting with the user creation process. A SYS connection is required because of several DBMS package grants necessary. Review: ods_users.lst 3.5. Import Web Tailor Objects from export file The components necessary for the Web Tailor foundation of the Administrative UI must be imported into the ODS database from a dump file included with the ODS source. From within the ods/install directory: Imp system/[password] parfile=wtailor.par log=wtailor.log file=wtailor.dmp August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation 1-17 3.5.1. Click Enter. Resolve any import related errors prior to continuing. 3.6. Build ODS Functional Objects on ODS Database This step installs the Oracle Streams processes in the Banner and ODS databases. It also installs the database objects necessary for reporting and data extractions. The Administrative UI objects are also created during this step. Because of the cross-product dependency between many of the views within the ODS, the installation of the reporting tables and views is done by object type and not necessarily by product. The composite tables are built along with the supporting procedures prior to the views being created. From within the ods/install directory: sqlplus /nolog @ods_install.sql 3.6.1. Click Enter. Review: ods_install.lst 3.7. Stage and Install the ETL Components on the ODS Database. In this step, you will run several Stage and ETL (extract, transform and load) installation scripts on your ODS database that will create staging users in the ODS, stage the necessary Banner tables, and compile all change tables, triggers, packages and views by Banner product area. A staging user is created for each of the ETL driver scripts that you run. The names of the staging users will match the schema owner of the Banner product that will be staged. For example, the student_etl_install.sql script will create a SATURN user in the ODS. Since Banner tables and data will be imported into each of the stage users in ODS, these new users should be treated as trusted accounts, similar to any Banner product owner, and secured appropriately. The ETL objects are used to initially load the data into the ODS from your staged Banner tables. The ETL change tables and triggers are used to maintain a record of changed data for incremental refresh purposes. There is one Stage and ETL driver script for each Banner product within the directory. You should run the Stage and ETL driver script for each ODS module you have licensed. If you do not have a particular Banner product installed and attempt to run the corresponding Stage and ETL script, the installation of the database objects will fail. The Stage and ETL installation scripts have a naming convention of [product]_etl_install.sql. $ODS_HOME/ods/install 1-18 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation August 2010 3.7.1. Access the ODS_HOME/ods/install directory. 3.7.2. The name of the ODS tablespaces that will contain staged tables must match the name of the Banner tablespaces that contain the source tables. Optionally, run the following script to view the required tablespaces in ODS for each schema that may be staged along with the size estimates: sqlplus /nolog @required_tablespaces.sql Review required_tablespaces.lst and create additional tablespaces in ODS as necessary 3.7.3. Click Enter after each entry to continue to the next entry: 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 3.7.4. Review each corresponding output file for errors. For example, general_etl_install.lst. Troubleshooting [product]_etl script issues Note If you encounter errors when running these scripts, refer to the “[product]_etl_install.sql scripts” section in the “Troubleshooting” chapter for information about possible resolutions for some errors. 3.8. Import and Deploy OWB Mappings using OMB*Plus With the mapping dependencies installed on both the Banner and the ODS database, the OMB import and deploy process can be started. As part of this process, the source objects needed for data extraction, and the target tables on the ODS are verified to ensure they exist and that appropriate permissions are present to allow the ETL process to run properly. The tcl script referenced below is dynamically created based upon the products chosen in Step 3.2 during the start.tcl process. The params.tcl file that was previously modified is also utilized by this OMB*Plus session. There is no need to modify any parameters contained within unless problems were encountered during the start.tcl process. OMB*Plus will need to be restarted from the proper August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation 1-19 directory (refer to Step 3.2, “OWB Repository Installation”for steps to start OMB*Plus) and the parameters within params.tcl need to be re-parsed within this OMB*Plus session. The ods_install.tcl script can then be started. This script will import each Product/Project MDL file, register the Source (Banner) and Target (ODS) locations 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. 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. Unix OMB*Plus $ ./OMBPlus.sh 3.8.1. Click Enter. OMB*Plus: Release 10.2.0.2.8 Copyright (c) 2000, 2006, Oracle. All rights reserved. OMB+> cd /u01/sghe/ods/ods/owb 3.8.2. Click Enter. OMB+> source params.tcl 3.8.3. Click Enter. Parameter values have been set for:odshost:1521:ODS OMB+> source ods_install.tcl 3.8.4. Click Enter. Windows OMB*Plus D:\oracle\owb10.2\owb\bin\win32>OMBPlus.bat 3.8.1. Click Enter. OMB*Plus: Release 10.2.0.2.8 Copyright (c) 2000, 2006, Oracle. All rights reserved. OMB+> cd d:/sghe/ods/ods/owb 3.8.2. Click Enter. OMB+> source params.tcl 1-20 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation August 2010 3.8.3. Click Enter. Parameter values have been set for : odshost:1521:ODS OMB+> source ods_install.tcl 3.8.4. Click Enter. Note Because of the memory intensive operation of the OMB*Plus application, the import/deploy process can sometimes fail without warning. Further investigation into application and system logs will reveal a Java “out of memory” error. In order to minimize the impact of this on your install or upgrade, review the following suggestions: • Ensure the import/deploy process is run locally on your ODS server, rather than a desktop class machine. • Shutdown unnecessary processes on the server such as other databases or virus scan applications in order to allow the import/deploy process to utilize as much memory as needed. • There are two memory management parameters within the OMB*Plus shell and bat files (OMBPlus.sh, OMBPlus.bat). Depending upon your total memory available on your ODS database server, these values can be searched for and increased within each file to allow the process additional memory resources: Delivered Settings: -Xmx256M –Dlimit=256M Recommended Settings: -Xmx1024M –Dlimit=1024M This recommendation is based on a ODS Database server with a minimum of 2GB of system memory. The output from each process of the import and deploy process is written to log files under the ods/owb/log subdirectory. These log files should be reviewed for any errors prior to continuing. It is also recommended the deploy results also be verified using the Deployment Manager within the OWB Client application or the OWB Audit Browser. Refer to the Oracle Warehouse Builder documentation for further information. 3.9. Verify the state of the ODS To recompile any invalid objects as a result of the ODS install process, run the gurutlrp.sql script located in the ODS_HOME/ods/install directory: sqlplus /nolog @gurutlrp.sql Troubleshooting gurutlrp script issues You should resolve any invalid objects prior to continuing with the Banner ODS installation process. Refer to the “gurutlrp.sql script” section in the August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation 1-21 “Troubleshooting” chapter for information about possible resolutions for some invalid objects. Keep Invalid Oracle OLAP objects The following four objects may be invalid in your ODS and EDW database under the design repository and target schemas. These objects are the result of the Oracle OLAP option not existing on your ODS/EDW database. They have no impact on the daily operation of the ODS or 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. These objects are: 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) This is the end of the ODS database component installation on your ODS database. 3.10. Apply Required Data Changes This step uses the database link created as part of the import/deploy process in 3.8 to extract data from the GTVSDAX table in Banner to the MGRSDAX table in the ODS. The MGRSDAX table contains default values used during the ODS load process. Refer to the ODS Handbook for additional information. sqlplus odsmgr/odsmgr_password 3.10.1. Click Enter. 3.10.2. Start mgrsdax_data_ods.sql Review: mgrsdax_populate.lst 1-22 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation August 2010 3.11. Install Partition Exchange Load Components (optional) This optional installation step introduces the partition exchange load components into the ODS for the MFT_TRANS_HISTORY and MPT_PAYROLL_DISTRIBUTION tables. The partition exchange load components allow you to run the data load for these tables as concurrent processes, using temporary tables and the database partitioning option. Note The Oracle Partitioning database option is separately licensed. It is your institution’s responsibility to ensure that the licensing necessary for partitioning functionality is in place before you use this component. ODS Database Steps From within the ods/install directory, run the following scripts to build the temporary tables for partition exchange loads and rebuild the ODS tables and associated partitions. These scripts will also update the Administrative User Interface components as necessary with the partitioning enhancement. There is a script for each ODS product or module where partitioning functionality has been built to permit a staggered implementation. You should only run the scripts for the products which you have licensed at your institution. These scripts reference the login.sql file in the install directory which was modified as necessary in Step 3.3, “Modify login.sql for ODS database”. 3.11.1. Access the ODS_HOME/banner/install directory. 3.11.2. Run the following script if you have licensed Banner Finance. sqlplus /nolog @ods_partitioning_finance.sql 3.11.3. Review ods_partitioning_finance.lst 3.11.4. Run the following script if you have licensed Banner Human Resources. sqlplus /nolog @ods_partitioning_hr.sql 3.11.5. Review ods_partitioning_hr.lst 3.11.6. Run the following script if you have licensed Banner Student. sqlplus /nolog @ods_partitioning_student.sql 3.11.7. Review ods_partitioning_student.lst August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation 1-23 OWB Installation Steps 3.11.8. Follow the instructions in Step 3.2, “OWB Repository Installation” to properly configure and source the params.tcl file and initialize OMB*Plus. 3.11.9. Start OMB*Plus and navigate to the ods/owb subdirectory within the OMB interface OMB+> cd /u01/sghe/ods/ ods/owb Or OMB+> cd D:/sghe/ods/ods/owb 3.11.10. Source the params.tcl file and source each of the following tcl files to start the import and deploy process for the new partitioned mappings: OMB+> source params.tcl OMB+> source finance_partitioning.tcl OMB+> source hr_partitioning.tcl OMB+> source student_partitioning.tcl 1-24 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation August 2010 3.11.11. Verify the deploy results of the following mappings using the Deployment Manager within the OWB client or the Runtime Audit Browser web site. LOAD_MFT_TRANS_HISTORY_1_PART LOAD_MFT_TRANS_HISTORY_2_PART LOAD_MFT_TRANS_HISTORY_3_PART LOAD_MFT_TRANS_HISTORY_4_PART LOAD_MFT_TRANS_HISTORY_5_PART LOAD_MPT_PAYROLL_DIST_PART1 LOAD_MPT_PAYROLL_DIST_PART2 LOAD_MPT_PAYROLL_DIST_PART3 LOAD_MPT_PAYROLL_DIST_PART4 LOAD_MPT_PAYROLL_DIST_PART5 LOAD_MST_STUDENT_COURSE_PART1 LOAD_MST_STUDENT_COURSE_PART2 LOAD_MST_STUDENT_COURSE_PART3 LOAD_MST_STUDENT_COURSE_PART4 LOAD_MST_STUDENT_COURSE_PART5 Step 4 4.1. Configure the ODS 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, and 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. If performing the install on the web server machine (that is, the web server is on the same machine as the ODS), simply copy all of the subdirectories in the web_files folder to the DAD document root. If using a file transfer protocol to copy the files to another machine, create each of the subdirectories off the document root and then copy the files as follows: August 2010 Folder Description Transfer Instructions css CSS Files used for web settings Copy all files in ASCII Mode gengifs WebTailor Graphics Files Copy all files in Binary Mode Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation 1-25 Folder Description Transfer Instructions iagifs IA Admin Graphics Copy all files in Binary Mode iahelp IA Admin Help Files Copy all html, .css and .js files in ASCII mode. Copy pdf and graphics files in Binary mode. iajs IA Admin javascript files Copy all files in ASCII Mode metadata IA Admin Metadata Folder Copy all files in ASCII Mode. Copy all files in subdirectory, bcreps in Binary mode. wtlgifs WebTailor Graphics Files Copy all files in Binary mode wtlhelp WebTailor Help Files Copy all files in ASCII mode ssrhelp Self Service Reporting Help Files Copy all html, .css and .js files in ASCII mode. Copy pdf and graphics files in Binary mode. 4.2. Configure Web Server for Administrative User Interface This step describes one method of configuring your application server. Depending upon the version of the Oracle Application Server used at your institution and how you typically configure your app. Server, this step may be different. The setup and configuration of a data access descriptor (DAD) is detailed in this step. As part of installation step 3.4, a www_user schema was created. This user does not own any objects and was only setup with limited system and object privileges in order to connect to the database for Admin UI functionality. The www_user account will be used to setup communication between your application server and the ODS database. Refer to your Oracle 1-26 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation August 2010 Application Server for information on setting up a DAD. The following is an example DAD configuration using www_user for database access: <Location /ods> SetHandler pls_handler Order deny,allow Allow from all AllowOverride None PlsqlDatabaseUsername www_user PlsqlDatabasePassword u_pick_it PlsqlDocumentTablename IA_ADMIN.MGBDOCS PlsqlDatabaseConnectString myodsserver:1521:ODS SIDFormat </Location> Note The PlsqlDocumentTablename directive is required to import jobs from the Administrative UI. The table (IA_ADMIN.MGBDOCS) is delivered with the software and tells the Oracle Application Server modplsql engine where to store multi-part file uploads (the CSV file that is uploaded as part of the Import feature for an IA_ADMIN job.) After setting up your web server, you can access the Administration User Interface using the following URL as a reference, assuming your web server is configured to listen on port 7777: http://yourwebserver.yourdomain.com:7777/ods/twbkwbis.P_wwwlogin When first presented with a login page, the default User ID delivered is install and the PIN is 111111. 4.3. Configure and Run Metadata Publishing Process The metadata reports, which list the various data elements used in the ODS are available as static HTML pages within the Administrative UI. These metadata reports must be ‘published’ from data stored and maintained in metadata tables under the IA_ADMIN schema. The following configuration steps must be performed prior to publishing the metadata pages: • The UTL_FILE_DIR database init parameter must be explicitly setup and set to a ‘writable’ location on your database server. The metadata publish process will reference and write to the UTL_FILE_DIR location. • There are two ODS parameters which must be modified from within the Admin UI. From the main menu of the Admin 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 PUBLISH_LOCATION parameter August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation 1-27 must be set to your UTL_FILE_DIR location in order to publish properly. The 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. Example If you transfer the published metadata pages to a directory called metadata/ ODS under your web server’s document root, you would specify the parameter value as /metadata/ODS. There is a “metadata” directory delivered with the ODS source code which is transferred to your web server document root in Step 4.2. This directory does not contain any files, but does contain a subdirectory called ‘bcreps’. This subdirectory contains the Business Concept reports and is a referenced component of the metadata deliverables. If you do not transfer and store your published metadata reports under a metadata subdirectory on your web server, ensure you copy the bcreps directory to your metadata file location. When properly configured, following the steps above, meta data can be published from within the Administrative UI. There are three ways to publish meta data. The first way is to publish all meta data for ODS 4.3.1. From within the Administration UI, click Options 4.3.2. Click Schedule a Process. 4.3.3. Click Publish Meta Data Reports. The next two ways to publish meta data can be accomplished from the Maintain ODS Meta data Page. From here, the metadata can be published either for an entire subject area (Student, Finance, etc.) or for a particular source or target by clicking the Publish button. The publish operation can take some time if you’re running multiple systems at once. Once finished, the published html files must be transferred to your web server. 4.4. Load ODS Tables using Administrative User Interface Refer to the Administrative User Interface chapter of the ODS Handbook for information and detailed instructions on loading the ODS using the Administrative UI web site. 4.5. Run ODS Checks and Balances and Reconcile Processes After the upgrade process is complete, you should run the following processes from the ODS Administrative User Interface to verify the state of the ODS. • Checks And Balances Process Validates various internal aspects of the ODS instance. 1-28 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation August 2010 • Reconcile Processes Validates that the ODS composite table data matches the composite view data in Banner Refer to the Administrative User Interface chapter of the ODS Handbook for more information about these processes. 4.6. Run update_recsearchconds.sql script to update the recommended search conditions The ODS metadata uses the delivered indexes when documenting the Recommended Search Columns. The script update_recsearchconds.sql (in the dbscripts/utility_scripts directory) is used to generate that information based on the actual indexes in the database. If additional local indexes are added, it is recommended that this script is rerun (from the IA_ADMIN account) so the list of Recommended Search Columns accurately reflects the database. Step 5 Install Reporting Tools Refer to other chapters of this guide for instructions on installing Oracle Discoverer, Cognos ReportNet, and Self-Service Reporting. August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation 1-29 1-30 Banner Operational Data Store 8.2 Installation Guide Banner Operational Data Store Installation August 2010 2 Banner Self-Service Reporting Installation Prerequisites • Banner ODS version: 8.2 • Oracle Application Express (APEX) version: 3.1.2 Note SunGard supports the same minimum browser levels that are supported by APEX. These levels may change with each APEX release. For the minimum browser levels supported by the version of APEX that you installed, see the Oracle Application Express User’s Guide. SSR Installation Process Step 1 Create the SSRMGR schema and its objects SSR is an optional module of the Banner ODS and it has its own install script, ssr_install.sql. Run the ssr_install script. This will create the SSRMGR schema and all of the SSRMGR objects required for SSR. Step 2 Create an APEX workspace named “SSR” Login to APEX as an administrator using the URL format: http://hostname:port/pls/ database_access_descriptor/f?p=4550:10 hostname is the name of the system where Oracle HTTP Server is installed. port is the is the port number assigned to Oracle HTTP Server. In a default installation, this number is 7777. For more information, see “Accessing the Oracle Application Express Login Page” in the APEX Installation Guide. database_access_descriptor describes how Oracle HTTP Server connects to the database server so that it can fulfill an HTTP request. The default value is apex. f?p=4550 is the application that you are logging into. Application 4550 is the built-in administrative application that is delivered with Application Express. It contains the pages used by an APEX Administrator and the pages used by an APEX Workspace Administrator. An APEX Administrator maintains APEX at the workspace level. There are several tasks that both an APEX Administrator and an APEX Workspace August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation 2-1 Administrator can perform, but only an APEX Administrator can create, maintain, and delete workspaces. An APEX Workspace Administrator maintains a specific APEX workspace and the applications it contains. SSR is an example of an APEX application. To access the APEX Administrator pages, you request the administrator login page, which is page 10. This is the “:10” at the end of the URL above. Later in the SSR install, after you have created a new workspace for SSR, you will need to login as an APEX Workspace Administrator. The Workspace Administrator URL is identical to the administrator URL except for the login page number, which is page 1. After you have logged in, you should see four options: • Manage Service • Manage Workspaces • Manage Applications • Monitor Activity 2.1. From the Manage Workspaces drop-down list, select Manage Workspaces. 2.2. From the Manage Workspaces menu, click Create Workspace. 2.3. Type SSR in the Workspace Name field. 2.4. (optional) Type a description in the Workspace Description field. 2.5. Click Next. 2.6. From the Re-use existing schema drop-down list, select Yes. 2.7. Type SSRMGR in the Schema Name field. 2.8. Click Next. 2.9. Type the administrator’s username, password, first name (optional), last name (optional), and e-mail address in the corresponding fields. 2.10. Select Next. 2.11. After you confirm your request to create a workspace, you will see a message indicating that the workspace was successfully provisioned. 2.12. Select Done. Step 3 2-2 Add Schema Assignments 3.1. Click the Manage Workspaces icon from the Home menu. 3.2. From the Manage Workspaces menu, select Manage Workspace to Schema Assignments. Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation August 2010 3.3. Click Create. 3.4. Click Existing from the radio group. 3.5. Click Next. 3.6. Select SSR from the Workspace drop-down list. 3.7. Click Next. 3.8. Select ODSMGR from the Schema drop-down list. 3.9. Click Next. 3.10. On the subsequent Confirmation page, select the Add Schema button. 3.11. Repeat the previous steps, beginning with step 3.1, to add the IA_ADMIN schema and the ODSLOV schema. Step 4 4.1. Import and Install the SSR Application into the SSR Workspace Login to APEX as a Workspace Administrator using the URL format: http://hostname:port/pls/database_access_descriptor/f?p=4550:1 • hostname The name of the system where Oracle HTTP Server is installed. • port The port number assigned to Oracle HTTP Server. In a default installation, this number is 7777. For more information, see “Accessing the Oracle Application Express Login Page” in the APEX Installation Guide. • database_access_descriptor Describes how Oracle HTTP Server connects to the database server so that it can fulfill an HTTP request. The default value is apex. The remainder of the URL indicates to display the login page for a Workspace Administrator. You will now be presented with the APEX Login page. 4.2. Type SSR in the Workspace field, then type the administrator ID and password. 4.3. Click Login. 4.4. Three icon options will display at the top of the page: • Application Builder • SQL Workshop • Utilities August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation 2-3 4.5. Click Application Builder. 4.6. Select View Applications from the drop-down list. 4.7. Click Import. 4.8. Use the Browse button to locate the f101.sql file in the ssr/web_files install directory. 4.9. Select Application, Page or Component Export from the File Type drop-down list. 4.10. Select Unicode UTF-8 from the File Character Set drop-down list. This will begin the process to import the SSR application into the SSR workspace Export Repository. 4.11. After you see the Successfully Import File dialog box, click Next. 4.12. On the Install Application page, select SSRMGR from the Parse As Schema drop-down list. 4.13. Select Run and Build Application from the Build Status drop-down list. 4.14. Select Reuse Application ID 101 From Export File from the Install As Application radio group. Warning For “Install As Application”, be sure to select “Reuse Application ID 101 From Export File,” otherwise the URL to invoke SSR (described in the section “Publish the SSR End User URL” on page 2-10) will not be valid. 4.15. Click Install. 4.16. If the application installs successfully, click the Edit Application icon from the top page that displays. Step 5 Import the SSR Graphic Files SSR incorporates a number of graphic and static files which must also be imported. 2-4 5.1. Click the Shared Components icon. 5.2. Select Files from the drop-down list. 5.3. Select Images from the drop-down list. 5.4. On the next page select Create. 5.5. On the Create Image page, select No Application Associated from the Application drop-down list. Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation August 2010 5.6. From the Upload New Image field, click the Browse button to locate the email.gif file in the ssr/web_files install directory 5.7. Click Upload. Repeat the Image Upload process, beginning with step 5.4 above, for each of the graphic files (*.gif, *.jpg, and *.png) in the ssr/web_files directory/folder. Step 6 6.1. From the Images page, select Application 101 from the breadcrumb menu. 6.1. Click the Shared Components icon. 6.2. Select Files from the drop-down list. 6.3. Select Static Files from the drop-down list. 6.4. Click Create. 6.5. From the Create Static File page select No Application Associated from the Application drop-down list. 6.6. Click Browse to locate the scj_common.js in the ssr/web_files install directory. 6.7. Click Upload. Step 7 August 2010 Import the SSR JavaScript File Import the SSR Style Sheet Files 7.1. From the Images page, select Application 101 from the breadcrumb menu. 7.2. Click the Shared Components icon. 7.3. Select Files from the drop-down list. 7.4. Select Cascading Style Sheets from the drop-down list. 7.5. Click Create. 7.6. From the Create Cascading Style Sheet page, click Browse to locate the theme_V2.css file in the ssr/web_files install directory. 7.7. Click Upload. 7.8. On the next page select the “Create” button. On the “Create Cascading Style Sheet” page, use the Browse button to locate the scc_common.css file in the ssr/web_files install directory. Select “Upload”. Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation 2-5 Step 8 Customize Parameters There are three Banner ODS parameters defined in the Administrative User Interface. These parameters are delivered with default values that need to be customized for your environment. • ODS ADMIN – APP SERVER DAD Used by SSR to retrieve the SSR help files. • ODS ADMIN – WEB SERVER Used to retrieve the Banner ODS meta data for online help. • SHOW SQL ACCESS POLICY Used to set the policy for access to the SSR Show SQL feature. To Enter the Name of the Application Server DAD 1. Login to the Administrative User Interface. 2. From the Main menu, select Options. 3. Click Set Up Parameters. 4. Set the Internal Group to SSR CONFIGURATION. 5. Set the Internal Code 1 to ODS ADMIN – APP SERVER DAD. 6. Click Search. 7. Click the link in the Description column. The Update a Parameter page opens. 8. In the Description field, enter the Database Access Descriptor (DAD) that you defined for the Administrative User Interface. 9. Click Save. To Enter the URL of the Administrative Web Server 1. Login to the Administrative User Interface. 2. From the Main Menu, select Options. 3. Click Set Up Parameters. 4. Set the Internal Group to SSR CONFIGURATION. 2-6 Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation August 2010 5. Set the Internal Code 1 to ODS ADMIN – WEB SERVER. 6. Click Search. 7. Click the link in the Description column. The Update a Parameter page opens. 8. In the Description field, enter the URL for the Administrative User Interface in the format http://hostname:port (with no trailing slash character). 9. Click Save. To Set Up Access to the SSR Show SQL Function The SSR Show SQL parameters control who can access the Show SQL button, on the Search Criteria or Detail Report pages. Access can be granted or denied as a group or on an individual basis. You can grant access for all users or for individual users. See Step , “Set Up Your Show SQL Access Policy for All Users”,below, for more information. To grant access to individual users, you need to determine if you have more users who should have access or more users who should not have access. To grant access on an individual basis, see “Set up Access for Individual Users” for additional information. Set Up Your Show SQL Access Policy for All Users 1. From the Main Menu, select Options. 2. Click Set Up Parameters. 3. Set the Internal Group to SSR CONFIGURATION. 4. Set Internal Code 1 to SHOW SQL ACCESS POLICY. 5. Click the Description column. The Update a Parameter page opens. 6. Determine if you have fewer users who should have access or fewer users who should not have access. If you have fewer users who should have access, set the External Code field to DENY. If you have fewer users who should not have access, set the External Code field to ALLOW. ALLOW is the default. The next step will explain how to set up individual user exceptions to your Show SQL Access policy. August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation 2-7 Set Up Access for Individual Users If you set your Policy above to DENY, you will be entering new parameters, one for each user who is the exception to your policy, i.e., users who should have access to the Show SQL function. If you set your Policy above to ALLOW, you will be entering new parameters, one for each user who is the exception to your policy, i.e., users who should not have access to the Show SQL function. 1. From the Main Menu, select Options. 2. Click Set Up Parameters. 3. Click Create. The Create a New Parameter page appears. 4. Set the Internal Group to SSR CONFIGURATION. 5. Set the Internal Code1 value to SHOW SQL ACCESS. 6. Enter ALLOW or DENY in the External Code. 7. Enter a User ID in the Description field. 8. Repeat as needed to create a new exception parameter for each user. Install SSR Online Help SSR includes online help for every SSR Web page and for each SSR template. SSR assumes that the location of these help files is in a folder/directory called “ssrhelp” on the Web server where you have installed the Administrative User Interface. SSR uses the URL you entered in the “Customize Parameters” step for “ODS ADMIN – WEB SERVER” to create the help URL as: http://hostname:port/ssrhelp/ Create the ssrhelp folder/directory under the document root of your web server instance and copy into it all of the files/folders from the ssr/web_files/help install folder. Security SSR is delivered with two authentication methods: 2-8 Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation August 2010 • Oracle User Accounts This is the default method for SSR. • Application Express User Accounts This method uses Application Express User Accounts which are created and maintained either through the APEX Administrator interface or the APEX Workspace Administrator interface. If you choose to use Application Express User Account security or some other authentication method, see the section below called “Alternative Security” in the Optional Steps portion of this guide. The following scripts are delivered with SSR in the ssr/security install directory and can be used to implement Oracle User Account authentication as well as SSR Report Template authorization: • createSSRUser.sql • createSSRusers-sample.sql • ssr_user_grants.sql • Separate grant scripts for each SSR Report Template Use these scripts while completing the following installation steps: Oracle User Account Authentication Depending on your installation of Application Express, see the Oracle Application Express Installation Guide under either the section called “Configuring Oracle HTTP Server When Upgrading” or “Configuring Oracle HTTP Server in a New Installation”. Modify the APEX DAD to use a blank database login userID and password. This will enable users to receive a DAD login challenge which will prompt them for their Oracle userID and password. You can use the createSSRUser.sql script in the ssr/security install directory to create your Oracle User Accounts. Oracle User Account Authorization Once you have created Oracle User Accounts for user authentication, you now need to complete the security setup process by authorizing each user to access selected SSR Report Templates. The scripts noted above can be used to issue the grants that are required by an end user to gain access to specific SSR Report Templates. August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation 2-9 Example An end user could be authorized to access the General Ledger or Operating Ledger Report Templates in the SSR Finance area but not authorized to access Report Templates in the Accounts Receivable, Advancement, Human Resources, Financial Aid, and Student areas. Having modified the APEX DAD to blank out the username and password parameters, whenever you login to APEX you will now receive a login challenge from the APEX DAD. Answer the challenge using the IA_ADMIN userID and password. Since Banner ODS delivers the IA_ADMIN user with full DBA grants, you should answer the APEX DAD challenge as the IA_ADMIN user for the remainder of the SSR install and whenever you are performing maintenance on or upgrading SSR. Publish the SSR End User URL For your end users to access SSR, they will need to use a URL which is similar to the ones you created for your APEX Administrator and APEX Workspace Administrator URLs. The only difference is the application and page number at the end of the URL. This will direct them to application 101, page 1. They will see only the application itself, without the developer toolbar links that you can access from the bottom of each SSR page when logged in as an APEX SSR Workspace Administrator. http://hostname:port/pls/database_access_descriptor/f?p=101:1 For more information regarding application deployment, see the “Oracle Application Express Developer’s Guide”. Self-Service Reporting Installation – Optional Steps All of the following steps can be configured post-install if desired. Alternative Security As discussed previously, the default SSR authentication method is Oracle User Accounts. SSR is delivered with an alternate authentication method option which utilizes Application Express User Accounts. These accounts are created and maintained by an APEX Administrator or an APEX SSR Workspace Administrator. APEX also supports various other authentication methods, including SSO and LDAP. If you choose to authenticate using Application Express User Accounts, complete the following steps. Otherwise, if you choose to authenticate using a method other than Oracle User Accounts or Application Express User Accounts, see the Oracle Application Express Developer’s Guide for more information about your options for authentication methods. 2-10 Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation August 2010 Application Express User Account Security Change the Authentication Scheme: Since SSR is delivered with Oracle User Account authentication as the default, the Authentication Scheme is delivered with a value of “DATABASE”. Modify the Authentication Scheme to activate Application Express Authentication: 1. Login to APEX as an SSR Workspace Administrator. 2. Select Application Builder. 3. Select the SSR application. 4. Select Edit Attributes. 5. Select Security. 6. Click the Define Authentication Schemes in the Authentication attribute section. You should see two schemes icons: • Application Express • DATABASE, The Database option should indicate that it is the current scheme. 7. Select the Change Current link under Tasks section on the right side of the page. 8. Select Application Express from the Available Authentication Schemes drop-down list. 9. Select Next. 10. To confirm your selection, select Make Current. Application Express User Account Authentication You can set up user accounts one of two ways: “Create a user account through the APEX Administrator interface” on page 2-11 or “Create a user account through the APEX Workspace Administrator interface” on page 2-12. Create a user account through the APEX Administrator interface 1. Login to APEX as an APEX Administrator. 2. Select Manage Workspaces. August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation 2-11 3. Select Manage Developers and Users. 4. Select Create. 5. Enter the required information. 6. Click either Create or Create and Create Another. Create a user account through the APEX Workspace Administrator interface 1. Login to APEX as an SSR Workspace Administrator. 2. On the Home page, select the Manage Application Express Users link in the Administration box on the right side of the page. 3. Click Create End User. 4. Enter all the information on the page except for the section entitled “User Groups.” 5. Select Create or Create and Create Another. Create User Groups Authorization is accomplished by assigning end users to User Groups. Create a User Group for each SSR Report Template: 1. Login to APEX as an SSR Workspace Administrator. 2. On the Home page, select the Manage Application Express Users link in the Administration box on the right side of the page. 3. Select Create Group and create a group for each of the following Report Templates. Be sure to enter each name exactly as listed here: • Admissions Application • Advancement Person • Advisor Student Listing • Employee • Enrolled Students • Financial Aid Awards • General Ledger • Operating Ledger • Receivable Customer 2-12 Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation August 2010 Application Express User Account Authorization Follow the steps below to assign end users to SSR User Groups: 1. Login to APEX as an SSR Workspace Administrator. 2. On the Home page, select the Manage Application Express Users link in the Administration box on the right side of the page. 3. Select Existing Users. 4. Select a user from the list. 5. Under User Groups, select the appropriate User Groups for that user. 6. Click Apply Changes. Note Be certain to assign all User Groups to all users who are listed as Developers and/or Workspace Administrators. Change the Authentication Scheme application item An APEX application item, or global variable, called “F1_SECURITY_TYPE” has been created to direct the SSR permissions function, SCK_COMMON.F_getSSRPermissions, to use either Oracle User Account Security or Application Express User Account Security. To change the value of this item: 1. From the SSR Workspace Administrator Home page, select Application Builder. 2. Select the SSR application. 3. Select Shared Components. 4. In the section called Logic, select Application Items. 5. At the bottom of the page, click the arrow next to Existing Application Level Computations. That will display the list of application items. 6. Select the Edit icon in column 1 to edit F1_SECURITY_TYPE. 7. In the Computation section, change ORACLE to APEX and select Apply Changes. Email SSR has an email capability. In order to use it, APEX must be configured to send email. Refer to the Oracle Application Express Install Guide for instructions. APEX sends email August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation 2-13 by calling the PL/SQL APEX_MAIL package which is built on top of the Oracle supplied UTL_SMTP package. Therefore, the UTL_SMTP package must be installed and functioning. See Oracle Database PL/SQL Packages and Types Reference for more information about the UTL_SMTP package and “APEX_MAIL” on page 15-32. Modify Email Sender’s Name For those SSR templates which enable users to send e-mail to all persons or organizations who are selected via an SSR query, the e-mail sender’s name is delivered as “SSR Reporting”. This is a global value used by all SSR templates that include e-mail capability. To modify this value: 1. Login to APEX as an SSR Workspace Administrator. 2. Click Application Builder. 3. Click the SSR application icon. 4. Click Edit Attributes. 5. Click Definition. 6. Navigate to the Substitutions section. Modify the Substitution Value for EMAIL_FROM. Set Default Lines Per Page SSR creates online reports which, depending on the selection criteria chosen, can be very large. The default lines per page for SSR is 100. To determine whether this default is appropriate for your site, consider the following. The smaller you set this value, the faster the report page will load. However, this will produce more pages through which the end user will need to navigate. The larger you set this value, the slower the page will load for larger reports. But this will create fewer pages to be navigated. To modify the default value: 1. Login to APEX as an SSR Workspace Administrator. 2. Start up SSR by selecting the run application icon. This will place you on the SSR Main Menu, page 1. 3. At the bottom of the page click Edit Page 1. 4. In the Page Rendering column, scroll down to the bottom of the page. Under Computations click F1_LINE_COUNT_DEFAULT. 2-14 Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation August 2010 5. In the Source attribute you will see the default value of 100. Change that to your desired value 6. Click Apply Changes at the top of the page. SSR includes the capability for each end user to alter the default value for each report template on the report page. The user’s selection remains active throughout their SSR session or until they return to the SSR main menu at which time all user-defined preferences are initialized to the system defaults. Control Access to Population Selection Population Selection is built into several SSR templates and allows users to save the IDs (PIDMs) and, depending on the template, Academic Period for the persons or organizations selected by SSR queries. These groups of IDs can then be used as input to create other reports. Population Selection data is stored in tables owned by SSRMGR and, depending on the number and size of the populations saved, the amount of data stored in these tables can be significant. SSR is delivered with the Banner ODS Population Selection feature enabled. If you want to enable all SSR users to create Banner ODS population selections, you do not need to modify the system default. If you wish to turn this feature off: 1. Login to APEX as an SSR Workspace Administrator. 2. Start up SSR by selecting the run application icon. This will place you on the SSR main menu, page1. 1. At the bottom of the page click Edit Page 1. 2. Under Computations click F1_POP_SEL_AVAILABLE. 3. Change the default value located in the Source attribute from Y to N. Set Up a Second SSR Environment In addition to many of the Banner ODS objects owned by ODSMGR, SSR also accesses numerous SSR-specific tables, sequences, and packages owned by SSRMGR as well as the LOVFUNC package and numerous list of value views owned by ODSLOV that are used to populate the Lists of Values (LOVs) used on the SSR search criteria pages. If you are creating a second SSR environment by installing SSR into a second database, you can run the SSR install process without changes. However, if you plan to create a second SSR environment in a database where another SSR environment has been installed, you will need to create the database objects in different schemas (for example, August 2010 Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation 2-15 SSRMGR_TEST instead of SSRMGR) or in the same schemas but with different object names. Create the Database Objects in Different Schemas You will first need to determine which schemas to duplicate. For example, if you plan to access the same ODS data as the primary environment, you may want to use the same ODSMGR schema for both environments. You may also want to use the same ODSLOV.LOVFUNC package and the same ODSLOV.LOV_* objects. At a minimum, you will need to create a separate SSRMGR schema for the second environment, as SSRMGR contains those objects that are specific to SSR. 1. Review ssr_install.sql in the ods/install directory to determine which scripts you will need to modify with the new schema names. 2. Review the SSR installation instructions for the steps required to create and populate an APEX workspace for your second environment. Create the APEX workspace for your second environment and then complete the remaining SSR install steps. Create Database Objects in Same Schemas with Different Object Names 1. Review ssr_install.sql in the ods/install directory to determine which scripts you will need to modify with the new object names. 2. Review the SSR installation instructions for the steps required to create and populate an APEX workspace for your second environment. The primary parsing schema will need to be the name of your new SSRMGR test schema. 2-16 Banner Operational Data Store 8.2 Installation Guide Banner Self-Service Reporting Installation August 2010 3 Oracle Discoverer Installation This section outlines the steps required to import and configure the Banner ODS Discoverer content into Oracle Discoverer. Oracle Discoverer End User Layer The Oracle Discoverer End User Layer for the Banner ODS provides a fully integrated, web-based reporting solution against the reporting views. The Business Concepts necessary to create and run Discoverer reports have been included as part of the installation and have been constructed at the product level. Prerequisites The following prerequisites must be met prior to configuring and running the reports included with this delivery: • Oracle Database 10g Enterprise Edition Release 10.2.0.3.0. • Oracle Discoverer Plus and Viewer have been configured and tested according to the Installation Documentation. • Oracle Discoverer Administrator and Desktop Clients, included with the Oracle 10g Enterprise Edition Release have been installed for use by the Discoverer Administrator. This step is required for initial configuration of the Discoverer reports included. • An End-User Layer (EUL) has been built on the ODS instance, specifically for institutional reporting using the Banner ODS Reporting views. The product level business areas are included with this distribution for inclusion into this EUL. • You have verified that your environment meets the following minimum product release levels: Oracle 10g Enterprise Edition - Release2 (10.2.0.3.0) Oracle Discoverer Plus and Viewer – 10.1.2 Oracle Discoverer Desktop and Admin – 10.1.2.1 **These versions are the base release levels included with Oracle 10gEnterprise Edition Release 10.2.0.3.0. August 2010 Banner Operational Data Store 8.2 Installation Guide Oracle Discoverer Installation 3-1 Distribution Contents The Banner ODS 3.1 release brought about significant modifications to the structure of the business areas in the new EUL. It was designed to mimic the Business Concepts that were delivered in the Cognos Framework Model in the Banner ODS 3.0 release. The new style EUL contains 68 organized Business Concepts which will help users identify which reporting views to use when trying to write a report in a certain business area. A number of other enhancements were also incorporated into this new EUL based on client feedback to help make their Discoverer report writing experience as easy as possible. The older style EUL delivered in Banner ODS 2.0 up to Banner ODS 3.0 was also delivered for Banner ODS 3.1 and 8.0. However, it will no longer continue to be delivered starting in ODS 8.1. You may continue to use this older style EUL by refreshing the model after the ODS upgrade has been completed. Once the model has been refreshed, you will be able to bring any new items into the EUL and can join them to any of the ODS reporting objects that currently reside in your EUL. Oracle Discoverer provides several different methods of publishing reports to end users. The reports can be imported into the database or a shared file-system containing the report files can be utilized. This distribution includes methods of configuring either option. Configuration Steps 1. Install the Product Business Areas into the ODS End-User Layer using the import feature of the Desktop Administrator. The name of each business area export file is ODS_Discoverer_business_areas.eex. The import feature can be found in the file menu within Discoverer Administrator. The Business Areas can be imported into the existing EUL schema or can be managed separately, provided the Business Area schema had full access to the EUL. 2. Verify there were no errors during the import and ensure the EUL is valid before proceeding. It is recommended that individual accounts are given access to the Business Areas contained within. The ODS Security functionality is enforced within the Discoverer Reports. The End User Layer schema should never be used for reporting use within the Discoverer applications. A default EUL can also be assigned to each Discoverer User. Note The ODS Reporting Views, Composite Tables, and ODSLOV views need to be granted access to the new EUL schema. Run the following script (in 3-2 Banner Operational Data Store 8.2 Installation Guide Oracle Discoverer Installation August 2010 the ods\ods8.1\ods\install directory in your ODSMGR schema of your ODS: @grants_for_odsmgr_reporting.sql @grants_for_odslov_reporting.sql @grants_for_odslov_objects.sql Installation Instructions This section outlines the steps required to import the Banner ODS Discoverer content into Oracle Discoverer. 1. Import the appropriate .eex file into Discoverer Administrator. 1.1. Click File. 1.2. Click Import. 1.3. Click Add File. 1.4. Select the ODS_Discoverer_business_areas.eex. 2. Click Next. 3. You will be prompted to answer three questions. Select the following radio buttons: • Refresh the Object This brings in any changes from the new EUL without creating any duplicate objects. Check the Preserve display related properties, to ensure that all custom property changes made by a site will not be overridden by the property settings in the new EUL. • By Identifier This will match the items from the existing EUL to the new EUL by the database identifier instead of by the display name. Clients are encouraged to change the name of columns in their EUL to meet their reporting needs. By matching on identifier, this enables updates to be made without creating duplicate folders. • Always Take Ownership of Imported Workbooks 4. Click Next. 5. Click Start. 6. Click Finish when the import is 100% complete. August 2010 Banner Operational Data Store 8.2 Installation Guide Oracle Discoverer Installation 3-3 7. Select the Validate Folders option under the View menu item. This will ensure that all of the folders in each of the Business areas are valid. If there are folders that are not valid, a refresh of the EUL may be necessary. 8. 3-4 To ensure that your EUL and ODS database are synchronized, you can perform a refresh. You should perform the refresh on each of the Business Areas. This can be found under the File menu. If there are items that need to be refreshed, click the Impact button to ensure that no workbooks or joins are affected by the refresh. Banner Operational Data Store 8.2 Installation Guide Oracle Discoverer Installation August 2010 4 Cognos Business Intelligence 8 Installation Prerequisite Task Before you import the Banner ODS deployment archive into Cognos Connection, be sure that the following folder is present on the Cognos server. If it is not there, create it. Public Folders>ODS8.2>Updated Packages Import Banner ODS Deployment Archive (packages) into Cognos Connection 1. Copy the file c8_ods_packages_82.zip into the <Cognos Home>/Deployment directory. (For example, C:\ Program Files\cognos\c8\deployment). 2. Open Cognos Connection. 3. Click the Public Folders tab. 4. Click Content Administration from the Tools drop down list. 5. Click New Import . 6. Click Next. 7. Click the c8_ods_packages_82 radio button. 8. Click Next. 9. Click Next again. 10. Check the first checkbox in the upper left hand corner of the list to select all the objects in the import. 11. Click Next. August 2010 Banner Operational Data Store 8.2 Installation Guide Cognos Business Intelligence 8 Installation 4-1 12. Select the following options for import: 13. Click Next. 14. Click Finish. 15. Click Run. 16. Click OK. 17. After the import runs, navigate to Public Folders. 18. Copy the packages from the Public Folders>ODS8.2> Updated Packages folder into the required folder. 4-2 Banner Operational Data Store 8.2 Installation Guide Cognos Business Intelligence 8 Installation August 2010 Create portal tab for Banner Operational Data Store 1. Page down to Operational Data Store Pages. 2. Click Operational Data Store Pages checkbox. 3. Click the Operational Data Store Reports Portal Page. 4. Click the pencil to edit the Cognos Navigator object. 5. Click the Select a folder… link. 6. Move to the Public Folders until you see the Operational Data Store Reports folder. 7. Click the Operational Data Store Reports radio button. 8. Click OK. The Cognos > Public Folders > Operational Data Store Reports will be the folder now selected for the navigator breadcrumbs. 9. Click OK. You will see the Operational Data Store Reports folder in the navigator breadcrumbs. 10. Click the Add to my portal tabs icon in the upper right hand corner. 11. Click the blue Return arrow icon in the upper right hand corner by the Home icon. 12. Click the Operational Data Store Reports tab. 13. Click the Tab menu in the upper left hand corner. August 2010 Banner Operational Data Store 8.2 Installation Guide Cognos Business Intelligence 8 Installation 4-3 14. Click Modify the sequence… from the drop down list. 15. Click the Operational Data Store Reports tab. 16. Click the To top link at the bottom of the page to move the tab to the top of the list. 17. Click OK. 18. Click the Home Options drop down list. 19. Click Set View as Home. Upgrade Framework Manager Model For those clients who have applied institution-specific changes to their Banner ODS Framework Manager model, we provide the means to upgrade the model without losing these updates. To incorporate the ODS 8.2 enhancements into your data model you may employ one of two methods. You can merge the ODS 8.2 version of the sghe_ods models with your institution’s copy of the ODS 8.1 version of the model. This will apply all baseline changes made to the model since the ODS 8.1 delivery to your institution’s model (assuming there are no conflicting changes.) You can find more detail on how to employ either of the above referenced actions in the “Third Party Reporting Tools” chapter of the Banner Operational Data Store Handbook. 4-4 Banner Operational Data Store 8.2 Installation Guide Cognos Business Intelligence 8 Installation August 2010 Troubleshooting This section describes solutions to issues that may arise during the installation or upgrade of the Banner ODS 8.2. Use the information in this section as a troubleshooting reference while performing the Banner ODS 8.2 installation or upgrade. Issue Category Issue “Administrative UI issues” “Page not enabled for current user role(s) because INSTALL user is missing” T-3 “Checks and Balances” “Error Mapping is INVALID in the database” T-5 “Staging” “Restage an ODS stage table” T-5 “ORA-01422: exact fetch returns more than requested number of rows” T-7 “Error restaging tables; ORA-20000: Retrieving source database link terminated” T-8 “ods_upgrade.sql” “Scripts not connecting correctly” T-9 “[product]_etl_install.sql scripts” “ORA-04045: errors during recompilation/ revalidation” T-10 “ORA-04063: package body "ODSSTG.MGKSTRM" has errors” T-11 “ORA-20000: Adding a table rule terminated” T-14 “ORA-20000: Exporting and importing LONG table data terminated” T-16 “ORA-20000: Preparing to import terminated” T-17 “ORA-20000: Retrieving source database link terminated” T-18 “ORA-20000: Stopping the capture process terminated” T-19 “ORA-26723: user "ODSSTG" requires the role "DBA"” T-19 August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-1 Issue Category Issue “ORA-31685: Object type failed due to insufficient privileges” T-20 “ORA-31693: Table data object failed to load/ unload” T-21 “ORA-31693: Table data object failed to load/ unload” T-22 “ORA-39014: One or more workers have prematurely exited” T-24 “ORA-39083: Object type INDEX_STATISTICS failed” T-25 “ORA-39125: Worker unexpected fatal error” T-26 “Cannot stage table; no matching records in MGBSTRM” T-26 “Installation stops responding” T-27 “[product]_stage.sql” “ORA-20000: Preparing to import terminated” T-28 “gurutlrp.sql script” “ORA-01031: insufficient privileges message Alumni/ODS views invalid” T-29 “OWB* and WB_OLAP* invalid objects” T-31 “UPD_80100* invalid objects” T-32 “UPDATE_MBT* and DELETE_MBT* invalid objects” T-32 “LOAD_MFT_TRANS_HISTORY* invalid objects” T-33 “EDW_ADV_GIFT_EXTR invalid object” T-33 “API2422 Connection details are not set for the metadata location” T-34 “DELETE_MAT_PROSPECT_CONT_EXP package not found” T-34 “Error importing SUPPORTEDLANGUAGE American English” T-35 “OWB issues” T-2 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 Issue Category Issue “ods_repos.tcl fails; ORA-00922: missing or invalid option” T-36 “RTC-5161. Error when trying to deploy the T-37 ODSMGR_LOCATION connector SOURCE_DB” “OMB06312: Cannot modify any properties of a registered location except the password” T-38 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. August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-3 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; T-4 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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. Restage an ODS stage table Related FAQ: 1-C8Y1U1 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. August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-5 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); T-6 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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. August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-7 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 — T-8 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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. August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-9 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. T-10 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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'); August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-11 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 T-12 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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) as defined in the step 1.6 of the Banner ODS 8.2 Upgrade Guide. 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 August 2010 directory. Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-13 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. T-14 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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. August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-15 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. T-16 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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. August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-17 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. T-18 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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: August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-19 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. T-20 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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: August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-21 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: T-22 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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'', '|| August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-23 '''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 T-24 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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 August 2010 128K Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-25 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. T-26 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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. August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-27 [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. T-28 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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. August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-29 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. T-30 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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 August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-31 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. T-32 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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. August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-33 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. T-34 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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. August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-35 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. T-36 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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. August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-37 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. ----------------------------------------- T-38 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010 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. August 2010 Banner Operational Data Store 8.2 Installation Guide Troubleshooting T-39 T-40 Banner Operational Data Store 8.2 Installation Guide Troubleshooting August 2010