C Troubleshooting OracleAS Metadata Repository Creation Assistant

C.1 Unable to Connect to the Database

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:

  1. Rename the file to something else.

  2. Exit OracleAS Metadata Repository Creation Assistant.

  3. Restart OracleAS Metadata Repository Creation Assistant.

  4. Try connecting again.

  5. When OracleAS Metadata Repository Creation Assistant is done, rename the file back.

C.2 Unable to Connect as "sys" User

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:

  1. Rename the file to something else.

  2. Exit OracleAS Metadata Repository Creation Assistant.

  3. Restart OracleAS Metadata Repository Creation Assistant.

  4. Try connecting again.

  5. When OracleAS Metadata Repository Creation Assistant is done, rename the file back.

C.3 No Space

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:

1. Exit OracleAS Metadata Repository Creation Assistant.

2. Add another raw device to the database.

3. Restart OracleAS Metadata Repository Creation Assistant.

If your database uses a file system, perform the following steps:

1. Ensure that the file system has enough disk space.

2. Set tablespaces to AUTOEXTEND.

C.4 Loading Fails on Real Application Clusters Database After Specifying Multiple Nodes

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.

C.5 Manual Steps: Cleaning Up a Failed Registration or Deregistering OracleAS Metadata Repository

This section describes how to clean up registration entries in Oracle Internet Directory without using OracleAS Metadata Repository Creation Assistant.

1. Connect to Oracle Internet Directory using Oracle Directory Manager.

   1. Start up Oracle Directory Manager.

      prompt> $ORACLE_HOME/bin/oidadmin
      
      

   2. In the Connect screen, enter the connect information. Log in as the Oracle Internet Directory superuser (cn=orcladmin).

2. Clean up the database registration entries in Oracle Internet Directory:

   1. Expand the following entries (shown in Figure C-1):

      Entry Management > cn=OracleContext > cn=your_database_name

   2. 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.

   3. Right-click cn=your_database_name and delete it.

   Figure C-1 Clean up Database Registration Entries

   
   Description of "Figure C-1 Clean up Database Registration Entries"
   
   

3. Clean up the metadata repository registration entries in Oracle Internet Directory:

   1. Expand the following entries (shown in Figure C-2):

      Entry Management > cn=OracleContext > cn=Products > cn=IAS > cn=IAS Infrastructure Databases > orclReferenceName=your_database_name

   2. Delete each child entry under orclReferenceName=your_database_name.

   3. Delete the orclReferenceName=your_database_name entry.

   Figure C-2 Clean up Metadata Repository Registration Entries

   
   Description of "Figure C-2 Clean up Metadata Repository Registration Entries"
   
   

C.6 ORA-01403: No Data Found

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.

prompt> unsetenv NLS_LANG
 - or -
prompt> setenv NLS_LANG american_america.us7ascii

You can set NLS_LANG back to its original value after running OracleAS Metadata Repository Creation Assistant.

C.7 ORA-06510: PL/SQL: Unhandled User-Defined Exception

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.

C.8 Need More Help?

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.