Oracle® Application Server Metadata Repository Creation Assistant User's Guide
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium B25336-01 |
|
Previous |
Next |
This appendix describes how to solve common problems that you might encounter when running OracleAS Metadata Repository Creation Assistant. It contains the following sections:
Section D.4, "Loading Fails on Real Application Clusters Database After Specifying Multiple Nodes"
Section D.7, "ORA-06510: PL/SQL: Unhandled User-Defined Exception"
Problem
OracleAS Metadata Repository Creation Assistant is unable to connect to the database
Solution
Check the following:
Make sure you are using correct service name (SID or SID.domainname).
Make sure the database is up.
Make sure the listener is up.
Make sure you have network connectivity to the database.
Check that the glogin.sql
or the login.sql
files, located in the ORACLE_HOME\sqlplus\admin
directory, do not contain user prompt lines, which look like the following:
column db_name new_value db_name noprint select user ||' on ' || name "db_name" from v$database ; set sqlprompt "&db_name> "
If either file contains the user prompt lines:
Rename the file to something else.
Exit OracleAS Metadata Repository Creation Assistant.
Restart OracleAS Metadata Repository Creation Assistant.
Try connecting again.
When OracleAS Metadata Repository Creation Assistant is done, rename the file back.
Problem
You get the following message when running OracleAS Metadata Repository Creation Assistant:
RepCA unable to connect as sys. Error message: *** Specify Database Connect *** ERROR -SQLException on getting SID and SYSTEMNAME informationjava.sql.SQLException: @ ORA-01017 : invalid username/password; logon denied
Solution
Try the following:
Check that you entered the correct password for the "sys" user.
Reset the password for the "sys" user and try again. You can reset the password using the ORACLE_HOME\bin\orapwd
command. See Section 1.5.12, "Password File Authentication", step 1, for details.
Check that the glogin.sql
or the login.sql
files, located in the ORACLE_HOME\sqlplus\admin
directory, do not contain user prompt lines, which look like the following:
column db_name new_value db_name noprint select user ||' on ' || name "db_name" from v$database ; set sqlprompt "&db_name> "
If either file contains these lines:
Rename the file to something else.
Exit OracleAS Metadata Repository Creation Assistant.
Restart OracleAS Metadata Repository Creation Assistant.
Try connecting again.
When OracleAS Metadata Repository Creation Assistant is done, rename the file back.
Problem
You load OracleAS Metadata Repository Creation Assistant in an existing Real Application Clusters database and you get a error.
Solution
If your database uses raw devices, perform the following steps:
Exit OracleAS Metadata Repository Creation Assistant.
Add another raw device to the database.
Restart OracleAS Metadata Repository Creation Assistant.
If your database uses a file system, perform the following steps:
Ensure that the file system has enough disk space.
Set tablespaces to AUTOEXTEND
.
Problem
You load OracleAS Metadata Repository Creation Assistant in an existing Real Application Clusters database and you get a error. On the Specify Database Connection Information screen, you specified multiple nodes of the Real Application Clusters database.
Solution
When you input the nodes of the Real Application Clusters database on the Specify Database Connection Information screen, only specify one node of the database. The Real Application Clusters software will automatically replicate the data loaded by OracleAS Metadata Repository Creation Assistant onto all of the nodes.
This section describes how to clean up registration entries in Oracle Internet Directory without using OracleAS Metadata Repository Creation Assistant.
Connect to Oracle Internet Directory using Oracle Directory Manager.
Start up Oracle Directory Manager.
Select Start > Programs > Oracle - OracleHomeName > Integrated Management Tools > Oracle Directory Manager.
In the Connect screen, enter the connect information. Log in as the Oracle Internet Directory superuser (cn=orcladmin
).
Clean up the database registration entries in Oracle Internet Directory:
Expand the following entries (shown in Figure D-1):
Entry Management > cn=OracleContext > cn=your_database_name
Delete all the child entries under cn=
your_database_name
, starting with the bottom-most child entry.
Before deleting the cn=DESCRIPTION_0
entry, expand it until you reach the last child. Then delete each child starting with the innermost child.
To delete an entry, right-click each child entry and select Delete from the pop-up menu. Click Yes in the Confirmation dialog. When deleting some child entries, you may get some error messages. You can ignore these error messages.
Right-click cn=
your_database_name
and delete it.
Figure D-1 Clean up Database Registration Entries
Clean up the metadata repository registration entries in Oracle Internet Directory:
Expand the following entries (shown in Figure D-2):
Entry Management > cn=OracleContext > cn=Products > cn=IAS > cn=IAS Infrastructure Databases > orclReferenceName=your_database_name
Delete each child entry under orclReferenceName=
your_database_name
.
Delete the orclReferenceName=
your_database_name
entry.
Figure D-2 Clean up Metadata Repository Registration Entries
Problem
When OracleAS Metadata Repository Creation Assistant loads the Workflow schema, it returns a PL/SQL error ORA-01403: "no data found".
Solution
Your NLS_LANG
environment variable is set to a non-English locale. Before you run OracleAS Metadata Repository Creation Assistant, you need to make sure that the NLS_LANG
environment variable is unset or is set to american_america.us7ascii
.
You can set the environment variable using the System Properties dialog box.
You can set NLS_LANG
back to its original value after running OracleAS Metadata Repository Creation Assistant.
After OracleAS Metadata Repository Creation Assistant is loaded, the error ORA-06510: PL/SQL: unhandled user-defined exception" is found in the log file.
This error is caused when the loading scripts for the DSGATEWAY
schema are run. These scripts belong to the OracleAS Syndication product, which is obsoleted. The DSGATEWAY
schema is created for backward compatability.
If this appendix does not solve the problem you encountered, try these other sources:
Oracle Application Server Release Notes, available on the Oracle Technology Network (http://www.oracle.com/technology/documentation
)
OracleMetaLink (http://metalink.oracle.com
)
If you do not find a solution for your problem, open a service request.