AD UTILITES

AD_TOP is product in Aplication which is under directory /tlcc/apps/apps_st/appl/ad/12.0.0

AD Utility :AD Utilities are a group of tools designed to install, upgrade, maintain, and patch applications.

ADPATCH is a utility that is used to apply individual patches, mini-packs, or maintenance packs to an Oracle Applications instance.

ADADMIN AD Administration (adadmin) is used performs maintenance/administration tasks on an Oracle Apps Instance. Task associated with adadmin are divided into two broad categories database and file system task.

ADCTRL Utility to determine status of worker (started by ad patch , adadmin or other ad utility) and to control ( restart/drop/skip) workers.

ADRELINK Used to relink apps executables with product libraries , if some library definition is changed or executable is corrupted.

ADMRGPCH To merge different patches & create single patch . This is helpful when you have too many patches , you can merge them & apply in one shot.

ADCLONE Utility to clone Instance from Test to Prod, Vice Versa

ADCONFIG To configure different components in Applications like changing port number or domain name or increasing number of JVM's

ADIDENT Utility to find version of a file in oracle applications (Identification )

ADLICMGR To license a product in applications , you might have license to use only 10 products initially then later decided to use 5 more so license them first by this utility

ADSPLICE You add a product in application, by default you might have 90-105 ( may be more ) products like AP, GL, AR and now oracle released one more product so add this product using this utility .
Using adadmin
Example:
[apdlcc@lcctest ~]$ 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 '/dlcc/apps/apps_st/appl'.
Is this the correct APPL_TOP [Yes] ?YES
Filename [adadmin.log] :
Do you wish to activate this feature [No] ?NO
Please enter the batchsize [1000] : Press Enter (Batch Size By default 1000 Only)
using ORACLE executables in '/dlcc/apps/tech_st/10.1.2'.

Is this the correct database [Yes] ? YES Just Check UR in TLCC 0r DLCC
Enter the password for your 'SYSTEM' ORACLE schema: MANAGER
Enter the ORACLE password of Application Object Library [APPS] :APPS

AD Administration Main Menu
--------------------------------------------------

1. Generate Applications Files menu

2. Maintain Applications Files menu

3. Compile/Reload Applications Database Entities menu

4. Maintain Applications Database Entities menu

5. Change Maintenance Mode

6. Exit AD Administration


Enter your choice [6] :
If u Select 1 Means generate some applications files like message,form,report,JAR

Generate Applications Files
----------------------------------------

1. Generate message files

2. Generate form files

3. Generate report files

4. Generate product JAR files

5. Return to Main Menu


If u Select 2 Means Maintain Applications Relink,Copy, Snapshot etc
Maintain Applications Files
----------------------------------------

1. Relink Applications programs

2. Copy files to destinations

3. Convert character set

4. Maintain snapshot information

5. Check for missing files

6. Return to Main Menu

If u Select 3 Means Compilation
Compile/Reload Applications Database Entities
---------------------------------------------------

1. Compile APPS schema

2. Compile menu information

3. Compile flexfields

4. Reload JAR files to database

5. Return to Main Menu



If u Select 4 Means Maintain Applications


Maintain Applications Database Entities
---------------------------------------------------

1. Validate APPS schema

2. Re-create grants and synonyms for APPS schema

3. Maintain multi-lingual tables

4. Check DUAL table

5. Return to Main Menu

If u Select 5 means Change Maintenance Mode

Change Maintenance Mode
----------------------------------------

Maintenance Mode is currently: [Disabled].


Maintenance mode should normally be enabled when patching
Oracle Applications and disabled when users are logged on
to the system. See the Oracle Applications Maintenance
Utilities manual for more information about maintenance mode.


Please select an option:

1. Enable Maintenance Mode

2. Disable Maintenance Mode

3. Return to Main Menu

Now we discus How to Apply the patch using ad patch

Patch applying is an Major AppsDBA Activity



Shutdown the Application server after that enable maintenance mode using adadmin

1)Download the Patch
2)Using FTP Move to the PATCH_TOP Directory

PATCH_TOP:/tlcc/apps/patches or /dlcc/apps/patches
3) Unzip the Patch
Afterr unzipping it create and Directory for that Patch number
Ex:unzip p12345.zip
12345
4) Go to 12345
5) [apdlcc@lcctest 6836355]$adpatch

Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA

Oracle Applications AutoPatch

Version 12.0.0

NOTE: You may not use this utility for custom development
unless you have written permission from Oracle Corporation.


Attention: AutoPatch no longer checks for unapplied pre-requisite patches.
You must use OAM Patch Wizard for this feature. Alternatively, you can
review the README for pre-requisite information.


Your default directory is '/dlcc/apps/apps_st/appl'.
Is this the correct APPL_TOP [Yes] ? YES
Filename [adpatch.log]:patchnumber.log
Do you wish to activate this feature [No] No
Please enter the batch size [1000]:1000
Using ORACLE executables in '/dlcc/apps/tech_st/10.1.2'.

Is this the correct database [Yes] YES
Enter the password for your 'SYSTEM' ORACLE schema: manager
Enter the ORACLE password of Application Object Library [APPS]: APPS

Your default directory is '/dlcc/apps/patches/patchnumber': Press Enter
Please enter the name of your Auto Patch driver file [patch.drv]:u12345.drv
Do you want to continue with Auto Patch [Yes]? YES
Enter the number of parallel workers [16]:

Patch Process going on……

How to tell if a patch completed successfully
If ad patch completes successfully, it will first spool out the contents of the readme.txt file, then display a message like the following.
Auto Patch is complete
You should check the file /u02/applmgr/PROD/install/log/D762433.log
for errors.
Resolving Patching Problems:
Reviewing Log Files:
Location of patchlogfile: $APPL_TOP/admin/SID/log
Mostly we are facing worker failures only in logfile mention which worker is failed
Go to that workerlog is like adwork004.log
Location of worker log:$APPL_TOP/admin/SID/log

The administrative tool used to manage patch workers is AD Control(adctrl)

[apdlcc@lcctest log]$ adctrl

Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA

AD Controller

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 '/dlcc/apps/apps_st/appl'.
Is this the correct APPL_TOP [Yes]: YES
Filename [adctrl.log] : xxxx.log
Enter the ORACLE username of Application Object Library [APPLSYS] :APPLSYS
Enter the ORACLE password of Application Object Library [APPS] :APPS
AD Controller Menu
---------------------------------------------------

1. Show worker status

2. Tell worker to restart a failed job

3. Tell worker to quit

4. Tell manager that a worker failed its job

5. Tell manager that a worker acknowledges quit

6. Restart a worker on the current machine

6. Exit

To execute an adctrl menu option, simply type the menu option and press Enter. If options 2–6 are chosen, either specifies the number of the worker that requires action, or presses Enter for the action to be executed for all workers.
The “Skip Worker” menu option is a hidden adctrl menu option. If a worker needs to be skipped, start adctrl, enter 8, and then enter the worker number. Only use this option if advised by Oracle Support.

If you want to restart the patch first go to
$cd $APPL_TOP/admin/SID $mv restart restart_old $mkdir restart
After cleaning up the restart files, you may then restart the adpatch session using adpatch.



CLONING PROCESS:

Cloning is process of creating replica of your source apps R12 Instance ( lets say you have one apps Instance with name TLCC and you want to create similar instance ( including same patches & user data) like DLCC then you will use adclone utility (Also called as Rapid Clone these days). In this case source Instance will be TLCC and target Instance will be DLCC.So here I am putting broad level steps you will use to clone apps instance .

Step1 . Prerequisites Steps you do before start cloning using rapid clone

1.1 Verify source and target nodes software versions

1.2 Apply the latest AutoConfig Template patch

1.3 Apply the latest Rapid Clone patches

Step2 . Clone Source to Target

2.1 Run preclone on DB tier
location: /tlcc/db/tech_st/10.2.0/appsutil/scripts/TLCC_lcctest
perl adpreclone.pl

2.2 Run preclone on Apps or middle tier
location: /tlcc/inst/apps/TLCC_lcctest/admin/scripts
perl adpreclone.pl

2.3 Copy source file system to target file system2.4 Configure db tier2.5 Configure apps/middle tier

Step 3 Finishing Task

3.1 Update profile options

3.2 Update printer settings (If printers are not configured or you don't want to use printer you can skip this step)

3.3 Update workflow configuration settings (Important)Related Metalink Note # 230672.1

Changes in Oracle Application Frame work(OAF)

Here is list of some changes which you will come across while working on any R12 project:
1)Apache Jserv is upgraded to OC4J(Oracle Containers for Java) server in R12.
2)How to enable log in R12?Since there is no Jserv as in 11i, there is no more dependency on jserv.properties file for enabling of log.Here are the details how to enable log on R12:In R12,Goto $ORA_CONFIG_HOME/10.1.3/opmn/conftake the backup of opmn.xmledit opmn.xml for data id="java-options" and add the following:-DAFLOG_ENABLED=true -DAFLOG_LEVEL=statement -DAFLOG_MODULE=fnd% -DAFLOG_FILENAME=/tmp/aflog.txt -Djbo.debugoutput=console The log message should get written in,$INST_TOP/logs/ora/10.1.3/opmn/oacore_default_group_1/oacorestd.out
3)How to add custom classpath in OC4J server classpath ? Add an entry in,$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployments/oacore/orion-application.xmlprepending the existing library path.4)Autocompilation setting of jsp files in R12.In file$INST_TOP/ora/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-web.xmlafterwards please restart apache$ADMIN_SCRIPTS_HOME/adapcctl.sh stopall$ADMIN_SCRIPTS_HOME/adapcctl.sh startallnow, whenever you change a character in your jsp, this will immediate reflect your output. In production environments this setting is not recommended.
4)Steps for Manual compilation of jsp in R12.> cd $FND_TOP/patch/115/bin> ojspCompile.pl --compile -s hello.jsp
5) Why R12 uses two Oracle homes in ? There is an interesting article on Steven Chan's blog on this which explains y Oracle introduced 10.1.3 and 10.1.2 both in R12 Application server archietecture:Why Use Two ORACLE_HOMEs for Release 12's Application Tier?
6)DBC file location in R12:$INST_TOP/appl/fnd/12.0.0/secure7)Bouncing OC4J server, for OAF to pick latest class and xml files.In R12, there are two scripts which need to run to bounce the HTTP server and make OC4J container pick latest class files instead of one as in 11i, we only need to run adapcctl.sh shell script to bounce Apache Jserv. Since in R12 Jserv is replaces by OC4J container, we need to run two scripts:
1)Script which is responsible for bouncing Oracle HTTP Server (powered by Apache).(adapcctl.sh)
2)Script which responsible for bouncing OC4J container (adoacorectl.sh)So basically, here is the sequence of steps you need to do :
1)adapcctl.sh stop 2)adoacorectl.sh stop 3)adapcctl.sh start 4)adoacorectl.sh startAll these scripts are in $ADMIN_SCRIPTS_HOME

HRMS Full Install to shared Mode

HRMS Full Install to shared Mode

Please follw Thw MEtalink ID:
1)Please folle these Steps
The output of this script will verify whether legislations have or have not been installed against your instance. SQL> select substr(application_short_name,1,4) app2 , rpad(decode3 (Legislation_code,null,'GLOBAL',Legislation_code),7,' ') LE_CODE4 , rpad(status,14,' ') "Install Status"5 , rpad(action,15,' ') "DataInst Action"6 , last_update_date7 from hr_legislation_installations8 where application_short_name in ('PER','PAY')9 order by LE_CODE,app;


Your Query Output shows that none of the Legislations is in Status Installed. Please go ahead and perform the step 2 of the note. Please confirm once again , none of the legislations are in status I. it should be Null.

2. If it is found from running the script that you have never run the hrglobal.drv script (legislations ARE NOT installed against your instance), then changing this instance from FULL HR Install to SHARED HR Install is quite simple. Just run the following script to flip the flag in table FND_PRODUCT_INSTALLATIONS from Installed(I) to Shared Installed(S): update FND_PRODUCT_INSTALLATIONS set STATUS = 'S' where APPLICATION_ID = 800; Note that you should verify the installation for ALL Oracle HRMS related products at this point, and alter the installation STATUS for these products as needed: application_id = 453 = HRi = Human Resources Intelligence application_id = 800 = PER = Human Resources application_id = 801 = PAY = Payroll application_id = 804 = SSP = SSP application_id = 805 = BEN = Advanced Benefits application_id = 808 = HXT = Time and Labor application_id = 809 = HXC = Time and Labor Engine application_id = 810 = OTA = Learning Management application_id = 8301 = GHR = US Federal Human Resources application_id = 8302 = PQH = Public Sector HR application_id = 8303 = PQP = Public Sector Payroll application_id = 8403 = LD = Labor Distribution The following script will display your current Installation STATUS for each of the above named Oracle HRMS related products: col a.application_name for a40 col a.application_short_name for a4 col b.status for a1 SELECT a.application_name, a.application_id, application_short_name, DECODE(b.status,'I','I', DECODE(b.status,'S','S', DECODE(b.status,'N','N',b.status))) FROM fnd_application_vl a, fnd_product_installations b WHERE a.application_id = b.application_id AND b.application_id IN (453,800,801,804,805,808,809,810,8301,8302,8303,8403) ORDER BY a.application_id; Based on your output of the above script, the 'update FND_PRODUCT_INSTALLATIONS' script can be altered as needed. EXAMPLE: If both PER and PAY were fully installed, and the hrglobal.drv script has never been run, then the 'update FND_PRODUCT_INSTALLATIONS' script would be altered as follows: update FND_PRODUCT_INSTALLATIONS set STATUS = 'S' where APPLICATION_ID IN (800,801); Once the flag has been flipped from Installed (I) to Shared Installed (S), then from this point forward the Shared HR forms should be available to you from within your other installed Oracle Applications, such as Payables, Purchasing, etc. Note that as a SHARED HR Installed instance you should check to see if you now also have the 'HR Foundation' responsibility available to assign to users. This responsibility availablity is dependent upon your Oracle Applications release version. You can verify your changes by running the following script once again: col a.application_name for a40 col a.application_short_name for a4 col b.status for a1 SELECT a.application_name, a.application_id, application_short_name, DECODE(b.status,'I','I', DECODE(b.status,'S','S', DECODE(b.status,'N','N',b.status))) FROM fnd_application_vl a, fnd_product_installations b WHERE a.application_id = b.application_id AND b.application_id IN (453,800,801,804,805,808,809,810,8301,8302,8303,8403)


2. If it is found from running the script that you have never run the hrglobal.drv script (legislations ARE NOT installed against your instance), then changing this instance from FULL HR Install to SHARED HR Install is quite simple. Just run the following script to flip the flag in table FND_PRODUCT_INSTALLATIONS from Installed(I) to Shared Installed(S): update FND_PRODUCT_INSTALLATIONS set STATUS = 'S' where APPLICATION_ID = 800; Note that you should verify the installation for ALL Oracle HRMS related products at this point, and alter the installation STATUS for these products as needed: application_id = 453 = HRi = Human Resources Intelligence application_id = 800 = PER = Human Resources application_id = 801 = PAY = Payroll application_id = 804 = SSP = SSP application_id = 805 = BEN = Advanced Benefits application_id = 808 = HXT = Time and Labor application_id = 809 = HXC = Time and Labor Engine application_id = 810 = OTA = Learning Management application_id = 8301 = GHR = US Federal Human Resources application_id = 8302 = PQH = Public Sector HR application_id = 8303 = PQP = Public Sector Payroll application_id = 8403 = LD = Labor Distribution The following script will display your current Installation STATUS for each of the above named Oracle HRMS related products: col a.application_name for a40 col a.application_short_name for a4 col b.status for a1 SELECT a.application_name, a.application_id, application_short_name, DECODE(b.status,'I','I', DECODE(b.status,'S','S', DECODE(b.status,'N','N',b.status))) FROM fnd_application_vl a, fnd_product_installations b WHERE a.application_id = b.application_id AND b.application_id IN (453,800,801,804,805,808,809,810,8301,8302,8303,8403) ORDER BY a.application_id; Based on your output of the above script, the 'update FND_PRODUCT_INSTALLATIONS' script can be altered as needed. EXAMPLE: If both PER and PAY were fully installed, and the hrglobal.drv script has never been run, then the 'update FND_PRODUCT_INSTALLATIONS' script would be altered as follows: update FND_PRODUCT_INSTALLATIONS set STATUS = 'S' where APPLICATION_ID IN (800,801); Once the flag has been flipped from Installed (I) to Shared Installed (S), then from this point forward the Shared HR forms should be available to you from within your other installed Oracle Applications, such as Payables, Purchasing, etc. Note that as a SHARED HR Installed instance you should check to see if you now also have the 'HR Foundation' responsibility available to assign to users. This responsibility availablity is dependent upon your Oracle Applications release version. You can verify your changes by running the following script once again: col a.application_name for a40 col a.application_short_name for a4 col b.status for a1 SELECT a.application_name, a.application_id, application_short_name, DECODE(b.status,'I','I', DECODE(b.status,'S','S', DECODE(b.status,'N','N',b.status))) FROM fnd_application_vl a, fnd_product_installations b WHERE a.application_id = b.application_id AND b.application_id IN (453,800,801,804,805,808,809,810,8301,8302,8303,8403) SQL> update FND_PRODUCT_INSTALLATIONSset STATUS = 'S'where APPLICATION_ID = 800; 2 31 row updated.SQL> col a.application_name for a40SQL> col a.application_short_name for a4SQL> col b.status for a1SQL> SELECT a.application_name,2 a.application_id,3 application_short_name,4 DECODE(b.status,'I','I',5 DECODE(b.status,'S','S',6 DECODE(b.status,'N','N',b.status)))7 FROM fnd_application_vl a, fnd_product_installations b8 WHERE a.application_id = b.application_id9 AND b.application_id IN (453,800,801,804,805,808,809,810,8301,8302,8303,8403)10 ORDER BY a.application_id;APPLICATION_NAME--------------------------------------------------------------------------------APPLICATION_ID APPLICATION_SHORT_NAME D-------------- -------------------------------------------------- -Human Resources Intelligence453 HRI SHuman Resources800 PER SPayroll801 PAY SAPPLICATION_NAME--------------------------------------------------------------------------------APPLICATION_ID APPLICATION_SHORT_NAME D-------------- -------------------------------------------------- -SSP804 SSP SAdvanced Benefits805 BEN STime and Labor808 HXT NAPPLICATION_NAME--------------------------------------------------------------------------------APPLICATION_ID APPLICATION_SHORT_NAME D-------------- -------------------------------------------------- -Time and Labor Engine809 HXC NLearning Management810 OTA NUS Federal Human Resources8301 GHR SAPPLICATION_NAME--------------------------------------------------------------------------------APPLICATION_ID APPLICATION_SHORT_NAME D-------------- -------------------------------------------------- -Public Sector HR8302 PQH SPublic Sector Payroll8303 PQP NLabor Distribution8403 PSP S12 rows selected.

Now your instance is share HR instance. Check with your functionaly guys, if they are able to open the people form on SHared Instance?

The Employee Form under the Purchasing Super user Responsibility is the correct form for Shared HR instance. you will not be able to open this form, if you have a full installation of HR.
I am entered the Name in People form in Purchasing and IndiaHRMS Manger
If it is success HRMS is in Shared Mode

Disk Space

Reduce Database Disk Requirements

The ORACLE2 server has run out of disk space. I take responsibility for the problem because I thought the ORACLE2 server had a 160G disk drive when it actually has a 30G disk drive. Some students (student groups) are consume about 2G of disk space and this has caused us to consume all available space on the computer. An additional disk drive that is 160G in size is on order, but has not yet arrived.

All students need to reduce the amount of disk space they are consuming. This document provides directions for helping clear up our space limitation problem. All student groups are expected to complete the requirements outlined in this document.

Delete Backup Copies of Your Database

Because space is limited, you will need to delete any backup copies of your database that are stored on the ORACLE2 server. You may wish to create a cold backup to another computer such as a home computer. We also maintain a backup of the server's disk drive to another backup device (tape) so your database files can be restored from that backup if necessary. Maintaining your own physical cold backup of the database on a personal computer will facilitate you restoring the database quickly if necessary, but this is not essential.

ALTER TABLESPACES

Another way to save space is to reduce the size of the existing tablespaces in your database. Initially I had you create tablespaces with meaningful sizes for small real-world databases, but most of the size allocated to these tablespaces will never be used during the term.

Modify the Size of the DATA, INDEXES, and USERS Tablespaces

The objective here is to save space by reducing the size of the DATA01, INDEX01, and USERS tablespaces in your database, and by dropping the READONLY01 tablespace that you created in Lab3. You should resize these tablespaces according to the table shown below. These sizes should be sufficient for the remaining lab assignments in the course. If these sizes generate errors such as: ORA-03297: file contains used data beyond requested RESIZE value, then try a successively large value in 500K increments.

Tablespace
New Size
USERS
2M
DATA01
512K
INDEX01
512K
READONLY01
DROP this tablespace from the database.

Example commands:

ALTER DATABASE
DATAFILE '/a01/student/user350/oradata/user350users.dbf'
RESIZE 2M;

ALTER DATABASE
DATAFILE '/a01/student/user350/oradata/user350data01.dbf'
RESIZE 512K;

ALTER DATABASE
DATAFILE '/a01/student/user350/oradata/user350index01.dbf'
RESIZE 512K;

DROP TABLESPACE READONLY01 INCLUDING CONTENTS AND DATAFILES;


Modify the Size of the SYSTEM, SYSAUX and TEMP Tablespaces

Modifying these two tablespaces will require some trial and error.

Attempt to reduce the SYSTEM tablespace to 225M from the current size. If this size is too small, use a slightly larger size, e.g., 230M or 235M until you reach a data file size that the SYSTEM tablespace will fit into.

ALTER DATABASE
DATAFILE '/a01/student/user350/oradata/user350system01.dbf'
RESIZE 225M;

The SYSAUX tablespace can be reduced in size significantly. In this example, the data filefor the tablespace was reduced to 75M in size.

ALTER DATABASE
DATAFILE '/a01/student/user350/oradata/user350sysaux01.dbf'
RESIZE 75M;

Here the TEMP tablespace's tempfile is reduced to 6M in size. Again, the size will depend on how much of the tablespace has been used recently for segment storage. Notice the use of the TEMPFILE clause instead of a DATAFILE clause.

ALTER DATABASE
TEMPFILE '/a01/student/user350/oradata/user350temp01.dbf'
RESIZE 6M;


Create a New (Smaller) Undo Tablespace (2M in Size)

The objective here is to save space that will not be used by your database in the UNDO tablespace. You can accomplish this by creating a new, smaller UNDO tablespace (named UNDO02), switching to the use of the new UNDO02 tablespace, and then dropping the old UNDO01 tablespace. The new UNDO02 tablespace will be 2M in size.

Step 1. Create a new UNDO tablespace named UNDO02. Ensure you use your $HOME/oradata location.

CREATE UNDO TABLESPACE undo02
DATAFILE '/a01/student/user350/oradata/user350undo02.dbf'
SIZE 2M REUSE AUTOEXTEND ON;

Step 2. With the database open, switch to the new UNDO02 tablespace.

ALTER SYSTEM SET undo_tablespace = UNDO02;

Step 3. DROP the old UNDO tablespace named UNDO01.

DROP TABLESPACE undo01
INCLUDING CONTENTS AND DATAFILES;

Shutdown your database and alter the init.ora file to reflect the name of the new UNDO tablespace, then startup the database again if you have additional tasks to perform.


RESIZE REDO LOG FILES

In order to resize the Redo log files, you need to check the status of the redo log groups to determine which ones are current, active, and inactive. Only inactive groups can be dropped.

Your goal is to reduce the size of the Redo Log Files to 4M each. This is the minimum allowable size.

Step 1. If you have two groups numbered 1 and 2, then add a third group as shown in this command. Three log groups are required in order to accomplish resizing easily.

ALTER DATABASE ADD LOGFILE GROUP 3
'$HOME/oradata/user350redo03a.log' SIZE 4M;

Step 2. Check the status of the log groups again. Our goal here is to drop and recreate Group 1, however, it must be "inactive" first.

SELECT group#, status from v$log;

If it is not inactive, then switch logfiles and recheck the status as shown here.

ALTER SYSTEM SWITCH LOGFILE;

SELECT group#, status from v$log;


When Group 1 is inactive, drop the logfile group and recreate the group with its single logfile member as shown here.

ALTER DATABASE DROP LOGFILE GROUP 1;

ALTER DATABASE ADD LOGFILE GROUP 1
'$HOME/oradata/user350redo01a.log' SIZE 4M;

Step 3. Now our goal is to drop and recreate Group 2. Switch logfiles and recheck the status of the log files. Continue switching and checking until Group 2 is inactive.

ALTER SYSTEM SWITCH LOGFILE;

SELECT group#, status from v$log;

When Group 2 is inactive, drop the logfile group and recreate the group with its single logfile member as shown here.

ALTER DATABASE DROP LOGFILE GROUP 2;

ALTER DATABASE ADD LOGFILE GROUP 2
'$HOME/oradata/user350redo02a.log' SIZE 4M REUSE;

If you already had three Redo Log Groups, then you now need to drop and recreate Group 3.

Step 4. Verify within your database the Redo log files you have. This SELECT command will list all of the redo log files by filename.

SELECT member, status FROM v$logfile;

Step 5. At the operating system level that you can now delete any redo log files that are not listed by the above SELECT statement.

Reduce Potential Memory Paging to Disk

Change the db_recovery_file_dest_size parameter in your init.ora file to the following value, then shutdown your database. On restart the potential disk space allocated to recovery will be reduced by 75% from that previously allocated.

db_recovery_file_dest_size=536870912

End of Notes.