Skip Headers
Oracle® Application Server Administrator's Guide
10g Release 2 (10.1.2)
Part No. B13995-01
  Go To Documentation Library
Home		 Go To Product List
Solution Area		 Go To Table Of Contents
Contents		 Go To Index
Index
Previous
Previous 		Next
Next 		 

6 Managing an OracleAS Metadata Repository

This chapter provides information on managing OracleAS Metadata Repository.

It contains the following topics:

6.1 Frequently Asked Questions About OracleAS Metadata Repository

OracleAS Metadata Repository is an Oracle Database 10g database and can be managed using standard database procedures and tools. However, there are some considerations for managing OracleAS Metadata Repository within the Oracle Application Server environment. This section answers frequently asked questions about managing the Metadata Repository.

6.2 Postinstallation Status of Metadata Repository Schemas

Table 6-1 shows the status of Metadata Repository schemas immediately after installation. The table contains the account status and initial password for each schema, depending on whether the Metadata Repository is registered with Oracle Internet Directory.

To unlock an account using SQL*Plus (be sure to set your ORACLE_HOME and ORACLE_SID environment variables before you run these commands): 

ORACLE_HOME/bin/sqlplus "SYS/password_for_sys AS SYSDBA"
SQL> ALTER USER schema ACCOUNT UNLOCK;

To lock an account: 

ORACLE_HOME/bin/sqlplus "SYS/password_for_sys AS SYSDBA"
SQL> ALTER USER schema ACCOUNT LOCK;

The method for changing passwords varies by schema. Refer to Section 6.4, "Changing Oracle Metadata Repository Schema Passwords" to determine the proper way to change a password.

Table 6-1 Postinstallation Status of Schemas in a Metadata Repository

Schema Account Status (Registered with Oracle Internet Directory) Password (Registered with Oracle Internet Directory) Account Status (Not registered with Oracle Internet Directory) Password (Not registered with Oracle Internet Directory)
ANONYMOUS OPEN RANDOM OPEN RANDOM
B2B OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
CTXSYS LOCKED RANDOM LOCKED RANDOM
DBSNMP OPEN Set by user during installation OPEN Set by user during installation
DCM OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
DIP LOCKED EXPIRED LOCKED EXPIRED
DISCOVERER5 OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
DMSYS LOCKED EXPIRED LOCKED EXPIRED
DSGATEWAYFoot 1  OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
EXFSYS LOCKED EXPIRED LOCKED EXPIRED
INTERNET_APPSERVER_REGISTRY LOCKED, NO CREATE SESSION EXPIRED LOCKED, NO CREATE SESSION EXPIRED
IPFoot 2  LOCKED EXPIRED LOCKED EXPIRED
MDDATA LOCKED EXPIRED LOCKED EXPIRED
MDSYS LOCKED EXPIRED LOCKED EXPIRED
MGMT_VIEW OPEN RANDOM OPEN RANDOM
OCA OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
ODS OPEN Same as the ias_admin password supplied during installation LOCKED EXPIRED
OEM_REPOSITORY OPEN RANDOM - Stored in Oracle Internet Directory OPEN RANDOM
OLAPSYS LOCKED RANDOM LOCKED RANDOM
ORAOCA_PUBLIC OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
ORASSO OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
ORASSO_DS OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
ORASSO_PA OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
ORASSO_PS OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
ORASSO_PUBLIC OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
ORDPLUGINS LOCKED EXPIRED LOCKED EXPIRED
ORDSYS LOCKED EXPIRED LOCKED EXPIRED
OUTLN LOCKED EXPIRED LOCKED EXPIRED
OWF_MGR OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
PORTAL OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
PORTAL_APP OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
PORTAL_DEMO OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
PORTAL_PUBLIC OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
SCOTT LOCKED EXPIRED LOCKED EXPIRED
SI_INFORMTN_SCHEMA LOCKED EXPIRED LOCKED EXPIRED
SYS OPEN Set by user during installation OPEN Set by user during installation
SYSMAN OPEN Set by user during installation OPEN Set by user during installation
SYSTEM OPEN Set by user during installation OPEN Set by user during installation
UDDISYS OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
WCRSYS OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
WIRELESS OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
WK_TEST LOCKED EXPIRED LOCKED EXPIRED
WKPROXY OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
WKSYS OPEN RANDOM - Stored in Oracle Internet Directory LOCKED EXPIRED
WMSYS LOCKED EXPIRED LOCKED EXPIRED
XDB LOCKED RANDOM LOCKED RANDOM

Footnote 1 Beginning with Oracle Application Server 10g Release 2 (10.1.2), the DSGATEWAY schema is not used. It is provided for backward compatibility.
Footnote 2 Beginning with Oracle Application Server 10g Release 2 (10.1.2), the IP schema does not contain any data. It is has been replaced by the B2B schema and is provided only for backward compatibility.

6.3 Viewing OracleAS Metadata Repository Schema Passwords

If a Metadata Repository is registered with Oracle Internet Directory, then some schema passwords are stored in the directory and you can view them using Oracle Internet Directory tools.

The following table lists the schemas whose passwords you can view in Oracle Internet Directory.

B2B DCM DISCOVERER5 DSGATEWAY
OCA ODS OEM_REPOSITORY ORAOCA_PUBLIC
ORASSO ORASSO_DS ORASSO_PA ORASSO_PS
ORASSO_PUBLIC OWF_MGR PORTAL PORTAL_APP
PORTAL_DEMO PORTAL_PUBLIC UDDISYS WCRSYS
WIRELESS WKPROXY WKSYS

You can view the passwords using the following procedures:

6.3.1 Viewing OracleAS Metadata Repository Schema Passwords using Oracle Directory Manager

You can view Metadata Repository schema passwords using Oracle Directory Manager as follows:

  1. Start Oracle Directory Manager with the following command: 

    (UNIX) ORACLE_HOME/bin/oidadmin
(Windows) Start > Programs >
Oracle Application Server - OracleHome > Integrated Management Tools >  Oracle Directory Manager

  2. Log in to Oracle Directory Manager as the orcladmin user.

  3. In the System Objects frame, expand Entry Management, expand cn=OracleContext, expand cn=Products, expand cn=IAS, expand cn=IAS Infrastructure Databases, and expand the orclReferenceName for the Metadata Repository.

  4. Select the OrclResourceName entry for the schema whose password you want to view.

  5. In the Properties tab, you can view the password in the orclpasswordattribute field.

6.3.2 Viewing OracleAS Metadata Repository Schema Passwords using ldapsearch

You can view Metadata Repository schema passwords using ldapsearch, a command-line tool, as follows: 

ORACLE_HOME/bin/ldapsearch -p oid_port -h oid_hostname -D "cn=orcladmin"
-w orcladmin_password -b "orclresourcename=schema_name,
 orclreferencename=metadata_rep_global_db_name, cn=ias infrastructure databases,
 cn=ias, cn=products, cn=oraclecontext" -s base "objectclass=*"
 orclpasswordattribute

The command returns several lines of output. The password is listed in the following line: 

orclpasswordattribute=password

The following is an example for viewing the ORASSO schema password. In this example, the ORASSO schema password is Og23NI78. 

ORACLE_HOME/bin/ldapsearch -p 3060 -h myhost -D "cn=orcladmin"
-w mypassword -b "orclresourcename=ORASSO, 
orclreferencename=orcl.mycompany.com, 
cn=ias infrastructure databases, cn=ias, cn=products, 
cn=oraclecontext" -s base "objectclass=*" orclpasswordattribute

OrclResourceName=ORASSO,orclReferenceName=orcl.mycompany.com
cn=IAS Infrastructure Databases,cn=IAS,cn=Products,cn=OracleContext
orclpasswordattribute=Og23NI78

6.4 Changing Oracle Metadata Repository Schema Passwords

The method for changing schemas passwords in the Metadata Repository varies by schema. Some schemas store their passwords in Oracle Internet Directory; you must change their passwords using the Application Server Control Console so that both Oracle Internet Directory and the database are updated. Other schemas do not store their passwords in Oracle Internet Directory; you can change their passwords in the database using SQL*Plus. A few schemas require special steps for changing their passwords.

Table 6-2 lists the appropriate method for change each Metadata Repository schema.

Table 6-2 Methods for Changing Oracle Metadata Repository Schema Passwords

Schema Method for Changing Password
B2B You must change the password in two places:
DCM If the Metadata Repository is registered with Oracle Internet Directory, you must change the password in two places:

If the Metadata Repository is not registered with Oracle Internet Directory, you only need to change the password directly in the database using SQL*Plus.

DISCOVERER5 Use the Application Server Control Console. Navigate to the Application Server Home Page for the middle-tier instance that uses this schema and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".
DSGATEWAYFoot 1  Use the Application Server Control Console. Navigate to the Application Server Home Page for the middle-tier instance that uses this schema and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".
IPFoot 2  You must change the password in two places:
OCA This schema requires special steps. Refer to Oracle Application Server Certificate Authority Administrator's Guide for advanced topics in administration.
ODS This schema requires special steps. Refer to Oracle Internet Directory Administrator's Guide for information on resetting the default password for the database.
ORAOCA_PUBLIC This schema requires special steps. Refer to Oracle Application Server Certificate Authority Administrator's Guide for advanced topics in administration.
ORASSO Use the Application Server Control Console. Navigate to the Application Server Home Page for the Infrastructure (Identity Management) installation and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".

After you change the password, restart Oracle HTTP Server: 

opmnctl stopproc ias-component=HTTP_Server
opmnctl startproc ias-component=HTTP_Server
ORASSO_DS Use the Application Server Control Console. Navigate to the Application Server Home Page for the Infrastructure (Identity Management) installation and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".
ORASSO_PA Use the Application Server Control Console. Navigate to the Application Server Home Page for the Infrastructure (Identity Management) installation and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".
ORASSO_PS Use the Application Server Control Console. Navigate to the Application Server Home Page for the Infrastructure (Identity Management) installation and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".

Changing the ORASSO_PS password requires that the database link from all Portal schemas to the ORASSO_PS schema be re-created. To do this, run the following command for each affected Portal instance: 

ORACLE_HOME/portal/conf/ptlconfig -dad dad_name -site [-pw PORTAL_schema_password]

Refer to Oracle Application Server Portal Configuration Guide.

ORASSO_PUBLIC Use the Application Server Control Console. Navigate to the Application Server Home Page for the Infrastructure (Identity Management) installation and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".
OWF_MGR You must change the password in two places:
PORTAL Use the Application Server Control Console. Navigate to the Application Server Home Page for the middle-tier instance that uses this schema and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".

After you change the password, restart Oracle HTTP Server: 

opmnctl stopproc ias-component=HTTP_Server
opmnctl startproc ias-component=HTTP_Server
PORTAL_APP Use the Application Server Control Console. Navigate to the Application Server Home Page for the middle-tier instance that uses this schema and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".
PORTAL_DEMO Use the Application Server Control Console. Navigate to the Application Server Home Page for the middle-tier instance that uses this schema and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".
PORTAL_PUBLIC Use the Application Server Control Console. Navigate to the Application Server Home Page for the middle-tier instance that uses this schema and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".
SCOTT Use SQL*Plus to change the password directly in the database. Refer to Section 6.4.2, "Changing Schema Passwords Using SQL*Plus".
SYS Use SQL*Plus to change the password directly in the database. Refer to Section 6.4.2, "Changing Schema Passwords Using SQL*Plus".
SYSTEM Use SQL*Plus to change the password directly in the database. Refer to Section 6.4.2, "Changing Schema Passwords Using SQL*Plus".
UDDISYS Use the Application Server Control Console. Navigate to the Application Server Home Page for the middle-tier instance that uses this schema and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".
WCRSYS Use the Application Server Control Console. Navigate to the Application Server Home Page for the middle-tier instance that uses this schema and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".
WIRELESS Use the Application Server Control Console. Navigate to the Application Server Home Page for the middle-tier instance that uses this schema and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".
WK_TEST Use SQL*Plus to change the password directly in the database. Refer to Section 6.4.2, "Changing Schema Passwords Using SQL*Plus".
WKPROXY Use the Application Server Control Console. Navigate to the Application Server Home Page for the middle-tier instance that uses this schema and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".
WKSYS Use the Application Server Control Console. Navigate to the Application Server Home Page for the middle-tier instance that uses this schema and follow the instructions in Section 6.4.1, "Changing Schema Passwords Using the Application Server Control Console".

Footnote 1 Beginning with Oracle Application Server 10g Release 2 (10.1.2), the DSGATEWAY schema is not used. It is provided for backward compatibility.
Footnote 2 Beginning with Oracle Application Server 10g Release 2 (10.1.2), the IP schema does not contain any data. It has been replaced by the B2B schema and is provided only for backward compatibility.

6.4.1 Changing Schema Passwords Using the Application Server Control Console

Some schemas store their passwords in Oracle Internet Directory. You must change their passwords using the Application Server Control Console so the password is updated in both the database and Oracle Internet Directory.

To change a schema password using the Application Server Control Console:

  1. Depending on the schema, navigate to the home page for the middle-tier instance or the Infrastructure. Refer to Table 6-2 to determine which home page to use.

  2. On the home page, click Infrastructure.

  3. On the Infrastructure page, click Change Schema Password.

  4. On the Change Schema Password page, select the schema. Enter the new password in the Password and Confirm Password fields. Click OK.

6.4.2 Changing Schema Passwords Using SQL*Plus

You can change some schema passwords directly in the database using SQL*Plus. To do so, connect to the database as a user with SYSDBA privileges and issue the following command: 

SQL> ALTER USER schema identified by new_password;

For example, to change the SCOTT schema password to "abc123": 

SQL> ALTER USER SCOTT IDENTIFIED BY abc123;

6.4.3 Changing Schema Passwords in Oracle Internet Directory

A few schemas (DCM, B2B, OWF_MGR) require you to manually update the password in the Metadata Repository and in Oracle Internet Directory. You can use this procedure to change these passwords.

  1. Start Oracle Directory Manager with the following command: 

    (UNIX) ORACLE_HOME/bin/oidadmin
(Windows) Start > Programs > Oracle Application Server - OracleHome >
 Integrated Management Tools > Oracle Directory Manager

  2. Log in to Oracle Directory Manager as the orcladmin user.

  3. In the System Objects frame, expand Entry Management, expand cn=OracleContext, expand cn=Products, expand cn=IAS, expand cn=IAS Infrastructure Databases, and expand the orclReferenceName for the Metadata Repository.

  4. Select the OrclResourceName entry for the schema whose password you want to change.

  5. In the Properties tab, update the password in the orclpasswordattribute field.

  6. Click Apply.

6.5 Changing the Character Set of Oracle Metadata Repository

To configure the middle-tier and infrastructure to work with OracleAS Metadata Repository after its character set has been changed:

  1. Modify the character set of all Database Access Descriptors (DADs) accessing the metadata repository to the new database character set.

    1. Using the Application Server Control Console, navigate to the middle-tier instance home page.

    2. In the System Components section, click HTTP_Server.

    3. On the HTTP_Server home page, click Administration.

    4. On the HTTP_Server Administration page, select PL/SQL Properties. This opens the mod_plsql Services page.

    5. Scroll to the DADs section and click the name of the DAD that you want to configure. This opens the Edit DAD page.

    6. In the NLS Language field, type in a NLS_LANG value whose character set is the same as the new character set for OracleAS Metadata Repository.

    7. Click OK.

    8. Repeat steps e to g for all DADs accessing OracleAS Metadata Repository.

  2. Reconfigure the Oracle Ultra Search index as follows:

    1. Connect to OracleAS Metadata Repository as WKSYS and invoke the following SQL script to reconfigure the default cache character set and index preference: 

      ORACLE_HOME/ultrasearch/admin/wk0prefcheck.sql

    2. Connect to OracleAS Metadata Repository as the default user (WKTEST) and invoke the following SQL script: 

      ORACLE_HOME/ultrasearch/admin/wk0idxcheck.sql

      The script requests you to enter the instance name (WK_INST). Enter "y" when prompted to go ahead with the change.

      This script reconfigures the instance (in this case, the default instance). It also truncates the Oracle Text index used by Oracle Ultra Search and you must force a recrawl to rebuild the index.

    3. Repeat step b for all Oracle Ultra Search instances that were created before you changed the database character set. Invoke the script as the instance owner, and then force a recrawl of all data sources, if necessary.

6.6 Renaming and Relocating Oracle Metadata Repository Datafiles

When you install OracleAS Metadata Repository, you can choose the location for its datafiles. The default location is ORACLE_HOME/oradata/SID. After installation, you may want to relocate datafiles to a different directory. For example, you may want to move them to a directory on a file system with more space. Or, you may want to move them to a directory on a different disk for performance reasons. Another thing you may want to do is keep the datafiles in the same directory, but rename them.

This section provides a procedure for renaming or relocating datafiles. You can use this procedure on one or more datafiles, and the datafiles may be in multiple tablespaces.

This procedure applies to:

The following example shows how to relocate two datafiles in two different tablespaces, as follows:

Before you start the procedure:

The procedure is as follows:

  1. Verify the location of your datafiles.

    You can verify the location of datafiles in a particular tablespace by querying the data dictionary view DBA_DATA_FILES.

    For example, to query the location of datafiles in the OCATS and DCM tablespaces: 

    SQL> SELECT FILE_NAME, BYTES FROM DBA_DATA_FILES
WHERE TABLESPACE_NAME = 'OCATS' OR TABLESPACE_NAME = 'DCM';

FILE_NAME                                       BYTES
---------------------------------------------   ------------
/infra_home/oradata/orcl/oca.dbf                78643200
/infra_home/oradata/orcl/dcm.dbf                96993280

  2. Shut down all middle-tier instances that use OracleAS Metadata Repository.

  3. Stop the Infrastructure that contains OracleAS Metadata Repository, then start an OracleAS Metadata Repository instance and mount the database without opening it, as follows:

    1. Stop the Application Server Control Console and OPMN-managed processes: 

      emctl stop iasconsole
opmnctl stopall

    2. Leave the Metadata Repository listener running.

    3. Stop the OracleAS Metadata Repository instance (make sure the ORACLE_HOME environment variable is set): 

      sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> SHUTDOWN

    4. Start an OracleAS Metadata Repository instance and mount the database without opening it: 

      SQL> STARTUP MOUNT

  4. Move the datafiles to their new location using the operating system. For example: 

    (UNIX)
mv /infra_home/oradata/orcl/oca.dbf /new_directory/oca.dbf
mv /infra_home/oradata/orcl/dcm.dbf /new_directory/dcm.dbf

(Windows)
rename C:\infra_home\oradata\orcl\oca.dbf D:\new_directory\oca.dbf
rename C:\infra_home\oradata\orcl\dcm.dbf D:\new_directory\dcm.dbf

    Note:

    You can execute an operating system command to copy a file by using the SQL*Plus HOST command.

  5. Use ALTER DATABASE to rename the file pointers in the database's control file: 

    SQL> ALTER DATABASE
RENAME FILE                 '/infra_home/oradata/orcl/oca.dbf',
                            '/infra_home/oradata/orcl/dcm.dbf'
TO                          '/new_directory/oca.dbf',
                            '/new_directory/dcm.dbf';

    The new files must already exist; this statement does not create the files. Also, always provide complete filenames (including their full paths) to properly identify the old and new datafiles. In particular, specify the old datafile name exactly as it appears in the DBA_DATA_FILES view of the data dictionary.

  6. Shut down OracleAS Metadata Repository, then perform a normal startup of the Infrastructure:

    1. Leave the OracleAS Metadata Repository listener running.

    2. Shut down OracleAS Metadata Repository: 

      SQL> SHUTDOWN

    3. Start OracleAS Metadata Repository: 

      SQL> STARTUP

    4. Start OPMN-managed processes and the Application Server Control Console: 

      opmnctl startall
emctl start iasconsole

  7. Start the middle-tier instances that use the Infrastructure.

  8. Verify the new location of your datafiles. 

    SQL> SELECT FILE_NAME, BYTES FROM DBA_DATA_FILES
WHERE TABLESPACE_NAME = 'OCATS' OR TABLESPACE_NAME = 'DCM';

FILE_NAME                                     BYTES
--------------------------------------------- ---------------
/new_directory/oca.dbf                        78643200
/new_directory/dcm.dbf                        96993280

  9. Perform a complete cold backup of OracleAS Metadata Repository. After making any structural changes to a database, always perform an immediate and complete backup.


    See Also:

    Part V, "Backup and Recovery"

  Previous
Previous 		Next
Next
  Go To Documentation Library
Home		 Go To Product List
Solution Area		 Go To Table Of Contents
Contents		 Go To Index
Index