Steps to Change Oracle Weblogic Server Node Manager & Administration User Password

The option to set the Oracle WebLogic Server Administration User password to a
non-default value is available during Oracle E-Business Suite installation. This section
describes the procedure to use (on the run file system) if you need to change the
password at a later time.

The EBS WebLogic Domain uses Node Manager to control the Administration Server
and the managed servers. For the EBS WebLogic Domain, the Node Manager and
WebLogic Server Administration User passwords must be same, otherwise the AD
control scripts will not work properly.

Important: 

If you need to change the Administration User password, you must change the Node Manager password first, If you do not do this, the WebLogic Server configuration change will not be detected and the next online patching cycle may fail.

The instructions that follow should be performed on the run file system. The password

change will be automatically propagated to the patch file system during the next adop

prepare phase or fs_clone operation.

1.Shut down all application tier services except the Admin Server.

On the primary node, run the command:

$ <ADMIN_SCRIPTS_HOME>/adstpall.sh -skipNM -skipAdmin

2. Change the Oracle WebLogic Server Node Manager and Administration User passwords by performing the following steps on weblogic console

Changing the Oracle WebLogic Server Node Manager Password

-Login to weblogic to server console: 


 

- Login using the current weblogic admin username and  password.

- Click on the lock and edit button

- Click on Domain link
- Click on Security TAB

   

- Click on "Advanced" Tab

- Provide the new node manager  password which you want to configure for weblogic admin user

- Click on "save"

 

- Verify settings updated successfully and then click on "Activate changes"

- Verify all changes has been activated successfully.

Changing the Oracle WebLogic Server Administration User Password

- Click on "Security Realms"

- Click on "myrealm"

-  select "users and groups" and select weblogic User:

 

- Provide same password as we have provided above for node manager.

- Make sure the settings has been updated successfully.

- take  backup of the following files:

$FMW_HOME/user_projects/domains/EBS_domain_PROD/servers/AdminServer/security/boot.properties

$FMW_HOME/user_projects/domains/EBS_domain_PROD/servers/oafm_server1/security/boot.properties

$FMW_HOME/user_projects/domains/EBS_domain_PROD/servers/forms-c4ws_server1/security/boot.properties

$FMW_HOME/user_projects/domains/EBS_domain_PROD/servers/forms_server1/security/boot.properties

$FMW_HOME/user_projects/domains/EBS_domain_PROD/servers/oacore_server1/security/boot.properties

After this we need to edit the following configuration file "boot.properties" for all managed and admin server  using text editor and update the password field with the above configured password ( new password).

password={AES}ATsg8vMdZRg1pDofFsrAiPUfqtDqyNarOKaBkqDtbqs\=

username={AES}ni/ohZITMmwRT8ft1wdc5dGr2sO+qlA5S0JwZVQrzEc\=

After editing all the above mentioned files we need to restart the application services using adstpall.sh and adstrtal.sh scripts. Above files password will be automatically encrypted during the start of the application services.

    
After restarting of services make sure all application services are started successfully. Verify that you are able to access weblogic server console and access ERP application.

3. Start all services, using the command:

$ <ADMIN_SCRIPTS_HOME>/adstrtal.sh

Custom Application in Oracle EBS R12.2

Creating a Custom Application in Oracle E-Business Suite Release 12.2 (Doc ID 1577707.1)

Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2 (Doc ID 1577661.1)

Oracle EBS 12.2.4 application tier autoconfig fails after database upgrade from 11.2.0.3 to 11.2.0.4

Problem

Oracle EBS 12,2,4 application tier autoconfig fails with following error.

WARNING: [AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution.  Errors are grouped by directory and phase.
The report format is:
      <filename>  <phase>  <return code where appropriate>

  [PROFILE PHASE]
  AutoConfig could not successfully execute the following scripts:
    Directory: /u01/CRP/fs1/inst/apps/CRP_oracle/admin/install
      jtfictx.sh              INSTE8_PRF         1

AutoConfig is exiting with status 1

Cause

DECLARE
*
ERROR at line 1:
ORA-20000: Oracle Text error:
DRG-50857: oracle error in drixmd.GetIndexRec
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at "CTXSYS.DRUE", line 160
ORA-06512: at "CTXSYS.CTX_DDL", line 948
ORA-06512: at "CTXSYS.AD_CTX_DDL", line 336
ORA-06512: at line 96



Solution
connect /as sysdba

ALTER SESSION SET CURRENT_SCHEMA=SYS;
grant select on SYS.DBA_PROCEDURES to ctxsys;

ALTER SESSION SET CURRENT_SCHEMA=CTXSYS;
SET PAGESIZE 0
SELECT 'Calling ctx/admin/driacc.plb on ' || SYSTIMESTAMP FROM dual;
SET PAGESIZE 10

@@?/ctx/admin/driacc.plb;

@$ORACLE_HOME/rdbms/admin/utlrp.sql

set serveroutput on
execute sys.validate_context;

select comp_name, status, substr(version,1,10) as version from dba_registry where comp_id = 'CONTEXT';

Reference
 Can Not Validate CTXSYS.DRIACC Package (Doc ID 1906873.1)

Oracle EBS R12 JSP Compilation Issue Resolution

Modify the value of "s_apctimeout" to -1 in the apps tier $CONTEXT_FILE which means indefinite wait.

Then Execute the autoconfig on application tier.

Then recompile the JSP again.

EBS R12.2 ADOP Patching & Issues

ADOP Patching Cycle

# Prepare for patching:
$ adop phase=prepare

# Apply patches:
$ adop phase=apply patches=<patch number>

# Finalize patch application:
$ adop phase=finalize

# Perform cutover:
$ adop phase=cutover

$ . <EBS_ROOT>/EBSapps.env run

These steps are performed post-cutover.
$ perl <AD_TOP>/bin/admkappsutil.pl

This will create the appsutil.zip file in <INST_TOP>/admin/out.

On the database tier, as the oracle user:

Copy or ftp the appsutil.zip file to the RDBMS_ORACLE_HOME, 

then run the following commands:

$ cd <RDBMS_ORACLE_HOME>
$ unzip -o appsutil.zip

Run AutoConfig on the database tier.

Run AutoConfig on the run file system of each application tier node.

Start the application tier services. 

# Perform cleanup:
$ adop phase=cleanup

$ adop phase=fs_clone 

ADOP Important queries 

select ADOP_SESSION_ID,PREPARE_STATUS,APPLY_STATUS,
FINALIZE_STATUS,CUTOVER_STATUS,CLEANUP_STATUS,
ABORT_STATUS,STATUS,ABANDON_FLAG,NODE_NAME 
from AD_ADOP_SESSIONS order by ADOP_SESSION_ID;

Note: STATUS
N - Not Applied In the current node but applied in other nodes
R - Patch Application is going on.
H - Patch failed in the middle. (Hard Failure)
F - Patch failed in the middle but user tried to skip some failures.
S - Patch Application succeeded after skipping the failed jobs.
Y - Patch Application succeeded.
C - Reserved for clone and config_clone. Indicates clone completed 

select ADOP_SESSION_ID, BUG_NUMBER, STATUS, 
APPLIED_FILE_SYSTEM_BASE, PATCH_FILE_SYSTEM_BASE, 
ADPATCH_OPTIONS, NODE_NAME, END_DATE, CLONE_STATUS
from ad_adop_session_patches
order by end_date desc; 

ADOP Patching Issues

Issue :

Error while running command: adop phase=prepare

ERROR at line 1:

ORA-20008: No Concurrent Manager is defined that can run concurrent program

ADZDPATCH

ORA-6512: at "APPS.AD_ZD_ADOP", line 240

Solution:

FNDLOAD
 apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct 
$AD_TOP/patch/115/import/US/adzdpatch.ldt - CUSTOM_MODE=FORCE 

Oracle EBS Important Profile Options

ICX: Limit Time
Determines the maximum number of hours a user can be logged on per session.

ICX:Session Timeout
Determines the length of time (in minutes) of inactivity in a user's form session before the session is disabled.

"ICX: Limit Time" is used to control the total time a session can be logged in, regardless of what activity is being done.
It is always assigned to higher value than "ICX: Session Timeout".

Configure Oracle EBS R12 with RAC

Using Oracle 12c Release 1 Real Application Clusters with Oracle E-Business Suite Release 12 (Doc ID 1490850.1)
Using Oracle Real Application Clusters 11g Release 2 with Oracle E-Business Suite Release 12 (Doc ID 823587.1)

Oracle EBS 12.2.3 Installation

Oracle E-Business Suite Release 12.2: Technical Planning, Getting Started, and Go-Live Checklist (Doc ID 1585857.1)
Oracle E-Business Suite Release 12.2.3 Readme (Doc ID 1586214.1 )
Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1)
Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)
Oracle E-Business Suite 12.2 Patching Technology Components Guide (Doc ID 1355068.1)

Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID 1320300.1)
Oracle E-Business Suite Release 12.2 Technology Stack Documentation Roadmap (Doc ID 1934915.1)
Oracle E-Business Suite Technology Stack and Applications DBA Release Notes for Release 12.2.3 (Doc ID 1606170.1)
Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1)
Oracle EBusiness Suite Installation and Upgrade Notes Release 12 (12.2) for Linux x8664
(Doc ID 1330701.1)

Oracle EBS R12 DB Tier Cloning Issue Resolution

Oracle EBS R12 DB Tier Cloning was NOT successful. But Database was mounted. Then following can be attempted to recover and startup the database.

1. Try to open the database using resetlogs option.

SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/u01/TEST/db/apps_st/data/system01.dbf'


2. If similar error comes like above, Shutdown immediate     

SQL> Shutdown immediate

3. Remark the parameter in initTEST.ora:  

 UNDO_MANAGEMENT=AUTO
 UNDO_TABLESPACE=APPS_UNDOTS

4. Add the parameter in initTEST.ora :         

    UNDO_MANAGEMENT=MANUAL
    _ALLOW_RESETLOGS_CORRUPTION = TRUE
    _ALLOW_ERROR_SIMULATION = TRUE

5. Startup database with Manual undo management.using new initTEST.ora      

sqlplus '/as sysdba'

SQL> startup mount pfile=initTEST.ora

SQL> recover database using backup controlfile until cancel;

SQL> alter database open resetlogs;

6. Create new UNDO Tablespace  

SQL> Create UNDO tablespace NEW_UNDOTS datafile '/u01/TEST/db/apps_st/data/undo01.dbf' size 2048M;

7. Take offline the OLD Undo Tablespace :  
 
SQL> alter tablespace APPS_UNDOTS offline;

8. Take online the NEW Undo Tablespace :  

SQL> alter tablespace NEW_UNDOTS online;

9. Shutdown the database :      

SQL> shutdown immediate;

10. Edit the initTEST.ora :  

    + Remark the parameter :

    UNDO_MANAGEMENT=MANUAL
    _ALLOW_RESETLOGS_CORRUPTION = TRUE
    _ALLOW_ERROR_SIMULATION = TRUE

    + Add and edit the parameter :

    UNDO_MANAGEMENT=AUTO
    UNDO_TABLESPACE=NEW_UNDOTS 

11. Startup the database :

SQL> startup

12. Set the  default Undo tablespace as NEW_UNDOS

SQL> alter system set undo_tablespace=NEW_UNDOTS;

13. Then we can drop the OLD Undo tablespace :   

SQL> drop tablespace APPS_UNDOTS including contents and datafiles;

14. Also reuse the existing TEMP tablespace tempfiles or create a new TEMP tablespace.

Open Database failed - DATAFILE NEEDS MORE RECOVERY TO BE CONSISTENT ORA-1194 ORA-1547 ORA-1110 (Doc ID 1528788.1)

Oracle EBS 12.1.3 - Database Upgrade from 11.1.0.7 to 11.2.0.4

Steps in the following metalink documents should be followed to do the database upgrade from 11.1.0.7 to 11.2.0.4.

Interoperability Notes EBS 12.0 and 12.1 with Database 11gR2 (Doc ID 1058763.1)
Complete Checklist to Upgrade the Database to 11gR2 using DBUA (Doc ID 870814.1)

Issue Resolution for ORA-00020: maximum number of processes (%s) exceeded

select resource_name, current_utilization, max_utilization, limit_value

from v$resource_limit 

where resource_name in ('sessions', 'processes');

When ORA-00020: maximum number of processes (%s) exceeded occurred in a database and also you are NOT able to connect to the database as sys even to increase the processes parameter.
In that scenario following will work to resolve the same.

1. Instead of logging to the database via sys user as sqlplus / as sysdba you can use the following command.
sqlplus -prelim "/ as sysdba"

2.  Then you can shutdown the database using shutdown abort
SQL> shutdown abort

3. Then connect to the database via sys user as follows.
sqlplus / as sysdba

4. Then mount the database and increase the processes parameter as required.
SQL> startup mount

5. Then open the database.
SQL> alter database open

Oracle EBS R12: Creating New Branch on New Bank Errors with ORA-06508: Issue Resolution

Oracle Payables – Version: 12.1.1 and later   [Release: 12.1 and later ]
Information in this document applies to any platform.
ARHRELTS.pls 120.2
ARHRELTB.pls 120.4
ARH2RGVB.pls
ARH2RGVS.pls
HZ_RELATIONSHIPS_PKG
HZ_REGISTRY_VALIDATE_V2PUB

In Payables, when trying to save a new bank branch on a newly created bank, users are getting the following online error message:The following SQL error occurred: ORA-06508: PL/SQL: could not find program unit being called.


Payables Manager > Setup: Payment Banks and Bank Branches
Bank Branches Tab > Create
Enter Bank Name, Number and Country
Branch Options > Create New Branch
Enter Branch Name and Branch Type
Click on Save and Next or Finish

The following SQL error appears

ORA-06508: PL/SQL: could not find program unit being called.
Log shows that HZ_RELATIONSHIPS_PKG is the missing program.

Solution

1. Execute HZ_RELATIONSHIPS_PKG to create the database package

       SQL>@ARHRELTS.pls
       SQL>@ARHRELTB.pls

2. Compile HZ_REGISTRY_VALIDATE_V2PUB

     Alter package APPS.HZ_REGISTRY_VALIDATE_V2PUB compile;
     Alter package APPS.HZ_REGISTRY_VALIDATE_V2PUB compile body;

3. Retest the issue.

Reference

R12: Creating New Branch on New Bank Errors with ORA-06508: PL/SQL: Could Not Find Program Unit Being Called; HZ_RELATIONSHIPS_PKG (Doc ID 1291931.1)

Oracle EBS R12 Concurrent Managers Issue Resolution - Execute adrelink

Problem Description -
"Scheduler/Prereleaser Manager" is showing status "System Hold, Fix Manager before resetting counters".

Problem Solution -
To implement the solution, please execute the following steps:

1. Stop all middle tier services including the concurrent managers.
Please make sure that no FNDLIBR, FNDSM, or any dead process is
running.

2. Stop the database.

3. Start the database.

4. Go to cd $FND_TOP/bin
$ adrelink.sh force=y link_debug=y "fnd FNDLIBR"
$ adrelink.sh force=y link_debug=y "fnd FNDFS"
$ adrelink.sh force=y link_debug=y "fnd FNDCRM"
$ adrelink.sh force=y link_debug=y "fnd FNDSM"

5. Run the CMCLEAN.SQL script from the referenced note below (don't forget to commit).
Note 134007.1 CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables

6. Execute the following SQL:
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where
CONCURRENT_QUEUE_NAME like 'FNDSM%';

7. Start the middle tier services including your concurrent manager.

8. Retest the issue.

Install Oracle Weblogic Server 10.3.6 on Windows

Install Oracle Weblogic Server 10.3.6 on Windows

Resolve Oracle Database 11g Installation Issue on RHEL 6

Below error comes when trying to install the Oracle Database 11g on RHEL 6.




There is a workaround to avoid this issue. Execute following command and start the database installation again.

$ export LD_BIND_NOW = 1

Oracle Database 12c Installation and Configurations

Oracle 12c Container & Pluggable Database Installation

All Oracle Database 12c installation options are very similar to the Oracle Database 11g installation other than the new concept of container & pluggable databases. To create the container database with pluggale databases in Oracle 12c following options can be used in the installation wizard or in DBCA.

The checkbox "Create As Container Database" has to be selected and the option "Create a Container Database with one or more PDBs" should be chosen with the number of pluggable databases and prefix of the pluggable database.

Important Queries for Administration


[oracle@prod admin]$ sqlplus '/ as sysdba'

SQL*Plus: Release 12.1.0.1.0 Production on Tue Oct 8 16:30:29 2013

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

Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL>

SQL> select con_id, banner from v$version;

    CON_ID
----------
BANNER
--------------------------------------------------------------------------------
         0
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

         0
PL/SQL Release 12.1.0.1.0 - Production

         0
CORE    12.1.0.1.0      Production

    CON_ID
----------
BANNER
--------------------------------------------------------------------------------
         0
TNS for Linux: Version 12.1.0.1.0 - Production

         0
NLSRTL Version 12.1.0.1.0 - Production


SQL> select sys_context('userenv','con_name') from dual;

SYS_CONTEXT('USERENV','CON_NAME')
--------------------------------------------------------------------------------
CDB$ROOT

SQL> select con_id, name, open_mode from v$pdbs;

    CON_ID NAME                           OPEN_MODE
---------- ------------------------------ ----------
         2 PDB$SEED                       READ ONLY
         3 PDB1                           READ WRITE
         4 PDB2                           READ WRITE


SQL> alter session set container = PDB1;

Session altered.

SQL> select sys_context('userenv','con_name') from dual;

SYS_CONTEXT('USERENV','CON_NAME')
--------------------------------------------------------------------------------
PDB1

SQL> select con_id, name, open_mode from v$pdbs;

    CON_ID NAME                           OPEN_MODE
---------- ------------------------------ ----------
         3 PDB1                           READ WRITE

SQL> alter session set container = PDB2;

Session altered.

SQL> select sys_context('userenv','con_name') from dual;

SYS_CONTEXT('USERENV','CON_NAME')
--------------------------------------------------------------------------------
PDB2

SQL> select con_id, name, open_mode from v$pdbs;

    CON_ID NAME                           OPEN_MODE
---------- ------------------------------ ----------
         4 PDB2                           READ WRITE

SQL> SELECT df.tablespace_name TABLESPACE, df.total_space TOTAL_SPACE,
  2  fs.free_space FREE_SPACE, df.total_space_mb TOTAL_SPACE_MB,
  3  (df.total_space_mb - fs.free_space_mb) USED_SPACE_MB, fs.free_space_mb FREE_SPACE_MB,
  4  ROUND(100 * (fs.free_space / df.total_space),2) PCT_FREE
  5  FROM (SELECT tablespace_name, SUM (bytes) TOTAL_SPACE,
  6  ROUND( SUM (bytes) / 1048576) TOTAL_SPACE_MB
  7  FROM dba_data_files GROUP BY tablespace_name) df,
  8  (SELECT tablespace_name, SUM (bytes) FREE_SPACE, ROUND( SUM (bytes) / 1048576) FREE_SPACE_MB
  9  FROM dba_free_space GROUP BY tablespace_name) fs
 10  WHERE df.tablespace_name = fs.tablespace_name(+) ORDER BY ROUND(100 * (fs.free_space / df.total_space),2);

TABLESPACE                     TOTAL_SPACE FREE_SPACE TOTAL_SPACE_MB
------------------------------ ----------- ---------- --------------
USED_SPACE_MB FREE_SPACE_MB   PCT_FREE
------------- ------------- ----------
SYSTEM                           272629760   10354688            260
          250            10        3.8

SYSAUX                           639631360   32309248            610
          579            31       5.05

USERS                              5242880    4194304              5
            1             4         80


RMAN Backup

[oracle@prod admin]$ rman

Recovery Manager: Release 12.1.0.1.0 - Production on Tue Oct 8 16:45:56 2013

Copyright (c) 1982, 2013, Oracle and/or its affiliates.  All rights reserved.

RMAN> connect target /

connected to target database: TEST (DBID=2126431506)

RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name TEST are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/12.1.0/dbhome_1/dbs/snapcf_TEST.f'; # default

RMAN> backup database plus archivelog;

Starting backup at 08-OCT-13
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=359 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=4 RECID=1 STAMP=828285237
input archived log thread=1 sequence=5 RECID=2 STAMP=828285267
input archived log thread=1 sequence=6 RECID=3 STAMP=828285630
input archived log thread=1 sequence=7 RECID=4 STAMP=828287384
input archived log thread=1 sequence=8 RECID=5 STAMP=828290783
channel ORA_DISK_1: starting piece 1 at 08-OCT-13
channel ORA_DISK_1: finished piece 1 at 08-OCT-13
piece handle=/u01/app/oracle/fast_recovery_area/TEST/backupset/2013_10_08/o1_mf_annnn_TAG20131008T164623_957td82r_.bkp tag=TAG20131008T164623 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 08-OCT-13

Starting backup at 08-OCT-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/TEST/system01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/TEST/sysaux01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/TEST/undotbs01.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/TEST/users01.dbf
channel ORA_DISK_1: starting piece 1 at 08-OCT-13
channel ORA_DISK_1: finished piece 1 at 08-OCT-13
piece handle=/u01/app/oracle/fast_recovery_area/TEST/backupset/2013_10_08/o1_mf_nnndf_TAG20131008T164625_957td9jb_.bkp tag=TAG20131008T164625 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00009 name=/u01/app/oracle/oradata/TEST/PDB1/sysaux01.dbf
input datafile file number=00008 name=/u01/app/oracle/oradata/TEST/PDB1/system01.dbf
input datafile file number=00010 name=/u01/app/oracle/oradata/TEST/PDB1/PDB1_users01.dbf
channel ORA_DISK_1: starting piece 1 at 08-OCT-13
channel ORA_DISK_1: finished piece 1 at 08-OCT-13
piece handle=/u01/app/oracle/fast_recovery_area/TEST/E8389F6267BA2A3EE0431C6FA8C0FFB3/backupset/2013_10_08/o1_mf_nnndf_TAG20131008T164625_957tdrrc_.bkp tag=TAG20131008T164625 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00012 name=/u01/app/oracle/oradata/TEST/PDB2/sysaux01.dbf
input datafile file number=00011 name=/u01/app/oracle/oradata/TEST/PDB2/system01.dbf
input datafile file number=00013 name=/u01/app/oracle/oradata/TEST/PDB2/PDB2_users01.dbf
channel ORA_DISK_1: starting piece 1 at 08-OCT-13
channel ORA_DISK_1: finished piece 1 at 08-OCT-13
piece handle=/u01/app/oracle/fast_recovery_area/TEST/E838A04FA7AD2A98E0431C6FA8C01C02/backupset/2013_10_08/o1_mf_nnndf_TAG20131008T164625_957tf804_.bkp tag=TAG20131008T164625 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00007 name=/u01/app/oracle/oradata/TEST/pdbseed/sysaux01.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/TEST/pdbseed/system01.dbf
channel ORA_DISK_1: starting piece 1 at 08-OCT-13
channel ORA_DISK_1: finished piece 1 at 08-OCT-13
piece handle=/u01/app/oracle/fast_recovery_area/TEST/E83894A1E2CD234FE0431C6FA8C0EE1E/backupset/2013_10_08/o1_mf_nnndf_TAG20131008T164625_957tfq7k_.bkp tag=TAG20131008T164625 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
Finished backup at 08-OCT-13

Starting backup at 08-OCT-13
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=9 RECID=6 STAMP=828290846
channel ORA_DISK_1: starting piece 1 at 08-OCT-13
channel ORA_DISK_1: finished piece 1 at 08-OCT-13
piece handle=/u01/app/oracle/fast_recovery_area/TEST/backupset/2013_10_08/o1_mf_annnn_TAG20131008T164726_957tg6hz_.bkp tag=TAG20131008T164726 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 08-OCT-13

Starting Control File and SPFILE Autobackup at 08-OCT-13
piece handle=/u01/app/oracle/fast_recovery_area/TEST/autobackup/2013_10_08/o1_mf_s_828290847_957tg7qs_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 08-OCT-13

RMAN>


Pluggable Database Cloning

SQL> conn / as sysdba
Connected.

SQL> alter pluggable database PDB2 close;

Pluggable database altered.

SQL> select con_id, name, open_mode from v$pdbs;

    CON_ID NAME                           OPEN_MODE
---------- ------------------------------ ----------
         2 PDB$SEED                       READ ONLY
         3 PDB1                           READ WRITE
         4 PDB2                           MOUNTED

SQL> alter pluggable database PDB2 open read only;

Pluggable database altered.

SQL> select con_id, name, open_mode from v$pdbs;

    CON_ID NAME                           OPEN_MODE
---------- ------------------------------ ----------
         2 PDB$SEED                       READ ONLY
         3 PDB1                           READ WRITE
         4 PDB2                           READ ONLY

SQL> create pluggable database PDB3 from PDB2 file_name_convert = ('PDB2','PDB3');

Pluggable database created.

SQL> select con_id, name, open_mode from v$pdbs;

    CON_ID NAME                           OPEN_MODE
---------- ------------------------------ ----------
         2 PDB$SEED                       READ ONLY
         3 PDB1                           READ WRITE
         4 PDB2                           READ ONLY
         5 PDB3                           MOUNTED

SQL> alter pluggable database PDB3 open;

Pluggable database altered.

SQL>  select con_id, name, open_mode from v$pdbs;

    CON_ID NAME                           OPEN_MODE
---------- ------------------------------ ----------
         2 PDB$SEED                       READ ONLY
         3 PDB1                           READ WRITE
         4 PDB2                           READ ONLY
         5 PDB3                           READ WRITE

SQL> alter pluggable database PDB2 close;

Pluggable database altered.

SQL>  select con_id, name, open_mode from v$pdbs;

    CON_ID NAME                           OPEN_MODE
---------- ------------------------------ ----------
         2 PDB$SEED                       READ ONLY
         3 PDB1                           READ WRITE
         4 PDB2                           MOUNTED
         5 PDB3                           READ WRITE

SQL> alter pluggable database PDB2 open;

Pluggable database altered.

SQL> select con_id, name, open_mode from v$pdbs;

    CON_ID NAME                           OPEN_MODE
---------- ------------------------------ ----------
         2 PDB$SEED                       READ ONLY
         3 PDB1                           READ WRITE
         4 PDB2                           READ WRITE
         5 PDB3                           READ WRITE

SQL>