|
"So
many gods, so many creeds; So many paths that wind and wind,
while just the art of being kind is all the sad world
needs."
-Ella
Wheeler Wilcox (1850-1919)
|
How
to manage an OracleAS Metadata Repository:
What
is a Metadata Repository?
It
is a database which is pre-seeded with schemas to support Oracle
Application Server Components and services. A
Metadata Repository is required, when you install the following
components.
-
An Identity Management (ODS schema)
-
A J2EE and Web Cache (DCM schema)
-
A Portal and Wireless
-
A Businesses Intelligence and FORMS
How
to obtain a Metadata Repository:
-
You can install it as part of an Infrastructure, or
-
Into an existing database using
the Oracle Metadata Repository Creation Assistant (repca)
How
to change Metadata Repository schema password:
This
schema stores its password in (OID) Oracle Internet Directory and you
must change its password using the oidadmin tool.
The
method for changing passwords varies by schema. You can view the
following passwords using Oracle Internet Directory tools or the
Oracle Application Server Control.
The
following are the 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
|
|
BAM
|
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
|
|
DSGATEWAY
|
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
|
|
IP
|
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
|
|
ORABPEL
|
OPEN
|
RANDOM - Stored in Oracle Internet Directory
|
LOCKED
|
EXPIRED
|
|
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 Director
|
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
|
How
to change OracleAS Metadata Repository Schema
As
we mentioned before, the method for changing schema passwords in the
Metadata Repository varies by schema. Some will store their passwords
in OID; you must change their password using the Application Server
Control Console so that both Oracle Internet Directory
and the database are updated.
How
to change a schema password using the Application Server Control
Console:
1-
Navigate to the home page of the middle tier instance or the
infrastructure.
2-
On the home page, click on the “Infrastructure” tab.
3-
On this page, click on the “Change Schema Password” link.
4-
Now, select the schema. Enter your new and confirm password.
5-
Click the “OK” item to apply your changes.
------------------------
----------------
------
---
-
Q:
In my Grid at the Host Preferred Credentials page, when I enter my
host credential, I get the "Connection to hostname.domain-name as
user oracle failed: ERROR: NMO not setuid-root (Unix-only)"
message. But when I go to my unix server, I can login without any
problem. Please help!
A:
If you have Linux Intel (64-bit) or Unix Solaris and you did not run
root.sh after the EM 10g Management Agent Installation, you get this
error.
To
correct it, you should do the following steps:
1-
Check the permissions and ownership of the nmo and nmb executable in
the $AGENT_OH/bin, where the management agent has been installed:
$
ls -al nmo
$
ls -al nmb
These
should be of the form :
-rwsr-s---
1 root dba 22465 Apr 13 17:53 nmo
-rwsr-s---
1 root dba 18055 Apr 13 17:53 nmb
2-
Logged in as the root user.
$
su root
$
chmod u=rwxs nmo
$
chmod u=rwxs nmb
$
chmod g=r nmo
$
chmod g=r nmb
$
chmod g+xs nmo
$
chmod g+xs nmb
$
chmod o= nmo
$
chmod o= nmb
$
chown root:dba nmo
$
chown root:dba nmb
Now,
go back to the same steps and you shoud not get the same problem.
Good
Luck!
|