Cisco VPN client for Windows 7/Vista/XP/9x

Download the suitable installation file for your operating system :

o Cisco VPN client v5.0.02 for Windows 2000/XP/Vista and Windows 7 (32 bits)

o Cisco VPN client for Windows Vista and Windows 7 (64 bits)

o Cisco VPN client v4.6. for Windows 9x

2. Run the downloaded program and install it.
3. After installation is complete, restart your computer.
4. Start the VPN Client (Cisco VPN Client).
5. Press the New button to add a new connection configuration.

6. In the Host field, enter: vpn.upv.es for access from Internet

In the Name box, type "soloupv" (without quotation marks) if you only want access to shared resources or "biblioteca" if you want access to the library's electronic journals.

In the fields Password and Confirm Password, type the password "upvnet " (without quotation marks).

7. At the "Transport" tab, check "Enable Transparent Tunneling" and "IPSec over UDP (NAT / PAT)"

Click Save button to complete the configuration.

8. Click Connect button to connect to the UPV network.

When prompted for a username and password, enter your credentials: domain\username, where 'domain' only can be ALUMNO (for students) or UPVNET (for staff)

9. If all is OK you'll be connected

Create UNDO Tablespace in Oracle 9i/10g/11g

To drop and recreate UNDO Tablespace in Oracle 9i/10g/11g

 1. Determine the size of your undo tablespace

SQL> select sum(bytes)/1024/1024/1024 from dba_data_files where tablespace_name='UNDOTBS1';

SUM(BYTES)/1024/1024/1024
-------------------------
                12.09375
               
2. Create a new undo tablespace of the same size (larger or smaller) depending on your database requirements.
SQL> create undo tablespace UNDOTBS2 datafile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL2\UNDOTBS02.DBF' size 400M;

    Tablespace created.
   
3. Edit your init.ora file and change the parameter "undo_tablespace=UNDOTBS2" so it points to the newly created tablespace.
    Change undo_tablespace=UNDOTBS2
    Change undo_management=MANUAL

    Setting undo_management now ensures the old rollback segments can be taken offline and avoids editing the pfile and restarting the instance again in Step 7.
   
4. Arrange a time when the database can be shutdown cleanly and perform a shutdown immediate.   

5. Startup the database

6. Confirm the new tablespace is in use:

    SQL> show parameter undo_tablespace

    NAME                 TYPE              VALUE
    -------------        -----------       ------------
    undo_tablespace      string            UNDOTBS2
   
7. Check the status of the undo segments and determine if all the segments in the old undo tablespace are offline. The segments in the new tablespace may also show offline.
    SQL>select owner, segment_name, tablespace_name, status from dba_rollback_segs order by 3;

    OWNER         SEGMENT_NAME         TABLESPACE_NAME         STATUS
    ------              --------------------------- ------------------------------ -----------
    PUBLIC         _SYSSMU3$                      UNDOTBS1                         OFFLINE
    PUBLIC         _SYSSMU2$                      UNDOTBS1                         OFFLINE
    PUBLIC         _SYSSMU19$                     UNDOTBS2                         OFFLINE

    ....etc.

    If the old segments are online, then they must be taken offline:

    SQL>alter rollback segment "_SYSSMU3$" offline;
    SQL>alter rollback segment "_SYSSMU2$" offline;

    This should be executed for all online rollback segments in the old tablespace.

8. Provided all the segments in the old undo tablespace are offline, you can now drop the old undo tablespace:
    SQL>drop tablespace UNDOTBS1 including contents and datafiles;

    Tablespace dropped.

9. Edit your init.ora file do the following changes.

    undo_management='AUTO'
    undo_tablespace='UNDOTBS2'
   
10. Shutdown the database (shutdown immediate) and restart it.

11. Monitor the alert log simultaneously during all steps.

Create TEMP Tablespace in Oracle 9i/10g/11g

To drop and recreate TEMP Tablespace in Oracle 9i/10g/11g

1. Create Temporary Tablespace Temp

CREATE TEMPORARY TABLESPACE TEMP2 TEMPFILE  ‘/u01/app/oradata/temp01′ SIZE 2000M, ‘/u01/app/oradata/temp02′ SIZE 2000M';

2. Move Default Database temp tablespace

ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp2;

3. Make sure No sessions are using your Old Temp tablespace

   a.  Find Session Number from V$SORT_USAGE:
       SELECT USERNAME, SESSION_NUM, SESSION_ADDR FROM V$SORT_USAGE;

   b.  Find Session ID from V$SESSION:

       If the resultset contains any tows then your next step will be to find the SID from the V$SESSION view. You can find session id by using SESSION_NUM or SESSION_ADDR from previous resultset.

       SELECT SID, SERIAL#, STATUS FROM V$SESSION WHERE SERIAL#=SESSION_NUM;
       OR
       SELECT SID, SERIAL#, STATUS FROM V$SESSION WHERE SADDR=SESSION_ADDR;

    c.  Kill Session:

    Now kill the session with IMMEDIATE.

    ALTER SYSTEM KILL 'SID,SERIAL#' IMMEDIATE;

4. Drop temp tablespace

DROP TABLESPACE temp INCLUDING CONTENTS AND DATAFILES;

5. Recreate Tablespace Temp

CREATE TEMPORARY TABLESPACE TEMP TEMPFILE /u01/app/temp/temp01′ SIZE 2000M;

6 Move Tablespace Temp, back to new temp tablespace

ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp;

7. Drop temporary for tablespace temp

DROP TABLESPACE temp2 INCLUDING CONTENTS AND DATAFILES;

 No need to do shutdown when drop temp tablespace and the recreate it. If something happen with temp tablespaces e.g. : crash, corrupt, etc. Oracle database will ignore the error, but DML (insert,update,delete) and SELECT Query will suffer.

Database Security Checklist

Oracle Database Security Checklist

For a production Database, must need to check the following points for
better security : -

1. Protecting the database environment.
2. Install only what is required.
3. Lock and expire default user accounts.
4. Changing default user passwords.
5. Change passwords for administrative accounts.
6. Change default passwords for all users.
7. Enforce password management.
8. Secure batch jobs.
9. Manage access to SYSDBA and SYSOPER roles.
10. Enable Oracle data dictionary protection.
11. Follow the principle of least privilege.
12. Public privileges.
13. Restrict permissions on run-time facilities.
14. Authenticate clients.
15. Restrict operating system access.
16. Secure the Oracle listener.
17. Secure external procedures.
18. Prevent runtime changes to listener.
19. Checking network IP addresses.
20. Harden the operating system.
21. Encrypt network traffic.
22. Apply all security patches.
23. Report security issues to Oracle.

Table lock

What is Table Lock??
What is Latch???

What is LOCK TABLE ???

Use the LOCK TABLE statement to lock one or more tables, table partitions, or table sub partitions in a specified mode. This lock manually overrides automatic locking and permits or denies access to a table or view by other users for the duration of your operation.
Some forms of locks can be placed on the same table at the same time. Other locks allow only one lock for a table.
A locked table remains locked until you either commit your transaction or roll it back, either entirely or to a save point before you locked the table.
A lock never prevents other users from querying the table. A query never places a lock on a table. Readers never block writers and writers never block readers.

What is Latch??

A latch is an internal Oracle mechanism used to protect data structures in the SGA from simultaneous access. Atomic hardware instructions like TEST-AND-SET is used to implement latches. Latches are more restrictive than locks in that they are always exclusive. Latches are never queued, but will spin or sleep until they obtain a resource, or time out.


What is the difference between locks, latches, enqueues and semaphores? for DBA??
 
A latch is an internal Oracle mechanism used to protect data structures in the SGA from simultaneous access. Atomic hardware instructions like TEST-AND-SET is used to implement latches. Latches are more restrictive than locks in that they are always exclusive. Latches are never queued, but will spin or sleep until they obtain a resource, or time out.
Enqueues and locks are different names for the same thing. Both support queuing and concurrency. They are queued and serviced in a first-in-first-out (FIFO) order.
Semaphores are an operating system facility used to control waiting. Semaphores are controlled by the following Unix parameters: semmni, semmns and semmsl. Typical settings are:
semmns = sum of the "processes" parameter for each instance
(see init<instance>.ora for each instance)
semmni = number of instances running simultaneously;
semmsl = semmns

Steps for releasing lock on a table:

Finding Locks


select session_id "sid",SERIAL# "Serial",
substr(object_name,1,20) "Object",
substr(os_user_name,1,10) "Terminal",
substr(oracle_username,1,10) "Locker",
nvl(lockwait,'active') "Wait",
decode(locked_mode,
2, 'row share',
3, 'row exclusive',
4, 'share',
5, 'share row exclusive',
6, 'exclusive', 'unknown') "Lockmode",
OBJECT_TYPE "Type"
FROM
SYS.V_$LOCKED_OBJECT A,
SYS.ALL_OBJECTS B,
SYS.V_$SESSION c
WHERE
A.OBJECT_ID = B.OBJECT_ID AND
C.SID = A.SESSION_ID
ORDER BY 1 ASC, 5 Desc

Finding Blocking sessions :

select l1.sid, ' IS BLOCKING ', l2.sid
from v$lock l1, v$lock l2 where l1.block =1 and l2.request > 0
and l1.id1=l2.id1 and l1.id2=l2.id2

select s1.username '@' s1.machine ' ( SID=' s1.sid ' ) is blocking '
s2.username '@' s2.machine ' ( SID=' s2.sid ' ) ' AS blocking_status
from v$lock l1, v$session s1, v$lock l2, v$session s2 where s1.sid=l1.sid and s2.sid=l2.sid
and l1.BLOCK=1 and l2.request > 0 and l1.id1 = l2.id1 and l2.id2 = l2.id2 ;

Sessions with highest CPU consumption :
SELECT s.sid, s.serial#, p.spid as "OS PID",s.username, s.module, st.value/100 as "CPU sec"
FROM v$sesstat st, v$statname sn, v$session s, v$process p
WHERE sn.name = 'CPU used by this session' -- CPU
AND st.statistic# = sn.statistic#
AND st.sid = s.sid
AND s.paddr = p.addr
AND s.last_call_et <> (SYSDATE - 240/1440) -- sessions logged on within 4 hours
ORDER BY st.value;

Sessions with the highest time for a certain wait  :

SELECT s.sid, s.serial#, p.spid as "OS PID", s.username, s.module, se.time_waited
FROM v$session_event se, v$session s, v$process p
WHERE se.event = '&event_name'
AND s.last_call_et <> (SYSDATE - 240/1440) -- sessions logged on within 4 hours
AND se.sid = s.sid
AND s.paddr = p.addr
ORDER BY se.time_waited;

Sessions with highest DB Time usage :

SELECT s.sid, s.serial#, p.spid as "OS PID", s.username, s.module, st.value/100 as "DB Time (sec)"
, stcpu.value/100 as "CPU Time (sec)", round(stcpu.value / st.value * 100,2) as "% CPU"
FROM v$sesstat st, v$statname sn, v$session s, v$sesstat stcpu, v$statname sncpu, v$process p
WHERE sn.name = 'DB time' -- CPU
AND st.statistic# = sn.statistic#
AND st.sid = s.sid
AND sncpu.name = 'CPU used by this session' -- CPU
AND stcpu.statistic# = sncpu.statistic#
AND stcpu.sid = st.sid
AND s.paddr = p.addr
AND s.last_call_et <> (SYSDATE - 240/1440) -- sessions logged on within 4 hours
AND st.value > 0; 
 


Step1:To verify the lock object Here is the import query:
---------------------------------------------------------------

SELECT o.owner, o.object_name, o.object_type, o.last_ddl_time, o.status, l.session_id, l.oracle_username, l.locked_mode
FROM dba_objects o, gv$locked_object l
WHERE o.object_id = l.object_id;

Step 2: Find the serial# for the sessions holding the lock:

SQL> select SERIAL# from v$session where SID=667;

SERIAL#
----------
21091

SQL> alter system kill session '667,21091';

System altered.

create database links

Re-create database links : -

To check for the existence of database links, use SQL*Plus on the database server node to connect to the Applications database instance as APPS and run the following query:

      $ sqlplus apps/<apps password>
      SQL> select db_link from dba_db_links;

If the EDW_APPS_TO_WH and APPS_TO_APPS database links exist, use the following commands to drop and re-create them:

      $ sqlplus apps/<apps password>
      SQL> alter session set global_names=false;
      SQL> drop database link EDW_APPS_TO_WH;
      SQL> drop database link APPS_TO_APPS;

      SQL> create database link EDW_APPS_TO_WH connect to apps
           identified by <apps password> using
           '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<host name>)
           (PORT=<port number>))(CONNECT_DATA=(SID=<ORACLE_SID>)))';

      SQL> create database link APPS_TO_APPS connect to apps
           identified by <apps password> using
            '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<host name>)
           (PORT=<port number>))(CONNECT_DATA=(SID=<ORACLE_SID>)))';

where <host name> is the host name of the database server node, <port number> is the port number of the new Net8 listener for the database instance, and <ORACLE_SID> is the ORACLE_SID of the database instance. If you have custom self-referential database links in the database instance, use the following commands to drop and re-create them:

      $ sqlplus apps/<apps password>
      SQL> drop database link <custom database link>;
      SQL> create database link <custom database link> connect to
           <user> identified by <password> using
           '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<host name>)
           (PORT=<port number>))(CONNECT_DATA=(SID=<ORACLE_SID>)))';

where <custom database link>, <user>, <password>, and <ORACLE_SID> are all as they were in the original database link definition, and <port number> is the port number of the new Net8 listener for the database instance.

Windows 8 Installation step by step

How to Install Windows 8? 

Windows 8 is Microsoft's latest operating system which is completely redesigned. It moves away from the traditional interface to a completely new interface known as Metro User Interface. The familiar start menu is now gone. Icons and windows are replaced with live tiles and magazine styled interface. Unlike any previous versions, Windows 8 and its variation RT works across multiple architectures and has been optimized for touch screen. So it will work on Intel based PCs or an ARM based tablet.
This step-by-step guide demonstrates how to install Microsoft Windows 8 Professional. You can follow this guide if you have Windows 8 basic edition or any other version as the steps are very similar.
The best way to install Windows 8 is to do a clean install. Before you start the installation process I recommend that you check Windows 8 System Requirements to ensure that your hardware is supported by Windows 8. If you don't have Windows 8 drivers for all your hardware, it is a good idea to download all the drivers from the hardware manufacturers web site and save all the necessary drivers on a CD/DVD or a USB drive before you start the installation.
Windows 8 Professional DVD is bootable. In order to boot from the DVD you need to set the boot sequence. Look for the boot sequence under your BIOS setup and make sure that the first boot device is set to CD-ROM/DVD-ROM.
 Or

Directly insert CD/DVD in DVD rom after that restart Laptop.
After few second press 5 to 10 times F12.

# few second you got Massage
select options
CD/DVD
USB
Hard-Disk

# Select CD/DVD
Press Enter...

>>>>>>>>>After few second you got next screen..........


Step 1 - Place Windows 8 DVD in your dvd-rom drive and start your PC. Windows 8 will start to boot up and you will get the following screen with a rotating progress bar.

Step 2 - The next screen allows you to setup your language, time and currency format, keyboard or input method. Choose your required settings and click next to continue. 

Step 3 - The next screen allows you to install or repair Windows 8. Since we are doing a clean install we will click on "install now". 

Step 4 - The setup process starts as shown.

Step 5 - At this stage you need to type your product key that came with your copy of Windows 8. Click next once you have entered the product key correctly.

Step 6 - Read the license terms and tick I accept license terms. Then click next to continue. 

Step 7 - Choose the type of installation you want. Since you are doing a clean install you need to click on custom.

Step 8 - Choose where you would like to install Windows 8. If you have one hard drive you will get an option similar to the image below. You can click next to continue then go to step 12.

If you have more than one drive or partition then you need to select the appropriate drive and click next. At this stage you can go to step 12.

If you want to partition a large drive then do not click next. Go to step 9.

Step 9 - If you want to partition an existing drive then click new. Choose the size of the partition and click apply.

Step 10 - Click OK to create the partition. Windows will create additional system partition which you don't have to worry about.

Step 11 - You will notice that you have 3 partitions. Partition 1 is system reserved. Leave this partition alone. Partition 2 is 30GB primary partition that was created in the last step. The third partition is unallocated which means it is not being used. You can however format it and use it as a second storage drive. This can be done after windows installation is finished so I will leave it for now.
Choose partition 2 (Primary Partition). This is where I will install Windows 8. Click next to continue.

Step 12 - At this stage Windows starts to copy files to your hard drive and begins the installation. This process might take a few minutes depending on your computer specification. Now is a good time to grab yourself a coffee.

Step 13 - When all the necessary files are copied Windows 8 will automatically restart as shown.

Step 14 - You will go through various progress bar and information messages as shown on the following images. Windows might restart automatically second time.

Step 15 - You are now presented with "Let's go through a few basics" screen. It will automatically select personalize option.

Step 16 - Choose your PC name and personalize the color. 

Step 17 - Here you can choose express settings or choose customize. I will choose customize to make further customization.

Step 18 - Choose Yes, turn on sharing and connect to devices.

Step 19 - Help protect and update your PC. Choose your preferred option and click next.

Step 20 - Send Microsoft info to help make Windows and apps better. Choose your preferred options or leave the default settings. Click next to continue.

Step 21 - Check online for solutions to problem. Choose your preferred options or leave the default settings. Click next to continue.

Step 22 - Sign in to your PC. Here you can login to your PC using a Microsoft email account such as your hotmail account.

If you do not have a Microsoft account you can create one by clicking Sign up for a new email address. Go to Step 23.

If you don't want to create an email account and prefer to create a local user name, click Sign in without a Microsoft account. Go to step 24.

Step 23 - Sign up for a new email address. If you want to create a new email account you need to complete the form below.

Step 24 - Click local account

Step 25 - Here you can choose a local user name and password. Choose finish to continue.

Step 26 - At this stage Windows starts to finalize your settings. You will get the following information screen as the installation moves forward.

 

Step 27 - As Windows 8 setup progresses you are given a presentation of the new interface. Its shows you how swiping the edge of the screen brings up the Charm bar. Using the Charm bar you can do a search or change your settings. It also demonstrates how you can hover your mouse on the bottom or top left corner to access the switch list. This list shows all open applications and allows you to switch between them.

Step 28 - Soon as the demonstration finishes windows moves into the final stages of the setup.

Step 29 - Finally the setup process is finished and you are presented with a completely new and unfamiliar Metro user interface. You have your most common application right in front of you. Clicking on any tiles will launch that application. At this point you can start using your computer. However, it may not be fully configured. You need to make sure that all the hardware is detected correctly and the necessary device drivers are installed. This can be done from the device manager.

Step 30 - To go to device manager click search on charm bar on the right. Then type devmgmt.msc. Click on the devmgmt icon on the left.

Step 31 - You will see all your hardware listed as shown on the image below. You need to check if you have any yellow exclamation marks next to the name of the devices, similar to "Base System Device" on the image below. This indicates that the driver has not been installed for this device.

At this stage you can install the driver for this device. To do so, Right Mouse click on Base System Device -> Update Driver Software...

Step 32 - You can choose to "Search automatically for updated driver software" or "Browse my computer for driver software". If you have the driver CD or if the driver is on a USB drive then choose "browse my computer for driver software". Window 8 will search and install the driver from the CD or you can locate the driver manually.

Once you have removed all the yellow exclamation marks from the device manager your Windows 8 configuration would be fully complete.

 

 ****************END******************

ADADMIN Utility

How to use adadmin in R12?

AD ADMIN UTILITIES

AdAdmin

Ad admin is a utility which is used to perform

Login as a Applmgr user:
[applmgr@apps ~]$ adadmin

Preliminary Tasks:

1. Running the environment file.
2. Verifying that ORACLE_HOME set properly.
3. Ensuring that ORACLE_HOME/bin and AD_TOP/bin are in your path.
4. Shutting down the concurrent managers when relinking certain files or performing certain database tasks.
5. Ensuring Sufficient temporary disk space.

Ad administration prompts:
Your default directory is '/u01/app/apps/uatappl'.
Is this the correct APPL_TOP [Yes]

Filename [adadmin.log] :

APPL_TOP is set to /u01/app/apps/uatappl

Please enter the batchsize [1000] :

Enter the password for your 'SYSTEM' ORACLE schema: manager

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







Ad admin Log files:

The main AD Administration log file is called adadmin.log by default. This name can be
Changed when starting up AD Administration.

Errors and warnings are listed in the log file
/u01/app/apps/uatappl/admin/UAT/log/adadmin.log


General Applications file menu


There are five functional choices in the generate applications file menu.

1. Generate Message Files:
This task generates message binary files in the $PROD_TOP/mesg directory from oracle application object library tables.

We generally perform this task only when instructed to do so in a readme file of a patch.

2. Generate Form Files:This task generate binary oracle forms file for all installed languages from the form definition files. Extension (*.fmx)

Perform this task whenever we have issue with a form or set forms.

Oracle application uses these binary files to display the data entry forms.

When we choose Generate form files:
It prompts following:


Generate Report files:
This task generates binary report files for all installed languages. Extension of the file name like (*.rdf)

When we choose Generate report files menu, it prompts the following.


Generate Graphics files:
This task generates Oracle graphics files for all installed languages. Extension of the file name like (*.ogd)

The serious of prompts and actions in this task are very similar to the prompts and actions in the Generate form files task.


Generate Product JAR files:
This generate product jar files task prompts
Do you wish to force generation of all jar files? [No]
If we choose No, it only generates JAR (Jave Archive) files that are missing or out of date.
Choose yes for this option when generating JAR files after upgrading the developer technology stack or after updating your Java version.

Maintain Applications Files tasks


Relink Application programs:
This task relinks all your oracle applications binary executables.
Select this task after us:
1. Install new version of the database or a technology stack component.
2. Install an underlying technology component used with oracle applications.
3. Apply a patch to the application technology stack.
4. Apply a patch to the operating systems

These tasks execute AD relink utility. Use AD admin, not the AD relink utility directly, to relink non AD-executables.
Create Applications environment file:
Select this task when you want to:
1. Create an environment file with settings that are different from your current environment file.
2. Recreate an environment file that is missing or currept.

Copy files to destinations:
The copy files to destinations task copies files from each product area to central locations where they can easily referenced by oracle applications.

Use this option to update the java, HTML and media files in the common directories (such as JAVA_TOP, OA_TOP) when users have issues accessing them.

1. Java file are copied to JAVA_TOP
2. HTML files are copied to OAH_TOP
3. Media files are copied to OAM_TOP

Convert Character Set:

1. This task converts the character set of all translatable files in APPL_TOP.
2. You should select this task when changing the base language or adding additional languages to oracle applications
3. You may need to convert database character set and file system character set to one that will support the additional languages.

Maintain snapshot information:

1. This task record details for each file in the APPL_TOP (like file name and file version).
2. They also record summary information’s about patches that have been applied to the APPL_TOP.
3. The maintain snapshot information task stores information about files, file versions and bug fixes present in an APPL_TOP.
4. You must run Maintain snapshot information option once for each APPL_TOP before you apply any patch that contains a “compatible feature prereq” line on that APPL_TOP.

Check for Missing files:

1. The check for missing files task verifies files needed to install, upgrade, or run oracle applications for the current configuration are in the current APPL_TOP.
2. Choose this task if you suspect there are files missing in your APPL_TOP.

Maintain Database Entries tasks:



Validate Apps Schema:

Validate apps schema task run SQL script (advrfapp.sql) against the apps schema to verify the integrity of the schema.
It determines:

1. Problems you must fix(not specific to apps schema)
2. problems you must fix(specific to apps schema)
3. Issues you may want to address(specific to apps schema)
A report called APPSschemaname.lst is produced in APPL_TOP/admin//out.
This report contains information about how to fix the issues. We can find following things by running the Validate Apps schema.

1. Missing or invalid package.
2. Missing or invalid synonyms.
3. Invalid objects in apps schema.

This task is more effective if run:

1. Immediately after an upgrading or applying maintenance pack
2. After a patch is applied.
3. After performing export/import (migration)
4. When doing custom development in the apps schema.

Recreate Grants and Synonyms:

This task recreates grants and synonyms for oracle application public schema (applsyspub)
Recreate grants on some packages from system to apps

Run this task when grants and synonyms are missing from the database. This may occur as a result of
1. Custom development
2. Incomplete database migrations
3. Patches and administrative sessions that failed to run successfully to completion
Maintain multi-lingual tables:

MLS or multilingual support is oracle application’s ability to operate in a multi languages simultaneously. When running Maintain multi-lingual task you can select the number of parallel workers. In generally run during the NLS install and maintenance processes. This task runs the NLINS.sql script for every product. It invokes pl/sql routines that maintain multilingual tables and untranslated rows.

Check Dual Tables:

This task looks for a dual table accessible by oracle applications and ensures the correct grants are set up. If such table not exists or if an existing DUAL table has more than one row, AD administration displays error. If a DUAL table containing only one row exists, AD admin completes successfully.

Maintain multiple reporting currencies:

This option varies depending on whether you currently have multiple reporting currencies (MRC) enabled or not.
If MRC functionality is implemented in your database, the option reads maintain multiple reporting currencies.

Convert to multiple organizations:

To convert in to multiple-org does the following thing:

1. Confirms that you want to run the task
2. Asks for the number of parallel workers
3. Create script to disable and re-enable triggers in the APPS schema
4. Disable all triggers in the apps schema
5. Converts seed data and transaction data to multiple organizations in parallel.
6. Re-enable all previously disabled triggers in the apps schema.

Compile and Reload Database Entries tasks:

Compile Apps Schema:

This task compiles uncompiled program units (pl/sql and java) in the apps schema.
You can perform this task with multiple workers.
When running this task, AD administration prompts,
Run Invoker's Rights processing in incremental mode [No]?
Type Yes at this prompt to run Invoker Rights processing only on packages that have changed
Since Invoker Rights processing was last run or accept the default to run Invoker Rights
Processing on all packages.
During the upgrade progress.

Compile Menu Information:

This option compiles menu data structures.
Choose this task after uploading menu entries.

It asks if you want to force compilation for all menus,

1. If you choose the default [no] only menus with changes are saved
2. If you enter yes all menus are compiled

Compile flexfield:

Run this task if the readme of a patch indicates that this step should be performed.
Details of the task with a list of compilation status of every flexfield are written to a log file.
The name of the log file is in the format .req. The main AD Administration log file contains the exact name of this log file.

Reload JAR Files to Database:

This option runs the loadjava utility to reload all appropriate oracle applications
JAR files into the database.

Change Maintenance mode:

1. Must be enabled before patching oracle applications
2. Improves patching performance
3. Restricts users access to system
4. Is enabled and disabled using AD administration







adadmin

Continuing our discussions on ad utilities today i will discuss about the most commonly used ad utility adadmin. Adadmin is a utility that performs a number of tasks required from maintaing and administering an Oracle Applications instance.

On a broad level the tasks performed by adadmin can be categorized into database activities and Applications filesystem management tasks.

In addition to these, adadmin in 11.5.10 onwards you can use adadmin to put the system in Maintenance Mode also. Maintenance mode is special mode introducted to facilitate maintenance tasks like patch application.

Before you run adadmin you must ensure the following.

Set your applications environment-

[applmgr@gayatri10 ~]$ cd /oracle/PROD/apps/apps_st/appl/

[applmgr@gayatri10 appl]$ . APPSPROD_gayatri10.env

Ensure that you have sufficient space in tmp disk.


root$ du -sh "/tmp"

For certain adadmin task you may require to shutdown your concurrent managers

You can run adadmin by typing adadmin at the command pront afdter seeting the environment.

[applmgr@gayatri10 scripts]$ adadmin

At the time of execution adadmin prompts you to verify and enter several information pertaining to your applications installation like APPL_TOP location ,ORACLE_HOME.adadmin log file name,batch size etc.

Adadmin can also be run in a non interactive mode. This is accomplished by creating a defaults file.The defaults file must be place at the location $APPL_TOP/admin/[sid]/

You can create the defaults file with the following syntax

$adadmin deafultsfile=$APPL_TOP/admin/[sid]/samtask.txt

Next time you can run adadmin for the same task by specifying the interactive=no option.

adadmin \
defaultsfile=APPL_TOP/admin/vis/samtask.txt \
logfile=adadmin_091306.log workers=9 \
interactive=no

If your previous session of adadmin had encountred with problems adadmin promts you to either continue with your old session or start with a frest session as show below

Your previous AD Administration session did not run to completion.
Do you wish to continue with your previous AD Administration session [Yes] ?


The main menu of adadmin presents you with the following six choices

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

First two options are related to maintaining applications file system the second twop options relate to database activities ,the fifth option here is used to put the system in maintenance mode and bring it back from maintenance mode.

Under the Generate Applications Files Menu you can perform the following tasks

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

1. Generate message files

2. Generate form files

3. Generate report files

4. Generate graphics files

5. Generate product JAR files

6. Return to Main Menu


Under the Maintain Applications Files menu you can perform the following tasks

Maintain Applications Files
----------------------------------------

1. Relink Applications programs

2. Create Applications environment file

3. Copy files to destinations

4. Convert character set

5. Maintain snapshot information

6. Check for missing files

7. Return to Main Menu

Under the Compile/Reload Applications Database Entities menu you can perform the following tasks

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

Under the Maintain Applications Database Entities menu you can perform the following tasks

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. Maintain Multiple Reporting Currencies schema

6. Return to Main Menu

Under the Change Maintenance Mode you can do the following

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

If you noitice the message this menu selection also shows the maintenance status (disabled in our case) of the system.

You can also forcefully exit adadmin at any point of time by typing 'abort',This will however result in a unclean exit of adadmin and the next time when you run adadmin you will be prompted with the option to start fresh or continue with the previous session as described earlier.