1: Installed the Oracle XE 10g on my local machine.
2: Started the RCU utility.
I received the following error:
RCU:6107 DB Init Param Error
C:Documents and Settingssandsing>sqlplus '/' as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Nov 16 16:17:48 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL> show parameters processes;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
aq_tm_processes integer 0
db_writer_processes integer 1
gcs_server_processes integer 0
job_queue_processes integer 4
log_archive_max_processes integer 2
processes integer 600
SQL> ALTER SYSTEM SET PROCESSES=500 SCOPE=SPFILE;
System altered.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 599785472 bytes
Fixed Size 1288820 bytes
Variable Size 167773580 bytes
Database Buffers 427819008 bytes
Redo Buffers 2904064 bytes
Database mounted.
Database opened.
-----------------------------------------
Then I received the below error:
RCU-6107:DB Init Param Prerequisite failure for: open_cursors. Current value is 300, it should be greater than or equal to 500.
alter system set open_cursors=500 scope=SPFILE;
Restarted DB.
Then I received the following error:
MSG:The OWA_UTIL (Oracle Web Agent) package in the database is missing or out of date, extra time will be required to install this package. Click Ignore to continue with the installation, or Abort to exit.
Error: The Oracle JVM is not installed in the database. It must be installed before loading the portal schema. Please install it and try again.
then I tried running the following scripts:
SQL> @?/rdbms/admin/pubutil.sql
SQL> @?/rdbms/admin/privutil.sql
Retarted the DB.
Tried running rcu once again:
Still facing the same issue.
SQL> select COMP_NAME, VERSION, STATUS FROM dba_registry;
--------------------------------------------------------------------------------
COMP_NAME VERSION STATUS
-------------- ---------------- -----------
Oracle Database Catalog Views 10.2.0.1.0 VALID
Oracle Database Packages and Types 10.2.0.1.0 VALID
Oracle Text 10.2.0.1.0 VALID
COMP_NAME VERSION STATUS
------------------- ----------- -----------
Oracle XML Database 10.2.0.1.0 VALID
SQL> SELECT count(*) FROM dba_objects WHERE object_type LIKE '%JAVA%';
COUNT(*)
----------
0
This shows that the JAVA VM is not installed for the database.
SQL> SHOW PARAMETER PFILE;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
spfile string D:WLSORACLEXEAPPORACLEPRODUCT10.2.0SERVERDBSSPFILEXE.ORA
SQL> SHOW PARAMETER SHARED_POOL_SIZE
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
shared_pool_size big integer 0
Since, ORALCE XE does not supports the JVM, I have decided to not install the Portal Schema and then the RCU utiltiy executed successfuly and I was able to create the nesessary schema for all other SOA components except PORTAL.
Tuesday, November 16, 2010
Thursday, May 20, 2010
Two Way SSL on Weblogic Server
This Post describes the steps and concepts required to Configure and use Two Way SSL with the Weblogic Server.
Admin Server Console is used as a Testing Application to verify the Configuration is working or not.
Wednesday, May 19, 2010
Issues while creating weblogic Custom Security Provider
One of the most important and common errors that generally comes while creating the Custom Security Providers is :
om.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for XXXXXX is not specified.
The above error comes due to incorrect usage of the Weblogic Mbean maker.
We should always use the below directory structure for creating the Custom Security Provider for Weblogic Server:
om.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for XXXXXX is not specified.
The above error comes due to incorrect usage of the Weblogic Mbean maker.
We should always use the below directory structure for creating the Custom Security Provider for Weblogic Server:
Wednesday, May 12, 2010
How to resolve : Authentication denied: Boot identity not valid
<11-May-2010 20:00:57 o'clock CEST> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
The above mentioned error occurs generally during server startups:
The above mentioned error occurs generally during server startups:
Tuesday, May 11, 2010
How to debug SSL issues with weblogic server
First of all I would suggest using the following debug flag in case of any kind of SSL issue on Weblogic server:
-Dweblogic.StdoutDebugEnabled=true
-Dssl.debug=true
If you need to debug any SSL issue with the standalone JAVA class then you can use the following debug flag:
-Djavax.net.debug=all : This is for turning all debugging.
-Djavax.net.debug=ssl : This is for turning SSL debugging.
Then In case if you are getting the following exception in the debug trace:
Monday, May 3, 2010
How to Develop Weblogic Custom Audit Provider
Through this post I will be providing the steps to develop a sample custom Weblogic Audit Provider.
Following files are required for this sample tutorial:
SimpleSampleAuditProviderImpl : This is a sample runtime class implementing the AuditProvider and AuditChannel.
SimpleSampleAuditorImpl : This is a sample class that extends the ContextHandlerImpl class to get the supported ActiveContextHandlerEntries
SimpleSampleAuditor : This is a sample Audit configuration Mbean Configuration file used to instantiate the Custome Audit Provider Mbean Type.
We will be following the link give below:
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/dvspisec/aud.html
Following files are required for this sample tutorial:
SimpleSampleAuditProviderImpl : This is a sample runtime class implementing the AuditProvider and AuditChannel.
SimpleSampleAuditorImpl : This is a sample class that extends the ContextHandlerImpl class to get the supported ActiveContextHandlerEntries
SimpleSampleAuditor : This is a sample Audit configuration Mbean Configuration file used to instantiate the Custome Audit Provider Mbean Type.
We will be following the link give below:
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/dvspisec/aud.html
Wednesday, March 31, 2010
Example of WS-Trust web service security using Weblogic server
This article describes how to secure a Web Service using a central Token Server.
The standards WS-Trust, WS-Policy, WS-SecurityPolicy and Web Services Security, formerly known WS-Security, are used.
A simple scenario with a consumer, a web service and a Security Token Service (in short STS) would serve as an example.
This specification defines a standard where in a web- service requiring some sets of authentication and message level security can trust a third party web-service( called as Security Token Service-STS) which is going to authenticate the actual request and will issue a token that can be accepted by the web –service.
The web-service should rely and trust the STS so that is can give response to the request authenticated by STS.
The Below Diagram shows the Flow of the Request between the components involved in a simple set-up showing WS-TRUST mechanism:
1: Web-Service Provider (WSP)
2: Web-Service Consumer (WSC)
3: Secure Token Service (STS)
The standards WS-Trust, WS-Policy, WS-SecurityPolicy and Web Services Security, formerly known WS-Security, are used.
A simple scenario with a consumer, a web service and a Security Token Service (in short STS) would serve as an example.
What is WS-Trust?
-----------------------
This specification defines a standard where in a web- service requiring some sets of authentication and message level security can trust a third party web-service( called as Security Token Service-STS) which is going to authenticate the actual request and will issue a token that can be accepted by the web –service.
The web-service should rely and trust the STS so that is can give response to the request authenticated by STS.
The Below Diagram shows the Flow of the Request between the components involved in a simple set-up showing WS-TRUST mechanism:
1: Web-Service Provider (WSP)
2: Web-Service Consumer (WSC)
3: Secure Token Service (STS)
Subscribe to:
Posts (Atom)