August 25, 2008

Oracle E-Business Suite R12.1 - DBA new features

I found the following are the couple of new dba features in R12.1

1. The following are the database and middle tier new verions:
Oracle Database 10.2.0.4
XDK for the Database Tier 10.2.0.4
Oracle Application Server (for Middle Tier Forms and Reports) 10.1.2.2
Oracle Application Server (for Middle Tier Java Code / Oracle Applications Framework) 10.1.3.3*
XDK for the Middle Tier 10.1.3.3*
Oracle HTTP Server 10.1.3.3*
Oracle HTTP Client 10.1.3.3*
Java SE Development Kit – JDK (for Middle Tier Java Code / Oracle Applications Framework) 6.0*
Java SE Development Kit – JDK (for Concurrent ProcessingTier) 6.0*
Oracle AS 10g Single Sign-On / Oracle Internet Directory 10.1.4.2
Oracle AS 10g Discoverer 10.1.2.2
Oracle Collaboration Suite 10.1.2
Oracle Enterprise Manager 10.2.0.2

2. AutoConfig Profiler
R12.1 AutoConfig contains an option to run in a Profiler mode. Running AutoConfig in this mode generates a performance report with timing details about each script instantiated and run by AutoConfig.

3. AutoConfig Parallelization Across Nodes
In R12.1, AutoConfig can be run in parallel on different nodes of an E-Business Suite instance. This lowers time it takes to run AutoConfig across all nodes of an EBS instance, thus shortening downtime for patching windows.

4. Shared Application Tier File System Amongst Multiple EBS Instances
This feature enables the sharing of the same file system amongst associated EBS Instances, for example PROD and PROD_BACKUP, or TEST and DEV. This guarantees that such instances are on the same patch level, reduces patching downtime and simplified dual maintenance. Sharing of the database file system is not included in this feature. Details are published as appendix B to the Oracle MetaLink Note 384248.1 titled "Sharing the Application Tier File System in Oracle E-Business Suite Release 12."

5. Middle Tier Load Balancing
This feature provides configuration support for major load balancing categories: DNS, OC4J Native, HTTP-layer (hardware/software). Details are available in Oracle MetaLink Note 380489.1 titled "Using Load-Balancers with Oracle E-Business Suite Release 12."

6. Build Context XML Utility for Cross Platform Migration
In R12.1 AutoConfig contains an Build Context XML Utility for the database tier. This utility enables and simplifies cross platform migration and database upgrades.

7. Integration with BI Publisher
Oracle Application Framework now integrates with BI Publisher so that customers can easily add a Print button to any Oracle Application Framework-based product page using personalization and publish existing Oracle E-Business Suite application data (tables) as BI Publisher reports using BI Publisher screens. Developers can also add similar buttons using the design time interface.

8. FNDLOAD - Data Type Support Enhancements
FNDLOAD is a generic seed data loader tool. Prior to Release 12.1, FNDLOAD supported CLOB data but not BLOB data in its LDT files. With Release 12.1, FNDLOAD supports BLOB data to better serve content-rich applications.

9. Workflow: Worklist - Bulk Notification Response and Bulk Notification Close
Worklist provides an Oracle E-Business Suite user with the list of notifications that ispending review. A worklist can be perceived an Inbox of items pending review within Oracle E-Business Suite. These notifications are sent from an underlying Oracle Workflow process submitted pertaining to a business transaction such as expense report approval, requisition/purchase order approval and time card approval.

The Bulk Notification Response feature provides the ability for mass response of WF worklist notifications. Oracle Workflow now lets users respond to multiple notifications of the same type at once using a Respond button on the Worklist and Notification Search pages. Oracle Workflow also lets users close multiple FYI notifications at once using a Close button on the Worklist and Notification Search pages. These features enhance user productivity by letting users handle similar notifications in bulk, rather than having to navigate to the Notification Details page for each notification individually.

10. Oracle User Management(UMX) - 360 Degree View
“360 degree” view aims to provide information in terms of “Who, What, Why and How”. When a search is made for.

To explain this feature we are providing an example. In case the user asks for “WHAT Roles does an user ABC have?” the system will also provide for “WHY that role was assigned to the user” and “HOW that role was assigned to the user”

Ref: Note:561580.1 E-Business Suite Release 12.1: Release Content Documents

.
Posted by at 1 comment:

July 23, 2008

Linux "find" command examples.

I use to use the following linux command serveral times for searching old files and delete it, like old backup files.

$ find . -mtime +7 -exec rm -f {} \;

The following url document enlighten me the FULL usage and understanding each options usage in detail.

http://www.radialsoftware.co.uk/index.php?option=com_content&view=article&id=12&catid=10&Itemid=14

.
Posted by at No comments:

July 21, 2008

OEM Agent failed after the server crashed.

Production box - 9.2.0.6 database
Suse Linux 9

Agent not started up. $ORACLE_HOME/sysman/log/emagent.trc files error shows " ORA-12541: TNS:no listener" error.

The Listener port for the prod database is 1531, the above error shows that the port is configured in targets.xml is 1521.

=> Edit $ORACLE_HOME/sysman/emd/targets.xml

-> changed port value, save and exit.

=> Stop and start the agent. Failed again with Timezone error.

---------
2008-07-21 09:54:02 Thread-1098714528 ERROR pingManager: OMS does not understand the timezone region of the agent. Either start the OMS using the extended list of time zones supported by the database or pick a value of time zone from /oracle/oem_agent/agent10g/sysman/admin/nsupportedtzs.lst , update the property 'agentTZRegion' in the file /oracle/oem_agent/agent10g/sysman/config/emd.properties and restart the agent.A value which is around an offset of -04:00 from GMT should be picked.
---------

Solution
===========
1. edit the file - Agent $ORACLE_HOME/sysman/config/emd.properties
from
agentTZRegion=-04:00
to
agentTZRegion= Etc/GMT+4

oracle@nsororacle:config>env agentTZRegion emd.properties
#agentTZRegion=US/Eastern
agentTZRegion=Etc/GMT+4
oracle@nsororacle:config>

2. on the command line set -
export TZ=Etc/GMT+4

oracle@nsororacle:/oracle/oem_agent/agent10g/sysman/emd> env | grep TZ
TZ=Etc/GMT+4

NB: Steps 1 and 2 are only required to set the correct timezone

3. Log in to the repository database as SYSMAN and run (again) -
SQL> select timezone_region from mgmt_targets where target_name like '%nsororacle%';

TIMEZONE_REGION
----------------------------------------------------------------
Etc/GMT+4

4. If all three match (i.e. Etc/GMT+4) - then go to the next step

NB: Step 3 sets the timezone in the repository database - if you have done this ignore steps 1-4

5. Clean out "pending" the files in -
$AGENT ORACLE_HOME/sysman/emd

eg.
rm -r $ORACLE_HOME/sysman/emd/state/*
rm -r $ORACLE_HOME/sysman/emd/collection/*
rm -r $ORACLE_HOME/sysman/emd/upload/*
rm $ORACLE_HOME/sysman/emd/lastupld.xml
rm $ORACLE_HOME/sysman/emd/agntstmp.txt

oracle@nsororacle: emd> ls
agntstmp.txt collection lastupld.xml protocol.ini recv state targets.xml upload

oracle@nsororacle: state> rm -f *
oracle@nsororacle: state> cd ../collection
oracle@nsororacle: collection> rm -f *
oracle@nsororacle: collection> cd ../upload
oracle@nsororacle: upload> rm -f *
oracle@nsororacle: emd> rm -f lastupld.xml agntstmp.txt

6. Start the agent
$AGENT_HOME/bin/emctl start agent

oracle@nsororacle:/oracle/oem_agent/agent10g/sysman/emd> emctl start agent
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Starting agent ......... started.

7. Issue an agent clearstate from the agent home
$AGENT_HOME/bin/emctl clearstate agent

oracle@nsororacle:/oracle/oem_agent/agent10g/sysman/emd>emctl clearstate agent Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
EMD clearstate completed successfully

8. Force an upload to the OMS
$AGENT_HOME/bin/emctl upload agent

oracle@nsororacle:/oracle/oem_agent/agent10g/sysman/emd> emctl upload agent
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
EMD upload completed successfully.

The agent should stop crashing now.

oracle@nsororacle:/oracle/oem_agent/agent10g/sysman/emd> emctl status agent
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 10.2.0.1.0
OMS Version : 10.2.0.1.0
Protocol Version : 10.2.0.0.0
Agent Home : /oracle/oem_agent/agent10g
Agent binaries : /oracle/oem_agent/agent10g
Agent Process ID : 24811
Parent Process ID : 24796
Agent URL : https://nsororacle.corp.nsoro.com:3872/emd/main/
Repository URL : https://nsororacle2.corp.nsoro.com:1159/em/upload
Started at : 2008-07-21 12:28:55
Started by user : oracle
Last Reload : 2008-07-21 12:28:55
Last successful upload : 2008-07-21 12:30:44
Total Megabytes of XML files uploaded so far : 6.10
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 39.77%
Last successful heartbeat to OMS : 2008-07-21 12:30:03
---------------------------------------------------------------
Agent is Running and Ready
oracle@nsororacle:/oracle/oem_agent/agent10g/sysman/emd>


=============================
Reference: Note:452481.1 - Problem: Agent Stops: The Agent Starts but crashes shortly afterwards - timezone change
=============================
Posted by at No comments:

July 10, 2008

Concurrent Request Details Query for Printing issue

Run the Following Query from SQL as apps user. You have to provide the Concurrent request ID as input.

set long 5000
set pagesize 5000
SELECT r.request_id, a.application_name,
t.user_concurrent_program_name, p.concurrent_program_name,
p.execution_method_code, p.execution_options,
p.output_file_type, p.save_output_flag, p.print_flag,
p.output_print_style, p.required_style, p.printer_name,
TO_CHAR(r.actual_completion_date, 'DD-MON-RR HH24:MI:SS'),
r.logfile_node_name, r.logfile_name, r.outfile_name,
r.nls_language, r.nls_territory, r.nls_codeset,
r.is_sub_request, r.phase_code, r.status_code,
r.completion_text, r.output_file_type, r.number_of_copies,
r.printer, n.printer_type, r.print_style,
i.printer_style, i.printer_driver, d.srw_driver,
printer_driver_method_code, spool_flag, stdin_flag,
d.command_name, d.arguments, d.initialization
FROM apps.fnd_concurrent_programs_tl t,
apps.fnd_concurrent_programs p, apps.fnd_application_tl a,
apps.fnd_concurrent_requests r, apps.fnd_printer n,
apps.fnd_printer_information i, apps.fnd_printer_drivers d,
apps.fnd_languages l
WHERE a.application_id = t.application_id
and r.concurrent_program_id = t.concurrent_program_id
and t.concurrent_program_id = p.concurrent_program_id
and n.printer_name = r.printer
and (n.printer_type = i.printer_type)
and (i.printer_driver = d.printer_driver_name)
and d.platform_code is NULL
and i.printer_style = r.print_style
AND r.nls_language = l.nls_language
AND l.language_code = t.language
AND l.language_code = a.language
and r.request_id = &REQ_ID;


The following is the sample output,

REQUEST_ID
----------
APPLICATION_NAME
--------------------------------------------------------------------------------
USER_CONCURRENT_PROGRAM_NAME
--------------------------------------------------------------------------------
CONCURRENT_PROGRAM_NAME E
------------------------------ -
EXECUTION_OPTIONS
--------------------------------------------------------------------------------
OUTP S P OUTPUT_PRINT_STYLE R PRINTER_NAME
---- - - ------------------------------ - ------------------------------
TO_CHAR(R.ACTUAL_C LOGFILE_NODE_NAME
------------------ ------------------------------
LOGFILE_NAME
--------------------------------------------------------------------------------
OUTFILE_NAME
--------------------------------------------------------------------------------
NLS_LANGUAGE NLS_TERRITORY
------------------------------ ------------------------------
NLS_CODESET I P S
------------------------------ - - -
COMPLETION_TEXT
--------------------------------------------------------------------------------
OUTP NUMBER_OF_COPIES PRINTER
---- ---------------- ------------------------------
PRINTER_TYPE PRINT_STYLE
------------------------------ ------------------------------
PRINTER_STYLE PRINTER_DRIVER
------------------------------ ------------------------------
SRW_DRIVER
--------------------------------------------------------------------------------
PRINTER_DRIVER_METHOD_CODE S S
------------------------------ - -
COMMAND_NAME
--------------------------------------------------------------------------------
ARGUMENTS
--------------------------------------------------------------------------------
INITIALIZATION
--------------------------------------------------------------------------------
669776
Payables
Invoice Register
APXINRIR P

TEXT Y Y LANDSCAPE N
26-FEB-08 16:47:57 NSORORACLE2
$COMMON_TOP//l669776.req
$COMMON_TOP//o669776.out
AMERICAN AMERICA
US7ASCII N C C
Normal completion
TEXT 1 Ricoh2228-Houston-FrontArea
HPLJ4SI LANDSCAPE
LANDSCAPE LANDSCAPEHPLJ4SI
HPL
C N N

lpr -P$PROFILES$.PRINTER -#$PROFILES$.CONC_COPIES -T"$PROFILES$.TITLE" $PROFILES
$.FILENAME
/eE/e&l1o2a5.45C/e(s0p16.66H/e&k6.75H


SQL> spool off;

This helped me for getting initial understanding towards fixing the printing issue.

.... ...
Posted by at No comments:

July 4, 2008

Fix data block corruption in 7.3.4

The database is in 7.3.4 running on HP box with a size of 9GB. This is a very old database and the box too.

After expected power failure, the Instance came up. However the application cannot access as data block was corrupted for certain data blocks.


SVRMGR> analyze table oem.invoice_file validate structure cascade;
analyze table oem.invoice_file validate structure cascade
*
ORA-01578: ORACLE data block corrupted (file # 3, block # 863317)
ORA-01110: data file 3: '/u03/oradata/js/data1a.dbf'

We are not able to do export/query or any activity with this table.

The following was resolved the issue from the metalink.

"The event 10231 allows Oracle to skip certain types of corrupted blocks on full table scans ONLY hence allowing export or "create table as select" type operations to retrieve rows from the table which are not in the corrupt block. Data in the corrupt block is lost.Set this event at session level:"

SQL> ALTER SESSION SET EVENTS '10231 TRACE NAME CONTEXT FOREVER, LEVEL 10';

Now the select * from query works and created new table using "create table as select" and drop original table.

This was fixed the data block corruption.

Reference:
28814.1 "Handling Oracle Block Corruptions in Oracle7/8/8i/9i/10g".
Posted by at No comments:

Database Block Corruption - Deduction

RMAN's BACKUP command with the VALIDATE and CHECK LOGICAL clauses allow a Database Adminstrator to quickly check for both physical and logical corruption. If the initialization parameter DB_BLOCK_CHECKSUM=TRUE, specifying CHECK LOGICAL detects all types of corruption that are possible to detect.

The following rman commands will deduct for physical/logical database corruption for the database and logs into db_validate.log file.

$ rman target / catalog rman/@rcat
RMAN> spool log to '/home/oracle/Scripts/db_validate.log';
RMAN>allocate channel for maintenance device type disk;
RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 4;
RMAN> run {
1 backup validate database;
2 backup check logical validate database;
}

To monitor this process, issue the following sql statement from SQLPLUS.

SQL> select sid, serial#, context, sofar, totalwork, round(sofar/totalwork*100,2) "%_complete"
from v$session_longops where opname like 'RMAN%' and opname not like '%aggregate%'
and totalwork != 0 and sofar <> totalwork
/

After this process completed, look for "block corruption" string in alert.log file, also query the v$database_block_corruption dynamic view, which will retrun records if there is a corruption in the database.

Reference:
Note:283053.1 - How To Use RMAN To Check For Logical & Physical Database Corruption
Posted by at No comments:

July 1, 2008

Transfer Concurrent Program Definitions - FNDLOAD

1) Log into the UNIX box
2) Go to $FND_TOP/patch/115/import/
3) Verify that the control file (lct) is in this directory – in the case of the concurrent program load it is afcpprog.lct
NOTE: Obviously you can do the execution from a different directory, e.g. there is US directory under the import directory, but I chose to keep it simple and do it under the import directory
4) Type FNDLOAD apps/simple4u@dfrwei 0 Y DOWNLOAD afcpprog.lct prog.ldt PROGRAM APPLICATION_SHORT_NAME=XBOL
5) FTP the ldt file to the server it is to be uploaded to
6) Upload the file in this order:
FNDLOAD apps/simple4u@tfrwei 0 Y UPLOAD_PARTIAL afcpprog.lct prog.ldt EXECUTABLE APPLICATION_SHORT_NAME=XBOL LANGUAGE=US

FNDLOAD apps/simple4u@tfrwei 0 Y UPLOAD_PARTIAL afcpprog.lct prog.ldt VALUE_SET APPLICATION_SHORT_NAME=XBOL LANGUAGE=US

FNDLOAD apps/simple4u@tfrwei 0 Y UPLOAD_PARTIAL afcpprog.lct prog.ldt VSET_TABLE APPLICATION_SHORT_NAME=XBOL LANGUAGE=US

FNDLOAD apps/simple4u@tfrwei 0 Y UPLOAD_PARTIAL afcpprog.lct prog.ldt DESC_FLEX APPLICATION_SHORT_NAME=XBOL LANGUAGE=US

FNDLOAD apps/simple4u@tfrwei 0 Y UPLOAD_PARTIAL afcpprog.lct prog.ldt PROGRAM APPLICATION_SHORT_NAME=XBOL LANGUAGE=US
7) That’s it – verify that the load worked by reviewing the log file and the application
NOTE: It would only allow me to upload once per session; if I log into UNIX with the terminal emulator and run upload it will not allow me to run upload again… I have to log out of UNIX and log back in. I’m sure this is a setting at the UNIX or terminal emulator that I was missing.
FNDLOAD apps/pwd 0 Y mode configfile datafile entity [ param ... ]

Parameter
Use

The APPS schema and password in the form username/password[@connect_string]. If connect_string is omitted, it is taken in a platform–specific manner from the environment using the name TWO_TASK.
<>
Concurrent program flags
Mode
UPLOAD or DOWNLOAD. UPLOAD causes the datafile to be uploaded to the database. DOWNLOAD causes the loader to fetch rows and write them to the datafile.

The configuration file to use (usually with a suffix of .lct, but not enforced or supplied by the loader).

The data file to write (usually with a suffix of .ldt, but not enforced or supplied by the loader). If the data file already exists, it will be overwritten.

The entity(ies) to upload or download. When uploading, you should always upload all entities, so specify a ”–” to upload all entities.
< [param] >
Zero or more additional parameters are used to provide bind values in the access SQL (both UPLOAD and DOWNLOAD). Each parameter is in the form NAME=VALUE. NAME should not conflict with an attribute name for the entities being loaded.



Concurrent Program Configuration File
The concurrent program configuration file afcpprog.lct downloads and uploads concurrent program definitions. It takes as parameters program name and application name. The following table lists the entities, sub–entities (if any), and download parameters for this configuration file.

Entity
Sub–entities, if any
Download Parameters
PROGRAM
INCOMPATIBILITY
CONCURRENT_PROGRAM_NAME, APPLICATION_SHORT_NAME
EXECUTABLE

EXECUTABLE_NAME




cd $FND_TOP/patch/115/import

cp credit.ldt /interface/inffrwei/TFRWEI/incoming/

cp /interface/inffrwei/TFRWEI/incoming/credit.ldt credit.ldt


FNDLOAD apps/simple4u@dfrwei 0 Y DOWNLOAD afcpprog.lct credit.ldt PROGRAM CONCURRENT_PROGRAM_NAME=FRWECRDSUM


FNDLOAD apps/simple4u@tfrwei 0 Y UPLOAD_PARTIAL afcpprog.lct credit.ldt EXECUTABLE CONCURRENT_PROGRAM_NAME=FRWECRDSUM LANGUAGE=US

cd $FND_TOP/patch/115/import

FNDLOAD apps/simple4u@tfrwei 0 Y UPLOAD_PARTIAL afcpprog.lct credit.ldt VALUE_SET CONCURRENT_PROGRAM_NAME=FRWECRDSUM LANGUAGE=US

exit

cd $FND_TOP/patch/115/import

FNDLOAD apps/simple4u@tfrwei 0 Y UPLOAD_PARTIAL afcpprog.lct credit.ldt VSET_TABLE CONCURRENT_PROGRAM_NAME=FRWECRDSUM LANGUAGE=US

exit

cd $FND_TOP/patch/115/import

FNDLOAD apps/simple4u@tfrwei 0 Y UPLOAD_PARTIAL afcpprog.lct credit.ldt DESC_FLEX CONCURRENT_PROGRAM_NAME=FRWECRDSUM LANGUAGE=US

exit

cd $FND_TOP/patch/115/import

FNDLOAD apps/simple4u@tfrwei 0 Y UPLOAD_PARTIAL afcpprog.lct credit.ldt PROGRAM CONCURRENT_PROGRAM_NAME=FRWECRDSUM LANGUAGE=US

exit
Posted by at No comments:

May 1, 2008

ERROR: NMO not setuid-root (Unix-only)

Problem: I had an issue of cloning database from OEM due to unix oracle OS user id. So I had changed the uid of oracle OS user by usermod -u 501 command. And then I was trying to defined the clone job, it does not connect with Destination and issued the following error.

ERROR: NMO not setuid-root (Unix-only)

Solution:

1. Connect as oracle user to the host giving the connection error (we assume that oracle is the OS user which installed the Grid Management Agent)

2. Stop the Grid Management Agent
$ cd $ORACLE_HOME/bin
$ ./emctl stop agent

3. Connect with the user root, keeping the oracle user environment

4. cd to the Management Agent ORACLE_HOME

5. Run the root.sh script
$ ./root.sh

6. Connect back to the oracle user

7. Restart the Grid Management Agent
$ cd $ORACLE_HOME/bin
$ ./emctl start agent


Ref:
Note:363108.1 - Problem: ERROR: NMO not setuid-root (Unix-only) in Grid Control
Posted by at No comments:

April 29, 2008

OEM - Unable to access Recovery Catalog

Problem: Managing the Production database from Oracle Enterprise Manager Grid control. The recovery catalog is available, the database is registered in recovery catalog, but still OEM gives an error,

Error
Only databases with a version number equal to 10 or above, or databases that use a recovery catalog of schema version 10 or above are supported. You can click the following link to register the database in a recovery catalog.
Register Database In Recovery Catalog


Solution:
1. In recovery catalog database server, login rman with catalog option.

$> rman catalog sysman/******
RMAN> upgrade catalog;

recovery catalog owner is SYSMAN
enter UPGRADE CATALOG command again to confirm catalog upgrade

RMAN> upgrade catalog

recovery catalog upgraded to version 10.01.00
DBMS_RCVMAN package upgraded to version 10.01.00
DBMS_RCVCAT package upgraded to version 10.01.00

RMAN>

Now if you refresh the OEM page and go to maintenance(T) -> manage current backup URL, it'lll work.

Reference:
Note:298466.1 - Cannot Manage Current Backups with Grid Control even when Recovery Catalog is used
Posted by at No comments:

April 16, 2008

Rman backup restore and recover to a new host - Backup "test"

The Restore of a Database to a New Host: Scenario

This scenario assumes the following:
  1. Two networked machines, oracle1 and oracle3, are running Linux.
  2. A target database named srinfra is on oracle1 and uses a recovery catalog rcat
  3. You want to test the restore and recovery of srinfra on oracle3, while keeping database srinfra up and running on oracle1
  4. The directory structure of oracle1 is different from oracle1, so that srinfra is located in /uXX/oradata/srinfra, but you want to restore the database to /u01/oradata/srinfra
    Database srinfra uses a server parameter file (not a client-side initialization parameter file)
  5. The ORACLE_SID for the srinfra database is srinfra and will not change for the restored database
  6. You have a record of the DBID for srinfra
  7. A media manager is accessible by both machines
  8. You have recoverable backups on tape of all datafiles
  9. You have backups of the archived logs required to recover the datafiles
  10. You have control file and server parameter file autobackups on tape

Use the following steps to perform the restore process:

  1. Make backups of the target database available to oracle3. To test disaster recovery, you need to have a recoverable backup of the target database. When preparing your disaster recovery strategy, ensure that the backups of the datafiles, control files, and server parameter file are restorable on oracle3. Hence, you must configure the media management software so that oracle3is a media manager client and can read the backup sets created on oracle1. Consult the media management vendor for support on this issue.
  2. Configure the ORACLE_SID on oracle3. This scenario assumes that you want to authenticate yourself through the operating system, which is much faster than configuring Oracle Net and creating a password file. However, you must be connected to oracle3 either locally or through a SQLNet alias.
    While connected to oracle3 with administrator privileges, edit the /etc/group file so that you are included: in the DBA group:
    dba:*:614:oracle
    Set the ORACLE_SID environment variable on oracle3 to the same value used on oracle1:
    $ export ORACLE_SID srinfra
    Start RMAN and connect to the target instance without connecting to the recovery catalog.
    $ rman TARGET / CATALOG rman/xxxx@rcat
  3. Start the instance without mounting it. To start the instance, you first need to set the DBID.
    Run SET DBID to set the DBID, then run STARTUP NOMOUNT:
    RMAN> SET DBID 1340752057;
    RMAN> STARTUP NOMOUNT;

    RMAN will fail to find the server parameter file, which has not yet been restored, but will start the instance with a "dummy" file. Sample output follows:
    startup failed: ORA-01078: failure in processing system parameters
    LRM-00109: could not open parameter file '/u01/app/oralce/product/10g/dbs/initsrinfra.ora'

    trying to start the Oracle instance without parameter files ...
    Oracle instance started

    Restore and edit the server parameter file.
    Because you enabled the control file autobackup feature when making your backups, the server parameter file is included in the backup sets.
    Allocate a channel to the media manager, then restore the server parameter file (SPFILE) as a client-side pararameter file (PFILE).
    RMAN> RUN {
    ALLOCATE CHANNEL t1 DEVICE TYPE "SBT_TAPE"
    PARMS='SBT_LIBRARY=/u01/app/oracle/product/10g/lib/libobk.so,
    ENV=(NSR_CLIENT=ORACLE1.VOCOLLECT.INT,
    NSR_SERVER=LEGATO1.INTERNAL,
    NSR_DATA_VOLUME_POOL=VCDBO)';

    SET UNTIL TIME="TO_DATE('16-MAR-08 23:59:59','DD-MON-YY HH24:MI:SS')";
    RESTORE SPFILE TO PFILE '/u01/app/oralce/product/10g/dbs /initsrinfra.ora' FROM AUTOBACKUP;

    SHUTDOWN ABORT;
    }

    Next, edit the restored PFILE . Change any location-specific parameters, for example, those ending in _DEST and _PATH, to reflect the new directory structure. For example, edit the following parameters:
    - IFILE
    - *_DUMP_DEST
    - LOG_ARCHIVE_DEST*
    - CONTROL_FILES

    Then restart the instance, using the edited PFILE:
    RMAN> STARTUP FORCE NOMOUNT PFILE='/u01/app/oralce/product/10g/dbs /initsrinfra.ora';

    Restore the control file from an autobackup and then mount the database. RMAN restores the control file to whatever location you specified in the CONTROL_FILES initialization parameter. For example:
    RMAN> RUN {
    ALLOCATE CHANNEL t1 DEVICE TYPE "SBT_TAPE"
    PARMS='SBT_LIBRARY=/u01/app/oracle/product/10g/lib/libobk.so,
    ENV=(NSR_CLIENT=ORACLE1.VOCOLLECT.INT,
    NSR_SERVER=LEGATO1.INTERNAL,
    NSR_DATA_VOLUME_POOL=VCDBO)';

    SET UNTIL TIME="TO_DATE('16-MAR-08 23:59:59','DD-MON-YY HH24:MI:SS')";
    RESTORE CONTROLFILE FROM AUTOBACKUP;
    ALTER DATABASE MOUNT;
    }
    Query the database filenames recorded in the control file on the new host (oracle3). Because the control file is from the “srinfra” database, the recorded filenames use the original oracle1 filenames. You can query V$ views to obtain this information. Start a new SQL*Plus session and connect to the newly created instance on oracle3:
    $ sqlplus '/ AS SYSDBA'
    Run the following query in SQL*Plus:
    SQL> COLUMN NAME FORMAT a60
    SQL> SPOOL 'db_filenames.out'
    SQL> SELECT FILE# AS "File/Grp#", NAME FROM V$DATAFILE
    UNION
    SELECT GROUP#,MEMBER FROM V$LOGFILE;
    SQL> SPOOL OFF
    SQL EXIT

    Write the RMAN recovery script. The script must include the following steps:
    For each datafile on the destination host that is restored to a different path than it had on the source host, use a SET NEWNAME command to specify the new path on the destination host. (If the file systems on the destination system are set up to have the same paths as the source host, then do not use SET NEWNAME for those files restored to the same path as on the source host.)
    For each online redo log that is to be created at a different location than it had on the source host, use SQL ALTER DATABASE RENAME FILE commands to specify the pathname on the destination host. (If the file systems on the destination system are set up to have the same paths as the source host, then do not use ALTER DATABASE RENAME FILE for those files restored to the same path as on the source host.)
    Perform a SET UNTIL to limit media recovery to the end of the archived redo logs.
    Run SWITCH so that the control file recognizes the new path names as the official new names of the datafiles
    Restore and recover the database
    RUN{
    # allocate a channel to the tape device
    ALLOCATE CHANNEL t1 DEVICE TYPE "SBT_TAPE"
    PARMS='SBT_LIBRARY=/u01/app/oracle/product/10g/lib/libobk.so,
    ENV=(NSR_CLIENT=ORACLE1.VOCOLLECT.INT,
    NSR_SERVER=LEGATO1.INTERNAL,
    NSR_DATA_VOLUME_POOL=VCDBO)';

    ALLOCATE CHANNEL t2 DEVICE TYPE "SBT_TAPE"
    PARMS='SBT_LIBRARY=/u01/app/oracle/product/10g/lib/libobk.so,
    ENV=(NSR_CLIENT=ORACLE1.VOCOLLECT.INT,
    NSR_SERVER=LEGATO1.INTERNAL,
    NSR_DATA_VOLUME_POOL=VCDBO)';

    ALLOCATE CHANNEL t3 DEVICE TYPE "SBT_TAPE"
    PARMS='SBT_LIBRARY=/u01/app/oracle/product/10g/lib/libobk.so,
    ENV=(NSR_CLIENT=ORACLE1.VOCOLLECT.INT,
    NSR_SERVER=LEGATO1.INTERNAL,
    NSR_DATA_VOLUME_POOL=VCDBO)';

    # rename the datafiles and online redo logs
    SET NEWNAME FOR DATAFILE 00001 TO '/u01/oradata/srinfra/system01.dbf';
    SET NEWNAME FOR DATAFILE 00002 TO '/u01/oradata/srinfra/undotbs01.dbf';
    SET NEWNAME FOR DATAFILE 00003 TO '/u01/oradata/srinfra/sysaux01.dbf';
    SET NEWNAME FOR DATAFILE 00004 TO '/u01/oradata/srinfra/srdata01.dbf';
    SET NEWNAME FOR DATAFILE 00005 TO '/u01/oradata/srinfra/SRIDX01.dbf';
    SET NEWNAME FOR DATAFILE 00006 TO '/u01/oradata/srinfra/srlarge01.dbf';
    SET NEWNAME FOR DATAFILE 00007 TO '/u01/oradata/srinfra/srlarge02.dbf';
    SET NEWNAME FOR DATAFILE 00008 TO '/u01/oradata/srinfra/srlarge03.dbf';
    SET NEWNAME FOR DATAFILE 00009 TO '/u01/oradata/srinfra/srlarge04.dbf';
    SET NEWNAME FOR DATAFILE 00010 TO '/u01/oradata/srinfra/SRIDX02.dbf';
    SET NEWNAME FOR DATAFILE 00011 TO '/u01/oradata/srinfra/SRDATA02.dbf';
    SET NEWNAME FOR DATAFILE 00012 TO '/u01/oradata/srinfra/undotbs02.dbf';
    SET NEWNAME FOR DATAFILE 00013 TO '/u01/oradata/srinfra/srlarge05.sbf';
    SET NEWNAME FOR DATAFILE 00014 TO '/u01/oradata/srinfra/srdata03.dbf';
    SET NEWNAME FOR DATAFILE 00015 TO '/u01/oradata/srinfra/srdata04.dbf';
    SET NEWNAME FOR DATAFILE 00016 TO '/u01/oradata/srinfra/sridx03.dbf';
    SET NEWNAME FOR DATAFILE 00017 TO '/u01/oradata/srinfra/sridx04.dbf';
    SET NEWNAME FOR DATAFILE 00018 TO '/u01/oradata/srinfra/srdata05.dbf';
    SQL "ALTER DATABASE RENAME FILE ''/u05/oradata/srinfra/redo01-1.log'' TO ''/u01/oradata/srinfra/redo01-1.log''";
    SQL "ALTER DATABASE RENAME FILE ''/u01/oradata/srinfra/redo01-2.log'' TO ''/u01/oradata/srinfra/redo01-2.log''";
    SQL "ALTER DATABASE RENAME FILE ''/u05/oradata/srinfra/redo02-1.log'' TO ''/u01/oradata/srinfra/redo02-1.log''";
    SQL "ALTER DATABASE RENAME FILE ''/u01/oradata/srinfra/redo02-2.log'' TO ''/u01/oradata/srinfra/redo02-2.log''";
    SQL "ALTER DATABASE RENAME FILE ''/u05/oradata/srinfra/redo03-1.log'' TO ''/u01/oradata/srinfra/redo03-1.log''";
    SQL "ALTER DATABASE RENAME FILE ''/u05/oradata/srinfra/redo03-2.log'' TO ''/u01/oradata/srinfra/redo03-2.log''";

    # Do a SET UNTIL TO prevent recovery of the online logs
    SET UNTIL TIME="TO_DATE('16-MAR-08 23:59:59','DD-MON-YY HH24:MI:SS')"; # restore the database and switch the datafile names
    RESTORE DATABASE;
    SWITCH DATAFILE ALL;

    # recover the database
    RECOVER DATABASE;
    }

    RMAN> EXIT;
    RMAN will apply as many of the archived redo logs as it can and leave the database in a state in which is can be opened.
    Now perform an OPEN RESETLOGS at the restored database.
    Caution: When you re-open your database in the next step, do not connect to the recovery catalog. Otherwise, the new database incarnation created is registered automatically in the recovery catalog, and the filenames of the production database are replaced by the new filenames specified in the script.
    If this is a test restore, never connect RMAN to the test-restore database and the recovery catalog.
    From the RMAN prompt, open the database with the RESETLOGS option:
    $ rman TARGET /

    RMAN> ALTER DATABASE OPEN RESETLOGS;

Posted by at No comments:

January 4, 2008

Huge Log files Generated by OMS

PROBLEM Description:

When monitoring the OMS logfiles, for my surprise there was 803G (yes it's Gig) logfiles where genereated at $OMS_HOME/opmn/logs directory. Each log file has 1.5G in size. The contents looks like the following,

$ tail ons.log.08-01-03_15:03:5608/01/03 15:03:56 [4] Local connection 0,127.0.0.1,6101 missing form factor08/01/03 15:03:56 [4] Local connection 0,127.0.0.1,6101 missing form factor08/01/03 15:03:56 [4] Local connection 0,127.0.0.1,6101 missing form factor08/01/03 15:03:56 [4] Local connection 0,127.0.0.1,6101 missing form factor08/01/03 15:03:56 [4] Local connection 0,127.0.0.1,6101 missing form factor

Cause: 6101 port was used by some other process

Solution:

Change this port (6101) number from $OMS_HOME/opmn/config/opmn.xml file with value range 6102 to 6109.

Take the backup of $OMS_HOME/opmn/config/opmn.xml file.

$ cp opmn.xml opmn.xml.orig
$ vi opmn.xml


as


save and exit.

stop all OMS serverices

$ opmnctl stopall
$ emctl stop oms

Update the config changes with DCM reporsitory

$ cd $OMS_HOME/dcm/bin
$ dcmctl updateConfig -d -v

Now start the opmn processes.

$ opmnctl startall
$ emctl start oms

=====================

Reference:
Note:444387.1 - Problem: Grid Control Oms Generate Huge Ons Logs
Posted by at No comments:
Subscribe to: Posts (Atom)