Posts Tagged ‘Oracle DBA’

« Older Entries

Oracle : FRM-92102 ERRORS

January 14th, 2023, posted in Oracle
Share

Error reported was

Users are experiencing FRM-92102:A network error has occurred . The forms client attempted to reestablish its connection to the server 5 time(s) witho
ut success. Please check the network connection and try again.

Reference SR is 6782240.992 ( Leviton Mfg Co )

Please read through Note: 365529.1 Ext/Pub Troubleshooting FRM-92XXX Errors in Oracle Applications:
Please provide feedback on the questions listed in sections:
A. General List of Questions
D. Intermittent or Random Disconnects

These sections gave very good understanding on the problem at hand.

The most important point was timeout settings.
What the following timeout settings are set to:
Timeout Parameters:

FORMS60_TIMEOUT = 120

Heartbeat = 2 in $OA_HTML/bin/appsweb.cfg

Self Service Timeout Profile Options:
ICX: Session Timeout = 30
ICX:Limit Time = 4
ICX:Limit connect = 1000

session.timeout=1800000 (zone.properties in Apache)

So analyst recommended following adjustments

The ‘FORMS60_TIMEOUT = 120’ should not be set so high. For users that walk away and stay con
nected, this will consume unnecessary resources.
It is recommended that the ‘FORMS60_TIMEOUT be set to something like 30 minutes with 60 minutes being about the
max.

Concerning the:
ICX:Limit Time = 4
ICX:Limit connect = 1000

The ICX:Limit Time, controls the total time a session can be logged in. If set to 4 hours,
then after 4 hours the user will get disconnected, regardless of what activity
is being done. Bump this setting up to something like 8 to 10 hours.

The ICX:Limit connect, needs to be bumped up to 2000 +, because each time Session Time is
checked it adds another ICX connection. This IS NOT DETERMEND BY THE NUMBER OF U
SER CONNECTIONS. The more ICX checks its self the more ICX connections you are g
oing to see. Session expiration can also occur when the total number of times th
e session is validated exceeds ‘ICX: Limit Connect’.

The above two ICX settings are most likely the source of the errors you are seeing.

So we had to reset above settings and bounce apps.

We had a question about licensing issue as well and analyst said

The ‘ICX:Limit Connect’ has nothing to do with the number of concurrent users connecting to the a
pplications. Increasing ICX:Limit Connect to 2000+ will NOT voilate your licens
ing with Oracle ( Leviton had only 1000 concurrent user license) .

Share
read more no comments

Oracle EBS Application [UNEXPECTED] java.io.FileNotFoundException

September 4th, 2022, posted in Oracle EBS Application
Share

The concurrent program the output of which is XML report is failing in warning and the log shows the below message:
Beginning post-processing of request 5292785 on node AP6105RT at 02-AUG-2006 04:47:48. Post-processing of request 5292785 failed at 02-AUG-2006 04:49:48 with the error message:

The Output Post-processor is running but has not picked up this request. No further attempts will be made to post-process this request, and the request will be marked with Warning status.
Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary. Example if the response time is set to 60 make it at-least 180. Bounce the concurrent manager once this is done. This will resolve the issue.

If the issue still persist, check the OPP log file. You follow below navigation

System Administrator -> Concurrent : Manager -> Administrator

On this screen click on Output Post Processor and then click on Processes button -> Manager Log button

 

Error : 

 

[11/10/19 10:27:07 AM] [OPPServiceThread1] Post-processing request 16359131.
[11/10/19 10:27:07 AM] [820550:RT16359131] Executing post-processing actions for request 16359131.
[11/10/19 10:27:07 AM] [820550:RT16359131] Starting XML Publisher post-processing action.
[11/10/19 10:27:07 AM] [820550:RT16359131] 
Template code: XXSD_RDF_TO_XML_PROC
Template app:  AR
Language:      en
Territory:     00
Output type:   EXCEL
[11/10/19 10:27:07 AM] [UNEXPECTED] [820550:RT16359131] java.io.FileNotFoundException:
        /usr/tmp/xml/xdoSBWzBuUW6V111019_1027079523.fo (No such file or directory)
	at java.io.FileOutputStream.open(Native Method)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
	at oracle.apps.xdo.common.tmp.TmpFile.createTmpFileJDK118(TmpFile.java:146)
	at oracle.apps.xdo.common.tmp.TmpFile.createTmpFile(TmpFile.java:113)
	at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:987)
	at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:212)
	at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1665)
	at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:975)
	at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5936)
	at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3459)
	at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3548)
	at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:285)
	at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:173)

[11/10/19 10:27:07 AM] [820550:RT16359131] Completed post-processing actions for request 16359131.

 

Cause :

The Temporary directory for XML Publisher has not been modified after making the clone so it was pointing to non existing location and getting error out.

 

Issue :

Issue was with XML Publisher temporary directory path.

 

Solution :

1. Create a new Temporary Directory on OS level for the cloned environment.
2. Make sure that the application owner (APPLMGR) has Read and Write permission this directory.
3. Setup this new directory for XML Publisher via :
XML Publisher Administrator responsibility: Properties -> General -> Temporary Directory.
3. Restart the Server.
4. Test again with a XML Publisher Report.

Share
read more no comments

Duplicate Database from RMAN Backup – Oracle

April 10th, 2022, posted in Oracle Queries
Share

Duplicate Database from RMAN Backup


Seven Steps for Duplicate Database :

Step 1) RMNA Backup (Prerequisites)

Step 2) Create Password File

Step 3) Create Directory Structure

Step 4) Create Pfile

Step 5) Start Database in nomount Stage

Step 6) Run Duplicate Database Command

Step 7) Verify Duplicate Database

 

Step 1 RMAN Full database backup required (Prerequisites)

If database is in non archivelog mode then Shutdown the database and open in mount stage then take database backup i.e.RMAN > backup database;

If database is in archivelog mode use command i.e.  RMAN > backup database plus archivelog;

Backup Database using following command

Backup Database

-bash-4.1$ rman

Recovery Manager: Release 12.1.0.2.0 - Production on Fri Mar 11 12:19:23 2016

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

RMAN> connect target sys/sysdba123@orcl

connected to target database: ORCL (DBID=1611723298)

RMAN>

RMAN> configure controlfile autobackup on;

using target database control file instead of recovery catalog

new RMAN configuration parameters:

CONFIGURE CONTROLFILE AUTOBACKUP ON;

new RMAN configuration parameters are successfully stored

RMAN> backup database plus archivelog;



Step 2 Create a password file for the duplicate instance.

Copy Source database password file and rename it to new database password file

Go to directory: /mnt/devops_0/Oracle/db1212/product/12.1.0.2/db_1/dbs/

$ cp orapworcl orapwduporcl





Step 3 Create directory structure for Duplicate Database

Login with user db1212

Following directories need to be created

–          DupOrcl

–          Oradata

–          Fast_recovery_area

–          Diag

–          Adump

Following are sample commands

-bash-4.1$ mkdir /mnt/devops_0/DupDB/DupOrcl

-bash-4.1$ mkdir /mnt/devops_0/DupDB/DupOrcl/adump

-bash-4.1$ mkdir /mnt/devops_0/DupDB/DupOrcl/oradata

-bash-4.1$ mkdir /mnt/devops_0/DupDB/DupOrcl/oradata/duporcl

-bash-4.1$ mkdir /mnt/devops_0/DupDB/DupOrcl/fast_recovery_area

-bash-4.1$ mkdir /mnt/devops_0/DupDB/DupOrcl/diag

-bash-4.1$





Step 4 Create Pfile with few parameters.

Login with db1212

Create Pfile with following parameters

Go to directory: /mnt/devops_0/Oracle/db1212/product/12.1.0.2/db_1/dbs/

Parameters as below for initduporcl.ora,

*.audit_file_dest='/mnt/devops_0/DupDB/DupOrcl/adump'

*.audit_trail='db'

*.compatible='12.1.0.2.0'

*.db_block_size=8192

*.db_create_file_dest='/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl'

*.db_name='duporcl'

*.db_recovery_file_dest='/mnt/devops_0/DupDB/DupOrcl/fast_recovery_area'

*.db_recovery_file_dest_size=4560m

*.diagnostic_dest='/mnt/devops_0/DupDB/DupOrcl/diag'

*.undo_tablespace='UNDOTBS1'





Step 5 Start Database in nomount stage.

-bash-4.1$ export ORACLE_SID=duporcl

-bash-4.1$

-bash-4.1$ echo $ORACLE_SID

duporcl

-bash-4.1$

SQL> startup nomount

ORACLE instance started.

Total System Global Area  222298112 bytes

Fixed Size                  2922760 bytes

Variable Size             163579640 bytes

Database Buffers           50331648 bytes

Redo Buffers                5464064 bytes

SQL>

SQL> exit




Step 6 Run Duplicate Database command.
$ rman auxiliary /

$ DUPLICATE DATABASE TO duporcl

SPFILE

set control_files='/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/control01.ctl'

set DB_FILE_NAME_CONVERT='/mnt/devops_0/OrclNew/oradata/orclnew/','/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/'

set LOG_FILE_NAME_CONVERT='/mnt/devops_0/OrclNew/oradata/orclnew/','/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/'

BACKUP LOCATION '/mnt/devops_0/OrclNew/fast_recovery_area/ORCLNEW'

;






Following is the log for above command for future references.

-bash-4.1$ rman auxiliary /

Recovery Manager: Release 12.1.0.2.0 - Production on Fri Mar 11 12:04:18 2016

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

connected to auxiliary database: DUPORCL (not mounted)

RMAN> DUPLICATE DATABASE TO duporcl

SPFILE

set control_files='/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/control01.ctl'

set DB_FILE_NAME_CONVERT='/mnt/devops_0/OrclNew/oradata/orclnew/','/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/'

set LOG_FILE_NAME_CONVERT='/mnt/devops_0/OrclNew/oradata/orclnew/','/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/'

BACKUP LOCATION '/mnt/devops_0/OrclNew/fast_recovery_area/ORCLNEW'

;

Starting Duplicate Db at 11-MAR-16

contents of Memory Script:

{

   restore clone spfile to  '/mnt/devops_0/Oracle/db1212/product/12.1.0.2/db_1/dbs/spfileduporcl.ora' from

 '/mnt/devops_0/OrclNew/fast_recovery_area/ORCLNEW/autobackup/2016_03_10/o1_mf_s_906121024_cg2639ch_.bkp';

   sql clone "alter system set spfile= ''/mnt/devops_0/Oracle/db1212/product/12.1.0.2/db_1/dbs/spfileduporcl.ora''";

}

executing Memory Script

Starting restore at 11-MAR-16

allocated channel: ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: SID=13 device type=DISK

channel ORA_AUX_DISK_1: restoring spfile from AUTOBACKUP /mnt/devops_0/OrclNew/fast_recovery_area/ORCLNEW/autobackup/2016_03_10/o1_mf_s_906121024_cg2639ch_.bkp

channel ORA_AUX_DISK_1: SPFILE restore from AUTOBACKUP complete

Finished restore at 11-MAR-16

sql statement: alter system set spfile= ''/mnt/devops_0/Oracle/db1212/product/12.1.0.2/db_1/dbs/spfileduporcl.ora''

contents of Memory Script:

{

   sql clone "alter system set  db_name =

 ''DUPORCL'' comment=

 ''duplicate'' scope=spfile";

   sql clone "alter system set  control_files =

 ''/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/control01.ctl'' comment=

 '''' scope=spfile";

   sql clone "alter system set  db_file_name_convert =

 ''/mnt/devops_0/OrclNew/oradata/orclnew/'', ''/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/'' comment=

 '''' scope=spfile";

   sql clone "alter system set  LOG_FILE_NAME_CONVERT =

 ''/mnt/devops_0/OrclNew/oradata/orclnew/'', ''/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/'' comment=

 '''' scope=spfile";

   shutdown clone immediate;

   startup clone nomount;

}

executing Memory Script

sql statement: alter system set  db_name =  ''DUPORCL'' comment= ''duplicate'' scope=spfile

sql statement: alter system set  control_files =  ''/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/control01.ctl'' comment= '''' scope=spfile

sql statement: alter system set  db_file_name_convert =  ''/mnt/devops_0/OrclNew/oradata/orclnew/'', ''/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/'' comment= '''' scope=spfile

sql statement: alter system set  LOG_FILE_NAME_CONVERT =  ''/mnt/devops_0/OrclNew/oradata/orclnew/'', ''/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/'' comment= '''' scope=spfile

Oracle instance shut down

connected to auxiliary database (not started)

Oracle instance started

Total System Global Area    1073741824 bytes

Fixed Size                     2932632 bytes

Variable Size                713031784 bytes

Database Buffers             352321536 bytes

Redo Buffers                   5455872 bytes

contents of Memory Script:

{

   sql clone "alter system set  db_name =

 ''ORCLNEW'' comment=

 ''Modified by RMAN duplicate'' scope=spfile";

   sql clone "alter system set  db_unique_name =

 ''DUPORCL'' comment=

 ''Modified by RMAN duplicate'' scope=spfile";

   shutdown clone immediate;

   startup clone force nomount

   restore clone primary controlfile from  '/mnt/devops_0/OrclNew/fast_recovery_area/ORCLNEW/autobackup/2016_03_10/o1_mf_s_906121024_cg2639ch_.bkp';

   alter clone database mount;

}

executing Memory Script

sql statement: alter system set  db_name =  ''ORCLNEW'' comment= ''Modified by RMAN duplicate'' scope=spfile

sql statement: alter system set  db_unique_name =  ''DUPORCL'' comment= ''Modified by RMAN duplicate'' scope=spfile

Oracle instance shut down

Oracle instance started

Total System Global Area    1073741824 bytes

Fixed Size                     2932632 bytes

Variable Size                713031784 bytes

Database Buffers             352321536 bytes

Redo Buffers                   5455872 bytes

Starting restore at 11-MAR-16

allocated channel: ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: SID=12 device type=DISK

channel ORA_AUX_DISK_1: restoring control file

channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01

output file name=/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/control01.ctl

Finished restore at 11-MAR-16

database mounted

released channel: ORA_AUX_DISK_1

allocated channel: ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: SID=12 device type=DISK

contents of Memory Script:

{

   set until scn  1804148;

   set newname for datafile  1 to

 "/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/system01.dbf";

   set newname for datafile  3 to

 "/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/sysaux01.dbf";

   set newname for datafile  4 to

 "/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/undotbs01.dbf";

   set newname for datafile  5 to

 "/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/example01.dbf";

   set newname for datafile  6 to

 "/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/users01.dbf";

   restore

   clone database

   ;

}

executing Memory Script

executing command: SET until clause

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

Starting restore at 11-MAR-16

using channel ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: starting datafile backup set restore

channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set

channel ORA_AUX_DISK_1: restoring datafile 00001 to /mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/system01.dbf

channel ORA_AUX_DISK_1: restoring datafile 00003 to /mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/sysaux01.dbf

channel ORA_AUX_DISK_1: restoring datafile 00004 to /mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/undotbs01.dbf

channel ORA_AUX_DISK_1: restoring datafile 00005 to /mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/example01.dbf

channel ORA_AUX_DISK_1: restoring datafile 00006 to /mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/users01.dbf

channel ORA_AUX_DISK_1: reading from backup piece /mnt/devops_0/OrclNew/fast_recovery_area/ORCLNEW/backupset/2016_03_10/o1_mf_nnndf_TAG20160310T121557_cg2615wf_.bkp

channel ORA_AUX_DISK_1: piece handle=/mnt/devops_0/OrclNew/fast_recovery_area/ORCLNEW/backupset/2016_03_10/o1_mf_nnndf_TAG20160310T121557_cg2615wf_.bkp tag=TAG20160310T121557

channel ORA_AUX_DISK_1: restored backup piece 1

channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:05

Finished restore at 11-MAR-16

contents of Memory Script:

{

   switch clone datafile all;

}

executing Memory Script

datafile 1 switched to datafile copy

input datafile copy RECID=6 STAMP=906206847 file name=/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/system01.dbf

datafile 3 switched to datafile copy

input datafile copy RECID=7 STAMP=906206847 file name=/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/sysaux01.dbf

datafile 4 switched to datafile copy

input datafile copy RECID=8 STAMP=906206847 file name=/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/undotbs01.dbf

datafile 5 switched to datafile copy

input datafile copy RECID=9 STAMP=906206847 file name=/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/example01.dbf

datafile 6 switched to datafile copy

input datafile copy RECID=10 STAMP=906206847 file name=/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/users01.dbf

contents of Memory Script:

{

   set until scn  1804148;

   recover

   clone database

    delete archivelog

   ;

}

executing Memory Script

executing command: SET until clause

Starting recover at 11-MAR-16

using channel ORA_AUX_DISK_1

starting media recovery

channel ORA_AUX_DISK_1: starting archived log restore to default destination

channel ORA_AUX_DISK_1: restoring archived log

archived log thread=1 sequence=11

channel ORA_AUX_DISK_1: reading from backup piece /mnt/devops_0/OrclNew/fast_recovery_area/ORCLNEW/backupset/2016_03_10/o1_mf_annnn_TAG20160310T121703_cg2637go_.bkp

channel ORA_AUX_DISK_1: piece handle=/mnt/devops_0/OrclNew/fast_recovery_area/ORCLNEW/backupset/2016_03_10/o1_mf_annnn_TAG20160310T121703_cg2637go_.bkp tag=TAG20160310T121703

channel ORA_AUX_DISK_1: restored backup piece 1

channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01

archived log file name=/mnt/devops_0/OrclNew/Archives/1_11_906113933.dbf thread=1 sequence=11

channel clone_default: deleting archived log(s)

archived log file name=/mnt/devops_0/OrclNew/Archives/1_11_906113933.dbf RECID=1 STAMP=906206849

media recovery complete, elapsed time: 00:00:01

Finished recover at 11-MAR-16

Oracle instance started

Total System Global Area    1073741824 bytes

Fixed Size                     2932632 bytes

Variable Size                713031784 bytes

Database Buffers             352321536 bytes

Redo Buffers                   5455872 bytes

contents of Memory Script:

{

   sql clone "alter system set  db_name =

 ''DUPORCL'' comment=

 ''Reset to original value by RMAN'' scope=spfile";

   sql clone "alter system reset  db_unique_name scope=spfile";

}

executing Memory Script

sql statement: alter system set  db_name =  ''DUPORCL'' comment= ''Reset to original value by RMAN'' scope=spfile

sql statement: alter system reset  db_unique_name scope=spfile

Oracle instance started

Total System Global Area    1073741824 bytes

Fixed Size                     2932632 bytes

Variable Size                713031784 bytes

Database Buffers             352321536 bytes

Redo Buffers                   5455872 bytes

sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUPORCL" RESETLOGS ARCHIVELOG

  MAXLOGFILES     16

  MAXLOGMEMBERS      3

  MAXDATAFILES      100

  MAXINSTANCES     8

  MAXLOGHISTORY      292

 LOGFILE

  GROUP   1 ( '/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/redo01.log' ) SIZE 50 M  REUSE,

  GROUP   2 ( '/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/redo02.log' ) SIZE 50 M  REUSE,

  GROUP   3 ( '/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/redo03.log' ) SIZE 50 M  REUSE

 DATAFILE

  '/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/system01.dbf'

 CHARACTER SET AL32UTF8

contents of Memory Script:

{

   set newname for tempfile  1 to

 "/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/temp01.dbf";

   switch clone tempfile all;

   catalog clone datafilecopy  "/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/sysaux01.dbf",

 "/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/undotbs01.dbf",

 "/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/example01.dbf",

 "/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/users01.dbf";

   switch clone datafile all;

}

executing Memory Script

executing command: SET NEWNAME

renamed tempfile 1 to /mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/temp01.dbf in control file

cataloged datafile copy

datafile copy file name=/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/sysaux01.dbf RECID=1 STAMP=906206886

cataloged datafile copy

datafile copy file name=/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/undotbs01.dbf RECID=2 STAMP=906206886

cataloged datafile copy

datafile copy file name=/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/example01.dbf RECID=3 STAMP=906206886

cataloged datafile copy

datafile copy file name=/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/users01.dbf RECID=4 STAMP=906206886

datafile 3 switched to datafile copy

input datafile copy RECID=1 STAMP=906206886 file name=/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/sysaux01.dbf

datafile 4 switched to datafile copy

input datafile copy RECID=2 STAMP=906206886 file name=/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/undotbs01.dbf

datafile 5 switched to datafile copy

input datafile copy RECID=3 STAMP=906206886 file name=/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/example01.dbf

datafile 6 switched to datafile copy

input datafile copy RECID=4 STAMP=906206886 file name=/mnt/devops_0/DupDB/DupOrcl/oradata/duporcl/users01.dbf

contents of Memory Script:

{

   Alter clone database open resetlogs;

}

executing Memory Script

database opened

Finished Duplicate Db at 11-MAR-16


Step 7 Check Duplicate Database Status

-bash-4.1$ ps -ef | grep pmon

db1212    8550     1  0 Mar09 ?        00:00:12 ora_pmon_orcl12c

db1212   32132     1  0 12:07 ?        00:00:00 ora_pmon_duporcl

 -bash-4.1$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Fri Mar 11 12:09:06 2016

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

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 – 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> select name,open_mode from v$database;

NAME      OPEN_MODE

——— ——————–

DUPORCL   READ WRITE

Share
read more no comments

How to Regenerate Reports files in Apps R12 using adadmin

December 26th, 2021, posted in Oracle EBS Application
Share
[apdba@oracledb1 ~]$ cd $GL_TOP

[apdba@oracledb1 12.0.0]$ ls

admin  forms  html  lib  mds    mesg  patch    sql

bin    help   java  log  media  out   reports



[apdba@oracledb1 12.0.0]$ cd reports/



[apdba@oracledb1 reports]$ ls

US

[apdba@oracledb1 reports]$ cd US/

[apdba@oracledb1 US]$ ls

GLCRDR.rdf    GLRTB2.rdf    GLXCLVAL.rdf  GLXRBUDA.rdf  GLXRLRUR.rdf

GLGDOCDE.rdf  GLRTBD.rdf    GLXCOCRR.rdf  GLXRCAUT.rdf  GLXRLSEG.rdf

GLGENCRE.rdf  GLRTR1.rdf    GLXDALST.rdf  GLXRCTRS.rdf  GLXRLSUS.rdf

GLGVFNAV.rdf  GLWACCTR.rdf  GLXDDA.rdf    GLXRDRTS.rdf  GLXRLTCL.rdf

GLGVOPEN.rdf  GLXACDAL.rdf  GLXDFLST.rdf  GLXRLACH.rdf  GLXRLVAT.rdf

GLRFCLD.rdf   GLXAVADT.rdf  GLXDFUSR.rdf  GLXRLBOL.rdf  GLXRSUOM.rdf

GLRFGNJ.rdf   GLXAVTRB.rdf  GLXETB.rdf    GLXRLCOA.rdf  GLXUSA.rdf

GLRGCBGT.rdf  GLXBCRBC.rdf  GLXJETAX.rdf  GLXRLFBL.rdf  GLXXTB.rdf

GLRGNJ.rdf    GLXBCSD.rdf   GLXLSLST.rdf  GLXRLHST.rdf  GLYRLBGE.rdf

GLRGNL.rdf    GLXBOR.rdf    GLXRBCR.rdf   GLXRLMAB.rdf  GLYRLGLG.rdf

GLRJED.rdf    GLXBTB.rdf    GLXRBDHR.rdf  GLXRLRFL.rdf  GLYRLJGE.rdf

GLRSGNJ.rdf   GLXCAR.rdf    GLXRBJRN.rdf  GLXRLRUD.rdf  GLYRLJRE.rdf

Take backup of two .rdf files and we will regenerate them using adadmin


[apdba@oracledb1 US]$ mv GLCRDR.rdf       GLCRDR.rdf.bkp

[apdba@oracledb1 US]$ mv GLYRLJRE.rdf   GLYRLJRE.rdf.bkp

[apdba@oracledb1 US]$

[apdba@oracledb1 US]$

[apdba@oracledb1 US]$ adadmin

                     Copyright (c) 2002 Oracle Corporation

                        Redwood Shores, California, USA

                     Oracle Applications AD Administration

                                 Version 12.0.0

NOTE: You may not use this utility for custom development

      unless you have written permission from Oracle Corporation.

Your default directory is '/u01/apdba/apps/apps_st/appl'.

Is this the correct APPL_TOP [Yes] ?

AD Administration records your AD Administration session in a text file

you specify.  Enter your AD Administration log file name or press [Return]

to accept the default file name shown in brackets.

Filename [adadmin.log] :

************* Start of AD Administration session *************

AD Administration version: 12.0.0

AD Administration started at: Mon Apr 08 2013 09:00:20

APPL_TOP is set to /u01/apdba/apps/apps_st/appl

You can be notified by email if a failure occurs.

Do you wish to activate this feature [No] ?

Please enter the batchsize [1000] :

Please enter the name of the Oracle Applications System that this

APPL_TOP belongs to.

The Applications System name must be unique across all Oracle

Applications Systems at your site, must be from 1 to 30 characters

long, may only contain alphanumeric and underscore characters,

and must start with a letter.

Sample Applications System names are: "prod", "test", "demo" and

"Development_2".

Applications System Name [PROD] : PROD *

NOTE: If you do not currently have certain types of files installed

in this APPL_TOP, you may not be able to perform certain tasks.

Example 1: If you don't have files used for installing or upgrading

the database installed in this area, you cannot install or upgrade

the database from this APPL_TOP.

Example 2: If you don't have forms files installed in this area, you cannot

generate them or run them from this APPL_TOP.

Example 3: If you don't have concurrent program files installed in this area,

you cannot relink concurrent programs or generate reports from this APPL_TOP.

Do you currently have files used for installing or upgrading the database

installed in this APPL_TOP [YES] ? YES *

Do you currently have Java and HTML files for HTML-based functionality

installed in this APPL_TOP [YES] ? YES *

Do you currently have Oracle Applications forms files installed

in this APPL_TOP [YES] ? YES *

Do you currently have concurrent program files installed

in this APPL_TOP [YES] ? YES *

Please enter the name Oracle Applications will use to identify this APPL_TOP.

The APPL_TOP name you select must be unique within an Oracle Applications

System, must be from 1 to 30 characters long, may only contain

alphanumeric and underscore characters, and must start with a letter.

Sample APPL_TOP Names are: "prod_all", "demo3_forms2", and "forms1".

APPL_TOP Name [oracledb1] : oracledb1 *

You are about to use or modify Oracle Applications product tables

in your ORACLE database 'PROD'

using ORACLE executables in '/u01/apdba/apps/tech_st/10.1.2'.

Is this the correct database [Yes] ?

AD Administration needs the password for your 'SYSTEM' ORACLE schema

in order to determine your installation configuration.

Enter the password for your 'SYSTEM' ORACLE schema:

The ORACLE username specified below for Application Object Library

uniquely identifies your existing product group: APPLSYS

Enter the ORACLE password of Application Object Library [APPS] :

AD Administration is verifying your username/password.

The status of various features in this run of AD Administration is:

Saving product information.

AD code level : [B.1]

            AD Administration Main Menu

   --------------------------------------------------
  1.   Generate Applications Files menu
  1. Maintain Applications Files menu
  1. Compile/Reload Applications Database Entities menu
  1. Maintain Applications Database Entities menu
  1. Change Maintenance Mode
  1. Exit AD Administration
Enter your choice [6] : 1

         Generate Applications Files

   ----------------------------------------
  1. Generate message files
  1. Generate form files
  1.     Generate report files
  1. Generate product JAR files
  1. Return to Main Menu
Enter your choice [5] : 3

AD utilities can support a maximum of 999 workers. Your

current database configuration supports a maximum of 73 workers.

Oracle recommends that you use between 4 and 8 workers.

Enter the number of workers [4] :

Your current character set is "UTF8".

Do you want to generate Oracle Reports objects

using this character set [Yes] ?

Do you want to regenerate Oracle Reports PL/SQL library files [Yes] ?

Do you want to regenerate Oracle Reports executable files [Yes] ?

Enter list of products ('all' for all products) [all] : GL

Generate specific reports objects for each selected product [No] ?

The current set of installed languages is: US

Please select languages for generating Oracle Reports files.

You may select all of the above languages, or just a subset.

Enter list of languages ('all' for all of the above) [all] :

You selected the following languages: US

Is this the correct set of languages [Yes] ?

Reading product report information...

Selecting Oracle Reports PL/SQL library files to generate...

Selecting library files for General Ledger...

Selecting product reports to generate...

Selecting reports for General Ledger...

Generating Oracle Reports objects...

Creating the AD_UTIL_PARAMS table...

Table AD_UTIL_PARAMS already exists, so dropping the table and recreating it.

Creating FND_INSTALL_PROCESSES table...

Writing dependencies of jobs to run to appldep.txt file...

There are now 60 jobs remaining (current phase=admin+1):

    0 running, 60 ready to run and 0 waiting.

Reading completed jobs from restart file (if any).

There are now 60 jobs remaining (current phase=admin+1):

    0 running, 60 ready to run and 0 waiting.

Determining which java executables are supported by adJavaWorker...

Starting worker processes.

Worker process 1 started.

Worker process 2 started.

************* Start of AD Worker session *************

AD Worker version: 12.0.0

AD Worker started at: Mon Apr 08 2013 09:02:04

APPL_TOP is set to /u01/apdba/apps/apps_st/appl

Worker process 3 started.

************* Start of AD Worker session *************

AD Worker version: 12.0.0

AD Worker started at: Mon Apr 08 2013 09:02:04

APPL_TOP is set to /u01/apdba/apps/apps_st/appl

************* Start of AD Worker session *************

AD Worker version: 12.0.0

AD Worker started at: Mon Apr 08 2013 09:02:04

APPL_TOP is set to /u01/apdba/apps/apps_st/appl

Worker process 4 started.

Checking if all jobs have their actual and symbolic arguments in sync....

Done.

Writing jobs to run to restart file.

Reading jobs from FND_INSTALL_PROCESSES table ...

************* Start of AD Worker session *************

AD Worker version: 12.0.0

AD Worker started at: Mon Apr 08 2013 09:02:04

APPL_TOP is set to /u01/apdba/apps/apps_st/appl

Done reading jobs from FND_INSTALL_PROCESSES table ...

Telling workers to read 'todo' restart file.

Done.

Starting phase 1001 (admin+1): Generate Report Files

There are now 60 jobs remaining (current phase=admin+1):

    0 running, 60 ready to run and 0 waiting.

There are now 0 jobs remaining (current phase=Done):

    0 running, 0 ready to run and 0 waiting.

Telling workers to quit...

All workers have quit.

Dropping FND_INSTALL_PROCESSES table...

FND_INSTALL_PROCESSES table dropped.

Dropping AD_DEFERRED_JOBS table...

AD_DEFERRED_JOBS table dropped.

Copying files to destination ...

Done copying files to destination.

Review the messages above, then press [Return] to continue.

Backing up restart files, if any......Done.

Now go and check in $GL_TOP



[apdba@oracledb1 ~]$ cd $GL_TOP

[apdba@oracledb1 12.0.0]$ ls

admin  forms  html  lib  mds    mesg  patch    sql

bin    help   java  log  media  out   reports



[apdba@oracledb1 12.0.0]$ cd reports/

[apdba@oracledb1 reports]$ ls

US

[apdba@oracledb1 reports]$ cd US/

[apdba@oracledb1 US]$ ls  GLCRDR.rdf   GLYRLJRE.rdf
GLYRLJRE.rdf  GLYRLJRE.rdf

Note: Regenerating of report files is completely dependant on licensing

Share
read more no comments

APPS_TS_TX_DATA and APPS_TS_TX_IDX Size Keep On Increasing

May 31st, 2021, posted in Oracle Queries
Share

APPS_TS_TX_DATA and APPS_TS_TX_IDX Size Keep On Increasing

Solution:

Step1:
You can truncate these tables for deleting entire data without any back up.The truncate is more faster compare to delete command because data in the table is not write to roll back segments.

SQL>truncate table xla.XLA_DIAG_SOURCES;
SQL>truncate table xla.XLA_DIAG_EVENTS;

Step2:
Turn OFF the “SLA: Diagnostics Enabled” profile option at all levels.

Step3:
Check the tables, tablespace and archive logs status

Share
read more no comments
« Older Entries