APPS Blogs

Video fragments of my session posted at the end — read on. I arrived at Omni Mandalay Hotel on Sunday evening with Dan Norris. I was flying through Chicago and it turned out that Dan was on the same flight and only few rows behind me. Small world. Preparations for the conference were very chaotic on my [...]

At least once a week I get the question, "How do I train my self or my people in X?" Over the my next few blog articles, I will address this very question. I will give you a roadmap to... Bill Sawyer http://www.oracle.com/technology/products/applications/ebs/index.html

I'm pleased to welcome Bill Sawyer to our ever-growing panel of guest bloggers. Bill Sawyer is a Senior Manager in the Applications Technology Group for the E-Business Suite. Specifically, Bill's team covers the curriculum that supports E-Business Suite tools and technologies. Curriculum products cover three main areas: training courses available from Oracle University (under the category of E-Business Suite Technology), prepackaged content developed for Oracle's User Productivity Kit, and training materials publicly available through Oracle's documentation and other related materials. Steven Chan http://blogs.oracle.com/stevenChan/about.html

Hi all,

As you might have observed that the integration between Oracle Access Manager and WebLogic server varies with different versions of WebLogic Server and hence it’s architecture varies.

So I would like to give a brief on how the architecture looks like and what are the components needed for this integration.

Until WebLogic Server 10.3.0, the connector used between OAM and WebLogic is the SSPI and is available for download seperately. It is evident that SSPI Connector configuration is not very easy to get it working as customers will end up with running into lot of issues with access privileges or weblogic startup etc., . However there is no difference in components used for this integration in both WebLogic versions except the separate SSPI Connector. You would need a proxy infront of WebLogic if you want to achieve Single Sign-On and just an access gate if you want to authenticate to the WebLogic as an OAM user. If you are just looking for authentication only, then you can’t achieve SSO which demands a proxy server. From architecture perspective, you will need a Connector (installed explicitly) sitting inside the WebLogic server.  The working authentication schemes are Basic and Form.

Moving to the new version, from WebLogic Server 10.3.1 onwards, the connector has been removed. Therefore the integration becomes very easy and so the architecture is.  Here, a jar file called oamAuthnProvider.jar (for OAM 10.1.4.3) has been introduced which acts as an alternative to SSPI connector. Internally, it contains classes to talk to WebLogic Server and OAM access server. This jar file has to be copied to lib directory of weblogic server for which we are attempting to do the integration. An Identity Asserter has to be created in the WebLogic server which listens to the ObSSOCookie. The recommended authentication scheme for WLS 10.3.1 is Form Login.

References:

Blog by Josh Bregman

OAM Documentation

Please reply your comments/suggestion and it is highly appreciated.

Share This

If you are looking for documentation on Oracle WebLogic Server 11g (component in Oracle Fusion Middleware) then here are few good links

1. Recommendation for Oracle WebLogic Server 11g Disaster Recovery here  which covers File System and Network artifacts.

2. If you are using JMS (Java Messaging services)  and T-Logs in WebLogic server then check recommendations for DR here

3. Whole Server Migration : Read about Server migration in WebLogic server (Automatic and Manual server migration) here

4. Service Migration for pinned services (JMS, JTA and user defined singleton service) here

5. If you are planning to use Virtualization and Partitioning technologies (Non Oracle) with WebLogic server then check this

6. Check High Availability configuration for Oracle WebLogic here

More information on High Availability and Disaster Recovery documentation for Fusion Middleware component - SOA, WebCenter, Identity Management (OID, SSO, Access Manager) coming soon …..

If you know any document regarding WebLogic Disaster Recovery (Failover) configuration then  update it under comments section.

Previous in series Related Posts for Learn WebLogic with Us

1. Oracle WebLogic Installation Steps
2. Domain , Administration & Managed Server, Cluster in Oracle WebLogic
3. Create Domain in Oracle WebLogic
4. Oracle WebLogic Server - Startup/Shutdown
5. Oracle WebLogic Server 10g R3 10.3 is out now
6. Deploy Application on Oracle WebLogic Server
7. Cluster Architecture : Oracle WebLogic Server
8. Start WebLogic Server on Linux on port 80, 443 <= 1024
9. JDBC (Java DataBase Connectivity ) in Oracle WebLogic - Overview
10. WebLogic Server JDBC for Database connection : Step by Step
11. Security in Oracle WebLogic : Realm, Security Provider, Authentication, Authorization, Users
12. Deploy ADF application to Oracle WebLogic Server
13. Node Manager in Oracle WebLogic Server
14. Configure Oracle HTTP Server infront of Oracle WebLogic Server mod_wl_ohs
15. How to install weblogic server on 64 bit O.S. (Linux /Solaris) ?
16. Oracle WebLogic Login Issue : Password is not correct (Password Lock Policy)
17. Oracle WebLogic Server : Node Manager in nutshell
18. Certification : 1Z0-108 Oracle WebLogic Server 10g System Administrator Certified Expert
19. How to integrate WebLogic with Oracle Internet Directory for Login : Authentication
20. opatch, adpatch and now “smart update” (BSU) to apply weblogic patches
21. Disater Recovery documentation for Oracle WebLogic Server 11g (Fusion Middleware)

Share This

Hi Everyone,

I am pleased to announce the next release in our extensive Oracle related White Paper Library of:

Oracle Application Express The Fast Way to Extend to Oracle E-Business Suite

Authored by Rod West

The Purpose of Rod’s Paper:

This article describes how an APEX application can be integrated with the E-Business Suite 11i and R12. There are many tools that Applications developers can use to extend E-Business Suite but often developers are unaware that APEX can be closely integrated with the E-Business Suite. APEX forms and reports can be added to E-Business Suite menus and spreadsheet data can be uploaded into the E-Business Suite application.

Please feel free to drop by the White Paper library to request your copy of the White Paper today.

Thanks Rod for putting together this article.

Oracle E-Business Suite Release 12.1.1 Consolidated Upgrade Patch (CUP1) is now available in My Oracle Support. This patch is now mandatory for customers who are upgrading to Release 12.1.1 from the following releases: * Oracle E-Business Suite Release 11i version 11.5.9 (base, CU1, CU2) * Oracle E-Business Suite Release 11i version 11.5.10 (base, CU1, CU2) Sharath Vishwanath

I'm pleased to welcome Sharath Viswanath to this blog's panel of guest authors. Sharath Vishwanath is a Manager in Oracle E-Business Suite's Quality and Release Management team. This team owns the release process for the E-Business Suite. Steven Chan http://blogs.oracle.com/stevenChan/about.html

Upgrading to 11g Release Grid Infrastructure? You probably want to read on… Oracle 11g Release 2 Grid Infrastructure has been dramatically redesigned compare to 10g and 11gR1 Clusterware. Coming with impressive set of new features, Grid Infrastructure also uses much more memory. While RAM is rather inexpensive these days, it does pose an inconvenience in some [...]

Oracle has been working on a major upgrade to its Business Intelligence product line for almost four years.  We were told at Open World that the result would be called BI 11g and would arrive in 2010.  Oracle does not like to introduce anything near the end of its fiscal year that finishes at the [...]

Shahed pinged me about this during SOA installation:

$ sh irca.sh
Integration Repository Creation Assistant (IRCA) 10.1.3.1.0
(c) Copyright 2006 Oracle Corporation. All rights reserved.

Enter database "host port serviceName" [localhost 1521 orcl]: justanexample 1521 soa11g
Enter sys password:
Running IRCA for all product(s):
connection="justanexample 1521 soa11g", , orabpelUser=ORABPEL, esbUser=ORAESB, orawsmUser=ORAWSM

ERROR: Failed to establish database connection due to the following error:
ORA-01017: invalid username/password; logon denied

Please check your connection parameters and try again.

I tried it and got different result:

$ sh irca.sh
Integration Repository Creation Assistant (IRCA) 10.1.3.1.0
(c) Copyright 2006 Oracle Corporation. All rights reserved.

Enter database "host port serviceName" [localhost 1521 orcl]: "justanexample 1521 soa11g"
Enter sys password:
Running IRCA for all product(s):
connection=""justanexample 1521 soa11g"", , orabpelUser=ORABPEL, esbUser=ORAESB, orawsmUser=ORAWSM

ERROR: Failed to establish database connection due to the following error:
Io exception: NL Exception was generated
Please check your connection parameters and try again.

A search on My Oracle Support showed up Article [ID 580448.1]

Cause

A valid connection 'as sysdba' could not be established to the Oracle RDBMS instance.

Testing a connection from a JDeveloper client to the target RDBMS shows that a SYSTEM schema can
create a connection, but SYS is also unable to create a regular rdbms connection. Therefore
JDeveloper is having the same problem making a 'SYS as sysdba' connection over jdbc thin.

Solution

Create a password file and ensure that your RDBMS allows remote connections as sysdba.

Issue was resolved after creating passwordfile by running orapwd :
Usage: orapwd file= password= entries= force= ignorecase= nosysdba=

Just a quick announcements… If you didn’t manage to attend my presentation, Oracle 11g ASM — The Evolution, during RMOUG or other conferences, you have a chance to see it online today. I’m doing it a web-cast at RAC SIG. It’s today, 4-Mar-10 at 12:00pm EST (9:00am PST).

In previous posts I have specified the supported and working WebLogic JDK versions for Oracle Entitlement Server. I have tested protecting the WebLogic Server application where OES Admin is installed on WLS 10.3.1 and it went fine.

However, when I used WLS 10.3.1 for Admin server and tried to install the WebLogic Portal sample application (SimplePortalExample present in ales32-ssm/wls-ssm/examples) , I am stuck up with the below specified error.

[exec] com.wles.blm.BLMObjectFindException: Could not set password user //user/RootOrg!PortalDemo!wlp_dir/customer/ does not exist
[exec]     at sun.reflect.GeneratedConstructorAccessor199.newInstance(Unknown Source)
[exec]     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
[exec]     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
[exec]     at com.bea.security.blmws.common.ExceptionUtility.handleException(ExceptionUtility.java:36)
[exec]     at com.wles.soap.BLM.BlmBindingImpl.handleException(BlmBindingImpl.java:9673)
[exec]     at com.wles.soap.BLM.BlmBindingImpl.setPasswordUnknown(BlmBindingImpl.java:8749)
[exec]     at com.wles.soap.BLM.BlmBindingSkeleton.setPasswordUnknown(BlmBindingSkeleton.java:10661)
[exec]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[exec]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[exec]     at java.lang.reflect.Method.invoke(Method.java:597)
[exec]     at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:388)
[exec]     at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:283)
[exec]     at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
[exec]     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
[exec]     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
[exec]     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
[exec]     at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453)
[exec]     at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
[exec]     at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
[exec]     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
[exec]     at org.apache.axis.transport.

BUILD FAILED
/tmp/AlesConfig.performAlesChecks5515137296247183624/LoadAdditionalPolicies.xml:108: exec returned: 251

Since Oracle provides support only for Certified versions, I could not have a chance to get it working.

Hence the best approach in case you are using WebLogic Portal and OES is to use the supported WLS i.e., 10.3.0 for Admin Server. When I did so, it worked like a charm.

Share This

Oracle Database 11g Release 2 version 11.2.0.1 is now certified with Oracle E-Business Suite Release 12 (12.0, 12.1) on the HP-UX Itanium platform. Steven Chan http://blogs.oracle.com/stevenChan/about.html

It is important to know which WebLogic versions and JDK versions are supported with Oracle Entitlement Server. If you would like to see the Certification matrix for OES, here it is. Only WebLogic 10.3.0 is supported for Admin and SSM, if you are using WebLogic Portal, 10.2.0 is supported.

From my experience, WebLogic 10.3.1 is also supported by Admin and SSMs. But one should be very careful while using JDK versions while installing. I have tested JDK 6 for Admin Server and SSM while installing and it works fine. Incase you are protecting a WebLogic domain using WebLogic SSM, you would specify the JDK version while creating the domain using config wizard. It is better to use JDK 5 instead of 6. Follow the same for WebLogic Portal as JDK 5 while creating domain.

I have seen weird errors in the scenario where WebLogic Portal is being protected by OES. I created the WebLogic Portal domain with JDK6 and tried to create the SSM instance using ConfigTool. The ConfigTool stopped after the below message is shown in the response.

Checking if default ARME port is free: 8014
Generating policy files based on templates …
Checking if SSM instance already present
Checking to see if SSM ARME port is free.
Checking JDBC parameters…
Checking to see if asipassword was run…
Assuming Domain is Weblogic 9.x and above
Checking WLS version number…
Checking to see if weblogic server is running
Weblogic server not running
Checking to see if weblogic server starts (This may take several min. depending on the host) logging into weblogic server.

The solution is to create the domain using JDK 5 version.

Share This

This is a sample document showing how to migrate Non ASM DB to ASM DB
1 create the ASM instance

2.Create the required  DISK groups according to  the needs

DB name DEVEL

SQL> select file_name from dba_data_files;

FILE_NAME
——————————————————————————–
/oracle/DEVEL/system01.dbf
/oracle/DEVEL/undotbs01.dbf
/oracle/DEVEL/sysaux01.dbf
/oracle/DEVEL/users01.dbf
/oracle/DEVEL/example01.dbf

SQL> select name from v$controlfile;

NAME
——————————————————————————–
/oracle/DEVEL/control01.ctl
SQL> select MEMBER from v$logfile;

MEMBER
——————————————————————————–
/oracle/DEVEL/redo03.log
/oracle/DEVEL/redo02.log
/oracle/DEVEL/redo01.log
Shutdown the database.

SQL> SHUTDOWN IMMEDIATE

Start the database in nomount mode.

RMAN> STARTUP NOMOUNT (make sure you start with the spfile )
Restore the controlfile into ASM
RMAN> restore controlfile to ‘+DATA1′ from ‘/oracle/DEVEL/control01.ctl’;

Starting restore at 22-FEB-06
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=37 devtype=DISK

channel ORA_DISK_1: copied control file copy
Finished restore at 22-FEB-06

Find the contlrol file in ASM

ASMCMD> find -t CONTROLFILE  +DATA1 *

+DATA1/DEVEL/CONTROLFILE/backup.264.583101555
+DATA1/DEVEL/CONTROLFILE/backup.265.583101651
Modify the spfile for the controlfile new path
SQL> alter system set control_files=’+DATA1/DEVEL/CONTROLFILE/backup.264.583101555′,’+DATA1/DEVEL/CONTROLFILE/backup.265.583101651′ scope=spfile;

System altered.
shutdown  the database and restart in mount state
SQL> shutdown
ORA-01507: database not mounted
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.

Total System Global Area  473956352 bytes
Fixed Size                  1220072 bytes
Variable Size             142606872 bytes
Database Buffers          327155712 bytes
Redo Buffers                2973696 bytes
Database mounted.

SQL> select name from v$controlfile;

NAME
——————————————————————————–
+DATA1/devel/controlfile/backup.264.583101555
+DATA1/devel/controlfile/backup.265.583101651
Now move the datafiles to ASM

(here as my DB size was too small  i used this simple method, where as in big sized DB you should implement some other strategies to do everything in  in parallel  as the downtime will be minimal)
RMAN> BACKUP AS COPY DATABASE FORMAT ‘+DATA1′;

Starting backup at 22-FEB-06
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=37 devtype=DISK
channel ORA_DISK_1: starting datafile copy
input datafile fno=00001 name=/oracle/DEVEL/system01.dbf

output filename=+DATA1/devel/datafile/system.256.583100553 tag=TAG20060222T202229 recid=5 stamp=583100614
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:01:05
channel ORA_DISK_1: starting datafile copy
input datafile fno=00003 name=/oracle/DEVEL/sysaux01.dbf
output filename=+DATA1/devel/datafile/sysaux.257.583100615 tag=TAG20060222T202229 recid=6 stamp=583100652
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:45
channel ORA_DISK_1: starting datafile copy
input datafile fno=00005 name=/oracle/DEVEL/example01.dbf
output filename=+DATA1/devel/datafile/example.258.583100661 tag=TAG20060222T202229 recid=7 stamp=583100675
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting datafile copy
input datafile fno=00002 name=/oracle/DEVEL/undotbs01.dbf
output filename=+DATA1/devel/datafile/undotbs1.259.583100677 tag=TAG20060222T202229 recid=8 stamp=583100680
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:07
channel ORA_DISK_1: starting datafile copy
input datafile fno=00004 name=/oracle/DEVEL/users01.dbf
output filename=+DATA1/devel/datafile/users.260.583100683 tag=TAG20060222T202229 recid=9 stamp=583100684
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:01
channel ORA_DISK_1: starting datafile copy
copying current control file
output filename=+DATA1/devel/controlfile/backup.261.583100685 tag=TAG20060222T202229 recid=10 stamp=583100686
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 22-FEB-06
channel ORA_DISK_1: finished piece 1 at 22-FEB-06
piece handle=+DATA1/devel/backupset/2006_02_22/nnsnf0_tag20060222t202229_0.262.583100689 tag=TAG20060222T202229 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 22-FEB-06

RMAN>
RMAN> SWITCH DATABASE TO COPY;

datafile 1 switched to datafile copy “+DATA1/devel/datafile/system.256.583100553″
datafile 2 switched to datafile copy “+DATA1/devel/datafile/undotbs1.259.583100677″
datafile 3 switched to datafile copy “+DATA1/devel/datafile/sysaux.257.583100615″
datafile 4 switched to datafile copy “+DATA1/devel/datafile/users.260.583100683″
datafile 5 switched to datafile copy “+DATA1/devel/datafile/example.258.583100661″
RMAN> ALTER DATABASE OPEN;

database opened

SQL> select file_name from dba_data_files;

FILE_NAME
——————————————————————————–
+DATA1/devel/datafile/system.256.583100553
+DATA1/devel/datafile/undotbs1.259.583100677
+DATA1/devel/datafile/sysaux.257.583100615
+DATA1/devel/datafile/users.260.583100683
+DATA1/devel/datafile/example.258.583100661
Move the redo logs to ASM

SQL> select * from v$log;

    GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
———- ———- ———- ———- ———- — —————-
FIRST_CHANGE# FIRST_TIM
————- ———
         1          1          5  104857600          1 YES INACTIVE
       567335 22-FEB-06

         2          1          6  104857600          1 YES INACTIVE
       567340 22-FEB-06

         3          1          7   52428800          1 NO  CURRENT
       567343 22-FEB-06

SQL> alter database drop logfile group 1;

Database altered.

SQL> alter database add logfile group 1 (’+DATA1′) size 100M;

Database altered.

SQL> alter database drop logfile group 2;

Database altered.

SQL> alter database add logfile group 2 (’+DATA1′) size 100M;

Database altered.
SQL> alter system switch logfile;

System altered.

SQL> select * from v$log;

    GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
———- ———- ———- ———- ———- — —————-
FIRST_CHANGE# FIRST_TIM
————- ———
         1          1          8  104857600          1 NO  CURRENT
       567349 22-FEB-06

         2          1          6  104857600          1 YES INACTIVE
       567340 22-FEB-06

         3          1          7   52428800          1 YES INACTIVE
       567343 22-FEB-06
SQL> alter database drop logfile group 3;

Database altered.

SQL> alter database add logfile group 3 (’+DATA1′) size 100M;

Database altered.
SQL> select member from v$logfile;

MEMBER
——————————————————————————–
+DATA1/devel/onlinelog/group_3.268.583102251
+DATA1/devel/onlinelog/group_2.267.583102163
+DATA1/devel/onlinelog/group_1.266.583102121
RMAN> BACKUP AS COPY SPFILE FORMAT ‘+DATA1′;

Starting backup at 22-FEB-06
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=32 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 22-FEB-06
channel ORA_DISK_1: finished piece 1 at 22-FEB-06
piece handle=+DATA1/devel/backupset/2006_02_22/nnsnf0_tag20060222t211333_0.270.583103615 tag=TAG20060222T211333 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 22-FEB-06

Now find the spfile in the ASM

ASMCMD> find -t parameterfile +DATA1 *
+DATA1/DEVEL/PARAMETERFILE/spfile.273.583106111

Now make an entry in the pfile, like below
[oracle@RAC2 dbs]$ cat initDEVEL.ora
spfile=’+DATA1/DEVEL/PARAMETERFILE/spfile.273.583106111′
[oracle@RAC2 dbs]$

so now all the  DB files are stored in ASM.

Please let me if you have some questions or doubts.

Share This

The topic is related to creating a duplicated copy of  DB from production  to Development  using rman.
The below steps are applicapable in 9i,10g and 11g.In 11g there are some new methods for creating duplicate DB  which I will be covering  in coming topics

The database names used here

database names:

Primary Database SID:       PROD  server RAC1
Duplicate Database SID:     DEVEL server RAC2

Steps involed 
1.  Backup the primary database.

2.  Determine how much disk space will be required.

3.  Ensuring you have enough space on your target server.

4.  Making the backup available for the duplicate process.

5.  Creating the init.ora & administration directories for the duplicate database.

6.  Ensuring SQL*NET connections to primary database and RMAN catalog are working.

7.  Execute the RMAN script

1. Backup the primary database
Before creating a duplicate database, we must create a backup of the production DB including archivelogs also.Here i have used backup media as disk  and i am not using a recovery catalog DB

connect to the target database and take a fresh  backup

[oracle@RAC1 backup]$ export ORACLE_SID=PROD
[oracle@RAC1 backup]$ rman target /

RMAN> run
2> {
3> allocate channel d1 type disk;
4> allocate channel d2 type disk;
5> backup format ‘/oracle/backup/df_prodt%t_s%s_p%p.bak’ database;
6> sql ‘alter system archive log current’;
7> backup format ‘/oracle/backup/df_archive%t_s%s_p%p.arc’ archivelog all
8> release channel d1;
9>  release channel d2;
10> }

2.  Ensure enough space is available on the target server for Db and backup pieces

3.  Ensuring you have enough space on your target server.

4.  Making the backup available for the duplicate process.
     copy  the database from source server to target server

5.Creating the pfile  file  for the duplicate database

create a pfile and add the below contents  and start the DB in nomount mode

[oracle@RAC2 dbs]$ cat initDEVEL.ora
audit_file_dest =/oracle/DEVEL/adump
background_dump_dest =/oracle/DEVEL/bdump
core_dump_dest =/oracle/DEVEL/cdump
user_dump_dest =/oracle/DEVEL/udump
db_name =”DEVEL”
instance_name =DEVEL
control_files =(’/oracle/DEVEL/control01.ctl’)

db_file_name_convert =(”/oracle/PROD/”, “/oracle/DEVEL/”)
log_file_name_convert =(”/oracle/PROD/”, “/oracle/DEVEL/”)

undo_management =AUTO
undo_retention =10800
undo_tablespace =UNDOTBS1
db_block_size = 8192
compatible = 10.2.0.1.0

[oracle@RAC2 dbs]$ export ORACLE_SID=DEVEL
[oracle@RAC2 dbs]$ sqlplus ‘/ as sysdba’

SQL*Plus: Release 10.2.0.1.0 - Production on Sat Feb 18 21:01:50 2006

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup nomount
ORACLE instance started.

Total System Global Area  113246208 bytes
Fixed Size                  1218004 bytes
Variable Size              58722860 bytes
Database Buffers           50331648 bytes
Redo Buffers                2973696 bytes

SQL> exit

6.  Ensuring SQL*NET connections to primary database and RMAN catalog are working.

  Add  the conection descriptors in the tnsnames.ora and check the connectivity

7.  Execute the RMAN script
[oracle@RAC2 backup]$ rman target sys/oracle@prod

Recovery Manager: Release 10.2.0.1.0 - Production on Sat Feb 18 21:28:31 2006

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

connected to target database: PROD (DBID=4289561465)

RMAN> connect auxiliary /

connected to auxiliary database: DEVEL (not mounted)
RMAN> run
2> {
3> allocate auxiliary channel C1 device type disk;
4> allocate auxiliary channel C2 device type disk;
5> duplicate target database to DEVEL;
6> release channel C1;
7> release channel C2;
8> }

The above script will do the duplication and it will open up the development database.

Please let me know if you have some doubts or issues.
 

Share This

Oracle Database 11g Release 2 version 11.2.0.1 is now certified with Oracle E-Business Suite 11i (11.5.10.2) and Release 12 (12.0, 12.1) on the IBM AIX 5.3 and 6.1 on Power Systems (64-bit) platform. Steven Chan http://blogs.oracle.com/stevenChan/about.html

At times, it is important to import/export policies from Database. I am explaining the scripts to be used to achieve this.

The policies are present in the XML config file policyIX_config.xml in the location BEA_HOME/ales32-admin/bin.

To export policies from Database to an XML file:

Assume you are running from the location  BEA_HOME/ales32-admin/bin.

./policyIX.sh -export ../config/policyIX_config.xml policies_export.xml -passwdPrompt

-passwdPrompt is optional field and is the OES admin password.

The <export_configuration> element present in policyIX_config.xml specifies which policies, roles, identities etc., to be exported to the file policies_export.xml. If you are interested, open the  policyIX_config.xml and check for the various elements available.

The stuff that gets exported are Organizations, Resources, Policies, Roles, Actions etc.,

To import policies from XML file to the Database:

Assume you are running from the location  BEA_HOME/ales32-admin/bin.

./policyIX.sh -import -disableTransaction ../config/policyIX_config.xml policies_export.xml  -passwdPrompt

disableTransaction is used to prevent loading of policies in single transaction. This is recommended when loading a large policy set. It improves loading performance, but loaded policy data will not be rolled back if the loading fails.

References:

OES Docs

Share This

The Client Applications Desktop Integrator (ADI) is now certified with Oracle E-Business Suite Release 11i running on the 11gR2 Database. Customers may continue using the client-installed ADI after upgrading their E-Business Suite Release 11i environment to the 11gR2 Database. Steven Chan http://blogs.oracle.com/stevenChan/about.html