Apps DBA sites

http://www.onlineappsdba.com/

http://appsdbainfo.com/

What is a Cold Backup

Answer: Cold backup also referred to as an offline backup, is the backup performed while the database is in a cold state ( No Activity ). To ensure consistency in the backup, the database needs to be shutdown while perfoming this kind of backup.

Datafiles, Control Files, Redo Log Files and Parameter Files must be copied to offline storage using the copy utility.

What is the difference between logical and physical backups?

Answer: Logical backup means backing up the individual database objects such as tables, views , indexes.. using the utility called EXPORT, provided by Oracle. The objects exported in this way can be imported into either same database or into any other database. The backed-up copy of information is stored in a dumpfile, and this file can be read using another utility called IMPORT. There is no other way you can use this file.
Physical backups rely on the Operating System to make a copy of the physical files like data files, log files, control files that comprise the database.

How do I find the database archive log status

Answer: Invoke svrmgrl and issuse the following command
ARCHIVE LOG LIST Why does oracle provide Ocopyxx, instead of using copy utility on NT for online backups

Answer: NT copy utility locks the file to prevent access to the file while it is being copied.

Ocopy opens the file using CreateFile() with the FILE_SHARE_READ and FILE_SHARE_WRITE flags. This allows for online backups to be performed and archived redo logs are used for recovering from inconsistencies during backup

Which is better to use, logical backup or physical backup?

Answer: Physical backups are always the best to use because of the ease in restoring and recovering databases from failures.

Logical Backups should be used in conjunction with physical backups to provide redundancy and ease of recovery in case any data is corrupted or objects are dropped due to user errors

Question: Is there a way to read the contents of redo log files and control files?

Answer: NO and Yes

You should not be opening redo logs or control files for reading. Thats the No answer.

Oracle starting with 8i provides a tool called the Log Miner which can be used to extract the do and undo sql for individual transactions from the redo logs.

There is a very good article written by Biju Thomas and you can find the link in the Technical Docs Section of this site.

What is the difference between recovering and restoring?

Answer: Restoring involves copying (most likely from tape) a backup file to replace a damaged datafile. Recovery is the process of applying redo logs to the database to roll it forward.

In case of a datafile loss, you would first restore the datafile from your backup system and then recover the database.

hat are the best backup plan and quick recovery ?

Answer: this is a environment specific solution....
(Tim Cheng Writes ...)
Our production DB is 7 x 24 for telcom company.And we need backup 300+ Gb and
quick recovery when the storage failures.
Our backup plan are below:
1. enable archive mode
2. put addition redo members to another storage.
3 hot backup for all data files to another storage (We take 5 hours for 300+ Gb every day)
4. logical backup for all db structure & important tables.
5 setup a standby DB on another server for contingency
6 select OPS(Oracle Parallel Server) option

what is incrementa export or incremental backup
and how to do it.
i am using oracle8 in sun solaris platform

Answer: An incremental export is an export taken since the last full or cumulative export. The incremental export only exports the objects ( ex : tables ) that have changed since the last full or cumulative export.

An incremental backup acts at a DATA BLOCK level when performed with RMAN. This makes the database backups a lot smaller when there are minor changes to a large database. Only changed blocks since the last backup are written to the backup set.

Concurrent Manager Secrets
Description about important CM tables

FND_CONCURRENT_QUEUES
TARGET_NODE
-Used to indicate where additional processes should be started
-Used by managers to determine if they should shut themselves down for migration
-Managers compare parameter value passed on startup to this value
-Used by UI to indicate where processes exist (not entirely accurate in migrating case)
-Assigned by ICM based on primary, secondary settings

NODE_NAME
-Indicates primary node for PCP - directed load
-Where processes should be started unless node is not online or has been determined to be unavailable
-If no node is specified ICM will assign target node by default to NODE_NAME2
-Indicates secondary node for PCP - directed load failover
-Only assigned as TARGET_NODE if primary node is unavailable

FND_CONCURRENT_PROCESSES
NODE_NAME
-Indicates where the manager process is running
-Also indicates where the manager's files exist
-Populated using value from uname() (physical machine name)
-Used by ICM when terminating process
-Used when viewing log file in UI
-Used by Purge Program to delete process logfile
-Could be used for workload statistic calculations
-Will likely be used by RPMs to attempt to find a local OPP
-Similarly used in 11i.X to locate Reports Server

Concurrent Request log/Out:
FND_CONCURRENT_REQUESTS
LOGFILE_NODE_NAME, OUTFILE_NODE_NAME
-Indicate where files exist
-Used in UI for File Viewing
-Used by Purge Program to delete files
-Value populated by mgr process, based on its own node




FND_NODES

NODE_NAME
-Indicates node name where DBC file is located.
-Adgendbc.sh script creates DBC file.

SERVER_ID
-Will be used to authenticate connections from the node.
-Updated by adgendbc.sh which calls AdminAppServer API.

FNDSVCRG
The FNDSVCRG executable is triggered from the control scripts before and after a script starts or stops the service. FNDSVCRG will connect to the database to verify the configuration of the Seeded GSM Service. If the service in question is not enabled to be managed under GSM, the FNDSVCRG executable will do nothing and exit. The script would then continue to perform its normal start/stop actions. If the service is enabled for GSM management, the FNDSVCRG executable will update service-related information in the database including the environment context, the current service log file location, and the current state of the service


Phase status Description

PENDING/Normal -Request is waiting for the next available manager.
PENDING/Standby-Program to run request is incompatible with other program currently running.
PENDING/Scheduled-Request is scheduled to start at a future time or date.
PENDING/Waiting-A child request is waiting for its Parent request to mark it ready to run. For example, a request in a request set that runs sequentially must wait for a prior request to complete.
RUNNING/Normal-Request is running normally.
RUNNING/Paused-Parent request pauses for all its child requests to finish running. For example, a request set pauses for all requests in the set to complete.
RUNNING/Resuming -All requests submitted by the same parent request have completed running. The Parent request resumes running.
RUNNING/Terminating-Request is terminated by choosing the Cancel Request button in Requests window.
COMPLETED/Normal-Request completed successfully.
COMPLETED/Error-Request failed to complete successfully.
COMPLETED/Warning-Request completed with warnings. For example, a request is generated successfully but fails to print.
COMPLETED/Cancelled-Pending or Inactive request is cancelled by choosing the Cancel Request button in the Requests window.
COMPLETED/Terminated-Request is terminated by choosing the Cancel Request button in the Requests window.
INACTIVE/Disabled-Program to run request is not enabled. Contact your system administrator.
INACTIVE/On Hold-Pending request is placed on hold by choosing the Hold Request button in the Requests window.
INACTIVE/No Manager-No manager is defined to run the request. Check with your system administrator. A status of No Manager is also given when all managers are locked by run-alone requests.

How do you check the status of the managers from the OS
-Unix command: $ ps -ef grep LIB
-Note that the Internal Concurrent Manager can be spotted in this
listing because its command is "FNDLIBR FND CPMGR ..." whereas
the others show more like "FNDLIBR FND Concurrent_Processor ..."
-The Unix userid shown in the first column of this listing is
crucial: these concurrent manager processes should be owned by
the same Unix userid which owns the Applications code ($APPL_TOP
and its subdirectories); this user is usually referred to as
"applmgr"


Where do all the files generated by the concurrent managers go

-The ICM log file goes in the $FND_TOP/log directory and usually matches
std.mgr.
-The workers' log files go in $FND_TOP/log and match W*.mgr
-The concurrent request log/out files go under the product top directory associated with the product running the request: for instance, log/out files for AR reports go under $AR_TOP.
-The log files for concurrent requests go in the $APPLLOG subdirectory under the appropriate product top directory and match l*.req
-The out files for concurrent requests go into the $APPLOUT subdirectory
-If APPLCSF is set, it should point to the complete path to a directory which has $APPLLOG and $APPLOUT subdirectories. This $APPLCSF directory will be used instead of the various product top directories to write
*all* the log/out files to.



The most common concurrent manager problems are caused by file
protection problems at the Unix level.

-Are you starting the concurrent managers as applmgr?
-Can applmgr do the following to create a file in the
$FND_TOP/$APPLLOG directory?
$FND_TOP/$APPLOUT directory?
Unix: $ touch $FND_TOP/$APPLLOG/a
-If this fails, who owns the directory?
Unix: $ ls -ld $FND_TOP/$APPLLOG
-Is this directory a symbolic link? if so, what are the protections
on the directory it points to?
-Are you running out of disk space on this partition? i-nodes?
Unix: $ df -k
Unix (on some systems) to check i-nodes: $ df -i
-Is APPLCSF set?
-If so, can applmgr do this?
Unix: $ touch $APPLCSF/$APPLLOG/a
-Check $APPLOUT (usually "out") directories just like log directories.


Concurrent Manager tables

FND_NODES
FND_CONCURRENT_PROCESSES (fcproc)
FND_CONCURRENT_REQUESTS (fcr)
FND_CONCURRENT_QUEUES (fcq)
FND_CONCURRENT_PROGRAMS (fcprog)
FND_EXECUTABLES
FND_CP_SERVICES
FND_CONCURRENT_QUEUE_SIZE
FND_CONCURRENT_QUEUE_CONTENT
FND_CONCURRENT_PROGRAM_SERIAL
FND_CONCURRENT_TIME_PERIODS
FND_CONCURRENT_PROCESSORS

Multi Node to Single Node Cloning

With Oracle Applications 11.5.10 the ability to clone from a multi node to a single node system using rapid clone has now been certified.

This is accomplished by the Shared APPL_TOP and Merging APPL_TOP features.

Source System here refers to the multi node system to be cloned
Target System refers to the newly to be created single node system
Applications Version 11.5.10
Operating System Linux ES 4

The following Steps are required to be performed on the source system

1. Apply application tier patches using adpatch

Apply patch 4038964
Apply patch 4175764

Both the above patches are include in the consolidated update 2 or CU2 so in case you are on 11.5.10.2 or later you can ignore this step.

2. Maintain snapshot information

Log in as the applications user on each application tier node and run 'Maintain Snapshot Information' by using adadmin.

3. Merge existing APPL_TOPs

Log in to the primary node of your application tier as the application user user and run:

$ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl appsTier merge

This will prompt you with option to merge secondary nodes

Now log in as the applications user to each of the secondary application tier nodes being merged and run:

$ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl appltop merge

4. Prepare the source system database tier.

Log on to the database tier of the source system as the oracle user and run the following commands:

$ cd [RDBMS ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl dbTier

With this all the pre clone tasks on the source system have been completed.

The next set of tasks is required to be carried out on the target system that is the system on which you wish to place the merged single node instance.

1. Create OS user accounts

Create a OS user account for your applications

$ useradd -g dba -d [home_directory] -p password username

Similarly create a OS user account for your database

2. Modify the orainventory to reflect the new location

$ vi /etc/oraInst.loc

3. Copy the following application tier directories

Copy the following application tier directories from the primary node of your source system to the target application tier node, retaining the original directory structure:

– [APPL_TOP]
– [OA_HTML]
– [OA_JAVA]
– [COMMON_TOP/util]
– [COMMON_TOP/clone>
– [806 ORACLE_HOME]
– [iAS ORACLE_HOME]

4. Copy the required files for merging

Log in as the applications user to each of the secondary source nodes and recursively copy:

Directory [COMMON_TOP]/clone/appl
- to -
directory [COMMMON_TOP]/clone/appl on the target system node

Before proceeding with the next steps you must shutdown your oracle applications services and the database on the source system

5. Copy the database tier file system

Log on to the source system as the database user

Copy the database (DBF) files from the source to the target system
Copy the source database ORACLE_HOME to the target system

After this you can now startup the database and applications services on your source system and release it for use.

6. Configure the target system database server

Log on to the target system as the database user and type the following commands to configure and start the database:

$ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
$ perl adcfgclone.pl dbTier

This will prompt for new ORACLE_SID, ORACLE_HOME, Port Pool, JAVA_TOP and DATA_TOP give the appropriate values matching your target system

Once successful this should start your database and listener

7. Configure the application tier server nodes

The database and its listener should remain up before executing the next set of commands.
Log in to the merged APPL_TOP node as the applications user and execute the following commands:

$ cd [COMMON_TOP]/clone/bin
$ perl adcfgclone.pl appsTier

This will prompt you new port pool for applictaion tier services as well as new APPLTOP,COMMON_TOP,ORACLE_HOME and IAS_TOP

Successful completion of this task will bring up your application tier services on the target or the cloned node.

8. Post Clone Tasks

Log in to the target system application tier node as the APPLMGR user.
Run the following tasks in adadmin for all products:
o generate JAR files
o generate message files
o relink executables
o copy files to destination

9. Clean up of the target system

Remove the temporary directory [COMMON_TOP]/clone/appl to reduce disk space usage.

How can I see if my database is running in Archive Log Mode

Answer: Startup Svrmgrl and issue the command archive log list. That will show you if you are running in an archive or noarchive log mode and also various details about log switches etc.

How to Increase the size of a tablespace

Answer: There are 2 ways to increase the size of tablespace.

1. Add an Extra Data file to the tablespace

alter tablespace users add datafile '/u01/oradata/orcl/users02.dbf' size 25m;

2. Resize the Datafile that is currently supporting the tablespace. Some versions of Oracle does not like this, and brings the instance down, so do not use this unless you are really sure.

alter database datafile '/u01/oradata/orcl/users01.dbf' resize 50M;

ow can I verify my Init.ora Parameters when the database is running

Answer: Connect to server manager and Use the command show parameter

to show all parameters that start with db, issue the following command

svrmgrl> show parameter db

How do I find my current Session Id

Answer: You can get it from the userenv('sessionid'). Here is how you can use it.

select osuser, username,sid,serial#
from v$session
where audsid = userenv('sessionid');

Can some one tell me how to change the db_name of the database without recreating the db

Answer: http://www.dbasupport.com/dbres/Technical_Docs/Database_Administration/General_Tasks/ ow can I find whether datafiles are in Auto Extend mode or not?

Answer: Query the DBA_DATA_FILES view and see the AUTOEXTENSIBLE column.

Example:
select FILE_NAME, AUTOEXTENSIBLE from dba_data_files;

If AUTOEXTENSIBLE is YES then your file is in auto extend mode. Then Find the corresponding MAXBYTES and INCREMENT_BY columns from the same view.
MAXBYTES is the maximum size that the file can grow and the INCREMENT_BY is the minimum size of the increments added to the file when it extends.

How can I drop a database?

Answer: To drop a database, remove its datafiles, redo log files, and all other associated files (control files, parameter files, archived log files).

To view the names of the database's datafiles and redo log files, query the data dictionary views V$DATAFILE and V$LOGFILE.

Why does a user get an error of not having quota after upgrading from Oracle7 to Oracle 8

Answer: IN ORACLE 7.3 ONCE USER IS GRANTED RESOURCE ROLE ,HE CAN ENJOY UNLIMITED SPACE ON ALL TABLESPACES. WHERE AS IN
8 ON WARDS U GOT TO SPECIALLY SAY
QUOTA UNLIMITED ON <>. How to maximize and efectively use of Audit Trail ? How to manage the growth of audit trail tables ?

Answer: These are extremely general questions and hard to answer.
Maximizing and effectively using Audit Trail - About the only general rules I know of are

1. Know why you're auditing. If you don't have a specific reason for auditing, don't do it! It slows down overall system performance.

2. Once you know why you're auditing, select auditing options that are as specific to your purpose as possible. For instance, if you're concerned about insertions into one table, DON'T audit on all insertion statements. Just audit insertion statements in the specific table. This minimizes the amount of audit record writing.

Controlling Audit Trail Size - The more critical this is to you, the more frequently you need to go in and clean up the audit trail. This involves either deleting records that are of no interest or moving the records to another table if you want to keep them. If you review all the records and determine that there is nothing of interest, truncate the table. If you find you are frequently truncating the table, you might want to reconsider whether or not you really need to be auditing.

Finally, bear in mind that Oracle auditing is event-based, not value-based. This may change your decision on whether or not to turn auditing on.

How do I find the name of the database I am connected to?

Answer: The Database name can be found through many views . The view everyone as access to is the GLOBAL_NAME.

SELECT GLOBAL_NAME FROM GLOBAL_NAME;

submitted by: faq Are ther any procedures instead of analyzing objects individually?

Answer: As of Oracle 8, it is possible to utilize a technique instead of analyzing schema objects individually. Analyzing a table, cluster, or index can affect current shared SQL statements, which are statements currently in the shared pool. Whenever an object is analyzed to update or delete statistics, all shared SQL statements that reference the analyzed object are flushed from memory so that the next execution of the statement can take advantage of the new statistics. The following procedures are now available following procedures:

DBMS_UTILITY.ANALYZE_SCHEMA() - This procedure takes two arguments - the name of a schema and an analysis method ('COMPUTE', 'ESTIMATE', or 'DELETE'). It gathers statistics on all of the objects in the schema.

DBMS_DDL. ANALYZE_OBJECTS() - This procedure takes four arguments - the type of an object ('CLUSTER', 'TABLE', or 'INDEX'), the schema of the object, the name of the object, and an analysis method ('COMPUTE', 'ESTIMATE', or 'DELETE'). It gathers statistics on the object.

Need to apply Patch Set 7.3.4.5 to production instance.
Can someone give me the proper steps to do it using oracle installer

Answer: Patch set application Notes is included in the patch set and please refer to them since they differ based on the OS and patchlevel you are upgrading from

submitted by: Nancy

How do I connect to a default user, irrespective of the loginname and pwd given at the logon screen?

Answer: In the File glogin.sql add the last line as connect username/password@databse.
The connection will be directed to the above mentioned databse everytime

Question: Oracle complained of a bad block in table. How can I retrieve the data other than the data that is in the bad block

Answer: First thing you need to do is find the bad block ids. To do this you can run dbverify. Lets assume our block id is 1234

Now find the segment name by running this query
select segment_name, segment_type, block_id, blocks
from dba_extents
where (1234 between block_id and (block_id + blocks - 1))
/

Once you have the bad segment name, its better to create a temporary table with good data if the segment is a table. If the segment is an index, drop the index and recreate it.

create table good_table
as
select * from bad_table
where rowid not in
( select /*+index(bad_table, any_index)*/ rowid
from bad_table
where substr( rowid, 1, 8 ) = 1234)

AutoConfig is a tool for configuring an Applications instance using standard

utilities. It manages your Release 11

i configuration files, such as httpd.conf,

jserv.properties, and appsweb.cfg.

All the information required for configuring an Applications instance is collected in

a repository, called the Applications Context. AutoConfig uses information from the

Applications Context file to generate all configuration files and update database

profiles.

Rapid Install installs an environment compatible with AutoConfig. There is an

Applications Context file for both the applications and the database tier. The

applications tier Context file is an xml file in /admin. In Release

11.5.9, this Applications Context file is named .xml. If you

migrated to AutoConfig in a release earlier than Release 11.5.9, this Applications

Context file is named .xml. The Applications Context file for the database tier

is in /appsutil and is named

.xml.

There are two ways your configuration can be changed: run the Context Editor or

apply a patch that contains a new version of a file controlled by AutoConfig. When

you change the Applications Context file with the Context Editor, or when a patch

changes any associated template, you can run AutoConfig to propagate the new

values to the configuration files in both the APPL_TOP technology stack and in the

ORACLE_HOME technology stack.

The Way to run Autoconfig:

AutoConfig generates the new configuration files for the APPL_TOP and the Oracle

Homes in the associated techstack. AutoConfig uses the parameters stored in the

Applications Context file and system configuration templates to create new process

control scripts and update system profiles.

1.

Log on as applmgr and set the environment.

2.

Stop all server processes.

3.

Start AutoConfig on the application tier.

bash-2.05$ cd gmnphonecomn/admin/scripts/GMNPHONE_TSS2/
bash-2.05$ pwd
/grmnphone/gmnphonecomn/admin/scripts/GMNPHONE_TSS2
bash-2.05$ ls
adalnctl.sh adautocfg.sh adexecsql.pl adfrmctl.sh adstpall.sh gsmstart.sh
adapcctl.sh adcmctl.sh adfmcctl.sh adpreclone.pl adstrtal.sh jtffmctl.sh
adaprstctl.sh addisctl.sh adfmsctl.sh adrepctl.sh adtcfctl.sh sqlnet.log

bash-2.05$ adautocfg.sh
Enter the APPS user password:
AutoConfig is configuring the Applications environment...

AutoConfig will consider the custom templates if present.
Using APPL_TOP location : /grmnphone/gmnphoneappl
Classpath : /grmnphone/gmnphonecomn/util/java/1.4/j2sdk1.4.2_04/jre/lib/rt.jar:/grmnphone/gmnphonecomn/util/java/1.4/j2sdk1.4.2_04/lib/dt.jar:/grmnphone/gmnphonecomn/util/java/1.4/j2sdk1.4.2_04/lib/tools.jar:/grmnphone/gmnphonecomn/java/appsborg2.zip:/grmnphone/gmnphonecomn/java

Using Context file : /grmnphone/gmnphoneappl/admin/GMNPHONE_TSS2.xml

Context Value Management will now update the Context file

Using Context file : /grmnphone/gmnphoneappl/admin/GMNPHONE_TSS2.xml

Context Value Management will now update the Context file

Updating Context file...COMPLETED

Attempting upload of Context file and templates to database...COMPLETED

Configuring templates from all of the product tops...
Configuring AD_TOP........COMPLETED
Configuring FND_TOP.......COMPLETED
Configuring ICX_TOP.......COMPLETED
Configuring IEO_TOP.......COMPLETED
Configuring ABM_TOP.......COMPLETED
Configuring ECX_TOP.......COMPLETED
Configuring BIS_TOP.......COMPLETED
Configuring GL_TOP........COMPLETED
Configuring AMS_TOP.......COMPLETED
Configuring CCT_TOP.......COMPLETED
Configuring WSH_TOP.......COMPLETED
Configuring CLN_TOP.......COMPLETED
Configuring OKE_TOP.......COMPLETED
Configuring OKL_TOP.......COMPLETED
Configuring OKS_TOP.......COMPLETED
Configuring CSF_TOP.......COMPLETED
Configuring XNC_TOP.......COMPLETED
Configuring IGS_TOP.......COMPLETED
Configuring IBY_TOP.......COMPLETED
Configuring PA_TOP........COMPLETED
Configuring JTF_TOP.......COMPLETED
Configuring MWA_TOP.......COMPLETED
Configuring CN_TOP........COMPLETED
Configuring CSI_TOP.......COMPLETED
Configuring WIP_TOP.......COMPLETED
Configuring CSE_TOP.......COMPLETED
Configuring EAM_TOP.......COMPLETED
Configuring IMT_TOP.......COMPLETED
Configuring FTE_TOP.......COMPLETED
Configuring ONT_TOP.......COMPLETED
Configuring AR_TOP........COMPLETED
Configuring AHL_TOP.......COMPLETED
Configuring OZF_TOP.......COMPLETED
Configuring IES_TOP.......COMPLETED
Configuring CSD_TOP.......COMPLETED
Configuring IGC_TOP.......COMPLETED

AutoConfig completed successfully.
The log file for this session is located at: /grmnphone/gmnphoneappl/admin/GMNPHONE_TCSSUNSERVER2/log/01301355/adconfig.log

For Database

bash-2.05$ /appsutil/scripts//adautocfg.sh

How To Use AD Merge Patch
Create Source and destination directory
Copy all the patche to source directory
and run the below scripts
admrgpch -s /home/applmgr/patch10g/source -d /home/applmgr/patch10g/dest -merge_name sriharish

Executing the merge of the patch drivers -- Processing patch: /home/applmgr/patch10g/source/4888294 -- Done processing patch: /home/applmgr/patch10g/source/4888294
-- Processing patch: /home/applmgr/patch10g/source/4653225 -- Done processing patch: /home/applmgr/patch10g/source/4653225
-- Processing patch: /home/applmgr/patch10g/source/5985992 -- Done processing patch: /home/applmgr/patch10g/source/5985992
-- Processing patch: /home/applmgr/patch10g/source/6502082 -- Done processing patch: /home/applmgr/patch10g/source/6502082

Copying files...
5% complete. Copied 98 files of 1942...
10% complete. Copied 195 files of 1942...
15% complete. Copied 292 files of 1942...
20% complete. Copied 389 files of 1942...
25% complete. Copied 486 files of 1942...
30% complete. Copied 583 files of 1942...
35% complete. Copied 680 files of 1942...
40% complete. Copied 777 files of 1942...
45% complete. Copied 874 files of 1942...
50% complete. Copied 971 files of 1942...
55% complete. Copied 1069 files of 1942...
60% complete. Copied 1166 files of 1942...
65% complete. Copied 1263 files of 1942...
70% complete. Copied 1360 files of 1942...
75% complete. Copied 1457 files of 1942...
80% complete. Copied 1554 files of 1942...
85% complete. Copied 1651 files of 1942...
90% complete. Copied 1748 files of 1942...
95% complete. Copied 1845 files of 1942...
100% complete. Copied 1942 files of 1942...

Character-set converting files...
4 unified drivers merged.
Patch merge completed successfully
Please check the log file at ./admrgpch.log.