| Oracle® Warehouse Builder Installation and Administration Guide, 10g Release 2 (10.2.0.2) for Windows and UNIX Part Number B28224-04 |
|
|
View PDF |
| Oracle® Warehouse Builder Installation and Administration Guide, 10g Release 2 (10.2.0.2) for Windows and UNIX Part Number B28224-04 |
|
|
View PDF |
This chapter contains reference information to use in the event that you encounter errors or problems with your installation. This appendix includes the following topics:
This section includes the following topics:
Not Able to Launch any of the Warehouse Builder clients or other Oracle products
Additional Error Logging for Errors and Other Unexpected Behavior
Warehouse Builder Repository Assistant: OWB_ORACLE_HOME\owb\UnifiedRepos\log_<timestamp>.log
Warehouse Builder Control Center Service: OWB_ORACLE_HOME\owb\log\Repository_Name\log.xx on the Oracle Database server
Warehouse Builder Design Center: Specify the location on the Preferences tab.
If you attempt to launch a Warehouse Builder client such as the Design Center and the splash screen displays momentarily but the client fails to launch, you may have overwritten required java objects during the subsequent of another software product.
If the client is installed on Windows and you launched the client from the Start menu, you may not see any error messages. Manually launch the client by typing at the DOS prompt run <OWB_ORACLE_HOME>\owbclient.bat.
You are likely to encounter an error message such as No fonts were found in '<drive>:\Program Files\ Qarbon\viewlet Builder3jre\lib\fonts'.
If Warehouse Builder appears to be frozen or hanging, perform a stack trace as follows:
At the DOS command prompt, enter: cd OWB_ORACLE_HOME\owb\bin\win32\
Run owbclient.bat.
When the program hangs, press Ctrl+Break.
This produces the thread-dump. This information helpS Oracle Support to identify the problem.
If Warehouse Builder is producing errors or exhibiting other unexpected results, additional error logging can help you or Oracle Support identify the cause.
For additional error logging:
At the command prompt, navigate to:
For Windows: OWB_ORACLE_HOME\owb\bin\win32
For UNIX: OWB_ORACLE_HOME/owb/bin/unix
Run one of the execution files as listed in Table 1-9 and pipe the output to a log file (for example, owbclient.bat > owbclient.log):
Examine the resulting log file.
Use this log when contacting Oracle Support.
To check, verify, or reinstall the Java Virtual Machine (JVM) server in the database, refer to OracleMetaLink:
In your Web browser, go to: http://metalink.oracle.com.
Log in to OracleMetaLink, or register as a new user.
Type the following terms into the Search field (note that they are separated by semicolons): INITJVM.SQL; INSTALL; JAVAVM; JVM; VERIFY; SERVER; INSTALL; CLEANUP
Press Enter.
This search returns the cleanup notes for the JVM. The number of available documents frequently changes because Oracle Support creates, merges, and deletes various cleanup notes. This string of search words will return the most current and pertinent documents.
It is possible that when you install Warehouse Builder Runtime components on an HP-UX operating system, the following error occurs: INS0022: A spawned program error. This may be a database server issue.
To identify the database server issue:
From SQL*Plus, connect to a SYS user.
Create user test_lj identified by test_lj; Grant connect, resource to test_lj;
Create ORACLE_HOME/owb/bin/unix/test.sh with the following contents:
../unix/loadjava -thin -verbose -order -resolve -user 'test_lj/test_lj@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=hpdgpa3)(PORT=1522))(CONNECT_DATA=(SERVICE_NAME=dgpadw)))' ../../lib/int/rtpserver.jar
Change directory to ORACLE_HOME/owb/bin/unix/.
Run test.sh.
This section includes the following topics:
No fonts were found in '<drive>:\Program Files\ Qarbon\viewlet Builder3jre\lib\fonts'
RTC-5301: The Control Center Service is not currently available.
Lineage and impact analysis reports: Extensive tablespace requirements for materialized views.
INS0009: Unable to connect to the database. Verify the connect information.
ORA-12514: TNS: listener could not resolve SERVICE_NAME given in connect descriptor.
PL/SQL: ORA-04052: Error occurred when looking up remote object
SYS user has SYSDBA credentials. You can verify this from SQL*Plus by issuing the following connect statement:
connect sys/<<sys_password>>@TNS_NAME_OF_DB as sysdba;
In a standard database installation, the preceding connect statement works because REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE and the default password file is created by the installation process.
REMOTE_LOGIN_PASSWORDFILE=NONE, then the statement connect sys/<<sys_password>>@TNS_NAME_OF_DB as sysdba; will fail. In this case, you have the following options:
Reconfigure your database with REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE and create a password file if none exists.
If the preceding is not an option, reconfigure your database with O7_DICTIONARY_ACCESSIBILITY=TRUE. With this setting, connect sys/<<sys_password>>@TNS_NAME_OF_DB will work, which enables Warehouse Builder Assistants to connect to SYS user.
reposinst.sh, or an OMB Plus session, OMBPlus.sh, on an AIX computer. This occurs due to the JDK folders having a unique structure on AIX machines.start_service.sql.
If it is not possible to run the service on the server host, then start the Control Center Service on the local computer using the script local_service_login.sh or local_service_login.bat as appropriate. Use this script as follows:
local_service_login.sh [-startup | -closedown] <OWB-Home>
In this mode, the Control Center Service runs on the local computer and is available only when that computer is available and can connect to the Control Center.
Use the script show_service.sql to determine the status of the service.
NAMESPACESERVICEIMPL may be invalid. This occurs after a database export or import from the Warehouse Builder repository schema if the repository owner has no SELECT privilege on SYS.V_$SESSION. You can diagnose the cause as follows:
In SQL*Plus, connect to the Warehouse Builder repository schema.
Enter the following command at the SQL prompt:
ALTER PACKAGE NAMESPACESERVICEIMPL compile body;
If Warning: Package body altered with compilation errors appears, enter the following command at the SQL prompt:
show errors;
The following errors mean that the Warehouse Builder repository owner has no SELECT privilege on SYS.V_$SESSION.
PL/SQL: SQL statement ignored PLS-00201: Identifier 'SYS.V_$SESSION' must be declared
In SQL*Plus, connect as the SYS user.
At the SQL prompt, enter the following command:
grant SELECT on V_$SESSION to Warehouse Builder_Repository_Owner;
Connect to the Repository_Owner.
Enter the following command at the SQL prompt:
alter package NAMESPACESERVICEIMPL compile;
SYS user has SYSDBA credentials. You can verify this from SQL*Plus by issuing the following connect statement: connect sys/sys_password@TNS_NAME_OF_DB as sysdba;
In a standard database installation, the preceding connect statement works because REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE and the default password file is created by the installation process.
If your database is configured with REMOTE_LOGIN_PASSWORDFILE=NONE, then the statement connect sys/sys_password@TNS_NAME_OF_DB as sysdba; will fail. In this case, you have two options.
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE and create a password file if none exists.O7_DICTIONARY_ACCESSIBILITY=TRUE. With this setting, the statement connect sys/sys_password@TNS_NAME_OF_DB will work, which enables the Warehouse Builder Assistants to connect to SYS user.NAS_DATA directory.
From your OWB_ORACLE_HOME, start the Name and Address Server:
For Windows: Run owb\bin\win32\NAStart.bat.
For UNIX: Run owb/bin/unix/NASTART.sh.
Open the log file: owb\bin\admin\NASvr.log.
The log should contain a list of installed countries.
If there is no such list, verify that you have extracted the regional library data to the correct location. If you have extracted the data to the wrong location, you can either reinstall the data, or modify the owb\bin\admin\NameAddr.properties file to indicate the correct file path. If you modify the NameAddr.properties file, stop and restart the Name and Address Server as follows:
For Windows: Start the server by running owb\bin\win32\NAStart.bat. Stop the server by running owb\bin\win32\NAStop.bat.
For UNIX: Start the server by running owb/bin/unix/NAStart.sh. Stop the server by running owb/bin/unix/NAStop.sh.
Once you have verified the installation, you can stop the Name and Address Server if you wish, because it is automatically started at the execution of any mapping that employs the Name and Address operator.
Autoextend On.-mx parameter in the owbclient.bat file. The -Dlimit parameter in the owbclient.bat file specifies the memory threshold (80% of Dlimit) at which OWB memory manager begins to assist Java garbage collection. If you change the -mx parameter value, set the -Dlimit parameter to the same value, or at least to 90% of the value. Note that setting the -Dlimit to a low value can have a negative impact on the performance of Warehouse Builder.-Dlimit parameter in Warehouse Builder as follows:
Exit Warehouse Builder.
Open this file in a text editor:
For Windows: Open the $OWBHOME\bin\win32\ombplus.bat.
For UNIX: Open the $OWBHOME\bin\win32\owbclient.sh.
Change the -Dlimit parameter to 334.
Save and close the file.
Restart Warehouse Builder.
MAX_ENABLED_ROLES parameter, this error occurs.MAX_ENABLED_ROLES parameter in the init.ora file. When you deinstall a repository or a target schema, delete the associated roles as well.SERVICE_NAME is added to the TNSNAMES.ORA as a subclause to the CONNECT_DATA section in the Net Service Name entry. This replaces the (SID=<SIDname>) subclause in the previous versions of Oracle Database8i (8.1.x).TNSNAMES.ORA file as follows:
Use the GLOBAL_DBNAME parameter in the LISTENER.ORA for each SID that you want to identify as a separate service. Use the value of this parameter as the value of the SERVICE_NAME parameter. You will need to activate any changes you make to LISTENER.ORA for this purpose by stopping and restarting the listener process.
Use the values of the parameters existing in the INIT.ORA, namely SERVICE_NAMES and DB_DOMAIN, to determine the value of the SERVICE_NAME that you must use in TNSNAMES.ORA. The valid construction of this value is <SERVICE_NAMES>.<DB_DOMAIN> with the period separating the two INIT.ORA values. If your SERVICE_NAMES is BIKES and your DB_DOMAIN is COM, then your SERVICE_NAME is BIKES.COM.
If there is no DB_DOMAIN parameter set in your INIT.ORA, or if there is no GLOBAL_DBNAME in the LISTENER.ORA, then you can use the SERVICE_NAMES from the INIT.ORA in your TNSNAMES.ORA for the SERVICE_NAME parameter.
For example, if INIT.ORA contains SERVICE_NAMES = "TEST817" and db_domain is not set, then the TNSNAMES.ORA entry is: CONNECT_DATA =(SERVICE_NAME = "TEST817")).
If you have multiple values specified in the SERVICE_NAMES parameter in the init.ora, you can use one of them. If SERVICE_NAMES is not set, then you can use DB_NAME.DB_DOMAIN parameters from the INIT.ORA file.
If SERVICE_NAMES and DB_DOMAIN is not set in the INIT.ORA and there is no GLOBAL_DBNAME in the LISTENER.ORA,then your SERVICE_NAME in TNSNAMES.ORA file is be DB_NAME.
SYS user and entering the following command: SELECT * FROM GLOBAL_NAME; If the Global Name of the old database does not match that of the new database, then a domain mismatch is causing this error.ALTER DATABASE RENAME GLOBAL_NAME TO xxx10G.US.ORACLE.COM; or redeploy your connectors. Refer to the Oracle Warehouse Builder User's Guide for information on deploying connectors.select_catalog_role privilege. If you have the same dimension object defined in multiple Warehouse Builder target schemas, then Oracle Export creates duplicates in the export file, and this error occurs when you import.SYS user to the existing version of the Oracle Database from which you exported the target schemas. Enter the following statement in SQL*Plus: revoke select_catalog_role from OLD_Target_Schema;Export the target schema into an Oracle .DMP file again, and then import the file into Oracle Database 10g.Ensure that ORACLE_HOME and PATH are set correctly in Oracle Database 10g. Your Oracle home directory must to point to the OWB_ORACLE_HOME. Set your PATH variable to include the OWB_ORACLE_HOME\bin directory before any other Oracle products.
Ensure that the TNSNames.ora file is configured correctly:
For Windows: From the Oracle Database 10g program group, start Net Configuration Assistant and select Local Net Service Name Configuration to configure TNSNames.ora.
For UNIX: Set ORACLE_HOME and PATH to the OWB_ORACLE_HOME for Warehouse Builder 10g Release 2 (10.2.0.2), then execute OWB_ORACLE_HOME/bin/netca to start Net Configuration Assistant. Select Local Net Service Name Configuration to configure TNSNames.ora.
sys.dbms_aq.SYS user and run a query to identify which user sessions are pinning the Advanced Queue packages, using the following query as an example:
column s.sid format a5;
column s.serial# format a8;
column s.username format a10;
column objectname format a10;
select distinct
s.sid,
s.serial#,
s.username,
x.kglnaobj as objectname
from
dba_kgllock l,
v$session s,
x$kgllk x
where
l.kgllktype = 'Pin' and
s.saddr = l.kgllkuse and
s.saddr = x.kgllkuse and
x.kglnaobj in ('DBMS_AQ', 'DBMS_AQADM');
The following is an example of the output you receive:
SID SERIAL# USERNAME OBJECTNAME
--- ------- -------- ----------
9 29623 RTU_4942 DBMS_AQ
Noting the SID and Serial Number, issue the following command to kill the user sessions:
ALTER SYSTEM KILL SESSION 'SIDNoted, SerialNumberNoted';
For example, type the following to kill the session listed in the sample output for this error:
ALTER SYSTEM KILL SESSION '9,29623';
|
 Copyright © 2000, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|